I recently received a white paper from , a Belgium-based business development and project manager with 25 years experience in software development for businesses. His paper provides an interesting perspective concerning mobile versus web apps.
I’ve written at length about this subject many times and I’ve been keenly interested in apps and frameworks that streamline enterprise app development. FileMaker Go is an example of a balance between rapid native app development without the headaches of XCode and all that comes with single-platform solutions.
André’s perspective is purely based on web services; CSS3 and HTML5 and I applaud any team that doesn’t rule this avenue out and considers this approach with some degree of open-mindedness. I’ve often repeated a quote (not sure of its origin by the way) -
With few exceptions, most native apps could be written as web apps and provide a relatively similar experience.
It’s clear in André’s paper that he shares a similar fondness for web-based business apps and even though he is a self-described non-technical “developer”, he was able to research and suss out the key concepts necessary to build effective web-based user interfaces for iPad, and all iOS devices for that matter.
The chart below reviews some of the pro’s and con’s of Web versus Native apps. This is not intended to be comprehensive – just some of the high points. You can also find a more comprehensive discussion about these attributes in the downloadable resource Mobile Apps: Native or Web?
While this list of pros and cons serve as a useful starting point for determining a sound app strategy for business apps, it doesn’t factor in the future of CSS3 and HTML5 or the rapid adoption and expanding skills that are emerging in the mobile app development community. As such, André’s viewpoint on this topic is simply an early glimpse of a very likely shift toward web-based apps.
Critics of HTML5 and CSS3 [today] cite the fact that both of these standards are incomplete and likely to change over time. André makes a very good argument for pushing on with web apps right now.
Why even look at standards that are still in draft stage, one might ask. Because of Webkit. Webkit is the rendering software inside Safari. Apple keeps Webkit in ʻopen sourceʼ. Other users are Google Chrome and the Android browser (as well the browser in Nokia S60 phones). Webkit is being pushed aggressively by Apple towards full HTML5/CSS3 support: there are even ʻnightly buildsʼ available on Internet for developers liking to live dangerously. Each Safari release contains the latest stable version of Webkit. The risk for Apple is that some features done now may be different or absent in the released standard. The benefit for us that we can use most of HTML5 and CSS3 today.
In his paper, André also points out very clearly that it’s a collection of key technical concepts that provide a clear path to easy-to-develop and maintain mobile device presentations of business data.
When used together, these attributes transform a web site into a web app. The user will see an icon on the screen that will open an application. There is no difference to a full- blown app and nobody can see this app is actually driven by web standards and run by Safari.
The key concepts are:
- CSS3 media queries
- CSS 3D transformations (example)
- HTML manifest attribute
- Client side database (SQLLite)
- Full-screen extensions
Bill French on iPhoneCTO
The chart above lists why Native Apps will WIN with consumers:
When it comes to apps, EASY WINS.
Performance
Seamless User Interface
Seamless Installation
Seamless Payment Options
Streamlined Support
These are all reasons why Native Apps are better than Web Apps for consumers.
The reasons for Web App existence are all reasons for the developer, NOT the consumer.
EASY is why iTunes wins over pirated music.
EASY is why iPhone apps are preferred over Web Apps.
No one – no developer, no consumer – wanted Web Apps when Apple proposed that Web Apps are what should be preferred for iPhone app development. No one.
What developers and consumers wanted are Native Apps.
Arguing for Web Apps goes against the grain. Web Apps simply are second class compared to Native Apps. They are simply not as popular compared to a Native App.
James,
The “mobile touch web” is already many times larger than mobile native apps (see http://iphonecto.com/2010/05/05/2011-mobile-enterprise-development-controversy-native-app-web-app/). Do you have data that suggests otherwise?
BTW, I’m not falling on either side of this debate without a requirements context. There are many reasons that web apps may not be ideal in every context. However, one of the constrains is money and stating that native apps are the only way to go irrespective of any given context or constraints, is unreasonable.
I am currently in the closing stages of the development of a Web App, and from my perspective I disagree with James Katt. Obviously there are strong points for both sides.
I am creating a mobile sales web app with the app cache web pages, SQLite local databasing, and JQuery tools. It’s beautiful. The only extra work that was required of me was to get a solid web developer who was a real problem solver.
It’s lightning fast, user friendly, and self aware of synchronizing itself with our servers. 3G is no longer a hinderance to my mobile sales force!
I appreciate the iPad for what it is. the only choice I have. But when The time comes to move on, I’m independent of any single platform. I think many will see the benefit of the agility a few extra hours of development time will bring to the table.