Maps and Geolocation App Development

Location features buyers ask for, and what makes each hard

Most apps that need maps need two or three of these features, not all of them. Tepia scopes each one separately, because the platform tools and the failure modes are different:

Because of the region limits, Tepia often registers only the nearest geofences on the device and swaps them as the user moves, rather than loading every location at once.

Background location, permissions and battery

Background location is where app review, user trust and battery life all collide, so Tepia designs it before writing code. On iOS, users choose between allowing location while using the app or always, and can share only an approximate location. On Android, background access must be requested separately after foreground access, recent versions send users to system settings to grant it, and Google Play requires a declaration explaining why your app needs it. Apps that ask too early or without a clear reason get denied by users and questioned by reviewers.

Tepia asks for location at the moment a feature needs it, with a short screen that explains the benefit, and builds a useful fallback when the answer is no or only approximate. For tracking, we combine distance filters, motion detection that pauses GPS when the phone is still, and batched uploads, so a technician or driver can run tracking through a full shift. Those patterns underpin our GPS time tracking apps and driver apps.

Choosing a map provider

Tepia picks the map stack by what your users search for, where they are, and how the map needs to look:

• Google Maps Platform has the deepest place data and global coverage, which matters when users search for businesses and addresses.
• Apple MapKit feels native on iPhone, has a strong privacy story, and offers MapKit JS for web dashboards.
• Mapbox gives detailed control over map styling, supports downloadable regions for offline use, and works well for custom data layers such as territories.

Usage terms matter as much as features. Some providers restrict showing their place results on another company’s map or caching their data, so Tepia checks terms before mixing services. Apps used in the field often need maps that work without signal, which ties into our offline first app development approach. For dispatch or delivery products, routing usually moves server side, covered in route optimization software development.

The backend behind a live map

A moving dot on a customer’s screen depends on a server that can take in thousands of location updates a minute and send only the useful ones back out. Tepia builds this with Node.js or .NET services, stores the latest position and a trimmed history in PostgreSQL with PostGIS, and pushes updates to watching clients over WebSockets or Firebase rather than having every phone poll.

We throttle and filter on the server too: a point that has not moved meaningfully is not rebroadcast, and points with poor accuracy are dropped before they make a driver appear to jump across a highway. Spatial indexes let dispatch screens ask which units are inside a polygon or within ten minutes of a job without slowing down as the fleet grows. Our real time applications work covers the same patterns beyond maps.

How Tepia approaches maps and geolocation

Location work follows the six Tepia phases, with field testing built in rather than left to launch week.

1. Discovery: interviews with the people who will be tracked and the people watching the map, a review of your address and territory data, and User Stories such as a customer receiving an arrival alert. The Investigation Summary recommends a map provider and the permission level each feature needs.
2. Design: wireframes for map screens, marker styles, permission priming, approximate location fallbacks and tracking status, with a map style matched to your brand.
3. Development and Testing: the location service, PostGIS schema and real time updates are built together. Alpha testing uses simulated routes in Xcode and the Android emulator; Beta includes drive tests on real phones across urban, suburban and rural areas, with test plans for accuracy, battery drain and geofence timing.
4. Training: dispatchers and managers learn the live map, history views and how to adjust zones and geofences.
5. Launch: addresses are geocoded and cleaned during data migration, background location declarations are submitted with the store listing, and tracking rolls out team by team.
6. Support: location quality is monitored by device and OS version, and new zones or features are added as requests arrive.

See the full Tepia process.

Accuracy, privacy and honest expectations

GPS is accurate outdoors, less so between tall buildings, and weak indoors. Tepia sets expectations accordingly: we smooth tracks and snap them to roads where it helps, use Wi-Fi or Bluetooth beacons when indoor position truly matters, and design geofences large enough to trigger reliably instead of at the exact curb.

Location is also sensitive data. California law treats precise geolocation as sensitive personal information, and both app stores require you to disclose how location is used. Tepia collects location only while a job, shift or trip is active, sets retention periods, lets users see what was recorded, and keeps access limited by role in the admin portal. If your app needs a map that people trust, talk to Tepia or browse our work.

Frequently asked questions