top | item 4188113

Why Google Chrome on iOS stands a chance

16 points| surdattack | 13 years ago |blog.cleartrip.com | reply

23 comments

order
[+] shangaslammi|13 years ago|reply
Misses the most important point: syncing.

I don't know about the masses, but at least that was the biggest reason in my circles why people were excited to have Chrome on iOS.

[+] preavy|13 years ago|reply
Not only does Chrome on iOS sync bookmarks, but it allows you to see what tabs are open on Chrome on all your other devices and what tabs were last open on devices which are currently switched off.
[+] ZeroGravitas|13 years ago|reply
Sync is the best feature for Firefox on Android too, it makes all the other bugs and oddities worth dealing with.

It makes me wonder about how many iPad users have Android phones, or iPhone users with Windows (or even Linux) machines, or iPhone users with Nexus 7s etc., you get the idea, anyone not fully inside the Apple sphere is probably going to get a lot of benefit from unifying browsing across platforms.

[+] rcruzeiro|13 years ago|reply
Yes, definitely the sync was the feature I have been looking forward too. It's a shame that Apple is taking so long to develop their on syncing (just like they're taking their time developing a lot of thing that could be branded an iCloud service).
[+] surdattack|13 years ago|reply
Shangaslammi Agreed.

Reason #4 has everything to do with this!

[+] mcherm|13 years ago|reply
Why Google Chrome on iOS doesn't stand a chance: because if it succeeds, Apple has the power (and inclination) to simply block it.
[+] herval|13 years ago|reply
which app have they reportedly blocked after it succeeded?
[+] pooriaazimi|13 years ago|reply
> 5. Chrome will prove to be more developer friendly.

I love V8 infinitely better than Apple's JS engine, but you can't say Safari is less developer friendly than Chrome.

Safari 6 has much more developer tools now (detailed timeline of element renders & JS timers/dispatches), in a nicer package. And, the new Web Inspector in iOS 6 is absolutely marvelous! You open the webpage on iPad and inspect it on Safari's new web inspector (and you can tap on different elements to inspect them, just as you can do in FireBug).

http://adrielservice.com/blog/?p=894

http://taitems.tumblr.com/post/24936855546/what-ios-6-mobile...

[+] adhipg|13 years ago|reply
> You open the webpage on iPad and inspect it on Safari's new web inspector (and you can tap on different elements to inspect them, just as you can do in FireBug).

That's true of Chrome on Android and even RIM's Playbook with Chrome Developer Tools. There's even talk about Chrome trying to get that working with it's versions on iOS.

> Safari 6 has much more developer tools now (detailed timeline of element renders & JS timers/dispatches), in a nicer package.

The nicer package there has been the biggest problem. I still haven't been able to figure out what all those icons mean. The simplest 'Elements' view (highlight elements to inspect them) now needs to be enabled after three clicks and a lot of time spent hovering over the icons to know that you have the right one. Safari 6's developer tools seem to be designed by designers who don't use developer tools IMHO. It's very pretty but lacks any sort of usability.

[+] taligent|13 years ago|reply
Hilarious on every point.

1. If the web browser is redundant then would would anyone make the effort to download Chrome. Nice self-contradiction here.

2. Safari in Mountain Lion has a single URL field with predictive search just like Chrome. So it could be an upcoming feature for iOS6 for all we now.

3. I fail to see what technology apart from maybe SPDY Google has "invented" that allows it to be so dramatically faster than Safari that it can compensate for the loss of JIT. Especially when benchmarks today show Chrome to be pretty slow.

4. Taking the top spot in the App Store is no big deal especially for free apps. There's been some incredibly stupid and pointless apps that have shared that position. Quick. Stop the press. The Talking Ted app is now number 1. Is there something profound to be said about humanity because of that ?

5. This is my favourite. Apple contributed the WebKit DOM inspector that Chrome has been using. And the new one in Safari now is much more "developer friendly" than Chrome.

[+] rrreese|13 years ago|reply
Regarding point one, if I understand correctly the author means that since most apps open in their own web view rather then opening safari directly the fact that chrome can't be integrated is less of a problem.

The browser is not redundant, as people start it when they want to browse to some random page.

For me I don't agree, I open safari from apps all the time, so lack of integration pretty much guarantees that I won't be using chrome.

[+] codeka|13 years ago|reply
> Especially when benchmarks today show Chrome to be pretty slow

Do you mean Chrome on iOS or desktop? Which benchmarks are showing Chrome to be pretty slow?