·7 min read·By Piotr Waskiewicz
A festival app without the App Store — what we learned building Stagebly
Why progressive web apps now beat native for most events — and the specific trade-offs you accept in exchange for a 5-minute setup.
For a decade, if a 20,000-attendee festival wanted a mobile experience, it paid someone $50-100K to build a native app, submitted it to two app stores, fought rejections for a month, and asked attendees to install it every year.
That decade just ended.
What changed
iOS Safari now supports the full progressive web app (PWA) feature set: add-to-home-screen, push notifications, offline caching via Service Worker, Web Share API with file attachments, even background sync. Android has supported this for years. For an events audience — where the median session is under 10 minutes and the whole experience lives or dies on the weekend — the friction of a native install has become the single largest drop-off in the funnel.
We tested this with Sunrise Festival, one of Poland's largest electronic music festivals. Instead of asking attendees to install a dedicated app from the App Store, we shipped a PWA at mdt.stagebly.com. Three clicks from QR scan to Add to Home Screen, no store login, no review cycle.
What still matters
The things organizers actually care about still work:
- Push notifications. iOS Safari PWAs finally support them — you just have to ask for permission after the user adds the app to their home screen, which matches Apple's UX assumption that home-screen apps are trusted.
- Offline mode. The schedule, map and info pages survive a signal-dead field. Service Workers pre-cache on first visit; analytics writes queue and flush on reconnect.
- Sharing. Web Share API v2 now accepts binary files, which means we can generate a personalised "lineup card" PNG server-side via
@vercel/ogand hand the raw file to Instagram Stories, WhatsApp and X. The viral loop a festival wants — attendees posting their festival plan — becomes trivially easy.
What you give up
Two things. First: App Store discoverability. Nobody finds an event PWA by browsing a store. This isn't a loss — event apps are linked from tickets, QR codes and emails, not searched for — but it changes the install flywheel.
Second: background capabilities. If you need continuous GPS tracking for a heat-map view, or NFC for payments, you still want native. Most events don't.
What we learned
Two things surprised us. The first: attendees install a PWA at a 3-5x higher rate than a native app. The friction drop is real. The second: once installed, the usage pattern is indistinguishable from native — push CTR, session length, retention over a 3-day event all match the published benchmarks for native event apps.
If you're an event organizer deciding between a custom native app, a generic event platform (EventMobi, Whova) or something like Stagebly — ask your 2026 self this question: what fraction of my attendees actually installed last year's app? If it's below 30%, you paid for discoverability you didn't get.
We built Stagebly for organizers who want to answer that question differently in 2027.