Site Analytics Available
How many? Traffic, sources, devices and geography for every site you run, plus the business events your site already pushes to a dataLayer.
Site Analytics in detail →App Analytics Available
How is the app doing, release by release?
The same product as Analytics for sites, pointed at an app. You add one SDK (see measuring an app) and Skomi reports what people did: which screens they reached, how long a session lasted, which release they were on, and whether it crashed.
What you get
The questions an app actually raises.
A site has a URL and a referrer. An app has neither, and has something a site does not: a version people are stuck on until they choose to update. These reports are built round that difference.
Screens, sessions and people
The three totals everything else is read against. A screen is what a page view is for a site; a session ends the same way a visit does, after half an hour of quiet.
Broken down by release
Every figure can be read per version, which is the breakdown an app needs most and a site has no equivalent of. A regression is usually one release, not one screen.
Crash-free sessions and crash-free users
Both, because they answer different questions: one bad screen crashing every session is a different problem from one unlucky device crashing constantly.
Session length, median and mean
Median first. A handful of forgotten background sessions drag a mean somewhere no real session went. The mean is shown beside it rather than instead of it.
Errors, grouped
What broke, on which release and how often, with the screen it happened on. Fatal and non-fatal are counted separately.
Live, while it is happening
Who is in the app right now, on which screen and which release. Useful in the ten minutes after you ship something.
Mobile and desktop
The same reports you read for a site
Every report on this page is the one Skomi draws for a site, reading an app instead. What an app adds is the questions only an app has: which build people are on, which OS version, which device, and how many sessions finished without a crash. Apps are tracked separately from sites and counted separately against your plan.
There is no script tag to paste, so the equivalent is a package and one line to start it. The SDK batches what it collects and keeps it if the device is offline, sending when there is a connection. An app measured only when it has signal is an app measured only in cities. The wire format is frozen at version 1: you can change a site's script this afternoon, and you cannot make somebody update an app.
Eight clients cover the platforms: Android and iOS natively, Kotlin Multiplatform, Flutter and React Native across both, Unity for games, and .NET and Electron on the desktop.
Android · Kotlin
Skomi.start(this, SkomiOptions("your-app-id")) Skomi.screen("checkout/review")
iOS · Swift
Skomi.start(options: SkomiOptions(appId: "your-app-id")) Skomi.screen("checkout/review")
What it is not
The things an app half does not do.
Stated here rather than discovered after you have integrated. Two of the three site products have no app version at all, and one of them is the one people ask about most.
No session recordings or heatmaps
Behavior records a page's DOM and replays it. An app has no DOM, so there is nothing for it to record, and rebuilding it for native views would be a different product rather than the same one.
No in-app feedback widget
Feedback pins a comment to the element a visitor pointed at, which needs a page. Ask inside your own app and send it wherever you already send support.
Identity is on the device
A site measured by Skomi stores nothing on the visitor's device and needs no consent banner for it. An app is the other case: the SDK holds an id, so tell people in your privacy notice as you would for any other app.
The rest of the platform
Same script, same account.
Every product reads the site you have already registered. Switching one on is a toggle, not another installation.
Site Behavior Available
What did they do? Heatmaps of where people click and how far they scroll, replayable recordings of real visits, and a live view of who is on the site now.
Site Behavior in detail →Site Feedback Available
What did they say? Let visitors rate a page and say what is wrong, pinned to the exact element they were looking at and triaged in one inbox.
Site Feedback in detail →Point it at an app.
Same account, same bill, same reports you already read for the site.