Design · 2 min
Your app may be tested on fast office Wi-Fi, but customers use it on trains, in basements, at the edge of town and on cheap data plans. Design for that.
Show something straight away
When the app opens, show what it already knows, like the menu from last time or the user's bookings, then refresh in the background. A blank screen with a spinner feels broken.
Say what's happening
- "You're offline. Showing your saved bookings."
- "Couldn't send your order. We'll try again when you're back online." with a "Try now" button.
Never fail silently.
Never lose what people typed
If someone fills in a form and the signal drops, keep their answers. Make it safe to try again without placing the order twice.
Keep it light
- Compress photos and load smaller versions on small screens.
- Avoid huge videos on main screens.
- Load only what's needed for the current screen.
People on limited data plans will thank you, and the app will feel faster for everyone.
What should work offline?
Decide for your app. Often useful:
- the loyalty card and its code
- tickets and booking confirmations
- the menu or catalogue (marked as "last updated")
Test it
Most phones and developer tools can simulate slow networks. Or simply try your app in a lift, on a train or with airplane mode switched on and off.
