3 ms·
You're right with everything you say – from a developer perspective. I agree, most apps are indeed shit and that's why they have few users. I agree, you certain
by WA 9y ago
You're right with everything you say – from a developer perspective. I agree, most apps are indeed shit and that's why they have few users. I agree, you certainly can build beautiful apps with a smaller budget. I agree, most things don't need an app.
But, and this is a big BUT and the reason why hybrid is a good solution: Users demand apps. Your average user rather downloads an app for the local bus service or a museum than going to a mobile website, because experience taught them that mobile websites are shitty and some apps work offline, at least. Yes, both of us rather use a good mobile website, but average Joe doesn't.
The app experience might not be better, it might even be worse, but users are looking in the Stores for apps like that. The reality of the App Store is that there are a handful of "good" apps everybody uses, and then there are the 95% that are garbage anyways, but are still preferred over mobile websites.
I'm not saying that you can build the perfect app with hybrid, but solutions that are good enough for most people, because they want to catch the next bus and give zero fucks about a native experience. And then, saving 30-50% or maintaining an app for Android AND iOS as a solo developer suddenly becomes quite a strong point in favor of hybrid.
- ryanwaggoner 9y agofrom a developer perspective I think you have it backwards. I think you're still hung up on the developer experience, not the user experience. My observation is that users clearly prefer native apps to hybrid apps. And yes, you can throw together a hybrid app a bit faster, but you're just going to lose out to someone who did a better job (probably with native). So you might have saved a few bucks, but it's all going to be wasted. Just my observation, YMMV, etc, etc.