Offline-First: Building Cloud Apps for Patchy Internet
Omondi works as a field officer for an agricultural supplier, visiting farmers across western Kenya. His company gave him a shiny new cloud app for recording orders. It worked beautifully in the office in Kisumu. Then he drove out to meet a farmer on a hillside where the network signal was one bar on a good day and zero on most. The app showed a spinning circle. The farmer offered him tea. The circle kept spinning. The order was written on the back of a receipt, and the receipt was lost by Thursday. It is the best argument for offline-first app development in Kenya we have heard.
This is the problem with cloud apps designed by people who assume the internet is always there. In Kenya, connectivity is much better than it used to be, but it is still not guaranteed. Bundles run out. Power goes off and takes the router with it. Some areas simply have weak coverage. An app that only works with a perfect connection is an app that fails at the worst possible moment.
What offline-first means
Offline-first is a way of designing software so it works without a connection by default, then syncs with the cloud whenever a connection is available. Instead of the app constantly asking the server for permission to do anything, it saves work on the device first and sends it up later.
For the person using it, the experience is simple: the app just works. They record the order, take the photo or mark the attendance, and the app quietly handles the rest when the signal comes back.
Where it matters most
Not every app needs to work offline. A dashboard for the managing director, used from a desk with fibre, can probably assume a connection. But offline-first is worth considering whenever work happens in places or moments where the internet is unreliable:
Field sales and agents visiting customers in rural areas
Schools recording attendance or marks during a power outage
Shops and kiosks that must keep selling when the network is down
Health workers and surveyors collecting data in remote areas
Delivery riders confirming drops on the move
The tricky parts
Offline-first sounds simple, but it introduces some interesting problems. The biggest one is conflicts. What happens if two people edit the same record while both are offline? Say Halima updates a customer's phone number on her phone while her colleague at head office updates the same customer's address. When both sync, the system needs clear rules about which change wins, or how to combine them.
Other questions a good design has to answer:
How much data should live on the device, and how much should stay in the cloud?
How is data on the phone protected if the phone is lost or stolen?
How does the user know what has synced and what is still waiting?
What happens if a phone stays offline for a week?
Should some actions, like payments, require a live connection?
That last point is important. Some things should not happen offline. Confirming a payment, for example, needs a real answer from a real server. A good offline-first app is clear about which actions can wait and which cannot.
Tell the user what is going on
One of the simplest improvements is honest communication. A small indicator that says "3 records waiting to sync" builds far more trust than a mysterious spinner. Users relax when they know their work is saved and will be sent later. They panic when they cannot tell whether that order just vanished.
Offline-first app development: what to ask your developers
If you are about to build a cloud app for your business, ask your developers directly how it behaves without internet. Ask them to demonstrate it with the phone in airplane mode. Retrofitting offline support later is usually much harder than designing for it from the start.
Omondi's company eventually rebuilt the order app to work offline. He now records orders on the hillside, drinks his tea in peace, and the app syncs everything when he reaches the tarmac road. The receipts in his pocket are back to being just receipts.
Planning a field, school or retail app that has to survive patchy internet? Talk to Philsoft about offline-first design, or browse our mobile and web app development services to see what we build.