June 2026 Summaries

Google's Billing Choice program introduces flexibility in payment processing for digital goods within Android apps by allowing developers to offer users a choice between Google Play Billing and their own billing systems, including external web links. This initiative requires developers to integrate a choice screen, which can be rendered either by Google or the developer, and to report every alternative transaction back to Google using an external transaction token. The program involves four integration scenarios based on who renders the choice screen and where the payment occurs, with distinct obligations such as maintaining a compliant user interface and managing subscriptions while ensuring all transactions are reported accurately to Google. Billing Choice is not merely an alternative billing method but a coexistence with Google Play Billing, demanding developers to balance the benefits of control over their payment processes with the responsibilities of compliance and fair choice presentation to users.

In the competitive landscape of app development, simply mimicking successful competitors is no longer sufficient; the key to standing out lies in personalizing and genuinely iterating upon existing ideas to create a distinct product that resonates with users. While learning from successful apps can provide a beneficial starting point, the real challenge is to innovate beyond the standard templates and UX patterns that have become ubiquitous, making apps feel indistinguishable from each other. Developers are encouraged to infuse their apps with "heart" by authentically addressing user needs and speaking their language, which requires a deep understanding of the users' problems and preferences. With the advent of AI-assisted development and no-code tools, building apps is easier than ever; however, the difficulty has shifted to distribution and standing out in a crowded market. Successful apps combine genuine user engagement with a strong distribution strategy and an effective monetization system, balancing creativity with practical business acumen to ensure they attract, retain, and convert users effectively.

The text explores the debate between annual and monthly subscription models, arguing that while annual subscriptions are often favored for their perceived advantages in retention, cash flow, and lifetime value (LTV), monthly subscriptions have their own significant benefits that are frequently overlooked. It suggests that annual plans, although popular, can mask fundamental issues with product-market fit by providing misleading retention metrics. Monthly subscriptions, on the other hand, offer faster feedback loops, allowing companies to quickly gather insights and adapt their strategies, particularly in the early stages of development or in low-trust environments. The text emphasizes that monthly plans are particularly valuable when the app is new, the market is uncertain, or the user base has a preference for shorter commitments, such as in emerging markets or among younger users. It highlights that understanding the specific needs and behaviors of users can guide the choice of subscription model, and that monthly plans can serve as a strategic tool for learning, building trust, and optimizing revenue, rather than merely being a secondary option to annual subscriptions.

Apple has begun enforcing App Review Guideline 5.6.3 by rejecting apps that prompt users for reviews during the onboarding process, as this practice is considered manipulative and erodes customer trust. Previously, some apps garnered numerous five-star ratings by asking for reviews before users could fully engage with the app. Apple now advises developers to remove review prompts from the onboarding flow and instead request feedback at "natural and happy moments" when users have genuinely interacted with the app. To adapt, developers should implement systems to track user engagement, prompting reviews only when users are likely to give positive feedback, ensuring compliance with Apple's guidelines and potentially enhancing app store ratings.

RevenueCat has removed the "Always decline" option from its refund preference settings in the dashboard, as this approach has proven ineffective and can lead to increased chargebacks, which are detrimental to developers. Although existing settings of "Always decline" remain active, users are cautioned that its utility is diminishing. The change stems from Apple's refund system, where preferences serve as signals rather than binding decisions, and persistent decline requests are increasingly disregarded by Apple's systems. As a result, developers risk users opting for chargebacks, which can jeopardize developer accounts. RevenueCat now offers alternative options, such as letting Apple decide, granting full refunds, or prorating refunds based on usage, and developers can still decline specific refunds using the $appleRefundHandlingPreference attribute. This shift aims to enhance the effectiveness of refund management and mitigate adverse outcomes for developers.

Eric Duffett, a high school teacher and entrepreneur, transformed his hobby into a successful business with the creation of Shot Pattern, a golf strategy app. Initially developed as a simple tool to draw lines on satellite maps for golfers, the app gained traction when Eric invested $5,000 in course data, enabling it to simulate shots and enhance its functionality. Despite a setback when he declined a $75,000 buyout offer from a renowned golf company, Eric's persistence paid off as strategic Meta ads significantly boosted app downloads and revenue, surpassing the initial offer in profit. By 2026, Shot Pattern had crossed $1 million in sales, with Eric remaining the sole developer while hiring a contractor to manage business operations. Eric continues to teach, sharing his entrepreneurial journey with students and emphasizing the importance of perseverance and creativity in business.

RevenueCat's recent office hours on June 5, 2026, showcased several new features designed to enhance app monetization and growth strategies, with live demos and Q&A sessions led by product managers. Key highlights include the AI Editor, which enables the creation and refinement of paywalls using conversational prompts, and Paywall Rules for customizing component visibility based on specific conditions. The Funnels Builder allows the creation of web onboarding experiences, and A/B Testing within Funnels optimizes conversion rates by experimenting with different variables. One-Tap Purchases via Express Checkout integrates Apple Pay and Google Pay for seamless transactions, while Stripe Managed Payments handles global sales tax complexities. The platform also introduced a flexible Discounts system, advanced statistical tools for Experiments, and Rico, an AI-powered advisor for app growth. Enhancements to the dashboard include Benchmarks for comparing app metrics with industry peers and In-App Ad Revenue tracking for a comprehensive understanding of monetization. Additionally, support for Apple's 12-month commitment subscription model was announced, aimed at reducing upfront costs for users. These features collectively aim to streamline the monetization process and provide actionable insights for app developers.

RevenueCat's Codegen Gradle Plugin addresses the issue of using raw string keys for entitlements, offerings, and packages in Kotlin code by generating type-safe accessors through a build-time interaction with the RevenueCat API. This plugin enhances coding safety by converting dashboard keys into typed Kotlin properties, enabling IDE autocomplete and compile-time error detection for incorrect keys, thus preventing runtime bugs caused by typos or changes in the dashboard. The setup involves applying the plugin from the Maven Central repository and configuring it with essential properties like apiKey, projectId, and packageName. It offers options for caching and offline mode to maintain build efficiency without constant network dependency, and provides flexibility for developers by allowing dynamic updates from the RevenueCat backend without requiring immediate code changes or new releases. The plugin is ideal for projects with stable identifiers, turning potential runtime issues into compile-time checks, while allowing for dynamic offerings management where necessary.

The text provides a comprehensive guide on securing premium content in mobile apps, using a hypothetical app called "Catflix" as a case study. It discusses the vulnerabilities of client-side checks for premium content access and suggests more secure alternatives, such as implementing Firebase App Check and server-verified entitlements through Firebase Cloud Functions and RevenueCat. The text explores different approaches, including direct API calls, custom webhooks, and the RevenueCat Firebase Extension, which automates the syncing of user entitlement data to a Firestore database. It emphasizes the importance of not relying on client-side checks due to their susceptibility to tampering and highlights the benefits of using server-side solutions to ensure only authorized users access premium content. Additionally, it touches on the use of custom claims in Firebase Auth to efficiently manage user entitlements and the importance of refreshing ID tokens to reflect updated user statuses promptly. The article concludes by stressing the necessity of securing Firebase projects, protecting sensitive API keys, and staying updated with evolving technologies, such as the experimental Dart SDK for Firebase Cloud Functions.

WWDC26 introduced significant changes for subscription app businesses, focusing on enhanced monetization and user engagement strategies. Apple now allows annual subscriptions to be billed monthly, offering a new pricing model that can improve user retention by spreading the cost over twelve months. Retention Messaging is a novel tool that allows developers to present customized offers to users attempting to cancel their subscriptions, potentially increasing save rates. The ability to sell subscriptions to groups and organizations through group purchases and volume purchasing expands market opportunities, particularly in enterprise and educational sectors. Additionally, Apple has enabled cross-developer Bundles and Suites, allowing different developers to collaborate on subscription packages. The App Store is also getting new creative asset placements and personalized discovery features, enhancing app visibility. Lastly, Apple's updated App Review Guidelines aim to maintain a higher quality of apps by targeting saturated categories and encouraging developers to improve or update their offerings, aligning with the new Personalized Collections feature to highlight quality apps.

The text discusses the process of migrating from native Android and iOS in-app purchase implementations to a shared layer using Kotlin Multiplatform and RevenueCat's SDK. It highlights the challenges of integrating billing systems because of the differing purchase models and types on each platform. The migration process involves replacing native billing initializers, purchase flows, and entitlement checks with Kotlin Multiplatform equivalents, simplifying the codebase by using RevenueCat's store-agnostic concepts like Offerings, Packages, Entitlements, and CustomerInfo. This transition allows for a unified purchase flow and easier management of entitlements across both platforms, while maintaining continuity for existing customers through synchronization of purchases and user identities. The text also outlines the importance of verifying parity between the native and shared implementations before removing the old code and notes some platform-specific capabilities that require additional consideration.

The text discusses an alternative paywall model called "name your price paywall," which allows users to select from various priced packages that unlock the same entitlement, offering flexibility in how much they choose to support an app. This model is exemplified through a custom paywall developed for the app Trippity, which provides a lifetime unlock for features while letting users decide their support level. Implementing this involves setting up multiple in-app products linked to a single entitlement via platforms like RevenueCat, which simplifies entitlement management and allows for experimentation with different pricing strategies. The process can be automated using the RevenueCat AI Toolkit or done manually through platforms like App Store Connect or Google Play Console, and it can be integrated into apps using frameworks such as React Native. This approach is particularly beneficial for indie apps and projects that rely on user support for ongoing development.

Austin Blake defied conventional advice within the indie developer community by focusing on creating "Stuff," a task management app, despite the saturated market of to-do list applications. He utilized a modern AI-driven workflow, employing a system of AI agents to plan, critique, and code, which expedited the app's development for macOS. Blake faced challenges in adapting the app from iOS to macOS, including accommodating different user expectations and interface designs, such as selection states and undo functions. He experimented with the app's free trial period, reducing it from a month to seven days, which resulted in increased conversions by keeping the app fresh in users' minds. Additionally, Blake encountered unexpected delays during the App Store review process for the Mac version, leading him to advise future developers to allow extra time for approval. His journey included transitioning from a film major to a role at Apple and later joining RevenueCat as a Developer Advocate, with "Stuff" receiving recognition for its innovative use of on-device AI models.

Subscription apps often mistakenly view churn as the end of their customer relationship or resort to offering discounts to win back users, but a well-structured reactivation strategy can be a significant growth lever. Churned users, having once trusted the app enough to subscribe, represent a valuable segment that, when approached strategically, can yield high returns. Effective reactivation begins at the point of churn by collecting data through a simple questionnaire, allowing for personalized follow-up based on specific cancellation reasons. Timing plays a crucial role, with tailored outreach strategies differing for monthly and annual subscribers, and reliant on understanding each user's behavior and reasons for leaving. Rather than defaulting to discounts, contextual offers, usage-based incentives, and highlighting product improvements can foster genuine re-engagement. Ensuring a frictionless return experience by minimizing onboarding and maintaining user preferences is essential, as is recognizing that the success of reactivation is ultimately tied to the product's quality and user experience prior to churn. By positioning themselves thoughtfully, subscription apps can remain at the forefront of churned users' minds, encouraging them to return when the timing is right.