Build log/Events

What an event app needs, and what attendees rarely open

An event app earns its place with the ticket, the schedule, the map and live updates. Networking and sponsor pages need a clear purpose, or they tend to sit unopened.

The short answer

  • An event app needs four things attendees use at the venue: a ticket that opens without signal, a schedule with a personal agenda, a venue map and live updates.
  • Networking features only work when enough attendees opt in and there is a specific reason to connect, such as booking meetings at a trade show.
  • For a one-off event, a fast mobile website with Apple Wallet and Google Wallet passes often does the job, while a native app suits events the same people return to.

An event app is software on an attendee’s phone that holds their ticket and tells them where to be and when. The features that earn their place are the ones people need at the venue: the ticket, the schedule with a personal agenda, a map and live updates. Networking, sponsor pages and gamification are the features most likely to go unopened unless each one is designed around a real reason to use it.

The four features attendees use on the day

Start from what an attendee does between arriving and leaving. They show a ticket at the door. They check what is on next and where. They find a room, a stage or the toilets. They find out when something changes. Every feature in an event app should support one of those four jobs, or have a clear reason to exist alongside them.

Ticket wallet

The ticket should open in two taps, with no login and no signal. The most reliable way to do that is a wallet pass. Apple Wallet and Google Wallet both support event tickets and store the barcode on the phone, so the pass opens even when the venue network is down. If the app has its own ticket screen as well, cache the barcode on the device the first time it loads. Our article on offline event check-in covers the scanning side at the door.

Schedule and personal agenda

A schedule lists every session. A personal agenda is the attendee’s own shortlist, built by starring the sessions they want. The agenda is what people check during the day, so it should be one tap from the home screen and should flag a clash when two starred sessions overlap. Filters by day, track, stage and time matter more than clever recommendations. Each session needs a room, a start and end time, the speakers and a short description, all kept in step with the organiser’s master schedule.

Venue map

A map answers “where is Hall 3” faster than any signpost. It does not need to be an interactive 3D model. A clear floor plan for each level, with room names that match the schedule exactly, does the job. Link every session to its room on the map, and mark the things people look for most: entrances, toilets, food, the cloakroom and first aid. If the venue changes between years, the organiser must be able to replace the map without a new app release.

Live updates

Room changes, delays, cancelled sessions and safety messages need to reach people quickly. Push notifications do this best, with an announcements feed inside the app as the record of what was sent. Keep pushes rare and useful. An app that sends sponsor promotions every hour teaches people to mute it, and then the safety message goes unseen. We cover this in push notifications that help.

Features that often go unopened

Some features appear on every event app feature list and get little use in practice. They are not useless, but each one needs a plan.

  • Attendee networking. A directory of attendees only works if enough people opt in and complete a profile. At a small event most people would rather walk over and talk. Networking earns its place when it solves a specific problem, such as booking 15-minute meetings between buyers and suppliers at a trade show. Appearing in a directory shares personal data, so make it opt-in and explain who will see each profile.
  • Sponsor pages. A list of sponsor logos with a paragraph each is rarely read. Sponsors usually get more from a session they host appearing in the agenda, or a stand marked on the map.
  • Gamification. Points for visiting stands can work at a large exhibition with a prize worth chasing. At a one-day conference it is mostly noise.
  • Session chat and Q&A. Q&A with upvoting works well when a moderator reads the questions out on stage. Open chat channels for each session often stay empty.
  • Social feeds. An in-app feed competes with the social networks attendees already use, and it needs moderating.

A useful test for any feature is to name the moment at the event when someone will open it, and what they will do in the next 30 seconds. If nobody on the team can name that moment, leave the feature out of the first version and add it when there is evidence people want it.

Working offline at a busy venue

Venue Wi-Fi and mobile networks struggle when thousands of phones share one building. An event app should assume a weak connection at exactly the moment it matters most. In practice that means five rules.

  1. Download the full schedule, speaker list and maps when the app is first opened, and refresh them in the background whenever there is a connection.
  2. Store the ticket barcode on the device.
  3. Save agenda changes on the phone first and sync them later.
  4. Show when the schedule was last updated, so an attendee knows whether they are looking at the latest version.
  5. Keep images small, so the first download finishes on a weak signal.

This is the same approach we use in Estimark, which saves to the phone first and syncs later, because a building site has the same problem as a packed exhibition hall.

Native app, mobile website or white-label platform

There are three ways to put an event guide on an attendee’s phone. The right one depends mainly on how often your audience will use it.

Mobile website or PWAWhite-label event platformCustom native app
Attendee has to installNoUsuallyYes
Push notificationsLimited on iPhoneYesYes
Works offlineYes, if built for itDepends on the platformYes, if built for it
Wallet ticketsYesUsuallyYes
Design and featuresFull controlWithin the platform’s optionsFull control
Time to launchShortShortestLongest, including app store review
Best fitSingle events and one-off conferencesOrganisers who want standard features nowEvent series, membership bodies, products where the app is the business

Requiring an install asks a lot of someone attending for one day. Many will not bother, and the organiser ends up running a printed programme alongside the app. A fast mobile website, linked from the confirmation email and a QR code at the door, reaches everyone. The main gap is notifications. On iPhone, a website can only send push notifications once the person has added it to their Home Screen. Our guide to PWAs and native apps goes into the detail.

A native app makes sense when the same people come back, for example to a festival series, an annual conference run by a membership body, or a venue with a season of events. The install is then paid for once, and the app becomes a channel the organiser owns all year.

When to build and when to use a white-label platform

White-label event platforms sell a ready-made app that carries your branding. They are quick to set up and include the standard features above. The trade-offs are that you work within their data model, their design options and their pricing. Attendee data also sits on their systems under their terms, which you need to check as part of your obligations as controller under UK GDPR.

A custom build makes sense when the app needs to do something the platforms do not, or when it must connect closely to your own systems. Signs that you are in that position:

  • Your ticketing, membership or CRM system is your own, and the app must read and write to it in real time.
  • You run many events a year and per-event or per-attendee platform charges keep adding up.
  • The app is part of what you sell, for example meeting slots at a trade show or cashless top-ups at a festival.
  • You need offline behaviour or accessibility that the platforms you have tried do not provide.

Whichever route you take, test on a crowded network before the event, check the app with a screen reader and large text settings, and agree who on the organiser’s team can send a push notification on the day.

Planning an event app or attendee portal? See how we approach event software.

Questions people ask

What features does an event app need?

An event app needs a ticket that opens without signal, a schedule with a personal agenda, a venue map and live updates through push notifications or an announcements feed. These cover what attendees actually do at the venue. Networking, sponsor pages and gamification are optional and should be added only with a specific use in mind.

Do attendees download event apps?

Installing an app is a bigger ask for a single day than for a multi-day event or one people attend every year. For a one-off event, a mobile website reached by a link or QR code removes the install step entirely. Whichever you choose, also offer the ticket as an Apple Wallet or Google Wallet pass.

Should an event app work offline?

Yes. Venue networks are often overloaded when an event is busiest, which is when attendees need the app. The ticket, schedule and maps should be stored on the phone, with any changes synced when a connection returns.

Is a white-label event app good enough?

For many organisers it is, especially for standard conferences that need a schedule, a map and a ticket. It becomes limiting when the app must connect closely to your own ticketing or membership systems, or when you need features the platform does not offer. Check where attendee data is stored, and on what terms, before signing.

Written by Flavoureak

We build and run Estimark, CurioKids and CalcStack, and we build web and mobile software for other businesses. Start a project.