Your Conference, Branded Your Way, in Every Attendee's Pocket
A mobile conference app that takes on your event's identity, caches the full programme on the device, and gives you a choice between two distribution models depending on scope.
Two Ways to Publish Your Event
Pick the distribution model that fits your scope, timeline, and branding budget.
Featured inside HEPCon
Default — fastest path
- Live in 48 hours from your agenda export
- Themable per event: your colours, logo, splash, cover image, sponsor placements
- Attendees install HEPCon once and find your conference listed inside
- No app-store review delays
- Included in the Pro plan
White-label standalone app
Enterprise — full custom branding
- Your own app on the App Store and Google Play under your organisation's name
- Custom app icon, splash screen, store-listing text and screenshots
- Apple and Google review timelines add roughly 1–3 weeks — plan accordingly
- Same offline-first engine and same backend as the standard app
- Enterprise tier add-on
Most events start with the featured-inside-HEPCon route and upgrade to white-label for the next edition once they see attendee engagement numbers.
Branded for Your Event, Inside the HEPCon App
Set your visual identity once. Every attendee opening the event sees your branding — not a generic HEPCon shell.
What gets themed per event
- Primary and secondary brand colours — drive buttons, accents, headers, and active-state indicators
- Event logo — surfaces on the home card and navigation chrome
- Cover and splash image — 1600 × 800 recommended for the home hero
- Sponsor tier placements — logos render inline with the programme, ordered by tier
- Optional: custom event hashtag, external website link, code of conduct copy
What the attendee sees
An attendee at your event opens HEPCon and lands on your event's home screen — your colours, your logo, your cover image. No HEPCon-branded loading screen between them and your programme. The visual context says "you're at this event".
When several organisations run events on the platform, each event keeps its own identity. An attendee with three events in their list sees three distinct visual experiences as they switch between them — not a generic chrome with different titles.
Offline-First, Properly
Network round-trips happen only when something has actually changed. Everything else lives on the device.
First open: full sync
The entire programme — sessions, abstracts, speakers, rooms, sponsors, maps — downloads into a local database. Typical sync time: a few seconds, regardless of how large the programme is.
Every subsequent open: instant
The app reads from the local cache first. "Today" appears in milliseconds; search is instant; abstracts open without a spinner. No network dependency for the core experience — only for delta updates.
Updates: deltas only
When a session moves or a speaker substitutes, the app fetches only the delta — typically a few hundred bytes, not the full programme. Network failure mid-update leaves the cached state intact and usable.
Where the Backend Lives
Honest about what's globally distributed and what isn't.
Static assets, served from edge locations worldwide
App-store binaries, branding images, splash screens, sponsor logos, and supporting static content are served from Google Cloud's global CDN. The response comes from the closest edge node to the attendee — whether they're in Sydney, São Paulo, or Stockholm.
Application data in Frankfurt (EU, GDPR)
Programme data, attendee favourites, and event configuration live in a single EU region: Frankfurt. This is intentional. Many European academic societies and medical organisations require EU data residency for GDPR compliance, and the single-region design makes that contractually clean.
Authentication, global
Sign-in flows (anonymous, ORCID, LinkedIn) route through the identity provider's global infrastructure, so login latency stays in the 100–200 ms range regardless of where the attendee is sitting.
Real-time interactions
Live features (Q&A posting, mic queue, real-time polls) hit the Frankfurt region. For an attendee in Australia or Asia, that adds roughly half a second of latency versus a European attendee. Acceptable for typed Q&A; not noticeable for browsing because browsing is local-cache.
Working on a specific kind of conference?
Each vertical has its own framing of the same mobile app, tuned to the audience.
Trusted by many
multiple major conferences • 10,000+ attendees
See Your Conference in the Mobile App
Send us a sample export from Indico, ConfTool, EasyChair, or a spreadsheet. We will build a working preview branded for your event within 1–2 business days.
Request a Custom Preview Talk About White-Label