Address Input Optimization: Autocomplete and Caching in Mobile Apps

Address Input Optimization: Autocomplete and Caching

Imagine a user typing “Tversk” and the system suggests 5 options in 300 ms. Without proper implementation, each keystroke triggers a separate API request—70% of users abandon the form if delays exceed 2 seconds. Average address entry time with autocomplete is 8 seconds, without it 35 seconds (per Nielsen Norman Group). The technical challenge is not just adding a library, but choosing the provider, configuring debounce, caching, and session tokens. Let's break down how to do it right.

How to Choose a Geocoding Provider?

For most Russian projects, we recommend a DaData + Google combo: DaData as primary, Google as fallback for foreign addresses. This reduces request costs by 40% compared to using only Google. DaData is 2 times more accurate than Nominatim for Russian addresses—critical for logistics. Google Places with session token is 3–5 times cheaper than without.

Why Is the Session Token Important in Google Places?

On iOS, use the GooglePlaces pod and GMSPlacesClient.findAutocompletePredictions(fromQuery:filter:sessionToken:callback:). The key point is GMSAutocompleteSessionToken: one token per search session (from first character to result selection). This reduces costs 3–5 times compared to requests without a token. As the Google Places documentation states: "Using session tokens allows multiple requests to be grouped into a single billing."

let token = GMSAutocompleteSessionToken()
let filter = GMSAutocompleteFilter()
filter.type = .address
filter.countries = ["RU", "BY", "KZ"]

placesClient.findAutocompletePredictions(
    fromQuery: query,
    filter: filter,
    sessionToken: token
) { results, error in
    guard let results else { return }
    self.suggestions = results.map { $0.attributedFullText.string }
}

After selecting an address, call fetchPlace(fromPlaceID:placeFields:sessionToken:) to get coordinates—and reset the token. Without fetchPlace, coordinates are not available from autocomplete.

On Android, use Places.initialize(context, apiKey) + PlacesClient. In Jetpack Compose:

val placesClient = Places.createClient(context)
val request = FindAutocompletePredictionsRequest.builder()
    .setQuery(query)
    .setSessionToken(AutocompleteSessionToken.newInstance())
    .setTypesFilter(listOf(PlaceTypes.ADDRESS))
    .setCountries("RU", "BY")
    .build()

placesClient.findAutocompletePredictions(request)
    .addOnSuccessListener { response ->
        _suggestions.value = response.autocompletePredictions
    }

What Does Debounce Give?

Without debounce, each keystroke triggers an API request. At an average typing speed of 4 characters per second, that's 4 requests instead of one. Our experience shows that proper debounce of 350 ms reduces the number of requests by 70%.

Step-by-step debounce implementation:

1. Create a Publisher/Flow from the text field.
2. Apply debounce(for: 350 ms) operator.
3. Add a length filter (>= 3 characters).
4. Use flatMapLatest to cancel the previous request.

On iOS with Combine:

searchTextField.textPublisher
    .debounce(for: .milliseconds(350), scheduler: DispatchQueue.main)
    .removeDuplicates()
    .sink { [weak self] query in
        guard query.count >= 3 else { return }
        self?.fetchSuggestions(for: query)
    }

On Android with StateFlow:

searchQuery
    .debounce(350)
    .filter { it.length >= 3 }
    .distinctUntilChanged()
    .flatMapLatest { fetchSuggestions(it) }
    .stateIn(viewModelScope, SharingStarted.Lazily, emptyList())

flatMapLatest cancels the previous request on new input—without it, old results may overwrite new ones.

Offline and Cache: How to Improve UX?

Store the last 10–20 selected addresses locally (UserDefaults / SharedPreferences) and show them when the input field is empty. This solves the most common case: users ordering delivery to the same address.

For search history, use Room / Core Data with columns address_string, lat, lon, last_used_at. On input, first search the local database (LIKE query), then concurrently request the API—show the local result immediately, replace with the API result when it arrives. Cache response time is 2–5 ms vs 200–500 ms from API.

class AddressSearchViewModel: ObservableObject {
    @Published var query = ""
    @Published var suggestions: [String] = []
    private var cancellables = Set<AnyCancellable>()
    private let placesClient = GMSPlacesClient()
    private let token = GMSAutocompleteSessionToken()

    init() {
        $query
            .debounce(for: .milliseconds(350), scheduler: DispatchQueue.main)
            .removeDuplicates()
            .filter { $0.count >= 3 }
            .flatMapLatest { [weak self] query -> AnyPublisher<[String], Never> in
                guard let self = self else { return Just([]).eraseToAnyPublisher() }
                return Future { promise in
                    let filter = GMSAutocompleteFilter()
                    filter.type = .address
                    filter.countries = ["RU"]
                    self.placesClient.findAutocompletePredictions(
                        fromQuery: query,
                        filter: filter,
                        sessionToken: self.token
                    ) { results, error in
                        guard let results = results, error == nil else {
                            promise(.success([]))
                            return
                        }
                        promise(.success(results.map { $0.attributedFullText.string }))
                    }
                }.eraseToAnyPublisher()
            }
            .receive(on: DispatchQueue.main)
            .assign(to: &$suggestions)
    }

    func selectAddress(_ placeID: String) {
        let token = GMSAutocompleteSessionToken()
        let fields: GMSPlaceField = [.coordinate, .formattedAddress]
        placesClient.fetchPlace(fromPlaceID: placeID, placeFields: fields, sessionToken: token) { place, error in
            guard let coordinate = place?.coordinate else { return }
            // save coordinates
        }
    }
}

How to Test Autocomplete on Edge Cases?

Testing autocomplete catches errors that are hard to spot in production. We use a mock layer: replace API responses with test data (empty response, delays, errors). Check edge strings: empty string, single character, special characters (!@#$), very long addresses (200+ characters), addresses with non-standard letters (umlauts, Cyrillic). Also simulate network failures and timeouts—the app should gracefully show a fallback message and not crash. We have a checklist of 25+ scenarios for each project.

What's Included in the Work?

• Provider selection and integration (DaData, Google, Yandex).
• UI component development with dropdown list (SwiftUI / Jetpack Compose).
• Implementation of debounce, request cancellation, session tokens.
• Local caching of address history.
• Error handling: no network, API rate limits, invalid input.
• Testing on edge strings (empty, special characters, very long addresses).
• Integration documentation.

We have implemented address search in 30+ projects—from delivery services to geographic information systems. We guarantee stable operation under high load. Get your project evaluated—contact us for a consultation.

Timeline: two to four days—provider, UI, debounce, history cache, testing. Cost is calculated individually for your tasks. Get a consultation to find out how long your app's integration will take.

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.