2024-2025
HYTE 2.0 Elastic Materials
HYTE 2.0 Elastic Materials
HYTE 2.0 Elastic Materials
HYTE, a sister brand of IBP, has grown rapidly since its establishment. To meet industry standards, the team set out to improve the e-commerce website by streamlining development processes and delivering a better experience for its users. The goal was to create a robust design system that ensures consistency, efficiency, and supports future growth.
HYTE, a sister brand of IBP, has grown rapidly since its establishment. To meet industry standards, the team set out to improve the e-commerce website by streamlining development processes and delivering a better experience for its users. The goal was to create a robust design system that ensures consistency, efficiency, and supports future growth.
HYTE, a sister brand of IBP, has grown rapidly since its establishment. To meet industry standards, the team set out to improve the e-commerce website by streamlining development processes and delivering a better experience for its users. The goal was to create a robust design system that ensures consistency, efficiency, and supports future growth.
Branding
Branding
Illustrations
Illustrations
Products
Products
UI/UX
UI/UX
Role
Role
UI/UX, Visual Designer
UI/UX, Visual Designer
Team
Team
1 Designer, 1 Developer, 1 PM
1 Designer, 1 Developer, 1 PM
Timeframe
Timeframe
May 2024 – Present
May 2024 – Present
Tools
Tools
Figma, Adobe XD, Illustrator, JIRA, Microsoft Clarity
Figma, Adobe XD, Illustrator, JIRA, Microsoft Clarity
Design System
Design System
Style guide 2.0
Style guide 2.0
What’s the problem?
What’s the problem?
HYTE’s design system wasn’t its own blueprint. It was patterned after MUI, which made it look complete but didn’t reflect the brand’s identity. About 80% of components had no defined usage, some essential ones were missing, and inflexible layouts created confusion and extra work during collaboration between designers and developers.
HYTE’s design system wasn’t its own blueprint. It was patterned after MUI, which made it look complete but didn’t reflect the brand’s identity. About 80% of components had no defined usage, some essential ones were missing, and inflexible layouts created confusion and extra work during collaboration between designers and developers.
HYTE’s design system wasn’t its own blueprint. It was patterned after MUI, which made it look complete but didn’t reflect the brand’s identity. About 80% of components had no defined usage, some essential ones were missing, and inflexible layouts created confusion and extra work during collaboration between designers and developers.



What can we do to make it better?
What can we do to make it better?
We revamped the design system to meet industry standards, establishing a comprehensive blueprint to improve development efficiency and brand consistency. The new system includes a component library, style guide, content guide, and documentation.
We revamped the design system to meet industry standards, establishing a comprehensive blueprint to improve development efficiency and brand consistency. The new system includes a component library, style guide, content guide, and documentation.
We revamped the design system to meet industry standards, establishing a comprehensive blueprint to improve development efficiency and brand consistency. The new system includes a component library, style guide, content guide, and documentation.



Competitor Analysis
Competitor Analysis
Reviewed top gaming and tech brands to extract effective patterns, layouts, and brand approaches, then tailored them to HYTE’s identity and user needs.
Research Data
Research Data
Audited HYTE’s products and, with stakeholders, identified inconsistent components, accessibility gaps, and inflexible layouts.
Aim
Aim
Strengthen the brand, improve usability, and streamline the design–dev workflow with a consistent, maintainable system.
How do we get started?
How do we get started?
First of all, we created an extensive library from scratch to development process. To ensure smooth process and communication with our devs and achieve our goal for the design system.
First of all, we created an extensive library from scratch to development process. To ensure smooth process and communication with our devs and achieve our goal for the design system.
First of all, we created an extensive library from scratch to development process. To ensure smooth process and communication with our devs and achieve our goal for the design system.
Style Guide
• Breakpoints
• Typography
• Iconography
• Spacers
• Grids
• Divider
• Color
Components
• Buttons
• Forms
• Alerts
• Badges
• Cards
• Tickets
• Tabs & Menu
Content Guide
• Principles
• Restrictions
• Usage
• Definitions
Documentation
• Best practices
• Editorial guide
• Implementation guide
• Do’s & Don’ts
What does our design system contain?
What does our design system contain?
We created 300+ components and 200+ tokens to support site functionality and visual hierarchy. Each component is curated to reflect the brand’s perspective and defined for use across likely scenarios. Here are a few sneak peeks from the system:
We created 300+ components and 200+ tokens to support site functionality and visual hierarchy. Each component is curated to reflect the brand’s perspective and defined for use across likely scenarios. Here are a few sneak peeks from the system:
We created 300+ components and 200+ tokens to support site functionality and visual hierarchy. Each component is curated to reflect the brand’s perspective and defined for use across likely scenarios. Here are a few sneak peeks from the system:



Color
Color



Typography
Typography



Forms
Forms



Spacers
Spacers



Buttons
Buttons



Alerts
Alerts



Tags
Tags



Cards
Cards
How does the design work?
How does the design work?
We applied an atomic design approach to enable dynamic usage across pages with different template layouts, making builds faster with preset components for both designers and developers. Below is one example of how they’re composed together:
We applied an atomic design approach to enable dynamic usage across pages with different template layouts, making builds faster with preset components for both designers and developers. Below is one example of how they’re composed together:
Atoms
Input Label
|
BUTTONS
Molecules
First Name
Enter your first name
Organisms
First Name
Enter your first name
Last Name
Enter your last name
Templates
Your Name
First Name
|
Last Name
Enter your last name
SAVE
CANCEL
Functionality & Features
Functionality & Features
Functionality & Features
Components
Components
Before
The old version had only two fixed styles, no states or guidelines, and every button was its own parent component, taking up space and making it slow to find what you need.
• Only two fixed styles, limited flexibility
• No states or usage guidelines
• Each button as a parent component, heavy on storage
• Slow to locate components
The old version had only two fixed styles, no states or guidelines, and every button was its own parent component, taking up space and making it slow to find what you need.
• Only two fixed styles, limited flexibility
• No states or usage guidelines
• Each button as a parent component, heavy on storage
• Slow to locate components



After
The new version is more flexible and compact. Adjustments take just a few clicks, and includes states, guidelines, a parent–child setup for faster loading, and clear naming for quick finds.
• Greater flexibility and dynamic usage
• Defined states and usage guidelines
• Parent–child component structure, reducing loading inefficiency
• Clear naming conventions for quick and easy location of components
The new version is more flexible and compact. Adjustments take just a few clicks, and includes states, guidelines, a parent–child setup for faster loading, and clear naming for quick finds.
• Greater flexibility and dynamic usage
• Defined states and usage guidelines
• Parent–child component structure, reducing loading inefficiency
• Clear naming conventions for quick and easy location of components





Variables & Tokens
Variables & Tokens
Before
Conventions and usage were scattered across multiple frames, making it slow to find the right info. Any change required tedious updates to individual elements.
• Scattered across multiple frames
• Time-consuming to locate information
• Tedious to update when one element changed
Conventions and usage were scattered across multiple frames, making it slow to find the right info. Any change required tedious updates to individual elements.
• Scattered across multiple frames
• Time-consuming to locate information
• Tedious to update when one element changed



After
Everything is organized into a single library with related categories grouped together, clearer naming, and faster syncing.
• Centralized library with related categories
• Clear numeric naming for quick reference
• One update syncs across all frameworks
Everything is organized into a single library with related categories grouped together, clearer naming, and faster syncing.
• Centralized library with related categories
• Clear numeric naming for quick reference
• One update syncs across all frameworks



How is it applied?
Here is a snippet of the in-progress submission modal, showing how tokens, components, and content guidance work together.
Here is a snippet of the in-progress submission modal, showing how tokens, components, and content guidance work together.
Here is a snippet of the in-progress submission modal, showing how tokens, components, and content guidance work together.
What we achieved from the design system
What we achieved from the design system
Although it took more steps to set up, it was worth it. Now we’ve got seamless collaboration between designers and developers. It’s quicker to find what we need, everything stays in sync, and one update fixes it everywhere, no more digging through files.
Although it took more steps to set up, it was worth it. Now we’ve got seamless collaboration between designers and developers. It’s quicker to find what we need, everything stays in sync, and one update fixes it everywhere, no more digging through files.
Although it took more steps to set up, it was worth it. Now we’ve got seamless collaboration between designers and developers. It’s quicker to find what we need, everything stays in sync, and one update fixes it everywhere, no more digging through files.
• Quicker search and access to components
• Consistent naming and structure
• Quicker search and access to components
• Consistent naming and structure
• Quicker search and access to components
• Consistent naming and structure
• No more repetitive manual updates
• Smoother handoff between design and dev
• No more repetitive manual updates
• Smoother handoff between design and dev
• No more repetitive manual updates
• Smoother handoff between design and dev
© 2021–2025 Designed by Sena Lim. Don’t steal, unless you're a raccoon.
© 2021–2025 Designed by Sena Lim. Don’t steal, unless you're a raccoon.
This site was built between naps and breakdowns.
This site was built between naps and breakdowns.