Check the device OS (Android/Android XR or VisionOS) and the vendor’s published developer or sideload instructions. If those are missing, treat the unit as vendor‑locked. Insist on a live demo: enable developer mode and show an ADB pairing or an APK or store install on the exact unit you will buy.
Time needed about 90 minutes, spread across online checks and a short in‑store demo
- No published developer or sideload documentation means treat the device as vendor‑locked.
- A live demo that enables developer mode and performs an APK or store install on the exact unit is decisive proof.
- Public developer docs and a developer portal are verifiable evidence; marketing claims are not.
- Region locks, enterprise MDM and custom firmware can block installs even on capable hardware.
- If a device is locked, choose a model with a documented developer path or use vendor apps and phone companions.
- A phone or laptop with a browser and the headset’s product page or listing
- A USB cable compatible with the headset and a laptop with ADB installed if you can run a terminal
- A clear list of the specific apps you must run, with package names if known
- Contact details for the seller and permission to request a live device demo or screenshots
- Access to our apps directory to check app compatibility after verifying the device is open
The steps
- Confirm the advertised OS and developer docsAsk the seller what OS the device runs and for a link to the vendor’s developer or sideload documentation.You should see: You receive a URL or a document that shows steps for enabling developer mode, sideloading, or using a store.
- Request an About/Settings screenshotAsk for a screenshot of the headset’s About or Settings page that shows the OS identifier and build string.You should see: The screenshot clearly shows an OS name such as Android, Android XR or VisionOS, or a vendor firmware string you can research.
- Show Developer options on deviceRequest the seller open Settings on the headset and display Developer options or equivalent on the device screen.You should see: Developer options appear on screen with items like USB debugging or pairing prompts visible.
- Perform an ADB pairing or show a terminalAsk the seller to connect the headset to a laptop and show the terminal running 'adb devices' or the pairing prompt on the headset.You should see: The terminal lists the device as 'device' or shows a live pairing interaction on the headset.
- Run an APK install demonstrationRequest the seller install a simple APK (your app or a known test APK) onto the headset while you watch.You should see: The installer or terminal shows an 'adb install' returning 'Success' or the App Store shows an Install button that completes and launches the app.
- Launch the app and test persistenceOpen the installed app, use its basic features, then reboot the headset and reopen the app.You should see: The app launches and functions; after reboot it remains installed and launches again.
- Get written confirmation of limitationsAsk the seller to provide written notes about any restrictions, MDM, or required accounts that affect installs.You should see: You receive a clear statement of any enterprise management, region locks, or account requirements.
- Cross‑check the app on GlassesAppsAfter the demo, search our apps directory and the relevant device page to confirm compatibility and community reports.You should see: You find matching compatibility notes or install reports for the app and device.
Check if glasses allow third-party apps
Treat any headset without published developer or sideload documentation as vendor‑locked. Ask the seller to show developer options, an ADB connection, or a live app install on the exact unit. If the vendor documents a developer path for Android/Android XR or VisionOS, you can verify the steps yourself.
- Either public developer docs and tools exist, or there is no verified install path.
- Acceptable proof: Developer options visible, ADB pairing on screen, or a completed APK/store install.
What technical signal actually matters
The key signal is the OS plus a documented app distribution path. Android and Android XR provide developer options, USB debugging and APK packaging; VisionOS shows an App Store and developer workflows. If the vendor publishes these concrete steps you can follow, request to verify them; marketing claims are not proof.
- Android/Android XR: developer options, USB debugging and ADB install instructions.
- VisionOS: App Store listing and developer account guidance.
- Proprietary firmware: require explicit sideload docs; absence is a red flag.
A step‑by‑step pre‑purchase checklist you can use right now
Use this checklist when messaging a seller or visiting a store. Demand screenshots first and a live demo if possible. Each item below is a verifiable claim you can match to a screen, terminal output, or a file on the exact unit you intend to buy.
- Ask which OS the device runs and where the vendor documents a developer/sideload path.
- Request a screenshot of Settings showing Developer options or equivalent.
- Ask for a screenshot or video of an ADB session listing the device, or a live 'adb install' returning success.
- If the vendor advertises Play Store or another store, ask for a live install from that store onto the headset.
- If buying online, check the vendor’s terms and developer portal for sideload instructions and changelogs.
How to verify from public sources before you visit
Check vendor developer docs, an official app store listing, and independent install reports or videos. These public sources let you rule out locked firmware before you schedule a demo. Use our apps directory and community threads to confirm inconsistent or missing documentation.
- Check the vendor’s developer portal for step‑by‑step sideload or SDK instructions.
- Look up the vendor’s app store listing to confirm third‑party availability.
- Search forums, walkthrough videos and our apps directory for install reports.
Brand‑specific notes and red flags to watch for
Some vendors ship Android but lock the bootloader, hide ADB, or limit installs by policy. Region or enterprise firmware can block installs even when hardware supports them. Research the vendor’s history and community reports before you commit to a purchase.
- Product pages that advertise 'app store only' or a closed ecosystem without developer docs are a red flag.
- If a seller claims sideloading is possible but cannot show the developer menu or a live install, treat that as suspect.
- Check community threads for reported firmware locks on devices like the Even Realities G1 or other models listed under Android XR.
What you can and should not do if the device is locked
Do not attempt to bypass vendor locks or jailbreak a device before understanding warranty and legal consequences. That can void warranty and may be illegal. Choose a model with an open app platform or rely on the vendor’s supported apps and companion phone features as a safe alternative.
- Safe alternatives: pick a model with documented Android/Android XR or VisionOS support, or use the vendor’s supported apps.
- If you need one app, ask the vendor to add it or provide an enterprise install path rather than attempting a hack.
How to interpret the evidence the seller gives you
Screenshots and promises are weaker than interactive demos. Insist you perform a clear action: enable developer mode, see the ADB pairing prompt, run 'adb install' and see a success message. If the seller shows only photos or chat screenshots, treat that as insufficient.
- Good proof: you enable developer mode, you see the ADB pairing prompt on the headset, and an installer returns 'Success'.
- Weak proof: a screenshot sent in chat, a salesperson’s verbal claim, or a vague vendor FAQ.
What goes wrong in practice and why
The common failure is trusting verbal claims or stock photos. Buyers pay, then discover developer options are hidden, ADB never pairs, or installs fail. The buyer attempting the real install is usually the first to notice the problem.
- ADB shows 'unauthorized' because the headset did not show or accept the pairing prompt — ask the seller to show and accept the prompt.
- 'Install failed' because the vendor blocks unknown apps or enforces signature checks — demand a live demo of the exact app you need.
- App disappears after reboot due to MDM or provisioning scripts — request documentation of enterprise management policies.
Where to confirm app compatibility once the device is open
After you verify the device is open, confirm specific app compatibility. Search our apps directory and the device page for install reports. If an app requires Google Play services, check whether the headset has Play Store access or can run the app without those services.
- Compare the apps you need against device pages and community reports.
- If an app relies on Play services, confirm Play Store access or test the app without Play services during the demo.
What to do next
Take the checklist into the demo or paste it into messages to the seller. If the device fails any proof step, walk away or choose a model with a documented developer path. After a successful demo, verify your must‑have apps in our apps directory before completing the purchase.
- Request a live demo of developer mode and an APK install for the exact app you plan to use.
- From the demo you learn whether the device accepts installs, whether apps persist after reboot, and whether management policy blocks installation.
Where this usually goes wrong
- Seller shows only a screenshot and refuses a live demoScreenshots can be taken from another unit or faked; the seller may not reproduce the behavior on the unit you will receive.Refuse the purchase or demand an in‑person demo on the exact unit you will take home.
- ADB lists the device as 'unauthorized' or never appearsThe headset did not present or accept the ADB pairing prompt, or the vendor firmware blocks pairing.Ask the seller to show and accept the pairing prompt; if it never appears, treat the device as locked.
- An APK installs but disappears after rebootDevice is managed by MDM or a provisioning script removes unapproved apps at boot.Request written MDM policy details or choose a different device without management constraints.
- Installer returns an install failure without a clear errorVendor enforces signature checks, missing libraries, or blocks specific package names.Request the exact error message; if it indicates blocking, ask the vendor for an approved install path or a different model.
The checklist
- Confirm the advertised OS and developer docs
- Request an About/Settings screenshot
- Show Developer options on device
- Perform an ADB pairing or show a terminal
- Run an APK install demonstration
- Launch the app and test persistence
- Get written confirmation of limitations
- Cross‑check the app on GlassesApps
Frequently asked questions
Can I sideload APKs on Ray‑Ban Meta?
It depends on the specific model and its firmware. Check the Ray‑Ban Meta device page on GlassesApps for community reports and ask the seller for a live demo of developer mode or an APK install on the unit you will take home.
How do I tell if a headset is running Android XR or proprietary firmware?
Ask the seller for the exact OS string from Settings or a screenshot of the About page. If it shows Android/Android XR or a VisionOS build and the vendor provides developer docs, that signals an open path; a vendor name with no developer docs indicates proprietary firmware and requires proof of sideloading.
What if the seller says I can 'request an enterprise install'?
An enterprise install is not the same as unrestricted sideloading. It may require device registration, an MDM profile or a corporate account. Ask for the written process and a demo of the app installed under that process; treat it as a partial workaround unless it meets your needs.
Are videos enough proof that a device allows third‑party apps?
A recent, unedited video showing you performing the actions is stronger than a screenshot but still less reliable than a live demo. Videos can show another unit. The only irrefutable test is you performing a live install on the exact unit you will buy.
Where can I find apps known to work on open headsets?
Use our apps directory to search for apps and see device compatibility notes. After you confirm a device is open, cross‑check the app pages with the device page (for example Even Realities G1 or the Android XR page) for community install reports.
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.