Color roles
Four roles are enough for most surfaces. Semantic success and error colors appear only when their meaning is required.
#7472F4
#625FE0
#F0EFFF
surface
One visual language for Itunda products: strong hierarchy, restrained color, predictable spacing and components that explain their state without visual noise.
Color and decoration are supporting tools. Structure comes first, so users can scan, understand and act quickly.
The same decisions repeat across web, Android and iOS without turning every screen into a collection of colored cards.
Four roles are enough for most surfaces. Semantic success and error colors appear only when their meaning is required.
Large type is for important moments. Body text remains compact and readable.
Use a simple 4px rhythm. Larger gaps separate ideas rather than decorating containers.
Prefer open space and separators. Add a surface only when it improves grouping or interaction.
A subtle background separates content without creating another visual object.
Examples stay close to production behavior and make the primary action obvious.
One primary action. Secondary actions stay quiet.
Labels and supporting text explain the task without adding noise.
Every important component has a clear default, loading, disabled and error state.
Itunda Indigo should guide attention, not color every surface.
Clear context first. One primary action next. Supporting choices remain available but visually quiet.