Shared publicly  - 
Trent Archer's profile photoChristopher Bajor (FtLauderdood)'s profile photoRoss Byrne's profile photojustin leboutillier's profile photo
Id much rather have a wacom (or similar) screen.
Could this be the beginning of the eventual merging of Android and Chrome? 
if google got something, it better cook it fast..
Have to be convertible into a tablet if it's going to sell. 
Can I start a rumor? Maybe the reason it is called "link" is because ChromeOS and Android are going to be married in a deep and loving way... You know "linked" together?
Touch based laptop is like a fish on a bike, chrome would need to converge with android but even then if needs to be something that splits to a tablet. I think a solid chrome book with decent stored low price and a very high quality feel could be a winner. Cheap is already a winner but not everyone wants it to feel as cheap as current models do
+Joseph Hurtsellers +Ben Ferguson  Unlikely. I obviously don't know for sure and have no inside knowledge and cannot predict the future etc, but below is my reasoning why I don't think that a merge will ever happen.

Google makes far more money off of the open web than it does Android applications and almost all of their services started out on the web or have far more functionality through the web-based client.
A native application store model doesn't favour Google in the long-term because it results in user lock-in (which means they can make less money, see above) and requires that they develop more than one version. If a well-made web app is made, it can work well on different screen sizes and it doesn't matter what hardware the user is on, for the most part.
Additionally, an Android-Chrome merge would basically be a Chromified Android application launcher. You may as well just make Chrome for Android good and ditch Chrome if that was the case.

Perhaps most importantly of all, it's just not where the world seems to be heading. Yes, of course, native applications such as those found on Android, Windows and other operating systems can do more. But the web is getting better all the time. We have document editors, video editing, great games (via Native Client technology) and new technology such as WebRTC coming out frequently. If a developer or company can make their application work on the web, they can increase their total addressable audience (get more users) because it doesn't matter if you're on iOS, Android, Windows or Mac. It just works. That means more users and more revenue.
Though native applications are more capable, the web is improving all the time and it's getting no more difficult for the user.

Android is incredibly-popular right now and there are good reasons for this. However, I think the reasons above (and the falling cost of materials and Google's willingness to sell devices at cost to push in order to Chrome OS) will ultimately result in Chrome OS being the more popular operating system in the coming years.

Finally, security, simplicity and speed.
Though Android is great and I like it very much, adding Android compatibility to Chrome would make devices running such a combination slower, more complex and less secure. Sure, you'd get more functionality, but as I've previously stated, the web (web applications and technologies) are getting better all the time and they're extremely-simple for the end user. Reducing security and adding complexity for the sake of adding support for Applications that develops would need to rebuild (in many cases) doesn't make for a simple (or good) user experience.
+Khalid Boutin but doesn't everyone agree that mobile has a lot more growing to do? Google is dedicated to improving the mobile experience and at the same time they want the chrome book to get more exposure. Seems like a two birds one stone deal if you ask me.
+Khalid Boutin I think you have some very good points but I find there to be one big flaw, in that you seem to have assumed ChromeOS would be rolled into Android or something, instead I still view them as separate entities, but with a lot of cross over, being able to use web apps through chrome on android for instance, or unified notifications, unified contacts, Google. Instead of Android becoming a larger part of Chrome OS I see Chrome OS becoming a larger part of Android. I do see the industry headed that way. Making Android a bit closer to Firefox OS and Chrome OS where the power of the Web is leveraged more and more.
+Christopher Bajor For now, yes. But if Chrome OS starts to make more sense (if, say, it could deliver a really great user experience on a smaller screen - such as a phone) then Google would focus on the more useful operating system.

I think that although native applications will always likely be more capable, Google is focused on Android right now because the web can't do enough of the things a large number of users want. But once it can, they've lots of reasons to focus on Chrome OS.
All the while that Android is the more popular OS of course, Google is still working on Chrome OS and developing it so that it's ready to take centre stage if and when the time comes.
Oh how weird lol that was the verge's caption for it
+Ben Ferguson I contend that adding Android in any way to Chrome OS would ruin it by messing with those three core principles (speed, security and simplicity) without getting enough benefit in exchange. But again, this is entirely speculation on my part.
+Khalid Boutin Well what I am thinking is adding Chrome OS to Android. Not the other way. So the contacts app would become HTML5 based or something, notifications would reference a web database that would be universal for all things googley. So when you cleared a notification from your chromebook it would clear on your phone. I am not saying OS integration. Just services integration.
I remember long ago before gingerbread was ever a reality I was very hopeful Google would come out with a chrome phone. Or a "cloud phone". Is that what you're talking about?
+Ben Ferguson Unless I'm misunderstanding, that could be done just by making Chrome on Android almost as good as Chrome currently is on desktop. Chrome 26 (currently in the Dev and Canary channels) has a notification centre, for example.
That is a good approach, as it would allow Chrome OS to continue improving and make use of some of it in Android, without messing with Chrome OS.
+Christopher Bajor Essentially, yes.

Once Chrome OS works well enough and the hardware is cheap enough, I see no reason for Google not to offer a Nexus 7-style tablet, but powered by Chrome. Native Client (the technology that runs Netflix on Chrome OS) is already being converted to work on the processors commonly used in smartphones and tablets and if Google is developing a Chromebook with a touchscreen, it would follow that their own web apps would work really well with a touch-based device.
There would need to be more improvements and better touch support from major web-based applications to get a Chrome-based phone going, but that I think is the ultimate goal.
But surely having a chrome only portable device would leave something to be desired without any trace of android on it. Does anyone else agree or am I alone on this one?
+Christopher Bajor I don't disagree right now. But by putting out a touchscreen Chromebook Google can encourage web developers to better support touch. A few years down the line, a Chrome tablet or phone could become viable, but some things need to happen before that.
Another option for Google might be to introduce a Chrome OS tablet in the next year and just make it very cheap and not widely advertise it. That would give them data and eager beta testers, before launching a more refined, better supported product a couple of years later.
Come on Pixel! Baby needs new toy!
+Christopher Bajor I just wish they'd hire me in some capacity. If only to stop telling the world about their secret plans ;)
I want one of whatever those things are regardless. 
Add a comment...