Driving into work today I noticed a few things from my fellow drivers that made me grab the steering wheel a little more tightly and slow down. The driver in front of me was hitting his brakes every 5 seconds, and it was becoming quite annoying. So, rather than endure this the entire drive, I decided it was time to pass him. As I finally had the opportunity to pass, I noticed as I was driving by that there was an iPad somehow attached to his steering wheel – that he was reading and tapping while driving.
Interesting? Yes. Unsafe? Yes. Shocking? No.
This really solidifies what we already know as true – mobility is on the upswing at an unprecedented level, even to the point where people are willing to do unsafe things so they can still be connected to their beloved mobile devices – because these devices connect them to the people and information they need.
This is a microcosm of the mobile market today, where business need is finally catching up to consumer demand. So, as mobile grows, the ability to expand the footprint of business solutions grow, and thus utility, usage, and time on device will also grow.
But really the question becomes – what’s the best way to feed the mobile frenzy? What’s the best way to design, build, and deploy mobile applications? Which provides the best UI – mobile app or mobile web?
There are quite compelling arguments for each, and I believe there are key considerations when taking into account SAP aobile apps. There’s the Netweaver Mobile client that allows us to take web or traditional platform solutions and make them compliant from a mobility standpoint. There’s also Sybase that provides a solid foundation to jump start your SAP apps in SUP. Let’s take a look at the pros and cons of each side.
Mobile App vs Mobile Web
300,000. That’s how many apps are in Apple’s App Store. And that number is growing as we speak. Then add in another 50,000 apps on Android and you start to get into a silly numbers game. They’re popular and multi-generational. My 2 1/2 year old knows how to use my iPhone, open up her kid apps, and stay occupied for a while. And I didn’t have to teach her. So there’s no question the popularity and utility is there.
For mobile webb apps and sites the picture typically hasn’t been as rosy. Not so long ago if you accessed a website on your mobile phone that WASN’T an iPHone or Droid, you’d see a white screen background with some blue hyperlinks. Not what I would call a polished UI worthy of building a site on. But the argument for actually doing these low-fidelity screens was because bandwidth was usually low, browsers weren’t advanced enough to support more, and HTML / CSS hadn’t caught up to mobility yet.
But that’s all changing.
We all know that with mobile apps, you get polished UIs, ability to call operating system apis natively ( like camera, or flash), and you get performance boosts from the device hardware. Also native apps provide better performance which is why gaming and entertainment apps are much more prevalent than that of the mobile web.
But there are some cons associated with mobile apps. One of the cons for apps lies in the deployment mechanism of the app store itself (at least for iOS ). It’s very locked down and the time-to-fix / enhancement ratio is days to weeks. So if you’re looking at instant updates or releases, you have to consider this downside. Comparatively a mobile web app has an unbelievably fast deployment mechanism in the web itself. Got an update?. Deploy it now. Enhancement release or bug fix? No problem. Mobile web as a medium to deploy updates to users is fluid and not locked down.
Also consider navigating from app to app or from an app to the web on your smartphone device. When you launch a URL from the app, it will always close the app and opens a browser. This is kind of annoying but there’s really no way around it if you need to bounce around apps to and from the web or other apps. With mobile web, you have the ability to keep the user experience consistent while in the mobile browser, and annoying closes and relaunches will not exist. Food for thought.
Another con with apps is a biggie. There’s a lot of apps. Almost too many to handle. And maybe, even before the end of the year we could be talking about a million apps Apples’ app store and another 200 thousand for Android. That’s very significant. Finding an app is definitely an issue right now, imagine what it will be like in one year. So unless your app is one of the top 20, or your marketing program is off the hook, your app will be buried. “there’s an app for that” could turn from catchy ad slogan to annoying reality.
But its still a very rosy picture for the native app market. The popularity alone is going to drive acceptance and use, thus demand. So mobile apps appeal to users in way’s that mobile web may not. And until mobile browsers on ALL mobile devices and platforms can handle really great HTML5/CSS3 UIs, the market for iOS and Android apps will continue to grow. End there is some prestige involved with mobile apps – personalization, and that little satisfactory thrill when you see a new app icon appear and start loading on your phone desktop screen.
So, right now, mobile apps win out. But, if you are betting on the future of HTML5, than mobile web will become much more prominent as time goes on. They’re not as common as native mobile apps are now, but if you can push the technology to get the UI to look and feel and work like a native mobile app, than they will be. Let’s see what 2011 holds for Mobile UIs and maybe we’ll eventually be able make a choice – mobile app or mobile web.