A Festival App Platform for a Live Entertainment Portfolio

One codebase, many festivals: the guide in every fan's pocket and the group's clearest view of its audience.

Festival events feeding one app platform that returns business insights Four festival event cards on the left feed a large phone in the center whose screen shows a lineup list and a map pin, labelled app platform, which feeds an insights dashboard on the right with a five-bar chart and a sparkline, a green check at its corner and a pulsing ring around the tallest bar. EVENT EVENT EVENT EVENT APP PLATFORM INSIGHTS

A Portfolio, Not a Festival

In the middle of the last decade the largest electronic music promoters in North America were being gathered into one company. SFX Entertainment bought them one by one, took the group public in 2013, went through bankruptcy in 2016 and emerged as LiveStyle. Among the brands in that portfolio was Disco Donnie Presents, a client of ours since 2015. What the parent company needed from its brands was not just good festivals but a way to see across them: who attended, what they cared about, and what the portfolio could learn from one event that would help the next.

A festival attendee's phone is where that information lives. It is also the one place a promoter can reach a fan during the event itself, when a stage change or a weather delay has to travel to twenty thousand people in a minute. So the mobile app for a festival became two things at once: the best guide a fan could have in their pocket, and the portfolio's most direct source of intelligence about its audience.

One App Platform for Every Event

Between 2015 and 2017 we designed and built a mobile application platform for the group's festivals, and then the process for stamping out a new app for each event from it. A fan downloading the app for a Texas festival and a fan at a Florida one were using the same platform with different skins, schedules and content, and the promoter was running one codebase rather than a dozen.

The Pieces

Hybrid apps for iOS and Android

Built with Ionic so a single codebase shipped to both stores, and kept working on the older Android phones a festival crowd actually carries.

A Node.js API behind everything

An API service shared by the websites and the apps: lineups, schedules by stage, venues, promoter listings, a worldwide event list and search, and user accounts, so content was entered once and appeared everywhere.

Push notifications that reach everyone

The notification service was rebuilt from PhoneGap push to OneSignal and rolled out across the group's apps, giving promoters a reliable way to reach a whole crowd at once.

A repeatable process for new apps

Launching an app for a new festival became a documented, streamlined process that reused the core, so the portfolio could add events without adding engineering projects.

Built for the on-sale spike

We analyzed request logs from peak moments and built a utility to replay them against the API in development, so capacity was tested against real traffic patterns rather than guesses.

Intelligence back to the group

Ticketing sales data was collected automatically from the ticketing platform into the group's marketing cloud, with daily summaries, giving the portfolio a view across brands that no single festival had.

Why It Mattered to the Group

A portfolio company's advantage is supposed to be scale: shared infrastructure, shared audience data, shared lessons. Festivals resist that, because each one is a world of its own with its own fans and its own team. The app platform was one of the few places where the scale advantage was real. Every event got a better app than it could have afforded alone, the group got a consistent picture of its audience, and a fix or a feature reached the whole portfolio at once.

The portfolio did not stay together. LiveStyle sold Disco Donnie Presents back to its founder in 2020, and other brands went their own ways. The platform thinking survived the corporate structure: the promoters we still work with launch their sites and apps the same way today, from shared foundations rather than fresh starts. That continuing story is on the Disco Presents page.

When a Shared Platform Fits, and When It Does Not

If you run one event, or two, a shared platform is overhead. Build the best single app or site you can and keep it simple. The calculation changes at around the fifth brand, when every launch is repeating work the last one did and every improvement has to be made several times.

The honest prerequisite is organizational, not technical. A shared platform only works if the group is willing to let its brands share, which means agreeing on what is common and what each event may change. Groups that cannot make that agreement should not build a platform; they should accept the cost of separate builds and stop paying for coordination they will not use. Groups that can make it get the one advantage a portfolio is supposed to have.

Go Deeper

Array

The rest of the live entertainment work.

The Disco Presents Story

Eleven years behind the sites, apps and data of a festival promoter.

Live Entertainment and Ticketing Platforms

A UDX Talks session on the technology behind live events.

Elevating the Live Entertainment Experience

How we deliver digital solutions for the industry.

The TravelBank Squad

An embedded JavaScript team integrating a hotel supplier end to end.

Our Work

Every project record, searchable by technology and client.

Guidance

Practical writing from our engineering practice.

Running Several Brands on Separate Builds?

Tell us how many properties you launch and how each one is built today. We will tell you whether a shared platform would pay for itself, and what you would have to agree on first.