# Event app first release: what to scope for the day itself
Source page: https://dfygames.com/guides/event-app-scope (published 2026-10-19, updated 2026-10-19) · Topic: Event and loyalty apps
Cite as: DFY Games, "Event app first release: what to scope for the day itself", updated 2026-10-19, https://dfygames.com/guides/event-app-scope

**Quick answer:** A first event app should cover what attendees need on the day: the schedule, a personal agenda, venue information, announcements and check-in against a ticket list you already have. Ticketing, live streaming and attendee networking are each large enough to be separate projects, so the first release links to existing tools for them.

- Pricing: Written scope and quote
- First release: Schedule, agenda, check-in, news
- Keep outside: Ticket sales, streaming, chat
- Best fit: Recurring events and venues

## Build for the day of the event

Attendees open an event app for a handful of reasons: what is on now, where is it, what did I save, and how do I get in. A first release that answers those well beats one that tries to replace the ticketing site, the stream and the conference chat at once.

| Screen | What it does | Data it needs |
| --- | --- | --- |
| Schedule | Sessions by day, track and room | Session list managed in the admin |
| Session detail | Time, room, speakers, save to agenda | Session and speaker records |
| My agenda | Saved sessions with reminders | Stored on the device or in the account |
| Speakers | Profiles linked to their sessions | Speaker records and photos |
| Venue | Map image, rooms, facilities, travel notes | Static content and an image |
| Announcements | Organizer updates and room changes | Admin posts, optional push |
| My ticket | QR code for entry | Attendee list imported from your ticketing tool |
| Staff check-in | Scan tickets at the door, see counts | Staff accounts and the attendee list |

This guide is about what to put in the first release. How we build and quote it, and how it fits with returning-visitor features if you also run a venue, is on the [event app development](https://dfygames.com/apps/event-loyalty) page.

## Separate check-in from ticketing, streaming and networking

These four features sound similar on a wishlist. In a build they are very different, and three of them already exist as mature products you can link to.

| Feature | First release | Why | If you need it in the app |
| --- | --- | --- | --- |
| Check-in | Include | Scanning a QR against an imported list is a contained job and saves door staff time | Add offline scanning if venue signal is poor |
| Ticketing | Link out | Ticket sales involve payments, refunds, tax and fraud handling that ticketing platforms already do | Scope it as a separate payments project with its own quote |
| Live streaming | Link out or embed a player | Streaming infrastructure is specialist and priced by usage | Embed a stream from a provider; avoid building delivery yourself |
| Attendee networking | Leave out | Profiles, messaging, matchmaking and moderation make a social product on their own | Start with a simple opt-in attendee list, then measure demand |

> Import, do not resell: Keep selling tickets where you sell them now and import the attendee list into the app before the event, or sync it through the ticketing tool's API if it offers one. Check-in then works without the app ever handling payment.

## One event or many: does an app make sense?

A store app has fixed costs: the developer accounts, store review, and the effort of asking people to install something. For a single event, a mobile web page or an event platform's attendee app is usually the better spend. A custom app starts to pay for itself when the same organizer runs events repeatedly, owns a venue, or wants attendees to keep the app between events.

| Situation | Sensible option |
| --- | --- |
| One conference, one time | Mobile web schedule or an event platform's app |
| Annual festival with a loyal crowd | Custom app reused each year with new content |
| Venue with a programme of events | Custom app with schedule, check-in and a rewards card |
| Series of workshops or meetups | Custom app or a membership tool, depending on how members pay |

If the events are part of a paid membership, the [membership build or buy guide](https://dfygames.com/guides/membership-build-vs-buy) is the better starting point.

## Plan for venue signal and the rush at the doors

Event apps are used in the worst network conditions a phone sees: a full hall, a basement, a field. Two scope decisions follow. First, cache the schedule, venue map and the attendee's ticket on the device so they open without signal. Second, decide whether staff scanners need to work offline and sync later; that adds conflict handling (the same ticket scanned at two doors) and is worth paying for only if the venue is known to be bad.

Load matters too. Check-in traffic arrives in a burst at opening time. The backend does not have to be large, but it has to be tested against that peak before the day, which belongs in QA.

## Who updates the schedule

Schedules change until the last minute. The admin panel needs to let a non-technical organizer add or move a session, change a room and post an announcement, and those changes should reach the app without a store update. Decide who does this work and give them the right role. A CSV import for the first load of sessions and speakers saves a lot of typing.

Admin tasks for a first event app:
- [ ] Create, edit and cancel sessions, rooms and speakers
- [ ] Import sessions and speakers from a spreadsheet
- [ ] Import or sync the attendee list from the ticketing tool
- [ ] Post announcements, with or without a push notification
- [ ] See check-in counts by door and by time
- [ ] Copy last year's event as a starting point for the next one

## What changes the quote

The quote grows with the number of event formats you support, offline needs, integrations with ticketing or CRM tools, and whether attendees need accounts or can use the app anonymously with a ticket code. Payments inside the app, streaming and networking each add a separate block of scope. For a structure to send, use the [app brief template](https://dfygames.com/guides/app-brief-template), then request a [written scope and quote](https://dfygames.com/apps/quote).

## FAQ

**Should an event app sell tickets?**
Usually not in the first release. Keep ticket sales on your ticketing platform and import the attendee list so the app can handle check-in.

**Can the app work without signal at the venue?**
Yes, if offline use is in scope. Schedules, maps and tickets can be cached on the phone, and staff scanning can sync later at extra cost.

**Is a custom app worth it for a single event?**
Rarely. A mobile web page or an event platform's app is usually cheaper for a one-off; a custom app suits recurring events and venues.

**Can attendees message each other in the app?**
It can be built, but messaging, matchmaking and moderation are a large scope of their own, so we recommend leaving them out of the first release.

**How do schedule changes reach attendees?**
The organizer edits the session in the admin panel, the app picks up the change from the server, and an optional push notification tells attendees.

## Related
- Service page: [Event and loyalty apps](https://dfygames.com/apps/event-loyalty)
- [Loyalty app scope and cost: one reward loop and its tradeoffs](https://dfygames.com/guides/loyalty-app-scope)
- [Custom loyalty app vs loyalty platform: build or buy?](https://dfygames.com/guides/loyalty-build-vs-buy)

---
DFY Games (Done For You Games), https://dfygames.com. More guides: https://dfygames.com/guides · Index for AI assistants: https://dfygames.com/llms.txt