Case study
Next Gig
Designing and building a mobile-first coordination platform for working UK musicians — replacing group-chat chaos with transaction clarity.


Solo — product design, engineering, PM
2025 – present
Personal product / SaaS
React · TypeScript · Firebase
01Overview
Next Gig (originally Gig Hub) is a mobile-first progressive web app designed to solve the logistical and administrative challenges faced by independent gigging musicians in the UK.
Working musicians operate in a demanding environment: they must perform, coordinate ensembles, manage emergency bookings, and track complex freelance earnings. In practice, this coordination is fragmented across SMS, WhatsApp group-chats, and emails, leading to miscommunication, double bookings, and tax-season stress.
I designed and built Next Gig from scratch as a single, calm source of truth. The application acts as a transaction diary where bookings have explicit states, payment details are documented, and roster communications are automated.
02The Problem
Group-chat noise and administrative overhead
Freelance live music operates on a network of backup players known as deps (substitutes). When a core band member cannot make a date, the band leader (MD) has to find a replacement.
In a typical setup, the MD messages multiple players. This informal system creates three main problems:
- Dep Churn: Messages get lost in busy WhatsApp chats. Band leaders end up chasing people individually, leading to phone tag and last-minute panic.
- Ambiguous Confirmations:Informal messages like “maybe” or “should be fine” are easily misread as confirmations. Gigs can go unfilled or get double-booked because there is no single record of who agreed to what.
- Scattered Finances: Musicians must track their earnings, travel mileage, and expenses for self-assessment tax returns. Since fees and details are scattered across messages and spreadsheets, completing tax returns is often a chaotic manual process.
03The Solution
A structured workspace for live music logistics
Next Gig structures the communication around gig bookings. By treating each booking as a transaction with a defined state, we replace noisy chats with clean actions:
- For Band Leaders: A dashboard to manage gigs, coordinate lineups, and send automated offers to dep rosters.
- For Deps: A clean mobile interface to review gig details (date, fee, venue, load-in time) and accept or decline with one tap.
- For Ensembles: A shared schedule that automatically alerts members to date conflicts.
- For the Individual: A private ledger that tracks fees and expenses, rolling them up into a UK tax-year summary.
04UX Audit & Iteration
Refining details through usability reviews
To refine the app, I conducted regular usability reviews against our primary user personas: Priya (the busy MD), Jamie (the dep on the go), and Cal (the committed band member).
These reviews highlighted three main friction points, which I addressed in the final design:
Dep Fee Input Placement
Originally, the Dep Fee input was placed at the bottom of the Share panel. Band leaders had to scroll past the roster picker and settings to reach this required field. Moving it immediately below Roster selection simplified the form on mobile.
Mobile Quick-Actions
Accept and Decline buttons were originally hidden on mobile screen widths. Deps had to tap into the gig detail screen to respond. Surfacing simple action icons directly on the list view reduced this to a single tap.
Proactive Conflict Checks
Conflict warnings were only shown after opening an offer details sheet. I added a conflict detection check across the main gig list, displaying warning badges on conflicting dates immediately.
Visual Evolution: Gig Detail & Lineup

Flat list format showing basic time, fee, and tag fields without coordination context.

High-contrast layout surfacing active status badges, team rosters, and real-time coverage notifications.
05Core Features
Built for the realities of freelance musicians
1. My Gigs Command Centre
A centralized dashboard compiling dates, fees, offers, and deps into a single view. Users can easily scan upcoming slots, respond to invitations, and track coverage without digging through disjointed messaging threads.

2. List & Share Gigs
Enables band leaders to input key gig parameters (date, venue, performance times, fee, and instrumentation) and share them with the band or a saved roster. This replaces scattered messaging threads with a single source of truth.

3. Automated Dep Offers
Band leaders can offer a gig to a prioritized roster. The system automatically offers it to the first player; if they decline or don't respond, the system promotes the offer to the next player, eliminating manual follow-ups.

4. Private Earnings Ledger
Tracks individual fees, travel mileage, and expenses, rolling them up into a UK tax-year summary with CSV export capabilities to simplify tax filing for freelance players.

06Design System
High-density mobile patterns
Next Gig is designed primarily for mobile-first usage. The visual design prioritizes readability and ease of use in low-light gig environments:
- FormSidePanel split-header pattern: A layout that places key action parameters (Date, Time, Fee) in a sticky header block above the scrollable details sheet, ensuring primary information remains visible.
- Semantic Coverage Badges: Standardized badges (Covered, Pending, and Offered) allow band leaders to check booking statuses at a glance.
- CSS Motion Staggers:Subtle staggers on list entries guide the user's eye and improve the perceived responsiveness of real-time data loads.
07Outcomes & Impact
A live research preview for freelance musicians
Next Gig is live at nextgigapp.com (opens in new tab) as an installable PWA research preview.
The project has achieved its primary goals:
- Pilot Validation: The app is actively used by a group of freelance musicians to coordinate bookings and track schedules.
- Performance and Accessibility: Built as a lightweight React application, Next Gig maintains high performance and meets web accessibility guidelines.
- Process Validation: Serving as a testbed for design patterns, real-time database syncing, and developer handoff processes.