Why we built cross-society discovery on the same campus

The loneliness of being one voice in a crowd

University campuses are strange places. Thousands of students, but you might never find your people. A student at Edinburgh told me she'd been to her Christian Union for a term before discovering there was a separate Bible study group meeting in the library. No one had mentioned it. It wasn't secret; it just wasn't visible to her.

When we first launched Campus Fellowship, we focused on the essentials: events calendar, prayer requests, announcements. We made it easy for student leaders to post. Students could sign up, see what was happening. Good. But we were still thinking of Campus Fellowship as a noticeboard for a single society.

The real problem was lonelier than that. A student might feel alone in their interest. Maybe they wanted to explore faith through art and philosophy. Maybe they'd just moved from a different country and wanted to meet other Christians from their background. Maybe they were wrestling with something specific and wanted to find a smaller group. Campus Fellowship wasn't helping them find each other across the different groups and societies on the same campus.

The moment we stopped thinking like a single-group app

We were in our second month of university testing. We'd sent Campus Fellowship to about fifteen Christian Unions across the UK and US. The feedback started to cluster around the same thing. Not 'add more features'. Not 'make it prettier'. But 'we want students to discover what else is happening on campus. People are going to five different WhatsApp groups to stay in the loop.'

One chaplain at a US college told us straight: 'You're solving one problem really well. But campuses have multiple faith communities. If you only see your own society's calendar, you're missing something important about what fellowship actually means.'

That was the turning point. We realised Campus Fellowship needed to be a window onto the whole Christian ecosystem on a campus, not just one corner of it. Not a generic discovery app, though. It had to stay specific. These weren't random student groups; they were Christian communities. Prayer groups. Bible studies. Events run by chaplains, by CUs, by course-specific fellowships, by student-led ministries.

Building discovery that doesn't feel like a directory

Cross-society discovery sounds like a nice feature in a roadmap. In reality, it was harder than it looked. We couldn't just make a list of every group on campus and call it discovery. That's a directory. Useful, maybe, but not the same thing as actually helping someone find their people.

What we needed was for each society to stay independent (run their own events, prayer boards, announcements, member lists) but for students to see across the campus. To know that if their CU has a prayer group, there's also a justice-focused Bible study three buildings away. To notice when a chaplaincy is running something alongside their society's event. To find a smaller study group if the main event feels too big.

The technical challenge was real. We're pulling information from multiple groups on the same campus, but keeping each one's identity. Different leaders, different tones, different focuses. One CU might be more liturgical; another charismatic; a third academic. A student should be able to see all three without the app flattening them into 'just another church thing'.

We built the campus event calendar to show every event across every society, with RSVP built in. We made sure the Bible study group manager could work at scale. The society announcement feed lets students see what's actually being talked about across the campus, not just in their own group's chat. And the member directory, which sounds simple, became something more interesting. A student can see who else is around, and find someone else in their course who shares the same faith community.

What changed when we got it right

We tested the cross-society discovery feature at a large US university with five different Christian groups. I spent a day listening to student feedback. One student said something that stuck: 'I thought I was the only one who cared about this. Turns out there are twelve of us meeting in a different room.'

That's not just a feature working. That's isolation ending.

Another shift happened with leaders. A CU president realised she could see what a campus ministry was doing, coordinate better, avoid accidental clashes. She started going to prayer meetings she hadn't known existed. The chaplain felt less lonely too. He wasn't the only adult working across the whole campus; there were student leaders he could support, and other communities he could learn from.

The discovery wasn't about competition. It was about belonging. Campus Fellowship became a place where a student could feel the actual scope of Christian community on their campus. That's different from 'here are some churches nearby'. It's more specific. It's about your campus, your peers, your generation.

Why this matters for how we'll keep building

We could have stayed narrow. Campus Fellowship for your CU, Campus Fellowship for your prayer group. Useful enough. But we'd have missed something important about university life. Faith communities aren't isolated atoms. They're connected. A student doesn't experience Christianity on campus through one lens; they experience it through multiple encounters, multiple leaders, multiple groups. Sometimes the biggest thing that happens is finding the group that fits them best, not the one they happened to join first.

Building cross-society discovery taught us that Campus Fellowship works best when it acknowledges the whole ecosystem. When a chaplain can see what student leaders are doing. When a student who's been at the edge of a group can finally find a smaller space that fits them. When communities know they're not alone on campus.

It's why Campus Fellowship is built specifically for campuses with multiple Christian communities, not as a generic tool that happens to work for churches. The discovery matters because the campus context matters.