Retention is not a universal metric waiting to be selected from a menu. A finance app, a travel app, and a workplace tool can all create value at very different intervals. The definition must follow the product’s natural rhythm.
Define meaningful return
Opening the app may be too weak. Identify the repeated action that signals value: completing a transfer, planning a trip, reviewing a task, or another core behaviour. Keep passive activity separate from purposeful use.
Match the window to the use case
Calendar-day retention is useful for frequent behaviours, while rolling or bracketed retention can better represent less frequent needs. Examine several windows before choosing the view that guides product work.
Look for different journeys
Aggregate curves can hide meaningful differences between acquisition sources, first-use paths, customer types, and app versions. Segment only where context suggests a mechanism; avoid slicing until chance patterns appear.
Every app has its own cadence, user intent, and technical constraints. Apply these ideas as a starting framework, then test the definitions against your product context.