Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My app works, then suddenly stops reacting

Short answer

An app that opens and then locks up is usually doing slow work on the part of the program that handles touches, such as reading a big list, waiting on a slow server or saving data. The fix is to move that work away from the screen. Collect when it freezes and bring me the phone model.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The app opens fine, then stops reacting to touches on one screen.
  • It freezes when a list, a map or a search loads.
  • Android shows a message that the app is not responding.
  • It freezes more on older phones or after using the app for a while.
  • It only freezes when the connection is weak.

Why does this happen?

  1. Slow work blocks the screen

    Android says an app is not responding when it has not reacted to a touch within 5 seconds, and shows a dialog that lets the user force quit. The page names slow reading and writing of data and long calculations on the main thread as common patterns.

  2. The app waits for a slow server

    If the app asks the server for data and stops everything until the answer comes, a slow server becomes a frozen screen. The app should keep working and show progress instead.

  3. Heavy screens on older phones

    Large lists, big images and complex animations are fine on a new phone and heavy on an old one. Testing only on the developer's own device hides it.

  4. Data piled up over time

    A screen that was quick with a few records can freeze when it has to load thousands, because it was written to load everything at once.

What can I do about it today?

  1. Write down exactly when it freezesWhich screen, which action, how many seconds, and whether it comes back by itself. Patterns point at causes.
  2. Collect phone models and system versionsAsk two or three affected users which phone they have. If the freeze is only on older models, say so.
  3. Check the Android vitals page in Play ConsoleIf you own the Play Console account, open Android vitals and note the not-responding numbers. Do not change anything there.
  4. Test with a good and a weak connectionTry on fast Wi-Fi and on a weak mobile signal. A freeze that only happens on the weak one points at waiting on the network.
  5. Hold the next release until you know the causeNew features on top of a freezing app make it harder to find the cause.

When should I bring someone in?

  • Users leave one-star reviews that mention freezing or crashing.
  • The freeze happens on the screen where people pay, book or sign in.
  • Your developer says it works on their phone and cannot reproduce it.

How do I handle it?

  1. Reproduce it on the weak deviceI test on the kind of phone your users have, not only on a new one, and on a slow connection.
  2. Find what blocks the screenI use the platform's profiling tools to see which operation holds the main thread, instead of guessing.
  3. Move the work off the screenSlow reading, calculating and network calls are moved so the screen stays responsive, and long lists load in pieces.
  4. Check with real numbers afterI compare the not-responding reports before and after the release. I cannot promise a number, because users' phones and networks vary.

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 freezing and stuck on loading?

Stuck on loading means the app never reaches its first screen. Freezing means the app starts and works, then stops reacting to touches. They have different causes.

Is the freeze caused by my server?

It can be, when the app waits for a slow answer. It can equally come from heavy work inside the app. Testing with a strong and a weak connection helps tell them apart.

Do I need to rebuild the app?

Rarely. Most freezes come from a few screens that do too much at once, and those can be repaired one at a time.

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.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.