4 ms·
How is Apple deliberately hampering performance for web apps? What evidence is there for this?
by fjarlq 14y ago
How is Apple deliberately hampering performance for web apps? What evidence is there for this?
- mille562 14y agohttp://www.tuaw.com/2011/03/18/apple-confirms-some-webkit-optimizations-unavailable-to-ios-apps/ http://www.tuaw.com/2011/03/18/apple-confirms-some-webkit-op... The discussion is about apps written natively vs apps written in HTML (not web pages viewed in safari). The only method available to develop an iOS app with HTML is to use UIWebView, which is crippled compared to Safari.
- MaxGabriel 14y agoHe's referring to web apps that are embedded inside a native wrapper. UIWebViews don't use the more performant Nitro JS engine.
- girvo 14y agoDue to security concerns, JIT (also known as "Nitro" in iOS parlance) is disabled for UIWebViews, but is enabled in the browser itself. I assume that is where this is coming from.
- woadwarrior01 14y agoI guess he's talking about javascript JIT being enabled in Mobile Safari, while not being enabled for apps using UIWebView.
- deleted 14y ago[deleted]
- monsterix 14y agoThere is some evidence for sure. For example, iPad Safari doesn't allow full-screen mode, nor implements fullscreen API as per standards. Another browser on the iPad (Dolphin) supports it interestingly. Support for ordinary CSS properties like z-index, position:fixed and iframe is pathetic. Some of the things that I can recall now. UIWebView takes it to another level of pain altogether.