It’s cheaper to build multiple native applications than one responsive web app
1–10 of 322 posts
Re: It’s cheaper to build multiple native applications than one responsive web app
#2I can totally relate to some of this.
If you take a look at Meeker's 2016 Internet trends report that came out last week, you will see that 3 apps dominate 80% of the usage on phones. I decided when I started my food side project a year back, that I was not going to do a native app.
I have been trying to make the front end look better, but I did not want to use very heavy frameworks, so I settled on using the SASS mixin library Bourbon.io along with the grid and a few others the company provides.
The css that is produces is very tight, and I can save on developer costs. I should say, save on finding another front end developer as the one I was using took some money and ran.
Re: It’s cheaper to build multiple native applications than one responsive web app
#3Although 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.
Re: It’s cheaper to build multiple native applications than one responsive web app
#4"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.
Re: It’s cheaper to build multiple native applications than one responsive web app
#5Although 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.
The fact that you go to this effort is why I love HN.
Re: It’s cheaper to build multiple native applications than one responsive web app
#6Ehhhh, I really haven't had these issues with any of the meteor apps I've made. Even getting swiping and full page animation transitions has been relatively simple. My experience is anecdotal, but I actually left being android developer to do mobile web and I've found the experience to be far easier.
Re: It’s cheaper to build multiple native applications than one responsive web app
#7(note: I've met Eran a few times, he is very smart and I respect his opinion)
Note aside: this is one of those "it really depends" kind of situations. For many cases native apps are always going to be cheaper to build. For others the web is just much better. It seems like the problem Eran is describing is more of a labor shortage. It's really, really difficult to hire good web developers. I have no idea why this is.
Re: It’s cheaper to build multiple native applications than one responsive web app
#8What this article needs is more F-bombs. Otherwise it's ranty but makes some good points.
Re: It’s cheaper to build multiple native applications than one responsive web app
#9Although 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.
"Top 10 Sumome popups you won't believe your eyes when you see" didn't cut it for you? Thanks for making our day a little better!
Re: It’s cheaper to build multiple native applications than one responsive web app
#10When you multiply that 90% consumer coverage by the percentage of people who will install your app when you ask them to, it's going to knock down your 90% pretty considerably.