itunda. / Design System / Showcase
Itunda · IDS 3.1

The current Itunda visual language.

This showcase applies product-first hierarchy, generous rhythm, precise typography and quiet surfaces inspired by modern Korean fintech systems—while keeping Itunda Indigo, our identity, semantics and platform contracts distinctly Itunda.

Itunda Indigo #7472F44px spacing rhythmPretendardSemantic tokensNative behaviorWeb · Android · iOS
01 · Principles

Inspired by the discipline, not the identity.

Itunda borrows proven design-system principles—clear hierarchy, compact type steps, consistent spacing, calm surfaces and obvious actions—then applies them to its own product language.

One core message

Every product surface should make its purpose obvious before the user studies the controls.

purpose → context → action

Hierarchy first

Large type is reserved for meaningful product moments. Most UI stays compact and scannable.

display → title → body → caption

Rhythm over decoration

A 4px base and predictable 8/12/16/24/32 steps create structure without excessive containers.

4 · 8 · 12 · 16 · 24 · 32

One decision at a time

Each surface gets a clear primary action. Secondary choices stay quiet until they are needed.

primary → secondary → tertiary

Context before controls

Explain what is happening before asking for a choice. Controls should answer a known question, not create one.

context → choice → confirmation

Itunda signature

Indigo remains the brand anchor. Reference-inspired neutrals never replace the Itunda identity.

#7472F4 · #625FE6

Value before action

Show why a task matters before presenting the control. The user should understand the benefit before committing attention.

value → context → action

Explain why

When a request needs trust, give the reason close to the decision. Explanation should reduce uncertainty, not add another step.

reason → choice → recovery
02 · Foundations

Small decisions, repeated consistently.

The showcase uses the current IDS token language rather than the older standalone blue palette. Brand color is an identity role; components consume semantic roles. Layout stays intentionally quiet so hierarchy comes from content, not chrome.

Color roles

Indigo is the current Itunda brand role. Neutrals carry most of the interface; semantic colors communicate intent.

Typography

Pretendard-first typography with explicit scale and line-height.

RWF 248,000
Display24 / 32 · 700
Body16 / 24 · 400
Label15 / 20 · 500
Caption13 / 18 · 400
H132 / 40 · 700
H224 / 32 · 700
H318 / 24 · 700

Spacing

4px base rhythm, from micro gaps to major sections.

4 · micro
8 · control
12 · inline
16 · content
24 · group
32 · major group
40 · section
64 · major

Motion

Motion communicates cause and effect and respects reduced-motion preferences.

fast 140ms
normal 220ms
slow 420ms
reduced 0ms
Preview timing
03 · Components

Real component states, not static mockups.

These examples intentionally show the updated component contract: hierarchy, state, validation, selection and accessibility behavior.

Actions have a clear order.

Primary actions carry the task forward. Secondary actions remain available without competing for attention; destructive actions are unmistakable.

Inputs explain themselves.

Labels, help, validation and recovery stay close to the value they describe.

Used to identify your Itunda account.
Enter an amount greater than zero.

State is always legible.

Checkbox, radio and switch expose state through native semantics, shape and position—not color alone.

Feedback leads to recovery.

Success confirms the result. Errors explain the problem and point toward the next useful action.

Identity verified. Your account is ready.

Design for the whole state.

Component completeness includes loading, disabled, error and recovery—not only the happy path.

DefaultReady for interaction
LoadingProgress without layout jump
DisabledUnavailable but understandable
ErrorRecovery is explained
Recovery pattern

Name the problem → explain what happened → give one clear next action.

List rows and financial information

Primary content, metadata and values align for quick scanning.

Mobile money
Today · 14:20
− RWF 8,500
Card payment
Yesterday · 09:10
RWF 42,000
Rwanda Utilities
Sep 25 · Electricity
− RWF 18,300
04 · Quality

Quality is what still works under pressure.

The same product quality rules should be visible to designers and developers: semantics, focus, content resilience, reduced motion and platform parity.

Accessibility

Ready
native semantics
accessible names
descriptions + errors
44px minimum target
keyboard focus
screen-reader state
large-text resilience
WCAG 2.2 AA target

Design and implementation target WCAG 2.2 AA. This showcase documents the contract; product releases still require platform-specific accessibility verification.

Elevation & surfaces

surface 0 · no elevation
surface 1 · subtle card separation
surface 2 · overlay / floating content

Content resilience

long labels wrap
localized strings expand
amounts remain readable
validation stays visible
large text preserves hierarchy
RTL-safe expansion
no color-only meaning

One contract, native implementations

The visual language is shared, while platform behavior stays native.

WebReact + Web IDS
semantic HTML · keyboard · responsive layout
AndroidKotlin + Jetpack Compose
TalkBack · font scaling · native motion
iOSSwift + SwiftUI
VoiceOver · Dynamic Type · native controls
05 · Product language

Make the next step obvious.

IDS should disappear into the product. The customer should understand the value, the context and the next action without learning the interface first.

Neighborhood Marketplace

Find what you need nearby.

Simple hierarchy, familiar controls and clear next actions — with Itunda Indigo reserved for moments that need attention.