Fixture
One controllable light or lighting unit.
Leksa / Connected lightingLight, under
Light, under
your control.
From adding a fixture to saving a scene: a mobile control system for home and professional lighting.
Follow the story ↓LEKSA LIGHTING04 / Connect → Control
2 monthsConcept to design delivery
3–300Fixtures in the design scope
1 appSetup, control and scenes
Design delivery / Tested with R&D and an engineerBy Samriddhi Tiwari
Context
A light is simple. A room full of lights is not.
Channel
An independently adjustable output.
Scene
A saved combination of light settings.
The intentSet the room once.
Set the room once.
Bring it back in a tap.
Problem
The same app. Different kinds of light.
A single-channel fixture and a colour-temperature fixture need different controls. Shared devices also need clear availability.
Why this direction
The interface should reflect the light that is connected, and explain why a command is unavailable.
Structure
From a new fixture to a familiar scene.
- 01
Sign in
Enter the workspace.
- 02
Add
Identify the fixture.
- 03
Adjust
Set its channels.
- 04
Save
Name a reusable scene.
FixturesControl individual lights.⇄ScenesRepeat a group of settings.
Structure
Establish the flow before the finish.
Original design artefacts. View full wireframes · View interface system
Solution / 01
A useful home, from the first tap.
Fixtures and scenes are easy to reach. Setup starts from an explicit add action.
Design choice
Keep frequent controls distinct from guidance and updates.
Solution / 02
Only the controls this fixture needs.
Single-channel, dual-channel and temperature controls reflect the connected device.
Design choice
Do not make people translate hardware differences into generic controls.
Solution / 03
A blocked action needs an explanation.
Empty inputs, conflicting details and devices in use should explain what to change next.
Design choice
Feedback belongs beside the action that needs attention.
Solution / 04
Save the setting. Repeat the feeling.
Choose the fixtures, name the scene and keep it ready to use again.
Design choice
Selection comes before naming, so the scene has a clear scope.
Decisions
Feedback matters beyond the screen.
− Earlier direction? The question✓ Chosen direction
One generic control layout
What can this fixture actually do?
Show controls that match the hardware.
A disabled action with no explanation
What should I fix?
Make input requirements and conflicts visible.
A command looks like a completed action
Did the physical light respond?
Keep command state and device feedback distinct.
Results
A complete control journey, in 2 months.
2 monthsConcept to design delivery
3–300Fixtures in the design scope
1 appSetup, control and scenes
Delivered
Setup, fixture control and reusable scene flows.
Collaborated
Reviewed interactions with R&D and an engineer.
Carry forward
Clear feedback for shared devices and real hardware states.
01 / 10Scroll to unfold the story