For example, the PhoneGap open source framework bundles HTML into hybrid apps for five platforms: iOS, Android, BlackBerry, Symbian, and WebOS. The creators worked with Apple to scrutinize the code and as a result Apple will look only at the HTML and other features you add during its app approval process; it has essentially preapproved the PhoneGap code.
The downside of the Web approach for mobile Building smartphone apps with HTML is a fairly painless way to create cross-platform applications that can tap into the deeper parts of the native API. I've built several applications this way and found that they usually worked on both iPhones and Android smartphones with no changes.
Still many of the complaints of mobile developers who write in Objective-C or Java also revolve around juggling resources. The little handsets have so much less memory than desktops and it's always a challenge to deal with them, whether you're doing native or Web app development. Don't take the issues I raise as being reasons to try the Web app approach. After all, the several hours you might spend monkeying with CSS is nothing compared to the years that some people have devoted sweating with pointers and memory issues. For the hours of work they take, the HTML apps can be stunning successes.
This article, "Escape the App Store: 4 ways to create smartphone Web apps," was originally published at InfoWorld.com. Follow the latest developments in software development and mobile technology at InfoWorld.com. For the latest business technology news, follow InfoWorld.com on Twitter.
Read more about developer world in InfoWorld's Developer World Channel.
This story, "Escape the App Store: 4 ways to create smartphone Web apps" was originally published by InfoWorld.