🏠 Overview › 🎯 Features ›🎯 Push Notifications

Push Notifications

Feature Detail

medium complexity extracted Notifications Confidence: 100%
4
Components
4
Shared
0
User Stories
Yes
Analyzed

Description

Push notifications deliver real-time alerts to peer mentors and coordinators on their mobile devices for activity follow-ups, assignment arrivals, and platform events. A dedicated inbox screen lets users review and act on past notifications, with unread counts surfaced in the bottom navigation tab. The system supports foreground (in-app banners) and background delivery with offline queuing via the Drift local database, ensuring no alert is lost when connectivity is unavailable.

Sources & reasoning

Line 181 lists push notifications as a core always-available Mobile App capability, confirming MVP scope. Line 116 (HLF Phase 2) cites scenario-based push messages, but the base delivery infrastructure is required from launch. Line 298 confirms the inbox screen. Blueprint marks this [MVP].

  • docs/source/likeperson.md · line 181
    Push notifications and assignment tracking
  • docs/source/likeperson.md · line 116
    Scenariobaserte push-meldinger og kalendersynkronisering.
  • docs/source/likeperson.md · line 298
    Notification inbox

Analysis

Business Value

Push notifications are the primary channel for time-sensitive operational communication across a distributed volunteer network. Coordinators depend on alerts to action follow-ups promptly without manual polling of screens. HLF reported 40% dissatisfaction with peer mentor follow-up quality; reliable push delivery directly addresses this gap. The inbox provides a persistent audit trail of received alerts supporting accountability. For organizations managing hundreds of peer mentors, push notifications reduce coordinator workload by surfacing the right information at the right moment, improving overall program quality.

Implementation Notes

PushDeliveryProvider abstracts APNs (iOS) and FCM (Android) behind a single interface, enabling future provider swaps without changing consumers. Device tokens are registered and refreshed at app startup via AuthService. The Next.js backend issues notification payloads and persists records in NotificationRepository for inbox rendering. Offline-first: unread counts and notification records are cached in Drift so the inbox loads without connectivity. All notification UI elements must carry semantic labels and screen-reader-compatible announcements to satisfy WCAG 2.2 AA requirements.

Components (8)

User Interface (1)

ui NotificationInboxScreen medium

Service Layer (1)

service PushNotificationService medium

Data Layer (1)

data NotificationRepository medium

Infrastructure (1)

infrastructure PushDeliveryProvider medium

Shared Components

These components are reused across multiple features

User Stories

No user stories have been generated for this feature yet.