Smart Glasses Glossary | AURAI | AURAI

AURAI Glossary

Smart Glasses Specs, Decoded

Every spec explained with AURAI's critical perspective. Learn how manufacturers measure each metric, how they game the numbers, and what really matters for your daily use.

153 terms

Brightness

brightness_nits

Display & OpticsUsed by 45 products

Display brightness in nits (cd/m2).

Why It Matters

Brightness specs in smart glasses are perhaps the most misleading of all display metrics. Problems include: (1) manufacturers report panel brightness before optical losses — a panel rated at 2,000 nits behind a waveguide with 40% optical efficiency delivers only ~800 nits to the eye; (2) "peak brightness" vs. "sustained brightness" vs. "typical brightness" are conflated — peak brightness may only be achievable in a small HDR highlight window or for a few seconds before thermal throttling; (3) nits measured at the panel do not account for ambient light washout — a 1,000-nit see-through display becomes nearly invisible in direct sunlight (~100,000 lux) because the human eye adapts to ambient brightness; (4) some manufacturers quote "perceived brightness" which is a subjective metric with no standard definition.

How It's Measured

Integer value in nits (cd/m2). AURAI stores the manufacturer's stated brightness figure, which typically represents peak panel brightness before optical losses. For accurate outdoor usability assessment, divide the stated value by 2–3x for birdbath optics or 3–5x for waveguide optics to estimate eye-level brightness.

In Practice

Under 500 nits (at-eye): indoor use only — display washes out near windows. 500–1,500 nits (at-eye): usable indoors and in shade, struggles in direct sunlight. 1,500–4,000 nits (at-eye): visible in most outdoor conditions except direct sunlight glare. Above 4,000 nits (at-eye): truly sunlight-readable, currently rare. For context, a 3,000-nit panel behind a typical waveguide (35% efficiency) delivers roughly 1,050 nits to the eye — adequate for overcast outdoor use but not sunny conditions. Most consumer AR glasses in 2026 deliver 400–1,200 nits at-eye in practice.

Deep dive →

Diopter Adjustment

diopter_adjustment

Display & OpticsUsed by 1000 products

Built-in vision correction adjustment.

Why It Matters

This is a significant usability factor that manufacturers often bury in footnotes. Without diopter adjustment, users who wear prescription glasses must either: (a) wear the smart glasses over their existing glasses (uncomfortable, often impossible due to fit), (b) purchase custom prescription lens inserts ($75–$200 additional cost and 1–3 week wait), or (c) wear contact lenses. Manufacturers market "prescription compatible" which may only mean option (b) exists as a third-party accessory, not that the device has built-in correction. The distinction matters enormously for the ~65% of adults who need vision correction. Some devices offer adjustable diopter dials (typically -5.0D to +3.0D range) while others have fixed focal distances that work for some prescriptions but not others.

How It's Measured

Boolean. TRUE if the product has any form of built-in, user-adjustable diopter correction (mechanical dial, slider, or electronic). Separate prescription insert accessories do NOT qualify — those are tracked via the prescription_lens_option field. The specific diopter range is stored in diopter_adjustment_range.

The same manufacturer inflation tactics apply as with horizontal resolution. Additionally, some products have non-standard aspect ratios (e.g., 16:9 panel in a 16:5 visible window) where the panel resolution exceeds the optically usable resolution — the edges are physically clipped by the optics. Vertical resolution is particularly important for text-heavy AR use cases like teleprompting and notification overlays, where vertical pixel density determines how many readable lines fit in the display.

How It's Measured

Integer value representing vertical pixels for a single eye. Should reflect the optically usable vertical resolution, not just the panel spec, though in practice most sources report panel resolution.

In Practice

For wearable displays primarily used as virtual screens (movie watching, desktop mirroring), a vertical resolution of at least 1080 pixels is the practical minimum for comfortable extended use. Below 720 vertical pixels, text rendering quality drops noticeably. Notification-only AR overlays (e.g., INMO Air, Focals by North) may use as few as 480 vertical pixels, which is adequate for short text snippets but unsuitable for productivity.

Deep dive →

Resolution per Eye (Width)

resolution_per_eye_w

Display & OpticsUsed by 46 products

Horizontal resolution per eye in pixels.

Why It Matters

Manufacturers exploit resolution reporting in three primary ways. First, binocular products sometimes report combined (both-eye) resolution — a "3840x1080" spec might actually be 1920x1080 per eye. Second, panel resolution does not equal perceived resolution: optical losses, especially in waveguide systems, can degrade effective resolution by 20–40%, making a 1920-pixel panel look closer to 1200 pixels in practice. Third, resolution is meaningless without FOV context — 1920 pixels spread across 46 degrees is sharp (42 PPD), but the same resolution across 90 degrees is noticeably pixelated (21 PPD). Always compute pixels-per-degree (PPD) for meaningful comparison.

How It's Measured

Integer value representing horizontal pixels for a single eye. Sourced from panel manufacturer datasheets where available, otherwise from product specs. For binocular products using a single wide panel (e.g., some VR-style viewers), this should be half the total horizontal resolution.

In Practice

Under 30 PPD (pixels per degree): visible screen-door effect and pixelation on text. 30–40 PPD: acceptable for video, readable large text. 40–60 PPD: sharp for most content, comfortable for extended reading. Above 60 PPD: retina-grade, indistinguishable from a high-quality monitor. Most consumer AR glasses in 2026 land in the 30–45 PPD range. For a typical 46-degree FOV display, 1920 horizontal pixels yields roughly 42 PPD — adequate but not exceptional.

Deep dive →

Supports 3d

supports_3d

Display & OpticsUsed by 1000 products

Google-powered captions often support 50+; on-device models fewer.

Captioning Mode

captioning_mode

Audio & Camera

Type of captioning support. Values: none | live_only | live_and_recorded | transcription

In Practice

XREAL Air 2 Ultra supports live captions; Envision Glasses do full transcription.

Deep dive →

Captioning Offline

captioning_offline

Audio & Camera

Whether captioning works without an internet connection.

Why It Matters

dB of noise attenuation.

In Practice

ANC earbuds achieve ~25-45 dB; clinical hearing aids vary by mode.

Deep dive →

Speaker Count

speaker_count

Audio & CameraUsed by 43 products

Number of individual speaker drivers.

Why It Matters

Most smart glasses ship with 2 speakers (one per temple arm), providing basic stereo. Some premium models include 4-6 drivers (typically a full-range driver plus a tweeter per side) for richer sound, but manufacturers sometimes inflate the count by listing passive radiators or bass ports as "speakers". A passive radiator is not an independently driven speaker — it improves bass response of an adjacent active driver but produces no sound on its own. A "4-speaker system" that is actually 2 active drivers + 2 passive radiators delivers noticeably less output than a true 4-driver system.

How It's Measured

Integer count of speaker drivers. Count only active, electrically driven transducers. Passive radiators, bass reflex ports, and resonance chambers should not be counted. When manufacturer specs are ambiguous (e.g., "quad speaker system"), verify through teardown data or review analysis whether all units are active drivers.

In Practice

1 speaker (mono): adequate for notifications and voice assistant responses; no spatial separation. 2 speakers (stereo): the baseline for music and media; provides basic left-right separation given the close proximity to ears. 4+ speakers (multi-driver): diminishing returns in the glasses form factor because the drivers are millimeters from the ear. The quality of DSP tuning and driver selection matters far more than raw count in this product category.

Speaker Type

speaker_type

Audio & CameraUsed by 81 products

Speaker technology: open-ear directional, bone conduction, in-ear, etc.

Why It Matters

Speaker type is the single most impactful audio spec for smart glasses, yet manufacturers frequently bury it or use vague terms like "premium audio" without specifying the underlying technology. The three main categories have radically different characteristics: (1) Open-ear directional speakers project sound toward the ear canal via small drivers on the temple arms — decent audio quality but audible to nearby people at moderate-to-high volumes. (2) Bone conduction transducers vibrate the skull to transmit sound — the ear canal stays completely open for situational awareness, but bass response is severely limited and audio leakage at high volume is significant. (3) In-ear/sealed speakers deliver the best audio fidelity but block ambient sound, defeating the purpose of see-through eyewear for many use cases. Some manufacturers claim "private listening" for open-ear designs, but independent tests show audio leakage is clearly audible to anyone within 1-2 meters at above 50% volume.

How It's Measured

Stored as free text. Normalize to standard categories: "open-ear directional", "bone conduction", "in-ear sealed", "hybrid" (combined approaches). If the manufacturer uses proprietary branding (e.g., Bose "Open Ear Audio"), note the underlying technology rather than the marketing name.

In Practice

Open-ear directional (most common in 2024-2025 smart glasses): good for phone calls, podcasts, and navigation prompts while maintaining awareness of traffic and conversation. Not suitable for noisy commutes or private listening in quiet offices — people nearby will hear your audio. Bone conduction: best for runners and cyclists who need maximum environmental awareness; worst for music enjoyment due to weak bass. In-ear sealed: best audio quality but feels redundant with smart glasses — users seeking sealed audio typically prefer dedicated earbuds.

Deep dive →

Telecoil Compatible

telecoil_compatible

Audio & CameraUsed by 826 products

Whether the device supports telecoil (T-coil) hearing loop systems.

Why It Matters

Required for ADA compliance in many public venues (theaters, airports).

In Practice

Most consumer smart glasses lack telecoil; hearing aid hybrids may include it.

Deep dive →

Video Resolution

video_resolution

Audio & CameraUsed by 37 products

Max video capture resolution and frame rate (e.g., "1080p@30fps").

Why It Matters

Manufacturers frequently headline their highest resolution without noting the frame rate cap or stabilization penalty. A device advertised as "4K video" may only shoot 4K at 15-24 fps (choppy, unsuitable for action), while usable 30 fps is only available at 1080p. Electronic image stabilization (EIS) often forces a resolution downgrade or crop — the stabilized output may be 1080p even if the unstabilized max is 4K. Some devices also impose recording time limits at higher resolutions due to thermal throttling, making the headline spec impractical for real use.

How It's Measured

Stored as a text string combining resolution and frame rate, e.g., "1080p@30fps", "4K@30fps", "720p@60fps". There is no universal standard for this field; manufacturers variously report "1080p", "FHD", "1920x1080", or "2K". Normalize to the "{resolution}@{fps}fps" pattern. If multiple modes exist, store the highest practical mode (the best resolution that sustains at least 30 fps with stabilization on).

Wired or wireless — determines latency, bandwidth, and freedom of movement.

Why It Matters

Manufacturers often list "Wireless" when the device supports Bluetooth audio but still requires a USB-C cable for display output. XREAL Air is "wired" for display but "wireless" for nothing — yet some listings conflate its Bluetooth audio support with wireless connectivity. Conversely, some devices advertised as "wireless" use Wi-Fi Direct for display streaming with noticeable latency (30-80ms) that makes them unsuitable for gaming. The distinction between data connection and display connection is critical and almost never clarified in spec sheets.

How It's Measured

Binary classification: Wired or Wireless, referring to the primary display/data link. Devices that use wired for display but wireless for audio/control are classified as Wired. Devices with optional wired and wireless modes may list both. USB-C with DisplayPort Alt Mode is the dominant wired standard; Miracast/Wi-Fi Direct is the dominant wireless display standard.

In Practice

Wired = zero perceptible latency, guaranteed bandwidth, but you are physically leashed to a device. USB-C cables degrade — expect to replace them annually with heavy use. Wireless = freedom of movement but 20-80ms added latency (fine for video, bad for gaming), potential compression artifacts, and additional battery drain on both ends. For AR overlay use cases, even 30ms of added latency causes visible misalignment with head movements. If gaming or precision work matters, insist on wired.

Deep dive →

Hearing Aid BT Protocols

hearing_aid_bt_protocols

Platform & ConnectivityUsed by 15 products

Recorded as the manufacturer-stated OS. AURAI editorially notes when a "proprietary" OS is a known Android fork. Version numbers are tracked separately when disclosed. Be skeptical of "Android-based" claims that don't specify the AOSP version — some ship Android 9 in 2026.

In Practice

visionOS = best polish, fewest apps, Apple lock-in. Android XR = growing ecosystem, fragmentation risk across OEMs. Meta Horizon OS = strong social/gaming library, Meta account required. Snap OS = excellent camera integration, tiny app ecosystem. Proprietary = expect exactly the features it ships with and nothing more. If the manufacturer goes under, a proprietary OS device becomes e-waste faster than an Android-based one.

Deep dive →

SDK Available

sdk_available

Platform & ConnectivityUsed by 38 products

Whether a public SDK exists for third-party app development.

Why It Matters

Differentiator for developer-facing products.

In Practice

Meta glasses with Spark AR SDK vs consumer-only frames.

Deep dive →

SDK URL

sdk_url

Platform & ConnectivityUsed by 5 products

URL to the official SDK or developer documentation.

In Practice

https://developers.meta.com/horizon for Ray-Ban Meta.

Deep dive →

Software Ecosystem

software_ecosystem

Platform & ConnectivityUsed by 50 products

How rich and alive is the app/software world around this device.

Why It Matters

This is the field manufacturers inflate most aggressively. "Thousands of apps" can mean thousands of flat Android phone apps that technically launch but are unusable on a head-mounted display. Meta Quest's library of 500+ purpose-built spatial apps is categorically different from a Rokid device claiming "Android app compatibility." Developer SDK availability, active third-party development, and app store curation quality matter more than raw app count. Watch for "coming soon" ecosystems that never arrive — multiple AR glasses have launched promising app stores that remained empty.

How It's Measured

AURAI editorial assessment, not a standardized metric. Factors include: number of purpose-built apps (not sideloaded phone apps), SDK public availability, active developer community size, app store update frequency, and notable third-party integrations. Stored as free text describing the ecosystem state.

In Practice

Interaction & AIUsed by 10 products

JSONB array of privacy feature name strings. Common values: "Recording LED", "Hardware Camera Shutter", "Physical Microphone Disconnect", "On-Device Processing", "End-to-End Encryption", "Guest Mode", "Auto-Delete Recordings", "Privacy Zone Geofencing", "Open Source Firmware". Features are recorded based on manufacturer documentation and teardown verification where available.

In Practice

The privacy features that actually matter for social acceptability: (1) Visible recording LED — must be bright enough to see in daylight from 3+ meters. Meta Ray-Ban Meta's LED is visible but small; Snap Spectacles' spinning LED ring was more obvious. (2) Hardware camera disable — a physical shutter or switch, not a software toggle that could be overridden. (3) On-device processing for sensitive data — biometric data, health metrics, and conversation audio should never leave the device without explicit consent. For enterprise use: data residency, GDPR compliance, and IT admin controls are non-negotiable. The sad reality: most smart glasses treat privacy features as a checkbox exercise rather than a core design principle. Buyers who care about privacy should prioritize devices with hardware-level controls over software promises.

Deep dive →

Sensors

sensors

Interaction & AIUsed by 43 products

In Practice

Most consumer smart glasses (Ray-Ban Meta, XREAL, Vuzix Z100) use right_temple. Apple Vision Pro uses none (eye+hand tracking only).

Tracking DoF

native_tracking_dof

Interaction & AIUsed by 5 products

How many axes of head/body movement the device can track — defines the AR experience tier.

Why It Matters

This is the clearest technical dividing line in the smart glasses market, and it is frequently misrepresented. 3-DoF (three degrees of freedom) tracks head rotation only: look left/right, up/down, tilt. 6-DoF (six degrees of freedom) adds translational tracking: lean forward/back, step left/right, stand/sit. The difference is profound — 3-DoF gives you a floating screen that rotates with your head, 6-DoF gives you objects anchored in physical space that you can walk around. Some manufacturers claim "6-DoF" when they have IMU-based 3-DoF with drift-prone visual-inertial odometry that loses tracking after minutes. True 6-DoF requires outward-facing cameras with SLAM (Simultaneous Localization and Mapping), not just an accelerometer and gyroscope.

How It's Measured

Integer: 0, 3, or 6. 0-DoF = no spatial tracking (audio-only glasses, basic displays). 3-DoF = rotational tracking only via IMU (accelerometer + gyroscope). 6-DoF = rotational + translational tracking via inside-out camera-based SLAM or external tracking systems. Some devices offer 3-DoF natively but can achieve limited 6-DoF with an external accessory or beacon system — these are recorded as 3.

In Practice

0-DoF: the device is a speaker, microphone, or dumb display with no spatial awareness. Fine for audio glasses and basic HUDs. 3-DoF: virtual content rotates with your head but doesn't stay anchored in space. Acceptable for watching movies (the screen follows you) but disorienting for AR overlays. Usable for seated media consumption. 6-DoF: virtual objects stay pinned to real-world locations. You can place a virtual monitor on your desk and it stays there as you move. Required for any meaningful AR experience, gaming with room-scale movement, or professional spatial computing. The jump from 3-DoF to 6-DoF is the single biggest experiential leap in the entire product category.

Voice Assistant

voice_assistant

Interaction & AIUsed by 33 products

Which voice AI you can talk to through the glasses.

Why It Matters

This field has become the primary battleground for smart glasses differentiation since 2024. But "supports Google Assistant" can mean the glasses have a dedicated on-device integration with wake-word detection, or it can mean "if your paired phone has Google Assistant, it passes through audio." The experience difference is night and day. Meta AI on Ray-Ban Meta is deeply integrated with visual context (the camera can see what you see). Alexa on Echo Frames is audio-only but highly responsive. ChatGPT on some devices is a web API call with 2-5 second response latency. The assistant name tells you the brand; you need editorial context to know the depth of integration.

How It's Measured

JSONB array of voice assistant names/brands. Includes both on-device integrations and passthrough/relay integrations without distinction in the data field. AURAI editorial notes indicate integration depth: "native" (dedicated on-device pipeline), "companion relay" (passes to phone), or "API" (cloud call with higher latency).

In Practice

Native integrations (Meta AI on Ray-Ban Meta, Siri on Apple Vision Pro) respond in under 1 second and can access device-specific features (camera, display, sensors). Companion relay integrations add 0.5-2 seconds of latency and cannot access glasses-specific hardware. API-based integrations (ChatGPT on various devices) add 2-5 seconds and require active internet. For real utility, what matters is: can the assistant (a) respond quickly enough for conversational use? (b) access the glasses' camera for visual questions? (c) work offline for basic commands? As of 2026, only Meta AI and Apple's Siri deliver all three on their respective platforms.

Deep dive →

Voice Assistant Integration Depth

voice_assistant_integration_depth

Interaction & AIUsed by 1 product

How deeply each voice assistant is integrated — native, phone relay, or API wrapper.

Why It Matters

The voice_assistant array tells you brand names; this field tells you whether those names deliver real value. Native integrations respond in under 1 second with full sensor context. Companion relay adds 0.5-2s latency and loses sensor context. API wrappers add 2-5s and provide a generic chatbot experience.

How It's Measured

JSONB object keyed by assistant name. Each entry: integration_level (native | companion_relay | api), has_visual_context (boolean), works_offline (boolean), wake_word (text), response_latency_tier (fast | medium | slow). NULL means unverified.

In Practice

Target Personas

target_personas

Commerce & ContextUsed by 1000 products

Intended user profiles (e.g., "The Executive," "The Creator," "The Athlete").

Why It Matters

Target personas are derived from a combination of manufacturer marketing and AURAI editorial analysis. Manufacturers tend to claim their product is "for everyone," which is never true. A $2,000 spatial computing headset is not for casual consumers regardless of how the ad shows a grandmother using it. AURAI assigns personas based on the realistic intersection of the device's capabilities, price point, form factor, and ecosystem requirements. We distinguish between who the manufacturer wants to sell to (aspirational marketing) and who will actually benefit from the product (practical reality). A device with no display but excellent audio is tagged for "The Podcast Listener" and "The Hands-Free Professional," not "The AR Developer."

How It's Measured

Stored as a JSONB array of string labels from a controlled vocabulary. Personas are assigned editorially, not algorithmically, though we use spec profiles to suggest initial assignments. Each product typically receives 2-4 persona tags. We avoid overly broad personas ("tech enthusiast") in favor of specific use-case-driven profiles.

In Practice

Use persona tags to quickly filter for devices that match your actual use case. If you are a cyclist who wants turn-by-turn navigation, filtering for "The Athlete" or "The Commuter" will surface relevant devices faster than reading through spec sheets. But remember that persona tags reflect our editorial judgment of the best fit — your specific needs may cross persona boundaries.

Use Cases

use_cases

Commerce & ContextUsed by 1000 products

Primary usage scenarios (e.g., "Teleprompting," "Navigation," "Translation").

Why It Matters

Use cases sit at the intersection of manufacturer intent and real-world capability. A product may be marketed for "Real-time Translation" but the translation feature requires a constant smartphone connection, a paid subscription, and only supports 5 languages — that is a very different "translation" device than one with onboard processing and 40 languages. AURAI assigns use cases based on what the product can credibly do today, not what the manufacturer roadmap promises. We are particularly skeptical of use cases that require software features not yet released or that depend on third-party app ecosystem development. If a use case requires asterisks and footnotes, we either do not list it or we add a qualifying note.

How It's Measured

Stored as a JSONB array of strings from a semi-controlled vocabulary. We distinguish between primary use cases (the product genuinely excels at this) and secondary use cases (it can technically do this but other products do it better). Only primary use cases are stored in this field. Editorial team validates use cases against hands-on testing, independent reviews, and user community feedback. Use cases are revisited when major firmware updates add or remove functionality.

In Practice

If your purchase decision hinges on a specific use case ("I need this for cycling navigation"), check whether that use case appears in this array. If it does not, the product likely was not designed with that scenario in mind, even if it could theoretically work. Products with fewer, more focused use cases often execute better than "Swiss Army knife" devices that claim to do everything.

Acoustic Measurement Standard

acoustic_measurement_standard

Identity & ClassificationUsed by 918 products

[Hearing Detail Specs] Norm under which acoustic values (OSPL90, FOG, EINL, frequency response) were measured.

Announced Date

announced_date

Identity & ClassificationUsed by 5 products

Date product was first publicly announced (distinct from release_date)

Battery Type

battery_type

Identity & ClassificationUsed by 1 product

[Hearing Detail Specs] Official manufacturer battery system or size: zinc_air_10, zinc_air_312, zinc_air_13, zinc_air_675, lithium_ion_rechargeable.

Brand Id

brand_id

Identity & ClassificationUsed by 1000 products

Links this product to its manufacturer in the brands table.

Certifications

certifications

Identity & ClassificationUsed by 1000 products

Regulatory certifications array, e.g. ["FCC", "CE", "RoHS"]

Computational Locus

computational_locus

Identity & ClassificationUsed by 61 products

Where the processing brain lives — on the glasses or somewhere else.

Why It Matters

This is the single most important architectural decision a manufacturer makes, yet it is routinely buried or obscured. "Standalone" and "all-in-one" are used interchangeably by marketing teams even when the device offloads heavy compute to a phone. Qualcomm AR1/AR2-based glasses that require a paired smartphone are sometimes marketed as "standalone" because they have an onboard chip — but that chip only handles sensor fusion, not application logic. Apple Vision Pro is genuinely onboard; XREAL Air 2 is genuinely tethered. Meta Ray-Ban Stories occupy a grey zone: onboard for audio, paired smartphone for AI features. Always check what happens when the companion device is absent.

How It's Measured

No ISO standard. AURAI classifies into four tiers: (1) Onboard/Integrated — runs apps independently (e.g., Apple Vision Pro, Meta Quest 3). (2) Dedicated Compute Unit — separate puck or belt pack (e.g., Magic Leap 2 Compute Pack). (3) Paired Smartphone — requires phone for app logic, glasses handle display/sensors (e.g., XREAL Air, RayNeo Air 2). (4) Tethered Host Device — wired to PC/console (e.g., Lenovo Legion Glasses). Some devices span multiple tiers depending on mode.

Generation numbering is straightforward in theory but manufacturers do not follow consistent rules. Some brands increment by 1 for each annual refresh (Gen 1, Gen 2, Gen 3). Others skip numbers for marketing impact (jumping from Gen 2 to Gen 5 to imply a larger leap). Some use decimal versions (1.5, 2.1) for mid-cycle refreshes, though AURAI stores only integer generations. The generation number appended to the product name (e.g., "ProductName (Gen 2)") helps distinguish products in the same family, but it is not a reliable indicator of how much the product has actually improved — a "Gen 3" might be a minor spec bump while a "Gen 2" from a competitor might be a ground-up redesign.

How It's Measured

Stored as a positive smallint. Null means the product is either the first (and only) generation or the manufacturer does not use generation numbering. The generation value feeds into the computed name column: when set, the display name becomes "Brand Model (Gen N)." We do not store sub-versions or decimal revisions.

In Practice

A higher generation number within the same product line generally means newer hardware, but do not assume Gen 3 is three times better than Gen 1. Check the actual spec differences. Sometimes a brand's Gen 1 product from last year outperforms a competitor's Gen 3 if the competitor has been making incremental updates to a weaker base design.

Has Audio Jack

has_audio_jack

Identity & ClassificationUsed by 1000 products

Whether device has a 3.5mm audio jack

Has Fall Detection

has_fall_detection

Identity & Classification

Algorithmic feature, not only a hardware sensor.

Has Haptics

has_haptics

Identity & ClassificationUsed by 1000 products

Whether device has haptic feedback

Has Tinnitus Masker

has_tinnitus_masker

Identity & ClassificationUsed by 1 product

Indicates if the hearing aid has a dedicated tinnitus masker or sound therapy feature.

Hearing Program Count

hearing_program_count

Identity & ClassificationUsed by 910 products

[Hearing Detail Specs] Number of selectable hearing programs, when stated.

Id

Identity & ClassificationUsed by 1000 products

Internal unique identifier for the product.

Ipd Max Mm

ipd_max_mm

Identity & ClassificationUsed by 7 products

Maximum interpupillary distance in mm

Ipd Min Mm

ipd_min_mm

Identity & ClassificationUsed by 7 products

Minimum interpupillary distance in mm

Is Cros Compatible

is_cros_compatible

Identity & Classification

Indicates if the device supports CROS/BiCROS configurations for single-sided deafness.

Last Capture At

last_capture_at

Identity & ClassificationUsed by 1 product

[FRA-47] Timestamp of the most recent capture run that touched this product.

Last Capture Source Type

last_capture_source_type

Identity & ClassificationUsed by 1 product

[FRA-47] Source kind of the most recent capture (paste, document_upload, url, openclaw).

Last Capture Source URL

last_capture_source_url

Identity & ClassificationUsed by 1 product

For glasses-form-factor: 130-138mm suits narrow faces, 138-148mm fits average faces, 148-155mm accommodates wider faces. If the frame width is more than 5mm narrower than your face width, expect temple pressure headaches. If more than 5mm wider, the glasses will feel loose and shift during head movement — catastrophic for display glasses that require precise optical alignment. For reference, most traditional adult eyewear frames are 135-145mm wide.