Back to Features

Mobile app analytics

The same for your iOS and Android app, built with Swift, Kotlin, Flutter or React Native.

Your app as a second surface

The app sits next to your website as its own tab. Switch to it and everything is where it was: the written summary, the flow map, the recommended fixes, the list of people and what they did.

Nothing is mixed together. Website numbers stay website numbers, and the app is read on its own terms.

Installing it

The same single prompt with your project key, pasted into your AI builder or coding agent, which does the work. React Native, Swift, Kotlin and Flutter are covered.

Ship a build, open the app once, then press the button. The card stays Not installed until real events arrive, and turns Installed when they do.

What is different about an app

There are no pages and no page views. An app has screens, taps and events, so those are the numbers you get — users, sessions, total events, with the change against the previous period.

If the pageview and click counters sit at zero while events climb into the thousands, that is the shape of a correctly instrumented app, not a broken one.

Onboarding, step by step

The flow map is where an app pays off fastest, because onboarding is a funnel whether you designed it as one or not. Every step is there with the count that reached it: started onboarding, pasted a link, described the product, saw the plan, started the trial.

Two steps lose ten people, one loses fourteen. At that scale you are not reading a percentage, you are reading individuals, and you can go and look at every one of them.

Why they did not pay

The summaries say what the funnel cannot. People reaching the paywall several times, interacting with it, leaving to the home screen without paying, then running the whole onboarding again from the start.

A drop at the plan step reads as a pricing problem. Someone repeating onboarding three times to get back to that screen reads as something else entirely.

People without emails

Most app users never give you an address, so they are listed by their install, with country, device, sessions and a written summary of each visit. It is enough to recognise a returning person and follow what they tried.

Fixes for the wiring itself

Mobile installs usually arrive half-wired, and the first fixes say so: define and connect a success event, check where the funnel events are sent from, repair the capture that is measuring nothing.

Those come before any advice about the product, because a conclusion drawn from missing events is worse than no conclusion.

You shipped a product.

Let's get it earning.

Get started