| "The average Joe barely even comes close to using the internet to its fullest potential. What makes you think something as complex and convoluted as AR (not to mention expensive) will be any different?" I think that AR will become as ubiquitous as our phones because all of the core functionality on a phone will be better on AR. Instant alerts in my peripheral vision (again a non-obtrusive display is crucial)? Call up directions while driving with cortana / siri and have lay over unobtrusively? Watch TV on a 100" screen anywhere? All things that I've done / played with in Hololens demos, all amazing, all "no question" will be massively adopted when they get the form factor correct. Heck just look at a current app like SNAP - already on 50%+ of phones of 18-24 year olds - is a perfect app use case. Camera, stories, sharing - all better and more accessible in AR. And they're already demonstrating the desire / utility of AR via "filters" and their new "World Lenses" release today. Want that bunny rabbit filter on all day as your "look"? Done. Want it only accessible to your co-workers and not your boss, cool set it and forget it as long as the device knows your social graph. |
That's a lot of functionality, and there is a market for this functionality, however this market isn't the mass market.
Like computers, phones are also barely used to their full capacity. There is a quote about how we have the most powerful tools and the largest repository of information all at our fingertips, yet we concede to our whims and spend it on frivolities (see: usage of social media and mobile games vs. non-entertainment apps).
The regular consumer does not give a shit about any of this supposed functionality of AR. You can tell them "oh it'll have this, and instant alerts will be unobtrusive, and the UI, it'll be optiimized to hell and back!" But, these are weightless promises. Consumer phones haven't even gotten to the point of seamlessness and great UX (though Apple is coming close).
Snapchat is simple, AR is most definitely not.
This is an adoption problem. You can't keep throwing features at it and believe the problem will fix itself.