I think your point about the hardware is a good one. All these "small pc equivalent" boxes seem to be overpriced to me, especially the arm-based ones that are essentially competing with smart phones.
From the software side, it's a whole different animal. ChromeOS is intended to be very different from Android. I don't think you can compare some of the features like verified boot or integrated cloud services. Also, you can install apps on android as you like with the flick of a setting. ChromeOS doesn't have installed apps in the sense that they reside on the device. Apps are websites in ChromeOS, no difference. I'm pretty sure "installing an app" and "bookmarking a website" are the same thing in ChromeOS.
>I'm pretty sure "installing an app" and "bookmarking a website" are the same thing in ChromeOS.
Not quiet so. I write chrome apps myself and there is is difference between websites and installable apps. Mostly they have more API access and features such as background processes. But the underlying technology is exactly same as websites. It's essentially a local website that is not hosted on any server but in browser's environment.
If you are interested to know exact differences then allow me to make a shameless plug. This is a media player but is installable instead of hosted. This makes it possible for the app to have a background page which runs even if the browser is closed. Being instalable instead of hosted also has an advantage of more flexible file API. But that is bound to change soon.
Thanks for clarifying. I'm a bit disappointed in Google about this. I would much prefer the apis to be shared completely between the 2 models and don't see why they can't be.
Also, installable web apps should be something not specific to Chrome. Why not make this an open standard so I can install my apps to other browsers without extra effort from the app developer.
As i said, the work is being done on APIs. Infact in developer channels of the browser, I think all the html5 APIs are accessible to everyone. As for background pages, there is no way of running a background page that is hosted somewhere else because there is an internal api that allows communication between pages's javascript in realtime. And such communication would not be possible with a hosted file.
And there is a thing known as installable web-apps. Which basically means you can install an app with just one manifest file hosted online. (it used to be in about:flags but now i think it has landed in stable release, but not sure). Which means no hassle of webstore or even maintaining a separate crx file, just upload a manifest.js once and forget :) Unfortunately background processing is not possible in hosted apps, just in installable ones.
From the software side, it's a whole different animal. ChromeOS is intended to be very different from Android. I don't think you can compare some of the features like verified boot or integrated cloud services. Also, you can install apps on android as you like with the flick of a setting. ChromeOS doesn't have installed apps in the sense that they reside on the device. Apps are websites in ChromeOS, no difference. I'm pretty sure "installing an app" and "bookmarking a website" are the same thing in ChromeOS.