Developer Informed MVP Design System
Enterprise SaaS design system for internal game management tools, creating a safer workflow and improving developer efficiency.
CLIENT
Riot Games - DevPlat
Role
E2E Lead Designer
Problem Statement
Problem Statement
Problem Statement
Value Proposition
Players and developers have distinct goals and needs, a unified tooling design system could streamline development, ensure consistency across teams, reduce technical debt and reliance on external frameworks.
The goals were:
Create a centralized, scalable design system that simplifies developer workflows.
An experience that works across teams prioritizing dense and scannable data, increased build safety, with design support in place.
Forward thinking system that might allow for all internal tooling to use one system, reducing maintenance costs by deprecating existing duplicate systems.
Value Proposition
Players and developers have distinct goals and needs, a unified tooling design system could streamline development, ensure consistency across teams, reduce technical debt and reliance on external frameworks.
The goals were:
Create a centralized, scalable design system that simplifies developer workflows.
An experience that works across teams prioritizing dense and scannable data, increased build safety, with design support in place.
Forward thinking system that might allow for all internal tooling to use one system, reducing maintenance costs by deprecating existing duplicate systems.
Connect to Content
Add layers or components to swipe between.
Value Proposition
Players and developers have distinct goals and needs, a unified tooling design system could streamline development, ensure consistency across teams, reduce technical debt and reliance on external frameworks.
The goals were:
Create a centralized, scalable design system that simplifies developer workflows.
An experience that works across teams prioritizing dense and scannable data, increased build safety, with design support in place.
Forward thinking system that might allow for all internal tooling to use one system, reducing maintenance costs by deprecating existing duplicate systems.
Value Proposition
Players and developers have distinct goals and needs, a unified tooling design system could streamline development, ensure consistency across teams, reduce technical debt and reliance on external frameworks.
The goals were:
Create a centralized, scalable design system that simplifies developer workflows.
An experience that works across teams prioritizing dense and scannable data, increased build safety, with design support in place.
Forward thinking system that might allow for all internal tooling to use one system, reducing maintenance costs by deprecating existing duplicate systems.
Designed Experience
Designed Experience
Aligned MVP Solution
Sharing The Invite Code
To make MVP launch dates, the simplest version allowing users to share access codes with friends was landed on. The result was a responsive flow, which provided users access through our system registration, and the ability to share an access code through their chosen method. Had we forced this experience through the console flow, it would limit user options. This solution allowed users to chose their own share path - be that email, discord, or text (as seen below!).
Sharing The Invite Code
To make MVP launch dates, the simplest version allowing users to share access codes with friends was landed on. The result was a responsive flow, which provided users access through our system registration, and the ability to share an access code through their chosen method. Had we forced this experience through the console flow, it would limit user options. This solution allowed users to chose their own share path - be that email, discord, or text (as seen below!).
Sharing The Invite Code
To make MVP launch dates, the simplest version allowing users to share access codes with friends was landed on. The result was a responsive flow, which provided users access through our system registration, and the ability to share an access code through their chosen method. Had we forced this experience through the console flow, it would limit user options. This solution allowed users to chose their own share path - be that email, discord, or text (as seen below!).
Redeeming A Shared Code
Redeeming a code shared by your friend, needed to be as simple as registration. The flow was the same, except the landing page had a unique code tied reflecting the registered user it came from. The friend just needed to log in, choose their platform, and you're ready to play!
Redeeming A Shared Code
Redeeming a code shared by your friend, needed to be as simple as registration. The flow was the same, except the landing page had a unique code tied reflecting the registered user it came from. The friend just needed to log in, choose their platform, and you're ready to play!
Redeeming A Shared Code
Redeeming a code shared by your friend, needed to be as simple as registration. The flow was the same, except the landing page had a unique code tied reflecting the registered user it came from. The friend just needed to log in, choose their platform, and you're ready to play!