Downloads are a start.
Usage tells the story.
See how many devices actually use your app, how often they return and how long sessions last. Understand the audience behind every release, without advertising identifiers.
iOS, tvOS & Android · PRO & ENTERPRISE · Hosted in Switzerland
Illustrative data · devices, not people
A clearer picture of your active audience
A spike in sessions can mean more devices, more frequent visits, or both. Know which story your numbers are telling.
Separate reach from repeat visits
Track distinct active devices over a day, a trailing week and a trailing month. One device opening the app ten times is not ten new devices.
See whether usage becomes a habit
Stickiness shows the share of your monthly active devices that are active on a given day. Follow the trend, not just a growing download count.
Know what is actually being used
See which app and OS versions account for reported sessions. Compare device models and languages to put release and support decisions in context.
For release adoption plus a confidence-based crash-health verdict, explore release rollout health.
Measure time in the app, not in the background
An average can hide a lot of brief visits. See the spread of session lengths before deciding what changed.
- Foreground time only. Background launches and background time do not inflate session-duration metrics.
- Go beyond the average. Compare median and P10–P90 trends, a duration histogram and clear duration ranges.
- Find the affected audience. Filter by app version, OS, device model or language to see where session patterns differ.
Usage tells you what changed. Crash reporting and non-fatal errors help you investigate whether failures are part of the story. To time a specific operation rather than a whole session, explore performance traces.
Illustrative distribution · not a time-spent target
Useful analytics. Deliberate collection.
Enable session monitoring in the SDK you already use. No custom event taxonomy to design before you can understand basic app usage.
AppeliumFeedback.start(
apiKey: "YOUR_API_KEY",
sessionMonitoring: .enabled
)AppeliumFeedback.start(
apiKey = "YOUR_API_KEY",
application = this,
sessionMonitoring =
SessionMonitoringConfiguration.Enabled()
)Devices are counted using a randomly generated SDK identifier. Your data is hosted and processed in Zürich, Switzerland. You choose which features to enable.
Frequently asked questions
What do DAU, WAU and MAU mean in Appelium?
They count distinct active devices, not logged-in users. DAU covers a UTC day; WAU and MAU cover trailing windows of 7 and 30 UTC days. A device active on several days is counted once within each window, rather than adding up the daily totals. Counts are approximate distinct-device estimates.
What does stickiness tell me?
Daily stickiness is DAU divided by MAU: the share of the monthly active device base that is active that day. The Dashboard summary averages those daily ratios over the completed days in the selected range. It helps reveal habitual use, but is not a cohort-retention measurement.
Does background time count toward session duration?
No. Session monitoring measures foreground time. Background launches and time spent in the background do not contribute to session-duration metrics. Explore the average, median, P10–P90 trends, a duration histogram and fixed duration ranges to understand the distribution.
How are devices identified, and which plans include this?
The SDK uses a randomly generated, stored device identifier, not an advertising identifier. These are device counts, not a way to identify people or deduplicate one person across devices. Collection is off until you enable it. Sessions and active-device analytics are available on PRO and ENTERPRISE for iOS, tvOS and Android.
Understand the audience behind every release
Active devices, everyday habits and meaningful session trends. In one place.
You are in a good company - Join over 150 apps!
Over 150 apps in Switzerland choose to use Appelium.
👨💻 Latest content from our Engineering blog:
XPCService
Strongly typed bidirectional communication channel between UIApplication and XCUIApplication with powerful APIs and super fast performance.
More about XPCService
Screen Flow Pattern in UI tests
Robust and scaleable pattern for structuring UI tests. Highly reusable screen verification code with human readable test case code. All flows and interactions statically typed 🙌.
More about the Screen Flow Pattern
SnapshotQuery™
Learn about SnapshotQuery - our latest addition to AppeliumTests which radically improves the performance of your XCUITests while making them more stable and reliable at the same time.
More about SnapshotQuery
Early access and news
Be the fist one to know about all the exciting engineering posts and product announcements.