top of page
background.png
top thesis

Building the design system behind Playhouse

Playhouse is an AI-powered social app that helps people connect and meet up. I designed and refined its interfaces while building a Figma library of 500+ reusable components and variants to support its launch.

ROLE

Product Designer, Design Systems

TIMELINE

January - April 2025

FOCUS

Interface Refinement, Figma Library

Playhouse — Phone showcase.png
top duo
background.png

Bringing the pieces together

I moved the existing designs from MasterGo into Figma and developed the shared component library. Along the way, I refined designs, updated variants and adjusted interface copy.

The work brought two connected responsibilities together: improving the interfaces people would use and organizing the reusable pieces behind them. Rather than treating the library as a separate output, I worked across the screens and their shared patterns as the system took shape.

MasterGo to Figma migration.png

Moving the existing interfaces into Figma created the workspace for the shared component library.

adbg.png

01/ THE SHARED LIBRARY

Organizing the library

The library grouped the system into foundations, components, icons, and patterns or templates. The team walkthrough introduced both the page structure and the local text and color styles, making the organization part of the guidance rather than leaving people to discover it on their own.​​

adbg.png
Library organization overview.png

The library grouped foundations, components, icons and patterns so the team could find the right starting point.

adbg.png

02 / FLEXIBLE COMPONENTS

Making room for different states

Reusable components let the team adapt screens for different content and interactions. The examples below show how imagery, text and button states could change within the system.

background.png

I added variants and editable properties to a shared meetup card. The reference frame shows how the team could update its content and toggle optional details without rebuilding the layout.

Adding variants and component properties.png

A shared meetup card with variant controls and editable properties for its content, status and optional details.

background.png

I updated variants as part of the interface work. The Invite / Sent examples show how a component can communicate both the available action and its resulting state.

In the team exercise, the invitation action uses a yellow Invite variant, while the completed action uses a muted Sent variant. Showing both in context makes the state change easier to understand and gives the team a concrete reference when assembling screens.

Invite and Sent variants.png

The sharing exercise demonstrates the Invite / Sent variants alongside the full action sheet.

adbg.png

03 / GUIDANCE & HANDOFF

Helping the team build with it

I created usage guidelines and a hands on demo to help the design and engineering teams use the library and carry the designs into development.

background.png

Since the teams were pretty new on Figma, I created usage guidelines and a hands on demo to help teach them how to use the library and carry the designs into development.

​

The walkthrough connected three parts of working with the system:

  • Find the right starting point: Enable the Playhouse library, use the Assets panel and bring components into a design.

  • Adapt an instance: Change images and text, explore button states, and understand the relationship between a component and its instances.

  • Keep the work connected: Find the main component, leave comments in Figma and review interaction flows for developer handoff.

Guidance and developer handoff.png

Selected material from the team walkthrough, enabling the library and reviewing interaction flows for handoff.

Playhouse — Phone showcase.png
background.png
background.png
background.png
  • LinkedIn
  • Facebook

Made with 💜 by Precious Aghaeze © 2026

bottom of page