Skip to main content

Google Chrome OS – All You Want To Know - Part 1 - What, Why, Demo & Preview Screens

If you missed the Google Chrome OS webcast then following are some main points & screenshot form the webcast that will help you get an idea about it.

One thing is clear though that Google has long way to go with their Google Chrome OS (a year may be).

The webcast presentation was done using Google Chrome OS and Google Docs.

Some of the main points I learnt about the Google Chrome OS are as below.

1. When you will boot Google Chrome OS then it will turn on very fast just like TV. Currently it takes 7 sec to show login screen and 3 seconds after login.

2. Every time you will reboot, OS will auto update itself with latest patch. Seamless to users.

3. Users will not able to install any software or application on the OS. Everything will be online in Google Clouds or other clouds depending upon what you doing.

4. Everything will run under the Google Chrome browser. All application that will run in Google Chrome OS will be Urls. You will able to add applications in favorites as Urls.

5. It will not run any Android apps. This is because Android apps are installed on Android OS while in the Google Chrome OS, installation is not possible.

6. In case of malware or any other issue, Google Chrome OS will auto reboot and fix the issue by re-imaging the OS. It will keep your all your settings and cache and you will not loose anything.

7. Google Chrome OS will be open source and anyone will be allow to copy, edit & create their own version of Google Chrome OS Save “Laksha Chromium OS”. Same is true with Google Chrome Browser and there are few customized versions out there.

8. Google Chrome OS will not run on any hardware but only on specially built net books. These net books will only have flash memory (no regular hard disk), specially built faster wireless card etc. Google is providing Google Chrome OS hardware reference to hardware vendors to build custom machines for Google Chrome OS.

The webcast started with talk on Google Chrome Browser. This was important as in Google Chrome OS user will do everything using Google Chrome browser. I have compiled main point regarding this talk in a separate blog post “Google Chrome Browser Roadmap – Points from Google Chrome OS Webcast”.


Why Google Building Chrome OS?


Current Trends:


1. Net book are expanding

2. People are spending most of the time online

3. 100s of million of user in the cloud. Last 5 years most of the popular applications are web, only 1/10 is desktop

4. Phones becoming smarter, expose rich application framework, they becoming more like computer

5. On the other hand laptop are becoming smaller (net books) with better battery life. May be in future you will have a net book that you will use whole day and only charge during night. Just like a cell phone today.


Future – Google Chrome OS

Google Chrome OS is targeted to achieve following:

Speed - blazingly fast, like TV, you turn it and get it. Google Chrome OS currently takes about 7 seconds to show login screen and 3 seconds after login. Google trying to reduce this time to almost none so you get a TV like experience.

Simplicity - every app is web application, no conventional desktop, no software install, no updates. Everything is link a URL, browser

Security - because user don't install binary we can manage all malware. Google Chrome OS will completely inside the browser security modal.

All data in cloud, user will able to use any machine and see the same thing after login. Users will able to share machines and get the same feel on all machines. If user will loose their machine they will not loose any data as everything is in cloud. Buy new one, login and you got everything back.



Demo - Screenshots



When you turn on the Google Chrome OS, it will take 7 seconds to display login screen and then 3 seconds after login. When OS start, it will auto open Google Chrome Browser. For end users Google Chrome Browser is Google Chrome OS. Users will do everything inside Google Chrome Browser.

App Tabs - Notice the smaller tables in the Google Chrome Browser. These tabs are apps (Urls) that you added in your favorites list. You can add online applications like Google Docs, Calendars, Gmail etc to favorites list.

The very first icon in the Google Chrome Browser is App menu where you can find & explore apps to add to the favorites list.


Persistence light weight windows - Another feature is persistence light weight windows. These windows could be Google talk chat window, Google Notepad or music from MySpace. User can use these window when needed and then minimize to task bar.


Data Stored in Cloud - All data will be stored in the Google Cloud (or other cloud but not on the machine). For example in the following window, user open Notepad. Notepad open as persistence light weight window. Whatever user will type will be saved in Google Cloud – in Google Docs.


Playing Games – Although everything will run inside the Google Chrome Browser, you will still get desktop like experience while playing games. This will be done by making Google Chrome Browser more powerful - “Google Chrome Browser Roadmap – Points from Google Chrome OS Webcast”.


Reading Books in Google Chrome OS / Google Chrome Browser from Google Books website.


Watching Video


Switching Between Windows



File Browser - Attaching a SD card


Opening an excel file while browsing and SD card


Attaching a Camera – And open picture & video from Camera

image image


  1. We used internet for our many purpose and these are very important some use for business and some use for the entertainment or some use this for their study but for the use this we need google chrome and it's very important. Many writer use this for the best paper writing services and it's a good way to use the net so those not know about this thy just read this.


Post a Comment

Popular posts from this blog

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart.  Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel.   I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances.   RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then you do not get

TIME – 25 Best Blogs of 2009

Every year Time makes a list of best blogs in the world. They chose 25 blogs from millions of blogs in the world, spanning politics, housekeeping, astronomy and everything in between. Below if a direct link to the TIME website for the list. I also copied it to easy comparison of last year best with this year best blogs.   25 Best Blogs of 2009     25 Best Blogs 2008   25 Best Blogs of 2009 Talking Points Memo The Huffington Post Lifehacker Metafilter The Daily Dish by Andrew Sullivan Freakonomics BoingBoing Got2BeGreen Zen Habits The Conscience of a Liberal: Paul Krugman Crooks and Liars Generación Y Mashable Slashfood Official Google Blog synthesis bleat /Film Seth Godin's Blog Deadspin: Spor

Howto Run Your HTML Static Website Locally In IIS On Windows PC

WHAT & WHY: As a developer many time you may wish if you could run your static HTML website locally on your computer (Windows 7, Windows Vista, Windows XP, Windows 2008). Although with Static website, you could easily download and double click the index.html or home.html file to open and run other pages. But this will not give you the real world senario. For example you will not able to use a path like /images/home-page-banner.jpg. You will have to use a relative paths like ../images/home-page-banner.jpg. Following are very easy steps to do so. These steps are for Static HTML website. I will also post steps for more advance websites that uses ASP, ASP.NET, Dotnetnuke etc and uses database server.   WHAT YOU NEED: 1. IIS Server installed on your local machine 2. FTP username, password to download files form your FTP server 3. Administrative rights on local machine. Many task will display messages requesting Administrative privilege to run the task.    STEPS: 1.