January 2018 Summaries

Developers face a challenging experience when testing in-app purchases for iOS apps due to a range of issues associated with Apple's sandbox environment. The process requires creating sandbox accounts through iTunes Connect, which is cumbersome and prone to errors that can render accounts unusable. Logging in and out of sandbox accounts can disrupt devices, and testing recurring subscriptions may lead to persistent login prompts that affect personal devices. Developers encounter difficulties due to non-specific error messages, often stemming from environmental mismatches or unaccepted contracts, and the purchasing UI differs between sandbox and production, leading to misleading tests. Moreover, managing separate backend configurations for sandbox and production environments adds complexity and risk of app rejections. The article suggests that eliminating the sandbox environment in favor of whitelisting regular App Store accounts for testing could enhance the developer experience and improve the quality of in-app purchase implementation for end-users.

App Store receipts, introduced as an alternative to the SKPaymentQueue in iOS 7, provide a comprehensive snapshot of a user's in-app purchase (IAP) history and serve as the source of truth for developers. Although traditionally treated as mere tokens for server-side validation, these receipts contain detailed transaction information encoded using ASN.1 within a PKCS#7 container, secured through Apple's cryptographic signature process. Developers can extract and validate receipt contents using Apple's public documentation and cryptographic tools, bypassing the need for server-side validation via Apple's /verifyReceipt endpoint. However, the process is complex and prone to errors, lacking access to certain subscription-related fields like latest_receipt_info and pending_renewal_info, which could necessitate updates without recent receipts. Due to these challenges and potential security risks, it is recommended to use Apple's validation service or third-party solutions like RevenueCat to manage subscriptions effectively.

Apple's recent changes to Schedule 2, Section 3.8(b) of the Paid Applications Agreement have simplified the requirements for disclosing information about auto-renewing subscriptions, now focusing only on the title, length, and price of the subscription. Previously, developers faced challenges due to Apple's stringent and sometimes obscured submission criteria, which often resulted in app rejections for non-compliance. The updated requirements are intended to be displayed clearly within the app's purchase flow, without necessitating user interaction such as opening links, despite earlier expectations that information in StoreKit's modal alerts would suffice. The burden of implementing these requirements, including the need to incorporate specific legal language into the app's interface, has been criticized by developers as creating unnecessary complexity and cost. While Apple claims these changes address legal concerns, developers argue that adjustments to the iOS purchase flow would have been a more user-friendly solution.

The shift from traditional one-time app purchases to a subscription-based model is advocated as a necessary evolution to address the challenges faced by app developers in the modern marketplace. The old boxed software model, where developers could rely on periodic upgrades for revenue, is now obsolete due to app stores. Developers struggle with providing ongoing support and updates without a sustainable financial model, leading to issues like abandonware and low-quality software. The proposed solution is a patronage-like system through auto-renewing subscriptions, which aligns the interests of developers with their users by ensuring ongoing support and innovation. This model promises recurring revenue, allowing for greater stability and the potential to build a community of dedicated users. Despite the benefits, challenges remain, such as subscription fatigue and the technical complexities of implementing subscription systems. Nevertheless, with support from platform giants like Apple and Google, which have adjusted their policies to encourage long-term customer retention, the subscription model is positioned as the future of app monetization, offering a win-win scenario for developers and platforms alike.