Featured Project · Event Tech
Eventify
A white-label event app platform we built for organisers who didn't want to babysit a CMS for every conference. iOS, Android and a web admin — all of it ours.
Visit eventify.io
A white-label event app platform we built for organisers who didn't want to babysit a CMS for every conference. iOS, Android and a web admin — all of it ours.
Visit eventify.io
Eventify came to us with a problem most event tech founders run into eventually: every event needs a slightly different app. Branding changes, the agenda changes, sponsors change, sometimes even the language changes. Spinning up a fresh app for every conference doesn't scale. They needed one platform that an event organiser could log into, configure in an afternoon, and ship to the App Store and Play Store under their own brand.
We'd seen variations of this problem before, but Eventify wanted to push it further — they wanted full multi-tenant white-labelling, deep customisation of the agenda, attendee networking, exhibitor booths, sponsor tiers, lead capture, push notifications by track, and a check-in flow that worked offline. All of that, configured from one admin panel.
The platform is split across three things that actually need to talk to each other constantly. The mobile app (one codebase per platform — native Swift and Kotlin, not a wrapper), the admin web app where the organiser configures everything, and the API layer that ties them together. Honestly, the API was where we spent the most time. Real-time agenda changes, attendee imports of 5000+ people, session check-ins streaming in from a dozen scanners at once — it has to be fast and it can never lose a record.
The full feature set keeps growing — the team at Eventify ships almost every week, and we still help with the heavy mobile work and the harder API problems.
I'll be honest about a few things that didn't work the first time, because the rest of the case studies on the internet make every project sound like it shipped on rails.
The first version of the QR check-in worked beautifully in the office and fell over at a 4000-person conference because everyone scanned in within a 30-minute window. We'd built the scanner to confirm with the server before flipping a UI state to "checked in", which sounded safe but pushed the API into a queue death-spiral. We rewrote it to do an optimistic local check-in, then reconcile with the server in the background — and added an idempotency key so duplicate scans don't double-count. That was the second rewrite. The third one made it work fully offline and then catch up on reconnect.
White-label apps complicate push notifications. We had to make sure a notification scheduled for "ACME Conference 2024" never reached an attendee of a different event running on the same backend. We put each event into its own topic, scoped device tokens by tenant + event, and added a server-side guard that rejects any send not scoped to a tenant. Boring, but the kind of thing where one mistake means a very awkward Monday.
Organisers move sessions around constantly — speaker shows up late, a room gets switched, a track gets renamed at 8am. We started with pull-on-foreground and got complaints. Switched to WebSocket fan-out for the duration of an event window, which is on a per-tenant basis. It cost us some infrastructure complexity but cut "where's the session?" support tickets to almost zero.
We picked native iOS and Android over cross-platform deliberately. Eventify needs to feel premium because it's resold to enterprise organisers, and a slow tab transition or a janky scanner loses contracts. The admin is a React SPA. The API runs on Node with PostgreSQL for transactional data and Redis for the realtime layer. It's hosted on AWS with multi-region failover, which has earned its keep more than once during a live event.
Eventify is currently used at conferences, trade shows, exhibitions, hybrid summits and a fair number of internal corporate events that nobody outside the company will ever hear of. The platform handles event sizes from a few hundred attendees up into the tens of thousands. The admin lets a one-person events team launch a fully branded, fully-featured app in a day or two — which used to take a month with traditional event-app vendors.
If you run events and you've been frustrated by stitching together five different vendors for registration, app, networking and check-in, take a look at eventify.io. They have a free demo and the team is good at responding to questions.
This isn't a "delivered and walked away" project. We're still on the team for the harder mobile work and the parts of the API that need careful handling around concurrency and data integrity. New features go through a small RAD-style spec round before we touch the code, the same way we run all our long-running engagements. Nothing fancy — just the old discipline of figuring out what you're building before you build it.
If you're building a B2B SaaS product that needs a serious mobile experience — multi-tenant, white-label, offline-tolerant, the kind of thing where the app can't go down on launch day — that's our wheelhouse. Drop us a note and we'll talk about it. Get a free quote here, or just email [email protected]. No deck, no sales call required to start.