Make leaving a task or account understandable, with explicit consequences and honest completion states.
Leaving can mean closing a draft, signing out, or requesting account deletion. Give each action a distinct name and explain its effect on the person's work. Do not treat these outcomes as interchangeable.
| Action | Information to establish |
|---|---|
| Leave an unfinished task | Whether the draft is saved, discarded, or recoverable |
| Sign out | Which session ends and what happens to local unsaved work |
| Delete an account | Which account and data are affected, what remains, and when the operation completes |
These are application policies and service operations. Liquidify does not define retention periods, deletion guarantees, authentication, or billing behavior. Keep an unspecified policy pending until its owner supplies the details.
Place account actions where people can find them and use explicit labels. “Delete account” should not lead only to deactivation. Describe any verified limitation before confirmation, including a delay or information that must remain.
Separate account deletion from any commercial cancellation process. If the product has such a process, its owner must document the relationship; do not assume one action performs both. Apple-specific account and purchase services are not browser features supplied by Liquidify.
Use Dialogs for a short consequential decision. Name the affected account or item, explain the consequence, and offer a safe cancellation path. A destructive role communicates intent; application code performs the operation.
An enabled Dialog action requests closure after its callback returns and does not await a promise. After confirmation, show execution progress and the confirmed result in an appropriate page context. If the operation fails, retain a meaningful status and recovery path instead of presenting deletion as complete.
After a completed exit, move to a route the person can still access and place focus appropriately. Do not leave focus on a removed control or a page that requires the ended session. Explain how to return if the action is reversible.
Test cancellation before confirmation, request failure, repeated activation, and delayed completion. Dismissing a view does not cancel an operation that has already started. Provide status or follow-up messages only through services the application actually implements.