E-Seats
Buying a ticket without ever leaving the event page
E-Seats is a Georgian ticketing platform: concerts, theatre, sport, seminars — you find the event, pick a ticket, pay, and the ticket lands in your pocket as a QR code. I designed the whole product: the browsing, the checkout, the account area, and the design system that renders it all in dark and light across desktop, tablet and phone.
Role
Product Designer
Platform
Web · responsive
Scope
Full product · design system
Year
2025

A ticket is an impulse. The design’s job is to not interrupt it.
Someone hears their favourite singer is coming to town and wants two tickets — right now, on whatever device is in their hand. Every extra screen, every forced signup, every surprise fee between wanting and having is where a ticketing site loses the sale. E-Seats is designed around protecting that impulse.
Browsing works like a poster wall.
The landing is rows: this week, trending, then a band per category — concerts, sport, theatre, business, even a rail-travel search. Deeper in, category pages filter by date and venue with chips, not forms. Every card is the same shape: photo, date badge, name, venue.


The insight
The whole purchase happens on top of the event page. You never leave the thing you’re excited about.
Four steps, all layered over the event page.
The event page has one button, and the price is already on it. From there every step — tickets, details, payment, confirmation — opens as a sheet over the same page, dimmed but visible behind. Close any sheet and you’re exactly where you were, excitement intact.
You can buy without an account.
The gate offers three doors, and the third one is “continue without signing in” — because a first-time buyer with tickets in hand is not the moment for a registration form. Checkout collects name, email and phone anyway, so the tickets always have somewhere to go. For those who do sign in: a phone number and a code, with Google and Facebook as the fallback.
SolvesForced signup, abandoned cart


Pick, confirm, and see the fees before you pay.
Ticket types are rows with steppers — price per type, the 10-ticket limit stated right in the sheet. The next sheet restates the full order — sector, row, amount — above the contact fields, and the payment sheet itemises the total: tickets, transaction fee, service fee, then the button. No fee appears for the first time on a receipt.
SolvesSurprise costs at the end



The ticket is a QR code — and it’s hard to lose.
The confirmation is the one loud screen in the flow: a green sheet holding each ticket with its own QR code, above every fact of the order — date, venue, holder, phone. The same tickets live under My Tickets, split into active and history, for the moment at the door.
Solves“Where’s my ticket?”


Designed once, rendered six ways.
The whole product exists in dark and light, on desktop, tablet and phone — six full renders of the same design, 165 screens in all. That’s only sustainable because every colour in the interface is a named token carrying a dark value and a light value: swap the values and the theme follows, no redesign.
Tokens do the theming.
The variables table is the contract: background, cards, text, brand — each a token with its two values. The light theme is the proof that it works: the same landing, the same components, nothing redrawn.


The phone gets a layout, not a shrink

Re-laid-out, not shrunk.

The same four steps, full-screen.
What it did.
165
Screens designed
Counted across the six renders
6
Full renders
Dark + light × desktop, tablet, phone
4
Steps to a ticket
All sheets over the event page
0
Forced signups
Guest checkout is a first-class door
The best checkout is the one that never takes you away from the thing you’re buying.
Next case study
Sweet Fung Records
A Tbilisi vinyl record shop — diagnosed back to health, then rebuilt to its redesign as a reversible plugin layer.