Help for owners
My app sits on a blank screen for ages when customers open it
Short answer
The slowest way an app opens is a cold start, when the phone has to build the app from scratch. Android's documentation names heavy start-up code, large screens, work that blocks drawing and old splash-screen tricks as the usual causes. First measure it on a real, older phone, then fix the biggest delay, not the first guess.
Does this sound like your situation?
- After tapping the icon, customers see a blank or white screen for a long moment.
- The app opens quickly when it was used a minute ago and slowly after the phone restarted.
- It is fast on my new phone and slow on customers' older ones.
- Reviews say the app takes forever to start, or people say they open it and then give up.
- The splash screen stays up while the app waits for the internet.
Why does this happen?
Cold, warm and hot starts are different amounts of work
Android describes three kinds of start. In a cold start the app begins from scratch, for example the first launch since the phone booted or after the system closed the app. It is the heaviest of the three, so it is the one to measure and improve first.
Confirmed by developer.android.com
Too much work is done before the first screen
Android's guide lists heavy start-up code in the application object as a common cause: set-up that does not need to happen yet, disk reads and extra garbage collection. Its recommended remedy is to set things up only when they are first needed.
Confirmed by developer.android.com
The first screen is too heavy to draw
The same guide names a large or complex screen, loading and decoding images, and blocking the first drawing on disk or network as typical causes. The app waits for all of it before showing anything.
Confirmed by developer.android.com
An old custom splash screen adds time
For Android 11 and earlier, splash screens built by switching off the system start window or by using a separate screen can add start-up time. From Android 12 the guide says moving to the SplashScreen API is required.
Confirmed by developer.android.com
Start-up waits for the server
If the first screen cannot appear until a network answer arrives, a slow connection or a slow server turns directly into a long start. That is a different cause from the app code, and it needs a different fix.
What can I do about it today?
- Time it on an older phoneClose the app fully, restart the phone, open the app and count the seconds until you can use it. Do it on the oldest phone you can borrow, not on your own newest one.
- Compare with and without internetRepeat the test once in airplane mode. If it opens much faster, the wait is on the network or the server, not in the app itself.
- Note what the customer seesWrite down whether the screen is blank, a logo or a spinner, and how long each lasts. A screenshot or a short screen recording helps a developer a lot.
- Collect the exact phones and versionsFrom reviews and support messages, list the phone models and app versions that report slow opening.
- Do not ask for a quick fix to the splash screenHiding the wait behind a longer or fancier splash screen does not shorten it. Ask for the cause to be measured first.
When should I bring someone in?
- The slow start is in reviews and users are leaving, and nobody on your side can read a performance trace.
- It got slower after an update, a new SDK or more data in the app.
How do I handle it?
- Measure the start, not guessI record the time to the first screen and the time until the app is usable, on an older phone, from a cold start. The two numbers show whether the delay is drawing or loading.
- Find the biggest blockI trace what runs before the first screen: set-up code, third-party libraries, disk reads, big images and network calls. One or two items usually account for most of the wait.
- Move work out of the wayAnything not needed for the first screen is started later or only when first used. The first screen shows quickly with placeholder content while the rest loads.
- Re-measure on the same phoneEach change is measured again with the same test, so the improvement is a number and not an impression.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
What is the difference between cold and warm start?
Android's documentation says a cold start begins from scratch, while in a warm start the system brings the running app back and does only part of that work. A hot start does the least.
Why is my app fast for me and slow for customers?
Older phones have less memory and slower processors, and the first launch after a restart is a cold start. Testing on a recent phone with the app already in memory hides both.
Can a longer splash screen fix it?
No. It only covers the wait. The wait ends when the work done before the first screen is reduced.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.