Why We Built the Society Announcement Feed

The WhatsApp trap nobody wanted to admit

Here's the thing about university Christian groups: they are deeply fragmented by design. A single campus might have three, four, or even six different societies. A student might be in the main Christian Union, a prayer circle, a weekly Bible study, a mission group, and a worship band. Each has its own group chat.

When we first built Campus Fellowship, we thought the events calendar would be the glue. Students would check the app, see what's on, show up. Simple. But three months in, campus leaders told us something we hadn't anticipated: the calendar isn't where announcements live. Announcements still live in WhatsApp, because WhatsApp reaches people. An event needs a poster, a date, an RSVP link, yes. But it also needs a last-minute reschedule notice. A speaker cancellation. A location change. A room code that leaked to the wrong group chat. A 'bring a friend' reminder on the morning it happens.

We watched one group's group chat. Fourteen hundred messages in a month. Three of those were calendar link clicks. The rest were noise masking news.

What the feedback was really asking for

When campus leaders asked for 'announcements,' we initially thought they wanted a notification system bolted onto the events feature. A way to broadcast a message to all members at once. We sketched that out. It looked tidy. Clean. Wrong.

Then someone asked a better question: 'What if different societies on the same campus could announce things, and students could choose which ones they follow?'

That question changed everything. Because on a campus with five Christian groups, a student might join the main CU events, but only follow Bible study announcements and prayer requests. The societies themselves control what they post. There's no central moderator deciding which groups deserve visibility. The feed becomes a commons where each group has a voice.

That's different from a general announcement board, which tends to collapse into clutter within weeks. It's different from notifications, which students mute. It's a feed of announcements from communities the student has already chosen to know about. The friction is lower than checking WhatsApp or email, but the authority is higher because it comes from the groups themselves.

Launch week taught us where the real friction lives

We rolled out the announcement feed to a small group of campuses in late September. Fourteen groups across three universities. We expected adoption to be immediate. Instead, the first week was quiet.

Then the messages arrived. Not complaints, exactly. More like clarifications. Group leaders told us: 'We love this, but can we schedule announcements in advance?' Another: 'Can members see when an announcement was edited?' Another: 'What happens if two groups announce the same event?'

The third question was the insightful one. Two separate prayer groups announced the same corporate prayer evening. Students saw it twice. It wasn't wrong, but it made the feed feel cluttered. That's when we realised the announcement feed isn't just infrastructure; it's a small cultural tool. It asks groups to think about what's announcement-worthy versus what's just coordination noise. It asks whether they should co-post with a partner group or post separately. It makes visibility a choice, not a broadcast.

We added scheduling and edit history. That felt technical. But the real work was watching how groups used the feed and letting them teach us what it should be.

Why announcements matter more than you think

This is probably worth stating plainly: the announcement feed isn't the flagship feature of Campus Fellowship. Events matter more. Prayer requests matter more to many groups. But announcements do something the others don't. They keep a community from fracturing into parallel conversations.

A prayer group can thrive on a private forum. An event can be posted anywhere. But announcements are the connective tissue. A speaker is coming to town. The prayer meeting time is changing. New members are welcome. Bring your parents to our service next month. These aren't small things. They're how groups stay coherent as membership turns over every year.

And because the app works on campus level, a student following multiple societies sees one feed, not five separate feeds. They're not thinking, 'I should check the CU WhatsApp, then the Bible study WhatsApp, then the prayer group chat.' They open Campus Fellowship and see what's happening across their Christian community in one place.

What we got wrong before we got it right

Honestly, we built too much at first. We wanted to add image upload, rich formatting, scheduling, digest emails, the works. We also wanted to make announcements searchable, tagged, archived, probably filtereable by category. It took a campus chaplain pointing out the obvious: 'Just let us post text and a link. That's it. Fast. Simple. No friction.' She was right. The feature is better for being simpler.

We also assumed group leaders would treat announcements like formal communications. They don't. Some groups post multiple times a week. Others post once a semester. Some are casual. Others are polished. The feed doesn't impose a tone. It just carries the voice of whoever's managing that group's presence on any given day.

A quiet feature that stops a quiet crisis

One of the stranger things about building software for universities is how fast information decay sets in. A student hears about a prayer meeting from a friend, shows up, and realizes it was cancelled three days ago. Someone misses a signup deadline because the change was announced in a group chat that loaded as unread. People stop trusting information because it's always either missing or buried.

The announcement feed doesn't solve that with noise. It solves it with clarity. One voice per community. One place to check. No parallel ecosystems.

A theology student from Edinburgh messaged us last month. She said: 'My mate was in the CU but kept missing events because he wasn't on the group chat. Now he checks the app. He's to three meetings in a row.' That's the actual job of the feature. Not to make announcements fancier or louder. Just to move them somewhere students already look.