# Live Time

> Live Time believes hosting should feel easy. An iOS event flow, one question at a time.

A case study by [Royden So](https://roydenso.com), product and brand designer. Page: https://roydenso.com/live-time

- Role: Product design, coded prototype
- Surface: iOS
- Industry: Events
- Timeline: July 2026, about three weeks

Live Time is an events app used at more than 100 universities, where brands like Red Bull and Gopuff send perks to the parties people host. I redesigned how a host makes an event, and delivered it as a coded iPhone prototype that engineering built from.

The old flow was a long form with one format for every kind of event. I rebuilt it the way Airbnb paces its host onboarding: pick what you're planning, then answer one question per screen, on a sheet over the page your guests will see.

## Impact

- 6 sections for all 43 kinds of event, one question per screen
- 4 of 18 sample events left in an awkward category, against 6 to 8 for the other lists
- ~3 weeks from kickoff to a handoff engineering was already building from

![Live Time: a host picks a category, answers the guided sheet one question at a time, and the invitation writes itself](https://roydenso.com/assets/design/live-time/loop-create.webp)

## Guided creation

One long form became six sections, the same for all 43 kinds of event.

### Problem

Creating an event was a long form built around one format. Hosts named the event before they knew what it was, and nothing showed them what a guest would get.

The category list mixed four kinds of thing, so an event fitted two at once, and the number of sections ran from five to eight depending on the pick. Every "n of N" went stale.

### Decision

Category comes first: six by purpose, each with its own second question, 43 kinds of event in all. The disc you press flies to the middle and turns over to show your pick.

The same six sections for everyone: When, People, Where, Cost, Extras, Finish. Category changes what the questions say ("When's the DJ set?") and what they assume, never how many there are.

The questions live on one tall sheet over the event page, which fills in as the host answers. Drag the sheet down and you are looking at what a guest gets, so there is no preview screen.

Headcount is a dial of six spoken ranges, from 1 to 10 up to 250 and over, and it can't be skipped: the venue list, the table booking and a brand's perk all need it.

Finish drafts the invitation from everything answered: three to swipe between, each the invitation itself. Publishing needs only a title.

### Results

The progress bars never change length. Scored on 18 sample events, the six categories left 4 in an awkward home, against 6 to 8 for the other lists we tried.

One event page serves three modes, being built, previewed and live, so the old review screens were deleted.

### Tradeoffs

Category no longer sets the length of the flow. Giving a category its own length back is a one-line change.

A required headcount reversed the team's call to make it skippable. We agreed to settle its place with an A/B test.

![Eight screens from the guided flow drifting toward the camera four at a time: the date, free products, the headcount dial, a brand, the category pick, a ticket, the headcount orbit and a finished event page](https://roydenso.com/assets/design/live-time/loop-guided-space-v3.webp)
![A woman in sunglasses laughing, holding up an iPhone with her event live: Pregame at the Loft, its photo cover and the host's Manage panel](https://roydenso.com/assets/design/live-time/dial-close-v5.webp)
![A woman on a picnic blanket in a pink Live Time cap, a glass of orange wine in her hand](https://roydenso.com/assets/design/live-time/drafts-close-v3.webp)

## Brand partnerships

Perks climb with the guest list, to keep hosts inviting after the first box.

### Problem

Brand perks are what set Live Time apart, but the old perk was bolted on after creation and had a single floor. Once enough guests signed up, the meter went green and stopped meaning anything.

That is exactly when a host stops inviting, right when ten more people would have earned a second box.

### Decision

The floor earns the first box, and every set number of RSVPs after it earns another, up to the brand's stock. Doughlicious starts at 15 RSVPs and adds a box every 10, up to 5. The brand names its own unit: a box, a case, a kit.

The ladder shows in three places: on the brand's row, on the brand's page, and above the guest list with Share inside it, because the link is the only way to the next rung.

Asking a brand is one step in Extras, "Who's helping you host?", where brand cards carry a real photograph and their floor. A requested brand sits among the hosts in a dashed ring until it accepts.

The request fills in what the app already knows, such as the address, the date and the headcount, and marks those values as filled in for you.

### Results

The ladder's arithmetic lives in one function that the screens and their copy both read from, so a brand's numbers can't disagree across the app.

### Tradeoffs

The ladder stops at the brand's stock. At the founder's request a big "FREE" label became a $0 total, which reads as an agreement rather than a giveaway.

![Eight finished events gliding past one at a time, each a white page in its own colour: Pregame at the Loft in blue, Glow Night in magenta, Rooftop Golden Hour in teal, Arcade Night in violet and more, each with its host, date, place, who's going and a button for its price](https://roydenso.com/assets/design/live-time/loop-ladder-v4.webp)
![Two hands holding an iPhone over a green blanket on the grass: Pregame at the Loft as guests see it, hosted by Ella Moreno, with RSVP and chip in $10](https://roydenso.com/assets/design/live-time/roster-leather-v5.webp)
![The headcount orbit turning around Ella, the host: the guest count, a matched brand, Gopuff, shopping and capacity, every logo upright](https://roydenso.com/assets/design/live-time/loop-orbit-v2.webp)
![A 3D map of the blocks by the Manhattan Bridge in deep burgundy, one block on Forsyth St standing up in hot pink under a map pin: The Loft, Chinatown](https://roydenso.com/assets/design/live-time/venue-map-v1.webp)

## The live event

Publishing lands the host on their live event page, with Share and Manage on top.

### Problem

The old flow ended on "Create another event", so the reward for finishing was watching the event disappear.

### Decision

Publishing holds one moment, the invitation and a tick, then hands over to the event page as guests see it, with the host's Share and Manage on top.

Invites start from the person, and the channel follows: "We'll text 2, email 1." The CSV import reads the file and reports what it found before it adds anyone.

The guest list is one screen with segments, and a segment exists only if someone is in it. Approve slides right, decline slides left.

At the door the ticket is a QR code. Scarcity is a count, "9 left", never a countdown, and a guest who is turned away gets a next step.

### Results

The event page is the same screen in every mode, so there is no separate admin view for a host to learn.

![Eight screens of the live event fanning out into a row, then the camera sweeping back along it: You're live, the event page, invites, the guest list, text blasts, the playlist, ticket scanning and settings](https://roydenso.com/assets/design/live-time/loop-live-v4.webp)
![A host picks a category, answers the guided sheet one question at a time, and the invitation writes itself](https://roydenso.com/assets/design/live-time/loop-create-v2.webp)
![A wine bottle with a Live Time label in a net bag on a picnic blanket, beside burrata and a halved orange](https://roydenso.com/assets/design/live-time/ticket-lap-v3.webp)

## Scope

- The create-event redesign, from the category picker to the live event.
- The brand partnership flow and the perk ladder.
- Invites, the CSV import, the guest list and the host's console.
- The coded prototype, the Screens board and the UI kit behind them.
- The decision log and the handoff to engineering.

## Contributions

- Working sessions with the founder on the platform and the brand partnerships expansion.
- Screen-by-screen reviews with engineering, who started building once the layout was locked.

## Brief to handoff

1. Kickoff: A call with the founder about the platform and the brands, then a trial weekend on the create flow.
2. Reference: Airbnb's host flow, Luma and Partiful, studied for the order of the questions and the copy.
3. Prototype: I built the flow in code inside a real iPhone frame, 62 screens by the handoff.
4. Review: Four reviews with the team. Each note became a numbered decision, 98 in all.
5. Handoff: I exported the source, the Screens board and the decision log for engineering.

## Lessons

- Airbnb's host flow is easy because of its order. I studied what it asks first and how it words each question, then paced our one-question screens the same way.
- Score the options before choosing one. I tried the category lists on 18 sample events, and the one we chose left only 4 in an awkward spot.
- On a short contract, write the decisions down. I logged 98 across four reviews, so the team still has the reasons after the handoff.

## Looking back

I liked taking a long form and making it one simple question at a time for someone who just wants to throw a party. I worked it out in sessions with the founder and showed the team along the way, and I was glad to do it with them.
