The paths page lays out the four options. This page says how the three features actually get done, whether we buy the software or build it ourselves, and the plan to finish them for the October demo.
A pair of light glasses is best at sharing the view. A phone is best at translation and measurement. So the simple approach uses two devices. A headset can do all three in one unit, but it is bulkier. Both approaches appear in the four paths, and we plan for both.
The phone does the heavy work, and the result is shown back on the glass. This is the safe approach and our demo lean.
One device covers all three, and it is the only kind that can measure on its own. The trade is weight and comfort for a full shift, so we keep it as the all-in-one option.
Read a row to see how one feature gets done across the three paths. Greener means it is already proven, amber means it needs a short test first.
| Feature | Path 2 Industrial glass + phone |
Path 3 AR glass + phone |
Path 1 Headset (Quest 3) |
|---|
Each feature is its own track so they run in parallel. The hard part, gluing the two devices together, is its own track that can fall back to a phone screen if it slips.
Sharing the view, translating, and measuring each work on their own. The hard 90% is making the two devices act as one: a shared marker to anchor the measurement, a link between glass and phone, and a clean way to show the result. We keep this as a separate track, and if it slips we fall back to showing the result on the phone screen, so the demo never fails.
All three features are deliverable across the four paths. We buy the share on the industrial glasses or build it ourselves on the AR glasses and the headset, the phone or the headset handles translation and our own measurement, and the open items are the RayNeo camera test and the three-language audio in factory noise. See the four paths and the decision.