Gallery
See what others have created
mammothfiver
@mammothfiver
Leaving
Design the leaving flow for a user who is exiting an active product context. This is not just a logout screen: it could be leaving a workspace, ending a subscription, abandoning an edit, or confirming account sign-out. The screen should make the action and its consequence explicit before the user commits.
Start with the current context and the thing being left. If there is anything at risk — unsaved changes, pending invites, active sessions, billing changes, or loss of access — surface that plainly in the confirmation step. Keep the language direct and specific, not vague reassurance.
Give the user a clear way back out, and make the destructive or final action visually secondary unless the consequence is truly irreversible. If the flow needs a final acknowledgement, thank-you, or handoff state after exit, keep it brief and functional: confirm what happened, then point to the next place they should go.
What to deliver
- Design the leave-confirmation screen for the current context.
- Show the consequence of leaving in plain language.
- Give the user a clear cancel path and a clear continue path.
- Include any required save/discard choice before exit.
- Add the post-exit state or farewell screen if the flow ends outside the product.
Think about crafting a memorable farewell with visuals that softly encourage the user to consider returning. A pleasant leave-taking can create positive last impressions.