[Bluestrike2]

I think the issue is less the cost to developers and more the cost to users. Were there more users, no doubt a larger number of indie developers would be able to justify the expense. Without those users--or at least a reliable promise of those users in the near future--it's tough to justify even dipping your toes into it. It's a chicken and egg problem that's fundamentally tied to cost as well as hardware limitations. Discomfort from the bulk and weight was my biggest sticking point even before the price, for example.

Plus, the hardware is just the initial starting point. Your initial outlay will quickly be eclipsed by the dev hours spent working on Vision versions of your app(s), and that's when the opportunity costs become particularly noticeable. Time spent on a Vision app that may have no real market for years is time you could be spending adding features, testing changes, fixing bugs, marketing, etc. Skipping on Vision Pro is really a no-brainer for most indie developers, at least for the foreseeable future.

[throwanem]

Yes. That was my original point, just above the head of the branch where you responded. Could I have been more concise or more clear? Serious question, I am mildly retooling my prose style of late.

[Bluestrike2]

Ah, sorry about that. Any lack of clarity is on me; I had walked away for a bit before responding and ended up flattening the branch in my head by the time I started typing. You're fine :).