Does the event app work offline?

Full offline mode means the app keeps doing its job when the phone has no usable connection: airplane mode, a dead zone, or a venue Wi-Fi that is technically connected and practically useless. With no network, an attendee can still: — open the attendee directory and browse profiles; — read the agenda — sessions, times, rooms, speakers; — open the personal documents the organizer has made available to them; — check in and check out. That list is short on purpose, and precise on purpose. It covers the questions an attendee actually asks while standing in a hall: where do I go next, who is here, who is this person in front of me, am I counted as present. None of those should depend on the venue’s Wi-Fi, because none of them can wait.

This part matters more than the feature list, because an attendee who expects everything to work is exactly the attendee who decides the app is broken. Anything that is an exchange with someone else, right now, needs a network. A message is delivered when there is a path to deliver it, and not before. Live questions and polls are live by definition: they are collected and shown in the room as they happen, on both sides of the connection. Anything new also needs a network. If the organizer moves a session to another room, posts a news item, or adds a document while a phone is offline, that phone cannot know about it until it reconnects. Offline mode preserves what is already there; it does not receive what has not arrived yet. And one obvious thing worth saying out loud: installing the app needs a connection. An attendee who walks into a basement hall with no signal and no app installed cannot install it there. That is an operational problem rather than a technical one, and it gets solved before the doors open, not after. If you are comparing vendors on this point, ask for the list rather than the adjective. "Works offline" is an adjective. "The directory, the agenda, profiles, personal documents and check-in work offline" is a list, and a list can be tested.

Two moments decide everything. Before. The content has to be on the phone before it is needed. In practice that means opening the app at least once with a working connection — at home, at the hotel, on the train, in the lobby where the signal still holds. What the app has loaded is what stays available two floors down. That is why the download rate is an operating number rather than a vanity metric. Someone who installs the app on the escalator down to the exhibition hall gets neither the network nor the content. Across our events equipped with badges we measure roughly 85% download and usage (internal measurement, 2018), and at a SPIE seminar in 2018, 94% of attendees had downloaded the app. Those numbers are built in the two weeks before the event, with SMS and email campaigns, not at the registration desk. After. Actions taken with no network are replayed once the connection comes back. A check-in recorded in a basement breakout room is not lost: it goes up when the phone finds a signal again, and it lands in the organizer’s back office like any other. That replay is what separates a real offline mode from a read-only copy of the agenda. An app that only lets you look at things while the network is down is a cache. An app that lets you act, then honors those actions, works offline. One honest caveat: replay is not real time. If you need something visible on the organizer side during the session itself — a live headcount at the door of a full room — that needs a connection, like anything else that happens now.

Two situations, one symptom, two different causes — and the same precaution. The basement. Plenary rooms, breakout rooms and exhibition halls sit below ground level far more often than not, behind concrete and steel. Cellular coverage does not go down there, and there is nothing to negotiate: it is physics, not goodwill. The venue may offer Wi-Fi, and that Wi-Fi may or may not reach the back of room 4. Saturated Wi-Fi is the worse case, because the phone believes it is connected. The status bar is full and nothing loads. Two thousand people walking into the same hall between 8:40 and 9:00, all opening the agenda within the same five minutes, is a load profile most venue networks were never sized for. The same thing happens again at the mid-morning break, and again just before the closing session. What follows for an organizer is a planning rule more than a technical one: never build the day around the venue’s network, and never treat the Wi-Fi password as a deliverable. Assume the connection will be unusable during the two peaks, then check that what you need at exactly those moments — the agenda in everyone’s hand, check-in at the door — is on the list of things that work without it.

None of them technical. Get the app installed early. Two weeks out, by SMS and email, with a clear reason to install it now rather than on arrival. Ask everyone to open it once before they travel. That one launch with a connection is what fills the phone. Publish the agenda early. Last-minute changes are precisely the ones that will not reach the people already underground. Say it from the stage. "The agenda, the directory and check-in work without a network; messaging and live questions need one" is a sentence a host delivers in ten seconds, and it prevents most of the complaints. None of this is exotic. It is the difference between an app that holds up in the hall and an app that gets blamed for the building.

— App features: /features — The organizer dashboard: /organizer-dashboard — Conferences: /conferences — Trade shows and exhibitions: /trade-shows — Corporate events and internal meetings: /corporate-events — The Smart Ruby badge: /badges — Case studies: /case-studies — Talk to us: /contact