Journal
Quiet signals in onboarding drop-off
Teams often describe onboarding drop-off as a cliff. The chart agrees. The people do not fall; they wait. App Audience Intelligence, as we teach it, starts by naming the wait.
A permission dialog is not a conversion step. It is a social moment: the app asks for a kind of intimacy the store listing never mentioned. If your audience arrived from a supermarket partnership, they may treat camera access as a different request than someone who hunted you in a listing for “habit tracker”.
Empty states are the second quiet signal. Designers polish them as brand. Observers should ask who is empty on purpose — a shared household list with one active shopper — and who is empty because the import failed on a train with a patchy signal. Those are not the same audience, and a single “activation” metric will pretend they are.
The third signal is the uncoded pause: the three seconds while a webview loads terms, or while a bank-grade spinner thinks. Session replay shows thumbs hovering. Dashboards show a duration bucket. In Cohort Signal Studio we make people write the pause as a sentence with a cause they can actually see.
None of this tells you which button to move. It tells you which claims about “confused new users” you should stop repeating. Confusion is a mood. A denied permission is an event. We prefer events, then a careful inference, then a hope you keep off the slide.
The Pause module sits in the flagship studio if you want this work marked rather than merely read.