Implementing Geolocation in Mobile Chat Apps

Implementing Geolocation Sending in Mobile Chat App

The "Share Location" button in a chat looks simple enough until you run into iOS distinguishing between one-time location (requestLocation) and continuous monitoring (startUpdatingLocation), or Android 10+ requiring the separate ACCESS_BACKGROUND_LOCATION permission for background updates. Furthermore, live geolocation (where the recipient sees your real-time movement) is a fundamentally different architecture from a one-time coordinate snapshot. Our team has implemented such solutions for 12 projects (delivery, social networks, tracking), so we're sharing practical insights.

Why One-Time Location Is Simpler Than Live?

One-time location: the user taps a button, sends a point, and that's it. Ideal for "Meet me here." Live tracking: continuous broadcasting of coordinates for 15–60 minutes, as in Google Maps Messenger or WhatsApp. Architecturally, they are different beasts: one-time requires a REST request to a static map API, live requires WebSocket and background services. Comparison by key parameters:

Live location requires twice the resources on the backend and mobile client, but provides a fundamentally better UX for tracking a courier or travel companion. According to our data, live tracking can boost user engagement by 3x compared to one-time sharing.

One-Time Location: Code on iOS and Android

For a one-shot "where am I" you just request coordinates once, generate a message with a static map, and send it as an attachment in the chat. The recipient sees a map preview with a marker.

iOS (Swift)

import CoreLocation

class LocationManager: NSObject, CLLocationManagerDelegate {
    private let manager = CLLocationManager()
    var onLocation: ((CLLocation) -> Void)?

    func requestOnce() {
        manager.delegate = self
        manager.desiredAccuracy = kCLLocationAccuracyHundredMeters
        manager.requestWhenInUseAuthorization()
        manager.requestLocation() // one-time request
    }

    func locationManager(_ manager: CLLocationManager,
                         didUpdateLocations locations: [CLLocation]) {
        guard let location = locations.last else { return }
        onLocation?(location)
    }
}

requestLocation() gives exactly one update and stops. Use kCLLocationAccuracyHundredMeters – meter-level accuracy is unnecessary for chat and saves battery.

Android (Kotlin)

On Android, one-time location is obtained via FusedLocationProviderClient with getCurrentLocation():

val fusedLocationClient = LocationServices.getFusedLocationProviderClient(this)
fusedLocationClient.getCurrentLocation(Priority.PRIORITY_HIGH_ACCURACY, null)
    .addOnSuccessListener { location ->
        sendLocationToChat(location)
    }

Live Geolocation: Architecture

Broadcasting current location requires three layers:

1. The sending mobile client periodically writes coordinates to the server.
2. The backend stores the latest coordinates and pushes updates to subscribers (WebSocket / SSE).
3. The receiving mobile client receives updates and moves the marker on the map.

Why Live Geolocation Requires WebSocket?

REST requests at 3–5 second intervals would generate colossal load on the server and mobile traffic. WebSocket or Server-Sent Events allow the server to push updates to all subscribed clients with minimal latency. For the sending client, also WebSocket: every 3–5 seconds a JSON with coordinates, bearing, and accuracy is sent. This reduces traffic by 40% compared to REST polling.

Android: Why ForegroundService Instead of WorkManager?

WorkManager with PeriodicWorkRequest has a minimum interval of 15 minutes – useless for live geolocation. A ForegroundService with a status bar notification is required – the user sees that the app is actively using GPS.

class LocationTrackingService : Service() {
    private lateinit var fusedLocationClient: FusedLocationProviderClient
    private val locationCallback = object : LocationCallback() {
        override fun onLocationResult(result: LocationResult) {
            result.lastLocation?.let { location ->
                sendLocationToServer(location.latitude, location.longitude)
            }
        }
    }

    override fun onStartCommand(intent: Intent?, flags: Int, startId: Int): Int {
        startForeground(NOTIFICATION_ID, buildNotification())
        fusedLocationClient = LocationServices.getFusedLocationProviderClient(this)
        val request = LocationRequest.Builder(Priority.PRIORITY_HIGH_ACCURACY, 5000L)
            .setMinUpdateIntervalMillis(3000L)
            .build()
        fusedLocationClient.requestLocationUpdates(request, locationCallback, mainLooper)
        return START_STICKY
    }
}

iOS: background location updates

On iOS, live broadcasting in the background works via startUpdatingLocation with allowsBackgroundLocationUpdates = true and the UIBackgroundModes: location key in Info.plist. Without this key – a crash still in development, not at App Store review. Additionally, NSLocationWhenInUseUsageDescription and NSLocationAlwaysAndWhenInUseUsageDescription must be added. According to Apple CoreLocation documentation, background updates require a mandatory description in Info.plist.

How to Ensure Geolocation Data Privacy?

App Store Review Guidelines Sections 4.2 and 5.1 require explicit consent and a clear explanation of why coordinates are collected. Use ATT (App Tracking Transparency) only if data is shared with third parties. For your own needs, the system permission dialog is sufficient. On Android, permissions must be declared in the manifest: ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, ACCESS_BACKGROUND_LOCATION – the last one with an in-app justification. Our solution includes checking all these requirements at the code review stage. 90% of users prefer apps that clearly explain location use.

Display on the Recipient's Map

The recipient sees the sender's marker overlaid on their own location. Movement animation is mandatory – otherwise the marker "jumps." A message in the chat with live geolocation contains a session_id. The recipient subscribes to the WebSocket channel of that session. Every N seconds the server publishes {lat, lng, bearing, accuracy}. Bearing is needed to rotate the icon in the direction of movement.

Static Map Preview

For one-time location in the chat bubble, we render a static image via MapKit Snapshot or Google Static Maps API:

// iOS MapKit Snapshot
let options = MKMapSnapshotter.Options()
options.region = MKCoordinateRegion(
    center: coordinate,
    latitudinalMeters: 500,
    longitudinalMeters: 500
)
options.size = CGSize(width: 240, height: 160)

MKMapSnapshotter(options: options).start { snapshot, _ in
    guard let snapshot = snapshot else { return }
    let image = snapshot.image
    // display in chat cell
}

The snapshot is rendered asynchronously – it does not block the UI during fast scrolling.

What's Included in the Implementation

Our team provides a full cycle of work for integrating geolocation into chat:

• Architectural design (type selection, protocols, backend API)
• Permission and configuration setup (Info.plist, AndroidManifest)
• Map integration (Google Maps SDK, MapKit, static images)
• Mobile client development (iOS and/or Android)
• Backend setup (WebSocket server, session storage)
• Testing on real devices (current iOS and Android versions)
• Preparation for publication on App Store and Google Play

Timelines and Cost

• One-time location with static preview: 2–3 days, starting at $1,500.
• Live tracking with ForegroundService / background mode: 4–6 days, starting at $3,500.
• Cost savings: combining both features in a cross-platform solution reduces total cost by 20%.
• Get a consultation on geolocation architecture for your project – contact us. We guarantee compliance with App Store Review Guidelines and are ready to share 10+ years of experience in mobile development.

How to Integrate Maps and Geolocation in Mobile Apps: Google Maps, MapKit, Geofencing, Tracking

We integrate geolocation and mapping services into mobile apps—it's more than just "adding a map." It involves permission setup, managing accuracy and power consumption, and accounting for iOS and Android specifics. Whether it's a delivery tracker, running app, or store locator, each case requires a tailored approach. Contact us for a free project assessment within 2 hours.

Permissions: One of the Most Common Sources of Bad Reviews

On iOS, location permission is the most sensitive after microphone and camera. Since iOS 14, the system shows an indicator in the status bar when location is used in the background—users notice this. NSLocationWhenInUseUsageDescription and NSLocationAlwaysAndWhenInUseUsageDescription must contain honest explanations, otherwise the app may be rejected during review. Requesting always permission immediately on launch is a sure way to get denied by 80–90% of users. The correct flow: first request whenInUse, then always only when the user reaches a feature that requires it, with a clear explanation of why.

On Android (API 29+), ACCESS_BACKGROUND_LOCATION is a separate permission that cannot be requested together with foreground. First request foreground permission, then background separately. Google Play requires justification for background location in a questionnaire during publication. If the justification is weak, the app may be rejected or forced to remove background location. Over 5 years of work, we have successfully completed over 20 reviews; none of our apps were rejected for this reason.

Accuracy and Power Consumption: How to Avoid Battery Drain

Continuous GPS at maximum accuracy consumes 100–150 mW—battery drains in 4–6 hours. For most tasks, this is excessive.

On Android, FusedLocationProviderClient (Google Play Services) combines GPS, Wi-Fi, and cellular network, selecting the optimal source. LocationRequest.Builder with priorities:

• PRIORITY_HIGH_ACCURACY — GPS on, for navigation
• PRIORITY_BALANCED_POWER_ACCURACY — accuracy ~100 meters, Wi-Fi + cellular
• PRIORITY_LOW_POWER — accuracy ~10 km, only cellular
• PRIORITY_PASSIVE — coordinates from other apps, no active request

For a running tracker in active mode—HIGH_ACCURACY with 2–5 second interval. For geofencing background notifications—PASSIVE or LOW_POWER; the system wakes up on event. GPS accuracy is well-documented.

On iOS, CLLocationManager with desiredAccuracy (kCLLocationAccuracyBest, kCLLocationAccuracyHundredMeters, etc.) and distanceFilter—minimum movement in meters before next update. For route tracking with battery saving: desiredAccuracy = kCLLocationAccuracyNearestTenMeters, distanceFilter = 10—updates only on actual movement.

Significant Location Changes—iOS mode that works at OS level without active GPS: updates on cell tower change, minimal battery drain. Accuracy ~500 meters—suitable for logging user location history, not for navigation.

How to Choose a Mapping SDK? Comparative Analysis

Google Maps SDK is the default choice for most projects: familiar UI, good documentation, Directions API, Places Autocomplete. Limitation—dependency on Google Play Services (issue for Huawei) and pricing at high request volumes (paid after certain usage).

Mapbox is preferable when you need custom map styles (corporate branding, dark theme), offline maps for offline work, or compatibility with devices without GMS. MapboxNavigation SDK provides full navigation with voice instructions, route recalculation, and lane guidance. Mapbox renders polygons 2x faster when loading 500+ markers compared to Google Maps—confirmed by our load tests.

For Flutter—google_maps_flutter (official), flutter_map (OpenStreetMap + MapLibre, fully open-source), mapbox_maps_flutter (after official SDK release).

Example: App with Offline Maps and Geofences for 100+ Points

A retail chain client needed a map with offline mode and push notifications on store entry. We chose Mapbox—it supports downloading entire regions and offline geocoding. Result: zero network failures, 30% battery reduction due to PASSIVE mode.

Why Does Geofencing Have Delays?

Geofencing triggers an event on entry/exit of a geographic zone (circle of given radius). In practice, delay can be 1–3 minutes—the cost of energy efficiency.

On Android—GeofencingClient from Google Location Services. Add Geofence objects with setTransitionTypes(GEOFENCE_TRANSITION_ENTER | GEOFENCE_TRANSITION_EXIT) and PendingIntent for BroadcastReceiver. Limitations: max 100 active geofences per app, minimum radius ~150 meters (due to accuracy), delay of several minutes for battery saving.

On iOS—CLCircularRegion + CLLocationManager.startMonitoring(for:). Limit: 20 regions per app. The OS decides when to check—developer cannot control delay. For more precise geofencing with small radius—iBeacon (CLBeaconRegion) or CLVisit for places where user spent time.

If you need more than 20 (iOS) or 100 (Android) zones—server-side logic is required: periodically send coordinates to server, server checks zone entry and sends push. Less time-accurate but scales to thousands of zones. Geozone working principles are well-documented.

Route Tracking and Background Geolocation

Tracking a run or a courier route in the background are technically different tasks.

On iOS, background geolocation works via UIBackgroundModes: location in Info.plist. Without this key, when the app goes to background, CLLocationManager gets a few minutes and then sleeps. With the key, it works continuously, but the system may pause it at critically low battery.

For a running tracker on iOS: startUpdatingLocation at start of workout, write coordinates to Core Data every 5 seconds; on pause—stopUpdatingLocation, but keep startMonitoringSignificantLocationChanges to avoid losing the app's position completely.

On Android for courier tracking, you need a Foreground Service with FOREGROUND_SERVICE_TYPE_LOCATION (mandatory from API 29). Foreground service shows a persistent notification—this is a platform requirement, not a bug. Without it, Android Doze will kill location updates. WorkManager for background tasks is not suitable—it does not guarantee continuity.

Algorithmic part of route tracking: raw GPS coordinates are noisy. For smoothing—Ramer-Douglas-Peucker algorithm for track simplification or Kalman Filter for real-time noise filtering. Without filtering, the track looks like random zigzags, and the estimated distance is 20–30% more than actual.

How We Implement Maps and Geolocation: Step-by-Step Process

1. Scenario Analysis—determine foreground/background needs, accuracy, number of geofences, offline requirement.
2. SDK and Architecture Selection—compare Google Maps, Mapbox, HERE, MapKit based on project criteria (use our comparison as a baseline).
3. Integration and Permission Setup—configure Info.plist / AndroidManifest.xml, test review checks (App Store Review Guidelines Sections 4.2/5.1, Google Play policy).
4. Tracking/Geofencing Implementation—add CLLocationManager / GeofencingClient, configure filters and power saving.
5. Unit and Integration Testing—on real devices (emulator does not simulate delays or Doze/App Nap behavior). Test at least 50 scenarios.
6. Load Testing—simulate 500+ markers, moving objects, check FPS and battery consumption.
7. Deployment and Monitoring—release via TestFlight / Firebase App Distribution, collect crashlytics logs, track permission denial rates.

Timeline and Deliverables

What you get in any case:

• Source code with comments (Swift, Kotlin, Dart, TypeScript)
• Integration with your backend (REST/GraphQL/WebSocket)
• 1 month support after delivery (bug fixes, help with store reviews)
• Guide for publishing to App Store and Google Play (including background location justification)
• Code signing certificates, provisioning profiles, Google Maps/Mapbox keys

Our expertise: 10+ years in mobile development, 50+ geolocation projects, certified Apple and Google developers (Google Associate Android Developer). Every app undergoes triple code review and load testing.

Order turnkey map and geolocation integration—contact us for a consultation and preliminary project estimate within 2 hours.