Case study 02, 2026
MXperience Club — A community platform for Logitech MX creators in Indonesia
One journey designed and built end to end, from finding an event to holding a ticket: Discover, Join, Attend, Connect, Return.
- Role
- Design and front-end, built from scratch
- Status
- Live, prototype flows
Context
MXperience Club is a community platform for creators, designers, developers, and creative professionals in Indonesia, with Logitech MX as the product context.
To write: Who asked for it, and what your brief was.
The problem
To write: Where events and members lived before MXperience Club, and what broke for members and organisers.
Admission rules (ticket types, access codes, approvals) had to be clear before someone invested time in a form — and online events needed a different kind of information than offline ones.
Framing
Design the journey, not the homepage: Discover, Join, Attend, Connect, Return. Every screen had to move a member one step along it.
The first draft came from an AI prompt. The work was deciding what to keep, what to cut, and which rules the interface had to enforce.
Key decisions
Decision 1
Access code before the form
Members pick a ticket type and validate an access code (VIP, Media, Community) before filling anything in, so nobody completes a form only to be turned away.
Decision 2
No fake maps for online events
Online events show the platform and how to join instead of a placeholder city or map. The meeting URL appears only on a confirmed ticket.
Decision 3
Accessible by default
16 px body text, 14 px minimum for supporting text, touch targets around 44 px, visible keyboard focus, reduced motion respected, light and dark themes, Indonesian and English.
The solution
Discovery that filters the way people decide
Upcoming and past events filter by online or offline, free or paid, curated or open. Event pages carry schedule, venue or online access, speakers, and seat availability next to the registration action.
From registration to ticket
Dynamic questions, consent, waiting, approved and rejected states, a QR ticket, and My Tickets. Admission information appears once, close to the action.
AI draft versus what shipped
Side by side, the first prompt output and the shipped homepage show where AI stopped and design decisions took over: hierarchy, real content, and admission rules.
Where it stands
- Journey stages, from Discover to Return
- 5
- Minimum touch target across the flows
- 44 px
- Front end at mxperienceclub.com; payment, sign-in and ticket email are prototyped
- Live
Reflection
To write: What critiquing the AI draft taught you about your role as a designer (this is the core of your MX Fest talk).