Go to market · Plume · Design System & Product Design · 20 Oct 2026

Plume: the design system and the apps it shipped.

A new case study, separate from Data Stories. The product and system work you led as Principal Designer is missing from the site, and so is the brand systems work. This page gathers what exists, so the case study can be built in Figma.

01 The test

A design lead who has never heard of Plume opens the page and, from the opening alone, can say what Plume makes, what shipped, who built it, what you did and with what. The same test as Glydways.

02 What is missing from the site

  • Product design: HomePass, the consumer Wi-Fi app, and the operator-side tools.
  • Design systems: the mobile design system and the dashboard design system.
  • Brand systems: Plume brand work beyond Data Stories.

03 The work on record

WorkWhat it isFacts on recordSource
HomePassPlume's consumer app for running home Wi-Fi. iOS and Android.Redesign to fix three problems: slow, dated, cluttered. Launched globally. Android rating 4.19 → 4.55. 78% of new iOS ratings were 5-star at peak after launch.hotha.me/homepass
Mobile Design SystemThe first design system for Plume's iOS and Android apps, built from scratch.Semantic tokens for color, type, radius and spacing. Light and dark modes. One core component, Left · Middle · Right, used 549 times in the app. Figma components documented with developer notes.hotha.me/mobile-design-system
Operator SuitePlume's tools for the internet providers that run its network.Locked on the source. Needs your material.hotha.me (locked)
Dashboard Design SystemThe system behind the operator dashboards.Locked on the source. Needs your material.hotha.me (locked)
Brand systems—Not on the site anywhere. Needs your list.You

Dates come from your years at Plume, not from his page. Credit: the product facts come from the public portfolio of Shravan Hotha, who reported to you and is credited there as lead or co-lead. The case study names him. Your own role is stated in your words, never inferred from his page.

04 The case study, proposed

  • Name: Plume Design System. One page for the system and the products built on it.
  • Ground: light.
  • Hero: HomePass on a phone in a home, then the system sheet.
  • Brief: Shipped · Outcome · Role · Team · Stack. Shipped: HomePass on iOS and Android, global, your dates. Outcome: Android 4.19 → 4.55; one core component used 549 times. Role: Principal Designer. Team and Stack: to fill.
  • Chapters: System (tokens, light and dark, the one core component) → Product (HomePass, then Operator Suite and dashboards) → Implementation (Figma to engineering) → Decisions → How it's built.
  • Related Work: Data Stories, and the brand systems page once it exists.

05 For Figma today

  1. Cover: HomePass in place, 2560 × 1440.
  2. Before and after: the three problems, slow, dated and cluttered, against the shipped screens.
  3. System sheet: color in light and dark, type, radius, spacing.
  4. The one core component: Left · Middle · Right and the atoms it holds.
  5. Operator side: one dashboard screen, if it can be shown.

06 Only you have these

  • Your role in your words: what you set, what you reviewed, what you shipped yourself.
  • Your years at Plume.
  • Team: size and functions, and who else to credit.
  • What can be shown from Operator Suite and the dashboards.
  • The brand systems work to add, by name.
  • Stack beyond Figma: iOS, Android, web.