LOGIN | REGISTER NOW | SUBSCRIBE
 
Print

Facebook approached mobile like an enterprise


By Joseph Hill


 Joseph Hill
Email
September 24, 2012 —  (Page 1 of 2)
Some view Facebook’s very public stance on the importance of native experiences (and the mistake of HTML5) as just Facebook news, with no real relevance to the rest of the world. However, if you dig a little deeper into Zuckerberg’s statements and the history of Facebook’s mobile execution, there are surprising parallels between Facebook’s approach to mobile and how most large enterprises initially approach mobile.

Many CIOs dismissed Zuckerberg’s comments as irrelevant to them. They should take heed, however, because Facebook’s conclusions are the same as thousands of other companies at a similar mobile strategy stage, and they can benefit from their learning curve and experience.

The real mistake Facebook and other enterprises that start down the HTML5 road make is failing to recognize important dynamics and patterns that happen when a new OS is introduced. Historically, the capabilities of a new platform are changing so rapidly that they are years from being standardized. This means that the best apps (the apps that take advantage of the groundbreaking capabilities of the new platform) are written to features of the OS.

The race for market share among device platforms is driving a tremendous amount of change and innovation at the operating system level, which far outpaces the velocity that a “standards” approach can ever achieve. Something as fundamental to the user experience as scrolling in a way that feels natural to the OS is very difficult to achieve outside of direct access to the device OS, as explained by Facebook in a post to the WC3 last week. Rapid innovation at the device OS level will continue for the foreseeable future because this is where device platforms will live or die.

One of the other challenges inherent in building HTML5 apps is that mobile browsers support the standard inconsistently. The “Ah ha” moment for many organizations happens when they start to build and deploy real apps to real users and realize that the union of HTML5 capabilities supported across mobile browsers is quite small, forcing them into “lowest common denominator” experiences, or spending engineering cycles on graceful degradation instead of groundbreaking features. As mobile becomes more central to an organization’s strategy, and as they see how these “lowest common denominator” apps actually perform with real users, it becomes clear that they cannot base their mobile strategy on HTML5.


Related Search Term(s): Facebook, HTML5, mobile

Pages 1 2 


Share this link: http://sdt.bz/36982
 
Most Read  Latest News  Resources
SAP unveils SAP HANA platform innovations for Big Data and spatial processing
Features include smart data access and expanded cloud deployment options
Alteryx raises $12 million to put Big Data analytics in the hands of all business analysts
Quest founder's firm, Toba Capital, selects Alteryx as its first analytics investment
Google I/O kicks off
Developers get new APIs and tools, and the Go language hits version 1.1
Jelastic launches new version of its Java and PHP hosting platform
Jelastic today announced the launch of a new version of its ultra-scalable cloud hosting platform
Digg!  Digg
Reddit  Reddit
Slashdot  Slashdot
Share on facebook  Facebook
Share on Twitter  Twitter


close
NEXT ARTICLE
Kik Launches an Open API to Enable Mobile Developers to Bake Instant Content Sharing Into Any App
API-powered developers like Rude Boy Games, DrinkOwl and FlyScreen can promote their apps to millions of Kik Messenger users Read More...
 
 
 




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

   
 
 

 


Download Current Issue
MAY 2013 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?