Capability-driven control
Let the light shape the interface.
Power, brightness, 2700K–6500K white light, and RGB color stay distinct, legible, and tied to confirmed state.
For independent lighting brands
See the complete local-first control loop: pair a virtual RGB+CCT light, shape brightness and color, save scenes, and recover from an offline state.
No account. No hardware. Data stays in this browser.
01 An original abstract light form — warm, quiet, and intentionally not tied to one fixture.
The browser experience uses a clearly labeled demo light; it does not claim real-hardware support.
Light state, scenes, and preferences stay in this browser and are not synced to a product cloud.
Controls follow declared device capabilities, and offline or failed actions never masquerade as success.
One complete P0 story
The experience is designed around the way light changes a space—not around a wall of device parameters. Every step still exposes what is pending, confirmed, or unavailable.
Enter without friction
No account and no unrelated permission prompt stand between the user and the first meaningful action.
Shape the atmosphere
Controls appear because the device declares RGB+CCT capability—not because every light is assumed to support everything.
Keep what feels right
Three built-in scenes and editable custom scenes turn an adjustment into something useful and repeatable.
Trust the difficult moment
Offline controls are blocked, cached state stays visible, and reconnecting restores a confirmed device state.
What the current iOS build proves
The protocol-independent P0 path has automated coverage. Real hardware remains behind an explicit adapter boundary until a licensed reference device and physical test matrix exist.
Capability-driven control
Power, brightness, 2700K–6500K white light, and RGB color stay distinct, legible, and tied to confirmed state.
Static scenes
Create, rename, overwrite, apply, and delete custom scenes with explicit confirmation.
State and recovery
Pending, confirmed, cached, offline, and reconnecting states keep the user oriented through failure.
A credible path for independent lighting brands
Independent lighting brands with one to ten products and no dedicated mobile app team.
The current code already separates brand identity, theme, supported adapters, device catalog, built-in scenes, legal links, and feature flags. That is a foundation for future white-label delivery, not a claim that every hardware integration is already complete.
Discuss a device and protocolKeep control close to the device when the hardware allows it.
Express brand differences through configuration and adapters.
Separate shipped behavior from plans, dependencies, and proof gaps.
See the complete loop
No account. No hardware. Data stays in this browser.