April 9, 2010

Mobile Web vs. Native Apps. Revisited

Written by Jon Arne Sæterås.Filed under Blog | 15 Comments to Read

It is about time to revisit the “native app or mobile web” question. I wrote a blog post on this a while back explaining the differences between these two ways of entering the mobile. Since then lots have happened in our business, both with regards to hardware and software. And not to forget, the usage of mobile web and apps.

As you know, Mobiletech believes in the mobile web as the platform for pretty much everything on mobile. We love iPhone apps, for sure. Mobile web and native apps can live happily side by side. Read this blog post as an advice where to make your future proof investment, and you can still create native apps for other cases.

Some background statistics

According to Informa market data there were 666 million mobile internet users by the end of 2009. This number is excepted to grow to 2.13 billion by 2014. According to Admob smartphones accounts for close to 50% of all mobile web traffic. Of the ~330 million smartphone users 50% have iPhone, 24% have Android, 18% have Symbian and 4% have RIM OS * (We know that these numbers are way to high since smartphone penetration is extremely high in Admobs markets. Some say that iPhone accounts for 2% globally and smartphones 15%). Feature phones are loosing terrain,while “internet enabled devices” (iPad, PSP, Nintendo DS etc) are gaining.

Globally the smartphone sales from 2009 is dominated by Symbian:

phonesales

Source: CloudFour.

The Mobile Web – worlds biggest app-store!

The numbers above points out that surfing the internet on mobile is popular and will be much more popular in the future. Many different sources suggests that web on mobile will be the dominant channel in the near future. Google says desktop web will soon be irrelevant. Search is also one of the most popular activities on mobile web according to Novarra. All in all, the potential discoverability on the web is very good! In addition to search you also have a stronger presence of social media on the mobile web. So for mobile web applications the audience is 666 million, smartphone native apps 330 million, iPhone apps 165 million.

Get the users to your site or app.

According to MocoNews, the New York Times iPhone application has reached 3 million downloads. How many regular users is that? If the numbers from Pinch Media are correct, this means 30000 users on a regular basis. Again, it is difficult to compare this number to the equivalent on mobile web, but the number of returning users on mobile web sites is way higher than 1%. If I look at the numbers Mobiletech has access to the lowest percentage I could come up with is 10% when it comes to regular users over time. From a big North-American customer of ours I know that most users are regulars, and that the number of page views has increased threefold the last year.

Different services, different medium.

According to a report from Taptu there are differences between what type of content or service fits best on web or apps. Obviously, games works best as native apps as they often use heavy graphics and benefit from not having to access resources via a browser. However, shopping (mCommerce) and services prefer the mobile web. According to Taptu this is because many of the mCommerce products do not fit into the static iTunes content oriented billing model. This fact is true for other sectors as well. On the mobile web you have the freedom to create what ever business model you want.

taptu_feb10b

One thing that we have learned from the apps is that they are great for marketing. Once you got an app, you get potentially lots of attention since the “app phenomenon” is so hyped and hot these days. So from a marketing perspective apps are great!

Usability; Native apps vs. mobile web

However, user testing of people attempting tasks on their mobile devices shows that the apps have much higher usability than the websites. For an “average” mobile site, compared to a glossy native iPhone app that is very true. As Jakob Nielsen points out; awkward input, download delays and badly designed sites are the main reasons. But remember that the iPhone app is tailor made for iPhone. The average mobile site is not. Therefore it is extremely important to adapt the presentation and interaction model to the device and browser you are serving. Gartner believes this will be the case in the near future as well:

“In mature markets, the mobile Web, along with associated Web adaptation tools, will be a leading technology for B2C mobile applications through 2012, and should be part of every organization’s B2C technology portfolio.” (Gartner, 2010)

Maintenance of mobile web apps compared to native apps.

If you have a good system for doing adaptation of content and presentation to mobile devices and browsers, you only need one codebase to develop and maintain. This will then work across all devices, feature phones as well as smart phones.

On the app side, however, you have a number of platforms you have to support. First you have the iPhone. The iPhone platform was pretty straight forward (even if you had the iPod with slightly different capabilities), but now the iPad has arrived. Now, you need to create an iPad version of your app as well.

The other big one is Android. Andriod is growing fast and gaining market from Apple rapidly. So you might want to create an Android app as well. But one version of the Android app is not good necessarily enough. Due to the nature of Googles Android project there might be fragmentation among Android implementation on devices as well. A similar issue as with the good old Java applications.

Symbian is the next big one. Even if the market share is decreasing it is still significant. RIM is also so big that it makes an impact. We should also mention Java, Windows Phone 7 / Mobile and WebOS from Palm.

Editorial control and freedom

To be able to control the content and presentation is very important for any content provider. Due to the cumbersome maintenance and update routines in native applications and appstores this process can take several weeks. The work includes programming, testing, approval process and then the end users have to actively choose to update the app. On mobile web apps you only have to do limited programming and testing. The users will then always get the latest content and experience.

Business models

Yes, most app-stores comes with a ready-to-use business model where the end users pay for the application, upgrades or access to content or services. In the iPhone case Apple is calling all shots; IF you will get business, HOW you will get business, and HOW MUCH revenue is shared with you. Currently 30/70. This seems to be a small price to pay to get access to a working payment scheme. But I have not heard of a single case from the media- , content-, services industry about anyone actually making money on this business model. We will probably get the proof when the iPad has been in the market a while. The media industry is hoping that the iPad will be the saviour of the badly hit business sector, but it is not looking good according to early numbers.

“One big trend that’s apparent: big media and entertainment companies are doing very well in top free apps, but are barely present in top paid apps, whether by number of apps downloaded, or by the gross revenues from their apps”

Frankly, after testing a few of these “iPad magazine apps” my self, I am not surprised.

So how about the business models on the mobile web? Well, there are none. In my experience in the mobile space this seems to be the main issue compared to native apps. Content owners and publishers don’t know how to make money on mobile web. This can be a show-stopper, I fully understand that. On the other hand we don’t know if the app-store model is working either. Further, on the positive side, no out-of-the-box business model means that you are free to create your very own where you get all revenue and the direct customer relationship. You probably have some business models from your desktop web offering you can reuse and adapt to mobile as well. Reuse is good.

Before you can get any business model to work, you need eye balls. As a part of the web, the eyeballs are closer and many more than just the “iPhone segment” or “app segment”. Next step would be to make sure the users who found your mobile web site come back again. Then we need to make the user feel happy and satisfied. This is where usability and optimised presentation and interaction comes into the picture. Now you have what you need to start exploring business models on the mobile web. The mobile industry is just at the breaking point of entering this stage now. Some have found working business models, other haven’t. Probably the business models will vary from case to case. There will not be a common mobile web business model. Even the mobile advertising business model is still immature. Still too close to desktop advertising. Hence, not utilising the unique aspects of the mobile channel.

My advice for the right direction would be: Think social media, think CRM, think mobile uniqueness, think rich media. There is a business model in there somewhere.

Owen Gloss spent $32,000 developing the iPhone app Dapple and made a total of $535 in revenue during the first month of sale. To break even, Owen needed to reach 9150 downloads. Read more of the interesting story here and a follow-up here.

DappleRevenueGraph1

Owen concludes with “I hope that this article might serve as a counter-point to the articles that seem to go around the web about devs making hundreds of thousands of dollars off an iPhone app. Everyone within the dev community understands that the odds of that happening are very slim”.

Best from both worlds

The Norwegian case “Meny” is a great example on how to get the distribution and business model from the app-store, and get the flexibility and the integrated workflow from the mobile web. The native app is only a skinned browser showing an optimised mobile web site. The same site as can be viewed through the web browser. Other approaches to such hybrid solutions include Appmakr and a hand full of others.

meny_frontbanner

HTML5 apps

The term “HTML5 apps” was introduced to me by Peter-Paul Koch. HTML5 apps are applications using the features of HTML5 in different wrappings. The app can run in a browser or it can be a standardized W3C Widget which is for all practical reasons a native application. I won’t dive into details on HTML5 here, but HTML5 includes many new features that makes it possible to create web based applications behaving like native apps.

Nextstop.com chose HTML5 apps over native iPhone apps. This video explains the concept:

[youtube]http://www.youtube.com/watch?v=Jks-idxVrCs[/youtube]

The Morgan Stanley mobile report states that HTML5 capable browsers and run-times are increasing rapidly. Further, Google have announced that they now put mobile before desktop, and the platform they have chosen is the web. For example Google Voice is a HTML5 app.

The W3C Widgets is a standard that allows web applications to run on the device like a native app. These widgets can even run on the desktop when the phone is idle. Moreover, widgets are not limited to phones. Widgets can run on desktops, kiosks, Macs, and more will come. Currently, you can run widgets on some Nokias, Vodafone S60 and Samsung phones, Opera desktop and mobile , the Bolt browser , and Windows Mobile 6.5. The future for widgets and apps based on web standards is bright, especially considering the work W3C is doing with the JavaScript APIs to sensors and services on the phone.

Here is a video explaining how the Facebook widget works on a Nokia N97:

[youtube]http://www.youtube.com/watch?v=h67Mr-kY-0I[/youtube]

So, you can easily create an augmented reality app like Layar using HTML5 and device APIs in the very near future. Good thing about that is that the HTML5 codebase works on more devices than the iPhone codebase.

Summary

I will try to sum this up in a table for your convenience:

Native apps (iPhone, iPad, Android, RIM, Symbian etc)HTML5 Apps (Mobile Web, Widgets)
OpennessOpen to anyone who signs an agreementOpen for real
Entry Cost$99/$299/$200 etc.0
Revenue split70/30 (Apple) or similar100% to you
RestrictionsSomeNone
Releases1-2 weeksContinuous
MicropaymentsYesNot good enough
PortabilityDevelop for each platformThe web covers all platforms capable of browsing
Discoverability You will need a very well defined strategy to break into the top list for your category in order to make it (AdWhirl estimates $1875 per day advertising budget can get you there , Pinch Media says the impact of being in the top 100 is a daily increase of 2.3x in the number of users)The web is known material, and one big appstore. Search, hyper linking, advertising are common and well known methods.
Market size and reachOnly selected platforms (smart phones are about 50% of the market ).All internet enabled devices. Cover 100% more end users than a full blown app approach.
Usage of device APIsAccess to most APIs like GPS, accelerometer, address book etc.Access to some. Like GPS. With HTML5 even more, and soon standardised by Device APIs and Policy Working Group
MaintenanceDifficult to support and maintain after app is downloaded. Multiple codebases to maintain.Users always gets the latest version. You are in control. One single codebase.
User interfaceClose to full controlLimited to the device/browser capabilities and the experience will vary.
PerformanceBetterGood
Offline usageYesYes. With HTML5, Google Gears etc.
Distribution via appstoresYesYes + the web
Icon on desktop/home screenYesYes, and even the application running on the desktop.
Handling of heavy graphicsVery goodNot good for gaming. HTML5 provides functionality that is more than good enough for inline video and as a “flash replacement”.
SexynessVery sexyThe average is not very sexy. Depending on the device and how it is designed.
Icon on home screenYesYes. As a bookmark opening the browser, or as a widget running directly in the desktop.

Sources; Mobiletech, CloudFour, blog.dudamobile.com

*) The stats here is not very comparable, I know. But good enough to give a picture. Informa has had a closer look and compared different sources in this PDF report.

About the Author Jon Arne Sæterås

Product Director

Other posts written by Jon Arne Sæterås (40 posts)

@jonarnes

  • Mike Rowehl: This is Mobility » Blog Archive » Opening Up Mobile Monitization said,

    [...] post at Mobiletech : Mobile Web vs. Native Apps. Revisited. Obviously, working at Chomp to help prop up the discovery end of the app ecosystem and funneling [...]

  • Mobile Web vs. Native Apps. Revisited | Mobiletech AS | The other side of the firewall said,

    [...] April 10, 2010 10:43 am [From Mobile Web vs. Native Apps. Revisited | Mobiletech AS] [...]

  • About Mobility » Blog Archive » On Reasons Why The Mobile/Wireless Usage Boom is Underway | Part 2 said,

    [...] on Opening Up Mobile Monetization, which he wrote in response to John Arne Sæterås’ blog Mobile Web vs. Native Apps. Revisited, I agree that technology and application richness and user experience all by itself are not [...]

  • Manju G said,

    Unless there is a need for device specific feature (like camera, GPS etc.,), the need for a native application is not justified, esp. for the enterprise. Native Applications are akin to legacy client-server architecture and we moved away from it adopting web (thin client) architecture on the desktop. One main issue with thick client is the cost of maintaining the app on the client device. This problem only multiplies considering the wide array of mobile client devices.

    The cost for building & maintaining native apps for many platforms (and versions thereof) is prohibitive and very hard to justify ROI. If the required features can be delivered by a Web app, it should be the first choice.

    Check my thoughts around this topic athttp://www.gmanju.com (my blog)

  • mogsie said,

    Now we have the Google Web App Store, the game changes. Any comments on these new developments, Jon Arne?

  • Scott Murray said,

    This is a fantastic round-up and analysis of all the business, technical, and user experience issues involved in this debate. Thank you for putting this all together.

  • Bill French said,

    Excellent analysis and great article.

    I think web apps will make a huge leap forward in the coming 24 months but there will always be cases where native apps trump web apps – it all boils down to the business requirements. I created this dynamic spreadsheet to help my company decide which approach (native or web) was right in a given project scenario. http://ipadcto.com/mobile-apps-native-or-web/

  • ireneh said,

    Wow, this is excellent and super useful. Thanks very much!

  • Arild Henrichsen said,

    Great post. I hope you don't mind I linked here from my EPiServer/.NET blog: http://www.epinova.no/blog/arild-henrichsen/dates…

  • Psysoul said,

    I guess soon we will be able to develope games in HTML5 / Javascript. This can be the future, as more mobile devices are used with internet.

    Check out these videos: http://www.youtube.com/watch?v=_RRnyChxijA&fe…
    http://www.youtube.com/watch?v=WPVhPGOLe7c
    http://rocketpack.fi/engine/

  • Murat said,

    Cross platform can be a solution. smartface Designer allow you to build mobile apps without writing any line of code. Also, it works for Symbian,Java, BB… It is not browser based it generates native output files like jar,sisx….
    You can check out from http://developer.smartface.biz/

  • @mstutman said,

    This is a fantastic post. At the end of the day, the decisions come down the nuances of specific business objectives, audience needs and context. There is no right answer, but based on search volume and increasing mobile traffic/usage, most businesses should start with at least a basic mobile site. I've written a post on the subject here:
    http://www.acsysinteractive.com/blog/mobile-so-mu…

  • Treasure Hunt App said,

    I have been preaching to people for years that both mobile web and native apps play complimentary roles in a fully-integrated web strategy, and that both are necessary to provide the best contextual user experience in any environment. It is great to see an article like this support the concept.

    Treasure Hunt App

  • JimBrown said,

    Truly agree with you that Native mobile application is published through the major application stores and developed for a specific mobile platform and native Smartphone application resides locally on the device and is published through the major application stores. While Web-based mobile application is a cross-platform and fully accessible via mobile browsers and web site that has been designed appropriately to fit size, performance, and appearance of a mobile device, thanks a lot.

  • @joshbroton said,

    With the newer developments in mobile web technologies, it bears revisiting. The idea of being able to develop one site that responds to the users device and displays it's content no matter what the form factor should and most likely will change the way users use the web, and the way we develop for it. I see more and more companies abandoning the idea of an app, with all it's baggage, and instead employ responsive design techniques. I've written more of my thoughts here: http://www.vistacomm.com/VistaComm/BlogPost.aspx?… and would welcome any of your thoughts on the subject.

Add A Comment

 

Oslo
Bergen
Stockholm
Copenhagen
Washington D.C.
London