Mobile Retention
Part of Mobile app retention
Comparing daily habits with naturally infrequent app use
Choose a return window that fits the user’s next need, and avoid treating quiet days in an occasional-use app as automatic failure.
Compare app use at the pace of the task. A daily routine may justify looking for use on successive days. A trip, appointment or renewal app may be useful only around the next relevant occasion. Low daily use alone cannot show that an occasional-use app failed.
Find the next reason to return
Ask when a person would have another reason to use the app after the first task. It might be tomorrow, the next work shift, a booked appointment or an event the app cannot observe. Check that assumption against the product’s actual use; an app category does not determine one cadence for everyone.
For a hypothetical daily log, another entry may be the useful return. For a trip organiser, consulting a saved itinerary during travel may matter more than opening the app every day after making the plan.
| Use pattern | Return question | Possible window |
|---|---|---|
| Regular routine | Was the task done again when due? | A defined daily or weekly task window. |
| Scheduled occasion | Was the app used around the next known event? | A window anchored to that event, where observable. |
| Irregular need | Did another need arise, and was the app used then? | A time-based window with the unknown opportunity stated. |
These are analysis choices, not industry benchmarks.
Separate quiet time from lost users
No recorded event can mean that no need arose, the person used another route, the app was unavailable or an attempted task failed. App logs may not distinguish those cases. Avoid treating every quiet day as abandonment.
Where the next opportunity is observable, compare people who had one. For example, among people with another relevant appointment, assess how many used the app to manage it within a defined window. Report people with no recorded next appointment separately. Where opportunity is not reliably observable, use a time-based cohort and state that limit.
Check eligibility. If a service works only in part of Australia, define the served area and relevant task conditions. Installation in Australia alone does not show that someone had an opportunity to return.
Key Metrics for Measuring Occasional App Use
- Eligible Users with Next OpportunityUsers who had a relevant appointment or event within the observation window.
- App Used During WindowNumber of users who engaged with the app during the defined return period.
- No Recorded Next UseUsers with no activity despite having an opportunity.
- Installation in AustraliaNot sufficient for eligibility—must also have access to service area and relevant task conditions.
Choose and interpret the window
Choose the action and window from the expected job before inspecting the result. Keep them stable across comparable cohorts and wait until their observation periods finish. A longer window can reveal occasional reuse but delays a finished comparison.
Dashboard periods may answer another question. Check the configuration and calculation before calling a cell “seven-day retention”.
Apple’s App Store Connect retention view records later opens among active devices that installed and opened the app; installers who never open do not qualify. As an analytical limitation, this measure alone cannot establish whether another need arose.
Show the chosen action, eligible group, window and both counts. Compare groups with similar opportunities and complete observation periods. A lower frequency should prompt a check of the next need and the route back to the task. The decision might be to improve access to saved work, change the measurement window or leave a successful occasional experience alone.
