Mobile App Development for Time Tracking with GPS and NFC

We develop mobile applications for time tracking that solve the problem of inaccurate check-ins and disputes with HR. Geolocated check-ins with anti-fraud mechanisms, offline mode, and 1C integration — it's not just convenient, it saves up to 15 hours per month on timesheet verification. Our solutions use an enterprise stack: Swift 5.9+ / Kotlin + Jetpack Compose, Firebase, PostGIS. Over 5 years on the market, 120+ completed projects — we guarantee quality and on-time delivery. The app pays for itself in less than 2 months by reducing timesheet errors.

How does geofencing ensure accurate check-ins?

Geofencing is the foundation of anti-fraud. On check-in, the app verifies that the user is within N meters of the workplace. iOS: CLLocationManager with requestLocation() (single measurement, saves battery) — accuracy kCLLocationAccuracyNearestTenMeters. Android: FusedLocationProviderClient.getCurrentLocation(PRIORITY_HIGH_ACCURACY) from Google Location Services. Indoor accuracy is improved via Wi-Fi fingerprinting: on check-in, a list of BSSIDs and RSSI is collected through NEHotspotHelper (iOS, requires entitlement) or WifiManager.getScanResults() (Android). If GPS is inaccurate, we compare against the office reference fingerprint. This approach improves location identification accuracy by 40% compared to using only GPS.

Comparison of geolocation methods

Why use NFC for check-ins?

For strict control — NFC tags at the entrance. The employee taps the phone to the tag, the app reads NFCNDEFReaderSession (iOS) or NfcAdapter (Android) and automatically records a check-in with a timestamp. Physical forgery is impossible. NFC eliminates the possibility of remote "padded" hours — until the employee approaches the tag, the check-in is not counted. This gives 100% accuracy when recording arrival/departure time.

Offline mode and sync: how does it work?

Construction, warehouse, field teams — internet is unstable. All check-ins must be saved locally and synced when a network appears. Local storage: SQLite via Room (Android) or GRDB.swift (iOS). Table time_records: id (UUID, generated locally), type (check_in/check_out/break_start/break_end), latitude, longitude, wifi_bssids, timestamp, synced (boolean), sync_error. Background sync: iOS — BGTaskScheduler with BGAppRefreshTask. Android — WorkManager with NetworkType.CONNECTED. During sync — batch upload of all unsynchronized records, server-side idempotency by client_id. Offline mode increases time tracking reliability by 30% compared to solutions requiring constant internet.

Timesheet and reports: what can you get?

The timesheet is a summary table for a period. For each employee: date, arrival time, departure time, breaks, total hours, status (on time/late/overtime). Generated on the backend, client receives paginated JSON. Export: PDF via WeasyPrint/Puppeteer on server or Excel via xlsxwriter (Python) / Apache POI (Java). Client downloads the file via a URL with a short-lived signed token. On iOS — UIDocumentInteractionController for opening/sharing. On Android — FileProvider + Intent.ACTION_VIEW. Integration with 1C: 1C can receive data via REST API (HTTP service) or via file exchange (CSV/XML on schedule). For direct integration, a 1C developer is needed on the client side — we prepare the API with the necessary data structure.

What if an employee forgets to check in?

Manual correction with a mandatory comment and notification to the manager (push via FCM/APNs) is necessary. The manager sees the change request and approves or rejects it. All corrections are logged.

Roles and structure: how to set access levels?

Three levels: employee (sees their timesheet, makes check-ins), manager (sees department timesheet, approves corrections), HR/accounting (full access, export, schedule configuration). Authorization — JWT with role in payload, checked at API middleware level. Work schedule (shifts, flexible, standard 9-18) is set in the admin panel — the mobile app uses it to calculate lateness and overtime.

What is included in the work?

• Documentation: architecture diagram, API description, user instructions.
• Source code with comments, set up CI/CD (GitHub Actions / GitLab CI).
• Publication to App Store and Google Play in compliance with App Store Review Guidelines and Google Play Developer Policy.
• Employee training (up to 3 hours of online sessions).
• 3 months of technical support and bug fixes.

Contact us to evaluate your project. Request a demo to see the functionality in action.

Comparison of basic and extended version

Timeline and cost

Basic app (GPS check-in/out, timesheet, export) — 2-4 weeks. With NFC, Wi-Fi fingerprinting, offline mode, and 1C integration — 6-10 weeks. Cost is calculated individually: number of platforms, whether a web version for HR is needed, volume of integrations with external systems. Get a consultation — we will calculate an accurate estimate for your project.

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.