UI/Design Guidelines
Design for clarity, consistency, and desktop flow. MapleOS apps should feel native to the operating environment, even when the content inside them is unique.
Respect window chrome
Assume the app lives inside a broader desktop experience. Layouts should work well in windows and side-by-side comparisons.
Use consistent iconography
Program identity should be recognizable, but not visually disconnected from MapleOS conventions.
Prefer shadcn/ui patterns
Use the shared component vocabulary for cards, tabs, buttons, inputs, and states so apps feel cohesive.
Keep high-trust actions visible
Important edits, sends, or automations should be explainable and easy to review before execution.