Mobile apps

Apps for people doing a job, not scrolling a feed

Business mobile work almost always fails on the same three things: it assumes signal, it ignores battery, and it was designed for someone sitting down. A field engineer with gloves on a rooftop needs large targets, offline capture and a sync they can see the state of.

Technologies used

FlutterReact NativeDartSwiftKotlinFirebaseREST APIsSQLite

What is included

  • Platform decision made on your constraints, not our preference
  • Flutter or React Native cross-platform build, or native Swift and Kotlin where the hardware demands it
  • Offline capture with a visible sync queue and conflict rules
  • Push notifications, deep links and background sync where needed
  • Store submission handled, including review responses and privacy declarations
  • Crash and performance monitoring from day one
  • Accounts, certificates and provisioning registered to you

How a project like this runs

  1. 01

    Constraints first

    Devices, connectivity, gloves, sunlight, battery, and whether it needs to work in a basement.

  2. 02

    Prototype the core action

    The one thing the app exists to do, on a real device, in the first fortnight.

  3. 03

    Build and test on hardware

    Real phones on real networks, including throttled and offline states.

  4. 04

    Store submission

    We prepare listings, privacy answers and screenshots, and handle review pushback.

  5. 05

    Post-launch window

    Two weeks of fast fixes while real usage exposes what testing did not.

An illustrative situation, not a client story

A service team records job sheets on paper, then someone types them into the office system three days later. We build a phone app that captures the sheet, photos and a signature offline, queues it, and syncs when the van reaches coverage. The office sees jobs the same evening. Paper stays in the vans for a season as a fallback.

Three questions we get about this

Cross-platform for most business apps: one codebase, one team, and the performance is fine. Native when you need heavy camera, Bluetooth, background location or platform-specific hardware access.

Often not. If it is occasional use over decent connectivity, a well-built responsive web app costs less and updates instantly. We will say so before you spend money on stores.

You do. The developer accounts are registered to your company and we work inside them.