Microsoft Teams Mobile — decoded design system

teams.microsoft.com · light · consumer · deep decode — measured live

Microsoft Teams 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.

Open in Mozaika →

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/teams.microsoft.com.

Decoded design system

Microsoft Teams Mobile's decoded design system: background #FFFFFF, text #1B1B1B, accent #303AA7, link #303AA7, primary #303AA7; type scale h1 34px / h2 22px / body 17px; 8px spacing base; 12px base radius. The single interactive/action color is #0067B8 — used only on interactive or must-notice elements (buttons, links, key highlights), never on large fills.

Color roles

Using these colors

• Action color #0067B8 — the single interactive color; only on things you click or must notice, never large fills.
• primary, accent, link are all #303AA7 — one role, not several (the action color).
• accent #303AA7 — accent for emphasis — keep it rare on the page.

Typography

• h1: 34px
• h2: 22px
• body: 17px

Spacing

• base unit: 8px
• scale: 4px, 8px, 12px, 16px, 24px, 32px, 48px, 64px

Radii

• base: 12px
• button: 0px

Shadows (elevation)

• card: rgba(0, 0, 0, 0.2) 0px 2px 6px 0px

Motion

Micro-interactions run at 250ms (dominant) with ease-in.

• durations: 250ms · 300ms · 500ms
• easings: ease-in · ease

Button states (measured)

• primary hover: background #005DA6
• primary focus: background #005DA6 · outline 2px solid rgb(0, 0, 0)

Motion choreography (measured)

Load order: div.lightbox-cover → div.lightbox-cover → div×3 → div.sign-in-box → div.background-image → div.pagination-view

Input (measured)

height 36px · radius 0px

Responsive (measured)

• breakpoints: 320px · 539px · 768px · 992px · 1400px
• mobile (390px): nav inline

Install it

Drop this measured system into any shadcn/Tailwind project in one command:

npx shadcn add mozaika.design/r/decode/teams.microsoft.com

Or as a Meta Astryx theme — a ready defineTheme file with the measured hover/press states baked in:

curl -o src/themes/teams.theme.ts https://mozaika.design/api/astryx/decode/teams.microsoft.com.ts

registry item · astryx theme · or query it over MCP: get_design_system("Microsoft Teams Mobile")

Export: DESIGN.md

# Microsoft Teams Mobile — Design System

> light, consumer, high — deep decode (measured live)

## Colors

| Role | Value |
|------|-------|
| bg | `#FFFFFF` |
| surface | `#F1F1F1` |
| border | `#DCDCDC` |
| text | `#1B1B1B` |
| text_muted | `#717171` |
| primary | `#303AA7` |
| accent | `#303AA7` |
| link | `#303AA7` |
| button_bg | `#0067B8` |
| button_text | `#FFFFFF` |

**Using these colors**

- **Action color** `#0067B8` — 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`, `link` are all `#303AA7` — one role, not several.
- **accent** `#303AA7` — accent for emphasis — keep it rare on the page.
- **Page coverage** (full-page screenshot pixels): `#F6F3F7` 98.3% · `#D8DEEA` 1.7%

## Typography

- h1: 34px
- h2: 22px
- body: 17px

## Spacing
- base unit: 8px
- scale: 4px, 8px, 12px, 16px, 24px, 32px, 48px, 64px

## Radius
- base: 12px
- button: 0px

## Buttons

| Button | Fill / text | Border | Radius | Padding | Font | Shadow |
|--------|-------------|--------|--------|---------|------|--------|
| primary | `#0067B8` / `#FFFFFF` | none | 0px | 4px 12px 4px 12px | 400 15px | none |

**States (measured, not guessed)**

- primary hover: background `#005DA6`
- primary focus: background `#005DA6` · outline `2px solid rgb(0, 0, 0)`

## Shadows (elevation)
- card: `rgba(0, 0, 0, 0.2) 0px 2px 6px 0px`

## Motion
- durations: 250ms (dominant) · 300ms · 500ms
- easings: `ease-in` (dominant) · `ease`

Micro-interactions use the dominant duration + easing; nothing on the page animates slower than the longest duration above — don't invent springier motion.

## Layout (measured)

| Section (y) | Height | Cols | Gap | Pad y | Split |
|---|---|---|---|---|---|
| 0 | 900 | — | — | 0/0 | — |

## Motion choreography (measured)
Load order: `div.lightbox-cover` @0ms → `div.lightbox-cover` @0ms → `div`×3 @180ms → `div.sign-in-box` @182ms → `div.background-image` @182ms → `div.pagination-view` @349ms
- `div.pagination-view` — opacity 0→1 — 250ms cubic-bezier(0.5, 0, 0.5, 1)

Rebuild the timeline, not just the durations — order, delays and staggers above are the choreography.

## Components (measured)
- input: h 36px · r 0px · bg rgba(0, 0, 0, 0) · placeholder rgba(0, 0, 0, 0.6)

## Responsive (measured)
- breakpoints: 320px · 539px · 768px · 992px · 1400px
- mobile (390px): body 15px · 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/teams.microsoft.com

Is this spec still current?

Microsoft Teams 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.

← All decoded design systems

An automated reading of Microsoft Teams Mobile's publicly-visible CSS (colors, fonts, spacing, motion) — not affiliated with teams.microsoft.com. No screenshots stored. Removal requests: hello@mozaika.design.