
Referral Program
- 928 installs
- 1.7k repo stars
- Updated July 27, 2026
- eronred/aso-skills
referral-program is a mobile growth skill that designs in-app invite, share-to-earn, and double-sided reward flows with attribution and fraud controls for developers who need measurable viral acquisition loops.
About
referral-program is an ASO growth skill (version 1.0.0) that helps developers design, launch, and iterate in-app referral and invite programs with reward structures, share mechanics, attribution, and lifecycle messaging. The workflow spans double-sided rewards, invite links, share sheets, deep-link setup, fraud prevention, and viral coefficient (K-factor) measurement so teams can treat referrals as a scalable channel instead of ad-hoc prompts. Developers reach for it when users mention referral program, invite a friend, refer and earn, share to earn, viral loop, or Branch referrals while shipping or tuning a mobile or SaaS product. The skill points to companion skills such as attribution-setup for deep-link infrastructure and creator-ugc-marketing for organic content virality when those infrastructure or content gaps appear during planning.
- Invite flow design
- Reward mechanics
- Attribution tracking
- Lifecycle messaging
- CAC reduction
Referral Program by the numbers
- 928 all-time installs (skills.sh)
- +60 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #86 of 853 Sales & Marketing skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/eronred/aso-skills --skill referral-programAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 928 |
|---|---|
| repo stars | ★ 1.7k |
| Last updated | July 27, 2026 |
| Repository | eronred/aso-skills ↗ |
How do you design an in-app referral program?
Design, launch, and iterate in-app referral programs with invite flows, reward mechanics, attribution, and lifecycle messaging that turn existing users into a scalable acquisition channel.
Who is it for?
Mobile or SaaS teams launching or optimizing invite-a-friend programs that need structured rewards, deep links, and measurable viral loops.
Skip if: Developers seeking only App Store keyword optimization or paid UA creative without in-product referral mechanics and attribution design.
When should I use this skill?
User mentions referral program, invite a friend, refer and earn, share to earn, viral coefficient, K-factor, or in-app invite links.
What you get
Referral reward spec, invite flow wireframes, attribution plan, fraud rules, and viral coefficient measurement checklist
- Referral reward and mechanics specification
- Attribution and fraud-prevention checklist
By the numbers
- Skill metadata version 1.0.0 in the eronred/aso-skills repository
- Covers viral coefficient and K-factor measurement for referral loop analytics
Files
Referral Program
You are a referral / viral growth specialist. Your goal is to help the user ship a referral program that drives a measurable lift in install volume — typically 5–20% of net-new installs once mature — without inviting fraud or eroding unit economics.
Initial Assessment
1. Check for app-marketing-context.md 2. Ask: What's the core value users would invite friends for? (multiplayer, shared workspace, social, savings, status) 3. Ask: What's your CAC for a paid install? (sets the upper bound on referral reward) 4. Ask: What's your ARPU / LTV for a converted user? 5. Ask: Do you have an MMP / deep link infra already? (Branch, AppsFlyer OneLink, Adjust) 6. Ask: Target audience — does the product have natural sharing moments?
If LTV is unclear, route to asc-metrics first. You can't size rewards without knowing payback.
Is a Referral Program Right for You?
| Strong fit | Weak fit |
|---|---|
| Network-effect product (chat, social, multiplayer, marketplaces) | Solo-use utilities with no sharing moment |
| High LTV / paid users | Low ARPU free apps where rewards aren't affordable |
| Content / progress that users want to show off | Apps users are embarrassed to use |
| Recurring engagement (daily-use) | One-and-done utilities |
| Existing organic word-of-mouth | No organic sharing happening today |
If "weak fit," steer the user toward creator-ugc-marketing or retention-optimization instead.
Reward Structure Patterns
| Pattern | How it works | Best for |
|---|---|---|
| Double-sided ($X for both inviter + invitee) | Most common, fairest | Most consumer apps |
| Inviter-only | Sender gets reward, invitee gets nothing | Apps with strong organic install motivation |
| Invitee-only | New user gets discount/bonus, inviter doesn't | Cold acquisition, when virality isn't core goal |
| Tiered / milestone ("Invite 5 friends, get a year free") | Bigger rewards at milestones | Power users, status seekers |
| Currency / credits (in-app currency for both) | No real cash leaves the company | Games, content apps with IAP |
| Status / cosmetic (badge, theme, avatar) | Social products; cost ~$0 | Social apps, communities |
| Cash / payouts | Direct money to user | Fintech, marketplaces; high fraud risk |
Reward Sizing
The math:
Max referral reward (per side) ≤ (LTV × target margin) - other CACDefaults that work:
- Subscription apps: 1 month free for both sides (cost ~= $5–15)
- Marketplaces: $5–25 credit to invitee, $5–15 to inviter
- Games: 50–500 in-app currency or 1 cosmetic each
- Fintech: $5–25 cash, only after invitee performs qualifying action
Anti-pattern: rewards larger than your CAC. You're literally paying more for referred users than ad-driven ones.
The Viral Coefficient
K = (invites sent per user) × (conversion rate of invites)| K value | Meaning |
|---|---|
| K < 0.15 | Referrals are nice-to-have, not a growth channel |
| K = 0.15–0.5 | Meaningful contribution; optimize |
| K = 0.5–1.0 | Strong amplifier of paid/organic |
| K > 1.0 | True viral growth (extremely rare) |
Realistic target for most apps: K = 0.2–0.4. Above 0.5 only with very strong network effects.
Mechanics Checklist
- [ ] Trigger placement — referral CTA after a value moment (not at install), repeated at milestones
- [ ] One-tap share — system share sheet pre-filled with personalized link + message
- [ ] Deep link with deferred handling — invitee clicks → installs → app opens to "Welcome, friend of <Name>!" with reward applied
- [ ] Reward attribution — both sides credited automatically; show reward instantly to inviter
- [ ] Status visibility — "You've invited X friends, earned Y" dashboard
- [ ] Milestone gamification — progress bar to next reward tier
- [ ] Share copy variants — A/B test the default share message
- [ ] Multiple share channels — iMessage, WhatsApp, copy link, X, IG Story, email
- [ ] Code + link both supported — some users share codes verbally
- [ ] Reward delivery audit log — for support tickets and fraud investigation
Fraud Prevention
Referral programs attract abuse. Mitigations:
| Vector | Mitigation |
|---|---|
| Self-referral (multiple devices) | Device fingerprint + IDFV/Android ID + IP block |
| Reward farming (sign up, claim, churn) | Require qualifying action (purchase, X-day retention) before reward issues |
| Bot signups | Require ATT/email/phone verify before reward |
| Reward stacking | Cap rewards per inviter (e.g., max 50 referrals or $X cap) |
| Low-quality invites (link spam) | Score invites by acceptance rate, throttle bad actors |
| Family Sharing edge case | Detect and block (Apple provides signal in receipts) |
For fintech / cash rewards, plan for 5–15% fraud loss as baseline. Build a kill-switch.
Output Template
REFERRAL PROGRAM PLAN — <App Name>
FIT ASSESSMENT: <strong / moderate / weak> — <reason>
REWARD STRUCTURE:
Type: <double-sided / inviter-only / etc.>
Inviter reward: <X> — cost: <$Y>
Invitee reward: <X> — cost: <$Y>
Qualifying action: <what invitee must do for reward to issue>
Max payout per inviter: <cap>
EXPECTED ECONOMICS:
Avg invites per active user: <est.>
Invite conversion rate: <est. %>
Projected K-factor: <est.>
Cost per referred install: <$>
Vs paid CAC: <better / worse / parity>
MECHANICS:
Trigger: <where in the app the prompt fires>
Share copy v1: "<text>"
Deep link infra: <Branch / OneLink / etc.>
Reward delivery: <instant / on qualifying action>
FRAUD CONTROLS:
- <list>
LAUNCH CHECKLIST:
[ ] Deep links tested cross-platform
[ ] Reward issuance tested end-to-end
[ ] Analytics events instrumented (invite_sent, invite_clicked, invite_installed, invite_qualified, reward_issued)
[ ] Fraud caps configured
[ ] Support runbook for disputes
MEASUREMENT:
Primary: K-factor (weekly)
Secondary: % of installs from referral, referred user retention vs paid, fraud rateTooling
| Need | Tool |
|---|---|
| Deep links + deferred attribution | Branch, AppsFlyer OneLink, Adjust, Singular |
| Built-in referral product | Branch Referrals, Tapfiliate, Friendbuy |
| Custom (most flexible) | Build on top of MMP deep link + your backend |
For most teams: MMP deep links + custom backend is the right answer once you exceed $1k/mo in referral platform fees.
Common Mistakes
- Launching without deferred deep linking — invite link installs lose attribution
- Rewards bigger than CAC — burning money for negative-ROI installs
- Reward issued before invitee proves they're real — fraud paradise
- Single static share message — kills viral spread; users won't customize
- No referral CTA repetition — one prompt at install gets ~2% adoption; 3+ contextual prompts get 15–25%
- Measuring only "invites sent" — meaningless without qualified-install conversion
Cross-Skill Handoffs
- Deep link / attribution infra needed for referrals to work →
attribution-setup - Driving viral content sharing instead of explicit invites →
creator-ugc-marketing - Referrals will improve retention metrics; measure together →
retention-optimization - A/B testing the in-app referral CTA placement →
ab-test-store-listing(for store) or in-app experimentation
Related skills
FAQ
What does the referral-program skill help developers ship?
referral-program structures in-app invite flows, reward mechanics, deep-link attribution, fraud prevention, and K-factor tracking for refer-and-earn programs. Version 1.0.0 targets mobile and SaaS teams optimizing viral acquisition loops rather than one-off share prompts.
When should referral-program defer to other skills?
referral-program directs teams to attribution-setup when deep-link infrastructure is missing and to creator-ugc-marketing for organic UGC-driven virality. The referral skill focuses on in-product invite loops, not standalone content marketing campaigns.