Mobile apps
Android-first apps built for real conditions: patchy data, shared devices, mobile money.
Who it's for
You are probably here because
-
01
Your field team is collecting data on paper and typing it in later.
-
02
Customers ask for an app and you are not sure one is warranted.
-
03
You need payments in the app, and M-Pesa is not optional.
-
04
Your last app worked in the office and failed in the field.
What's included
What you actually get.
An app that only works on good 4G is not finished. We build for the device and the connection your users actually have, and we test on a mid-range handset rather than a laptop simulator.
Customer-facing apps
Ordering, booking, accounts, notifications.
Field data collection, offline-first
Works with no signal, syncs when it returns.
Delivery and logistics tracking
Routes, proof of delivery, live status.
M-Pesa Daraja integration
STK push, C2B, B2C and reconciliation.
USSD and SMS fallbacks
For the users who will never install an app.
Play Store publishing and updates
Listing, releases, staged rollouts.
How it runs
Each stage, and what it produces.
-
01
Discover
What the app must do without a connection, and on whose phone.
Output
A written scope with the offline behaviour spelled out.
-
02
Specify
Screens, sync model, payment flow and a fixed quote.
Output
A specification and a clickable prototype.
-
03
Build
Cycles with a real installable build at the end of each.
Output
An APK on your own phone, every two weeks.
-
04
Publish and support
Store listing, release, monitoring, updates.
Output
A published app and a release process you can repeat.
What you are handed
- Source code and signing keys, transferred to you
- Play Console listing under your own account
- A tested offline and sync behaviour, documented
- Crash reporting and update process configured
Technology
Proof
One project, in full.
Stock and dispatch system for a regional distributor
Four branches on separate spreadsheets, month-end taking a week.
One day
Month-end close
Four branches tracked stock in separate spreadsheets. Dispatch errors were routine, nobody could see group stock in one place, and month-end close took a week of reconciliation that one person held in their head.
One day
Month-end close
Four
Branches on one system
Single view
Group stock
Commercials
How buying this works.
Engagement
Fixed-price build, then a monthly plan for updates and store maintenance.
Price
On request, after scope
What sets the price
Number of screens, whether it must work offline, how many payment and messaging integrations it carries, and whether iOS is in scope as well as Android.
Offline-first roughly doubles the sync work. It is usually worth it, and we will say so if it is not.
Every project is quoted after we understand the scope. You will have a written, fixed quote before any build work begins. No open-ended billing.
Questions
Answered plainly.
Yes. The repository and every credential transfer to you on final payment. You are never locked to us to keep running what we built.
Yes, after a paid two-day audit. We read the code, run it, and give you a written opinion on whether to continue it or restart, with the cost of each.
You, on your own account, or us under a care plan. Either way the account is in your name and you hold the credentials.
Yes, via Daraja: STK push, C2B, B2C and reconciliation. We have shipped all four and we will tell you which fits your flow.
Thirty days of fixes are included, then a monthly care plan if you want one. Support is the product, not an upsell.
Yes. We can also supply engineers into your team on a day rate if that suits you better than a fixed-price project.
Often bought alongside
Build
Get a scoped quote for your app
Tell us where it will be used and on what, and we will scope it honestly.
We reply to every enquiry within one working day.