We should be developing mobile apps now

Barriers to mobile app development are getting so low they are almost non-existent. As web developers today we have no excuse not be creating for mobile. We don’t need to wait for Flash CS5. The tools to create rich, responsive mobile apps for iPhone, Android and Nokia are already available with HTML5. If we have to deploy a native app there are open source tools available to convert web standards like HTML and JavaScript into native iPhone, Android, Blackberry, Palm and Nokia applications.

There are a number of advantages to developing with HTML5 instead of writing native Objective C applications for iPhone. You have probably already heard these:

  • Developing with web technology is much faster than with Objective C,
  • Bug fixes and updates can be deployed instantly,
  • We can utilize our existing HTML, CSS & JavaScript talent.

But what you might not have realised is:

Of course there are still differences between the various mobile devices, but with a bit of tweaking the same HTML5 app can be made to run on iPhone, Android, Palm and Nokia devices because they all use the Webkit browser engine.

Sometimes we might need to generate native applications, to sell the application in Apple’s App Store for example. But even that doesn’t mean we have to resort to Objective C or Java. There is a clever open source tool called Appcelerator Titanium which deploys native applications to iPhone and Android – and we can code them in standard HTML, CSS and JavaScript. Of course deploying as native apps removes some of the benefits inherent to web apps – such as rapid deployment and development iteration. But this approach still dramatically reduces barriers to development. Phone Gap is another open source tool for deploying native mobile applications from standard web technologies. Unlike Appcelerator, Phone Gap supports Blackberry, Palm and Nokia as well as iPhone and Android. However it doesn’t offer as rich of a feature set as Appcelerator. Rhomobile offers yet another framework, but it is targeted towards Ruby developers.

So when you next have an idea for a mobile app, don’t give up on it because you don’t know Objective C or Java, or because it is too difficult to create a cross-platform app. Put your existing HTML, CSS and JavaScript skills to use and take advantage of HTML5 or an open source web-to-native compiler. I will have a play around with Appcelerator and Phone Gap and post my findings on this blog.

Comparison of mobile application development methods

Native apps Web apps Native apps compiled from standard web code
  • Fast, best method for games
  • Easily monetised
  • Slow, separate development process for each platform
  • Instant deployments of bug fixes and updates
  • Can be cross-platform
  • Uses web standards
  • Avoid the App Store gatekeeper
  • Easily monetised
  • Easily deployed to multiple platforms
  • Uses web standards

4 comments

  1. Right on. To me Flash and Silverlight are both rapidly becoming dinosaurs on the path of extinction. Waiting anxiously for the first iphone These Days app ;-)

    Dirk Jumpertz | 3 Feb. 2010
  2. Interesting!
    I’m following the rise and application of HTML5 with great attention.
    Also curious what it will mean in the long run.

    Johan de Keulenaer | 3 Feb. 2010
  3. Excellent article!.. and totally agree.

    Specially that we can use our ability to build web pages which can perfectly run in mobile easily!

    Pablo | 4 Feb. 2010
  4. Very nice article, I subscribed to your feed!

    Just released two medical iPhone apps that I built, but I am not really fond of the iPhone SDK, and most of the features I don’t need. Still in doubt about Flex / Flash future, and GWT seems a bridge too far. I will re-look Appcelerator Titanium after your last blogpost on it.

    Thanks!

    Pieter Kubben, MD
    http://DigitalNeurosurgeon.com

    Pieter Kubben, MD | 4 Feb. 2010

Leave a reply

Switch to our mobile site