Role
Product concept, UI direction, and presentation
MuHome starts from a simple frustration: smart-home apps can show a lot of controls without making it clear what is actually happening.
Role
Product concept, UI direction, and presentation
Focus
Device status, routines, and simple controls
Status
Concept with room for higher-fidelity screens
These keep MuHome from turning into another generic dashboard full of controls.
The app should show what the home is doing right now before asking the user to dig through rooms, icons, or automations.
Moments like leaving the house or winding down at night should feel like clear flows, not hidden settings.
If automation gets something wrong, the user should be able to fix it quickly without fighting the app.
MuHome is still a concept, but the direction is specific enough to show the product thinking behind it.
A dashboard that makes the current home state easy to scan.
Scenes and routines that feel editable instead of mysterious.
Lighting and media controls that do not become a wall of toggles.
Automation feedback that says what changed and why.
Example flow
The user sees the current room state first: which lights are still on, what media is active, and whether any scheduled routine is about to run.
Instead of jumping between rooms and tabs, the interface offers the next sensible actions together: dim shared spaces, pause media, and trigger a preferred nighttime scene.
If something looks wrong, manual control stays close. The app should not force the user to trust hidden logic more than they should.
MuHome shows how I think through a product problem. It is not pretending to be a finished startup.
Turns a broad smart-home idea into a clearer app direction.
Shows how I think through status, hierarchy, and user actions.
Presents the idea cleanly enough for someone else to judge it.
I can walk through the product thinking, interface decisions, and what I would improve in the next version.