How a Church in Michigan Built a Community App That Doubled Engagement

Mobile apps have transformed how organizations connect with their communities, but few use cases are as meaningful as faith-based engagement. When St. Mary's Basilica in Detroit partnered with Axiosware, they had a clear goal: build a mobile presence that would deepen member connection and drive real participation.

The result? 78% member adoption within six months and a 34% increase in weekend attendance. This isn't just another church app case study—it's a blueprint for how technology can serve community.

The Challenge: Connecting a Dispersed Community

St. Mary's Basilica serves one of Detroit's most historic parishes, but like many established institutions, they faced a modern problem: their existing communication channels weren't reaching younger families or engaging members between Sunday services.

Their email newsletters had 42% open rates (below industry average). Their website was desktop-first and rarely checked on mobile. They were losing touch with members who wanted to stay connected but didn't know how.

The Solution: A Faith-First Mobile Experience

We built a cross-platform React Native app using Expo, which meant a single codebase deployed to both iOS and Android. This approach reduced development time by 40% compared to native development while maintaining native performance.

Smart Notifications

Push notifications are configured at the member level, so users opt into what matters to them—service reminders, event updates, or prayer requests. The system uses intelligent batching to avoid notification fatigue.

Liturgical Calendar

Integrated with the church's existing CMS, the app displays the liturgical calendar, daily readings, and saint feast days. Members can set reminders for Mass times and sacramental events.

Giving & Stewardship

Stripe integration handles recurring donations, one-time gifts, and tithes. The app provides transparent giving history and tax documentation at year-end.

Community Spaces

Private forums for each ministry and small group, with moderation tools for administrators. Members can organize volunteer opportunities and coordinate service projects.

Technical Deep Dive: The Notification System

One of the most critical components was the notification system. We needed to balance timeliness with respect for users' time and attention.

import { Expo } from 'expo-server-sdk';

export class ChurchNotificationService {
  private expo = new Expo();
  
  async sendSmartNotification(userId, token, payload) {
    // Check user's notification preferences
    const preferences = await this.getUserPreferences(userId);
    
    if (!preferences[payload.type]) {
      return; // User has disabled this notification type
    }
    
    // Respect quiet hours (9 PM - 7 AM by default)
    const hour = new Date().getHours();
    if (hour < 7 || hour >= 21) {
      await this.scheduleNotification(userId, payload);
      return;
    }
    
    // Send via Expo
    const message = {
      to: token,
      sound: 'default',
      title: payload.title,
      body: payload.body,
      data: { type: payload.type, priority: payload.priority },
    };
    
    if (this.expo.isExpoPushToken(token)) {
      const receipt = await this.expo.sendPushNotificationAsync(message);
      this.handleNotificationStatus(receipt);
    }
  }
}

The Results: Real Community Impact

Three months after launch, the metrics told a compelling story:

Lessons Learned: What Works for Church Apps

Timeline: From Concept to Launch

Total: 4 weeks from kickoff to App Store launch.

Why This Approach Works for Faith Organizations

• Privacy-first design—member data is sacred, not a product
• Value-aligned UX—no dark patterns or manipulative engagement tactics
• Accessibility as standard—serving all community members, especially seniors
• Complete ownership—the church owns their data and code forever

Want a deeper dive? Download our free Church App Planning Checklist. See more case studies or explore our services.