TEN:TWENTY

TEN:TWENTY answers one question, continuously: where exactly am I. It reads GPS, resolves the road underneath you, and prints the block, the street, the cross street ahead, your direction of travel and your speed. On the radio that is the difference between giving dispatch a location and giving them an approximation.

Road identity. A phone knows its coordinates; it does not know which road those coordinates belong to. Frontage roads run parallel to a highway within a few meters. Exits branch and rejoin. Geocoders return averaged or stale results, and address ranges simply do not exist on a lot of county road. Most of the engineering time went into deciding which road you are actually on, and into the harder half of that problem — knowing when the answer is not good enough to print.

When block data cannot be trusted the app prints BLOCK DATA UNAVAILABLE and falls back to street and coordinates.

That is a decision, not a gap. A wrong block number read aloud on the radio sends people to the wrong place. An empty field sends them to ask. The app is built to be wrong as rarely as possible and to admit it immediately when it is.

RoadIdentityResolver

which road the current position belongs to

RoadContextService

road context across transitions

ExitResolver

highway exits and their numbering

MapKit / CoreLocation

position, map, reverse geocoding, turn-by-turn

OpenStreetMap Overpass

cross streets and exit numbers — the only non-Apple call

WatchConnectivity

iPhone to Watch relay, device to device

App Intents

Siri and the Action Button, on device

Everything on the device. No accounts, no server, no analytics.

Shift recordings — GPS track, timestamps, notes — are written to the device and leave it only through the share sheet, when you send them. There is no copy on our side to subpoena, lose, or hand over. See the privacy policy for the full accounting.

support · terms · privacy · field testing