Event App Development: Ticketing, QR Entry, Scheduling & Networking
Organizers of large festivals face a dilemma: before the event, maximize ticket sales; during the event, provide navigation, networking, and live updates for thousands of participants. We create event apps that work in both modes without compromise. Our experience includes projects for conferences, music festivals, and sports events—each with its own specificity.
An event app lives in two modes: before the event (poster, ticket purchase, anticipation) and during (schedule, navigation, networking). Technically, these are different sets of requirements, and a common mistake is treating them the same. Before the event, purchase conversion is critical. During the event, it's about offline-first performance, speed, and real-time schedule updates.
Tickets
The event screen: description, speakers, program, remaining seats, "Buy" button. Ticket type selection (General, VIP, Online) → cart → checkout. For limited-capacity events, we implement a real-time counter via WebSocket or polling. If seats run out a second before purchase, we return 409 Conflict with a clear message.
Season passes or multi-day festivals require a single order covering multiple dates. Group purchase: the user buys 4 tickets, enters each participant's email—each receives their own QR.
The payment flow is critical. We integrate Apple Pay and Google Pay to minimize friction. Saved cards for repeat purchases. Using Stripe, Checkout.com, or a regional acquirer, conversion increases by 15–20%.
Why Real-Time Schedule Synchronization Matters
At a festival, the schedule changes every 10 minutes: a speaker falls ill, a session is moved. If the app shows outdated data, participants lose trust. WebSocket updates and push notifications solve this problem. On the client, we treat scheduleSessions as an Observable/Stream—when data changes, the UI redraws without a full reload.
QR Entry at Check-In
QR codes for tickets: JWTs containing ticketId, eventId, userId, exp (expiration), signed with a server key. On scanning at entry: signature verification → exp check → mark ticket as used (redemption flag in DB).
Protection against screenshot sharing: animated QR codes that refresh every 30 seconds with a new iat—a standard for large festivals. Offline: we accept the last loaded code with offline verification using a cache of used tickets on the volunteer's device.
The volunteer scanner app is either a separate build target or a separate app. Scanning uses AVFoundation / ML Kit. Sound and vibration feedback for successful/erroneous scans—crucial in a noisy crowd.
Schedule and Program
Multi-room schedule: horizontal time axis, vertical rooms/stages. We implement it with UICollectionViewCompositionalLayout or a custom Canvas. Overlapping sessions are displayed in parallel.
Personalized schedule: the user marks "Want to attend"—sessions are added to a personal program. Conflicts ("at 15:00 you have two events simultaneously") trigger a warning.
Real-time changes: a speaker falls ill, a session is moved. WebSocket schedule updates, push notifications to subscribed users. On the client: scheduleSessions as an Observable/Stream—on update, the UI redraws without reload.
Offline: schedule is cached on first load. At a festival, up to a third of attendees have no internet—the app must work. We use Core Data / Room / Isar with background sync when connectivity resumes.
How We Ensure Offline Operation at a Festival
Offline mode is a basic need for event apps. We cache the schedule, venue map, and QR tickets on the device. Synchronization happens in the background: when network appears, data updates, and conflict resolution uses last-write-wins. For networking, we use Bluetooth proximity, which requires no internet.
Networking
Participant profile: name, company, role, photo, links. Visibility is configurable (everyone / by request / hidden).
"Find people nearby" using Bluetooth proximity via CoreBluetooth (iOS) / Nearby Connections API (Android). Proximity radius ~10 meters. When another participant with networking enabled is detected, a banner pops up: "Nearby: Ivan Petrov, CTO at Acme Corp."
Business card exchange via NFC (NFCNDEFReaderSession iOS / NfcAdapter Android)—participants tap phones to exchange profiles. QR business card as a fallback.
Chat: private messages between participants, group channels by topic. We use Stream Chat or SendBird—ready SDKs with push notifications.
Participant Interactivity
Live Q&A: participants ask questions via the app, upvote others' questions. On the organizer screen, a real-time list sorted by rating. WebSocket synchronizes votes.
Polls: the speaker launches a poll → participants answer → results shown in real-time on a slide. We use ready solutions (Mentimeter API) or custom implementation via WebSocket.
A Case Study: Large Music Festival
On a recent project for a major music festival with 50,000 attendees, we replaced a static PDF schedule with a real-time WebSocket-driven app. The previous system required organizers to manually update PDFs and push notifications; announcement delays reached up to 10 minutes. Our solution integrated the scheduling backend directly with the app via WebSockets, allowing updates to propagate in under 2 seconds. The personalized schedule feature was used by 78% of attendees, and the offline mode ensured reliable access even in areas with poor network coverage. Check-in time dropped from 30 seconds per person to 5 seconds thanks to animated QR codes and offline verification.
Tech Stack and Platform Comparison
React Native is a popular choice for event apps: cross-platform, fast start, sufficient performance for schedules and chats. We use Zustand or Redux Toolkit for schedule state. react-native-vision-camera for QR scanning.
Flutter is similar but offers higher animation performance. Native Swift + Kotlin is preferred when Bluetooth proximity, NFC business card exchange, and maximum schedule performance are needed.
| Platform | Performance | Development Time | Community |
|---|---|---|---|
| React Native | High | Fast | Large |
| Flutter | High | Medium | Growing |
| Native (Swift/Kotlin) | Maximum | Long | Mature |
What's Included in Event App Development
| Component | Description |
|---|---|
| Analytics & UX | Interviews with organizers, prototyping |
| Frontend | iOS (Swift) + Android (Kotlin) or cross-platform |
| Backend | Node.js / Go, PostgreSQL, Redis |
| Payments | Apple Pay, Google Pay, Stripe / Checkout.com |
| QR System | JWT, animated QR, offline verification |
| Publishing | App Store, Google Play, TestFlight |
| Testing | Pilot event, load testing |
| Documentation | API docs, volunteer guide |
Our Process
Poster and checkout design → QR system and volunteer app → schedule with offline support → networking → interactivity → testing at a real event (pilot run) → publishing.
Timeline Estimates
MVP (poster, ticket purchase, QR entry, schedule): 4–7 weeks. Full-featured event app with networking, live Q&A, Bluetooth proximity, and multi-platform scanner: 2–4 months. Project cost is determined after requirements analysis.
We have been in the market for over 5 years and have delivered 15+ event apps for conferences, festivals, and sports events. Order your event app development today—we'll propose the optimal solution. Contact us for a preliminary assessment of your project.