Early PCs were VERY expensive at the time.

I think you need to shake up paradigms a bit in order to get true value from these glasses. You genuinely need to start viewing scene understanding abilities, frontier AI model API calls, and seamless hand tracking as core primitives that you combine thoughtfully and not new tech that you chain together hoping to land on a use case.

Now, the ecosystem and the engine so far were designed for lower stake experiences but to make the purchase of this device worthwhile for average users, they will need Vision Pro app depth of thinking and attention to detail while fitting into the far tighter software and hardware constraints.

So the key for them is to lower the skill ceiling so creatives can tap into more of the juice, which is why they've announced an Unity to Lens Studio bridge and closed loop agentic coding, while making it more attractive for seasoned developers to use their engine and push its capabilities(native c++ sdk).

It takes quite a lot, but from what I've seen over a year developing on their kit and watching their platform evolve, their strategy has sound fundamentals. But they urgently need to tap into a broader and more diverse talent pool, like say Blender and Houdini artists, harware & robotics engineers, ML engineers, even music producers and sort of corral their attention into their platform long enough for truly novel and useful applications to emerge.

If you want both, you pay for both. If you only want movie watching, something like the XREALs will suit you better. If you want notifications in your face while your phone's in your pocket, and you want to watch that video while standing in line, then this is for you.

I think the biggest constraint so far has been on the computer vision side. With a better processor, the glasses should be able to run real time 6dof object tracking, lower latency hand tracking potentially with better occlusion, and ideally OS-level subtle intent recognition since current air pinch based UI interactions will not make it into mainstream. I'm curious though as to whether they've expanded the ONNX model compatibility. In my experience with the '24 dev kit, this was a serious blocking point in doing any serious custom CV work.

They've also announced a C++ native dev kit, as until now you could only use JS and TS withno node libraries. I think this specific update might have an outsized downstream impact on the ecosystem.

I think they're all trying to be a phone replacement, when I need them to be a smart watch replacement. Give me smart glasses and a ring that controls them. Give me simple, watch like actions, notifications, but keep them out of view.

It takes time for older paradigms to be plodded through. I think the community is still sort of dizzy / dazzled from the novelty of the medium, and perhaps to some extent kept back by VR thinking and object/static 3d model type thinking. As developers and users' Overton windows shifts, and they begin to think of these glasses as something totally normal and even quite boring, they might develop the orientation of mind necessary to hone in on use cases that properly _fit_ what this medium can offer.

It took me a year of confusion and throwing darts in the void before I finally began to see what this form of computing might represent. And that gain of clarity happened _thanks_ to deeply synergetic advancements in AI model capabilities and more recently with agentic coding which freed up the bandwidth to operate on higher level interaction and geometric primitives.

AR in isolation is nearly useless, but in conjunction with other domains and the environment it begins to make sense.

In my opinion, the ideal environment to nurture AR development looks a lot like Bret Victor's Seeing spaces. A lab, tools, devices, surfaces, combined with spontaneous, open-ended, and somewhat continual interaction and learning. https://worrydream.com/SeeingSpaces/