How should I design an offline fallback for smart glasses?
Preserve useful local information, explain what is unavailable and avoid pretending that remote actions succeeded. The fallback should help the wearer continue or defer the task with a clear understanding of the state.
Decide which work can safely wait
Our recommendation is to separate reading saved content from executing a new action. A note can remain available locally. A message intended for a remote recipient needs a clear pending state until its delivery is established. Reconnection should not trigger surprising actions without the product's intended confirmation flow.
If a reply cannot be sent, retain the draft and show that it is unsent. Do not replace the failure with a success-looking checkmark because the draft was saved. The same principle applies to glasses commands: local acceptance and completion at the destination are different events.