Ubie is a Japanese healthcare-AI company whose products — a consumer symptom-checker (ユビー) and clinical software for hospitals — must do something most health software fails at: feel reassuring to an anxious person and c

Primary
Typography
· Open Sans
Radius

Evidence snapshot

legacy snapshot
Claims grounded
0/136 · 0%
Sources
0 surfaces · 0 sources
UI font basis
frontmatter · low
Components
10 documented · harvested

Needs work: freshness conflict · token source unverified · verification v2 missing

Design System
Ubie logo

Ubie

Ubie is a Japanese healthcare-AI company whose products — a consumer symptom-checker (ユビー) and clinical software for hospitals — must do something most health software fails at: feel reassuring to an anxious person and credible to a busy doctor, on the same screen. The interface answers this with a warm, optimistic clinical aesthetic. The canvas is pure white (#ffffff), text is a soft near-black (#32353a) that reads warmer than true black, and the system is anchored by two colors working in concert: a calm, trustworthy Ubie Blue (#3959cc) for interaction and a fresh, healing Ubie Green (#27cc91) that signals health, vitality, and positive progress.

04

Guidelines

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

Do

  • Use Ubie Blue (#3959cc) for interaction — links, primary buttons, focus, selection.
  • Use Ubie Green (#27cc91) for health, success, and positive progress.
  • Use warm near-black (#32353a) for text, never pure #000000.
  • Keep body text at 170% line-height for a calm, readable rhythm.
  • Use DB (Bold) weight for headings and button labels; M (Regular) for reading.
  • Choose radius by component size: 8px standard, 4px small, 12px cards/modals, pill for toggles.
  • Keep one primary action per screen; pair with a secondary, never two primaries.
  • Use UD Shin Go (or Universal Design fallback) for Japanese — it is an accessibility requirement.

Don't

  • n't use pure black for text or shadows — warm near-black keeps the brand soft.
  • n't crowd content — density reads as urgency/alarm to an anxious patient.
  • n't use red (#e32e55) decoratively — it is reserved for errors and irreversible actions.
  • n't rely on the disabled button state — prefer loading (Vitals guidance: disabled has poor contrast/affordance).
  • n't stack multiple decisions on one symptom-flow screen — one question per screen.
  • n't use heavy, high-opacity shadows — elevation is gentle.
  • n't write 1-word vague labels ("OK") — describe the action in ~15 chars.

Related design systems