Drivers and field crews
GPS tracking, job dispatch, signature capture, offline-first sync for when the cell signal drops. The pattern behind our logistics SaaS work.
Service · 05 · prototype
Mobile apps for problems
Now viewing
Home screen
Mobile apps for problems
that live in pockets.
Driver, field-service, customer, internal. Tap any app on the phone to try a real flow we’ve shipped for a client.
Tap any app icon to see a real interaction. Three of these are flows we’ve shipped for clients: driver dispatch, AI quoting, and call handling.
routeup
v3.2
Job #2841 · Pickup
24 Manchester St, Christchurch
2 km · ETA 8 min · cash on collection
quotery
AI
site photo · auto
takeline
3 today
+64 21 444 5678after hours · agent answered
8:42pm
!
+64 27 233 1190missed · message saved
7:18pm
+64 22 887 4421booking confirmed
3:04pm
vital
concept
Concept · case study coming
HealthKit integration, daily nudges, motion data. We have a working prototype, get in touch to see it.
trailmark
concept
Field routing prototype
Offline tile caching, pin-based booking, ETA. Working version exists internally; ask us to demo it.
deck
internal
Studio chat on the go
The studio agent in our pocket. Tap “Talk to D3V” at the top right to chat in the browser.
What we build Driver, field, customer, internal
Timeline 6 to 14 weeks to TestFlight
Engagement Fixed-scope · small ongoing retainer
Where it earns its keep
Six places where a mobile app actually pays back.
Customer-facing tools
Bookings, loyalty, order status, in-app messaging, push notifications. Apps that earn their place on the home screen.
Internal team apps
Shop-floor checklists, retail stock counts, audit trails, photo uploads. The stuff a web app on a phone screen can’t quite do well.
Health, fitness, wellness
Sensor and HealthKit integration, motion data, sleep, daily nudges. We hold the privacy bar especially high here.
Logistics and trades
Route planning, time tracking, quoting from a job site, machine inspection. Apps designed for one hand and gloves on.
Offline-first workflows
Inspections, surveys, field reporting in places without coverage. Local persistence, conflict resolution, background sync when the bars come back.
Native, hybrid, or web?
We pick the shape per problem, not per fashion.
a.
Native (Swift / Kotlin) for apps that demand it.
High-frame-rate UI, deep OS integration, HealthKit, ARKit, complex camera or audio work, hand-tuned performance. When you genuinely need it, accept no substitute.
b.
Cross-platform (Flutter or React Native) for shared codebases.
Most business apps live here. One codebase, two stores, predictable maintenance. We default to Flutter for new builds, React Native when there’s an existing team familiar with it.
c.
Progressive web apps when an app store isn’t worth the trouble.
If you don’t need push, offline, or deep OS integration, a well-built PWA is faster to ship, easier to update and free of the store review tax. We will say so when it applies.
Under the hood
A handful of tools we keep circling back to.
SW
Swift
SW
SwiftUI
KO
Kotlin
JC
Jetpack Compose
FL
Flutter
RN
React Native
EX
Expo
FI
Firebase
SU
Supabase
HE
HealthKit
MA
MapKit
MA
MapLibre
ST
Stripe
RE
RevenueCat
SE
Sentry
FA
Fastlane
TE
TestFlight
PC
Play Console
Related work
More of what we do.
Got an idea that needs to live in a pocket?
Bring us the problem, the user and the shape of the day-in-the-life. We will tell you, honestly, whether an app is the right answer.