Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I have no idea how many people use my app or when it crashes

Short answer

Both stores already show some crash and usage data, so start there. Apple only counts users who agreed to share diagnostics. Google Play shows crash and not-responding rates in Android vitals. For detail you need a crash reporter such as Firebase Crashlytics and an analytics tool, added to the app and shipped as an update.

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

Does this sound like your situation?

  • I hear about crashes from angry customers or reviews, never from the app itself.
  • I cannot say how many people use the app in a normal week.
  • My developer says it works on their phone, but users say it does not.
  • I do not know which screens people use or where they give up.
  • Nobody has ever shown me a report from the app.

Why does this happen?

  1. Reporting is not added unless somebody builds it in

    A crash reporter and an analytics tool are small pieces of code inside the app. If the original brief was only 'build the screens', they were never included, and the app tells nobody when it fails.

  2. The stores show only part of the picture

    Google Play's Android vitals shows the share of daily users who had a crash or an app-not-responding error. Apple's usage data only includes users who agreed to share diagnostics and usage information, and some reports are withheld when volumes are too low. So a small app can show very little.

  3. A crash reporter collects the details a developer needs

    Firebase Crashlytics collects crashes and non-fatal errors, groups related events into issues and sends real-time alerts for new, regressed and growing issues. It supports Apple, Android, Flutter and Unity apps.

  4. Analytics only counts what somebody decided to measure

    Google Analytics for Firebase collects common events automatically, and you can define custom events for what matters to your business, such as a finished order. Without that decision there is nothing to report on.

  5. Crash numbers can affect how easily people find the app

    Google states that an app above its bad-behavior thresholds for crashes or not-responding errors is likely to be less discoverable on Google Play. Not watching these numbers has a cost.

What can I do about it today?

  1. Open the free store reportsAsk for viewer access to your App Store Connect and Google Play Console accounts, or look at them with the account owner. Look at Android vitals and the Analytics section for crashes and usage. You only read; nothing changes.
  2. Write down five questionsFor example: how many people open the app each week, where do new users stop, and what do paying users do first. Analytics is set up around questions, so these decide what gets measured.
  3. Collect what customers already tell youGather support emails, store reviews and screenshots of problems, with the phone model and app version if they are known. This gives a developer something to look for.
  4. Ask your developer two plain questionsIs a crash reporter inside the current version, and who can see its reports? If the answer is 'no' or 'I am not sure', that is your answer.
  5. Check what your privacy policy saysAdding analytics changes what data the app collects. Make sure the privacy text and store declarations are updated at the same time, and have your developer or adviser confirm what applies to you.

When should I bring someone in?

  • Customers report crashes you cannot reproduce or even see.
  • You are about to spend money on marketing for an app you cannot measure.
  • Your developer is no longer available and nobody knows what is inside the app.

How do I handle it?

  1. Read what is already thereI check the code and the store consoles for any reporting already installed, and note who owns each account.
  2. Agree the questions firstI turn your questions into a short written list of events and screens to measure, kept small on purpose.
  3. Add crash reporting and analyticsI add a crash reporter and analytics to the app, with the accounts in your company's name so you own the data.
  4. Release and test itI ship the change as an ordinary update and check that a deliberate test error and the key events arrive in the dashboard.
  5. Hand over a readable viewYou get a short note on where to look and what a bad number means, so the next conversation with any developer starts from facts.

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?

Do the stores not already tell me everything?

No. Apple's usage data only covers users who agreed to share diagnostics and usage, and some reports are withheld when volumes are too low. Google Play shows crash and not-responding rates. Neither replaces a crash reporter that gives a developer the details.

Is Firebase the only option?

No, other tools exist. I name Firebase because its pages are public and it supports Apple, Android, Flutter and Unity apps. The choice depends on your app and your privacy needs.

Will adding this slow the app down or change how it looks?

It adds code that runs in the background and does not change the screens. I test the update before it goes to the stores like any other release.

Can this be added to an app that is already live?

Yes, through a normal update. It only reports from the users who install that new version.

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.