updated 06:45 pm EDT, Tue March 15, 2011
Is it a bug, an early omission, or a conspiracy?
In addition to the unavailability of Nitro for non-Safari web usage, iOS 4.3 also lacks web app caching, even HTML5 application caching, meaning they can't be run offline (although this was actually a change implemented in iOS 4.2). Further, the new version also makes web apps run in "synchronous mode" rather than the newer "asynchronous mode," which can affect graphics performance in full-screen mode. Overall, the bottom line is that web apps run noticeably slower and "choppier" in iOS 4.3 compared to the now-boosted performance of Safari or native apps.
Various conspiracy theorists -- including some developers -- speculate that this could be a deliberate move by Apple to make web apps unattractive, encouraging users to stick to native apps (where, if the app costs money, Apple receives a 30 percent cut). Others believe the changes are simple bugs or oversights that will be addressed in future revisions of iOS 4.3.
The dropping of offline caching and keeping web apps in synchronous graphics mode, however, seem more like omissions: the question is whether they are deliberate, or just overlooked in the rush to get iOS 4.3 out. Developers have filed bug reports and spoken with the MobileSafari team about the issues, but no official explanation has yet been issued. The "bugs" also can also affect native applications that use Apple's own UIWebView API to offer "in-app browsers" that act like Safari but actually aren't.
Although some developers in the Register story suggest that Apple will not fix these issues -- at least not immediately -- the impact on native apps that rely heavily on the web for updates (such as UrbanSpoon, Facebook, Ebay and Apple's own MobileMe Gallery app to name just a few) makes it unlikely that the problem will be ignored.
While there is a motivation for Apple to de-emphasize web apps' popularity -- in that they completely bypass the App Store -- commenters on the Register story correctly point out that most "web apps" are free (and a small percentage of the overall app market), meaning no loss of revenue and no real incentive for the company to expend any effort to weaken their limited appeal. Apple's iOS is still the only mobile platform that even offers full-screen web apps, or the option to make a website (such as MacNN.com) into a "web app" saved to the home screen.
O'Reilly author Maximiliano Firtman, one of the first to raise the issue, has published tests showing that iOS 4.3 runs web applications in the browser more than twice as fast as those outside the browser, but also posted that he does not believe it is any deliberate attempt by Apple to hinder the hybrid/HTML5 frameworks.
Firtman points out that web apps under iOS 4.3 run at roughly the same speed they did before -- they just don't (yet) take advantage of Nitro, which makes them look slow by comparison to in-browser web apps that do have that benefit. The caching issue and the synchronous mode are other factors that Apple will likely address in developer forums, but as more discussion and testing are done it appears likely that sabotaging full-screen web app performance was more likely an unintentional rather than deliberate act.
However, Firtman suggests that if Apple doesn't quickly address the issues, Google's Android community should -- as it would give them a new area in which to be competitive. [via The Register]