Why this matters
Many people buy small data bundles and switch data off to save it. Networks can be weak in rural areas, inside market buildings and on the road between towns, and power cuts can take masts down. If your design assumes a fast, constant connection, people will see blank screens, lose their work or pay twice by accident. Designing for slow data and offline moments is a real skill that companies serving African markets look for.
Keep screens light
Every megabyte costs your users money.
- Use images only when they help, and keep them small and compressed.
- Prefer simple shapes, icons and text over large photos and videos.
- Load the important content first and the extras later.
- Avoid auto playing videos.
- Offer a "data saver" option, for example to show images only when tapped.
Talk to developers about image formats and page size. You do not need to code, but you should know that a heavy design is slow and expensive for users.
Show what is happening
On a slow network, silence feels like failure. Design clear feedback:
- Loading states. A simple progress indicator or a grey outline of the content (a skeleton screen) shows something is coming.
- Timeouts. After a reasonable wait, say clearly what happened and offer "Try again".
- Last updated. If you show saved information, add the time, such as "Prices from 9:15 this morning".