Choosing mobile App vs. mobile Web site?
by Steffan Berelowitz
Steffan Berelowitz founded Bit Group, Inc. in 1995, and over its 14-year history has helped to develop a client list of Fortune 500, mid-market and emerging businesses. In addition to his responsibilities at Bit Group, Steffan served as a trustee of the Massachusetts Technology Leadership Council (MA Software Council) from 2001-2006. Steffan served on the board of directors of the Jewish Community Centers of Greater Boston as the chair of the advisory board of the Center for Information Technology of Hebrew College. Steffan is a member of the Boston College Technology Council. He is also a member of the Technology Network, a national network of senior executives from the nation's leading technology companies. Steffan served as an Internet consultant to former senator and presidential candidate Senator Bill Bradley. A graduate of Boston College, Steffan has spent the past 15 years in online services and technology. In 1993, Steffan was one of the key founders of ArtNet.
See other posts by Steffan Berelowitz
If you are considering building your mobile channel, will you choose to build a mobile app or should you build a mobile Web site?
Before we get into the finer points of this debate, we can ask a few qualifying questions first:
1) Do you need to access the phone’s camera?
2) Would you like funtionality available regardless of whether the phone is on the Internet (online or offline?)
3) Would you like to access the phone’s contacts?
4) Would you like to access the phone’s location or other core features (e.g. accelerometer, bluetooth)
If the answer to any of the above questions is yes, then your choice is simple. Build a native mobile app. If you did not answer yes to any of the above questions, here are some guidelines you can use to think about this question:
Native mobile apps
- Pro: Access the phone’s core features (see #1-4 above)
- Pro: Faster user experience (apps can more easily handle caching on the phone client)
- Pro: Richer user interface and user controls (more dynamic/graphical)
- Con: You may need to build multiple apps — one for each device: iPhone, Android, Blackberry, Symbian
Mobile Web
- Pro: A single mobile Web site may work on multiple phones (through each phone’s browser)
- Con: May be slower (more latency)
- Con: Less attractive user experience
- Con: Cannot use phone’s core features
- Con: Cannot work online/offline
There are some who believe that a new browser technology (HTML 5.0 and CSS3) will enable the mobile Web to become more competitive with the user experience of a mobile app. This may narrow (but not close) the performance gap in the future. In the meantime: If you choose to build a mobile Web site, you’ll spend less money and potentially reach more devices with a single solution. If you choose to build a mobile app, you can take advantage of more features and capabilities on the device, the location of the user, etc.
There are two other trends to keep in mind:
1) Smartphones (can run mobile apps) will overtake feature phones marketshare in 2011.
2) 74% of smartphone traffic is on iPhone or Android
According to AdMob, if you choose to build mobile apps, iPhone and Android will enable you to reach 74% of mobile users as of Feb. 2010.
October 11th, 2010 at 3:49 am
Un blog interesante, te hace pensar. Seguir asi