Role
Product Designer
Tools/Skills
Figma, Figjam, Jira
Team
PM, Devs
Duration
6 months
BACKGROUND
Friction in development
When I joined AstroLive, the product was already live and actively being developed. The team was developer-heavy, features were moving quickly, and design decisions were largely driven by immediate implementation needs.
PROBLEM SPACE
Absence of " What's Next "
At the file level, there were no design tokens or variables. Colors were applied visually rather than systematically, spacing was inconsistent, and components were recreated multiple times with slight variations. This made it difficult for developers to implement designs predictably and increased the risk of inconsistencies with every new feature.
APPROACH
Establishing Structure
I spent almost two weeks going through the existing file, untangling clutter, understanding what worked and what didn’t, and gradually shaping a clear direction for how the design system should be organized moving forward.
SOLUTION
Building the Design System
Throughout the implementation of the AstroLife design system, I closely studied the Material 3 Framework—reviewing them one by one and taking a deep dive into their structure—to apply the same principles as accurately and consistently as possible.
Collaboration and Handoff
I worked closely with developers and the Product Manager throughout the process. Design decisions were explained in walkthrough sessions, and detailed handoffs were supported through Jira tickets to ensure clarity during implementation.
Outcome
The design system was rolled out gradually across sprints rather than through a full relaunch. As new features were developed or existing ones updated, they adopted the system incrementally.
REFLECTION
Key takeaways
My Full Experience
If you’re interested and wanna deep dive in learning more about what I worked on in more detail, you can access it here.







