What's the alternative? Certainly multi platform native only makes sense at a certain scale. Your question might be too light on details to provide much advice.
If it's about making money or making a living, your best alternative is probably to make an app exclusively for the platform where most of your profitable customers are. You can expand to other platforms later if you get the scale.
Ask HN: Who has had a successful PWA product?
161–163 of 163 posts
Re: Ask HN: Who has had a successful PWA product?
#162Re: Ask HN: Who has had a successful PWA product?
#163Earlier quoted context omitted.
You talk a lot about what customers want, but they want apps only because Apple makes PWAs so unpleasant. There are some tech limitations (games might be tougher), but most of what makes PWAs suck is Apple. In another timeline, Apple chose to double-down on PWAs instead of the App Store after the iphone 1, and PWAs are the majority of non-performance-sensitive smartphone applications.
Every single “write once run everywhere” technology has sucked compared to native apps. Developers complained when the first iPhone came out and when Steve Jobs called web apps a “sweet solution”. Even Gruber called the solution a “shit sandwich”. If it’s only Apple holding PWAs back, then why do most of the same companies write Android apps instead of just producing PWAs that work on PCs and Android devices?
Google followed Apple's lead, so it's not like they have a choice.
And in case you haven't noticed, those same companies are happy to accept the performance hit of cross-phone libraries in order to not develop an app twice. If the PWA experience were better, they'd probably try that instead.
Most apps are boring, and don't require native performance.