A mobile app for conference days, built around the agenda.
A mobile app for conference attendees has one job on the day: get each person to the right room at the right time, tell them the moment that changes, and make the people in the building easier to find than the people online. It is not a video conference app, the kind used for calls, though the two meet at hybrid events and this page covers where. It is one of the most common community and organisation apps, because every association, user group and industry body runs at least one event a year and rebuilds the same agenda screen every time.
This page is about what the app has to carry: the records behind the agenda, the alerts that are worth a push, the difference between this and a conference video app, what the established platforms charge, and when a conference ends up building its own.
See what a conference app needs to carryThe short version
One agenda per person, alerts that are rare, and a map that works without signal.
A mobile app for a conference needs sessions whose rooms and times live on the server, a personal agenda for each attendee, push alerts that go to the people a change affects rather than to everyone, a venue map and agenda that still open when the hall has no signal, a badge QR code for the door, and, for hybrid events, a stream or call link on each session. Everything else, networking, polls, sponsor listings, is worth having, but those six are the reason people install it.
The records behind the agenda
What a mobile app for a conference actually needs.
Every conference app, off the shelf or custom, is a handful of records and the rules between them. The screens are the easy part. Here is the set, with the rule on each one that decides whether attendees trust the app on the day:
| Record | Fields | The rule that matters |
|---|---|---|
| Event | Name, dates, venue address, time zone, code of conduct, organiser contact. | Store every time in the venue's time zone and show it that way to people in the building. Remote attendees see their own. |
| Session | Title, abstract, track, start, end, room, speakers, format (talk, workshop, panel), level, capacity, stream link, recording link. | Room and time live on the server, never inside the app build, so a swap on the day does not need a new release. |
| Speaker | Name, photo, title, organisation, bio, sessions, links. | One record, linked from every session it appears in. Edit it once. |
| Room | Name, floor, capacity, map pin, accessibility notes, nearest exit. | Capacity is what turns a workshop into a waitlist, so it is a number, not a note in the description. |
| Attendee | Name, organisation, role, ticket type, interests, directory opt-in, badge QR code. | The directory is opt-in, and the attendee chooses which fields other people can see. |
| Personal agenda | Attendee, session, reminder offset, seat or waitlist status. | This is the join between people and sessions, and it is what makes a targeted alert possible at all. |
| Announcement | Title, body, audience (everyone, a track, a session, a ticket type), send time, channel (push, in-app feed, both). | Audience is a required field. Everyone is the exception, not the default. |
| Sponsor or exhibitor | Name, tier, booth number, logo, description, offer, lead-capture opt-in. | A lead is shared with a sponsor only when the attendee agrees at the booth, one scan at a time. |
| Feedback | Session rating, comment, event survey answers. | Ask at the end of each session, while people still remember it, not at the end of the week. |
Two of these carry more weight than they look. The personal agenda record is what lets you alert the forty people affected by a room change instead of the four hundred in the building. The announcement's audience field is what stops every phone in the hall buzzing for a sponsor's coffee voucher.
The workflow
The conference week, in order.
The records above are only useful in a sequence. This is the one most conferences follow, and each step leans on a field from the table.
- 1
Before tickets go on sale
Ship the shell, load the agenda from the server
The app goes through App Store review once. Everything that changes, sessions, rooms, speakers, sponsors, comes from your backend, so the schedule can be half finished when the app is approved and complete on the day.
- 2
As registrations arrive
Import attendees with their ticket type
Ticket type decides what the app shows: a workshop pass unlocks workshop booking, an online pass shows stream links instead of a map, a speaker pass shows the green room and the tech check slot.
- 3
In the run-up
Open personal agendas and flag clashes
Attendees star the sessions they want. When two starred sessions overlap, say so on the spot, and let a workshop with a capacity fill up and start a waitlist rather than overbook.
- 4
At the door
Scan the badge QR from the app
The QR code on the attendee record is the ticket. A scan at the door records who arrived and when, which is also the headcount you need if the building has to be cleared.
- 5
During the event
Send the alerts that matter, to the people they matter to
A room change goes to everyone who starred that session. A starting-soon reminder goes to the people who starred it. The whole audience hears about doors, the keynote, lunch and the closing survey, and little else.
- 6
After the last session
Turn the app into the archive
Recordings attach to the session records, ratings roll up per speaker, sponsors get the leads attendees agreed to share, and the app stays installed until next year's edition loads into the same shell.
Push notifications
Which alerts are worth a push?
The push channel is the reason attendees install a conference app rather than bookmark a web page, and it is also the fastest way to lose them. Apple's Human Interface Guidelines put it plainly: notifications need consent first, they should be concise and informative, and sending several for the same thing fills up Notification Center until people turn off all notifications from the app. The same guidance warns against putting personal or confidential information in a notification, which at a conference means no attendee's name in a push. Read Apple's notification guidelines
Applied to a conference, the audience and timing rules look like this:
| What happened | Who gets it | When | Push? |
|---|---|---|---|
| Room or time change | People who saved that session | Immediately | Yes |
| Session starting soon | People who saved that session | Ten minutes before, once | Yes |
| Doors open, keynote, lunch | Everyone on site | Once each | Yes |
| Venue notice or emergency | Everyone on site | Immediately | Yes |
| Closing survey | Everyone | Once, after the last session | Yes |
| Empty agenda nudge | People who have not saved a session | Once, before the event | in-app first |
| Sponsor offer or booth promo | Nobody, by push | In-app feed only | No |
These are product decisions, and they belong in the announcement record as an audience and a channel, so nobody can send to everyone by accident. Getting a push onto a phone, the permission prompt, device tokens, delivery and what happens when the app is closed, is a separate subject, covered in push notifications in mobile apps.
App or no app
Does every conference need an app?
No. A single-track day with a fixed programme is better served by a good web page, and an app nobody opens is worse than no app, because the organiser stops sending the emails that were working. The app earns its place when the schedule is personal, when it changes, or when the venue swallows the signal.
Try it
Does your conference need its own app?
Tick what is true of your event. This is a starting point, not a verdict; the right answer also depends on budget and on who will look after the app between editions.
Suggested route
Tick the statements above to see a suggested route.
Picking an approach
Programme PDF, website, platform, or your own app.
None of the records above need a particular tool, but each route makes at least one of them hard to get right.
| Approach | Personal agenda | Targeted push alerts | Works offline in the venue | Your name on the store listing | Price model | Who maintains it |
|---|---|---|---|---|---|---|
| PDF programme and email | No | No | yes, once downloaded | No | Free | You, by re-sending it |
| Conference website on mobile web | if you build it | web push only | No | No | Hosting and a developer | You or an agency |
| Event app platform (Whova, Cvent) | Yes | Yes | varies by platform | ask in the quote | Quote per event | The vendor |
| Custom-built conference app | Yes | Yes | if you specify it | Yes | Build cost plus Apple's yearly fee | You |
The shape underneath, one organiser broadcasting a schedule to a group that needs it on their phones, is not unique to conferences. It is the same shape as the best sports team communication app, a roster, fixtures and targeted alerts, and the best app for wedding planning, a timeline, a guest list and a venue. What changes is the vocabulary and the rules, which is why the records table matters more than the screenshots.
Terminology
Is a conference app the same as a video conference app?
Search results mix three products under one word. A conference app is the event companion on this page. A video conference app carries real-time audio and video between participants; it is what people mean by an app for conference video calls. Conference room scheduling, booking meeting rooms inside an office, is a separate need with its own software, and it is not covered here.
| What people call it | What it does | Who opens it | Where the two meet |
|---|---|---|---|
| Conference app (event companion) | Agenda, rooms, speakers, alerts, networking and check-in for one event | Attendees, speakers, sponsors and the organising team | Holds the stream or call link on each session so remote attendees join from the same agenda |
| Video conference app | Real-time audio and video between participants, screen sharing, recording | Anyone on a call; at a hybrid event, the remote attendees | Supplies the link the event app opens; it knows nothing about the agenda |
The overlap is the hybrid event. Remote attendees do not want a second app; they want the same agenda with a stream or call link on each session, session-level Q&A that the room moderator can see, and recordings that appear on the session afterwards. Nobody builds the video stack for that. The conference app holds the link and the access rule, online pass or in-person pass, and the video itself runs on a streaming or meeting service that already copes with a large audience. A conference video app in that sense is an event app with a link field on every session, not a replacement for the meeting tool.
What it costs
What does a mobile app for a conference cost?
The two names that come up first, Whova and Cvent, do not publish prices. Checked on 21 September 2026, Whova's pricing page is a quote request form: it asks for the event's format, its duration, the attendee count and how often you run events, then offers a demo. Cvent's pricing page lists Professional and Enterprise tiers and prices Registration, Attendee Hub, its attendee-facing event app, and OnArrival, its check-in product, as separate licences, with special rates for non-profits, again by quote. Budget for a conversation rather than a checkout, and expect the number to move with headcount and with how many events you run.
Two costs are fixed whichever route you take. Publishing on iOS needs an Apple Developer Program membership, 99 USD per membership year according to Apple's enrolment page, which also says nonprofits, accredited educational institutions and government entities that meet its requirements can request a fee waiver, and that covers a good share of the bodies that run conferences. And someone has to own the App Store listing: screenshots, a privacy policy, a demo account for the reviewer, and the resubmission when something changes.
Building your own moves the cost from per event to per month. Newly, for example, is $25 a month with no free plan; it builds the app from a description and ships the iOS build to App Store Connect, where you run it through TestFlight and submit it for review yourself. It does not produce Android release builds today, so an event with a large Android audience needs the agenda on the web as well, which is worth having anyway: the web version is the one that gets shared before anyone has installed anything.
When to build your own
Building a conference app around your own process.
The reason a conference builds its own app is rarely price and usually fit. Ticket types that unlock different things, a workshop booking rule the platform does not have, a code of conduct flow, a sponsor tier that wants something the template does not offer, an app under the organisation's own name that stays installed between editions. Each is small, and together they are a process that no off-the-shelf tool quite matches. That gap is what Newly is for: describe the conference you actually run, the records above, who sees what, which alerts go to whom, and it builds a real native app around that instead of around a vendor's template.
Write the records and the alert rules down first, on paper, since they are cheap to change before anything is built and expensive after. The table at the top of this page is the starting point for that document; the audience column of the alerts table is the part most teams forget to write down.
Sources
Where the specifics came from.
Four things on this page come from a primary source rather than general industry practice. The two pricing pages were checked on 21 September 2026.
FAQ
Conference apps, answered.
A conference app is the attendee's companion for the event itself: a personal agenda built from the session list, speaker and room details, a venue map, push alerts when a room or time changes, the attendee directory and messaging, the badge or QR ticket for check-in, live Q&A and polls, the sponsor and exhibitor list, and for hybrid events the stream link for each session. It replaces the printed programme and the stream of update emails with one place that is always current.
Start with the agenda, not the app icon.
A conference app lives or dies on records that stay current and alerts that reach the right forty people. Get those right, then build the app around them in Newly.