Talking Cards Toolbox
Feature Detail
Description
The Talking Cards Toolbox provides peer mentors with a browsable collection of conversation-starter cards to facilitate structured discussions with contacts. Cards are organized by theme and available offline, reducing cognitive burden during home visits or phone calls. The feature serves all four organizations and is built with WCAG 2.2 AA compliance, ensuring accessibility for peer mentors with varying digital skill levels and accessibility needs.
Sources & reasoning
All four organizations endorsed Talking Cards in the §4 priority matrix (NICE, Phase 3). Phase 3 maps to v1.1 by ordinal position. The feature is explicitly listed in both the Fase 3 development roadmap (§5) and the Fase 3 action items (§7), and it appears in the canonical area taxonomy (§8) as the sole feature of conversation-tools.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Talking Cards addresses conversation quality - a concern across all four organizations - by giving peer mentors ready-made prompts for sensitive discussions. This lowers the barrier for new and less experienced peer mentors and leads to more consistent, higher-quality support interactions for contacts. It also adds daily-use value beyond registration tasks, keeping peer mentors engaged with the app between activity logging sessions. All four organizations endorsed the feature in the priority matrix despite its NICE classification, confirming broad appeal. The low implementation cost relative to engagement benefit makes it an attractive Phase 3 addition once core operational features are stable.
Built in Flutter as a scrollable card browser backed by Drift for offline storage. Cards have title, body text, optional image, and theme tags; a versioned backend endpoint syncs the catalogue to clients without requiring an app release. Riverpod providers manage card collection and filter state. The module registers under the conversation-tools area ID for per-organization toggling via the Feature Toggles admin surface. WCAG 2.2 AA compliance requires semantic labels on all card elements, adequate contrast ratios, and minimum 24x24 touch targets. No user-generated writes are involved - only periodic read syncs - keeping the feature stateless and low-maintenance after initial build.
Components (46)
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.