Styles
Keep color, typography, and reusable visual choices consistent across a Project
Project styles keep repeated visual decisions consistent across screens. Use them for choices that express the app’s design language, then use local overrides only when a particular moment needs to differ.
Reuse design decisions
The Editor supports reusable color and text-style values. Named values make it easier for both people and Nuxie to apply the same intent throughout a Project.
Good candidates include:
- Brand and surface colors.
- Primary, secondary, and destructive action colors.
- Heading, body, caption, and price typography.
- Repeated corner, border, and spacing choices when the Editor exposes them as reusable values.
Text styles
Apply a named text style when multiple text elements should change together. Keep the semantic purpose in the name — for example, Paywall title or Legal caption — instead of naming a style after one screen.
Use system text styles when the Experience should follow platform typography. When a custom font is required, verify that the published release contains the needed font asset and inspect the result on a device.
Local overrides
A local override should communicate a real difference, not repair an inconsistent base style. Use it for a one-off emphasis or a state-specific presentation. Return to the shared style when the choice should apply broadly.
Runtime fidelity
The Editor previews the same Project model compiled for the native runtime, but final validation still belongs on a device or simulator. Check safe areas, color scheme, font availability, text scaling expectations, and interaction states before launch.