Misconin Labs

02 · Running

Runalysis

I start a tracker while Google Fit records the run anyway. Each reading becomes a point in a series. That series is one run — something I can compare, analyze, and keep, including a fastest stretch that happens in the middle of a longer day.

Two runs on one pace chart, with cadence and heart rate as other things you can select A list of saved runs with distance, time, and split paces A records grid that finds a stretch of a given length anywhere in the log
Two runs on one chart. Pace here; cadence and heart rate are the other switches.
Compare
Runs on one chart
Along a run
Pace, cadence, heart rate
A stretch
Any length, starting anywhere
Where
On my phone
Each frame is a screenshot of Fit — one point. The blue dot is where I was.
A 10K pace chart with one stretch highlighted
One run drawn out. The lit bit is a stretch I asked for, not a medal.

What it is

Fit is already timing the run. Runalysis sits beside it, builds a series of points, and lets me do the rest: compare days, look at pace or cadence, file the archive, or find a fastest segment that did not start at the gun.

How this actually works

Starting the Runalysis tracker begins taking timed screenshots of the Google Fit screen. The app reads each one and stores what it finds — distance, duration, steps, calories. One screenshot is one data point. The points in order are one run. A compile is those pictures played back, so you can watch the blue dot move.

From that series I can compare runs, look at pace, cadence, or heart rate, keep the archive, and ask for a fastest stretch of any length, even when it sits in the middle of a longer run.