medium complexity extracted Referral Program Confidence: 100%
5
Components
32
Shared
0
User Stories
Yes
Analyzed

Description

This feature enables peer mentors and coordinators to generate personalized referral invite links and QR codes that can be shared with potential new peer mentors. The system creates unique, trackable URLs tied to the referring user's account, allowing the organization to attribute new sign-ups to specific referrers. QR codes can be displayed on screen or saved for use in printed materials, making recruitment possible in both digital and in-person contexts. The feature is designed for low-friction sharing through native mobile share sheets, SMS, email, and social media.

User Flow

Invite Link & QR Sharing user flow
Click to expand

Analysis

Business Value

Peer mentor recruitment is a critical growth lever for all participating organizations. Manual recruitment via word-of-mouth is difficult to track and incentivize, leading to missed opportunities and slow growth. By providing a seamless, digital invite mechanism with QR support, Meander transforms every active peer mentor into a potential recruiter. Organizations benefit from measurable recruitment funnels, attributable sign-ups, and the ability to run targeted recruitment campaigns. For HLF specifically, the app has been positioned as a marketed membership benefit, making referral functionality a direct driver of membership growth and platform adoption across the network.

Implementation Notes

The invite link system generates unique tokens stored in the referrals table, linked to the referring user and organization. Short URLs are constructed server-side via the REST API and resolved during onboarding to pre-fill organization context. QR code generation is handled client-side in Flutter using a QR library (e.g., qr_flutter), rendering the invite URL as a scannable code. Deep linking via Firebase Dynamic Links or Universal Links ensures the invite URL opens the app or falls back to the app store. The native share sheet is triggered via the share_plus Flutter package. All tokens must be scoped to the organization for multi-tenancy correctness and should expire after a configurable period.

Components (37)

User Interface (1)

Service Layer (2)

Data Layer (1)

Infrastructure (1)

Shared Components

These components are reused across multiple features

User Stories

No user stories have been generated for this feature yet.