No it's not. Get better designers - ones who understand responsive design, and developers who speak modern javascript.
It’s cheaper to build multiple native applications than one responsive web app
31–40 of 322 posts
Re: It’s cheaper to build multiple native applications than one responsive web app
#32Since the article doesn't touch on specific I'm wondering where React Native falls regarding all this. I'm considering using it for our pending iOS and Android apps, seems like a no-brainer at this point versus true native.
Well React Native is one of many strategies they could use to build their app and later on back port their components to the web, should they resurrect it. I would agree with your point that it's a no brainer.
Re: It’s cheaper to build multiple native applications than one responsive web app
#33A lot of the issues here are with mobile Safari. I agree it completely sucks just due to how behind Safari are with ES6. On the upside the work is complete to fix this in dev releases, so there's a very good chance that we're 3 months or so away from a large step change. I'm not planning on releasing anything in the next 3 months, so that timetable is okay for me, YMMV
Re: It’s cheaper to build multiple native applications than one responsive web app
#34I understand and empathize with the author's aggravation. But cheaper? Really?
So iOs and Android are more than 90% of the market. You are telling me that it is cheaper to build and maintain 2 separate apps and pass on the remaining part of the market than have one app that covers everything?
Android device support is supposed to be a nightmare - there are so many versions to contend with, each device manufacturer can customize things.
iOS is easier to support but fighting with Apple can be quite the ordeal.
Using the web means you bypass these other issues but have to contend with the ones cited in the article. It sounds like pick your poison.
I could conceive that after the initial cost of building 2 separate apps, for iOS and Android, that perhaps it is less aggravating and costly to maintain them, as opposed to dealing with the web. However how complicated is the UI for the web apps? Can't you keep it simple? Unless you can show numbers I cannot in my wildest dreams believe that building and maintain 1 web app is more than twice the cost of building and maintaining 2 separate native apps.
What are you building that requires building a 2016 Web app with every new feature? Maybe that is your problem.
Re: It’s cheaper to build multiple native applications than one responsive web app
#35"You want mobile notifications? Sure, but not on mobile Safari." You can do this with PhoneGap. "Multiple line ellipsis? Sure, but only on webkit." Okay, yeah, this sucks. "Consistent rendering size across browsers? Just fuck off." This is probably your fault. "We fix a layout bug on Safari and break something on Edge." This is probably your fault. "We change font size on Chrome and now all you can see on Firefox is…
This is probably your fault
That's the point of the article. Getting these things right on the web is non-trivial (and therefore expensive).
Re: It’s cheaper to build multiple native applications than one responsive web app
#36Ehhhh, 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.
Easier, yes. The tools for web development are awesome and amazing, but there's so many restrictions and limitations that come with the web. Maybe the web is the way forward, but native will be kicking its ass (regarding experience) for a long time.
Re: It’s cheaper to build multiple native applications than one responsive web app
#37if web is future then future is now!
Re: It’s cheaper to build multiple native applications than one responsive web app
#38"You want mobile notifications? Sure, but not on mobile Safari." You can do this with PhoneGap. "Multiple line ellipsis? Sure, but only on webkit." Okay, yeah, this sucks. "Consistent rendering size across browsers? Just fuck off." This is probably your fault. "We fix a layout bug on Safari and break something on Edge." This is probably your fault. "We change font size on Chrome and now all you can see on Firefox is…
Did we read the same article? What is this condescending bullshit. Nobody is arguing these things CAN'T be done, just that it's too much effort on the web, and the only web devs that know the ins and outs of every browser enough to make it work are unaffordable and unavailable.
Re: It’s cheaper to build multiple native applications than one responsive web app
#39I understand and empathize with the author's aggravation. But cheaper? Really? So iOs and Android are more than 90% of the market. You are telling me that it is cheaper to build and maintain 2 separate apps and pass on the remaining part of the market than have one app that covers everything? Android device support is supposed to be a nightmare - there are so many versions to contend with, each device manufacturer ca…
Using the web means you bypass these other issues
Not really. If you are doing anything that relies on device hardware, camera, microphone etc... then device type absolutely matters - and it's even worse on mobile web because you can't get close to the metal.
Re: It’s cheaper to build multiple native applications than one responsive web app
#40Ehhhh, 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.
Similar experience here using Meteor + Ionic, exported with Cordova. I also feel like the skills I'm developing in web development are much more widely applicable than learning a particular mobile OS.