Darin Fisher on how we designed Google Chrome.

  • This episode of Designer Vs.Developer features a conversation with Darin Fisher, VP for Google Chrome, discussing the design and development of the browser.

  • The discussion covers the reasons for building a browser, the role of Webkit and multiprocessor architecture, and the importance of content over chrome.

  • Key principles of Chrome, known as the four 'S's (simplicity, speed, security, and stability), are explored, as well as the balance of using native and web technologies.

  • The conversation also touches upon both the accomplishments and regrets of the past 10 years of Chrome and forecasts what the future holds for the web.

  • Listeners can find more episodes of the podcast and video recording via the links provided in the content.

Welcome to Designer Vs. Developer, a show that tries to solve the challenges faced in the industry by opening a conversation between the two, providing take aways, solutions to workflows, tools and discussions on everyday struggles.

Mustafa speaks to Darin Fisher, VP for Google Chrome, about how design a browser and the 10 year anniversary of Chrome.

In this episode:

  • Why we decided to build a browser.
  • Webkit and multiprocessor architecture.
  • Content not chrome.
  • The four 'S's; simplicity, speed, security & stability.
  • Using both native and web technologies.
  • Both regrets and accomplishments.
  • What the next 10 years holds for the web.

Subscribe to Designer Vs Developer Podcast via Spotify Feedburner, iTunes Or Google Music

Watch the video recording.

Was this page helpful?
Yes
What was the best thing about this page?
It helped me complete my goal(s)
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
It had the information I needed
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
It had accurate information
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
It was easy to read
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
Something else
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
No
What was the worst thing about this page?
It didn't help me complete my goal(s)
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
It was missing information I needed
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
It had inaccurate information
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
It was hard to read
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.
Something else
Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue.