Ten-minute Rokid Max 2 demo checklist for in-store testing

Time needed about 10 minutes in store plus 10 minutes prep

The steps

1. Announce your test planTell staff you have ten minutes, list the exact apps and tasks you will run, and request a unit not in a demo profile.You should see: Staff acknowledge the 10-minute test and open the unit in normal mode or explain demo limitations.
2. Fit the device and wear for 10 minutesPut on the Rokid Max 2, fit any prescription insert or your glasses, and keep it on while you run the first checks for at least ten continuous minutes.You should see: You feel no persistent pressure points and the unit remains stable for ten minutes.
3. Static text readabilityOpen a note or PDF and read two short lines from arm’s length, then repeat near a window with higher ambient light.You should see: Text remains readable at normal distance and is still legible near a bright window.
4. Alignment and field-of-view checkLook straight, then 30° left and right and up and down; watch whether virtual overlays stay anchored to the same physical spot.You should see: Overlays remain aligned with facial anchors without frequent readjustment.
5. Movement and hand-tracking testOpen an AR overlay or navigation app, make two quick head turns, walk two steps, and move your hand to interact with on-screen controls.You should see: Anchors stay put during head motion and hand gestures register on the first attempt.
6. Native app and provenance checkOpen each critical app (captions, translation, maps, teleprompter), ask staff whether it is native, streamed, or side‑loaded, and, if allowed, disconnect the phone briefly and re-run the app.You should see: Apps you need run locally or staff clearly demonstrate provenance; apps that close after phone disconnect were streamed.
7. Audio and voice testMake a short call or record a 15-second voice note, then speak a command to the assistant while background noise is present.You should see: Call partners rate clarity as acceptable and voice commands work within one or two attempts.
8. Privacy indicator checkAsk staff to show the device’s recording indicator and demonstrate the permission flow before recording audio or video.You should see: There is a visible LED or on-screen indicator and a clear permission prompt before recording starts.
9. Repeat failing tests on a second unitIf any test fails, request a fresh unit and repeat only the failing checks while recording the behaviour on your phone.You should see: If the second unit passes, the issue was unit-specific; if it fails again, the problem is systemic.
10. Capture proof and check onlineSave your recordings and notes, then check app listings in the GlassesApps directory and the Rokid Max 2 device page after you leave.You should see: You have video evidence of failures or passes and recorded app provenance to compare with online listings.

AI glasses demo checklist

Use a time-boxed ten-minute sequence for the Rokid Max 2 that gives you decisive pass/fail answers on five areas: display/readability, tracking/latency, native app provenance, audio/voice, and privacy indicators. Do the tasks in order and leave if two or more areas fail.

Tell staff up front you have ten minutes and the exact apps or tasks you will run. That prevents a polished marketing demo from masking real-world behaviour.

Pre-demo: what to bring and the short script

Book 15–20 minutes but plan to use ten for the checklist and a few minutes for follow-ups. Bring your phone with Bluetooth and Wi‑Fi enabled, account logins for apps you use, one short video file and one document or note, and any prescription insert or your glasses.

Tell staff you will run a fixed script, that you may request a second unit, and that you need to try the specific caption or translation app by name.

• Phone with Bluetooth/Wi‑Fi and the critical apps signed in where feasible.
• One short video file and one document or note ready to open.
• Prescription insert or your regular glasses if you use them.
• Book 15–20 minutes and say you’ll use 10 minutes for the structured test.

Display and optics: test readability, field-of-view and fit

Check display indoors and near a bright window, test small-text legibility and confirm how much of your peripheral field the virtual image occupies. Test optical alignment with your eyes or prescription insert; misalignment or blurred text at normal reading distance is a reject.

Run a static-text read, an ambient-light check, and an alignment check in that order to expose brightness or optical alignment problems.

• Static text: open a note or PDF and read two lines from arm’s length; text should be readable without leaning forward.
• Ambient light: stand near a window and under store lighting; the image must not wash out.
• Fit and alignment: with inserts or glasses on, look straight and 30° left/right; overlays should remain anchored to facial points.

Latency, tracking and AR alignment: movement tests

Run an interactive overlay or navigation app and perform head turns, walk a few steps, and try hand gestures. You are checking whether virtual objects stay anchored, hand tracking follows your fingers, and overlays do not lag or judder during motion.

A pass is when anchors remain visibly attached during head motion, the hand cursor follows with only slight smoothing, and gesture inputs register on the first clear attempt.

• Open a navigation or AR overlay and walk two steps left and right; anchors should stay put.
• Raise your hand and move fingers; the on-screen cursor should track with minimal delay.
• Make two quick head turns; overlays should not judder or reset position.

Core app compatibility and real use cases: verify native apps run

Open the exact apps you plan to use and confirm they run natively on the Rokid Max 2 rather than streamed from your phone. Ask staff whether each app is native, side‑loaded, or streamed and, if allowed, disconnect the phone briefly to confirm local operation.

For captions, translation, maps and virtual monitors, run practical tasks and verify the app continues to operate if the phone disconnects or that staff can clearly show the app’s provenance.

• Open the captions app and play a short clip; captions must appear synchronously. See live captions.
• Run a translation or speak a phrase to the assistant and read the translated text back.
• Open maps or a navigation overlay and follow a simple direction with small head motion. See navigation.
• Confirm app provenance in the store and verify listings in our Apps directory.

Audio, microphone and voice controls: noisy-store checks

Make a short call or record a 15-second voice note in the store's ambient noise and test the device’s speakers or earbuds. Speak commands to the assistant and check recognition under background noise. If speech pickup is poor for normal or soft speech, count that as a fail for captions or calls.

Ask the person on the call to rate clarity and listen to the recorded note; you must recognise your speech without shouting.

• Place or receive a short call and ask the other side to rate clarity.
• Record a voice note and play it back; you should recognise your speech.
• Try voice commands with low-level store noise; basic commands should work within one or two attempts.

Comfort, battery and privacy indicators: the 10-minute wear test

Wear the unit for at least ten minutes while running the other checks. Watch for pressure points, heat on the temples, and whether the device needs frequent readjustment. Discomfort within ten minutes usually persists in daily use.

Check battery state on the device UI before you start and ask staff to show the visible recording LED or a clear on-screen camera/mic indicator and the permission flow for recording.

• Wear for 10 continuous minutes while running tests; note any discomfort or hot spots.
• Confirm battery percentage on the device UI before you start.
• Ask staff to show the camera/mic indicator and the permission flow before recording.

Where demos commonly fail and why

Demos often hide problems by using preloaded high-contrast content, dimmed rooms, or a single adjusted unit. That polished experience masks streamed apps and brightness limits and gives a false impression of day-to-day performance.

Repeating key checks near a window and verifying app provenance exposes these common failures.

• Polished demo content masks native performance differences.
• Streamed apps hide CPU/GPU or wireless bottlenecks.
• Single-unit quirks are mistaken for product characteristics.

What to do if a test fails in the store

Ask to try a second unit and repeat the failing checks immediately. Record a short video of the failing behaviour on your phone and ask staff to reproduce it on their demo profile. If staff refuse to disconnect the phone, insist on a clear provenance statement for the app.

If privacy indicators are absent or staff refuse recording, note that as a negative privacy signal and consider walking away.

• Request a second unit and repeat the same sequence while recording.
• Record failing behaviour on your phone for later comparison.
• Ask staff to disconnect the phone to prove the app’s provenance where safe.

Next step: verify app support and documentation online

After the demo, check the apps you used against the GlassesApps directory and the Rokid Max 2 device page to confirm long-term availability and platform support. If an app worked in store but is not listed as native, assume it may be unstable or region-locked.

Use our Apps directory and the device page for Rokid Max 2 to confirm which apps are native and which require phone tethering. Compare live-captions behaviour with our live captions guidance.

• Compare store behaviour to app listings at Apps.
• Verify the device page at Rokid Max 2 for capability notes.
• Cross-check live-captions behaviour with our live captions guidance.

Where this usually goes wrong

• Text looks sharp in-store but washes out by a windowStaff used a dimmed room or high-contrast demo media that masks brightness limitsRepeat the ambient-light test near a real window and request the device at a real-world brightness setting.
• Virtual objects float or drift during head turnsPoor tracking calibration, demo-mode optimisation, or a unit hardware faultAsk staff to reset tracking, try a second unit, and record both attempts for comparison.
• App worked while tethered but closes when phone disconnectsThe app was streamed or dependent on phone processingConfirm app provenance with staff, check the app listing on Apps, and treat streamed-only apps as unreliable for standalone use.
• Voice assistant misses commands in normal speechMicrophone placement, noisy environment or weak speech-model integrationTest in a quieter spot, try speaking closer to the mic, and ask staff whether noise-cancelling or beam-forming is enabled.
• Store refuses recording or to disconnect the phoneStore policy or fear of breaking the demo flowInsist on recorded proof for failing behaviour or walk away; lack of transparency is a reasonable reason not to buy.

The checklist

• Announce your test plan
• Fit the device and wear for 10 minutes
• Static text readability
• Alignment and field-of-view check
• Movement and hand-tracking test
• Native app and provenance check
• Audio and voice test
• Privacy indicator check
• Repeat failing tests on a second unit
• Capture proof and check online

Frequently asked questions