• Android offline map and geofence tracking module for field engineers (Mapbox + Room + WorkManager)

    18 hours ago
    • Desired budget up to 650.23 USD
    • Waiting for a performer...
  • Initial situation - there is a corporate Android application for field engineers (Kotlin, Android Studio, minSdk 26, targetSdk 34, MVVM, Hilt, Retrofit, Room). Currently the map only works online via Mapbox, and there is often no connection at sites. Because of this, employees do not see routes, and the system does not record visits to geofences.

    Subject area - service visits and control of visits to objects by geofences (points and polygons), collection of movement tracks and entry-exit events.

    The task is to add an offline maps module to the application and reliable collection of tracks/geo-events with subsequent synchronization, so that the application works in unstable network mode and in the background.

    Technical environment and limitations - Kotlin, Coroutines/Flow, Mapbox Maps SDK v10+ (or current), Room, WorkManager, FusedLocationProvider. Server APIs cannot be changed. You can add local tables and call only existing endpoints. The application should gracefully survive process restarts and killings. Geodata and tracks are stored locally until successful sending. The battery is important - you can't keep the GPS frequency high all the time. Devices - mass corporate Samsung/Xiaomi, Android 9-14. Access to the repository will be via Git, assembly via Gradle.

    What needs to be done in several stages
    1) Analyze the current implementation of the map and geofences, propose a local storage and synchronization scheme (a short design document of 1-2 pages in the project README).
    2) Implement loading of offline Mapbox regions for the selected zone (tiles + styles), with cache management - scale selection, volume estimation, progress, deletion and integrity check.
    3) Implement local storage of geofences (points and polygons) and the latest version of the geofence set. Geofences come from the server as a list, update according to the version/hash, without a complete download and remain unchanged.
    4) Implement tracking of movements in the background - recording a track as a set of points with timestamp, accuracy, speed, provider, as well as events of entry/exit from geofences. The recording frequency must adapt - more often when moving, less often when standing.
    5) Implement reliable synchronization with the server via WorkManager - sending queue in batches, replay with backoff, deduplication, successful delivery mark, protection from parallel workers.
    6) Add a minimal UI screen for module settings - an offline mode switch, a list of loaded regions, a download/delete button, an indicator of synchronization status and the amount of unsent data.

    The result is a PR to the repository with a working module, Room migrations, and testing instructions (steps for reproducing scripts) in Markdown.

    Measurable acceptance criteria
    - When the offline region is enabled, the map opens without the Internet and draws the base style and previously loaded tiles without crashing
    - Geofences are displayed on the map and are available for calculating entry-exit without a network (local data is used)
    - Track and geo-events are recorded for at least 30 minutes when the network is turned off, then when the network appears, they are sent to the server automatically without user intervention
    - After killing the process and restarting, the application continues tracking and synchronization without losing already recorded data (except for the last point at the time of killing)
    - Duplicate events do not appear on the server when resent (checked by idempotency keys/local identifiers)
    - In idle mode (the screen is off, the device is lying down), recording no more than 1 point per 5 minutes, when driving faster than 10 km/h - no less than 1 point per 15 seconds
    - All changes are covered by at least 6-8 instrumental/unit tests on Room/repositories/workers (without the requirement of 100% coverage)

    Additionally - use only official APIs, without root solutions and without third-party background geolocation services. Save the project code style, agree on new dependencies.
  • How would you rate this task?

    Sign in to leave your rating.

    Total ratings: 0

Your offer

You have not submitted an offer for this order yet.
Click “Submit an offer” to send your offer.

Need a similar task?

If this project is close to your need, you can view ready services in the category or post your own task with the required budget, deadline and requirements.

The project «Android offline map and geofence tracking module for field engineers (Mapbox + Room + WorkManager)» can be used as a reference for your own brief: what should be done, what result is needed and what budget to set.