Design for the person who just got interrupted
Real life has doorbells, bad connections, and half-finished tasks. Good interfaces leave a way back in.
The ideal user has a full battery, a stable connection, and twenty uninterrupted minutes. The person holding the phone might have none of those things.
They are comparing train times while walking to the station. They are halfway through an application when someone calls. They open a document, switch apps to find a detail, and return to a page that has forgotten everything.
Interruption is not an unusual edge case. It is a useful starting point for design.
Preserve the work, not just the page
Returning someone to the same URL is not enough if the form is empty and the filters have reset. What matters is the state of their task: what they entered, what they selected, and what remains unfinished.
A draft can make that state durable. It also needs an honest explanation of its limits. ‘Saved on this device’ means something different from ‘Saved to your account.’ Sensitive information needs deliberate storage choices, and a visible way to clear it.
Leave a recognizable place to resume
A long task benefits from a small recap. ‘You’ve added your details. Next: choose a time’ is easier to recover from than a screen full of fields with no indication of progress.
The same idea applies to reading. Keep the heading visible, preserve the reading position when appropriate, and let people jump between meaningful sections. Navigation should help someone rebuild context.
Make waiting safe to leave
If a photo export takes time, does the person have to watch it? Can they keep working? What happens if they close the tab?
The interface should answer those questions before they become expensive experiments. Show whether processing continues elsewhere or depends on the current page. Offer cancellation when it is possible. Do not imply background processing if leaving will stop the task.
Design a useful failure state
Picture a note that fails to sync. ‘Something went wrong’ leaves too much uncertainty. ‘Your note is saved on this device. Reconnect to sync it’ tells the person what is safe and what is pending—provided the product can actually guarantee that.
When nothing has been saved, say that clearly and preserve what can be recovered. A retry button is useful; a retry button beside the person’s intact work is better.
Try the interruption test
Start a task, leave halfway through, and return later. Switch devices if the product supports it. Try a slow connection. Navigate back after opening a detail page.
Look for the moments where you have to remember something the interface could have retained. Then decide which information should persist, for how long, and how the person can control it.
A good return experience does not demand an apology for leaving. It simply says: here is where you were, and here is how to continue.
