Native field clients
Kotlin on Android and Swift on iOS keep field-session, location, task, customer, expense, and sync behavior inside platform-native codebases.
Technology
Scootee has three connected parts: native field apps written in Kotlin for Android and Swift for iOS, a Next.js web portal for managers, HR and accounts, and a PostgreSQL data layer where every record carries its organization and row-level security controls access. Eligible records wait on the phone when there is no network and sync later.
Kotlin on Android and Swift on iOS keep field-session, location, task, customer, expense, and sync behavior inside platform-native codebases.
The Next.js portal gives employees, managers, operations, HR, accounts, tenant owners, and platform staff the surfaces permitted for their scope.
PostgreSQL records carry organization context and use row-level policies, authenticated sessions, storage rules, and domain validation.
Sessions, location points, trips, stops, customers, expenses, attendance, payroll-preparation periods, and requests can retain their relevant relationships for office review.
The employee starts a work session in the field app, and location recording begins for that session. On Android an active session runs as a location foreground service, so the phone shows an ongoing notification while recording; on iOS the app uses Core Location background updates with pause, resume and recovery. Ending the session stops the tracking workflow and finalises the route.
Each location fix is saved on the phone first and uploaded afterwards, so a dropped connection does not lose the route. See the employee tracking app for the employee’s view of the day.
Scootee keeps one canonical distance value for each session together with the method that produced it. Depending on the workflow, the distance comes from the recorded GPS trail, an eligible Android point-to-point road route, confirmed odometer evidence, or a disclosed fallback, and the method travels with the number into review and export.
Before a fix counts, the Android app rejects mock (spoofed) locations and fixes with missing or poor accuracy, and filters stationary jitter. Reviewers also see a GPS drift estimate on the session page. The same km value feeds conveyance reimbursement at per-km rates; the distance engine page explains each method.
GPS itself does not need mobile data. On Android, sessions, location points, expense claims with their receipt attachments, and employee requests are written to a local database and queued for upload; the iOS app keeps an offline queue for tracking and reconciles with the server without creating duplicates. Queued records submit once connectivity and sign-in recover. Queue coverage differs by platform and record type, so test it on your own phones and routes.
Where workforce screens refresh in real time, the portal subscribes to value-free change hints rather than streaming employee, GPS or payroll rows. When something changes, the portal re-reads the record through the same permission checks as any other request, so a manager only sees updates for staff inside their scope. Managers can open active staff, the recorded route and stops, visits, tasks and pending claims from one place — the field force management workflow.
Conveyance, attendance and payroll-preparation screens export Excel workbooks, and longer reports can be generated in the background and downloaded as CSV files. The conveyance export lists employee and session details, distance in kilometres, the rate in INR per km, the INR amount and the payment reference. Named payroll or accounting connectors are evaluated separately — see exports and integrations.
Both apps share the same organization-scoped backend, sign-in and session model. Android currently demonstrates the broader workforce workflow; the iOS client covers tracking, history and claims, and its public App Store release is still being prepared. Confirm store availability and the exact workflows each platform must support before rollout — the mobile field app page lists the current coverage.
Offline capture and recovery
Queue and sync coverage varies by mobile platform and record type. Test the selected release with your devices, permissions, and weak-network conditions.
Mobile app coverageEligible field records can be held on-device when the network is unavailable.
Workers and background services submit queued records after connectivity and authentication recover.
Office workflows use the relevant stored record. Distance method and quality help explain the calculation rather than imply that every GPS fix is exact.
Release configuration and mobile diagnostics help identify permission, policy, and sync failures during rollout.
Questions / answers
Scootee’s field apps are native: Kotlin on Android and Swift on iOS. Managers, HR and accounts use a separate Next.js web portal. All three use the same organization-scoped PostgreSQL backend.
Location is recorded only during an active work session, not all day, and the Android app reduces fix frequency when Battery Saver is on. Battery use still depends on the phone, the operating system’s background limits and the length of the session, so test it on the devices your staff carry.
The Android app rejects fixes it detects as mock locations and discards fixes with poor accuracy before they count toward distance. No phone-based system can rule out every manipulation, so reviewers should still read the route, stops and visits behind a claim.
A public API, scheduled delivery or named connectors are not promised on this page. Scootee provides Excel and CSV exports today; integration requirements are evaluated and quoted individually, as listed in the Enterprise plan.
Use the pilot to check authentication, organization access, mobile permissions, offline recovery, and exported records. Confirm store availability and supported device versions before distribution.