We know that social media usage is migrating to mobile, but how much of that usage is channeled through apps, and how much is through browsers?
Facebook reaches about 76% of the U.S. smartphone population through its popular app, according to recent data from comScore.
But an additional 10% of smartphone owners access Facebook only through the mobile Web (using a mobile browser such as Safari or Chrome).
In other words, Facebook sees a 13% gain in audience thanks to its mobile website.
Twitter is even more dependent on the mobile Web. Twenty-one percent of the U.S. audience accesses Twitter’s app, but an additional 8% access it over the mobile Web. That’s a 38% audience “lift,” taking the app-only audience as the base, for Twitter.
Pandora is 100% dependent on its app usage.
Looking at the top smartphone properties, one interesting case is Amazon, which reaches an impressive 66.8% of U.S. smartphone users. ! However, it fails to crack comScore’s top 15 apps list, meaning its app fails to reach the thresh hold of reaching 20% of smartphone users. Amazon is clearly still dependent on the mobile Web browsers for a big chunk of its audience.
It may be true U.S. mobile users are quickly moving away from the mobile Web in favor of apps, but developers and app publishers need to keep an eye on their mobile sites too.
Since Google Maps is no longer baked into Apple’s Maps app for iPhones and iPads, using the web-based version is your best option. Google is said to be working on a standalone Google Maps app for the iPhone, but it probably won’t be ready for a few months.
Many think HTML5, a new technology that allows developers to build rich web-based apps that run on any device via a standard web browser, will save the mobile web.
However, in August, Facebook sent shock waves through the HTML5 world when it released the latest update of its iOS app. In this update, Facebook abandoned its HTML5-heavy app for one built from scratch with Apple’s iOS SDK.
In a new report from BI Intelligence, we explain why Facebook decided to abandon HTML5 for the time being, analyze the state of HTML5 and native apps, and detail why it may take even longer for HTML5 to win out than previously thought.
Here’s a brief overview of why Facebook defriended HTML5:
- HTML5 app functionality still leaves much to be desired: HTML5 is a set of related standards. Th! is is ke y to understanding the problems that beset HTML5. As such, it has progressed relatively slowly. Facebook’s iOS product manager explained to The Verge, “Up until now, we’ve looked at scale, but we’ve become aware that while we have a great mobile website, embedding HTML5 inside an app isn’t what people expect.”
- And, HTML5 has a fragmentation problem: This is the very problem it is often trumpeted as a solution to. According to Appcelerator’s Michael King, there is a 30% differential on feature support across browsers. In other words, some HTML5 features may be supported in Chrome, but not in Safari or Firefox. This problem carries into mobile browsers as well.
- The success of Facebook’s mobile website underscored this issue: Just last April, Facebook said that its HTML5 mobile site had twice the number of users as its iOS and Android apps combined. This actually presented a problem for Facebook: iOS and Android’s mobile browsers don’t support a consistent feature set, including photo uploads! , a crit ical feature for Facebook.
- Apple and Google refused to help: Facebook started a Mobile W3C Community Group to promote the development of mobile browsers. Apple and Google, who combine for more than 85% of the global smartphone market and have a vested interest in the native app ecosystem, never signed on. The dream of building one HTML5 app and deploying across all platforms never becme a reality.
- But, the promise of HTML5 remains: Zuckerberg had this to say about HTML5: “It’s not that HTML5 is bad. I’m actually, long-term, really excited about it” His regret was not that Facebook spent two years dithering on HTML5, but that it spent two years on HTML5 when it wasn’t ready, or, as he put it, “it just wasn’t there.”
In full, BI Intelligence’s reports on HTML5 analyze:
- Why the HTML5-vs-Apps debate matters, breaking down its impact on distribution, monetization, platform power and network effects, and functionality.
- The success of an HTML5 pioneer, The Financial Times.How and when HTML5 will take over, laying out how it has all the hallmarks of a disruptive technology.
- What an HTML5 future will look like, with the promise of richer and more interactive experiences.
- Why native apps are winning now, and why it is taking so long for HTML5 to win out
Dr. Augustine Fou is Digital Consigliere to marketing executives, advising them on digital strategy and Unified Marketing(tm). Dr Fou has over 17 years of in-the-trenches, hands-on experience, which enables him to provide objective, in-depth assessments of their current marketing programs and recommendations for improving business impact and ROI using digital insights.
Collaborators – Digital Profs
- Netflix vs Blockbuster - Perfect example of an industry replaced by a more efficient version of itself
- The JKWeddingDance video was real; the viral effect was MANUFACTURED - Post 1 of 2
- Marketing Costs Normalized to CPM Basis for Comparison
- Coke vs Pepsi vs Dr Pepper
- Facebook advertising metrics and benchmarks
- Try On New Glasses in Warby Parker's Virtual Booth
- The Grand Unified Theory of Marketing(tm) - Digital String Theory
- 90-9-1 or 1-9-90 Rule of Social Media Participation
- Ad Injection: Yet Another Challenge for Online Advertising
- Brand Advertisers: Escaping an Ecosystem of Digital Advertising Fraud
- #SESNY: Toward a Performance Mindset for All Advertising
- Tips for Marketers Selecting a Digital Agency
- Context Is Not King or Queen; It's Just Necessary
- 2013 New Year's Digital Marketing Resolutions
- The Good, Bad, and Ugly of Online Campaign Ratings and eGRPs
- Why You Should Banish the Net Promoter Score Immediately
- Digital Strategy To-MAY-to vs. To-MAH-to
- The Agency-Client Relationship is Forever Changed
- Targeting vs. Privacy - Who Will Win?
- May 2015 (4)
- April 2015 (32)
- March 2015 (57)
- February 2015 (79)
- January 2015 (86)
- December 2014 (69)
- November 2014 (98)
- October 2014 (150)
- September 2014 (109)
- August 2014 (44)
- July 2014 (92)
- June 2014 (118)
- May 2014 (173)
- April 2014 (130)
- March 2014 (247)
- February 2014 (167)
- January 2014 (222)
- December 2013 (167)
- November 2013 (111)
- October 2013 (116)
- September 2013 (214)
- August 2013 (210)
- July 2013 (200)
- June 2013 (87)
- May 2013 (87)
- April 2013 (70)
- March 2013 (114)
- February 2013 (89)
- January 2013 (136)
- December 2012 (96)
- November 2012 (130)
- October 2012 (147)
- September 2012 (93)
- August 2012 (93)
- July 2012 (112)
- June 2012 (71)
- May 2012 (82)
- April 2012 (80)
- March 2012 (122)
- February 2012 (114)
- January 2012 (129)
- December 2011 (60)
- November 2011 (54)
- October 2011 (29)
- September 2011 (17)
- August 2011 (30)
- July 2011 (18)
- June 2011 (19)
- May 2011 (23)
- April 2011 (23)
- March 2011 (52)
- February 2011 (69)
- January 2011 (108)
- December 2010 (82)
- November 2010 (67)
- October 2010 (68)
- September 2010 (44)
- August 2010 (101)
- July 2010 (61)
- June 2010 (28)
- May 2010 (28)
- April 2010 (26)
- March 2010 (33)
- February 2010 (21)
- January 2010 (13)
- December 2009 (4)
- November 2009 (2)
- October 2009 (14)
- September 2009 (6)
- August 2009 (19)
- July 2009 (34)
- June 2009 (11)
- May 2009 (4)
- April 2009 (6)
- March 2009 (13)
- February 2009 (32)
- January 2009 (25)
- December 2008 (1)
- October 2008 (1)
- June 2008 (1)
- November 2007 (1)