Push Notifications
Feature Detail
Description
Push Notifications delivers real-time alerts to peer mentors and coordinators on their mobile devices for time-sensitive events such as new assignments, activity reminders, and coordinator messages. The feature integrates with platform-native push services (APNs for iOS, FCM for Android) to ensure reliable delivery across both mobile platforms. Notifications are stored in a persistent inbox so users can review past alerts even after dismissing the banner.
Sources & reasoning
Blueprint marks push-notifications [MVP]. The HLF section of likeperson.md explicitly cites scenario-based push messages as a direct solution to the 40% follow-up dissatisfaction rate. As the foundational delivery channel for all downstream notification features, MVP placement is required.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Push notifications are essential for an operational tool used by volunteers who may not open the app proactively. Timely alerts for new assignments, approval requests, and follow-up reminders directly address the 40% dissatisfaction rate with peer mentor follow-up identified in HLF's internal survey. For coordinators managing multiple peer mentors, push alerts about pending approvals and overdue activities improve oversight without requiring constant manual checking. This feature is foundational for all scenario-based notification workflows in later phases and cannot be deferred without breaking coordinator responsiveness.
Implement using Flutter firebase_messaging package for FCM (Android) and APNs (iOS). Backend issues push payloads via Firebase Admin SDK. Device tokens are stored per user-device pair and refreshed silently on each login. The notifications table stores all delivered notifications with read/unread status powering the inbox screen. WCAG 2.2 AA compliance requires notification banners to have sufficient color contrast and screen-reader-accessible labels on all interactive elements. Background and terminated-app message handling must be verified on both platforms before release.
Components (43)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.