Website, App and Design System
Building the digital ecosystem for an Australian luxury electrical brand
What we did
- Product strategy
- UX research
- IA
- E-commerce
- iOS and Android
- Design system
- Dev handoff


The problem
“We want to be the Dyson of the electrical world.”
That was the founders’ brief. They had a beautiful switch, no website, and an app they’d built that didn’t sell the idea.
-
Most buyers had never owned a smart switch, and Akāvi costs several times a normal one. The website had to make it feel worth it. The app had to make it easy.
-
I owned the strategy, the scope and how the website and app fit together. I ran the founder reviews, worked with the brand team and took the final calls.
-
The website is where people find Akāvi and fall for the product. The app is where they explore it, like walking into their own home: one switch, then the next room, then the next. The more they explore, the more they buy, and the easier the home gets.

-
- Research done in two weeks instead of months
- The founders gave us their brand work too
- A tokenised design system they own
Where we started
Akāvi came to us before launch. The switches were ready, the brand was in place, and the founders had already built a first version of the app. What they needed was a way to sell the product online, and an app people could actually get through.
On the website
- 01Nobody has shopped for a smart switch before
- 02It costs a lot more than a normal switch, so the price needs a reason
- 03People order long before their house is ready
In the app
- 01Too many features thrown at people on day one
- 02Pairing a device was hard, so people gave up
- 03Scenes and Insights, the best parts, were hidden
How I led the team
I was the design lead, with 3 UX designers and 1 UI designer. I set the scope, split the work, and took the final call whenever the website and the app needed different things. When the brand project came to us, we also worked closely with the brand team.
Scope, IA, final calls
We figured out how to sell the switch before designing how people set it up. The app then picked up the same story.
Onboarding stops after one switch. Everything else comes later, as small tours inside the app.
Their type and colour choices went straight into the design system, so we didn’t have to redo it later.
The approach
We split the work into two parts, the website and the app, because each had a different problem to crack.
Website
Part 1 of 2On the website, the job was discovery. People had to find Akāvi and, within a few scrolls, feel they were looking at a luxury product, not a switch.
OLUFSEN
There aren’t many direct competitors, and Clipsal and ZETR mostly sell on specs and range. So we looked wider, at brands that sell premium objects for the home and the self. That’s where the Range Rover-like feel came from: big visuals, short copy, the product up close.
- They don’t compare specs. They buy on feel and finish.
- Every object in the house has to belong there.
- Very little patience for anything technical.
We spoke to luxury homeowners, ran the interview notes through Dovetail AI to group what came up, and then checked every pattern ourselves.
We built the site like a magazine. Think Vogue, but for the home. Then we carried that into the cart, so a product this expensive still felt calm to buy.
- 1Homepage
Film and room shots, one line of copy per section
- 2Product page
The switch up close, in every finish
- 3Configure
Finish, then buttons, then bracket
- 4Cart
Pick a delivery date, change it until dispatch
We also gave sustainability its own page, and used 4design’s renders all through the site.


App
Part 2 of 2The app had the opposite problem. Akāvi’s devices are packed with features, and the risk was overwhelming people in the first five minutes.
The good ones get you to one working device fast, and only show you more once you’re comfortable.
- Pair one switch
- Name it, pick a room
- No switch yet? Demo mode
- Devices by room
- Dimming and timers
- Home summary
- Scenes
- Insights
- Motion sensor and modes
Every feature went into one of three groups, and a group only opens up once the one before it is working. Scenes and Insights, the reason people buy, got their own tabs.
Design system
We built the design system alongside the screens, not after. When the brand project came to us, the brand team’s type and colour choices went straight into our base tokens, so the brand, the website and the app all pull from one place.

wine.700gold.400ivory.50neutral.950surface.basetext.primaryaccent.activeborder.subtlebutton.primary.bgtoggle.track.onscene-card.radiusswatch.ring.selected


// tokens/semantic.json: one name, two modes. Builds CSS for the web, Swift and Kotlin for the app. { "surface.base": { "dark": "{neutral.950}", "light": "{ivory.50}" }, "accent.active": { "$value": "{gold.400}" } }
Impact
Months of research, done in two weeks
We used AI to scan the market, sort through reviews and draft early mockups, then checked everything ourselves.
A second project
The speed earned their trust, and the founders gave us their brand work as well.
Lower cost, earlier launch
Less time on research and rework brought the cost down, so the founders could plan their launch months earlier.
A system they own
A tokenised design system across web and app, ready for the next product line.
This project is under NDA
Want to see the whole thing?
I’ve only shown parts of it here. Leave me a message and we’ll get on a call, and I’ll walk you through the full process and the final screens.
shivamar275@gmail.com
LinkedIn