The bottom line
A minimum viable product needs only five features: analytics, re-engagement messaging, onboarding, a paywall and live chat or contact. They let a small app learn from real users and earn money without wasting time or money on extra features.
Key takeaways
- Analytics comes first because without it a team is building blind. 0:50
- Track where users drop off in onboarding, trial activations, time on each screen and retention.
- Many clients add analytics only after losing months or a year of user engagement with no data.
- Push, SMS and email bring users back to features they already have. 4:18
- An event reminder two days, one day and half an hour ahead makes the app feel smart without building anything new.
- Email matters because the team owns the customer contact, not Apple.
- Onboarding and a paywall decide whether a new install turns into revenue. 7:25
- Onboarding should state the one problem solved and use borrowed social proof, such as a pink noise stat of 27% better memory.
- Showing the paywall before sign-up raised paywall views from 40% to 94%, trial activations by 190% and sales by 52%.
- Live chat or a contact form catches problems before they become bad reviews. 10:55
- Junk messages are a better price than bad store reviews, and the chat also surfaces bugs like a broken contact button.
- A contact prompt on the delete screen reaches users just as they are about to leave.
I prefer junk before getting bad reviews.
Chaim, B7 Dev
Chapter summaries
0:00 Analytics shows what users actually do
Specific usage data, not a yes or no opinion, tells a team what to keep and what to fix.
- Track the one event that solves the app's core problem. 1:14
- Count how many users trigger it and how many reach it.
- Tied to the earlier advice to solve one problem well.
- Releasing the app and forgetting it leaves no way to know how much or how often it is used.
- Detailed numbers beat a simple "like" or "don't like". 1:41
- Details on how, when and how much show what to tweak, remove or change.
- "I don't know if it's yes or no": a bare opinion gives nothing to act on.
- Use a standard analytics tool, and learn to read it. 3:15
- Firebase (Google Analytics) and Mixpanel are common choices.
- Some teams install two packages to cross-check the data.
- The data can also be compared with App Store and Google Play analytics.
4:18 Re-engagement brings users back
Push, SMS and email each pull users back in a different way, so use all three with care.
- Push notifications make users open the app. 5:31
- Facebook, WhatsApp and Instagram send alerts like "another user interacted with you".
- Push can also announce new features or send a happy birthday.
- Push and email can point out hidden features users may not know about.
- SMS adds a check that the user has a real phone number. 5:57
- It can still be tricked, but most users are real.
- Social login also helps when the app needs user accounts. 4:31
- Email keeps a lasting copy in the inbox, but must not be spammed. 6:17
- Owning the address lets a team sell a new app or website product later. 7:00
- Steve's advice: if the app doesn't need email, don't collect it.
7:25 Onboarding sells the app's value
An onboarding screen should state the app's benefits and prove them before asking for money.
- Onboarding covers the benefits, the one problem solved and social proof. 7:40
- Steve's data says showing the paywall inside onboarding works, so it is counted as feature four.
7:47 Onboarding and the order of sign-up
A new user decides within moments, so onboarding must explain the app fast and put the paywall before the sign-up wall.
- Onboarding gets one or two screens to explain the app. 8:19
- Phones hold limited apps, so users give a new one only a few moments.
- The screens say what the app does, why, and how it solves the problem.
- Borrowed proof comes from searching the topic's published stats.
- Better onboarding raises retention and usage.
- Offer social login and ask for sign-up after the paywall. 9:11
- About 90% of iOS users sign in with Apple, and about 95% of Android users use Google.
- Calm lets users in, then asks for sign-up after a trial starts.
- A fitness client's mockups showed the flipped order.
- With 40% paywall views, 60% of users never get the chance to buy.
10:51 Live chat and contact us
A simple chat or contact option teaches a new product's team what confuses users, at almost no cost.
- Live chat is the least known feature and helps most early on. 10:51
- One audited app linked straight to WhatsApp from its paywall.
- Crisp.chat has a free plan and works on a website, in an app and on a paywall.
- The speaker is not affiliated with Crisp and has used it for years.
- Feedback arrives with the junk.
- A small contact icon guides users without hurting the flow. 12:40
- It can point users to a tutorial or promo video.
- Once the app has scale, the chat can be moved somewhere less visible.
- Watching users struggle shows where features were built wrong.
- Telling a tester which buttons to press hides those mistakes.
13:22 Designing so the app explains itself
The five features exist to reach product-market fit quickly without wasting time or money.
- Good design should need no explanation. 13:51
- If you must explain what the app does, the experience design is wrong.
- Time and money are tied together, so waste neither on the way to fit. 14:15
- Wave AI shows a contact option when a user hard-presses the icon to delete.
- With money, you don't want to waste time. Without it, you have time but should still stop wasting it.
In the growth library
Steve P. Young and Chaim, Steve P. Young, founder of App Masters; Chaim, app development partner at B7 Dev. Five features an app MVP needs to reach product market fit without overspending: analytics, re-engagement channels, onboarding, a paywall and live chat or contact us. Flipping the order of paywall and sign-up in one onboarding flow raised paywall views from 40% to 94% and trial activations by 190%.
Lessons that draw on this:
- How to design a paywall that converts
- What metrics to track and how to define them
- How to use notifications and lifecycle messages
- How to get users to the aha moment fast
- How to structure onboarding as a story
- How to decide how long onboarding should be
- How to learn from users and customers
- How to reduce churn and handle cancellations
- How to run trustworthy experiments
- How to launch a simple first version fast
More from
App Masters · The whole library, and ask it anything