>> We want to first start by booting the machine. So Kahn is actually--Kahn Lee, who is the
product manager on Chrome OS, is actually going to press the button and do a cold reboot.
Let's go. So we really care about how fast we can get the machine to boot. We want this
to be in a matter of seconds. And as you can see, we are in the log-in screen, right? It
takes about seven seconds right now and we are working very, very, very hard to make
this time shorter. It takes another three seconds to log-in to your favorite application.
So we are going to switch to the machine from which we have been projecting. In case you
didn't realize, we have been projecting from a Chrome OS machine. So we are going to get
out of the full screen mode and we are within Chrome OS. So two things before I get started
with the demo, first of all, hopefully, this is not a surprise to you, but it looks like
Chrome, right? And so, internally, we joke around, saying Chrome is Chrome OS, right,
and Chrome is the OS for all practical purposes. Having said that, there are many, many interesting
changes in Chrome which I'm going to walk you through to make it function like an operating
system. The advantage of doing it this way is it's very familiar and intuitive to most
users. Almost everyone knows how to use a browser; so we just want it to feel that way.
The second thing I want to say before I walk through the UI is, at this stage of the project,
we are opening up the project to a year ahead of release. So we are actually training through
the UI. I have to convince the team to stop checking in code so that we can kind of be
able to freeze it for the demo, right? We are checking in codes as we speak. So, a lot
of the UI is going to change. I'm not fully sure how it will turn out, but one thing I
can guarantee is it won't be exactly like what you're looking at today. Having said
that, there are many, many important concepts here which we are very sure will carry over
to the final product. So, I'm going to focus on covering those aspects for you first. So,
let's start with, it looks like Chrome but on the top left hand side, you're seeing some
small tabs; we call this application tabs. So, you can take any of your favorite applications.
In my case, it's Gmail and Calendar, et cetera; but it could be Facebook, it could be YahooMail,
whatever users want. You can take any application and, with one click, pin it to be your favorite
application. And once you do that, we call these application tabs. We are working very
hard to make it possible for you to get to your favorite applications instantly. So once
you choose something as an application tab, they always stay in place. So, let's open
a few tabs. As you can see, Kahn is opening a few tabs; but the application tabs on the
top left, the five of them, don't move at all. So you can open, close, et cetera; they
always stay in place. So, we are working very hard to make it easy for you to access your
favorite applications. In addition to this method of accessing your applications, there
is--on the top left hand side, you have something what we call as the App Menu. So, caveat,
the UI here is going to change but the concept is we really want you to be able to discover
new applications as well as to access your top applications. So let's go around and start
poking around the App menu. I'm noticing an interesting app called Contacts, so let's
try that out. Something interesting happened. Something popped from below--internally, we
call these as moles because they kind of come from underground but we are going to call
them panels externally. So, panels are something--which these are persistent lightweight windows which
you can have them around with you all the time. They are persistent. So, for example,
let's click on a few tabs--they don't move at all, right? And the panel stays; it's a
persistent window. There are several interesting use cases for it. You can minimize them and
make them go away and you can bring them back. We are going to work hard to make sure we
can automatically manage panels for users. So, this is a chat window. So, Khan is chatting
with David, one of the engineers on the team, and, hopefully, David says hi back. There
you go. So Buddy List and Chat is a great example of how you would use a panel. Let's
see one of the use cases for panels right there. So, let's poke around; there's Notepad.
So let's click on Notepad as an example. So, one more panel--the interesting thing about
Chrome OS is, I mentioned all data is in the cloud. So what does that mean? So, Khan is
going to type something here and maybe we should go to Google doc and open this notepad
file. You can see it's right there in the cloud. All data in Chrome OS is in the cloud.
So, as a model, anything you put on the machine is instantly available to you from anywhere
so--which is something we are very, very excited about. Let me show one more use case for panels.
Let's type YouTube in the Chrome Omnibox. Recently, we launched this very cool music
feature called Music OneBox by which you can type in names of songs and play it right off
the Google search page. So let's click on Beautiful Day. You can see a panel popped
up and it plays right in place. It's a persistent window; you can leave it there, you can minimize
it and keep working, right? You can use this to put streaming music from the Web. So these
are interesting examples of how we expect people to use panels. Before we get caught
up in the song, so, let's wrap it up. If you go to the-—well, let's go poke around at
the app menu once more. So, what I like about Netbooks is, today, I traveled and I go on
vacation and it's tough to carry my DVD player, my computer, my book reader, et cetera. The
great thing about Netbooks is these are ultra-light and mobile devices and once battery times
get much better, you can carry them around with you as general purpose devices. So, we
actually expect these to be great entertainment devices. People should be able to watch videos,
play music, play games, books, et cetera. So let's see how the experience looks like.
So I'm an avid chess player so I have this chess game which I use on my Chrome OS machine
and you can now--with just a flash--double-click, okay. So Khan is playing the chess game. You
can see how it's very easy and visual and you can enter--you can make it full screen
more and take over the screen. So these are good examples of what we expect people to
do with these machines. In fact, another good example of what you can do is read books.
So, for example, we are working hard on this experience and we have ways to go, but if
you look at Google Books, for example, here is "Alice in Wonderland." So you can have
it on your netbook in a full screen mode and you can read conveniently. It's--you know,
these are scanned books which are available, and I can totally imagine reading it to my
daughter, you know, carrying a netbook around with me. So it's very, very compelling. So
we are really interested in solving all these interesting user experiences for people. One
of the things is I spend all my time in one Chrome window, but it's very common for users
to have multiple sets of windows. So we want to walk you through that experience. For example,
it's the time of the year in which I'm trying to get all my gift shopping done before holidays
come around, right? So I have a set of windows with Amazon, eBay, et cetera, so I can easily
switch over to the other windows. And so I have Amazon and eBay; it's a completely different
Chrome instance for me. And I even have YouTube. I want to take the chance to show that YouTube
works and Flash works on the machine, so let's click on a video and make sure it works. So
as you can see, YouTube works and Flash works. I'll just move to another window. Let's go
back to the original window; you can move back and forth. In fact, you can go to the
"All View" mode and you can see all the windows which are open on your system. The UI here
is going to change a little bit, but you can imagine, I can open a new Chrome window, right?
And I can drag and drop a tab from one Chrome window to another Chrome window. It's very
simple, very intuitive and just works. So, this is the core part of the user experience.
Having said that, one of the things we realized is people are going buy these netbooks, they're
going to go home and do a lot of common things they are used to doing with computers. So
we actually have a long list of all these use cases and we are working hard to make
sure it works seamlessly for users. Let me walk through a couple of examples. Most people
plug in their cameras, right? They may plug in a USB drive. And so what happens if we
plug in a USB drive? You can imagine the set-up concept, but you can imagine Chrome opens
a tab and shows you what's in the content of a camera or a USB drive and you can see
the files that are on the machine. It turns out in this USB drive, there are Excel files.
We don't have Microsoft Excel on this machine. So what happens if we click Excel file. Let's
give it a shot. It turns out Microsoft office launched a killer app for Chrome OS. They've
been working very, very hard to do this. The point here is Chrome OS does not have a propriety
app framework. It's a completely open app framework. It's the Web; so anybody who puts
up a URL, anybody who writes an application that works on the Web and in a browser is
writing an application for Chrome OS. It's something we are very, very excited by. And,
for the record, I'm an avid Google Spreadsheets user--just a disclaimer. So, there are few
other use cases people can do. Here are some interesting use case we can demonstrate. So
Khan is going to take a picture; in fact, he has one of the new droids and it has a
five mega pixel camera so it's pretty cool. So, hopefully, we are going to get a good
picture out of it and he's going to take the picture, and let's see what happens if you
plug this in your Chrome OS machine. So you can see Chrome OS detects the camera as a
storage device, that the phone is a storage device. It can pull the picture right there.
So he's clicking on the picture. And here you go; I can see Arlington squarely in the
center of the picture. So it turns out there is a video on the phone as well. So let's
try and see what happens if you click the video. The video plays right in place in the
panel we talked about. So the point here is we really want it to be possible for all these
seamless use cases to--I mean, for all these use cases for uses to be seamless. We just
want computers to be delightful and works. So we are working very hard to make that possible.
One final example I just want to give is people run in to many, many different types of files,
right, when they use a computer. They need to be able to use those files. For example,
let's go to one of my favorite Web sites--I go there pretty often--the IRS.gov. And let's
go around and click on a PDF file, right? So what happens if you click on a PDF file?
It works. It's instant. It's in the browser, right? So, that's the underlying theme of
what we are trying to accomplish: speed, simplicity and security. So I'm going to take a step...