[airstrike]

In my hallucination, my customer base is myself. If I had extra time right now and one of these devices to play with, I'd build something I wish existed, not something I expect the general population to buy.

If it's good enough for me, it's probably already worth my time—though https://xkcd.com/1319/ comes to mind

Then maybe some subset of the population that is closer in interests to me would also find it useful, in which case the app might get more traction. That'd be nice, but not a necessary requirement for my definition of success

The big issue here is justifying spending thousands of dollars on the product. I'd go for it at $500 or so. Definitely not $2k or $5k.

[latexr]

The developer in question makes a living selling Safari extensions, and the Vision Pro app they’re referring to is a version of what’s probably their most well-known. So we’re talking about an established developer with an established user base selling a version of an established app.

Your advice makes sense in general but doesn’t apply to this specific case.

[airstrike]

It still applies to this specific case. He's released a version of his existing app hoping others might use, instead of solving a problem he identified would be best tackled with a Vision Pro than with a desktop app.

All I'm saying is "don't build an app for the masses if the market is small. build something that solves a real need that you have personally identified"

[lapcat]

> He's released a version of his existing app hoping others might use

I released a version of my existing app because customers requested it. I had no independent interest in the platform.

> instead of solving a problem he identified would be best tackled with a Vision Pro than with a desktop app.

I can't think of any problems that would be best tackled with a Vision Pro than with a desktop app.

[wpm]

>I'd build something I wish existed

Then you also better hope Apple permits you to use the APIs you need to build it.