Many people use products on a weak mobile signal and a phone that's a few years old. Design choices that keep products fast for them.
It’s easy to design on a fast laptop with good Wi-Fi and forget how most people will actually use the product. For many users, it’s a mid-range phone, a few years old, on a mobile signal that comes and goes.
Designing for that person first makes the product better for everyone.
Test on the phones people really use
We keep a few older, cheaper Android phones in the studio and test every project on them. A screen that feels instant on a new phone can take seconds to respond on an older one. You only notice by trying.
Make the first screen light
The first thing a user sees should load quickly, even on a weak signal. That means:
- Fewer, smaller images: compressed, sized for the screen, and loaded only when needed
- System-friendly fonts: one or two font files, not a whole family
- Less code up front: load extra features when someone actually uses them
Show progress, not a blank screen
When something does take time, say so. Skeleton screens, short loading messages and saved drafts all help. A user who can see that something is happening waits patiently. A user staring at a blank screen taps again, or leaves.
Plan for the signal dropping
On the way to a trailhead or a remote hotel, the connection will drop. Good products expect it. Forms keep what the user typed, actions retry when the signal returns, and important information is still visible offline.
Big targets, clear text
Older phones often have smaller screens and are used on the move. Larger tap targets, good contrast and readable text sizes make a big difference, and help accessibility at the same time.
Faster is better for everyone
A product that works well on an old phone with a weak signal feels effortless on a new one. If speed matters to your users, let’s talk about your project.
Working on something similar?
Tell us what you're building. We'll come back with questions and a plan.
Start a project
