Why doesn’t your location history show what you actually did?

Your phone can say, with real confidence, exactly where you stood at 11:42 on a Wednesday three weeks ago. Open the location history and there is the trail: home, a stretch downtown, a building near the gym, home again. It looks, at a glance, like a record of the day. Read it closely and it is not one. It knows where you were. It has no idea what you were doing once you got there, and that gap turns out to be most of what a day actually consists of.

A pin marks a place, not an event

Location history is built entirely out of coordinates and timestamps. "Downtown, 11:40am–1:15pm" is the whole entry, and that single line is compatible with dozens of completely different afternoons. It could be a lunch that ended a six-month negotiation. It could be forty-five minutes circling a parking garage before giving up and eating alone. The dot on the map is identical either way, because a dot only ever records where a phone was, and a phone does not know what happened around it.

Dwell time looks like tracking but is not

Most location apps surface a duration next to each stop — how long you were "at" a place — and that number invites the same mistake a screen time report invites: it reads like a measurement of the day, when it is only a measurement of proximity to a set of coordinates. Ninety minutes at an address could be the best ninety minutes of the week or the most tedious. The clock running underneath a GPS dot does not know the difference, because it was never built to ask.

Most days collapse to the same two addresses

For a large share of people, a location trail is not even especially varied — it is home, then one other building, then home again, five days running. That repetition is not a flaw in the data. It is an accurate reflection of where a body spends its hours. But it means the trail cannot tell two very different weeks apart. A week where something at that same desk finally clicked into place, and a week where nothing did, produce an identical map. The address stayed put. Everything that actually varied happened inside it, where GPS cannot see.

Indoors, it gets worse

Signal degrades the moment you step inside anything larger than a house. A shopping center, an office campus, a hospital, a train station — all of them tend to blur into a single smeared dot or a handful of jumping pings, because GPS was designed to work outdoors, looking at satellites, not to distinguish which floor or which shop a person is actually in. A short errand between two nearby addresses sometimes never registers as its own stop at all, folded into whichever stop came before or after it. The map gets least reliable exactly where a real day tends to have the most going on — inside buildings, doing things.

What a location trail is genuinely good for

None of this makes location history useless — it answers a narrow, specific question extremely well: was I near a particular place on a particular date? That is worth having when you are trying to remember where you parked, confirm a visit for an expense report, or work out which store you must have left something in. It is a record of proximity, kept automatically, and for exactly that use it beats memory every time. It was just never built to answer the much larger question of what the day was actually like once you arrived somewhere.

Where and what are different questions

This is the same split that shows up between a calendar and a record of what happened, or a screen time chart and an actual account of an evening. A location trail can tell you the shape of your movement through a day with total confidence. It cannot tell you what any of it meant, because meaning was never something GPS was built to capture — only coordinates were.

About TimeMap

TimeMap fills in the part a location trail leaves blank. Instead of coordinates logged automatically in the background, you write a short line about what is actually happening, wherever you happen to be, and give it a colour. Nothing about it depends on signal strength or which floor of a building you are on — the entry is about the thing itself, not about the phone's ability to triangulate it.

Keep your location history running for what it is genuinely good at: knowing where you were. Just do not expect it to also tell you, months later, what any of that time actually held. That is a different record, and it has to be written by someone who was paying attention to the day, not just to the satellites.