Skip To Content
BuzzFeed News Home Reporting To You

Utilizamos cookies, próprios e de terceiros, que o reconhecem e identificam como um usuário único, para garantir a melhor experiência de navegação, personalizar conteúdo e anúncios, e melhorar o desempenho do nosso site e serviços. Esses Cookies nos permitem coletar alguns dados pessoais sobre você, como sua ID exclusiva atribuída ao seu dispositivo, endereço de IP, tipo de dispositivo e navegador, conteúdos visualizados ou outras ações realizadas usando nossos serviços, país e idioma selecionados, entre outros. Para saber mais sobre nossa política de cookies, acesse link.

Caso não concorde com o uso cookies dessa forma, você deverá ajustar as configurações de seu navegador ou deixar de acessar o nosso site e serviços. Ao continuar com a navegação em nosso site, você aceita o uso de cookies.

The Problem With Chrome For iOS

Don't get me wrong, I would love Chrome on my iPhone and iPad. But Chrome for iOS isn't really Chrome — it's a much slower version of Mobile Safari.

Posted on June 28, 2012, at 2:24 p.m. ET

Facebook revealed yesterday that it is finally making a real, fully native iOS app. Until now, Facebook's app has been based on web tech — it's a browser and a mobile site inside of a blue-colored wrapper, basically. So why the sudden change of course? Because in-app browsers are required to suck in iOS. And barring some kind of special exemption, it's virtually guaranteed the Chrome for iOS will have to use the same slower browser engine that Facebook has been suffering with.

Mobile Safari, the default browser in iOS, uses a Javascript engine called Nitro, which in turn uses a technology called "just-in-time" compilation, or JIT, to execute scripts more quickly. The technical details aren't too important here — John Gruber has a good explanation here, if you want it — but the effects are. JIT makes Nitro faster, and Nitro makes Mobile Safari faster. This is great, if you're using Mobile Safari.

But other apps that want to include a browser function, be they Facebook or an actual alternative browser like Chrome, don't get Nitro. And developers can't use their own engines, either. For security reasons, the browser developers get to use in their apps is a variant of an older, pre-Nitro version, called UIWebView. Here's how Apple describes it:

You use the UIWebView class to embed web content in your application. To do so, you simply create a UIWebView object, attach it to a window, and send it a request to load web content.

It's fine — it renders pages with the same fidelity as Mobile Safari. But this is what all alternative browsers in iOS are forced to use. And it's slower. Noticeably slower. Here's how Mobile Safari and the Facebook app compare in a Javascript benchmark:

Loading a page is about more than executing Javascript, and this benchmark is allllll about Javascript, but the Facebook app runs it at about 1/4th the speed of Safari — a stark difference. And modern pages, particularly appy mobile ones, have a ton of Javascript. So this will make a big difference.

The ability to sync bookmarks and history, and to use Incognito Mode, is certainly useful, and the prefetching feature will help speed things up. And I generally like the choices Google has made with the Chrome interface elsewhere. But the best thing about Chrome on desktop is that it feels faster than every other browser, and Chrome on iOS almost certainly isn't going to have that.

Update: Yeah, it's way slower than Safari

Browsing feels fairly snappy, but certainly slower than Mobile Safari. Most damning is Gmail performance. In Chrome for iOS, it's a bit choppy. In Mobile Safari, it's much smoother.

A BuzzFeed News investigation, in partnership with the International Consortium of Investigative Journalists, based on thousands of documents the government didn't want you to see.