Gmail Mobile — decoded design system
Gmail Mobile's design system, decoded live by Mozaika: measured color roles, type scale, buttons with real hover/focus states, motion and the brand's own tokens.
This is a static, crawlable rendering for search & AI engines. The interactive version — filters, live decode console, copy & export — is at https://mozaika.design/decode/gmail.com.
Decoded design system
Gmail Mobile's decoded design system: background #FFFFFF, text #1F1F1F, accent #EB8D87, link #0B57D0, primary #EB8D87; type scale h1 34px / h2 22px / body 17px; 4px spacing base; 12px base radius. The single interactive/action color is #0B57D0 — used only on interactive or must-notice elements (buttons, links, key highlights), never on large fills.
Color roles
| Role | Value |
|---|---|
| bg | #FFFFFF |
| surface | #F1F1F1 |
| border | #DDDDDD |
| text | #1F1F1F |
| text_muted | #747474 |
| primary | #EB8D87 |
| accent | #EB8D87 |
| link | #0B57D0 |
| button_bg | #0B57D0 |
| button_text | #FFFFFF |
Using these colors
- Action color
#0B57D0— the single interactive color; only on things you click or must notice, never large fills. primary,accentare all#EB8D87— one role, not several (the action color).link,button_bgare all#0B57D0— one role, not several (the action color).- accent
#EB8D87— accent for emphasis — keep it rare on the page.
Typography
- h1: 34px
- h2: 22px
- body: 17px
Spacing
- base unit: 4px
- scale: 3px, 8px, 9px, 12px, 14px, 16px, 24px, 36px, 48px, 108px
Radii
- base: 12px
- button: 20px
Motion
Micro-interactions run at 150ms (dominant) with cubic-bezier(0.4, 0, 0.2, 1).
- durations: 150ms · 280ms
- easings:
cubic-bezier(0.4, 0, 0.2, 1) - animated properties: opacity, transform, border, box-shadow
Native design tokens
| Token | Value |
|---|---|
--gm3-sys-color-background | rgb(255 255 255 / 1) |
--gm3-sys-color-error | rgb(179 38 30 / 1) |
--gm3-sys-color-error-container | rgb(249 222 220 / 1) |
--gm3-sys-color-inverse-on-surface | rgb(242 242 242 / 1) |
--gm3-sys-color-inverse-primary | rgb(168 199 250 / 1) |
--gm3-sys-color-inverse-surface | rgb(48 48 48 / 1) |
--gm3-sys-color-on-background | rgb(31 31 31 / 1) |
--gm3-sys-color-on-error | rgb(255 255 255 / 1) |
--gm3-sys-color-on-error-container | rgb(140 29 24 / 1) |
--gm3-sys-color-on-primary | rgb(255 255 255 / 1) |
…and 26 more measured on the page.
Button states (measured)
- primary hover: box-shadow
rgba(60, 64, 67, 0.3) 0px 1px 2px 0px, rgba(60, 64, 67, 0.15) 0px 1px 3px 1px
Layout (measured)
- container max-width:
1408px
Motion choreography (measured)
Load order: div.AxOyFc → div.OabDMe
Scroll reveal: 1 elements rest at opacity 0, animate in over 0.1s cubic-bezier(0.2, 0, 0, 1).
Input (measured)
height 28px · radius 4px
Themes
dark counterpart: background #0E0E0E, text #E3E3E3.
Responsive (measured)
- breakpoints: 481px · 592px · 600px · 672px · 720px · 960px
- mobile (390px): hero 32px · nav inline
Install it
Drop this measured system into any shadcn/Tailwind project in one command:
npx shadcn add mozaika.design/r/decode/gmail.com
Or as a Meta Astryx theme — a ready defineTheme file with the measured hover/press states baked in:
curl -o src/themes/gmail.theme.ts https://mozaika.design/api/astryx/decode/gmail.com.ts
registry item · astryx theme · or query it over MCP: get_design_system("Gmail Mobile")
Export: DESIGN.md
# Gmail Mobile — Design System > light, consumer, high — deep decode (measured live) ## Colors | Role | Value | |------|-------| | bg | `#FFFFFF` | | surface | `#F1F1F1` | | border | `#DDDDDD` | | text | `#1F1F1F` | | text_muted | `#747474` | | primary | `#EB8D87` | | accent | `#EB8D87` | | link | `#0B57D0` | | button_bg | `#0B57D0` | | button_text | `#FFFFFF` | **Using these colors** - **Action color** `#0B57D0` — the single interactive color; it appears only on things you click or must notice (buttons, key highlights), never on large fills or backgrounds. - `primary`, `accent` are all `#EB8D87` — one role, not several. - `link`, `button_bg` are all `#0B57D0` — one role, not several (your action color). - **accent** `#EB8D87` — accent for emphasis — keep it rare on the page. - **Page coverage** (full-page screenshot pixels): `#F0F4F9` 98.8% · `#B5C1D4` 1.2% ## Typography - h1: 34px - h2: 22px - body: 17px ## Spacing - base unit: 4px (inferred from the measured scale) - measured scale: 3px, 8px, 9px, 12px, 14px, 16px, 24px, 36px, 48px, 108px — snap all gaps/padding to these ## Radius - base: 12px - button: 20px ## Buttons | Button | Fill / text | Border | Radius | Padding | Font | Shadow | |--------|-------------|--------|--------|---------|------|--------| | primary | `#0B57D0` / `#FFFFFF` | none | 20px | 0px 24px 0px 24px | 500 14px | none | | secondary | `rgba(0, 0, 0, 0)` / `#0B57D0` | none | 20px | 0px 16px 0px 16px | 500 14px | none | **States (measured, not guessed)** - primary hover: box-shadow `rgba(60, 64, 67, 0.3) 0px 1px 2px 0px, rgba(60, 64, 67, 0.15) 0px 1px 3px 1px` - transition: `border 0.28s cubic-bezier(0.4, 0, 0.2, 1)` ## Motion - durations: 150ms (dominant) · 280ms - easings: `cubic-bezier(0.4, 0, 0.2, 1)` (dominant) - animated properties: opacity, transform, border, box-shadow Micro-interactions use the dominant duration + easing; nothing on the page animates slower than the longest duration above — don't invent springier motion. ## Their own tokens (verbatim from :root) | Token | Value | |-------|-------| | `--gm3-sys-color-background` | `rgb(255 255 255 / 1)` | | `--gm3-sys-color-error` | `rgb(179 38 30 / 1)` | | `--gm3-sys-color-error-container` | `rgb(249 222 220 / 1)` | | `--gm3-sys-color-inverse-on-surface` | `rgb(242 242 242 / 1)` | | `--gm3-sys-color-inverse-primary` | `rgb(168 199 250 / 1)` | | `--gm3-sys-color-inverse-surface` | `rgb(48 48 48 / 1)` | | `--gm3-sys-color-on-background` | `rgb(31 31 31 / 1)` | | `--gm3-sys-color-on-error` | `rgb(255 255 255 / 1)` | | `--gm3-sys-color-on-error-container` | `rgb(140 29 24 / 1)` | | `--gm3-sys-color-on-primary` | `rgb(255 255 255 / 1)` | | `--gm3-sys-color-on-primary-container` | `rgb(8 66 160 / 1)` | | `--gm3-sys-color-on-secondary` | `rgb(255 255 255 / 1)` | _…and 24 more measured on the page._ Prefer these names when extending their system — it's the brand's actual vocabulary. ## Layout (measured) - container max 1408px ## Motion choreography (measured) Load order: `div.AxOyFc` @0ms → `div.OabDMe` @1ms - scroll reveal: 1 elements rest at opacity 0, animate in over 0.1s cubic-bezier(0.2, 0, 0, 1) (0 revealed during the drive). Rebuild the timeline, not just the durations — order, delays and staggers above are the choreography. ## Components (measured) - input: h 28px · r 4px · bg rgba(0, 0, 0, 0) · placeholder #1F1F1F - link: #0B57D0 · no underline ## Themes (both measured) - dark counterpart: bg `#0E0E0E` · text `#E3E3E3` ## Responsive (measured) - breakpoints: 481px · 592px · 600px · 672px · 720px · 960px - mobile (390px): hero 32px · body 14px · nav: inline ## How to apply Paste the Tailwind `@theme` (or CSS variables) as your base, then build each section to its spec — verify every color, radius, and font against these tokens. Hover/focus states, shadows and motion timings above are measured from the live page — match them exactly, don't re-guess them. --- > **Decoded with Mozaika** — measured live, not guessed. Full decoded design system + one-command install: mozaika.design/decode/gmail.com
Is this spec still current?
Gmail Mobile is re-measured from its live DOM every night — 16 measurements on record so far. The dated verdict (held, changed, or never settles) is on its drift ledger.
An automated reading of Gmail Mobile's publicly-visible CSS (colors, fonts, spacing, motion) — not affiliated with gmail.com. No screenshots stored. Removal requests: hello@mozaika.design.