Te In Roh
All work

Cover

An event discovery and ticketing app for Bolivia, built so a ticket bought on the bus still scans at the door.

Type
Event ticketing, mobile
Role
Product Designer
Timeline
6 weeks, concept to prototype
Tools
Figma, Figma Prototyping
Splash. The stepped mark and band introduce the cholet palette before any data.

colors from El Alto

Home. City first, then genre, then the featured flyer and the week's list.

city first, then genre

Event detail. Metadata rows, tiers with what's left, and a sticky price bar into checkout.

tiers show what's left

Checkout. A quantity stepper, the local QR Simple payment, and a plain total.

total never scrolls away

Ticket. A high-contrast QR card saved to the phone for venues with no signal.

works with no signal

Profile. Purchase history and settings reuse the rows from checkout.

Overview

Cover is a mobile event discovery and ticketing app for Bolivia. Nightlife and festival listings there sit scattered across Instagram stories, WhatsApp broadcasts, and word of mouth. I designed Cover to give event-goers in La Paz, Santa Cruz, and Cochabamba one place to find what's happening and buy in, with a ticket that scans at the door even without a signal.

Problem

Event discovery in Bolivia's mid-size cities runs on informal channels: a flyer reposted to a story, a link forwarded in a group chat. No source tracks what's happening, where, or what it costs. By the time a listing reaches a buyer, the venue may have changed or the cheap tier may already be gone. Paying means a bank transfer and a screenshot standing in for a ticket. No product treated a ticket purchase like a real transaction with a real receipt.

Process

  1. 01I mapped the purchase journey to four screens a user finishes in one phone session: discover, event detail, checkout, ticket. A desktop wizard can spread across ten steps; a phone screen doesn't get that room.
  2. 02I took the color system from El Alto's cholets, the party halls covered in stepped geometry and saturated paint. Magenta, turquoise, and orange each mark one kind of event, and yellow is kept for the single action on each screen. Bolivian event-goers already read that palette as a night out.
  3. 03I let the organizer's flyer be the event's image. Flyers are what organizers already make for Instagram, so Cover shows them as they are and puts every fact the app needs in plain text underneath.
  4. 04I standardized one metadata row, an icon chip plus a label, for date and venue on the event detail. Checkout and the ticket repeat the same date, time, and venue line in the same order, so the eye learns it once.
  5. 05Each ticket tier shows how many are left. The cheap tier running out becomes something you see before checkout, not something you find out after a bank transfer.
  6. 06I anchored every purchase screen with a sticky bottom bar: price and Comprar on event detail, total and Pagar on checkout. A buyer never scrolls up to check what they're about to pay.
  7. 07The ticket is a white QR card on the dark app, sized for a door scanner, and saved to the phone so it opens with no signal at the venue.

The event card, twice

v1: title fights the flyer's own type

v2: facts get their own block

Design system

Screens sit on a near-black violet ground so the organizers' flyers stay the brightest thing on screen. Three category colors, magenta for fiestas, turquoise for conciertos, orange for festivales, appear as small dots and tags, never as backgrounds. Yellow is reserved for the one action per screen. Titles and the wordmark are set in Unbounded, a wide geometric face that echoes the cholet facades; everything else is Archivo. Corners are 10 to 16 pixel rounded rectangles with hairline borders and no shadows, and the stepped band from the logo shows up only on the splash and the ticket.

  • Ground#120e17
  • Surface#1d1724
  • Fiesta#ff2e88
  • Concierto#00c2b2
  • Festival#ff6b1a
  • Action#ffc21a

Outcome

I delivered six screens ready for engineering: splash, home, event detail, checkout, ticket, and profile, tied together by one four-tab navigation (Inicio, Buscar, Entradas, Perfil) and a documented component set for flyer cards, metadata rows, tier rows, and sticky bars. Before build, I'd test the quantity stepper and the offline ticket with five to eight people in Santa Cruz, to see whether they trust the flow before real payments are wired up.

Reflection

I went back and forth on the event cards more than anything else in this file. Five facts, title, date, venue, price, and category, have to fit one compact card without turning it into a spreadsheet row. My first pass set the title over the flyer with a dark scrim. It looked fine on my own mock flyers, then fell apart on the kind organizers actually post, which already carry their own type everywhere: two titles fighting, the price lost in a crowd of DJ names. I moved the text into its own block under the flyer. The card got taller, and I still catch myself wanting that height back when I scroll eight events in a row. I don't have a clean answer yet. It's the first thing I'd put in front of real users before touching the visuals again.