Google tricks Chrome users for data?

Google Chrome is available for the public. This might be a very important step for the next generation web experience. However, the part that got my attention is different and I wish to discuss it.

Here is the screen shot of the download page of Google’s new browser. As you can see, optional checkbox which allows Google to gather your data is located at the same location as “I read and accept” checkbox that every user checks without even reading it.

Even though making “optional” keyword bold a is gesture of good will, I think it is a little tricky to put it on the same exact location where most of the users are conditioned to auto-check. What do you think ?

Once you have checked that box, Chrome installation comes in with pre-configured to gather your data. of course, it is still available to opt-out. And if you do not check the box, Cohrome will ask you one more time to enable it at the first time you launch the browser.

As I have previously discussed the importance of such data in the post: Social Data War , it is quite understandable why google deeply wishes people to share their data. Considering this browser is a step for next generation web experience (web-os), it is acceptable to assume that gathering data is an important portion.

Conclusion: Google is watching you. Google is wise 🙂


5 thoughts on “Google tricks Chrome users for data?

  1. my suggestion to whom that “loved” google chrome, and thinking that it is the next big leap to the browser history: Use Safari, or Opera, then you’ll find out the source of “Chrome” inspiration.

    Google is evil, open your eyes.

  2. Meric,

    I dont’t believe with the current situatuon of Chrome, it can be considered as a huge step, however I believe that their point of view to browser concept will make some other developers think. I mean the process-per-tab and js thing. Since it is opensource, it is easy to be ‘inspired’ by chrome.

  3. But there is a point that you’re missing dennis, that “js” thing is really awesome, but there is something going on the safari and ff side that is not made public yet. everybody knows that both companies are running new javascript engine (and testing them in closed betas) projects. I think the -real- benchmark results will be granted when we’ll find a way to use the new engines, besides, the sum of “process-per-tab” memory usage is much more than firefox and safari. (i cannot compare it to safari).

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s