Introduction

Semantic tokens, not raw values.

Every color, spacing, and radius decision is expressed as intent (content-primary-base, scale-spacing-400) rather than a hex code or pixel value, so theme changes propagate without touching component code.

Native on every platform.

Vroxal isn't a wrapper syntax bolted onto three frameworks. Angular components use Angular idioms, Flutter uses Material 3 widget patterns, Swift uses SwiftUI natively. You write platform-correct code, not Vroxal-flavored code.

Consistent intent, adaptive syntax.

The naming convention and design meaning stay identical across platforms even when the literal implementation differs, so a designer's spec translates predictably regardless of which platform engineering picks up the ticket.

Transparent parity.

Every component page shows exactly what's supported on which platform, and where. No guessing whether a feature actually shipped for your stack.

The full component library, with variables mapped directly to design tokens.

Tree-shakeable, standalone components built for modern Angular.

Material 3–inspired widgets that feel native to Flutter, not bolted on.

SwiftUI-native components — no UIKit bridging, no compromises.