Run the app’s live through-the-lens (TtL) preview on its GlassesApps listing, select your exact headset model and firmware, confirm live camera passthrough, readable text, latency and input methods in the preview, then verify device-specific release notes or ask for a recorded demo or in-store test if doubts remain.
Time needed about 90 minutes, spread over two sessions
- A live through-the-lens preview shows the app’s UI, brightness and occlusion as they appear inside the headset.
- Select the exact device model and firmware in the preview; small differences change passthrough, inputs and latency.
- Confirm live camera passthrough, readable text at arm’s length, acceptable latency, and the actual input methods shown.
- Corroborate the preview with device-specific release notes or support articles that name your model and firmware.
- Treat simulated camera feeds, companion-phone-only views or conflicting official docs as inconclusive.
- If you cannot confirm, request a recording made on your exact model and firmware or test the app in-store.
- A browser with access to GlassesApps and the app’s listing
- The exact headset model name you plan to buy (check the box or product page)
- If known, your target firmware or OS version to select in the preview
- A phone or laptop to compare a companion-phone UI if shown
- A short test script (20–30 seconds) to speak or read when testing latency
The steps
- Open the app listing on GlassesAppsGo to /apps, find the app you want, and open its listing so you can access the device selector, the preview control and linked documentation.You should see: You see the app page with a device selector, a run preview control and links to release notes or support articles.
- Select your exact device modelUse the device selector on the listing and choose the exact model name that matches the headset you plan to buy.You should see: The preview area updates to indicate the selected device model, usually showing the device name near the preview controls.
- Run the live through-the-lens previewClick the preview or run button and allow the preview to start; move your mouse or the preview window to check responsiveness.You should see: The preview shows the app UI layered over a camera feed that responds to motion or it labels the view clearly as 'simulated'.
- Cycle preview viewsSwitch between camera passthrough, HUD-only and companion-phone views in the preview controls to see how the app behaves in each mode.You should see: You can view at least two modes and see differences between in-headset passthrough, HUD-only and any companion-phone UI.
- Check text readability and placementUse preview controls or zoom to confirm subtitles, teleprompter text or UI elements are readable and not occluded by headset margins.You should see: Text is legible at typical viewing distances and important controls are within the visible field of view.
- Test latency and motion syncSpeak or move in the preview window and watch captions or teleprompter scroll for delay and alignment issues.You should see: Captions update closely in sync with speech and the teleprompter scroll follows without large jumps or variable lag.
- Confirm input methods shownLook for visible input controls in the preview (gesture hints, button labels, voice controls or companion-phone buttons) and verify they match how you plan to use the app.You should see: The preview indicates which inputs are available and where they appear (in-headset or via companion phone).
- Open linked release notes and support articlesFrom the listing, open the app’s release notes and device compatibility/support pages and search for your exact model and any firmware requirement.You should see: You find explicit mentions of your device model or a minimum firmware/OS version and notes about passthrough or microphone access.
Verify an app with through-the-lens preview
If you plan to buy Ray‑Ban Meta or XREAL Air 2 Ultra, run the app’s live through-the-lens preview on its GlassesApps listing, choose your exact model and firmware, and check live UI, camera passthrough, input methods and latency. The preview renders the app as it appears inside the selected headset.
Use the preview to confirm usable text size, where the UI sits relative to the frame, and whether the app relies on a companion phone or in-headset inputs.
- Run the TtL preview for the exact app listing and select your specific device model and firmware.
- Confirm live camera passthrough, readable text, visible recording indicators, and the input options shown.
How to run the live through-the-lens preview on an app listing
Open the app’s GlassesApps listing, pick your device from the selector, and click the preview or run control. The preview should either present a live AR view that responds to motion or display a clear simulated label. If it reacts when you move the preview window or cursor, the feed is live.
Run the preview from a laptop or phone so you can compare any companion-phone UI. Look for controls that let you cycle between passthrough, HUD-only and companion views.
- Use the device selector to pick the exact model name that matches your headset.
- Confirm the preview responds to motion and labels simulated views clearly.
What to check inside the through-the-lens preview
Check text size and contrast, field of view and occlusion, camera passthrough alignment and motion latency, and which inputs the app exposes. Readability and latency determine whether captions or a teleprompter are usable; inputs determine whether you can control the app as you intend.
Inspect each item one at a time inside the preview so you can tie a single observed problem to a specific fix or documentation search.
- Text: confirm subtitles or teleprompter text are legible at arm’s length using sliders or zoom.
- Field of view: ensure UI elements are not behind the frame or outside the visible area.
- Latency: speak or move and watch captions or scroll for sync delays.
- Inputs: verify the preview shows voice, gesture, device buttons or companion-phone controls as needed.
How to corroborate the preview with official proof
A live preview can be out of date or simulated; back it with the app’s release notes, a device-specific support article, or a compatibility list on the developer’s site. Proof is a documented mention of your exact model name and a firmware or OS threshold tied to the feature you need.
If documentation only uses platform-level terms like 'Android XR' without model names or firmware, treat the preview as provisional and seek stronger evidence.
- Look in release notes, the app’s compatibility page, and the device’s official app store listing.
- What counts: explicit model names, minimum firmware/OS versions, and notes about passthrough or microphone access.
- What does not count: marketing blurbs without model or firmware references.
- When docs conflict, the app’s device-specific support article or release notes should resolve the tie.
Device-specific checks: Ray‑Ban Meta and XREAL differences to watch
Ray‑Ban Meta and XREAL expose camera passthrough, companion-phone integration and inputs differently. Do not assume behavior transfers between them; select the exact model on the listing and confirm whether the preview uses an in-headset UI or a companion-phone UI before you buy.
If the preview defaults to a phone-only view, the app may rely on the phone for setup or controls and the in-headset experience may be limited.
- For Ray‑Ban Meta: confirm the preview shows full in-headset captions and passthrough or explicitly requires a companion phone: /devices/ray-ban-meta.
- For XREAL Air 2 Ultra: confirm passthrough alignment, HUD brightness and which inputs appear in the in-headset view: /devices/xreal-air-2-ultra.
Common red flags to stop you from trusting the preview
Treat simulated camera feeds, composited HUDs that do not respond to motion, companion-phone-only screenshots, or apps marked beta without device-specific notes as red flags. Any of these indicate the preview may not reflect the delivered in-headset experience.
If official support pages contradict the preview or demos come from another device model, require stronger proof before you buy.
- Simulated camera feed that ignores motion — do not trust passthrough claims.
- Only companion-phone screenshots — in-headset functionality may be incomplete.
- Beta or coming-soon labels without model-level release notes — functionality may be unstable.
- Conflicting official docs — ask the developer for device-specific clarification.
When the preview is inconclusive: how to get definitive proof
Ask the developer for a short unedited recording made on your exact model and firmware showing the feature you need. If the developer cannot provide that, test the app in-store or use a trial with a refundable purchase to validate the behavior yourself.
Be precise in your request: name the model, firmware and the exact scenario to demo so the developer can supply a useful clip.
- Request a recorded demo on your exact device model and firmware showing the feature in real use.
- Test in-store with a short script or use trial/refund policies and record your own test to prove the behaviour.
How this verification fails in practice, and why
Common failures come from selecting the wrong model in the preview, accepting a simulated feed as live, or missing companion-phone dependencies in the documentation. Small model-name differences and firmware requirements are easy to miss and produce false positives in previews.
Developers sometimes submit a single generic preview for multiple models; that saves them work and can leave you testing after purchase.
- Wrong model selected in the preview — you see a passing demo that does not match your device.
- Simulated preview accepted as live — you expect passthrough or low latency that the real device lacks.
What to do next, right now
Open the app’s GlassesApps listing, select your exact device model and firmware, and run the live through-the-lens preview. Confirm live camera passthrough, readable text, visible input options, and then open the linked release notes or support pages to confirm model and firmware support.
If anything is missing, request a recorded demo from the developer made on your exact device and firmware, or test the app in-store before you buy.
- Start at the app directory: /apps to find the listing.
- If captions matter, review our live captions guidance: /uses/live-captions and teleprompter listings: /uses/teleprompter.
Where this usually goes wrong
- Preview looks correct but the in-headset app lacks the feature after purchaseYou selected the wrong model or accepted a simulated preview; the developer provided a generic preview that does not match your firmware.Compare the listing model name to the device box, request a recorded demo on your firmware, or test in-store before accepting the device.
- Captions appear synced in the preview but lag heavily in the headsetThe preview used a higher-performing device or simulated low latency; your device or firmware has more processing delay.Check release notes for minimum firmware, update the headset, and ask the developer for a performance profile on your exact model.
- Preview shows camera passthrough but the real device shows a black or low-resolution feedThe preview was simulated or the app requires a firmware flag or permission not set on your headset.Check the device support article for required permissions, enable camera/mic access, and ask the developer for troubleshooting steps or a recorded demo.
- Essential controls exist only on the companion phone in the previewThe app implements critical interactions via the phone companion rather than in-headset.Confirm whether you can perform the task without the phone; if not acceptable, seek an alternative app that supports in-headset controls.
The checklist
- Open the app listing on GlassesApps
- Select your exact device model
- Run the live through-the-lens preview
- Cycle preview views
- Check text readability and placement
- Test latency and motion sync
- Confirm input methods shown
- Open linked release notes and support articles
Frequently asked questions
Can a through-the-lens preview guarantee an app will work on my headset?
No. A live TtL preview is strong evidence but not a guarantee. It can be out of date, simulated, or limited by preview defaults. Verify with device-specific release notes or request a recorded demo made on your exact model and firmware for a firmer confirmation.
What if the preview shows the app but I still worry about latency?
Test latency inside the preview by speaking or moving and watching captions or teleprompter scroll for sync. If the preview lacks a reliable test, ask the developer for a recording that demonstrates speech-to-caption latency on your exact model and firmware.
The app listing says 'compatible with Android XR' — is that enough?
Not usually. Platform-level statements are broad; compatibility should include specific model names or minimum firmware. If the listing only references Android XR, request model-level confirmation in release notes or support articles before trusting it for critical features.
What wording in official docs proves a feature works on my device?
Look for explicit device model names and a minimum firmware or OS version plus a note about the feature (for example, passthrough or low-latency captions). Generic marketing claims or screenshots without model labels do not prove support.
How should I ask a developer for a recorded demo?
Be precise: state your device model, firmware version, the exact feature to show (for example, 'real-time captions with microphone on and companion app closed'), and request a short unedited clip. A clear request yields a useful demo; vague requests yield generic clips.
Find apps that work on your glasses
Every app in the directory lists the glasses it runs on, how it works on each, and the official source that proves it.