The Argument

The argument is that from the user’s perspective, having to download an application kills the experience, and that people just won’t download.

Yes, it is a pain to download, but it is not a killer.

People will download applications as long as the application brings the right value or makes a difference. A good example of this is Jaiku, the popular social application that needed to be designed as a local application due to the needed integration with the handset’s functionality for presence, messaging and other.

I wonder how many Jaiku users exist, as that number would help understand (and defend or not) this argument about downloading local applications. It is important to realize though that Jaiku users are mobile-sophisticated-kind of users, and probably don’t represent the “critical mass”. BTW, not bad for a local application (and related services on the web) to get acquired by Google — congrats to the Jaiku folks. I always thought that Jaiku gets it.

A Solution is Needed

Downloading local application is the #1 problem from the usability perspective that must be corrected. If people can’t download the application and past that step, who cares about the rest of the issues: fragmentation, portability or whatever. Downloading must be easy, and must work: 1) to find or share the application, 2) to download, 3) to bill (if applicable). This goes inline with bullet #4 and #5 in Tim Bray’s message to the network carriers – Flat Rate Considered Harmful:

4. Build a developer ecosystem. Make it effortless to get in. Build a hot-new-apps social network; maybe in alliance with one of the big existing social nets.

5. Don’t ask developers for any money. But sell the use of your billing system at a really attractive rate, so people can sign up for apps and have it billed to their phone plan. Do it at a scale that an app can charge a dime a month and still make money on scale.

The New Model for Mobile Applications

I am still looking forward to the hybrid or lightweight application model, this is, the integration or convergence of (mobile) web technologies with access to local functionality, perhaps a new type of browser run-time with the (scripting) libraries for/to access local functionality (or even the Java APIs). The Java ME specification JSR 290 kind of started with this path. Recently I learned about Aplix’s JSX. Perhaps Google will be the one to deliver this new model for mobile applications. Will we encounter in this new model the same security issues and paranoia from network carriers that we see today with local applications? Very likely the answer is Yes.