Most organisers assume a conference needs its own app. Then they see the quote, wait weeks for app-store approval, and watch a fraction of delegates actually install it. Before you commission a native app, it is worth asking what your delegates need it to do, and whether a web app does the same job without the download. This guide lays out the choice.
What delegates use an event app for
Strip away the pitch and delegates use an event app for a short list of things: their badge for check-in, the programme and their own sessions, updates from the organiser, and sometimes networking with other delegates. Almost all of that is information they read on their phone. It does not need the deep device access that a native app is built for.
The problem with native apps
- The download barrier. Every delegate has to find your app, download it, and open it. Many never do, so your carefully built app reaches a fraction of the room.
- App-store delays. Apple and Google review builds. A last-minute change can sit in a queue while your event runs.
- Cost. A native app usually means two builds, iOS and Android, and a bill to match.
- Short shelf life. Delegates download an app for a two-day event and delete it the week after.
The web app alternative
A web app, technically a progressive web app or PWA, runs in the browser. The delegate opens a link and it works straight away. In two taps they add it to their home screen, where it gets an icon and behaves like an installed app. It caches the badge and schedule so the essentials work offline, and once it is on the home screen you can send push notifications to the phone. There is no store, no download barrier, and one link covers iPhone and Android.
Native app vs web app
| Factor | Native app | Web app (PWA) |
|---|---|---|
| Delegate has to download | Yes, from an app store | No, opens from a link |
| Works on iPhone and Android | Two separate builds | One link |
| Push notifications | Yes | Yes, once added to home screen |
| Offline access | Yes | Yes, cached essentials |
| App-store review | Required, can delay changes | None |
| Typical cost | High | Low |
Which one to choose
Choose a native app when you genuinely need heavy device features, such as offline maps, augmented reality or hardware integrations, and you run large events often enough to justify the cost. For most conferences, summits and corporate events, a web app delivers the badge, schedule, updates and notifications delegates actually use, and far more of them use it because there is nothing to install.
The Orkestriq delegate portal
Orkestriq gives every delegate a web-based portal that works from a link and installs to the home screen in two taps. It carries their QR badge, schedule and updates, works offline when Wi-Fi drops, and lets you push notifications straight to their phone. No app store, no download, on iPhone and Android.
See how it works →Frequently asked questions
Do delegates have to download anything?
Not with a web app. Delegates open a link and can add it to their home screen in two taps, where it behaves like an app. A native app has to be downloaded from the App Store or Play Store first.
Does a web app work offline?
Yes. A well-built web app (a PWA) caches the delegate's badge, schedule and event details on the device, so the essentials keep working when venue Wi-Fi is patchy.
Can a web app send push notifications?
Yes. Once a delegate adds the web app to their home screen, you can send push notifications to their phone, the same way a native app does.
Does it work on both iPhone and Android?
Yes. A web app runs in the browser, so it works on iPhone and Android from a single link, with no separate builds to maintain.