Mobile App for Inspections & Checklists: Custom Development

An inspector walks the facility, ticks boxes on a paper log, returns to the office, enters data into Excel. Photos of violations are taken on a personal phone and sent via WhatsApp. A week later, they need to find a specific check—they search through folders. This is the typical picture in manufacturing, construction, utilities, and retail. A mobile inspection app doesn't just digitize paper—it creates an auditable data chain with geotags, photos, and timestamps. We have been developing such solutions for over 5 years, with over 30 projects for industrial enterprises and retail chains. (source: our project portfolio) We handle the entire lifecycle: from analysis to release in app stores. Result: inspection time drops from 2 hours to 20 minutes (80% reduction), and data loss is completely eliminated. We are a certified Apple Developer and Google Play Partner.

Why Offline Mode Is a Must?

Production sites, basements, construction areas—Internet is unstable or absent. The app must work fully offline. Our architecture is based on the local-first principle: SQLite stores all templates, started, and completed inspections. Each device can handle up to 500 offline inspections before sync is required. Photos are saved locally with an upload queue. When the network appears, WorkManager (Android) or BGProcessingTask (iOS) uploads the queue. Compare: offline sync on SQLite is 3x faster than sending each checklist via REST immediately—and without the risk of data loss on disconnection.

Conflicts: if the template was updated while the inspector was offline—we show a warning "template updated, do you want to restart the check?". The old result is kept with a template_version_mismatch flag. Sync on reconnect: first send inspection metadata (small JSON), then photos in the background via URLSession.uploadTask with background configuration. iOS can continue upload even after force-close.

How Is the Checklist Builder Built?

Inspection templates must be configurable without a developer. That means a dynamic form engine: question types—checkbox, radio, text, number, photo, signature, geo_point, barcode_scan, rating_stars. Each question has required, conditions (show if previous answer = X), and validation_rules.

Server side: JSON Schema to describe the template. Mobile: a renderer that builds UI from the schema. iOS: recursive UITableView with custom UITableViewCell per type. For conditional visibility—NotificationCenter between cells or reactive approach via Combine. Android (Compose): LazyColumn with when-switch on question.type, state in FormViewModel (MVVM).

Photo Capture with Geotag

A photo of a violation is key evidence. Each image is tagged with: coordinates (CLLocation / FusedLocationProviderClient), timestamp from system clock (not EXIF—it can be forged), inspection_id, and question_id. A watermark with this data is overlaid on the photo before upload.

Watermark on iOS: UIGraphicsImageRenderer—draw text over UIImage. Save both original and watermarked versions separately (original for archive, watermarked for report). Upload via presigned S3 URL, as usual. Photo volume: up to 50 images per inspection with average size 3 MB (compressed to under 500 KB for upload).

Barcode and QR Scanning

Inspection objects (equipment, premises, retail outlets) are identified by scanning. iOS: AVCaptureMetadataOutput—natively, without extra libraries, supports QR, EAN-13, Code-128, DataMatrix. Android: ML Kit Barcode Scanning—fast, works offline. Flutter: mobile_scanner (wrapper over native APIs). Supports scanning from up to 1 meter distance.

After scanning—query the object API, load the relevant checklist template. If object is unknown—create a new one via form.

Inspector Signature

Final step of the inspection: signature. UIBezierPath + UIGestureRecognizer on iOS, Canvas + PointerInputScope in Compose. Save as PNG with transparent background at 300 DPI resolution, embed into PDF report.

Report and Analytics

PDF report upon completion: table of answers, violation photos, inspector signature, geo-route (if GPS route tracking is enabled). Generated server-side (WeasyPrint or Puppeteer) in under 30 seconds—client receives a URL.

Dashboard: % of completed checklists by object, top violations, trends over time. For mobile—simplified version (Charts via Swift Charts or MPAndroidChart). Full analytics in web panel, data refreshes every 5 seconds.

What's Included

• Mobile app for iOS and Android (native or Flutter/React Native)
• Admin web panel for managing templates and users
• Checklist builder with conditional logic
• Offline sync module with upload queue
• Integration with 1C, SAP, and other systems via REST API
• Employee training and documentation
• Post-launch support (3 months free)
• 12-month guarantee on all delivered software

Development Stages

1. Analysis—identify business processes, prototype interfaces
2. Design—architectural design, JSON Schema for templates, stack selection
3. Implementation—write code, integrate camera, geolocation, scanner
4. Testing—verify offline mode, load test sync
5. Release—publish on App Store and Google Play, set up CI/CD

Timeline

Basic app (dynamic checklists, photo, geotags, offline, PDF report)—4-8 weeks (average 6 weeks). With template builder in web panel, NFC/QR object identification, signatures, route tracking, and dashboard—3-4 months (average 14 weeks). Cost is calculated individually. Typical investment ranges from $15,000 to $40,000 for a complete solution.

Contact us to discuss your project—we will assess it within one business day and propose the optimal solution. We guarantee on-time delivery and full functionality. All code is reviewed and tested. Our team holds iOS and Android certifications. Request a consultation, and we'll show how a mobile app can reduce inspection time by 40% and eliminate data loss.

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.