Building for the Shattered Screen
Picture the phone your customer actually holds. It may be a low-cost Android with limited storage, a cracked screen, a slow connection and a battery that is nearly gone. It is probably not the latest flagship you test on.
If your app only runs well on a new phone and fast wifi, you are leaving out a large part of your market. Advertising to those people makes it worse, because you pay for installs that fail.
Where apps break on these phones
- Too big to install. Phones with little storage will not hold a large app. Many people delete apps to make room.
- Slow to open. Heavy screens and big images make the app freeze or crash.
- Data hungry. Mobile data costs real money. An app that downloads a lot quietly loses trust.
- Poor on bad networks. If it needs a steady connection for everything, it fails when the signal drops.
- Hard to read. Small text and tiny buttons are difficult on small or cracked screens.
- Battery drain. An app that heats the phone or empties the battery gets uninstalled fast.
A day in the life of a low-cost phone
Imagine your customer opens your app on a bus. The signal comes and goes. The screen has a crack across one corner, so they miss a button there. Their storage is nearly full, so the phone warns them about a pending update. Their battery is at 15 percent.
In that moment, a fast, light, forgiving app wins. A heavy, fussy one gets closed and forgotten. Design for that moment and you design for most of your users.
What to do about it
- Test on cheap phones. Buy or borrow two or three low-cost Android phones and use your app on them every release.
- Keep the app small. Compress images and remove what you do not need. Consider a lighter version of the app.
- Make the first screen quick. Show something useful fast, and load the rest afterwards.
- Work with weak signal. Save progress, retry quietly and tell people clearly when something is loading.
- Respect data. Let people choose lower quality images and avoid auto-playing video.
- Design for big, simple taps. Large buttons and readable text help everyone.
- Never lose their work. If the signal drops during a payment or form, save where they were so they can continue.
A simple weekly test routine
You do not need a lab. Once a week, do this:
- Install the newest version on your cheapest test phone.
- Turn off wifi and use mobile data on a weak signal if you can.
- Open the app, sign up and complete the main action, such as a payment or order.
- Note anything slow, confusing or broken, and how long each step took.
- Fix the worst problem before the next release.
Keep a short log. Over a few weeks you will see which fixes made the biggest difference.
What this means for your ads
- Your store page should show the real app size, so people are not surprised.
- Show screenshots from the actual app, not only polished designs.
- Check your install-to-open rate by phone type. If cheaper phones drop off more, the problem is the app, and more ad spend will not fix it.
- Target the phones and Android versions your app really supports, so you do not pay for installs that cannot work.
- Watch uninstalls in the first week. A spike on certain phones tells you where the app is failing.
What to measure by device
Ask your analytics tool to split results by phone brand, Android version and storage level if it can. Then compare:
- Install-to-open rate.
- Time to first screen.
- Crash rate.
- Sign-up completion.
- Day 1 and day 7 retention.
If one group is far worse than the rest, you have found your next fix.
Common mistakes
- Testing only on the newest phones in the office.
- Adding heavy animations and large images "to look modern."
- Forcing a full account setup before showing any value.
- Assuming everyone has fast, cheap data.
- Spending more on ads to cover for an app that crashes.
The takeaway
Build and test for the phone your customer really has. An app that runs well on a modest phone converts more installs, keeps more users, and makes every cedi of ad spend go further.
Need a second pair of eyes on how your app is performing for real users? Talk to us at osidion.com/contact.
