Most onboarding is designed for the first time someone uses your product. Almost no onboarding is designed for the second time. This is strange, because the second time is when the user actually decides whether you stay on their phone.
The paradox
The first time a user opens your product, they have infinite patience and zero context. They will read the welcome modal. They will follow the tutorial. They will accept your defaults. They are, in this moment, a tourist — and tourists are remarkably forgiving.
The second time, three days later, all of that has flipped. They have zero patience and full context. They remember roughly where the thing they want is, but not exactly. They are not going to read anything. They are going to tap, fail, and put the phone down.
This is the encounter that determines whether they have a third time.
What this implies
A surprising amount of good product design is designing for the second-time user, not the first. Specifically:
- The first time, show them where the thing is.
- The second time, put the thing where they last looked.
These are not the same place. The first one is the most-prominent slot. The second one is the most-recently-touched slot. If your product can only optimize one, optimize the second one.
The first session sells the product. The second session sells the third session, and that is the session that actually matters.
A practical pattern
I now build "second-time" navigation into apps from day one. The home screen of any feature shows, prominently, the thing you did most recently, not the thing the marketing team wants you to do.
It feels weird. It looks empty for new users. But by week two of usage, every user feels like the app has learned them — even though it's mostly just remembering one variable.
Most users can't tell the difference between "this app understands me" and "this app remembered the last thing I did." Honestly, neither can I.