Capture offline
Orders, deliveries, payments and visits are saved to a local database on the device. No signal needed, nothing waiting on a spinner.
BUILT IN-HOUSE
MOBILE APPS.
Native Android apps for field sales, deliveries, inspections and off-grid data capture. Offline-first, role-aware and wired straight into Odoo through a custom REST module we maintain.
- Kotlin
- Jetpack Compose
- Room
- Offline-first
- Play Store
RECENT BUILD
Field operations for a distribution business.
An East African distributor asked us to move their sales reps, delivery drivers and supervisors off paper and messaging apps. We shipped a native Android app that works offline, syncs when a signal returns, and posts every transaction straight into Odoo.
20+
Screens in production
13
Offline entities synced
9
REST endpoints
3
User roles
OFFLINE-FIRST
Built for bad signal.
A rep on a boda in the rain should never see a spinner. The app keeps working with no bars, then quietly reconciles with Odoo the moment a connection comes back.
Queue & retry
Every change waits in a pending queue with automatic retry. Close the app, swap a SIM or run flat, and nothing is dropped.
Post to Odoo
When signal returns the queue drains through our REST module into real sale orders, stock moves and payments. Head office sees it live.
ON THE PHONE
What the field team actually taps.
All roles
Daily dashboard
Deliveries, visits, stock on truck and pending payments in one glance.
Sales rep
Customer list
Pending, approved and rejected accounts with GPS and phone tap-through.
Sales rep
Field sales
Quotations captured offline, posted to Odoo as sale orders the moment signal returns.
Driver
Delivery runs
Drivers see only their assigned stock moves, confirm on arrival, sync back.
How we build mobile apps.
The patterns we fall back on when a client needs an Android app that talks to Odoo and still works with a cracked screen on a bus in the rain.
Offline-first by default
A local Room database is the source of truth while the user is in the field. Sync runs in the background when a connection is available.
- Room / SQLite persistence
- Pending queue with retry
- Conflict resolution rules
- Two-way delta sync
Role-based UI
Sales reps, delivery drivers and supervisors see different screens, different actions and different data, all from the same install.
- Backend role drives UI
- Per-role dashboards
- Approval workflows
- Territory filtering
GPS & photo capture
Geotagged customer creation, verified check-ins and photo evidence for deliveries and field audits.
- Location verification
- Camera + compression
- Push-only photo upload
- Map view per rep
Custom Odoo REST module
Purpose-built endpoints that speak the app's language rather than a generic XML-RPC wrapper. One module, versioned, shipped with the app.
- Token-based auth
- Batched reads & writes
- Mobile UID upserts
- Dual timestamps
Native Android
Kotlin and Jetpack Compose, clean architecture with MVVM. Unit-tested domain logic, Play Store distribution, signed releases.
- Kotlin + Compose
- MVVM + StateFlow
- Unit tests on domain
- Play Store releases
Multilingual out of the box
Shipped apps in English and French; adding a third language is an afternoon. Numbers, dates and currencies respect locale.
- English + French today
- Swahili on request
- Runtime language switch
- Locale-aware formatting
BEYOND DISTRIBUTION
The same foundation fits any team away from a desk.
Distribution is one shape of field work. Offline-first capture, role-based screens and a clean line back to Odoo suit a lot more than vans and routes.
- Field & van sales
- Deliveries & dispatch
- Stock-takes & counts
- Inspections & audits
- Field service
- Surveys & data capture
Need an app that works off-grid?
Tell us the field process, the user roles and the data it has to reach inside Odoo. We'll come back with a scope, a timeline and a price.