Mobile Retention
Part of Mobile app retention
Defining meaningful app activity
Choose a later action that reflects useful app activity, specify who qualifies and check that its event records the intended result.
Meaningful app activity is a recorded action that provides credible evidence someone used an app for a purpose it serves. For retention, define the later activity from the user’s result, then specify what the event includes and misses. An open, screen view or tap can help diagnose a journey, but none automatically shows a useful outcome.
What meaningful app activity shows vs. what it doesn’t
- App or screen opened
- An interface was reached
- Action attempted
- Someone tried to progress
- Result recorded
- A specified state was reached
Start with the later benefit
Ask what the person can now do, know or rely on. In a hypothetical itinerary app, viewing a saved trip may be useful when its details load and are needed. Opening the home screen says less. In a booking app, a confirmed booking is stronger evidence than tapping “Book” and receiving an error.
A useful result need not always be a transaction or saved change. Reading a timely timetable may be the whole task. Different eligible tasks may need different activity definitions. This article concerns later use after an initial experience; choosing a new user’s first valuable action is a separate decision.
| Observation | What it shows | Remaining question |
|---|---|---|
| App or screen opened | An interface was reached | Did it provide the needed information? |
| Action attempted | Someone tried to progress | Did the action succeed? |
| Result recorded | A specified state was reached | Does it represent the intended benefit? |
Specify the activity
For each proposed later action, write down who could reasonably perform it, which state qualifies, when it counts, how repeats are counted and which other routes can provide the same benefit. A saved-itinerary view, for example, should require the relevant trip information to load. Consider what happens if the trip was deleted, the person used an offline copy or the information was obtained another way.
The specification should say whether one person can qualify more than once in a period and how activity across devices is identified. Keep a broader app-use measure beside the task measure where it helps reveal valid activity the task event misses. Label each measure by what it records.
Defining meaningful app activity: key steps
- Who can perform the action?Define user eligibility
- Which state qualifies?Specify completion criteria
- When does it count?Set timing rules (e.g., within session)
- How are repeats counted?Determine frequency limits
- Can other routes provide the same benefit?Include alternative paths
- Is cross-device activity identified?Use consistent identifiers (e.g., Firebase User ID)
Check the event against the result
Firebase Analytics automatically logs some events. Its SDK also defines recommended events, and an app can log additional event types when it needs to collect more data. None of those event names establishes task value by itself.
Before adopting a task event, compare the recorded event with successful, failed, repeated and interrupted paths on supported app versions. Firebase DebugView can show development-device events near real time during instrumentation checks. Seeing an event there does not prove complete production coverage. An event called “completed” should fire only when the defined result has occurred.
Revisit the definition when a product change creates another valid route or changes the completion state. Mark any reporting break instead of comparing old and new event meanings as though they were identical.
Validating a task event against real-world outcomes
- Review recorded event nameEnsure it reflects actual result, not just action
- Test across app versionsCheck consistency on supported platforms
- Use Firebase DebugViewVerify near real-time event logging during testing
- Confirm success conditionsEvent should fire only when defined result is achieved
- Revisit after product changesUpdate definition if new valid paths emerge
