[grantheaslip]

I think what it comes down to is that as a developer, you've lost your way if you're creating a product you personally wouldn't want to use. Even if it were the case that the average user might not be that turned off by AIR (and I'm not convinced that's the case), if you've decided to base your product on a platform that's basically a deal-breaker if you're shopping around for apps (as AIR is for me), then I think you've set a really bad tone for your future enthusiasm for what you're making.

A frequent drum-beat on HN is having passion for what you create. Even if it saved me time in the short run and got me some degree of free platform support, I think having to work on an AIR app that I would probably never use in real life would probably doom the project in the long run.

When I think about the independent software projects that I love, it's obvious that the developers behind them love them as well. I (and I don't want to speak for everyone) can't see myself loving an AIR app.

[jarek]

I think what it comes down to is minimum viable product. Perhaps even budgeting. Maybe an assumption that since you don't like AIR, you can't see anyone else liking it.