Developing a Mobile App for a Religious Community
An app for a religious community is first and foremost a communication and content access tool: service schedule, sermon media library, community chat, and donation capability. The audience varies widely by age, so UX must be simple and the app must work on older devices without degradation.
Schedule and Notifications
Service schedule is a calendar with recurring events and exceptions. Local copy in Core Data (iOS) or Room (Android) synced on launch. Recurring events use iCalendar RRULE semantics—store as rule + exception list rather than N separate records.
Push notifications one hour before service via FCM or APNs. Client also uses local notifications via UNUserNotificationCenter (iOS) or AlarmManager + NotificationCompat (Android) as backup for users without stable internet.
Sermon Media Library
Audio and video sermons are core content. Video via HLS from CDN (AVPlayer with AVAsset(url: m3u8URL)), audio via AVAudioPlayer or AVPlayer depending on format. Background audio is essential—users listen during commutes.
Background audio on iOS: AVAudioSession with .playback category, UIBackgroundModes: audio in Info.plist, MPRemoteCommandCenter for Control Center and AirPods control (play/pause, next, seek). Without MPRemoteCommandCenter—system player notification won't show, AirPods won't manage playback.
Android: MediaSessionCompat + MediaBrowserServiceCompat + notification with MediaStyle. ExoPlayer in ForegroundService for background playback. PlayerNotificationManager from ExoPlayer auto-creates media notification with controls.
Sermon search: full-text via API. Filter by speaker, date, series. Offline access for downloaded materials—save in FileManager (iOS) or getExternalFilesDir() (Android).
Community Chat
General chat via third-party SDK (Stream Chat, SendBird) or WebSocket-based implementation. For small communities (up to 500 people), ready-made SDKs with freemium models are better for development time. Stream Chat SDK provides ready UI—ChatChannelVC / ChannelListFragment—customizable.
Content moderation—admin and moderator roles. Delete messages, block users. Required for religious community.
Donations
Built-in donation collection is most regulated. iOS forbids custom payment forms for digital goods without StoreKit. But donations for NGOs/religious organizations aren't digital content purchases, so WebView with external payment form (Stripe, PayPal) is allowed. State this explicitly in app purpose during review—otherwise risk rejection per guideline 3.1.1.
Android has fewer restrictions—native Stripe SDK (com.stripe:stripe-android) with PaymentSheet provides ready UI for card entry.
Recurring donations—subscriptions via Stripe Billing. Manage from app: cancel, change amount.
Supporting Older Devices
Minimum iOS 14 (covers >95% active devices in 2025). Android minimum API 26 (Android 8). iOS 14 lacks AsyncImage—use Kingfisher. Without @Observable (iOS 17)—use ObservableObject + @Published.
Font: Dynamic Type (UIFont.preferredFont(forTextStyle:), sp units on Android). Elderly users often increase system font size—app must respond correctly without text overflow.
Timeline
Schedule + media library with background audio + push: 4–6 weeks. Chat + donations + offline: 2–3 months. Pricing calculated after requirements analysis.