Part of that is, in my eyes, that it is an apt comparison. Some of the things that ended up making a touch only interface work well on the iPhone (I used Window

Part of that is, in my eyes, that it is an apt comparison. Some of the things that ended up making a touch only interface work well on the iPhone (I used Windows Mobile 6.0 with only a touchscreen at the time, so I am speaking from experience) were, at least partly, things public analysts, even those steeped in the field, could not really predict by what had been showcased during the announcement. Predictive text being utilized to change the virtual size of touch targets on the keyboard, yet keeping the design static to improve accuracy, was something even those with years working with and on touch only smartphone interfaces did not figure out in its entirety until after the phone was in their hands. The iPhone is a good parallel because just like with it, this is trying to further an existing class of devices and history has shown that, for as many things as I can criticize about them, Apple is very good at adding these unnoticeable optimizations and hidden tricks that make experiences work much more flawlessly. Adding to that, though, I will admit that the first iPhone was severely flawed in other ways, like lack of MMS and 3G. These however were not issues with the UX (compared to Windows Mobile which supported these but had UX issues out of every orifice), but rather conscious feature restrictions, on which Apple ended up back paddling. In fact, that is my main concern with the AVP, Apple intentionally restricting it in ways that will make the hardware less appealing and impactful. The AVP, in my eyes, should in the long term replace both Macs and iOS devices (at least iPads), but to do that, should enable the creation of software on device. I hope that, just like with 3G and MMS, Apple will see the light between V1 and V2 regarding local macOS app support (or at least Xcode). If that happens, I will buy one at their asking price. As it stands, I will wait for reviews and only buy one if it means a distinct improvement to my workflow, even though I'll need to take my MacBook with me. Apple should, just like with Xcode on the iPad, stop being afraid of letting new classes of compute device replace the old. To bring this back to the original iPhone, imagine if Jobs had announced that it is not an iPod on top of being a browsing device and phone, because they feared cannibalizing iPod sales. Would have been shortsighted, to say the least. Lastly, I will freely admit that past performance should not be used to predict future successes. It is possible that Apples methods may have changed since then, and they have not put as much consideration into solving the UX issues plaguing current pass-through AR devices, in which case justifying the price will be (even more of) a challenge. I doubt it though and, even if, more recent history (Apple Watch) has taught them a thing or two about pivoting a seeming failure into an impressive success.