---
id: mobility-bird-design-en
service: Bird
website: https://www.bird.co
category: mobility
document: DESIGN.MD
source_prompt: mobility-bird-representative-en
language: en
generated: 2026-07-18
---

# Bird DESIGN.MD

> Use this DESIGN.MD as the persistent design standard before building a Mobility site or app. It can be given directly to designers, frontend engineers, AI builders, and coding agents. Bird is an information-architecture reference only.

## Purpose

- Bird: https://www.bird.co
- Mobility: requesting and managing transportation
- vehicles, routes, and rides
- current location, ETA, and safety
- mobility

## Design brief

Create an original product that supports requesting and managing transportation. Make vehicles, routes, and rides easy to scan, compare, and act on. Treat current location, ETA, and safety as a primary design constraint. Starting direction: discovery and comparison flow · clear and confident · medium information density · location input -> map and list comparison -> immediate action · #111111 · Bird.

## Public interface design analysis

- Reference basis: These are recurring visual and structural patterns from public landing screens and representative task flows. Verify the current live capture because services change over time.
- Interface archetype: discovery and comparison flow
- Tone and manner: clear and confident
- Information density: medium
- Color strategy: restrained brand accents on neutral surfaces (#111111)
- Navigation model: action-first minimal navigation
- Structural sequence: location input -> map and list comparison -> immediate action
- Reusable patterns: map canvas, location input, option sheet, price policy, safety menu
- Independent application rule: Use the order and decision principles only. Do not reproduce logos, copy, imagery, icons, or proprietary screen composition.

## Screen architecture

- Global navigation with clear current location and account state
- Overview that exposes the next important action for vehicles, routes, and rides
- Search, filter, sort, or segmented views only where they reduce decision cost
- Detail view that keeps context, status, evidence, and the primary action together
- Persistent help, recovery, privacy, and safety access for current location, ETA, and safety

## Design tokens

```css
:root {
  --color-primary: #111111;
  --color-ink: #17201D;
  --color-canvas: #F6F8F7;
  --color-surface: #FFFFFF;
  --color-tint: #11111122;
  --color-danger: #DC2626;
  --radius-control: 6px;
  --radius-card: 8px;
  --space-1: 4px; --space-2: 8px; --space-3: 12px;
  --space-4: 16px; --space-6: 24px; --space-8: 32px;
  --content-reading: 720px;
  --content-wide: 1280px;
}
```

## Component specifications

- Navigation: active, hover, focus, disabled, and collapsed states
- Cards and rows: stable dimensions, realistic content, metadata hierarchy, and complete click targets
- Forms: labels, descriptions, validation, error summary, progress, and recovery
- Actions: one clear primary action per region; icon buttons require accessible names and tooltips
- Feedback: inline status, toast, banner, skeleton, progress, confirmation, and destructive-action dialog

## State design

For every data-driven region, define loading, empty, partial-data, stale, error, offline, permission-denied, disabled, saving, and success states. Keep layout dimensions stable so state changes do not shift surrounding content.

## Responsive rules

- 360px: one primary column, no horizontal page scroll, 44px touch targets
- 768px: preserve context with two panes only when each pane remains readable
- 1280px and above: constrain reading width and use extra space for comparison or persistent context
- Never scale type with viewport width; wrap long labels and localize for text expansion

## Accessibility requirements

- Semantic landmarks and heading order
- Complete keyboard operation with visible focus
- WCAG AA contrast in all states
- Programmatic labels, descriptions, errors, and live regions
- 200% zoom, reduced motion, forced colors, and screen-reader verification

## Design instruction for AI builders

```text
Design an original Mobility interface for [Product name]. Its goal is requesting and managing transportation; its core objects are vehicles, routes, and rides; its critical risk is current location, ETA, and safety. Use the token system and screen rules in this document. Specify realistic content, component contracts, all data states, responsive behavior, accessibility, and acceptance criteria. Do not copy Bird's logo, proprietary copy, images, or exact layout.
```

## Completion checklist

- [ ] The critical path for requesting and managing transportation is obvious without explanation
- [ ] vehicles, routes, and rides have clear hierarchy, status, and actions
- [ ] current location, ETA, and safety has prevention and recovery
- [ ] Mobile, tablet, desktop, keyboard, screen reader, zoom, and reduced motion are verified
- [ ] Loading, empty, error, offline, partial, permission, and success states are complete
- [ ] No protected brand asset or pixel-level layout from Bird is reproduced