How a mobile app for the agricultural sector solves the problem of no network connectivity

An agronomist stands in the middle of a field in Krasnodar Krai — the smartphone catches one bar of signal, GPS jumps 10–15 meters. They need to record an anomaly on a specific plot, take a photo of the disease spot, attach coordinates, and send it to the monitoring system. In half an hour, they'll be in an area with no connection at all. A classic mobile app won't work here. We develop AgriTech solutions that withstand such conditions. Our team has 10+ years of experience in mobile development for the agricultural sector and has completed over 50 projects for farms ranging from 100 ha to 25,000 ha. Savings on logistics thanks to accurate data can reach 20–30%, and the investment in the app pays back within one season.

Our AgriTech mobile app development services include offline maps for agronomy, GPS accuracy for agriculture, ML disease recognition for plants, John Deere API integration, field tasks geotagging, crop monitoring, offline-first architecture, smart farming, and precision agriculture. We provide comprehensive solutions for agribusiness.

How AgriTech Mobile Apps Ensure Offline Map Functionality for Agronomy

AgriTech apps operate in environments where the internet is often unavailable for several hours at a time. Fields don't change every day — you can (and should) preload raster or vector tiles onto the device.

Satellite imagery. For an agronomist, Sentinel-2 or DigitalGlobe is more important than road maps. A tile server is set up with data from Earth Engine or Copernicus Open Access Hub, tiles are cached via MBTiles format and displayed using MapLibre GL Native. Before heading out, the user downloads tiles for the desired region from the last 2 weeks — NDVI changes, disease spots, waterlogging become visible. MapLibre GL provides smooth zoom and works offline — load speed is 3 times faster than online requests over poor networks (MapLibre GL Native).

GPS accuracy. The smartphone's built-in GPS gives 3–5 meters in an open field, up to 15 meters under cloud cover. That's insufficient for accurate plot mapping. Solutions:

• Bluetooth receiver with GNSS (Trimble R1, Bad Elf GPS+) provides sub-meter accuracy via the standard NMEA 0183 protocol
• SBAS (WAAS/EGNOS) correction — free, improves to 1–3 meters
• RTK via mobile internet (NTRIP client) — centimeter-level, requires constant network

Integration of external GPS on Android: UsbSerialForAndroid for USB-OTG or BluetoothSocket for BLE receivers. On iOS — External Accessory Framework for MFi-certified devices.

Field work and tasks

The agronomist in the field performs tasks: plot inspection, sampling, irrigation, fertilization. This is a workflow of geotagged tasks created by an agronomist-consultant in a web interface, and the field worker executes them in the mobile app.

Task status model: created → assigned → in_progress → completed. When transitioning to in_progress, we record the GPS start point; at completed, we record the point and photo. If the user closes a task without a network, the operation enters a queue (Room database, table pending_operations), which syncs when connection is available via WorkManager with NetworkConstraint.

Identifying crops and diseases via ML

Taking a photo of a plant and automatically identifying the disease is a popular AgriTech feature. We implement it via Core ML (iOS) or TensorFlow Lite (Android) with a model fine-tuned on the client's crops. The model is packaged into .mlmodel/.tflite and lives on the device — works offline, critical for the field.

Base open-source models: PlantNet, iNaturalist API, or models from the PlantVillage dataset (38 disease classes across 14 crops). For production, we fine-tune on the client's regional data via Transfer Learning on top of MobileNetV3.

Limitation: the model recognizes foliar diseases but not micronutrient stress — for that, multispectral drone imagery is required, not a smartphone photo.

Integration with smart sensors and machinery

The AgriTech ecosystem includes soil sensors (Davis Instruments, Decagon), weather stations, smart irrigation systems (Netafim, Lindsay), and precision agricultural machinery (John Deere Operations Center API, AGCO Connect). The agronomist's mobile app is the integration point where data from all sources converges into a single field context.

For Bluetooth sensors on iOS: CoreBluetooth with CBCentralManager, manufacturer GATT profile. For sensors with WiFi/LoRaWAN — data is aggregated by the server, the mobile client queries via REST or WebSocket.

John Deere Operations Center provides an OAuth 2.0 REST API with data on machines, fields, and operations. Integration requires a developer partner account.

Field maps and polygons

Fields are drawn as polygons: the agronomist walks the boundary or traces it on the map with a finger. Polygon input via tapping points on the map — MKPolygon / GmsPolygon with live-preview edge. We save in GeoJSON, compute area via ST_Area(ST_Transform(geom, 32637)) on the server (UTM projection for metric accuracy).

What's included in our work

With each project we deliver:

• Architectural documentation (ERD, component diagrams)
• Source code in a private repository (Git)
• Integration with App Store Connect and Google Play Console
• Access to a test environment (TestFlight / Firebase App Distribution)
• 2-day training for the client's team
• 3-month warranty on critical bug fixes after delivery

Why choose us?

10+ years of experience, 50+ implemented projects in the agricultural sector, Apple and Google certifications. We know the App Store Review Guidelines (sections 4.2 and 5.1), set up code signing and provisioning profiles, work with push notifications (APNs/FCM). We guarantee stable operation of the app in field conditions. Get a consultation — we'll tell you how our solution can save up to 30% of agronomic time.

Stages and timelines

1. Audit: which sensors/machinery are already in use, what GNSS accuracy is needed
2. Development of an offline data model — fields, tasks, seasons
3. Map and polygon handling
4. ML module — dataset preparation or use of ready-made models
5. Integrations with external systems
6. Pilot on one farm before production

MVP (field maps, tasks, photo capture): 8–12 weeks. Full AgriTech platform with ML, machinery and sensor integration: 5–8 months. Cost is calculated individually.

Contact us for a consultation on your project — we'll select the optimal solution for your budget and timeline.

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.