Company
Chrome
We build for the web, then we check Chrome the way your customers use it: mid-range phones, a dirty cache, and a tab they already had open.
What it is
Chrome is Google's web browser, built on the Blink engine. It is the browser most people on the planet open, and the one most product teams test first. Chrome also means DevTools, Lighthouse, the Web Store, ChromeOS, and the engine inside Android WebView and many Electron apps.
When a site is slow, broken, or blocked in Chrome, it is broken for the majority of the audience. The browser is not a logo on a compatibility row. It is the runtime the interface actually runs in.
What it does
Teams use Chrome as the default test surface: layout, performance, service workers, payment sheets, and the DevTools that tell you why a page is 4MB. Extensions, enterprise policy, and ChromeOS matter for companies that issue machines.
We design and ship for the real Chrome your users have, including the last couple of versions, not only the nightly on a designer's laptop. Safari and Firefox still get a pass. Chrome gets the first honest look.
Why we use it
The browser most of your users will actually open.
Performance budgets, traces, and real-device checks sit in the same engagement as the design. Progressive enhancement keeps a form alive if a script is late. Installable web apps are only in scope when the brief actually needs a home-screen icon. We do not ship Chrome-only APIs as the only path.
If it only works on a fresh desktop profile, it is not done.
Built on it
Ships Chrome as its own browser and as the engine inside many Google apps.
Microsoft Edge
Is built on Chromium, the same open engine Chrome uses.
Brave
A Chromium browser with a different default on ads and privacy.
Electron apps
Slack, Visual Studio Code, and Figma's desktop shell run a Chrome-class engine.
Android
WebView on most phones is a Chromium engine, so Chrome bugs show up inside apps too.
Tell us what needs to ship.
You use a working prototype before the production build goes ahead.