Skip to content

Case study · Live music and festivals

Concert Music Festival.

A Spanish summer music festival wanted its official app to follow the website live and update without waiting for the stores. Polargate rebuilt the foundation in four days, ten days before the season started.

Home screen of the Concert Music Festival web app: the festival name and Sancti Petri, Chiclana de la Frontera, Cádiz over a dim stage, with a tab bar below.

At a glance

Client
Concert Music Festival
Sector
Live music and festivals
Year
2026
Stack
CapacitorReactViteTypeScriptTailwind CSSshadcn/uiTanStack QuerySupabasePostgreSQLDenoVercelWordPressGitHubGitHub ActionsiOSAndroidFirebaseResendVitestPlaywright
Concert Music Festival on a phone

01 · Concert Music Festival

The challenge.

The festival already had an official app in both stores. Its team works in WordPress and wanted the app to show every change to the line-up as soon as it was published, without editing code or waiting for Apple and Google to review a new release. It also wanted the backend under its own control and push notifications ready for the season, and the first show was ten days away.

For example: 22 public routes prerendered as static HTML. Hotel Marien

02 · Concert Music Festival

What we built.

Polargate rebuilt the foundation in four days. We moved the whole backend to a Supabase project we control: 31 migrations, 26 tables with row level security, 12 edge functions, 62 user accounts with their IDs intact, 265 gallery items and 603 storage files. We rewrote the content layer so the line-up is read live, and wrote a WordPress plugin plus an edge function that syncs every 30 minutes and copies images and PDFs into our own storage. Releases moved to the cloud: Xcode Cloud on iOS, GitHub Actions on Android, over the air updates for the rest.

A phone held up in the crowd at a night concert by the sea, showing the Concert Music Festival app with Sancti Petri, the confirmed artists and the tab bar, with the lit stage behind.
Recreated scene with the project's real screen

For example: 11 modules delivered in Phase 1. Elite Smart Build

03 · Concert Music Festival

The result.

The 2026 season ran on the new stack. 37 shows between 10 July and 17 August stayed in step with the official website without anyone touching code. The Android app is live in 177 countries, and the iOS app was relaunched and now takes most changes over the air, with no store review. On iOS we completed push at the native layer, and 149 devices signed up for notifications. End of edition mode was designed, built and deployed in a single day.

days from diagnosis to the new backend running
4
user accounts migrated with their IDs preserved
62
shows synced from the website in the 2026 season
37
sync interval between WordPress and the app
30 min
countries where the Android app is available
177
unit tests running on every change
106

For example: 2 languages live on the site, Spanish and English. Global Dynamic Security Group

04 · Concert Music Festival

How we did it.

For example: 100 / 100 / 100 Lighthouse mobile: accessibility, best practices, SEO. KD.tech

The context

A summer music festival on the coast of Cádiz, with a season running from July to mid August, had an official app for iOS and Android built on a no-code platform. The team works in WordPress, where the line-up lives inside an events plugin, and wanted the app to follow every change on its own.

What the festival asked for

We started on 30 June 2026, ten days before the first show, with four goals:

  • The line-up read live from WordPress, so a new artist appears without a new release or a store review.
  • The backend in a Supabase project we manage, with every user and file carried over.
  • Push notifications working on iOS and Android for the whole season.
  • Automated releases on both stores, plus updates over the air.

How it runs now

The festival team publishes in WordPress and the app follows within half an hour, on both stores and on the web. React, Vite, TypeScript, Tailwind and shadcn/ui on the front, Capacitor 8 for the native shells, Supabase for data, auth, storage and functions, Vercel for the web. 106 unit tests and one end to end smoke test run on every change, and Sentry and Crashlytics watch the app in production. Polargate keeps the app on a monthly maintenance retainer: content questions, store releases on both platforms, incident response, and the seasonal work of closing one edition and opening the next.

FAQ

Questions about this project.

How long does it take to move an app off a no-code platform?
For this festival app it took four days, from diagnosis to a backend under our control, plus one final submission on each store. Schema, edge functions, users, roles, media and secrets moved without data loss, and users kept their IDs so nobody had to register again. The time depends on how much sits inside the vendor's account, which is exactly what Polargate measures in a paid Discovery Sprint.
Can you connect the app to our WordPress or to our ticketing system?
Yes. Here the festival team keeps working in WordPress, and a plugin we wrote exposes the current edition through one endpoint, because the standard WordPress API does not return event dates and times. An edge function pulls it every 30 minutes and copies images and PDFs into our own storage, so the app runs on its own, independent of WordPress. Ticketing platforms depend on the API access the vendor grants.
Can we update the app without an Apple review every time?
Most of the time, yes. Anything living in the web layer, texts, screens, layouts and content rules, ships over the air through Polargate's OTA Hub, with channels, a rollout percentage and a minimum native version gate. Native changes, new permissions or new plugins still need a store release, which is automated from a git tag. On this app over the air is active on iOS, and Android updates go through the store.
Do you take over an app that another agency or a no-code tool built?
Yes, that is how this project started. Polargate begins with a paid Discovery Sprint: we read the code, the backend and the store accounts, and report what is solid, what to improve and in what order. You keep that report whether or not you continue with us. From there the backend runs on infrastructure that can be handed over intact.
What does it cost to keep a festival app running after launch?
This app runs on a monthly maintenance retainer, covering content questions, releases on both stores, incident response and the seasonal work of closing one edition and opening the next. Build work is quoted separately at a fixed price, as the download system was, with its smart link, native banner and print QR codes. Polargate prices a retainer by the surface it maintains, not by ticket volume.

For example: 536/536 translation keys present in each of the three languages. Estepona Golf

Next project

Hotel Marien.

Hospitality: 4-star all-inclusive resort hotel, Caribbean

Search engines and AI assistants can now read the resort's website

For example: 105,212 characters of body text readable by AI crawlers across 65 URLs, up from zero. Malacca Tables

Get started

Tell us what you want to build.

Websites, apps, custom systems and AI for companies that need them in production in weeks. Fill in the form or book a 30 minute call: a senior engineer answers within 48 business hours with a first take on scope, timeline and price.

What do you need?
Budget
When

At least ten characters.

Answer in writing within 48 business hours. No newsletter, no automatic sequence.

Rather answer the full brief?

First step

Discovery Sprint

Two weeks to close scope, architecture and price before anything is built.

No price list. You get a private quote, in writing, after a short call.

Then, to build, always at a fixed price

Not ready yet?

AI-native digital studio for mid-market companies

POLARGATE, S.L. · CIF B24895005
Calle Electrónica 6, 28027 Madrid, Spain