HoTWiReZ's DoMaiN

[News BoT]

<p align="center"></p><p><p>
Earlier today, Google announced Chrome for iOS (iPhone and iPad), and thanks to Richard Gaywood finding a&nbsp;direct link&nbsp;to the App Store, I got the chance to play around with it in-between a busy schedule of sessions and meetings at I/O 2012. Chrome on iOS weighs in at 12.8 MB and is version 19.0.1084.60.&nbsp;</p>
<p align="center">
<img alt="" src="http://images.anandtech.com/doci/6060/Photo Jun 28, 1 18 03 PM_575px.png" style="width: 250px; height: 375px; " />&nbsp;<img alt="" src="http://images.anandtech.com/doci/6060/Photo Jun 28, 1 17 39 PM_575px.png" style="width: 250px; height: 375px; " /></p>
<p>
Earlier I had a glimmer of hope that Apple had relaxed the App Store rules to allow Chrome as a real native application on iOS, complete with its V8 JavaScript engine and newer version of WebKit (535.19). Unfortunately, as suspected, Chrome on iOS uses iOS' UIWebView, which means the same rendering engine as mobilesafari. On my iPhone 4S running iOS 6 B2, you can see the same user agent string (with the Chrome OS version tacked in between some other things) shared between mobilesafari and Chrome.</p>
<div align="center">
<table align="center" border="0" cellpadding="0" cellspacing="1" width="575">
<tbody>
<tr class="tgrey">
<td align="center" colspan="8">
iOS MobileSafari</td>
</tr>
<tr class="tlblue">
<td width="120">
Location</td>
<td align="center" valign="middle" width="85">
WebKit Version</td>
<td align="center" valign="middle" width="85">
HTML5test.com Score</td>
<td align="center" valign="middle">
CSS3test.com Score</td>
<td align="center" valign="middle">
Sunspider 0.9.1</td>
</tr>
<tr>
<td class="tlgrey">
iOS 5.1.1</td>
<td align="center" class="text" valign="middle">
534.46</td>
<td align="center" class="text" valign="middle">
324 + 9</td>
<td align="center" class="text" valign="middle">
52%</td>
<td align="center" class="text" valign="middle">
2226.1</td>
</tr>
<tr>
<td class="tlgrey">
iOS 6.0 B1</td>
<td align="center" class="text" valign="middle">
534.46</td>
<td align="center" class="tlgrey" valign="middle">
360 + 9</td>
<td align="center" class="tlgrey" valign="middle">
57%</td>
<td align="center" class="tlgrey" valign="middle">
1842.9</td>
</tr>
<tr>
<td class="tlgrey">
Chrome for iOS (on iOS6 B2)</td>
<td align="center" class="text" valign="middle">
534.46</td>
<td align="center" class="tlgrey" valign="middle">
<strong>360 + 9</strong></td>
<td align="center" class="tlgrey" valign="middle">
<strong>57%</strong></td>
<td align="center" class="text" valign="middle">
6839.4</td>
</tr>
</tbody>
</table>
</div>
<p>
In addition, like other apps leveraging UIWebView, there's no access to mobilesafari's Nitro JavaScript engine which has JIT and other optimizations that make it run much faster. That means JavaScript execution is significantly slower inside Chrome on iOS than it is in mobilesafari.</p>
<p>
<div>Gallery: Chrome on iOS Gallery<div></div></div></p>
<p>
On the positive side, the Chrome interface is pretty much exactly how it appears on Android, including the nice tabbed card switcher complete with the ability to close and switch tabs by swiping off the edge of the screen. Scrolling around inside webpages is also nice and speedy on Chrome for iOS, which isn't a &nbsp;surprise since, again, it's using UIWebView. The real feature in Chrome for iOS sadly isn't a superior browsing engine, but rather the ability to sync your tabs, pages, and back history across the desktop and more mobile platforms.&nbsp;</p>
<p>
<strong>Update:</strong> As NobleKain points out in the comments, there's a discrepancy between WebKit versions between iOS 6 B1 and B2. B2 is now running 536.13, but WebView remains 534.46. Either way for users running iOS 5.1.1, these should be the same, I just unfortunately only have a device on me running the beta, hence the discrepancy.</p>
</p>

Read more...

Source: AnandTech
This channel features the latest computer hardware related articles.