Integrate ShareSheetBridge one-tap share button
epic-membership-recruitment-peer-mentor-ui-task-004 — Add a prominent one-tap share button on ReferralCodeScreen that invokes ShareSheetBridge with the referral link and a pre-composed Norwegian-language message. Handle platform share sheet responses and error states gracefully.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 3 - 413 tasks
Can start after Tier 2 completes
Implementation Notes
Use `Share.share(text, subject: ...)` from share_plus. Wrap the call in a try/catch for `PlatformException`. The pre-composed message should be a localized string constant — define it in your l10n/arb files as `referralShareMessage` with a `{url}` placeholder. Do not pass any subject parameter on Android as it is not universally supported across apps.
Keep the share payload minimal: referral URL + text only. The share button should use the app's primary button style to signal it is the primary CTA on this screen.
Testing Requirements
Write widget tests using flutter_test. Mock ShareSheetBridge to verify it is called with the correct URL and message string. Test (1) share button triggers ShareSheetBridge.share with correct arguments, (2) PlatformException results in error SnackBar, (3) button is disabled when provider is loading, (4) button is disabled when provider is in error state. On physical devices (iOS + Android), verify the native share sheet opens and the pre-composed message appears.
Include TestFlight testing to confirm iOS share sheet behavior.
QR codes rendered at the minimum 200×200 size may fail to scan under typical indoor lighting conditions on older or lower-resolution phone cameras, causing recruitment moments to fail when a peer mentor shows the screen to a prospective member.
Mitigation & Contingency
Mitigation: Set the default QR render size to 260×260 logical pixels (not the 200px minimum) and apply a high-contrast white module background. Test scan reliability on at minimum three physical devices (budget Android, mid-range Android, iPhone SE) before marking the screen as done.
Contingency: If scan reliability remains an issue, add a 'Enlarge QR' full-screen mode triggered by tapping the code, and ensure the text referral URL with copy-to-clipboard is always visible as a fallback sharing method.
The onboarding screen submits attribution and then hands off to an external membership registration URL (HLF's Dynamics portal or similar). If the external URL is unavailable, changes its format, or requires authentication the new member does not have, the conversion funnel is broken at its final step.
Mitigation & Contingency
Mitigation: Confirm the external registration URL and its expected query parameters with HLF's portal team before implementing the handoff. Record the pending_signup attribution event before launching the URL so data is not lost if the external site fails. Display a fallback message with contact information if the URL launch fails.
Contingency: If the external membership URL is not available at feature launch, implement a temporary form that collects name and email and stores a pending_member record in Supabase, allowing coordinators to manually complete registration while the integration is finalised.
Embedding the RecruitmentStatsWidget on the peer mentor home screen may conflict with existing layout components (activity summary, badge shelf), causing overflow or requiring a redesign of the home screen that is outside this epic's scope.
Mitigation & Contingency
Mitigation: Design the widget as a horizontally constrained card with a maximum height of 96dp so it can be inserted into any vertical list without overflow. Coordinate with the home screen's existing layout owners before starting the embedding task.
Contingency: If home screen embedding creates unacceptable layout conflicts, defer embedding to a separate home-screen redesign task and make the widget accessible only via the dedicated ReferralCodeScreen for the initial release.