A checklist of the features buyers ask about, grouped by job. For each one: what it is for, the question that separates a real answer from a tick in a box, and WebMobi’s answer — Yes, Partly or No — read from our feature register.
38 features · WebMobi column checked 2026-10-14
Every event app vendor will tick most of the boxes on a generic feature list. What separates them is the detail behind the tick: whether a feature works the way your event needs, whether it is inside the plan you were quoted, and whether it is live today or on a roadmap. So each feature below comes with the question to ask, worded to be hard to answer with a yes alone.
The WebMobi column is our own answer, read from WebMobi’s feature register on 2026-10-14: a feature is Yes only when the register records it as live in production. Of the 38 features here, WebMobi answers Yes to 23, Partly to 1 and No to 14. Use the checklist with the event app buying guide, which turns the features you need into tests to run in a demo, and send the written questions from the event app RFP to vendors who must answer on paper.
WebMobi Event App Builder · Build and launch your event app yourself.
WebMobi Event App Builder is a self-service event app builder that helps conference organizers, associations, agencies and event teams create and launch branded event apps — with registration, check-in (including offline check-in and walk-ins), session attendance, agenda, speakers and exhibitors in one platform.
What attendees will see, and how it gets into the system without retyping.
What it is for: Where people find the event and register before they ever open an app — the address you print and share.
Ask the vendor: “Can I choose the web address, change it after publishing, and will links to the old address still work?”
WebMobi today: Yes. Your event page has its own web address, which you can change in Settings; everyone holding the old address still arrives.
What it is for: The programme attendees navigate by: times, rooms, tracks and who is speaking.
Ask the vendor: “If I move a session after publishing, where does the change appear?”
WebMobi today: Yes. Sessions carry their rooms and locations inside the venue, and a session you edit once changes on the event page and in the app. See the agenda builder.
What it is for: Who is talking and why attendees should go, linked to the sessions they speak in.
Ask the vendor: “Do speakers’ email addresses stay private, and can a speaker be announced before the agenda is final?”
WebMobi today: Yes. Profiles appear on the event page and in the app without the speaker’s email address, and imported speakers show even before they are placed on a session. See speaker management.
What it is for: Getting the programme and the attendee list in from the files your team already keeps.
Ask the vendor: “Are my column headings recognised, and does importing the same file again duplicate, update or delete rows?”
WebMobi today: Yes. Sessions, speakers, sponsors, exhibitors and attendees import from a spreadsheet; headings such as first_name are recognised, sessions can link speakers by name or email, and an import adds and updates but never deletes. See bulk attendee import.
What it is for: Letting a sponsor, a speaker or a manager check the event before the public sees it.
Ask the vendor: “Can I share the event privately for review before it goes live?”
WebMobi today: Yes. A preview link shares the event privately before it is published.
What it is for: Reviewing the programme in a spreadsheet, or moving it between tools, without breaking it.
Ask the vendor: “If I export the agenda and import it back, do session times stay where they were?”
WebMobi today: Yes. The agenda exports with wall-clock times and the time zone named, so it can be imported back without sessions moving.
Who is coming, and what you know about them before they arrive.
What it is for: Collecting who is coming, with the person’s details kept by you rather than by a marketplace.
Ask the vendor: “When someone registers, whose list do they join — mine, or the vendor’s marketplace?”
WebMobi today: Yes. People register on your WebMobi event page and join your registration list, and you can add people by hand. See the event registration platform.
What it is for: Asking about dietary needs, job titles or session choices at sign-up.
Ask the vendor: “Can I add my own questions to the form, and do the answers appear in the export?”
WebMobi today: No. Custom registration questions are not part of WebMobi’s live feature set today.
What it is for: Charging for a place as people register.
Ask the vendor: “Who processes the payment, what fee is taken per ticket, and how are refunds handled?”
WebMobi today: No. WebMobi does not take ticket payments. For a paid event, paste the link to the ticketing you already use and the event’s button sends people there.
What it is for: Lower prices for groups or early registrants, and a queue for places once the event is full.
Ask the vendor: “Are discount codes and a waitlist inside the plan I am quoted?”
WebMobi today: No. Neither discount codes nor a waitlist is part of WebMobi’s live feature set today.
What it is for: Events that should not be advertised: an internal meeting, a members-only session.
Ask the vendor: “Can invited people get into an event that is not publicly advertised, and what does ‘private’ not stop?”
WebMobi today: Yes. Attendees enter the access code you send them to open the event. A code is not a guest list, so read what it does and does not stop before you rely on it. See private event registration.
What it is for: A personal code per registration, scanned at the door and at session rooms.
Ask the vendor: “Does every registration get its own code, including people added by hand or imported?”
WebMobi today: Yes. Every registration gets its own QR code. See QR code check-in.
The part of an event app that decides how opening time goes, and what you know afterwards.
What it is for: Getting people through the door quickly without special hardware.
Ask the vendor: “Can staff scan with their own phones, in an app and in a browser?”
WebMobi today: Yes. Staff scan attendee codes with the WebMobi app or in a phone browser. See event check-in.
What it is for: The attendee whose phone has died, or who never found the email with their code.
Ask the vendor: “Can staff find someone by name or email and check them in without a code?”
WebMobi today: Yes. Staff find the person by name or email and check them in, on the web and in the WebMobi app. See event check-in.
What it is for: People who turn up without registering.
Ask the vendor: “Can a walk-in be registered and checked in in one step, and what stops the same person being added twice?”
WebMobi today: Yes. A walk-in is registered and checked in in one step, and an email already registered for the event is matched to that registration instead of creating a second one. See walk-in registration.
What it is for: Venues with unreliable signal: basements, field sites, overloaded conference Wi-Fi.
Ask the vendor: “What works with no connection, on which phones, and which time is recorded — the desk time or the sync time?”
WebMobi today: Yes, in the WebMobi app: check-ins made with no signal are kept on the phone and sent when it reconnects, with the time they were made at the desk. The web check-in page needs a connection; what works on iPhone and on Android is in the note below. See offline event check-in.
What it is for: Knowing who attended each session, not just who came through the front door.
Ask the vendor: “Can staff scan into a specific session, in and out, and can I download who attended each one?”
WebMobi today: Yes. Staff choose the session in the app or on the web Check-In page and scan in and out; the attendance report lists the people in each session and downloads as a CSV. See session check-in.
What it is for: Answering “who let this person in, and when?” after the event.
Ask the vendor: “Is each check-in recorded with the staff member, the device and whether it was made offline?”
WebMobi today: Yes. History lists every check-in with the staff member, the device and whether it was taken offline, and shows when each phone last synced. See the check-in audit trail.
What it is for: Printed name badges produced at the desk or before the event.
Ask the vendor: “Can badges be designed and printed from the attendee list, and on which printers?”
WebMobi today: No. WebMobi does not design or print badges; attendees show their QR code. Print badges from your own template if you need them.
What attendees hold, whose name is on it, and how you reach them through it.
What it is for: The agenda, speakers, sponsors and exhibitors in attendees’ pockets.
Ask the vendor: “Do attendees install one app for every event or a separate app per event — and when was it last updated?”
WebMobi today: Yes. Attendees open your event in the WebMobi app from the App Store or Google Play. See WebMobi Event App Builder.
What it is for: Making the event look like yours rather than the vendor’s.
Ask the vendor: “What exactly carries my brand in the app, and on which plan?”
WebMobi today: Yes, on paid plans: attendees see your event’s branded experience inside the WebMobi app. On other plans they see the standard WebMobi layout.
What it is for: Your organisation’s name and icon on the App Store and Google Play.
Ask the vendor: “Is the app published under my organisation’s name, who owns the listing, and who keeps it updated?”
WebMobi today: No. Your event runs inside the WebMobi app, listed as “WebMobi: Event App Builder” on the App Store and Google Play.
What it is for: Telling everyone at once that a session has moved.
Ask the vendor: “Can I send a push message to every attendee, or only to one session’s audience?”
WebMobi today: No. Push notifications are not part of WebMobi’s live feature set today.
What it is for: Attendees finding each other and arranging to meet during the event.
Ask the vendor: “Is networking inside the plan I am quoted, is it on by default, and can attendees message each other directly?”
WebMobi today: No. WebMobi networking is in private beta and is not enabled by default. Request activation at /contact-sales or support@webmobi.com.
Features that give attendees something to do between sessions.
What it is for: Giving attendees a reason to visit sessions and booths they would otherwise skip.
Ask the vendor: “What earns points, who sets the challenges, and where is the leaderboard shown?”
WebMobi today: No. Points, challenges and leaderboards are not something an organiser can set up and run in WebMobi today.
What it is for: Guests sharing photos and messages on a screen in the room.
Ask the vendor: “How do guests post to the wall, and who controls what is shown?”
WebMobi today: Yes. Guests scan a code and post a photo or a message to the Live Wall.
What it is for: Asking the room a question and showing the answers live.
Ask the vendor: “Can a speaker run a poll or take questions from the app during a session?”
WebMobi today: No. Live polls and audience questions are not part of WebMobi’s live feature set today.
What it is for: Finding out what attendees thought of each session and of the event.
Ask the vendor: “Can attendees rate sessions in the app, and can I export the results by session?”
WebMobi today: No. Surveys and session ratings are not part of WebMobi’s live feature set today; session check-ins are the attendance signal.
What it is for: Letting people who cannot travel watch sessions live.
Ask the vendor: “Is streaming built in or a separate product, and is it inside the plan I am quoted?”
WebMobi today: No. WebMobi runs the in-person event; there is no streaming or virtual attendance.
The people who help pay for the event, and what they get from the app.
What it is for: Recognising sponsors under the tier names you sold, in the order you promised.
Ask the vendor: “Can I use my own tier names and decide who appears first?”
WebMobi today: Yes. Sponsor tiers keep the wording you give them, a display order you set decides who appears first, and each sponsor has a logo and a page of its own.
What it is for: Helping attendees find the exhibitors they came to see.
Ask the vendor: “Are exhibitors listed with their booth numbers on the event page and in the app?”
WebMobi today: Yes. Exhibitors are listed with their booths on the event page and in the app.
What it is for: Exhibitors scanning visitors’ codes to collect leads at their booth.
Ask the vendor: “Can exhibitors scan attendees, add notes and export their leads — and is that a separate licence?”
WebMobi today: No. There is no lead retrieval for exhibitors or sponsors; only your own check-in staff scan attendee codes.
Who can change what, what is recorded, and how you get your data out.
What it is for: Several people building and running the event without sharing one login.
Ask the vendor: “Can teammates edit the programme under their own accounts, and what can each role do?”
WebMobi today: Yes. Each person in your organization is an owner, an admin or a member, and teammates you make admins of an event can edit its speakers, sessions, sponsors, exhibitors and venues. See team permissions.
What it is for: Finding out what changed in the event, when, and what it said before.
Ask the vendor: “Is every change recorded with its before and after values and the person who made it?”
WebMobi today: Partly. Every change to your event content is recorded with what changed and when, and shown to the people who manage the event — but a change made directly in the dashboard is not yet attributed to the person who made it.
What it is for: Handing attendance to colleagues or other systems — and being able to leave one day.
Ask the vendor: “What can I export, in what format, and are times labelled with their time zone?”
WebMobi today: Yes. Session attendance and the agenda export as CSV files, with times in the event’s own time zone and the zone named. See attendance reports.
What it is for: Sending reminders and updates to everyone registered.
Ask the vendor: “Can I email all registrants, or one session’s attendees, from inside the platform?”
WebMobi today: No. Sending your own emails to attendees from inside WebMobi is not part of its live feature set today.
How the event app connects to the rest of your tools.
What it is for: Reading event data in your own systems, or working on the event from an AI assistant.
Ask the vendor: “What can the API read and write, and how is access authenticated?”
WebMobi today: Yes. A REST API reads your events, and WebMobi’s MCP server lets you work on your events from Claude or another MCP client. See the events API and MCP server.
What it is for: Sending registrations and attendance straight into your CRM or marketing tool.
Ask the vendor: “Which CRMs are connected natively, in which direction, and is it a separate licence?”
WebMobi today: No. There are no CRM connectors; data leaves WebMobi as CSV files you download.
A checklist tells you what to ask; a comparison tells you what each vendor has already published. Ours read each vendor’s own pages, record the date, and score WebMobi by the same rule:
New to the category? Start with what an event app is and the three ways to get one.
Written down here so you find out now, not on event day.
Ticket payments, custom registration questions, discount codes, waitlists, badge printing, an app under your own name, push notifications, points and leaderboards you can run, live polls, surveys, streaming, exhibitor lead retrieval, emailing attendees from the platform and CRM connectors.
WebMobi networking is in private beta and is not enabled by default. Request activation at /contact-sales or support@webmobi.com.
The web check-in page needs a connection. What works offline on iPhone and on Android is in the note under Check-in and attendance.
Content changes are recorded with what changed and when; check-ins are recorded with the staff member who made them.
On paid plans attendees see your event’s branded experience in the WebMobi app; on other plans, the standard WebMobi layout. Which plan includes what is on the pricing page.
The screens, labels and checks for each step are in the product guide on events.webmobi.com.
Sessions, speakers and sponsors — by hand or by spreadsheet, and what an import never does.
An import adds and updates but never deletes; matching, file limits, column mapping, the Event Info sheet.
Which way to check someone in, preparing phones, and what each phone shows with no signal.
Recording who attended each session on the web and in the app, re-entry, and the attendance export.
Who changed the event and who checked in whom — staff member, device, offline or not, repeat scans.
The three CSV exports, what each file contains, its time zone rules and its limits.
What each plan includes is on the pricing page.
The ones your event-day jobs need. For most in-person events that means an event page with registration, the agenda and speakers in an app, QR check-in that works on ordinary phones, a plan for when the venue has no signal, session attendance if sessions matter to you, and exports so the data can leave with you.
Because a checklist that lists only what the author sells is a brochure. The WebMobi column is read from our feature register: a capability is Yes only when the register records it as live in production, and Partly where it works with a stated gap.
Yes, in the WebMobi app. Check-ins made with no signal are kept on the phone and sent when it reconnects, with the time they were made at the desk. The web check-in page needs a connection.
No. WebMobi networking is in private beta and is not enabled by default. Request activation at /contact-sales or support@webmobi.com.
No. WebMobi does not take ticket payments. A paid event’s button can send people to the ticketing you already use.
No. There is no lead retrieval for exhibitors or sponsors; only your own check-in staff scan attendee codes.
No. Your event runs inside the WebMobi app on the App Store and Google Play; on paid plans attendees see your event’s branded experience inside it.
It was checked against WebMobi’s feature register on 2026-10-14. What each plan includes is on the pricing page; if a capability matters to your event, ask us to show it to you working.
Create an event and try the features your event depends on, or book a demo and we will show each one working — and tell you plainly where the answer is no.