Hands-Free Smart Glasses for Industry. What the Term Should Mean, and What to Ask.

Start Here: Vocabulary First

When a Field Task Needs a Display and When Voice Is Enough gives a decision rule by error type, and QAI-06 vs QAR-06 compares the two published models. This paper sits before both: it defines what "hands-free" should cover in a specification, so the other two can be applied correctly.

Three Things Hidden in One Word

Hands. The worker can give input and receive guidance without putting a tool down. This is a voice requirement.

Eyes. The guidance reaches the worker without looking away from the job. A spoken instruction does this. So does a display in the line of sight. A phone held in the other hand does neither.

Evidence. The glasses can see what the worker sees, so something can check the work. This needs a camera.

Buyers searching for "assisted reality" or "pick-by-vision" glasses usually mean guidance that stays in the worker's line of sight without being a full overlay registered to the object. Both map onto the form factors below.

The Three Form Factors

QWR's HUMBL page presents three tiers, all running the same HUMBL voice AI: audio only, audio plus camera, and audio plus camera plus display. Published model-level specifications exist for two of them.

QAI-06 is the under-49g voice-native model, with multimodal context, real-time AI translation and vision-based object recognition. Its published use cases are barcode verification and hands-free inventory in manufacturing and logistics, step-by-step maintenance guides and remote expert guidance in aerospace MRO, clinical workflow assistance in healthcare and field operations in defence.

QAR-06 adds a binocular colour waveguide display: 76g, 640×480 per eye, a 30° field of view, a Qualcomm AR1 on Android, Wi-Fi 6, a 12MP camera, a 3-mic array and USB-C. Its published use cases are on-site BIM walk-throughs with clash overlays, assembly guidance with predictive-maintenance overlays, clinical AR and enterprise training.

No model-level specification is published on that page for the audio-only tier. Ask for one before you price it.

Which "Hands-Free" Does Each Job Need?

Map your tasks to the three requirements. A barcode and inventory check needs hands and evidence, so a camera and a voice. A maintenance sequence with an expert on the line needs hands and eyes, which voice delivers. A fastener position, a BIM clash or a work instruction on the line needs the guidance to sit on the object, which needs a display. If every task on your list is the first two kinds, you do not need to pay for the third.

What to Ask Any Vendor

Ask what exactly runs on the device and what needs a connection. QWR describes HUMBL as an on-device and cloud hybrid, with edge inference for latency-critical tasks and cloud for heavy reasoning, and a local cache for offline memory. That is narrower than "works offline". Ask where captured data goes. QWR states AWS Mumbai hosting and DPDP Act 2023 compliance, and secure boot on QAI-06. Ask for battery hours under your shift load: both models are described as built for all-day wear, but no runtime figure is published. For fleet controls and lockdown, see Kiosk Mode, Secure Boot & Remote MDM; for reading the numbers on a sheet, see Reading an AI-Glasses Spec Sheet.

The Hands-Free Checklist

Write down, for each role: the three or four tasks the glasses must support; for each, whether it needs hands, eyes or evidence; the lightest form factor that covers every task; the on-device and connected split; where captured data lives; battery hours under your load; and the model-level specifications for the exact tier you are buying.

The Conclusion

Hands-free is a starting point for a specification, not a feature. Decide whether you are buying free hands, free eyes or checked work, and the hardware choice follows from it.