Apple Pulled Cal AI for Deceptive Billing Design, Not External Payments
At a glance:
- Apple removed Cal AI, a MyFitnessPal app, for violating in-app purchase rules
- The app used a deceptive billing design that prioritized weekly pricing over actual charges
- Cal AI returned to the App Store after fixing issues, now ranking #4 in Health & Fitness
Apple's Enforcement Against Cal AI
Apple clarified that Cal AI's removal wasn't due to external payment integration, which is now permitted in the U.S. following its legal victory against Epic Games. Instead, the app breached guidelines by failing to display in-app purchase options alongside third-party payment flows. According to Apple, Cal AI misled users by highlighting calculated pricing while obscuring the true subscription cost. The app also forced users through multiple payment steps after declining the initial offer, creating confusion and negative reviews. This enforcement underscores Apple's strict adherence to its App Store policies, even after regulatory changes allowing external payments.
The core issue revolved around Cal AI's billing structure. While the app directed users to Stripe for subscriptions—a permitted practice—it omitted the required in-app purchase option. Apple mandates that non-reader apps (those not offering streaming content) must include both in-app and external purchase paths. Cal AI's design violated this by presenting only a third-party flow, which Apple deemed deceptive. The app's free trial toggle further complicated matters by not clearly communicating automatic renewals, a common point of user frustration.
The App's Billing Design Flaws
Cal AI's interface allegedly prioritized weekly pricing calculations over the actual amount users would pay monthly. For example, if a subscription cost $9.99 monthly, the app might prominently display a $29.97 weekly total without clarifying the recurring nature of the charge. This approach exploited users' tendency to focus on short-term costs, a tactic Apple explicitly prohibits. Additionally, the app's free trial toggle lacked transparency about subscription terms, leading to unintended renewals. Users who canceled the trial were then funneled into a separate payment flow, creating a disjointed experience that violated Apple's requirement for clear, upfront billing.
The app's developers, MyFitnessPal, have not publicly addressed the incident. However, TechCrunch speculates that Cal AI may have been testing Apple's enforcement post-Epic Games ruling. The court mandated Apple to allow external payment links in apps, but Cal AI's case shows the company still penalizes non-compliance with in-app purchase requirements. This tension highlights the complexity of Apple's App Store policies, which balance regulatory mandates with its own revenue model.
Cal AI's Return and Implications
After addressing Apple's concerns, Cal AI was reinstated in the App Store. It now holds the #4 spot in the Health & Fitness category, suggesting user demand persists despite the controversy. The app's return indicates that corrections can mitigate enforcement actions, but it also signals Apple's vigilance. Developers must now navigate a stricter landscape where even permitted external payments require meticulous compliance with in-app purchase rules.
This incident may influence other apps relying on third-party payment systems. While Apple allows external links, the requirement to pair them with in-app options creates operational challenges. For instance, apps like Netflix or Spotify—classified as reader apps—avoid this scrutiny by offering streaming content. Cal AI's case serves as a cautionary tale about the risks of non-compliance, particularly for apps targeting health or fitness niches where billing transparency is critical.
Broader Context of App Store Enforcement
Apple's actions against Cal AI align with its broader efforts to maintain control over App Store economics. The company has previously targeted apps using web-based payments, citing concerns about revenue sharing and user experience. The Epic Games case set a precedent allowing external payments, but Apple's response to Cal AI shows it hasn't abandoned its in-app purchase-centric model. This dual approach—permitting external links while enforcing in-app requirements—creates a complex regulatory environment for developers.
The Russia payment suspension, announced earlier this month, further illustrates Apple's strategic shifts. By halting new purchases in Russia, the company may be testing market responses or addressing geopolitical concerns. However, this move is separate from the Cal AI case, which focuses on billing design rather than regional restrictions.
What This Means for Developers
Developers must prioritize transparency in billing designs. Apple's enforcement against Cal AI emphasizes that even permitted external payments require clear in-app alternatives. This means apps must display both purchase options simultaneously, avoid misleading pricing structures, and ensure trial terms are unambiguous. For non-reader apps, this adds a layer of complexity, as they must balance user convenience with regulatory compliance.
The case also raises questions about Apple's enforcement consistency. While the company allowed external payments post-Epic Games, it still penalized Cal AI for bypassing in-app requirements. This suggests Apple may be tightening its rules to protect its revenue share, which relies heavily on in-app transactions. Developers should expect continued scrutiny, particularly for apps in competitive or high-revenue categories.
Future Outlook
The Cal AI incident could set a precedent for how Apple handles similar cases. If other apps replicate its billing design, they may face removal. Conversely, if Apple relaxes its policies, it could create a loophole for developers. The outcome depends on regulatory developments and Apple's revenue interests. For now, the App Store remains a high-stakes environment where compliance is non-negotiable.
FAQ
Why was Cal AI pulled from the App Store?
What specific billing flaws did Cal AI have?
How does this affect other apps using external payments?
More in the feed
Prepared by the editorial stack from public data and external sources.
Original article