Scenario Notification Detail View
Component Detail
Description
Read-only detail screen surfaced when a user taps a scenario notification from the notification centre or a push alert. Shows the scenario context (e.g. days since last activity, certification expiry date) and a primary call-to-action button that deep-links to the relevant workflow.
scenario-notification-detail-view
Summaries
The Scenario Notification Detail View is the moment of truth for scenario-based notifications — the screen where a peer mentor moves from awareness to action. By presenting the full context of a notification (such as days since last activity or certification expiry date) alongside a clear call-to-action, this screen directly converts notification delivery into meaningful platform engagement. Without this detail view, notifications become dead ends that frustrate users and reduce the credibility of the alert system. A well-executed detail view increases the likelihood that mentors complete the intended workflow, driving programme outcomes such as re-engagement rates, certification renewals, and milestone progression that the organisation can report to stakeholders.
The Scenario Notification Detail View is a low-complexity mobile screen with two dependencies: scenario-deep-link-router for CTA navigation and scenario-notification-repository for fetching and marking notification data. It is a consumer-only screen with no data creation responsibilities, which keeps its scope contained. Key delivery coordination points are: the scenario-notification-repository must expose both `loadNotification` and `markAsRead` before this screen can be tested end-to-end, and the scenario-deep-link-router must have registered routes for all CTA destination screens. Testing must cover the mark-as-read side effect on load and the deep-link navigation for each scenario type.
Accessibility review should confirm that contextual data (e.g. expiry dates) is read correctly by screen readers.
The Scenario Notification Detail View is a read-only mobile screen backed by the `push_notification` data model. It exposes three interfaces: `loadNotification(notificationId)` fetches the full notification record from scenario-notification-repository on mount and populates contextual display fields (scenario type, message, contextual data such as days-since-activity or expiry date); `markAsRead(notificationId)` is called immediately after successful load to update read status in the backend; and `navigateToCta(deepLinkRoute)` delegates to scenario-deep-link-router when the primary CTA button is tapped. The screen has no edit state — all fields are display-only. Contextual data fields should be rendered from a typed map keyed by scenario type to ensure type safety.
Error handling must cover not-found and already-deleted notification states gracefully, redirecting back to the notification centre if the record no longer exists.
Responsibilities
- Display full notification message with contextual data
- Render primary CTA button linking to the relevant in-app screen
- Mark notification as read on view
Interfaces
loadNotification(notificationId)
markAsRead(notificationId)
navigateToCta(deepLinkRoute)
Relationships
Dependencies (2)
Components this component depends on