Reading a week of sessions without drowning
Thirty sessions, or three days of traces, is enough to test an inventory. More is usually repetition, not wisdom.
Read the noteShort pieces on in-app engagement: taps versus intention, first-open stories, event names that survive a quarter, onboarding drop-off, and reading a week of sessions.
These notes come out of reviews in Kuala Lumpur. They are not product announcements.
Thirty sessions, or three days of traces, is enough to test an inventory. More is usually repetition, not wisdom.
Read the noteA steep leave after onboarding is often a permissions sheet, a store login, or a second identity prompt — not a verdict on the product’s purpose.
Read the noteEvent names rot when they describe a mood. A naming session in KL rewrote a clinic stepper so next quarter’s hire would not guess.
Read the noteFirst-open tells you the app launched. It does not tell you whether anyone stayed with a task after the splash.
Read the noteIn-app engagement analytics goes wrong when every tap is treated as a decision. A grocery preview and a bag are different acts.
Read the note