When does an arrival alert need more than a map pin?
A geofence is a boundary around an area. When your app supplies location updates, Radar can report an entry or exit. That is different from drawing a pin or looking up an address. Let a person confirm arrival manually when location is off or uncertain.
The device’s reported accuracy and the size of the boundary affect confidence. Decide how your app should respond to a low-confidence event.
What counts as a tracked user?
Radar’s terms define a monthly tracked user as a distinct user who sends at least one location event in a calendar month. Radar’s current pricing describes annual commitments and distinguishes tracked-user products from Core Maps pricing by API calls.
Estimate both kinds of use if the app needs arrival events and map search. Check the actual agreement for your use case.
What location information would you keep?
Keep venue boundaries your team created and decide how long the app needs any location events. Radar’s terms limit storing address or place results from certain APIs to 30 days and restrict building a database from them. Check separately what your agreement allows for exports or event data.
A venue pin does not require a person’s location history. If you need an arrival feature, explain why the app asks for location and what happens if someone declines.
How would you plan an arrival prompt without tracking a person?
Draw a fictional venue and a pretend path across its boundary. Use no phone location, account, key or requests.
- Draw the intended areaMark a public entrance, a nearby road and where the fictional visitor stops.
- Decide which event should countWrite what happens when a location is inside, near the edge or too uncertain.
- Try it without locationShow the manual check-in and make sure the visitor can continue.