Implement Badge Icon Asset Manager
epic-achievement-badges-ui-task-004 — Build the badge-icon-asset-manager infrastructure component that maps badge definition icon keys to Flutter asset paths or network URLs. Implement preloading of badge icon assets for smooth UI rendering, handle missing icon fallbacks gracefully, and provide a typed API consumed by badge UI widgets.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 1 - 540 tasks
Can start after Tier 0 completes
Implementation Notes
Define BadgeIconSource as a sealed class with AssetBadgeIcon and NetworkBadgeIcon subtypes to enable exhaustive pattern matching in widgets. The icon manifest is a static Map
For network icons (future-proofing), validate URLs against an allowlist constant before creating a NetworkBadgeIcon. Register BadgeIconAssetManager as a Riverpod Provider so the badge shelf BLoC can access it. The resolveLabel method should return the badge displayName from BadgeDefinitionRepository as the accessibility label — avoid hardcoding strings in the asset manager. This ensures screen reader users of Blindeforbundet (who rely heavily on VoiceOver) get meaningful descriptions of each badge.
Testing Requirements
Unit tests using flutter_test. Test cases: (1) resolveIcon returns AssetBadgeIcon for an icon key present in the manifest, (2) resolveIcon returns a placeholder BadgeIconSource for an unknown key, (3) preloadIcons with an empty list completes successfully, (4) resolveLabel returns a non-empty string for known icon key and a generic fallback string for unknown key, (5) URL allowlist rejects a network URL from an untrusted domain. Widget test: BadgeShelfWidget renders placeholder for an unresolved icon key without throwing. Verify WCAG semantic labels are present on rendered icon images using the Flutter accessibility tester.
The badge-earned-celebration overlay must appear within 2 seconds of the triggering activity being saved, but badge evaluation runs server-side in an edge function triggered by a database webhook. Network latency, edge function cold start, and Supabase Realtime delivery delays could cause the overlay to appear late or not at all, breaking the motivational loop.
Mitigation & Contingency
Mitigation: Implement an optimistic UI path: after activity save, badge-bloc immediately checks whether any badge thresholds are crossed client-side using cached stats and badge definitions, showing the overlay speculatively before server confirmation. The server result then reconciles. Subscribe to Supabase Realtime on the earned_badges table for authoritative confirmation.
Contingency: If Realtime delivery is unreliable in production, add a polling fallback: badge-bloc polls for new earned badges 3 seconds after an activity save and shows the overlay if a new record is detected, accepting up to 5-second latency as a fallback SLA.
The celebration overlay uses animation for positive reinforcement, but motion sensitivity (prefers-reduced-motion) and screen reader users require a non-animated or text-only alternative. Failing to handle this risks excluding Blindeforbundet users or triggering vestibular discomfort for motion-sensitive volunteers.
Mitigation & Contingency
Mitigation: Check MediaQuery.disableAnimations in badge-earned-celebration-overlay and skip animation entirely when true, showing a static card instead. Add an ExcludeSemantics wrapper around the decorative animation widget and a separate Semantics node with a live region announcement of the badge name and congratulatory message.
Contingency: If accessibility issues are identified in TestFlight testing with Blindeforbundet's test group, fast-track a patch that defaults to the static card path and gates the animation behind a user preference setting in notification preferences.