Over the last few years include Google, there is one question that seems simple that appears again and again, that Google just could not answer. Why Chrome is not part of Android?
Most of the time, it was just a question to wonder why a very popular web browser Google is not part of a very popular operating system on their mobile? After all, the OS has a browser (the aptly named "Browser"), but not Chrome. Why not?
the question arises once again at the Google I / O last week. During the panel with a group of engineers at the Chrome team, it was one of the first questions asked. Feedback? "This is not something we talk about now." Ouch.
Based on my understanding, the Android team is a completely separate team from the Chrome team. Second, this branding problem that Google is not sure how to finish. Third, the Android browser, the same as Chrome, Chrome does not actually.
Google executives keep saying again and again when asked last week, both OS have different goals - and the things in very different ways. While Chrome may have started out as a web browser, is now much more from the perspective of ideology in Google. No one will admit this, but if they were to finally succeed, they like to believe that Android will not. Which makes it difficult to work together.
When Android was first launched in October of 2008, seemed either small or supervision of preventive measures, combined with a browser that is not labeled as Chrome. After all, the browser Google has just launched in beta version (on Windows) the previous month. assuming people like it, you would assume that Google will transfer over to be used in branding Android, right?
It is true that people such as Chrome. Plenty. However, Google does not ever move on top. This is despite the fact that Apple did just that on the iPhone with the Safari browser which is much less successful. Meanwhile, Opera and Mozilla Firefox has been committed to the mobile version of their popular browser. But Google's stuck with the "Browser" for Android.
And now they're probably stuck with it for good. The problem is that Chrome, for better or worse, is now linked with other similar products but different from Android - again, Chrome OS. Imagine if they started including the Chrome browser on Android tablet and then next year the launch of Chrome OS tablet. Consumers will be wondering what's the difference? (And this may have proved to be a problem on a PC / Chromebook side of things, we'll see.)
All that aside, it is still important to remember that Android is not really Chrome Browser. Both are both based on WebKit and uses Google's V8 JavaScript engine, but there are dozens of other features that Google is trying to associate with Chrome that they could not squeeze into the mobile web browser (at least not yet).
The same issues are true with Apple's Safari browser and a mobile their regular. But browsers generally appears to be less feature-focused, so the brand may be not as big of an issue. Plus, even if both sides do not cooperate in the Apple (although it seems like they might be), does anyone really believe there are in hell Steve Jobs will let the browser in the IOS is called anything but Safari?
Back to Google, on the other side of things, the Android team has their own wants and needs for the browser bundled with their software. And imagine if the problems in the Chrome team playing for a new build of Android? Or vice versa?
But with the launch of Honeycomb, Android Browser now starting to look more like Chrome too, thanks to the experience it offers tabbed browsing. This will only lead to more questions. And that's just a matter of time before users began to demand that the elements completely synchronized between the two (Chrome and Android Browser).
At that time, Google may have to consider this question once again. Is it time to take Chrome for Android?
(Source techcrunch.com/)
