Sub Club by RevenueCat David Barnard, Jacob Eiting

On the podcast: How to make better decisions with data, the many pitfalls of collecting and interpreting data, and why the best executive dashboard is probably a hand-written weekly email.
Key Takeaways:📝Balance data collection with business goals. Collecting all possible data can drown teams in noise and lead to compliance risks. Focus on collecting semantically important data that aligns with business goals and use cases to avoid unnecessary complexity and costs.
💡Prevent exponential cost increases by structuring data early. Establishing a well-structured data collection and management process early on prevents costly modifications and adjustments later. Early alignment and thoughtful planning are crucial.
🔒 Maintain control over data collection to simplify compliance. Managing your own data collection processes can reduce legal and compliance challenges associated with third-party data processors. This is especially crucial for adhering to regulations like GDPR.
🔧Opt for off-the-shelf data solutions early on. Leveraging open-source or ready-made solutions can save time and resources. Maintain a clear evaluation structure for transitioning to custom solutions when needed, and accept changes in data collection methods to avoid outdated systems.
📊Simplified insights over complex dashboards. Dashboards can overwhelm executives with too much data. Instead, providing a succinct, focused summary of key insights through something as simple as a weekly email can be more effective for decision-making.
About Guest 
📈 Director of Data Products at News Corp.
💡With over 15 years of experience, Taylor is an expert in building and implementing effective data collection and analytics strategies — helping organizations like Disney+, Business Insider, and Deloitte collect the right data and turn it into actionable insights.
👋 LinkedIn
Follow us on X:
David BarnardJacob EitingRevenueCatSubClubEpisode Highlights
[3:44] Laying a foundation: Data collection is a lot like constructing a building — setting up the right framework from the beginning can save you a lot of time, effort, and money later.
[7:30] The Goldilocks zone: Collecting either too much or too little data is costly and can potentially have ramifications for data regulation and privacy laws.
[16:58] Information overload: Data is only helpful if you derive actionable information from it.
[20:33] Distilling data: What is a “data product” team? (And why might you need one?)
[26:13] Build vs. buy: Most companies should start with an off-the-shelf data collection solution instead of building something internally — then consider a switch later when the scale and financials make sense.
[33:45] What’s in a name? What you call specific data points and even your data collection system can be very important.
[42:11] Ditch the dashboard: Fancy data analytics dashboards need to be interpreted to be valuable — and without context, they can be misleading.
[51:27] Trix are for… kids?: How Taylor’s experience promoting the television show “Bluey” on Disney+ illustrates the incredible power of data analytics.

On the podcast: How Mojo grew to over $1M in MRR, the most impactful pricing and paywall experiments, and why it’s important to choose complexity instead of just letting it happen.
Key Takeaways:
💪Bravery to pivot leads to long-term success. Early popularity can be deceiving. Without strong retention, it's time to pivot. Build features users love to evolve from a gimmick to a sustainable business.

🧱Make your paywall more prominent. Show your paywall during onboarding. Then, iterate on messaging, design, and pricing, focusing on one element at a time.

💲Pricing will always annoy someone. If no one complains, you’re underpricing. Be strategic about who you upset and how many people.

🤝Viral loops reduce the need for ads. Heavy ad spend can hide a lack of product-market fit. Build sharing and virality into your app first, then consider paid acquisition.

📈Choose complexity based on impact. Focus on your team’s strengths. Growth can be product-led or through, for example, paid acquisition, depending on what suits your team and app best.
About Guest
👨‍💻 CEO and co-founder of the video editing app Mojo.
🎬 Former GoPro employee and graduate of the Y Combinator accelerator program, Francescu and his team have built one of the top mobile apps for creating and editing social video content.
👋 LinkedIn
Resources
Connect with Francescu on X: https://x.com/Francescu More about Mojo: https://mojo-app.comPaul Graham’s essay “How To Do Great Work”: https://paulgraham.com/greatwork.html Follow us on X:
David Barnard - @drbarnardJacob Eiting - @jeitingRevenueCat - @RevenueCatSubClub - @SubClubHQ
Episode Highlights 
[4:27] AI + Mobile = ❤️: Why AI is probably the next mobile revolution.
[6:16] Going Pro: How Francescu got his start building mobile subscription apps.
[7:44] Pivot… PIVOT: Despite early success with their augmented reality app, Francescu and his team had to shut it down and pivot to a new idea.
[15:12] Pricing and paywalls and packaging, oh my: Why you need to show your paywall during onboarding (and other monetization lessons Francescu learned building Mojo).
[27:42] Viral moments: Building social sharing features into your app could save you time and money on user acquisition.
[36:19] The product-led growth trap: Developing new product features isn’t always the key to growth.
[41:15] Priced to annoy: If no one is mad about the cost of your app, your prices are probably too low.

On the podcast: Quitting a job to build your own apps, returning to that job after failing to gain traction, and the inflection point that allowed our guest to finally quit for good.
Key Takeaways:

💡If your first side project doesn’t take off, try again — Reviving a lackluster launch can be tempting, but it might indicate a lack of demand. Instead, start fresh with a new idea and watch for early signs of product-market fit.

💰Invest more in your product once you have “pull” and a channel — Achieving early product-market fit and having a reliable acquisition channel allows you to focus on enhancing your product and experimenting with monetization strategies.

🔞Avoid relying solely on one acquisition channel — While a dependable early channel like ASO is crucial, it comes with risks outside your control. Diversify by investing in owned or paid channels to adapt to changes more effectively.

🧑‍💻Building in public offers numerous advantages — Developing your app publicly immerses you in a supportive community of indie developers, providing motivation, inspiration, and valuable feedback. However, it can also attract copycat competitors.

📈"Test higher prices" should be at the top of your to-do list — Raising your app’s price may seem risky, but many indie developers are overly cautious. A/B testing can help you safely explore the impact of different price points without significant customer backlash.
About Guest
👨‍💻 Independent app developer and creator of HabitKit and Liftbear.
💡Sebastian began his career as a corporate web developer and became a full-time indie app developer after his habit-tracking app HabitKit took off.
👋 LinkedIn

Follow us on X:
David BarnardJacob EitingRevenueCatSubClub
Episode Highlights
[1:04] Web versus mobile: What motivated Sebastian to switch from web to mobile app development.
[4:17] Free solo: Having a corporate day job might not let you stretch your creative muscles as much as building your own concepts.
[6:43] Drive: If you’re going to build an indie app or venture-backed startup, make sure it’s something you need to do.
[12:13] Risky business: The riskiness of leaving a full-time job to pursue an indie venture is different for everyone, depending on life stage, finances, and family obligations.
[16:39] Just ship it: Your first idea might not be great, but getting started will lead to new, better ideas.
[24:04] If at first you don’t succeed: Sometimes it’s better to give up on an idea that isn’t working so you can focus on one with better product-market fit.
[28:38] Doing the (side) hustle: Making the decision to keep your day job or fully commit to your side gig can be tough.
[34:45] Changing the channel: The app stores are a black box — it’s a good idea to invest in additional acquisition channels in case of algorithm changes.
[38:26] Building in public: Having a following on social media can be a great source of support and user loyalty outside of the app stores.
[45:00] Raising prices: Don’t be afraid to experiment with higher prices — many apps are leaving money on the table.

On the podcast: Another Apple WWDC conference is in the books, and as usual, we’re excited to dig into everything Apple announced — and what it means for iOS developers and RevenueCat users. This year’s announcements covered everything from small quality-of-life enhancements in App Store Connect to the deprecation of some of Apple’s oldest in-app payments code.
Key Takeaways:

🏪 StoreKit 1 is deprecated — After 15 years, the old and creaking first version of StoreKit is being deprecated by Apple. It’ll likely stick around as so many legacy apps still use it, but StoreKit 1 will not receive new updates and features. 

🧠 Apple Intelligence — AI, rather than spelling the end of apps, could usher in a new era for apps. By building AI directly into the OS, connecting to services in a privacy-conscious way, Apple is opening up the potential of AI to all apps on the App Store. 

👀 Vision Pro — While Vision Pro is now available in new markets and has received an update to VisionOS, it still feels like a “publicly available beta”, where the audience size remains small. Great for experimentation, but not a place to build a business (yet). 

🧘 Quality-of-life improvements — Apple announced plenty of quality-of-life updates such as reduced screenshot requirements (now only one size per platform!), deep links for custom product pages, and a better experience for TestFlight users. 

🏆 Win-back offers — A fourth offer type is now available, which applies to users whose subscriptions have lapsed, something which wasn’t easy before. Win-back offers also come with functionality we haven’t seen before with the other offer types. 

🔏 AdAttributionKit — In what seems to be a successor to SKAN, Apple has announced a new privacy-focused ad attribution framework. AdAttributionKit better standardizes what existed before and comes with some new features (such as compatibility with third-party app stores).
About Hosts:
David Barnard is a Growth Advocate at RevenueCat and creator of apps like Launch Center Pro and Weather Up.
Jacob Eiting is the CEO of RevenueCat and an expert on subscription apps and in-app purchases.
Charlie Chapman is a Developer Advocate at RevenueCat, an indie developer of apps like Dark Noise, and host of the Launched podcast.

Follow us on X:
David BarnardJacob EitingCharlie ChapmanRevenueCatSubClubResources:
WWDC 2024 Session RecordingsSign-up Form to Get Notified About Advanced Commerce APIsApple Docs: What’s NewEpisode Highlights
[2:00] Goodbye to an old friend: After 15 years, Apple’s StoreKit 1 (recently renamed “original API for in-app purchase”) has been deprecated.
[7:09] AI in the OS: With natural language abilities integrated at the OS level, Apple Intelligence could change how developers build and users interact with apps.
[16:42] Vision of the future: Apple Vision Pro 2.0 is a cool opportunity for developers to experiment with, but it’s still early days (and the addressable market is currently small).
[21:07] App Store Connect updates: Apple announced multiple quality-of life improvements for App Store Connect, including the ability to nominate your app to be featured on the App Store, new tools for generating marketing assets, deep links for custom product pages, an improved TestFlight user experience, and reduced screenshot requirements.
[39:04] Baby, come back: App Store Connect now lets you set up win-back offers, giving you a new way to re-engage lapsed subscribers and raise your LTV.
[49:03] Streamlined purchasing: Users can now complete their entire purchase within the App Store (or you can opt out of this feature if you’d rather direct users to the purchasing flow within your app).
[50:21] Advanced Commerce APIs: With complex SKU bundling and the ability to track digital content from multiple apps within the same developer account, the updated App Store will support more complex monetization use cases.
[52:49] SKAdNetwork 2.0?: Appl

On the podcast: What to do when there are no jobs to be done, how to build innovative features, and why copying Duolingo’s engagement strategy probably won’t work for your app.
Key Takeaways:

🏆 To win over a mass market, you need to discover your app’s trigger. Apps serving niche audiences often have a well-defined job-to-be-done. Apps aiming for broad appeal, however, need to identify the triggers in a user’s daily life they will optimize for, in the absence of a specific user goal.

🪄 A framework for user retention. Apps that serve a mass audience need to work extra hard to engage and retain users. While niche apps might be inherently more retentive, they too would benefit from making the app: magical, relevant, intuitive in real-time, novel, and pleasurable.

🥅 Why you might not want to make “the Duolingo” of your niche. Apps like Duolingo try hard to shame you for not using them but make completing the day’s goal quick and easy. This approach may not be suitable for all long-term goals and doesn't work well when your aim is to retain as many users as possible.

🧑🏼‍🎨 Innovation isn’t accidental, it’s designed - here’s a framework to help:
Always align with your mission.Visualize the specific user you’re building this feature for.Specify the triggers you’re addressing.Know the job to be done for the user.Think through all of these areas when prioritizing your backlog.

👍🏼 Some features should be considered must-haves. Features that all your competitors have, fulfill a promise you sell users on, or whose absence will drive users to a competitor, or cause high levels of frustration if missing, should be prioritized. Deciding whether to prioritize these over innovative additions is up to you.
🦄 The other feature category to build for is “delighters.” While it’s difficult to know whether a feature will delight users, they typically drive retention, complete a known job in a delightful or magical way, and create “aha” or “wow” moments for the user.

About Guest
👨‍💻 VP of Strategy and creator of core features at Welltory.
💡Asya leads her team to build thoughtful, mission-aligned features that delight 8+ million active users.
👋 LinkedIn
Follow us on Twitter‣ David Barnard‣ Jacob Eiting‣ RevenueCat‣ Sub Club
Episode Highlights
[0:44] The Welltory story: How (and why) Jane Smorodnikova founded Welltory.
[6:55] Trigger happy: Some apps don’t have an obvious “job to be done.” When this happens, finding and nurturing the trigger for users to open your app is crucial.
[10:18] Making magic: Welltory’s framework for building a delightful, sticky app: Make it magical, make it relevant, make sense in real time, make it novel, make it pleasurable.
[21:14] The Duolingo of wellness apps?: Why Duolingo’s retention strategy wouldn’t work for Welltory.
[26:16] An innovation framework: When deciding what new features to build, align with your mission, know your personas, identify their triggers, and figure out what immediate and high-level problems you’re solving for them.
[37:11] Driving retention: The secret sauce for retaining users for the long term? Make your app experience magical and novel, provide relief, personalize and gamify the experience, and give users bragging rights and social sharing features.
[40:32] Feature deal-breakers: Make sure you build both must-have and nice-to-have features to avoid frustrating users and prevent them from switching to a competitor app.

On the podcast: How developers can launch and optimize their app listings on the Google Play Store. A conversation from Google I/O 2024 with Sarah Karam, director of Apps Partnerships at Google.
Key Takeaways:
There are now more ways to optimize revenue with Google Play Commerce, such as installment subscriptions and automatically adjusted local pricing. 

On Android, the leading apps diversify their monetization. Instead of offering just subscriptions, for example, they offer IAPs to cater for diverse user preferences. Tipping, for example, has seen huge growth. 

The leading Android apps also adjust their overall approach to cater for the huge and diverse user base. Just replicating your iOS strategy will only serve a small fraction of potential customers. How can you serve someone on a $200 phone as well as a $2000 one? 

“The consumer rarely buys what you think you sell” and understanding this can lead to secondary product-market fit, unlocking new growth. Stop thinking about your app in terms of the feature(s) it offers and more about what problem it solves. 


About Guest
👨‍💻 Director of Google’s Apps Partnerships team.
🤖 Sarah is passionate about helping developers succeed on Google Play Store and the Android ecosystem.
👋 LinkedIn
Resources
Google Play Academy
Guidelines to Getting Featured on Google Play
Guides to Help Grow Your Business on Google Play
Google I/O 2024 Keynote
Engage SDK
Custom Store Listings
Google Play business community on X
Android Developer YouTube Channel

Episode Highlights:
[3:57] Feature presentation: Getting your app featured on the Google Play Store can be great, but it isn’t the most important thing (and you still need to market your app to take advantage of being featured).
[8:46] Proactive engagement: Google’s newly announced Engage SDK (currently in developer preview) will surface apps at relevant times for users in the context they’re most likely to engage.
[13:53] Easier ways to pay (and get paid): New commerce options — including newly accepted forms of payment, installment payments, and student and senior plans — allow Android developers to serve more users around the world.
[23:37] Custom is key: Google Play Store listings can now be customized by the keywords users searched to find the app.
[29:38] Diversifying payments: Apps that offer in-app payments (IAP) in addition to subscriptions tend to perform better than apps that offer subscriptions alone.
[31:54] iOS =/= Android: To take full advantage of the Play Store, developers need to think about the diverse devices, budgets, and preferences of the 2.5 billion Android users around the world.
[34:40] Baby steps: Small experiments (like offering a paid 7-day pass instead of a free trial) can help you determine what works best for your app and tailor your offerings for diverse markets.
[45:00] Penny for your app?: Tipping is a surprisingly effective way of letting users pay for your product.