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
| Method | Accuracy | Battery | Indoors |
|---|---|---|---|
| GPS | up to 3-5 m | high | low |
| Wi‑Fi fingerprinting | up to 10 m | low | high |
| NFC | contact | no impact | excellent |
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.
Technical details of synchronization
Sync conflicts are resolved by the "last write wins" rule considering client_id. If multiple changes exist, server record takes priority. For tracking sync status, columns synced and sync_error are used. On sync error (e.g., timeout), the record is not marked synced and retries on the next window.
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
| Feature | Basic version | Extended version |
|---|---|---|
| GPS check-in/out | + | + |
| Wi-Fi fingerprinting | – | + |
| NFC tags | – | + |
| Offline mode | – | + |
| 1C integration | CSV only | REST API |
| Export PDF/Excel | Excel | Both |
| Support | 1 month | 3 months |
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.