Flamme · B2C · couples app
Hide your partner's answer until you answer the question yourself
Created a back-and-forth loop credited with lifting retention; no separate number
What they did
What happened
This shipped together with other changes, so the result can't be credited to this alone.
In their words
An Nayal - Full App Growth Guide 2026 - How to Make Viral Content to Get Users & Make Your App Retentive
JosephYeah, that makes a lot of sense. Is there anything you did in the product that created those emotional stakes?
An NayalOne of the things we used at that point was the missing out effect, where if you did not answer your the question, you could not see your partner's answer as well. So it kind of created this situation where you really wanted to discover what their answer was, and if they answered, you would want to answer, but if you answer, they want to answer as well. So it would create this loop which would carry over to increasing the retention.
An NayalApart from that, we figured out notification was one of the best tools. One thing we discovered too late, which helps also, is widgets. I think one of the big advantages you have in a mobile app as compared to a web app is you can place a widget on the home screen, and that widget is a easy way to call the user back every single time. One of the apps which did this really well was Couple Joy.
Get tactics like this every Monday
New tactics from the week's founder interviews, each linked to where it was said.
More from this episode
- Relaunch the date planner as an AI relationship coach right after ChatGPT came outDay-30 retention rose from 0.8% to 4.2%, still too low; press but no traction
- Make the daily question for couples the main thing on the home screenDay-30 retention went from 4.2% to ~30%, then 50%, with streak reminders
- Send a friendly morning reminder, then an evening 'your partner will be sad' nudgeDay-30 retention went from 4.2% to ~50% alongside the daily-question redesign
- Add a home-screen widget showing distance to your partner and days togetherWorked well, per the founder; copied from a competitor; no numbers
- Launch alongside a TechCrunch Startup Battlefield feature800% organic growth in one month; stopped by a trademark letter
- Start charging in a free app when the money runs outBarely survived; the early '15% conversion' counted renewals, so it was inflated
- Pitch big investors on great retention before you have a way to get usersFailed; top firms asked about distribution and no term sheets came
- Scroll TikTok 4 hours a day for 2 months to learn what worksGot the first account getting views, then copied the approach across accounts
- Run 20-30 TikTok accounts on numbered iPhones, 3-4 accounts per phone~50M organic views; host cites ~150K users
- Use one Apple ID on every farm phone to skip repaying for the proxy appFailed: TikTok linked the accounts, one flag hit all; lost 120 work hours
- Under 300 views means a broken account; 300-1,000 means fix the contentTheir working rule for which accounts and formats to fix; no numbers on impact
- Judge app videos by likes and question slideshows by shares and savesLow-like videos rarely drove downloads, even at 1M+ views
- Post slideshows of '5 uncomfortable but healthy questions to ask your partner'Shared a lot, but only 0.05-0.2% of viewers downloaded
- Post videos that show the app in use, not memesApp demos convert 0.5-1% of views vs 0.05-0.2% for memes and slideshows
- Give AI a 10-page brief with product details, winning scripts and a master promptTeam posts ~200 pieces a day from it; winners are fed back in
- Log every post by hand in a spreadsheet and review it every morningForces the team to study why posts fail; no numbers given
- Copy only formats that went viral on small accounts and get 'what app?' commentsAdopted after 50M views brought few conversions; C part learned late
- Run real 'what do I text back?' Reddit screenshots through the app on videoJust started; guest expects 0.5-1% of viewers to download
- Design the app's screens and loading animation to look good on TikTok
Tags: ios, fomo, reciprocity, locked-content, multiplayer