Build an offline first app now, not when satellite arrives

Vodacom wants to launch a satellite-to-phone service in South Africa towards the end of 2027, most likely with AST SpaceMobile, according to TechCentral's report on Vodacom's satellite-to-phone plans. Good news for any business whose people work on farm roads, reserves and long routes. My advice is not to wait for it: build an offline first app now, one designed to work with no signal first and sync later.

The coverage gaps are where field apps get used

South African mobile coverage looks almost complete if you count people, and much thinner if you count land. ICASA's State of the ICT Sector Report of South Africa, March 2026 puts 4G population coverage at 99.5% in 2025, while geographical broadband coverage stayed at 82.1%, barely moving in a year.

The missing part of the map is mostly where people do not live. It is the gravel road to a lodge or the access road to a mine. If you run tours, deliveries or field services, that is where your people open your app. Satellite exists to fill those places, which tells you the gaps are not closing soon.

Why waiting for 2027 is the wrong plan

Vodacom's satellite-to-phone service is, for now, only a target. Vodacom Group CEO Shameel Joosub "hopes" to launch towards the end of 2027 and will "more than likely" use AST. Nobody has published what it will carry, how fast or at what price. Airtel's Starlink Mobile service, switched on in the DRC in August, carries text messages and light data such as WhatsApp, but not voice. Direct-to-cell also will not work on 2G or 3G phones.

You cannot design a product around a spec that does not exist yet. An app that needs a live connection depends on whatever that service turns out to carry. An app designed for no signal does not care, and when satellite arrives it benefits for free, because what it sends is already small and already queued.

What we proposed for a reserve with no signal

When we scoped a visitor app for a South African game reserve with more than 200 kilometres of gravel roads, we assumed visitors would lose signal on those roads. So we proposed that the full map, roads, trails and points of interest download to the phone while the visitor still has signal, and keep working with none. GPS positioning would work the whole time, because GPS does not need mobile signal, and a sighting posted in a dead zone would wait on the phone and sync automatically when signal returns.

We were honest about one limit. An alert from reserve staff would reach every connected phone within seconds, but a phone with no signal only gets it once it reconnects. That last gap is the one satellite could close one day, because an alert is a tiny message. The heavy content would already have travelled on good signal.

What to check before you build an offline app

Go through every screen and ask what happens with no signal. Heavy content that rarely changes, like maps, price lists or job cards, should download in advance on good signal. Anything the user creates, like a signed delivery note or an inspection photo, should save on the phone and send when signal returns. Know exactly which few features truly need a live connection.

Ask your developer to show you the app in airplane mode, and what happens when two people edit the same record offline. A vague answer means the app was designed for the city. A progressive web app can work offline too, so this is a design decision before it is a native versus web one. If you are planning mobile app development in Cape Town for people who work outside town, have this conversation first.

Satellite to phone is worth having, and I hope Vodacom gets there. It can close the last gap for an app that already copes with no signal. It will not rescue an app that needs a good connection just to open.