4 ms·
Are you trolling? If you go native you have to write and maintain a different codebase for ever platform you want to support. With HTML5 you can update code wit
by marknutter 14y ago
Are you trolling? If you go native you have to write and maintain a different codebase for ever platform you want to support. With HTML5 you can update code without going through Apple's lengthy update process, and you can share that code across as many platforms as you like. HTML5 also allows you to tap into a much wider pool of developers.
- flatline3 14y agoNone of what you covered provides any advantage whatsoever to your users. It's all about making web developers happy.
- cluda01 14y agoI think that this is one of those instances where the needs of the company were prioritized over the needs of the user. Not to say this isn't uncommon in any industry, however, in prioritizing maintenance cost minimization they made the user experience markedly worse for the end user.
- marknutter 14y agoIn the case where you only have the resources to make an iOS version of your app, you certainly are thinking of your users when you use a cross-platform solution so that Android is supported.
- duaneb 14y agoPerhaps, but the better thing to do would be to write native apps for both users.
- anuraj 14y agoDo you think it matters to a company with a substantial mobile user base - and tons of money? HTML5 is for cheapos.
- marknutter 14y agoIn Facebook's case, it wasn't about money, lord knows they had plenty of that. It was about being more agile. With HTML5 they could play with a lot of different views without having to push a monolithic update to their users every time. HTML5 works better for some apps than native languages do; for instance, I'll bet dimes to dollars you're consuming Hacker News via the web, not a native app.
- cageface 14y agoMonotouch provides an interesting alternative. You still have to do custom UI for each platform, but you can reuse all the other code and still get native performance.