/ Argus Labs: Developer Experience
Project Specs
As part of UX @ Berkeley, I worked with a cross-functional team to research and propose improvements to Argus Labs’ World CLI and Cardinal Editor. Argus Labs is a technology company that specializes in building open and decentralized platforms, tools, and infrastructure for gaming, with a focus on enabling developer innovation and fostering collaborative ecosystems.
As the sole Researcher and Designer, I conducted user interviews, usability testing, drafted a user flow, and synthesized findings into actionable recommendations and product improvements.
I presented the report and designs at the UX @ Berkeley End-of-Semester Showcase in front of 40+ of my peers and to the CEO and engineering team at Argus Labs.
As the sole Researcher and Designer, I conducted user interviews, usability testing, drafted a user flow, and synthesized findings into actionable recommendations and product improvements.
I presented the report and designs at the UX @ Berkeley End-of-Semester Showcase in front of 40+ of my peers and to the CEO and engineering team at Argus Labs.
Role
Lead UX Researcher and Designer
Worked w/ Engineering x3, PM x1
Lead UX Researcher and Designer
Worked w/ Engineering x3, PM x1
Tools
• Interaction design
• User research
• Usability testing
• User interviews
• Competitive analysis
• Written and verbal
communication
• Stakeholder
communication
• Figma
• Interaction design
• User research
• Usability testing
• User interviews
• Competitive analysis
• Written and verbal
communication
• Stakeholder
communication
• Figma
Tasks
1. Increase “beginner” game developer engagement.
2. Analyze the current onboarding flow for World CLI and Cardinal Editor.
3. Conduct usability tests and interviews with beginner developers to understand where they struggle.
4. Audit and enhance current documentation.
1. Increase “beginner” game developer engagement.
2. Analyze the current onboarding flow for World CLI and Cardinal Editor.
3. Conduct usability tests and interviews with beginner developers to understand where they struggle.
4. Audit and enhance current documentation.
Timeline
3 months
3 months
COMING SOON!