How should Spectacles apps handle permissions?
Connect each permission request to a feature the wearer understands. Follow Snap's documentation for the relevant resource and test both approval and denial. An optional permission should not silently become a requirement for unrelated parts of the app.
Ask at the moment the feature needs access
Our recommendation is to explain the operation in ordinary language before requesting its input. If access is denied, show what remains available and how to continue. Repeatedly presenting the same unexplained prompt rarely helps someone decide.
A feature that uses an input for one specific interaction can keep the rest of its interface usable when that input is unavailable. If the entire task depends on permission, say so clearly. The recovery state should be an understandable product screen, not an unexplained editor-style error.
Sources
Sources checked September 11, 2026. How we research these answers ↗