Dec 4th, 2008
The Mobile Web vs. Mobile Apps: An Amazon Case Study
Amazon has a great mobile web site. When people have asked for good examples of iPhone optimized sites it’s easy to direct them to Amazon as a standout example. It’s very well designed. It’s fast. The amount of information and products presented feels appropriate to the small screen and an on-the-go context. The design language of Amazon.com, its parent site, is applied with thoughtful restraint — including the adapted sliding carousels.
So, why bother with a downloadable iPhone app?
Amazon announced yesterday the Amazon iPhone app for download in Apple’s app store. A better question is: What functionality warrants a downloadable app? And then, Will that functionality drive adoption better than a well designed mobile web site?
Doing what the mobile web can’t
At first glance, the only feature the application offers that the mobile web version does not is “Amazon Remembers”. The feature lets users to take photos with the iPhone camera and store them as items they want Amazon to remember for them. Amazon says they will try to send you a link to a matching product. What Amazon calls an “experimental feature” can hardly be the sole reason they developed this app. (To my surprise, Amazon Remembers correctly identified both items in my office I photographed. I was particularly impressed it found a 501st Legion Trooper Star Wars figure with Collector Coin.)
True to iPhone App standards
While the mobile web version is impressive, the iPhone app just might justify it’s 40 square pixels of real estate on my increasingly crowded home screen. It behaves as you would expect an Apple application to behave, with familiar icons at the bottom. Delete items from a wish list with a now familiar finger-swipe gesture. If I were a regular Amazon shopper, the iPhone version would become a staple as managing my cart and wish-lists is easier. Unlike Safari Mobile which fails to remember usernames and passwords, this application can.
The answer just might be the app store itself
Apple has done a great job creating an ecosystem for iPhone applications. Despite the aging paradigm of the iTunes Music Store (which needs a new name Steve), users are able to browse useful, noteworthy, and most importantly, user-rated applications. The fact is there’s no equivalent for well-designed mobile web sites, no matter how Safari-optimized they are. Amazon’s solid mobile web site will never show up in a hot list of the top 25 iPhone apps.
4 Responses to “The Mobile Web vs. Mobile Apps: An Amazon Case Study”
Leave a Reply
You must be logged in to post a comment.
[...] Vote The Mobile Web vs. Mobile Apps: An Amazon Case Study [...]
[...] Idlemode Valid XHTML | Valid CSS | Wordpress 2.6 var gaJsHost = [...]
Home screen icon management is the bane of the iPhone. It isn’t scalable to only create pages on the x-axis. Why can’t we navigate via the y-axis or even z-axis? Or sub-sets of applications? I’d love to put all my iPhone games in a “Games” folder.
As for apps vs. websites, there are obvious pros and cons to either. Apps can use the Apple SDK, so navigation is familiar in conjunction with other apps. Apps can also be launched from the home screen, without having to deal with one extra level of click. Apps can also work off-line, unlike websites. Apps don’t have the security, memory or technical limitations of the browser.
That being said, having browser-based apps also has a distinct advantage… it’s one of the only vehicles for multi-screen applications right now, from TV to consoles to PCs to MIDs to mobile devices.
Matt
I’ve written an article that describes the pros and cons as they relate to developing on the mobile web verus mobile applications… can find it here: http://fivemobile.com/development/mobile-web-mobile-apps