The Web Browser

The iOS UI isn't the only area that doesn't get an update with the iPad 2, the core apps also remain untouched. Mobile Safari on the iPad 2 is effectively the same browser used on the iPhone 4, just on a larger screen.

Web page compatibility is generally pretty good on mobile Safari, with the obvious exception of any website that requires Flash. Apple continues its firm stance on not supporting Flash and hoping the rest of the world will convert to HTML5 or iOS apps. I'm personally not a huge fan of Flash, however I do believe the lack of Flash support is frustrating on the iPad. For most usage it's not a problem, but missing Flash is yet another reason why the iPad can't be an exclusive travel companion for me. There are still far too many niche sites out there that require the use of Flash. And if I'm in a hotel room with only iOS devices and no notebook, not having anything that can run Flash is a problem.

I ran two compliance tests on mobile Safari: Acid3 and the HTML5 Test. Acid3 is near perfect with the exception of an errant box in the lower right hand corner of the final test image:

In practice I have noticed more rendering errors and browser issues in Honeycomb than I have under iOS 4.3. There's one particularly nasty Honeycomb bug that I've encountered several times that prevents web pages from loading entirely until you kill the Browser process and restart it.

In iOS 4.3 Apple increased the performance of its JavaScript execution engine significantly. The result is pretty astounding. According to SunSpider the iPad 2 is now slightly faster than the Motorola Xoom, however BrowserMark puts the Xoom well ahead of the iPad 2. Google is extremely adept (and aggressive) at optimizing browser performance, this is one area where I'm not entirely sure how well Apple will be able to keep up in the long run.

JavaScript execution is only one aspect of the total performance equation however. Scrolling smoothness has been a staple of iOS and the iPad 2 does not disappoint here at all. Google made huge improvements in going to Honeycomb, but browsing in iOS is still smoother on the iPad 2.

Web page loading performance also proves to be quicker on the iPad 2, although given Google's advantages in BrowserMark it's clear that this won't be the case for all web pages.

Performance isn't everything when it comes to web browsing, and one area where Google maintains a significant advantage is in its support for tabbed browsing. Mobile Safari still requires that you tap once to bring up an array of browser windows and then once more to select the window you want to view. Apple limits you to a total of 9 browser windows.

The web browser in Honeycomb on the other hand implements tabs just like a desktop browser. Tabbed browsing has a profuse impact on usability, not unlike what we saw on the desktop (when was the last time you used a browser without support for tabs?). The fact that Apple still hasn't implemented tabbed browsing on the iPad is unacceptable.

Apple handles all memory management within mobile Safari for you, so if you happen to leave too many windows open and the iPad runs out of memory iOS will simply evict some of those web pages out of main memory. On the iPad 1 this was more of a pain as it only had 256MB of memory and a 1GHz Cortex A8 CPU, web pages were evicted more frequently and took longer to load when you went back to them. The iPad 2 doubles memory size to 512MB and loads web pages around 50% faster than the original iPad - making the experience much better overall.

The UI & Honeycomb Comparison FaceTime & Photo Booth
Comments Locked

189 Comments

View All Comments

  • PeteH - Saturday, March 19, 2011 - link

    In the Garage Band section:

    "There are three Smart Instruments - Piano, Bass, Guitar, and Drums."

    I'm pretty sure that "three" should be a "four."
  • VivekGowri - Sunday, March 20, 2011 - link

    Ahaha, I'm an idiot - thanks for catching that, it'll be fixed.
  • PeteH - Sunday, March 20, 2011 - link

    As far as typos go that one isn't remotely bad. I once published a spec (internally) that had a section detailing how asynchronous boundaries were handled in my section of a chip. Unfortunately I had titled that section "Cock Domain Crossings."
  • Anand Lal Shimpi - Sunday, March 20, 2011 - link

    A few years ago I used the word overcocking instead of overclocking in an article.
  • UNLK A6 - Saturday, March 19, 2011 - link

    I'd like some clarification about LINPACK and Geekbench. Are these benchmarks created by compiling some portable code for each platform as a measure of floating point performance? Or, is this supposed to be some measure of how fast one can do linear algebra or DSP on the platform? On Mac OS and iOS, one wouldn't compile say LINPACK for this but use the hand-tuned LAPACK/BLAS and DSP routines built into Apple's Accelerate Framework. The difference between the two can be huge. Which do these benchmarks purport to supply--generic floating point performance or available linear algebra and DSP performance on the platform?
  • metafor - Sunday, March 20, 2011 - link

    I believe Linpack on both iOS and Android are plainly compiled (by the JIT in the case of Android) to run on the platform. They don't make any calls against the onboard DSP's nor do they use NEON beyond what the compiler is able to auto-vectorize.
  • name99 - Sunday, March 20, 2011 - link

    Apple supplies all the Linpack routines in optimized NEON code as part of the OS (in the Accelerate framework). Intelligent apps that need them use those routines.
    Android, as far as I know, does not provide an equivalent.

    You can use apps that deliberately bypass these iOS routines if you wish to get a handle on the raw FP performance of the hardware, but
    (a) it doesn't give actual linear algebra performance, if that is something your app or algorithm really cares about AND
    (b) it's kinda dumb because if you care about fp performance in any way, you'll be using NEON, so what's the value in a benchmark that doesn't exercise NEON?
  • nimus - Sunday, March 20, 2011 - link

    I hope AnandTech can do a comprehensive comparison of the usability/feature strengths between the Android, Apple iOS, BlackBerry Tablet OS (QNX), HP webOS, and any others tablet OSes.

    It will be interesting to see how the Windows Tablet OS will be able to compete when it finally is released for ARM processors.
  • KidneyBean - Sunday, March 20, 2011 - link

    I'm using a tablet, so I can't see the mouse-over pics :-(
  • tcool93 - Sunday, March 20, 2011 - link

    I don't know where the reviewer gets the idea Netbooks are much faster. That is nonsense. Here is a video showing an ARM 9 processor being just as fast, yet the ARM 9 processor is running 1/3 the speed of the Netbook Atom. (500mhz vs. 1600mhz for the Netbook).

    http://www.youtube.com/watch?v=W4W6lVQl3QA&fea...

    The Netbook also has a graphics accelerator in it, and the ARM shown in this video doesn't.

Log in

Don't have an account? Sign up now