All Posts Filed in ‘Mobile

Post

When Web App > Native App – on launching things

For the most part, application designers and engineers are drawn to native application because it allows full access to the hardware features and native user experience. In the end, you’ll ended up with prettier, more responsive, and easier to use application.

But one of the big advantage of Web app over native app is the easy of quick deployment, and potentially roll back of features and functionalities without going through the application marketplace (ie iTunes or Google Play).

One might also notice whenever you download a major update of your beloved application (say a 2.0 version of the app) there’s usually is no turning back to the old 1.0 version of that native app. Usually, you can’t have the same app installed side by side.

On the other hand, many large scale Web apps usually can accomodate a “try before you buy” UX. Users are encouraged to try the new UX before fully by-into the new features and user experience. I have yet to see any native app (either on PC or mobile) that does something like: ask the user to try a new version of the app (that’s a separate download and a new binary), and encourage the users to submit feedback before the official roll out of the major update. It’s an extra layer of work for the team but this is something worth experimenting for many larger organizations.

Post

Fragmentation of the Mobile UI

After watching this impressive video demo of HTC Sense UI for Android, it got me start thinking about the fragmentation of the Mobile UI.

Due to the open source nature of Android, heavy customization of the UI is to be expect. This type of heavy customization of mobile UNIX/Linux UI reminds me of the crazy varieties of the UNIX interface of the 1990s. Anyone still remember the different versions Motif, Gnome, KDE, Solaris, etc?

I am afraid we’re entering a very similar era with the Mobile UI.

“Classic Android” (Google Phone), HTC Sense UI for Android, Palm Pre’s WebOS, Symbian S60 Touch, etc. the choice are limitless. These ‘next gen’ UI are powerful, but yet difficult to use. They also require the users to relearn how things operate from handsets to handsets.

Imagine developer has to port popular mobile service to at least 5 different handsets’ OS. Imagine users switch between handsets and they have to relearn their favorite apps (i.e. Twitter client or Web browser).

I am aware of the great hope of HTML / JavaScript driven mobile-web apps (or even OS) that will “rule them all”. These solutions are (technically) sound for both the users and developer, but in reality, if you want to deliver top notch user experience, some middle of the road solution rarely works…

The PC Revolutions happened because we actually have limited choices. Macs or Windows (95 in particular). The next 3-5 years are critical for these Mobile OS. For mobile to succeed, natural selection has to occur. We’ll end up with no more than 3 different major mobile OS. Mark my words.

Post

iPhone 3G Hong Kong Usage Data

ePrice (fomerly PhoneDaily) posted an interview with Hutchison 3 Hong Kong in regarding the iPhone 3G services in Hong Kong.

The original interview is in Chinese, and focus on the poor iPhone 3G services (both data speed and call quality) in Hong Kong region.

Complains aside, Hutchison 3’s CTO Daniel Chong revealed some interesting iPhone usage stats of the region. On average, iPhone data usage is 10x of most smart phones. Compare with specific handsets, iPhone data usage is 6x of HTC Diamond, 10x of Nokia N95 8GB, 42x of Sony Ericsson W901i.

Compare with regular 3G handsets, iPhone 3G users are also fan of the Hutchison 3 portal. Over 32% of the iPhone 3G users use the official Planet 3 mobile portal with rougly 2.35 million impression since the release of the handset. The usual popular content are news, weather, and finance, etc.