Open almost any walking or running app and the first thing it asks you to do is press start, which quietly switches on GPS for the entire session. For a twenty-minute run that's a reasonable trade. For a dog owner who's out for an hour, twice a day, every single day, it adds up to a phone that's noticeably warmer in your pocket and a battery that's noticeably worse by evening — the kind of drain people eventually stop noticing because they've just accepted it as the cost of using a fitness app at all.

It isn't actually the cost of tracking a walk. It's the cost of tracking a walk with the wrong sensor.

How phones actually count a walk

Every modern iPhone has a small, dedicated low-power chip — Apple calls it the motion coprocessor — that does nothing but watch the accelerometer and gyroscope and count steps, all the time, using a tiny fraction of the power a GPS radio needs. It's the same hardware that's already feeding the Health app's step count before you've opened a single third-party app. Hapoo reads from that same source rather than requesting its own continuous GPS fix.

GPS, by contrast, works by triangulating your position against satellites (and often supplementing that with Wi-Fi and cell-tower data when satellites are weak), which means the radio has to stay powered on and actively communicating for as long as the app wants a location. That's an entirely different order of power draw than a motion chip passively counting acceleration patterns — GPS is built to answer "where," and answering "where" continuously is expensive. Motion sensing is built to answer "did movement consistent with walking just happen," and that's a much cheaper question.

Hapoo only needs the second question answered. It doesn't need to know where you walked to know that you walked — it just needs enough signal to tell a real walk apart from, say, folding laundry or a car journey, for long enough to count. That's a battery-cheap distinction to make from motion data alone.

Where GPS still comes in

GPS switches on only when you explicitly ask for a traced route, because that's the one feature that genuinely needs to know where you went — a route worth looking back on, or worth sharing as a card with the shape of the walk on it. That's a deliberate, opt-in cost for a specific, deliberate benefit, rather than something running in the background on every single walk whether you asked for it or not.

The same logic extends to the rest of the app. The Live Activity in the Dynamic Island, for instance, only appears during a traced walk you started on purpose — it isn't quietly polling your location the rest of the day to be ready for one.

The trade-off, stated plainly

This does mean Hapoo can't show you a map of every walk you've ever taken unless you asked for a trace at the time it happened — there's no background location log to retroactively draw a route from. That's not an oversight, it's the actual trade being made: continuous location logging is precisely the always-on cost this whole approach exists to avoid, so it isn't quietly kept running for a feature most walks don't use.

The alternative — running location services all day, every walk, just in case you might want a map of one of them later — is the exact trade a lot of walking and fitness apps make on your behalf without ever really asking. Most people who complain a fitness app "drains their battery" have never opened a settings screen to see which app is doing it or why; they've just noticed their phone runs hotter and their evening battery percentage is worse on days they went for a walk with the app open. That's almost always continuous GPS, not anything inherent to tracking a walk at all.

Why this matters more for a dog walking app specifically

A running app might get opened for thirty minutes, a few times a week. A dog gets walked once or twice a day, every day, for years. Any inefficiency in how an app counts that gets multiplied by a much larger number of actual sessions than most fitness tracking use cases ever see. Battery cost that's merely annoying in a running app becomes a real, cumulative problem in a dog walking app used this often — which is exactly why it was worth building the counting mechanism around the cheapest sensor that could actually do the job, rather than reaching for the most capable one by default.

See how it's built for the rest of the technical shape of the app — the same "don't ask for more than the feature actually needs" principle shows up in how photos are checked on-device, and in the device-identity model instead of an account.

A few things people ask

Does this mean Hapoo can't tell how far I walked? It can — distance comes from the same motion data, just not a plotted route on a map unless you traced it.

Will a traced walk still drain my battery the normal amount? Yes, roughly what any app using GPS would cost for that session — the saving comes from not paying that cost on every walk by default, not from making GPS itself free.

What if I always want a map, every walk? Then tracing every walk is a reasonable choice to make deliberately — the point isn't that GPS is bad, it's that it should be a choice you're making on purpose, not a background cost you never agreed to.