Smart home case study | Shivam Arora
01 / AkāviE-commerceSmart homeLuxury

Website, App and Design System

Building the digital ecosystem for an Australian luxury electrical brand

A launch website that sells a luxury switch, and a revamped app that sets it up and turns the home’s energy use into simple insights.

Year
2025–2026
Role
Design Lead
Team
1 UX Lead, 3 UX Designers, 1 UI Designer

What we did

  • Product strategy
  • UX research
  • IA
  • E-commerce
  • iOS and Android
  • Design system
  • Dev handoff
Under NDA, ask for a walkthrough
Akāvi website homepage: a softly lit living room with the line Elegant and luxurious switches
Akāvi app home screen
Website homepage and app homeResponsive web, iOS, Android

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.

  1. 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.

  2. 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.

  3. 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.

    Close-up of the gold Smart UFO switch
    • Research done in two weeks instead of months
    • The founders gave us their brand work too
    • A tokenised design system they own
01

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

  1. 01Nobody has shopped for a smart switch before
  2. 02It costs a lot more than a normal switch, so the price needs a reason
  3. 03People order long before their house is ready

In the app

  1. 01Too many features thrown at people on day one
  2. 02Pairing a device was hard, so people gave up
  3. 03Scenes and Insights, the best parts, were hidden
02

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.

Design LeadShivam Arora
Scope, IA, final calls
UX DesignerWebsite
UX DesignerResearch
UX DesignerApp flows
UI DesignerVisuals and system
Brand teamJoined with the brand project
Calls I made
Website first

We figured out how to sell the switch before designing how people set it up. The app then picked up the same story.

One device in onboarding

Onboarding stops after one switch. Everything else comes later, as small tours inside the app.

Brand team in the loop

Their type and colour choices went straight into the design system, so we didn’t have to redo it later.

03

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 2

On 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.

Market researchDirect and wider

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.

Talking to customersSynthesised with AI
  • 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.

What we builtHomepage to cart

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.

  1. 1Homepage

    Film and room shots, one line of copy per section

  2. 2Product page

    The switch up close, in every finish

  3. 3Configure

    Finish, then buttons, then bracket

  4. 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.

Exploded render of a switch and its mounting box
Render by 4design
Gold two-button Smart UFO switch on a textured wall
Smart UFO, gold

App

Part 2 of 2

The app had the opposite problem. Akāvi’s devices are packed with features, and the risk was overwhelming people in the first five minutes.

Market researchSmart home apps

The good ones get you to one working device fast, and only show you more once you’re comfortable.

How we split the features3 groups
01 / Set upOnboarding
  • Pair one switch
  • Name it, pick a room
  • No switch yet? Demo mode
02 / UseEvery day
  • Devices by room
  • Dimming and timers
  • Home summary
03 / ExploreWhen they’re ready
  • 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.

04

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.

How it connectsBrand to code
Brand teamType, colour, tone
PrimitivesRaw values
SemanticWhat each is for
ComponentsShared parts
WebsiteCSS variables
AppSwift, Kotlin
Foundations8pt grid
Colour
Type
Display serif sample
Spacing4 to 64
Radius4 to full
Tokens3 tiers
Primitivewine.700gold.400ivory.50neutral.950
Semanticsurface.basetext.primaryaccent.activeborder.subtle
Componentbutton.primary.bgtoggle.track.onscene-card.radiusswatch.ring.selected
Components and handoffWeb and app
Room toggle
ToggleWeb and app
Finish swatches
Finish swatchWeb and app
Scene card
Scene cardApp
// 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}" }
}
05

Impact

01

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.

02

A second project

The speed earned their trust, and the founders gave us their brand work as well.

03

Lower cost, earlier launch

Less time on research and rework brought the cost down, so the founders could plan their launch months earlier.

04

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