Mobile products

Software in the hands of people who are nowhere near a desk.

Field agents, drivers, health workers, cooperative members and customers are on Android phones, on networks that drop, in places where the data bundle ran out yesterday. Software written for an office assumes a connection that isn't there, and fails exactly where the work happens.

HOW YOU KNOW

You have this problem if…

If none of these sound like your organisation, this is probably not the domain you need — and we will say so rather than sell you into it.

  • !Your people work where the network doesn't, and paper gets typed up days later
  • !Field data arrives late, incomplete, or twice
  • !You need a customer app that survives a real review, not a wrapped website
  • !Your app works in Kigali and falls apart upcountry
WHAT WE BUILD

Systems we have built in this domain.

WHO ARRIVES WITH THIS

Field operations. Consumer fintech and commerce. Logistics and last-mile delivery. Health and agriculture programmes.

  • Customer apps for fintech, commerce and services — Android and iOS from one codebase
  • Offline-first field apps that sync when the network returns and never lose a record
  • Agent, driver and inspector apps with GPS, routing and proof of visit
  • In-app MoMo, Airtel Money and card payments
  • Push notifications, with SMS and USSD fallback for feature phones
  • Store submission and signing keys in your name, on both stores
TYPICAL STACK
React NativeExpoFlutterSQLiteOffline syncFirebaseNative modules

The stack is a consequence of the problem, not a preference. Where you already run something else, we work in what you have rather than forcing a rewrite you did not ask for.

HOW IT RUNS

Scoped before it is priced. Written down before it is built.

Every engagement in this domain starts the same way: a paid technical discovery that ends in an architecture, a fixed scope and a fixed price. You own that document either way.

01

Technical discovery

1–3 weeks · Fixed fee

Every engagement that involves building something new. This is where we start.

02

Fixed-scope build

Scoped in discovery · Milestone-based

A defined system with a clear boundary: a core platform, a payments engine, a mobile product.

03

Embedded engineering

Monthly, rolling · Per engineer, per month

Organisations with a technical team that needs depth, speed or a skill they do not have in-house.

04

Run & evolve

Ongoing · Monthly, under an SLA

Any system the organisation now depends on, whether we built it or inherited it.

Tell us what is breaking. We will tell you what it would take to fix it.

Bring us the problem