Experience principles
Define the user's task first, then assign responsibilities to the glasses, phone, and server. The following SDK integration design guidance should be used with examples and physical-device tests.
Start with these six priorities#
- 01 · Reading
Readable at a glance
Show the current result, object, and primary action on the glasses. Keep long forms, history, and detailed instructions on the phone.
- 02 · Control
Allow stop and exit
Make it clear how to end a task. On exit, stop subscriptions, animation, and capture, and release the current run's resources.
- 03 · Feedback
Respond to every action
Distinguish waiting, running, completion, and failure. While awaiting a glasses reply, explain that the state is being confirmed.
- 04 · Coordination
Show the same result on both sides
Track connection, application runtime, and business-task states separately. Avoid one side showing progress after the other has stopped.
- 05 · Recovery
Provide a next step after errors
Preserve input where possible and identify the unfinished action. Provide concrete steps such as reconnecting, authorizing again, or querying status.
- 06 · Validation
Check while wearing the glasses
Verify readability and responsiveness with the actual display, input, and Bluetooth link. Smooth simulator graphics do not represent physical-device performance.
Distribute a task across devices#
| User Needs | Suggested location | Example |
|---|---|---|
| Initial setup, accounts, long forms, and file selection | Mobile Web Page | Enter settings, choose a novel file, and send the current content to the glasses. |
| Immediate results, simple confirmations, and real-time game controls | Glasses GMP | Display text, move a paddle, and handle the primary button and head gestures. |
| Network requests, long-running tasks, and service credentials | Phone Web initiates requests; the developer's server handles business logic | Query weather, process audio, or call your own AI service, then return a result suited to the glasses display. |
| Packaging, QR distribution, installation, and runtime | Studio and MemoMind App | Use the existing workflow. Business pages should not implement the Bluetooth installation protocol themselves. |
Continue with the area you are designing#
Describe a complete scenario before coding#
- Write the user's goal, such as “Select text on the phone, display it on the glasses, and allow exit.”
- List the phone inputs, glasses results, and source of each confirmation.
- Write the actual user-facing message for loading, empty content, failure, and cancellation.
- Find an SDK example covering the capability. Verify its success path before adding your own page and business logic.
- Extend the same scenario with tests for disconnection, repeated clicks, backgrounding, and exit.