Give the draft the right lifetime
Jin moved draft retention beyond the individual screen, keeping text in memory for the current sign-in, account, and task. Returning to the task could restore the unfinished message.
A draft should survive a detour.
Preserving unfinished messages across mobile navigation.
An illustration of the work, not a product screenshot.
Follow the
whole problem.
An unsent message lived inside its task screen. Navigate to another task and the screen could unmount, taking the draft with it. Fixing that meant preserving the writing without letting it cross account or sign-in boundaries.
Test the boundaries
Regression coverage exercised the real composer through unmounting and reopening, clearing after send, account separation, and late writes from an old session.
Check the experience on a device
Native acceptance checks confirmed that navigating away and returning restored an editable draft. Review also consolidated the change onto the shared keyboard component.
The change merged with regression coverage and native acceptance evidence. Unsent text now survives task navigation within the same sign-in. This is in-memory retention; persistence across an app restart was outside the change.
01Small interactions deserve complete implementation.
02Preserving state includes deciding exactly when to clear it.
03Review can simplify the solution as well as correct it.