Overview
Trello is a card-board productivity tool with a public marketing site. The look is the Atlassian blue family: deep navy ink, a bright blue action, light gray surfaces and rounded 4 to 8px shapes. [Observed]
What defines the look:
- Deep navy ink. Text is
#091e42and#172b4d, not black. [Measured] - A bright blue action.
#0065fffills the main buttons, with#0747a6and#0052ccfor deeper blues. [Measured] - Pale surfaces.
#f4f5f7,#fafbfcand#deebfffor sections, and#f0f0f0for feature cards. [Measured] - Two Charlie faces. Display at weight 500 for headlines and Text at 400 for copy. [Measured]
- Soft, small corners. Buttons and cards use 4.8px, with 8 on panels. [Measured]
Source for this file: the Trello marketing home page measured in a browser at 1440 and 390 wide, read on 2026-10-06. The board and card screens are behind login and were not measured. The Atlassian Design System was not read. No app captures were used. See Known Gaps.
Core
Colors
| Role | Value | Where |
|---|---|---|
| Action blue | #0065ff | Primary buttons |
| Deep and link blue | #0747a6, #0052cc | Bands and links |
| Text | #091e42, #172b4d | Headlines and navigation |
| Page | #ffffff | Main surface |
| Pale grays | #f4f5f7, #fafbfc, #f0f0f0 | Sections and cards |
| Blue wash | #deebff | Highlight panels |
Typography
Charlie Display sets headlines at weight 500: 48 on 60 for the hero and 36 on 48 for sections. Charlie Text sets copy at 400: 20 on 30 for leads and 16 on 24 for body and buttons. [Measured]
Shape and spacing
Corners are 2, 4, 4.8 and 8, with circles for avatars. Buttons are 50 to 60 high, navigation items 60 high with 20 by 16 padding. Cards carry a soft shadow of 15 percent navy. [Measured]
Iconography and motion
Not measured in this pass. [Inferred]
Themes
Light on the pages measured. [Observed]
Platform: iOS
The Trello iOS app was not captured. The notes below follow from the web design and platform conventions.
Back and up navigation
Expected on iOS: Chevron plus previous title, swipe from the left edge.
Chevron plus previous title and the edge swipe, as the platform expects. Not confirmed on a device. [Inferred]
Primary navigation
Expected on iOS: Bottom tab bar, about five items.
A bottom tab bar for boards, notifications and account. [Inferred]
Main action
Expected on iOS: Nav bar or bottom bar button.
A floating or bar button for adding a card. [Inferred]
Sheets, dialogs and messages
Expected on iOS: Action sheets, alerts, modals.
Not measured. [Inferred]
Controls
Expected on iOS: Cupertino switches, pickers, segmented controls.
Not measured. [Inferred]
Text sizing
Expected on iOS: Dynamic Type.
Not measured. [Inferred]
Touch and pointer targets
Expected on iOS: 44pt minimum.
Not measured. [Inferred]
Insets and system bars
Expected on iOS: Safe areas, status bar.
Not measured. [Inferred]
Icons
Expected on iOS: SF Symbols or custom.
Not measured. [Inferred]
Account and sign-in rules
Expected on iOS: Equivalent login option when third-party sign-in exists (Guideline 4.8) and in-app account deletion. Note the date checked.
Not verified. Sign-in rules and account deletion were not checked. [Inferred] Checked: 2026-10-06 against the public web only.
Platform conformance
Expected on iOS: For each important component: what iOS expects, what this app does, and why it deviates.
The apps are expected to share the blue, the navy ink and the card style with the web. [Inferred]
Platform: Android
The Trello Android app was not captured. The notes below follow from the web design and platform conventions.
Back and up navigation
Expected on Android: System back and gesture, up arrow in the top bar.
System back and gesture, with an up arrow in the top bar, as the platform expects. Not confirmed on a device. [Inferred]
Primary navigation
Expected on Android: Navigation bar, rail on tablets.
A bottom navigation bar for boards, notifications and account. [Inferred]
Main action
Expected on Android: Floating action button.
A floating action button for adding a card. [Inferred]
Sheets, dialogs and messages
Expected on Android: Bottom sheets, dialogs, snackbars.
Not measured. [Inferred]
Controls
Expected on Android: Material switches, pickers, chips.
Not measured. [Inferred]
Text sizing
Expected on Android: Font scale.
Not measured. [Inferred]
Touch and pointer targets
Expected on Android: 48dp minimum.
Not measured. [Inferred]
Insets and system bars
Expected on Android: Edge to edge, system bars.
Not measured. [Inferred]
Icons
Expected on Android: Material Symbols or custom.
Not measured. [Inferred]
Account and sign-in rules
Expected on Android: Account deletion and data safety requirements. Note the date checked.
Not verified. Sign-in rules and account deletion were not checked. [Inferred] Checked: 2026-10-06 against the public web only.
Platform conformance
Expected on Android: For each important component: what Android expects, what this app does, and why it deviates.
The apps are expected to share the blue, the navy ink and the card style with the web. [Inferred]
Platform: Web
The Trello marketing home page, measured at 1440 and 390 wide. Board and card screens were not measured.
Back and up navigation
Expected on Web: Browser back, breadcrumbs.
Browser back. [Observed]
Primary navigation
Expected on Web: Top nav or sidebar.
A 60 high top bar with Features, Solutions, Plans and Resources and sign-in buttons. [Observed]
Main action
Expected on Web: Page-level button.
A bright blue button with white text, 50 to 60 high. [Measured]
Sheets, dialogs and messages
Expected on Web: Modals, toasts.
Not measured. [Inferred]
Controls
Expected on Web: Native or custom.
Square-ish blue buttons with a 4.8px corner. [Measured]
Text sizing
Expected on Web: Browser zoom.
Sizes are fixed pixel values at each breakpoint. [Measured]
Touch and pointer targets
Expected on Web: Pointer and keyboard.
Buttons measure 50 to 60 high. [Measured]
Insets and system bars
Expected on Web: Viewport, scrollbars.
Not measured. [Inferred]
Icons
Expected on Web: Any.
Not measured. [Inferred]
Account and sign-in rules
Expected on Web: Not applicable unless the product has accounts.
Not applicable to the public pages measured. [Observed]
Platform conformance
Expected on Web: For each important component: what the web norm is, what this app does, and why it deviates.
The responsive page keeps type and color and changes layout. [Measured]
Cross-platform consistency
Consistent across platforms: the blue and navy pair, pale surfaces and soft corners. [Measured for web, Inferred for the apps]
Intentionally different: not measured. [Inferred]
Do's and Don'ts
Do
- Use navy for text instead of black.
- Use one bright blue for the main action.
- Keep corners small and cards softly shadowed.
- Use pale blue for highlights.
Don't
- Don't use pure black text.
- Don't use pills for primary buttons.
- Don't add a second action color.
Known Gaps
- Boards, cards, lists and the signed-in app were not measured, so the core product look is only inferred.
- The iOS and Android apps were not captured. Their sections are inferred from the web design and platform conventions.
- Icons, motion and exact breakpoints were not measured.
- Account deletion and store policy rules were not verified.
- The Atlassian Design System was not read, so role names are not given.