Android & iPhone App Design: Is it twice the work?

This was mentioned in the article of course, but it bears repeating. I don't think there's any way around doing extra work when you target another platform. The UX guidelines for the Android and iPhone are different and you want to work within those guidelines.<p>HTML5 may be a way out of this, since the user is in a different contextual frame of mind, but if you want folks to think it's an "app" then you should still be aware of (and target) specific UX recommendations.

I'm inclined to think that eventually html5 "apps" will largely displace native apps for the same reasons so many desktop functions have migrated to the web. The porting issues this article describes are just some of the many disadvantages of native interfaces.

Looks like an interesting article. It's too bad some of the text is hidden behind ads (Chrome 6 beta/Win7).

Not if you make a slick html5 mobile version instead.