Print

Analyst Watch: Native vs. Web: The debate continues



Al Hilwa
Email
January 14, 2014 —  (Page 1 of 3)
The debate has raged for a couple of years now around the best way to build mobile apps. I discussed this in my column last March highlighting our IDC prediction that native and Web development will coexist. For 2014, we are going further and asserting that for mobile apps, HTML5 will not replace native development for the 2017 planning horizon, though certain parts of the technology, such as WebSockets, will mature for widespread mobile use.

So where is HTML5 now? To put it in Dickensian terms, these are the best of times for HTML5, these are the worst of times for HTML5. It’s the best of times because the technology is moving faster than ever and it has continued to hold developer attention. A large number of important companies are working furiously on evolving the technology, and all modern browsers now support it to a significant degree. Browsers are being updated at a dizzying pace, and new HTML5 features are being added or improved constantly.

But it's also the worst of times, because a number of high-profile efforts to develop important high-scale applications in HTML5 have failed (e.g. Facebook and LinkedIn), and as of today, few startups would risk implementing their flagship mobile application on HTML5. HTML5 has so far failed to be the imagined unifier of mobile development, and it is far from toppling native application platforms (e.g. iOS and Android) as the primary means for developing mobile applications.

What is going well with HTML5?
HTML5 is in fact being widely adopted, especially on the desktop. Desktop browsers now support almost all the key features, and many enterprise and consumer applications are refreshing their UIs to use more HTML5 features. An HTML5 gaming ecosystem has begun to mushroom with casual games like Bombermine and Battle Fish engaging the free-to-play desktop gaming world, and technologies like WebGL are starting to be used now that it is supported by IE11. New app builders like Construct 2 have sprouted for casual mobile developers, and new versions of Android and iOS are sporting improved browsers (notwithstanding bugs).



Related Search Term(s): native, IDC, HTML5

Pages 1 2 3 


Share this link: http://sdt.bz/67579
 


Comments


01/17/2014 10:13:06 PM EST

Two more powerful things have emerged in HTML5 camp in 2013: 1. HTML5 speed breakthrough. It turns out HTML5 can reach native level of fluidity by offloading the bulk of work to GPU and switching to real-time DOM management as demonstrated by famo.us (and implemented independently by our startup - shameless plug). 2. Packaged Apps. This new type of HTML5 apps (rolled out by Google on Chrome OS, desktop Chrome and soon on Android) provides full native-level device access and offline capability. Consider that Packaged Apps is the only means of making apps for Chromebooks which are rapidly gaining market share. This trend is also supported by Amazon allowing Packaged Apps in its FireOS App store, and the similar Packaged Apps in Mozilla FirefoxOS Marketplace.

United StatesGene Vayngrib


close
NEXT ARTICLE
SD Times Blog: Developers can now charge for HTML5 Web apps in the Amazon Appstore
Amazon announced a change that allows developers to price HTML5 apps just like their native coded counterparts Read More...
 
 
 




News on Monday  more>>
Android Developer News  more>>
SharePoint Tech Report  more>>
Big Data TechReport  more>>

   
 
 

 


Download Current Issue
APRIL 2014 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?