中文

The fake bends in your running route, and how they get deleted.

2026-11-22 · Pure Pace

Finish a new route and open the map, and you tend to see two things: a stretch you never ran — a straight line through a building, a leg across the river — or a loop you drew several times. There is a subtler one too: the distance is a few hundred metres longer than you expected, the pace slows down, and you conclude you had a bad day.

None of that is fairly summarised as “GPS is inaccurate”. Every fix is a point plus an accuracy radius: between buildings, under a bridge, beneath trees, that circle can be tens of metres across. What Pure Pace does is decide which fixes are worth believing, then remove the rest from the distance, the pace and the route together.

A point is not a path

The location service hands over a latitude and longitude, a timestamp and a horizontal accuracy in metres. The core system has already computed a great deal for you, but it will not do one thing: decide whether this fix is “the person is really here”.

We spent a while writing rules, one per bad case we saw. They fought each other: a rule added to fix A made the route around B stutter. What survived is a single entry point — GPSGate: every fix goes through it first, and only what comes out the other side reaches distance, splits, the route and the announcements.

Five gates, and one re-anchor

Each incoming fix has to answer five questions in turn; fail any and it is dropped and never enters the distance calculation:

There is one separate rescue, aimed at the ugliest kind of start: a stationary re-anchor. If two consecutive fixes both report a Doppler speed below 0.5 m/s and both land within 30 metres of the accepted track, the person is not moving and the location is drifting — so the head of the chain is moved to the new position without adding any distance. That way a day's record does not quietly gain tens of metres, and the route does not leave home in a spike and come back.

Distance: the straight lines between accepted fixes, summed

There is no shortcut: the great-circle distance between each pair of accepted fixes (haversine, Earth radius 6,371,000 m), summed. The start counts as 0 metres.

Each kilometre is triggered the moment “distance divided by 1000, rounded down” crosses an integer: the split time is recorded and one announcement is spoken. Split paces are derived from those same crossings, off the same set of points — so total distance and the sum of the splits cannot disagree.

Elevation is a different algorithm: a 3-metre hysteresis. Only when the fix is more than 3 metres above the last reference point is ascent added and the reference raised; dropping more than 3 metres only moves the reference down, never subtracts ascent. GPS altitude wobbles by tens of centimetres, which will not become a mountain, and a real hill is not lost. The live screen and the detail screen run the same calculation, so the two numbers always match.

Why China mainland needs one extra conversion

Apple Maps shows GCJ-02 coordinates in mainland China, while the location callback returns international WGS-84. The two differ by hundreds of metres — measured the same way in four cities: about 555 m in Beijing, 482 m in Shanghai, 622 m in Guangzhou and 364 m in Chengdu. Draw WGS-84 points straight onto a GCJ-02 map and the whole route shifts; it looks like you ran along the river.

Pure Pace's handling is restrained: storage, backup and distance all use WGS-84, and the conversion to GCJ-02 happens only at the step where points are drawn on the map, only inside the land boundary, with a 2-kilometre transition band outside it and no conversion for Hong Kong, Macau or Taiwan. The data itself stays a clean, internationally usable set of coordinates, and no map tool needs a second thought later.

The pause button on the lock screen, and the voice in your pocket

Nobody unlocks a phone mid-run. So distance, time, pace and the pause button live on the lock-screen Live Activity, and pressing pause really stops the recording rather than dismissing a banner. To save power, state is pushed at most every 3 seconds; each kilometre and each pause is pushed immediately.

The voice announcements had one trap worth describing: while the phone is locked, calling the system speak API does not start the queue and gives no callback at all. We found that on real devices. The fix is unglamorous but solid: synthesise the sentence to an audio file offline, then play it with an ordinary audio player. That works locked, in the background, face down in a pocket. A system vibration goes first — haptics are barely perceptible through fabric.

During an announcement the audio session ducks other audio rather than interrupting it: your music drops a little, then comes back. Nobody wants their song cut off for a pace number.

Deliberately not done

No auto-pause. It sounds considerate, but it has to guess between “you stopped” and “you are waiting at a light”, and one wrong guess eats a stretch of distance. Better to press a button than to own a record that edits itself.

No cloud sync. Records live in a local SQLite database, and backup is a JSON file you decide where to send. On import the app checks each record's id: what it already has is skipped, what it lacks is added, and existing data is never overwritten. When you change phones, that caution is worth more than one-tap sync.

No home-screen widget. The widget exists only to carry the live activity during a workout; it does not park a static mileage number on your home screen. Data is for looking back at, not for staring at.

The only network communication is Apple's in-app purchase. No account, no ads, no analytics, no crash reporting; workout data stays on this phone.

See Pure Pace

App Store: id6813886824 · iPhone, iOS 15.1 or later · Free download, Pro comes with a free 7-day trial, then a one-time purchase

Keep reading

Products: Sealion Seacat Seaflower Seaspider Seasnipe Seastar Seadog Jiong WBXL Xultray webapp
Blink templateJS skiafy tranid Yimaji WenYaJi DanceDouble Pure Pace mkok i.zhuatang 原创歌曲
(C) 2026 ZHUATANG.COM, All rights reserved
This site counts visits with Google Analytics and a small first-party log (IP address, page and referrer, no cookies), only to improve these pages; the apps themselves ship no analytics SDK whatsoever.
媒体素材 / Press Kit · Blog

update: 2026-11-22