toviaA place-tracking app sounds like something that should destroy your battery.
That was one of the first problems we thought about while building Tovia.
If an app wants to remember where you go, the obvious solution seems to be simple: keep GPS running, collect coordinates all day, and reconstruct everything afterward.
It also happens to be a poor fit for the kind of product we wanted to build.
Tovia isn’t trying to draw a second-by-second trail of everywhere you move. It is trying to answer a quieter question:
Where did you actually spend time?
That distinction changes how location tracking can work.
Tracking a route and recognizing a visit are different problems
Imagine a normal morning.
You leave home, walk to the subway, travel across town, pick up coffee, and arrive at the office.
A continuous GPS tracker might try to collect points throughout that entire journey:
8:21:04 — here
8:21:15 — here
8:21:27 — here
8:21:41 — here
That can be useful if you are recording a run, cycling route, or hike.
But for a personal life timeline, most of those coordinates are not particularly meaningful.
The things you are more likely to want to remember are:
Home — left at 8:20
Coffee shop — stayed 18 minutes
Office — arrived at 9:12
Tovia is built primarily around these visits, rather than around a continuous breadcrumb trail.
iPhone already knows how to recognize visits
Apple’s Core Location framework includes a service specifically designed around places where someone spends time: Visits.
Apple describes the Visits location service as its most power-efficient way to receive location information. Rather than providing a continuous stream of high-frequency location updates, the system monitors places someone visits and the time spent there, then delivers visit-related events to the app.[1]
In code, developers enable this behavior using:
startMonitoringVisits()When iOS detects a visit, it can provide a CLVisit object containing:
- a representative coordinate;
- horizontal location accuracy;
- an approximate arrival time; and
- an approximate departure time when available.
Apple documents these properties as part of CLVisit.[2]
That gives Tovia the raw ingredients for a visit without requiring the app to continuously request precise standard location updates throughout the day.
Why that matters for battery life
Not all forms of location tracking cost the same amount of energy.
Apple explicitly distinguishes between its location services. The standard location service provides more regular and precise location updates, but uses more power. The Visits service is designed to be substantially more power-efficient for applications that care about places and stays rather than continuous movement.[1]
That fits Tovia unusually well.
We care much more about:
You arrived here.
You stayed for a while.
You left.
than:
Your phone moved another 14 meters.
So instead of treating your entire day as a stream of GPS points, Tovia lets iOS do much of the work of recognizing meaningful stays.
The simplest way to describe it is:
Tovia listens for places, rather than constantly drawing your path.
What a visit actually looks like
Suppose you arrive at a café at 10:14.
At some point, iOS determines that you have meaningfully stayed there and provides Tovia with visit information.
A simplified record might look like:
Coordinate: nearby café location
Arrival: approximately 10:14
Departure: not known yet
Apple notes that a visit may initially contain only an arrival time. Later, when the person leaves, the system can deliver updated information including the departure time. Both arrival and departure times are approximate rather than exact measurements.[2]
Tovia can then turn that system-level visit into something much more human:
Blue Bottle Coffee
10:14 – 11:32
1h 18m
Coffee
The first part comes from the operating system.
The meaning comes from Tovia.
A coordinate is not yet a place
This is an important distinction.
Core Location can tell an app roughly where a visit occurred.
It does not inherently tell Tovia:
“You were at this exact branch of this exact café.”
The visit coordinate still needs to be interpreted.
Tovia can use map and point-of-interest information to associate that coordinate with a real place. And because location measurements always contain uncertainty, that result can occasionally be wrong.
A phone might think you were closer to the restaurant downstairs than the office above it.
A large shopping center may contain dozens of possible places.
A GPS position may drift toward the neighboring building.
That is why Tovia treats the system coordinate as an observation, not an unquestionable answer.
And over time, something more useful becomes possible.
Your own history can become better context than a new map search
The first time Tovia sees a visit somewhere, it may need to ask:
What place near this coordinate best explains this visit?
But if you have been to the same office twenty times, the problem changes.
Tovia already knows that this part of the map is meaningful to you.
So repeated visits can help form a personal layer of location history:
this cluster of visits is usually “Office”
this one is usually “Home”
this one is the gym you keep returning to
That means a place tracker can become more personal over time.
The world map tells Tovia what places exist.
Your history tells Tovia which places matter to you.
Tovia does not need to stay visibly open
Visit monitoring is designed to work beyond the foreground.
Apple documents that, when visit monitoring is active, the system can relaunch a terminated app when new visit events are ready for delivery.[3]
That matters because a life-recording app would be frustrating if you had to remember to launch it every morning.
The point of automatic recording is precisely that you should not need to think about it constantly.
You live your day.
The record forms quietly.
Why not record everything anyway?
Because more data is not automatically better memory.
A continuous GPS trail might contain thousands of coordinates from a single day.
But what would you actually want to see five years later?
Probably not:
Latitude 34.05231
Longitude -118.24372
10:42:17 AM
More likely:
That tiny restaurant we used to go to after work.
Or:
The park I visited almost every Sunday that summer.
Or:
The office where I spent 600 hours before changing jobs.
The purpose of Tovia is not to preserve every meter you traveled.
It is to preserve the structure of a life lived through places.
Privacy changes the architecture too
There is another reason we prefer this approach.
Location history is deeply personal.
Tovia’s core visit history, places, events, notes, and HealthKit-related records are designed to remain stored locally on the device rather than being uploaded to Visionular’s servers. You can read more in the Tovia Privacy Policy.
That means automatic location recording does not need to become a cloud archive of everywhere you have been.
The phone detects the visit.
Tovia turns it into a personal record.
The record stays with you.
Low-power tracking should feel invisible
The best version of Tovia is not an app you constantly operate.
It is an app you occasionally return to.
You open it after a week and see where the days went.
You open a restaurant and realize you have been there eleven times.
You look back at last summer and find the park that quietly became part of your routine.
You finish a trip and discover that the places, time, and memories have already formed a timeline.
The technology matters because it makes that possible without turning everyday life into a manual logging exercise.
Apple built a location service around the idea of meaningful visits rather than constant updates.
Tovia builds on the same idea:
remember the places that mattered, without recording every step along the way.