So, there are only a few apps for the headset at the moment and they are all first party. Apple needs developers to make apps for the headset before they start selling it in mass.
If they do not have apps for it, then people will see a “dead” ecosystem and possibly view it as a failed product.
They priced it at a point where consumers won’t really get it, but devs will. At least larger devs will. Selling it, shows the devs that it’s ready for the market and encourages them to get in early so they can possibly catch the wave of new users.
Once there are a decent amount and variety of apps for the headset, they will sell a slightly trimmed down version for significantly less.
What do you think?
You must log in or # to comment.
I think that’s been pretty obvious form the start. It was clearly priced at a premium upon being announced, and their initial production was cut from ~1mil units to just south of 400k. They know they won’t have many buyers for this first gen product and are pricing/producing as such.
I have some coding experience, and a formal education in software development. There’s little chance of me actually making something, but I want to buy it anyways.
Oh so do I. But not for $3500.
The optimist in me says I can play with it and find a cool use cas, and be one of the first to develop something for it, and make lots of money… or at least cover the device cost.
I would sooner use Meta’s solution for a virtual office, for a fraction of the price, but I won’t buy a Meta headset haha. I’ll definitely consider the later versions of Vision Pro assuming the price falls to closer-to-Index pricing.
I think the whole point of having the headset priced in this range was to make sure that the experience really is very good. I’m sure thet they could’ve made this juuuust a little worse and therefore a bit cheaper (e.g., leave out the eye display to the outside, use one or two cameras less etc).
But then, everyone using it would probably be like “meh, this is nothing special, maybe AR isn’t there yet” and abandon the idea. I think the first impression really matters here.
In the end, it’s a feedback loop: If noone develops apps for this, there are no apps and nobody wants to use it. If nobody uses it, nobody wants to develop for it.
Agreed! I think there’s also genuine uncertainty about what uses will be popular, much like the early Apple Watch iterations involved some amount of flailing to figure out what works.
The spare-no-expense approach can be seen as an effort to not close off avenues of exploration before they know what works. When optimizing for cost, decisions will be made to save money at the expense of ruling out some potential appeal, but right now nobody knows what will have appeal. The EyeSight feature seems like a prime example of something that very few would include in a product today because the appeal is uncertain while the cost is high. It might turn out to be a home run of a feature, and this luxury version of the Apple Vision product is how they can gain experience with it. If the response is instead that it looks like googly eyes, makes people uncomfortable, or doesn’t achieve the goal of letting people use Vision while in the presence of others, then maybe it would find itself on the chopping block to get costs down.
