← All work Say hello
TIPTIP · 2026 · CASE STUDY

TipTip Revamp

Redesigning the Homepage and Event Details of an Indonesian ticketing platform, so buying a ticket feels easy and safe.

ROLESenior Product Designer, led Event Details
TEAMPM, Design team, Engineering
TIMELINE2026, ongoing
PLATFORMMobile app & web
New TipTip Homepage and Event Details on two phones
8.7 / 10usability test score for the new design, against 6 for the current site
0 of 7buyers got stuck on search, the event page or picking a ticket
35 of 36homepage build issues on web fixed after design review
01THE PROBLEM

A ticketing site that still looked like a marketplace.

TipTip started as a creator marketplace. Digital content, live sessions and subscriptions have since been shut down, and events are the only thing left. The website never caught up: it still looked and spoke like a marketplace.

“It used to look like a government website.”Usability test participant, about the current TipTip.
“Old TipTip felt like a department store.”“Too many things, too crowded.” Another participant, same study.
Old TipTip homepage and event page
Where we started: events mixed with digital content, creator profiles and commission banners.

Everything here is a screenshot. TipTip’s Figma files, documents and research notes are confidential.

02THE GOAL

Make buying the ticket easy and safe.

Every participant already knew which event they wanted before opening a ticketing site. So the site’s job is simple. We set three goals:

  • Look and sound like an event ticketing platform
  • Everything needed to decide, on one page
  • Plan for every situation, from sold out to cancelled
03APPROACH

A system first, then pages, then proof.

I worked from the PM’s PRD with the design team and engineering, through benchmark, exploration, self-review, usability testing, then a build review against staging.

Foundations before pagesTipTip v2.0, our new Figma library: 43 components, 209 variants, 51 color styles and 1,500+ icons.
Six Claude skillsBenchmark, product knowledge, UX critique, UX writing, copy review and web QA. AI gave a fast first pass; I made every call.
Tested before any codeA clickable Figma prototype in front of real buyers, before engineering started.
04RESEARCH

Seven buyers, one clickable prototype.

I led one-on-one usability tests with 7 ticket buyers, 4 on mobile and 3 on desktop: 60 minutes each, 6 tasks from signing up to picking a ticket. Payment wasn’t part of it, so the numbers show direction rather than proof.

“Seeing this prototype, it finally feels like an event ticketing platform. The old one was all mixed up.” Danny, existing TipTip user

Spotlight vs TrendingBuyers couldn’t tell them apart, so Trending became Best-Selling Events.
Create Event got in the wayIt interrupted buyers, so it moved into one organizer banner near the bottom.
Does the price include tax?The price list now says prices exclude tax and service fee.
05KEY DECISIONS

What I designed, and why.

DECISION 01

Real events first, marketplace leftovers out

Most buyers land on mobile straight from Instagram or TikTok. The homepage now opens with a big banner and six Spotlight picks. Create and digital content are gone from the buyer’s path.

Homepage before and after, as a guest and signed in
Homepage before, then after as a guest and signed in.
DECISION 02

The homepage changes with the visitor

Guests, signed-in buyers and buyers with an unpaid order each see a slightly different page. An unpaid order comes first, with a live timer. Nearby events ask for location before assuming, and no section is ever left blank.

Homepage states: unpaid order, no location yet, nothing to show
Unpaid order, no location yet, and nothing to show.
DECISION 03

Decide on one screen

Event Details is where buyers decide if an event is worth their money. Poster, date, place and ticket prices sit up top. Tabs stay pinned and follow the section in view, and the price bar never leaves the screen.

Event Details before and after, first screen and while scrolling
Event Details before, then the first screen and while scrolling.
DECISION 04

Price first, then the details

In testing, the first thing buyers looked for was the price. So price and Buy Tickets stay pinned, sold-out tickets are greyed out in one honest list with a tax note, and posters open full size because they carry the lineup.

Event Details with pinned price, ticket list and full size poster
Pinned price bar, the ticket list and a full size poster.
DECISION 05

One page, many situations

Coming soon, almost sold out, fully booked, already bought, cancelled, ended. Only a small strip and the button change; everything else stays where buyers expect it.

Six Event Details states from coming soon to event ended
Six states of the same page.
DECISION 06

Words are design too

I wrote a UX writing guideline to retire the marketplace words: Produk became Event and Tiket, Kreator became Penyelenggara, Stok became Sisa tiket. Warm by default, calm and plain whenever money, tickets or refunds are involved.

06IMPACT

Early signals, and a build that matches the design.

  • 8.7 vs 6: test score for the new design against the current site
  • 0 of 7 buyers failed the core buying tasks
  • 35 of 36 homepage issues on web and 7 of 7 mobile app issues fixed after the build review
  • Homepage is built and reviewed; Event Details is in build review now
07REFLECTION

Most of the work lives in states buyers rarely see.

Testing early was cheap, and it changed real decisions. And renaming a section often fixed more than moving it: words are design.

Next is testing checkout and payment, the one part nobody has tried yet. After launch, I’ll track event page to checkout, and unpaid orders recovered.

NEXT CASE STUDY