When a mobile tab wakes up: restoring a clear SMS flow
A user switches to another app and returns minutes later to the code-waiting page. Its timer resumes where it stopped even though real time has passed. Test this transition separately in your SimAggregator client: the screen may have been suspended independently of the external order.
When the page returns, reconcile the local display with available state sources. A paused animation does not pause a deadline, and a lost connection does not automatically finish an order. If the current outcome is unknown, say so and show the last confirmed information.
Do not keep the only reference to ongoing work in a component's memory. Minimum recovery context should help locate the task without putting secrets in the address bar. Storage and lifetime choices belong to your application's architecture.
Lock the screen, switch apps, return after different intervals, and repeat after a page refresh. Use local fixtures when only the interface is under test. Success means the user understands what has already happened and does not start another purchase because an old screen is showing stale information.