| > It's virtually impossible to launch iOS-only today without enough funding that you can ride out the ensuing 1-2 years to also now build out and staff a web app Not every product needs a web app. If you absolutely need a web app, and it matters more than an iPhone app then build a web app first. > The old Mac indies have brand names and a benefit of a smoother transition since they were there before the App Store. The only real Mac app I've ever shipped came four years after the App Store. If you're going to call out my privilege, I need you to get the details right. > didn't Apple have Halide on the Apple Store phones at some point? Yes, after it had gained traction. The pre-install was an amusing distraction that made zero impact on downloads. > It's very, very, very, hard to get to market, get attention, and get to a competitive wage in the US, just on UX and an iOS app, even with a year or two of patience. That is a universal problem with building anything, whether it's a native app, web app, or protein shake. However, I'll argue tons more ways to build traction in native apps than web apps, on both a technical and marketing level. |
In the stronger tone you've consistently led me to believe you appreciate: I have absolutely no idea what your first mac app being in 2011 has anything to do with what I said, that you might have a slightly skewed perspective on the ability to build a sustainable product on just iOS. I guess that's your way of saying you didn't think you were even getting started / well-known until 13 years ago.
Take it for what it is: someone who benefited greatly from your and a select few others is saying you seem bizarrely myopic when you handwave about "normal people" and "as a consumer". "Prototyping in SwiftUI" made me absolutely cringe. Please try a modern web dev flow, Flutter, probably React Native. Then bizarrely combative coupled with "well if you need web build web" -- oh okay! Good to know an iOS app is enough and rest is irrelevant, unless it isn't.