Building a CRM mobile app that works in the field

A mobile CRM that only works on excellent WiFi in a quiet office is not a mobile CRM. Real field work happens in hospital corridors, on construction sites, in the driveways of clients, and in ambulances moving at 120km/h. The constraints are real, and building for them requires deliberate engineering choices.

Offline-first architecture

The fundamental requirement for a field CRM is offline capability. The app must work without a data connection, queue changes locally, and sync when connectivity returns — without data conflicts or lost updates. This requires a local-first data architecture: the app's primary data store is on the device, not the server.

Industry-specific mobile workflows

Mobile isn't just a smaller screen. Different industries need different mobile workflows. An EMS crew needs to capture an ePRF on scene with one hand while stabilising a patient with the other — the form must be fast, large-target, and work offline. A real estate agent needs to add viewing notes while standing in a property. A salesperson needs to log a call outcome from the car park.

• EMS: ePRF capture, offline sync, GPS incident tagging
• Real Estate: Property viewing notes, photo capture, client call logging
• Sales: Call outcome logging, deal stage updates, voice notes
• Construction: Site inspection forms, purchase order approval, progress photos

The Komilfo mobile approach

We're building native iOS and Android apps with React Native alongside a Progressive Web App for cross-platform reach. The mobile experience inherits the same industry morphing as the web — a healthcare user on mobile sees Patients and Appointments, not Leads and Deals.

Mobile parity isn't feature parity — it's workflow parity. The mobile app should support the complete workflows that happen away from a desk, not a stripped-down version of what the desktop does.