The opening hours of a release create plenty of movement but not always much certainty. Start with operational safety: crash-free sessions, failed requests, startup time and the health of flows that are central to the changed experience.
Read every movement against exposure. A modest incident affecting nearly every updated user may matter more than a dramatic anomaly inside a tiny cohort. Compare like with like by platform, app version, geography and acquisition source.
By the third day, revisit behavioural measures. Adoption and completion begin to carry more weight once enough eligible users have encountered the change. Record what you know, what remains uncertain and the next threshold that would alter the decision.
Need a clear view of a live release? Tell us what your team is deciding.