App
Claimed Ticket
See Event Information
EMPATHIZE
On this project, I collaborated with UX Researcher to got user feedback from previous version We did research from interview users of company and we gave users test case to took action so we could see the pain poin user.
The Old Version
Designed by another designer




Define
Users had no contextual understanding of the event (what it's about, where, when, or why they should join). Information gaps led to frequent switching between the app and external sources. The lack of integrated content also meant missed opportunities to engage users or highlight key event promos. Users with tickets had no clear place to track their ticket status or access usage instructions.
Ideation & Exploration
On the step, i found the ideation as many as and explore the design from Dribbble, Mobbin, and other platforms. Then, i did filter to prioritize design that possibly to build on this project. I also discussed with PM and developer to ensure my design could implement on this project based on time and capacity of development
High Fidelity Design









Evaluation
Designing for information completeness is just as important as visual polish. Users rely on context to act confidently.
Tab-based layouts are powerful when paired with well-defined user states.
Even small clarity enhancements (like status messages or fallback content) make a huge difference in high-stakes flows like ticketing.
