A branded event app that ships under your name
A branded event app is an event app that carries the organizer's name, logo and colours instead of the vendor's. event67 publishes branded apps to the App Store and Google Play under the client's own listing, so what an attendee downloads is your app rather than a container they have to search inside.
What this looks like in the product
The theme an organizer sets in the console flows through every screen the attendee sees.
- Theme editor
- Logo, splash, primary and accent colours and typography, applied to every screen from one console page.
- Store publication
- A separate App Store and Google Play listing under your own name, not a container app.
- Browser event site
- The same event in a browser for attendees who will not install anything.
- Per-event feature switches
- Photos, Q&A, polls, chat and the directory turn on and off per event.
- Role-based access
- Platform staff, organisation super-admins, organisation admins and per-event moderators.
Your app, first launch
- Your logo on the splash screen
- Your brand colours on every tab
- Your typography in headings and body
- Four tabs: Schedule, Connect, Photos, Me
- Store listing under your own name
Branded, white-label and container apps are three different things
These three terms get used as synonyms in vendor copy, and they are not synonyms. The distinction decides what your attendees type into the App Store search box, which is the only part of this that they will ever notice.
A container app is one app in the store, owned by the vendor, holding hundreds of events. Attendees download the vendor's app and then find your event inside it with a code. A branded app is a separate store listing under your organisation's name, with your icon on the home screen. White-label is the commercial arrangement that makes a branded app possible: the vendor's software, published without the vendor's identity attached to it.
So branded describes what the attendee sees, and white-label describes whose name is on the paperwork. event67 does both at once. There is no event67 container app for attendees to find first.
| Shape | What the attendee searches for | Whose name is on the listing |
|---|---|---|
| Container app | The vendor's app, then your event code | The vendor |
| Branded app | Your organisation or your event | Yours |
| Web only | A link you send them | Your domain or the vendor's |
event67 also serves a browser event site for people who will not install anything, which is a meaningful share of any audience over about 300 people. The web version is not a lesser tier with features stripped out of it; it is the same event, and an attendee can move between the app and the browser without losing their agenda.
What launching a branded app actually involves
Two of these four steps are yours and take an afternoon. Two are Apple's and Google's, and their clocks are the reason branded apps get quoted in weeks rather than days.
You set the theme in the console
Logo, brand colours, typography. The theme editor previews every screen as you change it and runs a WCAG AA contrast check on each colour pair, which warns you and asks you to confirm rather than blocking the save.
We build your store listings
App name, icon, subtitle, description, screenshots and the privacy labels, prepared against your brand rather than a template with your logo dropped in.
Apple and Google review the build
This is the step nobody controls. App Review turns most builds around inside a couple of days; Google Play is usually faster. A first submission from a brand-new developer account takes longer than a resubmission.
Your app is live and your invites go out
Bulk invite your list by CSV. Each invite carries a claim link, and the app is already in the store when the attendee taps it.
The honest schedule: plan on two to three weeks between deciding to launch and having a live store listing, and make sure whoever owns your Apple Developer account can act on a review question the same day. The build is not the long pole. The account paperwork is.
- app store listings published under your own name
- 2app store listings published under your own name
- realistic time from decision to a live store listing
- 2–3 weeksrealistic time from decision to a live store listing
- code you write, build, or receive
- 0code you write, build, or receive
What the organizer controls
- The theme
- Logo, splash screen, primary and accent colours, and typography, set once and applied everywhere. Change it mid-event and attendees see the change without updating the app.
- The store identity
- App name, icon and listing copy sit under your organisation's developer account or ours, whichever you prefer. Under yours, the app is unambiguously yours and stays yours.
- Which features are on
- Photos, Q&A, polls, chat, the attendee directory and the connection features are switched per event. A board meeting that wants a schedule and nothing else can have exactly that.
- Who can see what
- Attendee visibility is a per-person setting, and the organizer sets the default. Roles run from platform staff through organisation super-admin and organisation admin to per-event moderator.
What a branded event67 app will not do
Branded does not mean bespoke. You are getting event67's product wearing your identity, which is what makes it cost what it costs and ship when it ships.
- No custom screens or custom features built for one client. The layout is the layout.
- No ticketing or payments. event67 does not sell your tickets, so registration stays wherever it is today and you import the resulting list.
- No streaming, no virtual booths, no on-demand video library.
- No exhibitor lead capture and no badge scanning with a CRM sync. The QR in this product connects two attendees to each other.
- No badge printing, and no interactive floor plan or wayfinding.
- No source code handover. You get a published app and a console, not a repository.
If a bid requires abstract management, continuing-education credit tracking or a call for papers, event67 is not the answer to that bid, and we would rather you find that out on this page than in a demo.
Who a branded app is worth it for
A branded app earns its keep when the app itself is part of how the event is experienced rather than a utility bolted to the side of it. Three situations where that is reliably true:
- A recurring flagship conference, where the same attendees return each year and the icon staying on their phone between events is worth more than the download it saves.
- An internal event at a company with strong brand governance, where shipping staff into a third party's app is the objection that kills the purchase.
- An agency running events for several clients, where each client expects to see their own name and not the agency's stack.
It is worth less for a one-off event under about a hundred people, where the browser event site does the same job with nothing to install and nothing to review.
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
Is a branded event app the same as a white-label event app?
Nearly, and the difference is who the word describes. Branded is about the attendee: the app carries your name, icon and colours. White-label is about the contract: the vendor licenses you their software without their identity on it. A white-label arrangement is what produces a branded app, so a product can be white-label and still ship inside a vendor container if it is set up badly. event67 publishes a separate store listing, so both words are true here in the way buyers mean them.
Do attendees have to download the branded app?
No. Every event67 event also has a browser event site with the schedule, speakers and forms, so someone who will not install an app still gets the event. The app is where the live features live, so the people who install it get more, but nobody is locked out for refusing.
How long does it take to launch a branded event app?
Plan on two to three weeks. The theme and the console setup are an afternoon. The store review queues at Apple and Google are the part with a clock you do not control, and a first submission from a brand-new developer account is slower than a resubmission from an established one. If your event is closer than that, launch on the browser event site and add the branded app for the next one.
Is a white-label event app worth the cost?
It depends entirely on whether the price is per-app or per-attendee. Agencies that quote a branded app as a build charge you for software you do not keep. event67 charges per activated attendee: your first 50 are free on every event, each one after that is $5, and one event can never cost more than $4,750 no matter how many people turn up. The branding is not a line item.
Whose developer account is the app published under?
Either. Under yours, the listing is your property and stays with you if you ever leave. Under ours, you skip the account setup and the annual fee. Most first-time organizers start under ours and move later; a company with an existing developer account should use it.
Can we change the branding after the app is live?
Colours, logo, typography and content, yes, immediately, without a new build or a store review, because the theme is served from the backend and the app picks it up. The app's name and icon in the store are a store listing change and need a resubmission.
Keep reading
Features this depends on
Event types that lean on this
See it in your own event
Your first 50 attendees are free on every event, so the smallest version of this costs nothing to try.