Blurring the Line Between iPhone Web and Native Apps

Today, Rogue Amoeba took the opportunity to be among the first developers to express their gratitude—or rather, their sarcasm—towards Steve Jobs for unveiling what they referred to as a complete and terrific iPhone SDK this afternoon, which in reality, did not materialize as expected.

As evident from the flurry of comments that followed, it’s clear that Mac developers are less than pleased. Up to now, the only option for iPhone development involves honing skills in AJAX, Javascript, and Ruby on Rails.

Jobs’ announcement at the keynote that developers would be limited to running web-based applications on the iPhone has only served to deepen the divide, with OS X developers expressing a preference for creating native applications over web apps.

Further discussion in the Rogue Amoeba thread by a commenter named Joe highlighted a shift in perspective: web apps are increasingly being recognized as legitimate applications. This notion is further supported by Apple’s release of Safari for Windows, suggesting that the future of cross-platform compatibility might indeed lie within the browser.

This development is a boon for web developers, who suddenly find themselves as the new official iPhone developers.

However, this approach is not without its drawbacks. Mac developers who are keen on crafting applications for the iPhone might find themselves revisiting their old Javascript books.

Scott

Brian is a dedicated writer for TUAW, where he shares his insights and expertise on all things Apple. With a deep love for technology, Brian covers a wide range of topics, from the latest iPhone and iPad releases to the intricacies of macOS and Apple Watch features. His clear and engaging writing style makes complex tech topics accessible to all readers. Brian’s enthusiasm for Apple products shines through in every article he writes.