Three Platforms, One Problem: Why Gathrd Lives on iOS, Android, and the Web

The moment we realised a website wasn't enough

When we first launched Gathrd, we thought getgathrd.app would be the main hub. It's a beautiful discovery site. You can filter by denomination, search by postcode, see what's on this weekend. For church staff uploading events, it works. They're often on a desktop or tablet, planning ahead, adding details methodically.

But we kept hearing from attendees: 'I found your site once, but I can't remember the URL.' Or: 'I was in town yesterday and wanted to check what was on, but I didn't think to look it up.' The friction was real. Discovery happened in the moment. Someone finishes work on a Friday and thinks, 'What's on tonight near me?' They're holding their phone. They're not typing a URL into a browser. They're opening an app.

That's when we knew. One platform wasn't enough. We needed to meet people where they already lived: on their home screen.

iOS and Android aren't just mirrors of the website

This is the part that took the longest to get right. We could have just wrapped the website in a mobile shell, pushed it to the App Store, called it done. Plenty of platforms do that. But the use cases are genuinely different.

On the iOS and Android apps, you get location-based discovery. Open the app, allow location, and you see what's happening within five miles of you. Right now. No typing, no filtering unless you want to. For someone new to an area, or someone who just wants to know what's on tonight, that's transformative.

The other thing apps handle better: offline readiness. We built the door check-in with QR codes (integrated with NFC via TapTrust for churches that want to go further). That only works if the person checking you in has a reliable offline mode. An app does that. A mobile website, even a very good one, doesn't.

And there's the notification layer. If you're interested in a particular church's events, or you've bookmarked a retreat happening in three months, the apps can remind you. Not spam. Just useful nudges. The website can't do that without asking you to opt into browser notifications, which is a friction point most people never get past.

Why we didn't choose one platform

iOS or Android. We could have shipped one and come back to the other later. It would have been faster, cheaper, easier to maintain.

But here's what we learned from talking to churches: your congregation uses both. One person's got an iPhone, their neighbour's got a Pixel. A young family might have an iPad and two Androids. A church in rural Wales discovered Gathrd through the website, but half their tech-forward volunteers needed the Android app because that's what they actually carry.

We also can't ignore the maths. In the UK, iPhone users skew toward certain regions and age groups. Android reaches others. If we'd picked one, we'd have built a platform that worked brilliantly for half our audience and not at all for the other half. That felt wrong for something meant to serve the whole church.

So we bit the bullet. Two native apps. Different teams. Different testing. Different launch cycles. Yes, it's more work. But it means a Baptist church in Glasgow can use iOS, and their sister church in Belfast can use Android, and both of them discover the same prayer meetings and conferences and community events without friction.

The discovery site isn't going anywhere

Here's the thing people sometimes miss: we didn't build apps to replace getgathrd.app. We built them alongside it.

The website is still how most churches find us. Someone Googles 'Christian event booking platform UK' and lands on our discovery site. They see denomination filtering, they see how it works, they understand that we're faith-only (no nightclubs disguised as worship events), and they sign up for the Church plan at £19.99 a month.

The website is also where someone deep in the details lives. You're planning a conference. You need to see the full attendee list, adjust pricing, set up Gift Aid splits for UK donors, check your Stripe Connect payouts across 37 countries with PPP discounts applied. You do that on getgathrd.app on a proper screen with a keyboard.

But for the person attending? For the mum in Sheffield who wants to know if there's a prayer meeting on a Wednesday night? For the young adult visiting family in London for the weekend? That's the app. That's the moment. That's where we meet them.

The choice reflects who we serve

This is maybe the real heart of it. Eventbrite can live as a website and a single app because it's serving a huge audience doing dozens of different things. A platform for rock concerts and corporate conferences and wedding expos can abstract away the differences.

We built Gathrd for a specific community doing specific things. Churches want to reach people who believe what they believe. Attendees want to find worship, community, prayer, connection. That specificity meant we could make a real choice about platform strategy.

Our Fee structure reflects that same thinking. We charge 3% on paid tickets across all platforms, all plans. Eventbrite charges 6.95% plus 59p per ticket. That difference compounds. A church running a weekend retreat with 80 attendees at £25 each saves hundreds of pounds on Gathrd. Those savings matter to churches operating on tight budgets. That's not a feature. That's a values decision baked in from the start.

And Gift Aid automation with split-checkout? That's only in Gathrd because we serve UK churches. No generic events platform would build that. But for a church treasurer reconciling donations, that feature alone justifies moving from wherever they were before.

What we learned along the way

That Manchester church administrator? She eventually found her way back to us through the app. She downloaded it, saw the event she needed (it wasn't cancelled; it had been moved to a new date), and everything sorted itself out. But she also told us something we didn't expect: having the app on her home screen meant she started seeing other events. She's now promoting three different conferences to her congregation.

We see that pattern across both platforms. The moment of discovery changes when the door is always open. Someone glances at a notification, or opens the app out of habit, or shares an event with a friend because it's literally one tap away. That's what you can't replicate with a website, no matter how well designed it is.

The platform choice isn't really about technology. It's about understanding how actual people use actual tools. If you're waiting for someone to remember a URL and type it in, you've already lost the moment. But if Gathrd is sitting on their home screen, alongside the messages app and the maps app and the weather app? Then you're there when they need you.