A geofence is a virtual boundary around a real-world area. Instead of continuously asking “where is the phone?” merely to decide whether it has entered a place, an app can ask the platform to notify it when a configured device moves into or out of a defined region. Geofencing can be useful for reminders, automation and transparent fleet or family coordination, but it is not magic and it is not perfectly instantaneous.
The simplest geofence describes a circle using latitude, longitude and a radius. An application then specifies events it cares about, such as entering, exiting or dwelling in the area. Android's location services can monitor those conditions and deliver a transition to the app subject to platform limits.
A geofence therefore answers a different question from a detailed route logger. It may tell you that a device entered a site without needing to draw every metre travelled on the way there.
An enter transition occurs when the system decides the device has moved into the region. An exit occurs after it moves out. A dwell event can help distinguish somebody who actually remains at a place from somebody merely passing along a road at the edge.
These events are estimates based on available location data. They should not be treated as millisecond-accurate physical tripwires.
A badly designed application could keep the highest-accuracy GPS mode active continuously just to decide whether a user arrived at work. Platform geofencing can use the operating system's location knowledge more efficiently and wake the app when a relevant transition occurs.
That does not mean geofencing consumes zero battery. It means the platform can manage the task more intelligently than an app blindly polling every second.
If the phone's current location has an uncertainty of tens of metres, a tiny geofence can produce delayed or ambiguous transitions. Buildings, Wi-Fi availability, cellular conditions and background limits all influence when Android becomes confident that the boundary was crossed.
Choose a radius that reflects the real use case. A warehouse campus and one particular doorway are not equally suitable targets for ordinary phone geofencing.
Android limits background work and location access to protect privacy and battery life. Applications must use the supported geofencing and permission APIs rather than assuming they can run arbitrary continuous code forever. Delivery can also be affected by device state and manufacturer power management.
For the broader permission model, see Android background location.
In each case, people should understand when location is being used and what the resulting event does.
A geofence does not turn a phone number into a location sensor and does not remove Android permission requirements. The app still needs to be legitimately installed and configured on the device. LocationOf does not provide a covert geofence mechanism for monitoring another adult without authorization.
| Question | Geofence | Route tracking |
|---|---|---|
| Did the device enter an area? | Good fit | Can infer it from points |
| Which roads did it travel? | Not designed for this | Good fit |
| Need every intermediate point? | No | Usually yes |
| Can be more power-efficient for place events? | Often | Depends on interval |
If your objective is preserving an actual journey, see Android location history and GPS tracking.