at first I rolled my eyes but by the end I was filled with sympathy and agreement! spot on!
It’s cheaper to build multiple native applications than one responsive web app
11–20 of 322 posts
Re: It’s cheaper to build multiple native applications than one responsive web app
#12What about developing a core codebase to build an app for different platforms (including the web)? There are framework out there that can help you do that. At least in C++ (this is the language I use the most).
Re: It’s cheaper to build multiple native applications than one responsive web app
#131 dev = all
5 device dev = 5 apps
1 dev 100k 1*5 500k in salaries
Re: It’s cheaper to build multiple native applications than one responsive web app
#14And if only there were solutions that made it easier to prototype and get your backend running faster. It could make it even cheaper to make native apps. end: self serving response :)
Re: It’s cheaper to build multiple native applications than one responsive web app
#15I guess he hasn't heard of React Native...
Re: It’s cheaper to build multiple native applications than one responsive web app
#16Although a rant, this is also pretty substantive. We've replaced the baity title with a representative sentence from the article in the hope that commenters will follow suit.
this is also pretty substantive.
Fuckity fuck fuck fuck you, and shut the fuck up, dear reader. More fuckity fuck because the author has a keyboard macro that expands "," to "fuck".
I don't know, I thought it was pretty much a waste of my time. Read the top of the page you're looking at right now, read my first sentence. There, saved you a few minutes.
Re: It’s cheaper to build multiple native applications than one responsive web app
#17One app for iOS, one for Android, and I got over 90% consumer coverage
However with a huge friction point of requiring users to download and install an app.
Re: It’s cheaper to build multiple native applications than one responsive web app
#18"One app for iOS, one for Android, and I got over 90% consumer coverage" What's the consumer coverage for Mobile Chrome + Mobile Safari? Giving up on total cross-browser compatibility doesn't have to mean writing native apps.
The coverage is probably pretty high, but you're limited by each browsers respective feature set. There may be functionality that you can't ship due to limits on multiple browsers. Other issues arise if you factor in sites which needs to take into account all browsers; You'll end up bloating your JS/CSS to handle all of these conditions impacting mobile page size. It can be done, if the product is fairly simple, but problems arise as you increase your products complexity and feature set. Native apps have their own set of problems with distribution and the web has it's own set of problems with performance and hardware API access.
Re: It’s cheaper to build multiple native applications than one responsive web app
#19I guess he hasn't heard of React Native...
React Native is no panacea. For example, Discord has found it unsuitable for Android so far. [1]
https://discord.engineering/using-react-native-one-year-late...
Re: It’s cheaper to build multiple native applications than one responsive web app
#20And if only there were solutions that made it easier to prototype and get your backend running faster. It could make it even cheaper to make native apps. end: self serving response :)
Hawking your own startup here doesn't make sense since the issues presented in the rant discuss user-facing product architecture.