From Interest to Action
Arcatar’s value proposition is simple but powerful: customers can launch their own private-label platforms — fully branded spaces where they own their content, community, and commerce. For owners, this meant being able to customize the look and feel of their platform to reflect their unique identity, while still operating within Arcatar’s shared infrastructure.
As part of a two-person design team, I co-owned the creation of a flexible design system that allowed for customization across colors, typography, iconography, and UI styling, without breaking consistency or usability.
SKILLS
Wireframing / Design / Example
TOOLS
Figma / Jira / Example
MY ROLE
Design Lead
CLIENT
Arcatar
The Challenge
Owners wanted platforms that felt truly theirs. However:
Too much flexibility risked breaking usability (e.g., low-contrast colors).
Too little flexibility risked feeling generic (not distinct enough from other platforms).
The system had to be scalable and efficient, so new owner platforms could spin up quickly without reinventing the wheel.
The challenge: design a system that was both branded and standardized.
Discovery & Research
Tab 1
Tab 2
Tab 3
Arcatar serves a diverse customer base — from touring creators and gaming streamers to education orgs and nonprofits. Each customer’s platform needs to accommodate very different types of users:
• Owners: manage the overall platform and branding.
• Creators: publish content, manage subscribers, and track engagement.
• Subscribers & Members: access gated spaces, chat, and community features.
The challenge was to design a system that gave each role just the right features and permissions — enough to be powerful, but not overwhelming — while keeping the experience consistent across the product.
Design Approach
Tab 1
Tab 2
Tab 3
Arcatar serves a diverse customer base — from touring creators and gaming streamers to education orgs and nonprofits. Each customer’s platform needs to accommodate very different types of users:
• Owners: manage the overall platform and branding.
• Creators: publish content, manage subscribers, and track engagement.
• Subscribers & Members: access gated spaces, chat, and community features.
The challenge was to design a system that gave each role just the right features and permissions — enough to be powerful, but not overwhelming — while keeping the experience consistent across the product.
Testing
Tab 1
Tab 2
Tab 3
Arcatar serves a diverse customer base — from touring creators and gaming streamers to education orgs and nonprofits. Each customer’s platform needs to accommodate very different types of users:
• Owners: manage the overall platform and branding.
• Creators: publish content, manage subscribers, and track engagement.
• Subscribers & Members: access gated spaces, chat, and community features.
The challenge was to design a system that gave each role just the right features and permissions — enough to be powerful, but not overwhelming — while keeping the experience consistent across the product.
Collaboration
Arcatar serves a diverse customer base — from touring creators and gaming streamers to education orgs and nonprofits. Each customer’s platform needs to accommodate very different types of users:
• Owners: manage the overall platform and branding.
• Creators: publish content, manage subscribers, and track engagement.
• Subscribers & Members: access gated spaces, chat, and community features.
The challenge was to design a system that gave each role just the right features and permissions — enough to be powerful, but not overwhelming — while keeping the experience consistent across the product.
Outcomes
We delivered a role-based UX that balanced clarity with scalability:
• Owners gained clear access to customization and platform controls.
• Creators had streamlined publishing and analytics tools, supporting monetization.
• Subscribers/Members saw a clean, focused interface without unnecessary clutter.
This framework became the foundation for Arcatar’s private-label platforms, ensuring that each customer could serve their unique communities while keeping the product maintainable.
Retrospective
This project taught me how to design for complexity without overwhelming users. The role-mapping approach gave structure to a fast-moving startup environment and made the product scalable for different customer types.
If I could refine further, I’d invest earlier in user testing with real role-based users (e.g., actual creators and subscribers) to validate assumptions before rollout.