Beautiful by design. Consistent by contract.
Glaze UI is GoreeCloud's shared visual and interaction system: layered, rounded, fluid, accessible, privacy-conscious, and designed to preserve product personality instead of flattening every application into the same screen.
Material structure + liquid depth and fluidity + One UI ergonomics + GoreeCloud privacy, identity, and simplicity.
Depth with restraint
Glaze uses five intentional surface levels. Translucency is selective; readability, performance, hierarchy, and fallback behavior determine the surface.
Adaptive
Compact, Medium, Expanded, and Wide layouts transform navigation and density rather than simply shrinking.
Accessible
Visible focus, practical 44px targets, reduced motion, forced-colors resilience, semantic naming, and solid fallbacks are part of the contract.
Private
No tracking UI dependencies. Remote fonts, scripts, and icons are prohibited unless explicitly justified and documented.
Shared semantics, flexible composition
Glaze UI defines behavior and state vocabulary while allowing each GoreeCloud product to keep its own role, information architecture, imagery, and personality.
Actions
Buttons preserve accessible names, focus visibility, and practical target sizing.
Input
Placeholder text never replaces a visible label.
Feedback
State is communicated semantically, not by color alone.
Navigation
Eleven gates protect beauty and usability
- IdentityRecognizably GoreeCloud.
- TokensSemantic roles over local literals.
- SurfacesIntentional hierarchy.
- StatesPredictable feedback.
- AccessibilityKeyboard, focus, contrast, targets.
- Adaptive layoutTransform across breakpoints.
- PrivacyNo tracking dependencies.
- ResilienceCore experience survives fallbacks.
- PersonalityFamily resemblance, not clones.
- Cross-platformSame semantics, native primitives.
- Visual acceptanceReviewed light/dark and compact/expanded.
Version-specific by design
Stable GoreeCloud applications should identify the exact Glaze UI version they target, expose automated contract evidence, and document any approved exception with its reason, impact, fallback, and review condition.