AR research sprints when hardware isn’t shipped
Shipping Phase-0 R&D against hardware you can’t hold. The Parley approach to Everysight Maverick AI before the device ships.
Unreleased hardware problem
Parley is building an AR-glasses product for real-time bidirectional transcription between deaf and hearing users. The canonical hardware target is Everysight Maverick AI. As of May 2026, the Maverick AI hasn’t shipped commercially. The public spec sheet is limited. You can’t hold the device and run your pipeline against it.
I think this is more common than people admit. Most serious AR teams work against hardware that’s either not shipped or not in their hands. The question isn’t “how do we wait?” It’s “what can we build now that will still be valid when the hardware ships?”
Parley’s Phase-0 approach: ship hardware-invariant research (ASR architecture benchmarking, signer-holdout methodology, failure taxonomy) while explicitly flagging hardware-dependent assumptions (on-device latency budget, HUD rendering pipeline, microphone placement) as unvalidated. The Phase-1 COMPLETE milestone as of April 26, Notebooks 00, 01, and 02 all shipped with top architecture landing at 0.4467 ± 0.0097 on signer-holdout, shows what’s possible before the device is in hand.
The signer-holdout gap, roughly 35 percentage points below the random-split Kaggle leaderboard, is the most important finding from Phase 1. It exposes the benchmark’s structural optimism. It’s hardware-invariant. The gap exists regardless of which AR glasses are eventually targeted. That kind of finding compounds. Hardware-dependent work comes later.
Can-do vs can’t-do
Partitioning is the first discipline. Before any sprint planning, every work item gets categorized as hardware-invariant or hardware-dependent.
| Category | Examples | Publication readiness |
|---|---|---|
| Hardware-invariant | ASR model accuracy on benchmark and holdout datasets; signer generalization methodology; failure taxonomy; architecture comparison; dataset curation approaches | Publish now — findings hold regardless of specific hardware |
| Hardware-inferred | Latency budget estimated from comparable glasses; rendering pipeline designed for inferred HUD spec; audio preprocessing designed for assumed microphone placement | Publish with explicit caveat — conclusions may change when hardware specs confirmed |
| Hardware-dependent | On-device inference timing; HUD-specific rendering optimization; real microphone placement effects on ASR; thermal throttling under sustained load | Flag for Phase 2+ — requires device in hand to measure |
Parley’s community publication standard is higher than for internal research, specifically because the Deaf community deserves accurate capability claims. The r/deaf subreddit is on explicit hold until a Deaf-community advisor has reviewed Phase-2 numbers. “Our Kaggle benchmark shows 95% accuracy” and “our product works 95% of the time for real conversations” are very different claims. The hardware assumptions register prevents the conflation.
The rest of Expert · Lesson 14 is for subscribers.
AR research sprints when hardware isn't shipped
- Every Expert-tier lesson — diagnostic prompts, transcripts, prompt kits, full homework
- Every research paper — methodology, figures, tables, reproducibility appendices
- New Expert lessons + papers as they ship (quarterly cadence)
- Foundations + Operating lessons stay free; bundles on GitHub stay free; this tier is the deep stuff
Free while the early catalog ships. Paid tier comes later — subscribe now and you’re grandfathered in.