2. 2
How we organize teams at Google to create products.
How we actually went about designing Google Chrome.
3. Process
+
Philosophy
3
Two components to a successful design:
Repeatable process to maintain a design philosophy.
4. Idea
4
Generally, a Google project starts when some engineers have an idea.
They use their 20% time to build a prototype.
5. 5
First prototype of Google Chrome.
Multi-process: faster, more secure, more crash resistant.
Ideas also come from UX, customer support ... even sometimes PMs :)
6. Idea Implementation
6
Next, project gets staffed full time.
Most important thing is to iterate with data.
8. Idea Implementation Launch
8
Finally, launch, marketing, PR, etc.
9. “Content, not Chrome”
9
Our design philosophy: “Content, not Chrome”.
Speed isn’t just about technology, it’s also about UI design.
Going to present 5 ideas that support this philosophy.
36. Idea 3
Use data and algorithms to make the UI simpler.
36
It actually took a while to perfect the behavior of the Omnibox.
Sometimes you need to iterate a lot before something feels right.
37. 37
We’re working on a better version of Autofill.
When you first fill in a form, we’ll ask if you want to save the info.
40. 40
Most browsers warn the user when closing a window with multiple tabs.
But most of the time, the user actually wants to close the window.
41. 41
Instead, we implemented “undo” on our new tab page.
This is similar to how we handle drafts in Gmail: “Draft discarded - undo”.
42. Idea 5
Don’t get in the way of the user.
42
Avoid modal interfaces at all costs.
43. Content, not Chrome
Don’t waste pixels.
Only show features that are actually used.
Use data and algorithms to make the UI simpler.
Make features discoverable.
Don’t get in the way of the user.
43
These are just a few of the rules of thumb we use in designing Google Chrome.