"many advancements in what we can do with Javascript and HTML"<p>Please don't be closed minded about only using to languages because the "open" web won't let you use anything else (no transpilation crap please).<p>"The web is open"<p>It is not open in every sense. It is locked to a few languages and technologies: JS, HTML, CSS. Where can I vote for standardizing a proper intuitive grid control instead of CrapGL and crapvas?<p>"Why would we continue to have to have specialized developers working on ports of the same application for every different platform?"<p>To have a chance to work with languages that don't suck. Business could have a different view though.<p>"Imagine if all the new iOS features were available to javascript"<p>All I see is a potential sad future where you are forced to use one crappy script language for most career paths in IT.
I've held this viewpoint for a long time now, and it's yet to pan out. It's probably worth understanding the two main forces that lead to the browser defeating native desktop applications roughly 10 years ago:<p>- Developers liked the web for three reasons: write once run everywhere (give or take a few browsers peculiarities), no versioning of the software, and bugfixes are immediate.<p>- Users liked websites because they didn't want (or weren't able) to install software, and they got a consistent experience across mulitple computers (work + home).<p>Looking at these, it's clear why native is beating the web right now in mobile. Software is easy to install, and you only have one phone. It's still annoying when you run an app that hasn't been active in a long time and are forced to upgrade on the spot. But that's the only chink in the armor at this point.
Nope. The arguments in this piece are way off base. This is also now a very old argument which has been rehashed too many times. Modern wisdom shows us that native mobile apps have their place and Apple, Google, Mozilla and others are rapidly advancing web technologies. They are hardly holding back in order to force developers to build native apps. Once SVG, Canvas and other powerful HTML5 features become more common along with a more powerful runtime for the web, we will see the situation change. For now, I am happy building and using native mobile apps. I also build responsive web pages and plan on continuing doing so. They can coexist and they should.
While your points are reasonably valid, I think it's missing one grander conclusion: the tools are simply that, tools. Above all else, it's what you make with them that matters.<p>As an engineer, I might be interested in the implementation details of a particular system, but as an end user, I don't give a shit.<p>And with that, it's up to the engineer to determine the appropriate tool for the job, as has been the duty of engineers since man carved the first wheel.
For the most part, I agree with your opinions and have chosen to develop my product as a web app rather than one that runs on iOS or Android. However, I think web apps will always be hindered for developers if we have to continue relying on an arcane and ugly language like JavaScript.
On the deskop, I find it hard to believe that web apps will come to dominate the app space. Perhaps they will find a space to sit side-by-side with native apps. But will they ever be able to match the speed, responsivenes and capability of a native app? I'm sceptical. Web apps on mobile are mostly about consumption of content in some form or require limited interaction.<p>What if I want to create my own music? Edit or touch-up my photos? Create graphics for my web pages? Do some digital painting? Edit some videos? Dabble in 3D or motion graphics? Create an animated GIF? Create a richly formatted book, magazine, brochure or report? Can I do any of this right now in a web app with the same richness of features, speed and capability as a native desktop app?
Users use apps on phones. They don't want to open a browser and navigate to an 'app'.<p>They go to the app store to get apps. They don't open a browser and google for a web page and expect it to operate like an app. Also you need to have an internet connection to even use an app, who wants that.<p>Technology improves but the drag comes from user adoption. You'll need to change behaviour.