What breaks when a glasses prototype becomes an everyday app?
Sleep, interrupted connections, canceled requests and updates expose behavior a successful desk demo may never exercise. The app needs to recover its state rather than assuming every interaction begins with a fresh launch and a nearby device.
Old work should not return as new information
Imagine starting a request, leaving range and reconnecting after choosing another task. The old response may still arrive. Our recommendation is to tie responses to request IDs and expire work that no longer belongs on screen. Reconnection should restore the current interaction, not replay an unbounded history.
Record a short recovery sequence: start a request, interrupt the host connection, return and issue a new request. The useful result is an understandable current screen with no duplicate action. This is a proposed acceptance scenario, not evidence that a particular SDK already implements it.