April 2022 Summaries

The latest release of the iOS SDK, version 4, introduces significant updates, including a full migration from Objective-C to Swift, enabling StoreKit 2 features and Swift Concurrency support while maintaining compatibility with Objective-C. This version offers async/await alternatives to simplify code, introduces an AsyncStream for customer updates, and includes StoreKit wrappers to remain agnostic to StoreKit versions, allowing seamless feature implementation. The update enhances API consistency, clarity, and convenience with improved naming conventions and more informative docstrings. New APIs leverage StoreKit 2 for subscription management and refund requests, and the SDK is designed to automatically use StoreKit 2 where supported, with an option to enable it for all features. The release also includes a revamped documentation page and is the largest update to date, with numerous changes and contributions from the developer community, now in production across various apps.

RevenueCat has enhanced its integration with Expo, simplifying the process for developers to monetize React Native apps by supporting the Expo managed workflow, which previously lacked compatibility. The collaboration enables developers to use RevenueCat's react-native-purchases library to facilitate cross-platform in-app purchases and subscriptions without dealing with native complexities, as Expo abstracts the intricacies of Android and iOS builds into a JavaScript/TypeScript environment. Developers can choose between Expo's bare or managed workflows, with the managed option now accommodating RevenueCat functionalities thanks to Expo's recent updates in supporting in-app payments and permissions. The integration process involves setting up a project with Expo CLI, configuring RevenueCat products, and utilizing Expo's EAS tool for building native binaries, thereby streamlining app deployment and testing across platforms. This partnership aims to enhance the developer experience by minimizing technical hurdles, thus allowing more focus on app development and monetization.

RevenueCat's approach to maintaining a robust iOS SDK involves an extensive testing process that includes unit tests, StoreKit tests, backend integration tests, SDK installation tests, API tests, documentation reference tests, and a testing app for UI-based features. These tests are designed to ensure the SDK's reliability across multiple platforms and OS versions, with continuous integration (CI) playing a significant role in automating the process. Unit tests are run continuously during development to identify bugs quickly, while StoreKit tests verify correct usage of StoreKit, particularly StoreKit 2, which cannot be mocked. Backend integration tests are pivotal in verifying real app interactions with the RevenueCat backend, albeit with less precision than unit tests. API tests prevent unintended changes to the public API, ensuring compatibility for various apps. SDK installation tests focus on the successful integration of the SDK across different package managers, and documentation reference tests ensure that public documentation remains accurate and helpful. RevenueCat also conducts testing parties and gathers feedback from both internal and external app developers to refine user experience and catch any oversights. This comprehensive testing strategy allows RevenueCat to roll out new features confidently, knowing that their SDK is well-tested and reliable across diverse environments, ultimately enhancing user experience and satisfaction.

In a condensed version of Andy Carvell’s Mobile Growth Stack, the article outlines a streamlined approach for early-stage mobile app developers focusing on five key areas: user and audience research, product development, data taxonomy and event tracking, behavioral analytics, and onboarding and activation. Emphasizing the importance of understanding user needs before building, the guide suggests engaging with potential users through affordable methods like community forums and interviews. It highlights the necessity of analytics to track progress and improve user interaction, recommending tools like Firebase for startups. The piece advises that while paid acquisition strategies can be delayed until churn rates are reduced, non-paid activities such as community building and brand exploration can run in parallel. The 80/20 rule is advocated to balance effort and payoff, and developers are encouraged to postpone high-effort areas until foundational elements prove successful, allowing for sustainable long-term growth as outlined in the Mobile Growth Stack.