Aftershock: Design System & Rig Finder
Aftershock: Design System & Rig Finder
Created a scalable design system for a gaming e-commerce redesign, plus a Rig Finder page that grew engagement by 17%
Created a scalable design system for a gaming e-commerce redesign, plus a Rig Finder page that grew engagement by 17%
I contributed to the design system behind Aftershock's redesigned website, a gaming PC brand serving gamers and tech enthusiasts, and designed the Rig Finder, a guided quiz that helps people find the right PC.
I contributed to the design system behind Aftershock's redesigned website, a gaming PC brand serving gamers and tech enthusiasts, and designed the Rig Finder, a guided quiz that helps people find the right PC.
Design System
Design System
E-commerce
E-commerce
Web & Mobile
Web & Mobile
Gaming
Gaming

Overview
Overview
Role
UX/UI Designer
Duration
9 months
Scope
Website, Design System
Team
PM, Senior Designers & Developers
Aftershock builds custom gaming PCs and laptops for a growing audience of gamers and tech enthusiasts. As the brand grew, so did its website, and the interface started to feel inconsistent from page to page.
The website was redesigned to better support that audience. The challenge was to improve usability and consistency across the interface, while laying the groundwork for a design system that could scale and stay easy to maintain.
I worked alongside senior designers and developers: contributing to the design system, designing key pages and flows with it, and supporting the team through implementation.
Layla is a B2B SaaS platform connected to IoT sensors, giving property managers real-time visibility into properties they can't always be physically present in. Its users manage anywhere from 10 to 50+ properties at once — global, distributed, and often under high operational load with mixed technical proficiency.
Over two years, I led UX research from the ground up, built the design system from scratch, and redesigned the mobile app end-to-end for both iOS and Android. Working with an IoT-based product also meant going deep into technical research — I read through extensive sensor documentation to fully understand device capabilities and unlock features that weren't yet being used in the product.
This required close, ongoing communication with both hardware and software engineering teams to translate technical constraints into a mobile experience that actually worked.
Impact
Impact
A platform people actually used to talk to their government.
A platform people actually used to talk to their government.
UI components standardised across desktop and mobile
conversion
foundation areas documented
The Challenge
The Challenge
Buying a gaming PC is a big decision, and Aftershock's customers range from hardcore builders who know every spec to people buying their first rig. The website had to work for both, on desktop and mobile.
But as the site grew, the same elements were being designed in slightly different ways: buttons, inputs, cards and navigation that looked almost the same, but not quite. That slowed the team down and made the experience feel less polished than the products themselves.
Buying a gaming PC is a big decision, and Aftershock's customers range from hardcore builders who know every spec to people buying their first rig. The website had to work for both, on desktop and mobile.
But as the site grew, the same elements were being designed in slightly different ways: buttons, inputs, cards and navigation that looked almost the same, but not quite. That slowed the team down and made the experience feel less polished than the products themselves.
Research
Research
Before redesigning anything, I ran lightweight research with gamers and tech enthusiasts: short interviews, feedback analysis and usability checks on the existing site. It helped the team understand where people got stuck, especially when comparing PCs and making sense of technical specs, and gave us real input to shape the new website.
Before redesigning anything, I ran lightweight research with gamers and tech enthusiasts: short interviews, feedback analysis and usability checks on the existing site. It helped the team understand where people got stuck, especially when comparing PCs and making sense of technical specs, and gave us real input to shape the new website.
Foundations
The system started with the basics everything else would rely on.
An 8-point grid
Every element, from icons and type to spacing and whole components, follows multiples of 8. Desktop uses a 12-column grid at 1440px, and mobile switches to 4 columns, so layouts adapt smoothly between breakpoints.
The system started with the basics everything else would rely on.
An 8-point grid
Every element, from icons and type to spacing and whole components, follows multiples of 8. Desktop uses a 12-column grid at 1440px, and mobile switches to 4 columns, so layouts adapt smoothly between breakpoints.

8-point spacing scale, from 4px to 96px, used for every element and layout
Colour with a job to do
Beyond the brand's signature red and dark greys, colours were organised by purpose: text, icons, messaging (information, warning, success, error) and product badges like Selling fast, Delayed or Out of stock. That way, a colour on the site always means something.
Colour with a job to do
Beyond the brand's signature red and dark greys, colours were organised by purpose: text, icons, messaging (information, warning, success, error) and product badges like Selling fast, Delayed or Out of stock. That way, a colour on the site always means something.

Colour palettes organised by purpose: brand, UI, text, icons, messaging and badges
A type pairing with character
Big Noodle Titling gives headings the bold, gaming feel of the brand, while DIN 2014 keeps body text and labels clean and readable. Both have separate desktop and mobile scales.
A type pairing with character
Big Noodle Titling gives headings the bold, gaming feel of the brand, while DIN 2014 keeps body text and labels clean and readable. Both have separate desktop and mobile scales.

Type system: Big Noodle Titling for headings, DIN 2014 for body and labels, with desktop and mobile scales
These foundations became basic design tokens for colour, spacing and typography, so the interface stayed consistent and changes could be made in one place instead of on every page.
These foundations became basic design tokens for colour, spacing and typography, so the interface stayed consistent and changes could be made in one place instead of on every page.
Components
Components
On top of the foundations, we standardised 30+ components used across the site:
Buttons in primary, secondary, icon, small and link styles, each with default, hover and disabled states, plus guidance on when to use which
Form elements: inputs, labelled fields, dropdown selectors, checkboxes, radio buttons and a quantity selector
A full icon set, including PC-specific icons for CPU, GPU, RAM, SSD, fans and chassis
Badges and trust elements: product status badges, payment options and press logos
Shopify components, so the checkout matched the rest of the site
Everything was named consistently and organised for developers, which made handoff faster and reduced back-and-forth during implementation.
A few patterns kept showing up across every interview:
Users think in urgency, not in data.
Nobody wanted to browse metrics. They wanted to know whether something needed them right now.
Scale changes everything.
What feels manageable with 3 properties breaks completely at 30. The app had to work for the busiest manager, not the average one.
Context beats raw values.
"75 dB" means nothing on its own. Users needed to know if a reading was normal, rising, or a problem.
Confidence matters more than completeness.
Managers didn't need every data point. They needed to trust that sensors were online and the data was live.

Buttons: 4 sizes, 2 styles, 3 states

Icons, logos and badges: a shared visual language for navigation, PC specs, stock status and payment
Rig Finder
Rig Finder
The Rig Finder was where the system and my own design work came together. Choosing a gaming PC can be overwhelming, so the Rig Finder turns it into a short quiz: what games you play, what else you use your PC for, the size and style you like. At the end, it recommends a few rigs that match.
To make recommendations easy to understand, each result shows how well it fits your needs using the system's performance language: a PC can fall short, meet or exceed what you're looking for, with matching colours and icons. Badges like Our pick and Needs tweaking help people decide in seconds, and they can save or share their results or start over.
I designed the wireframes, prototypes and user flows for it, built entirely with system components.
The Rig Finder was where the system and my own design work came together. Choosing a gaming PC can be overwhelming, so the Rig Finder turns it into a short quiz: what games you play, what else you use your PC for, the size and style you like. At the end, it recommends a few rigs that match.
To make recommendations easy to understand, each result shows how well it fits your needs using the system's performance language: a PC can fall short, meet or exceed what you're looking for, with matching colours and icons. Badges like Our pick and Needs tweaking help people decide in seconds, and they can save or share their results or start over.
I designed the wireframes, prototypes and user flows for it, built entirely with system components.

Rig Finder quiz, desktop and mobile

Rig Finder results: recommended rigs with performance bars showing where each one falls short, meets or exceeds your needs
Learnings
Learnings
A good system lets you build from what already exists.
The Rig Finder was a completely new feature, but I didn't have to invent anything for it. Colours and badges already had a clear meaning, like falls short, meets and exceeds, so I could build the whole flow from components we already had.
Fix it once, and every screen updates.
Before the system, changing a button meant finding it on every page, and there were eight versions of it. Once pages were built from shared components, one change to the component updated it everywhere. That's why I always try to reuse before adding something new.
When names match the code, handoff is easier.
At first, naming components and states felt like a tidy-up task. Then I noticed that when our names in Figma matched what developers used in code, there were fewer questions and fewer mismatches. Now I treat naming as part of the design.
Learning from senior designers early shaped how I work.
This project was my first deep dive into design systems, and it's where I learned how structure, naming and documentation make a system something a team actually uses. It's the foundation for the systems I've built since.
Understand the system before designing the interface.
Working on an IoT product taught me that the most important design decisions often come from outside Figma: sensor logs, hardware limits, how data actually arrives. Learning the technical side early saved us from designing things that could never work reliably.
Start with what's broken, not with the brief.
"Redesign the app" could have meant a fresh coat of paint. Digging into tickets, reviews and interviews first turned it into a clear problem: people didn't know what needed their attention. Everything else followed from that.
Design is a shared language.
The biggest shifts happened when engineering, sales and product could see the same prototype and talk about the same scenario. Making decisions visible did more for alignment than any argument could.
What I'd do next
Toward the end of my time at Layla, the company started selling sensors directly to consumers on Amazon. That would change the app's biggest challenge: from helping managers prioritise many properties to helping a first-time homeowner set up a single device on their own. Self-serve onboarding and even clearer, plain-language data would be where I'd start

Three things this project taught me about building and using a design system