FLO design system

FLO's interface reads as clean, luminous, and quietly energetic.

Primary
Typography
· Pretendard Variable
Radius

Use the FLO DESIGN.md

Put the file at your project root and give your coding agent the first prompt.

Raw .md

Evidence snapshot

legacy snapshot
Claims grounded
0/104 · 0%
Sources
0 surfaces · 0 sources
UI font basis
frontmatter · low
Components
7 documented · 5 interactive, 1 with states

Needs work: token source unverified · verification v2 missing

The motion values in this reference were not observed in a capture — and neither were anyone’s. No design system we checked publishes a duration or easing scale; Toss states outright that its component motion lives in the Figma UI Kit rather than in its documentation. Treat any exact curve here as a local default.

Design System
Flo logo

Flo

FLO's interface reads as clean, luminous, and quietly energetic. A pure electric blue (#3f3fff) punches through an overwhelmingly white canvas, anchoring interactive elements — buttons, progress bars, active tab indicators, and checked inputs — with a single, unwavering brand hue. The surrounding palette is almost entirely achromatic: near-black body text on white surfaces, mid-greys for metadata, and a barely-there light grey for resting chips and dividers. This restraint keeps the music and cover art front and center. A muted rose-pink (#ff4d78) appears only in error or warning states, creating a deliberate secondary signal language. Overall the product feels like a clean audio studio: cool-toned, confident, and built for extended listening sessions without visual fatigue.

04

Guidelines

Do and Don't guidelines parsed from DESIGN.md.

Do

  • Use #3f3fff exclusively for the single primary action on any given screen
  • Apply Pretendard at 14–15px for all body copy to maintain readability across light and dark surfaces
  • Keep album artwork as the dominant visual; let cover art supply color temperature to each screen
  • Use pill shapes (radius 15–22px) for purchase and streaming action buttons; use square-cornered (radius 5px) for utility actions
  • Reserve #ff4d78 strictly for error, warning, and incorrect-input states
  • Maintain bottom-border-only treatment on text inputs to preserve a clean, understated form aesthetic

Don't

  • n't apply blue to more than one CTA per screen — dilutes the click-priority hierarchy
  • n't mix the indigo variant (#525cfd) and the primary blue (#3f3fff) on adjacent interactive elements
  • n't use drop shadows on flat list rows — elevation is reserved for floating layers only
  • n't reduce body text below 12px — smallest label size in production is 12px
  • n't apply border-radius above 22px to rectangular content cards — pill radius is reserved for action chips and buttons

Related design systems