What should I demonstrate before releasing a smart-glasses app?
Demonstrate the complete task on the intended hardware: input, processing, visible output, user action and recovery. Include denied permissions, background operation and interrupted connections where those conditions apply. A simulator or editor preview verifies a narrower part of the experience.
Show the difficult transitions
Many faults appear when a phone locks, a request finishes late or the glasses reconnect with old state. A release demonstration should show what the wearer sees and what the host actually records. Version information matters because firmware, app and SDK changes can alter the result.
We would keep a short evidence record naming the device, versions, conditions and observed outcome. That makes a successful demonstration useful to another person without implying that untested hardware or an all-day workflow has already passed.