On 25th January, Apple published its guidance on how it would comply with the EU’s Digital Markets Act (DMA). The response, in keeping with Apple’s response to other demands for reforms, effectively disincentivizes most apps from taking advantage of the changes. The changes are complex and confusing, and the answer to whether apps should make changes isn’t completely black-and-white.  To help developers navigate these changes, we pulled together an “emergency” episode featuring RevenueCat’s CEO Jacob Eiting and Head of Product Jens-Fabian Goetzmann, Runway CEO Gabriel Savit, and Nico Wittenborn, founder of Adjacent.  Here are the discussion’s key takeaways: 📲 The DMA Reforms How App Stores Work in the EU — The DMA mandates that app stores, like Apple's, cannot enforce the use of first-party app stores or in-app payment systems in the EU. Android already supports third-party app stores (sideloading), so Google’s focus has been on offering alternative payments via “user-choice billing”. For Apple, which does not support sideloading, the EU reforms have needed to be much more significant.    🔓 Apple Releases Opt-In New Business Terms — Apple’s response was to introduce an optional new set of business terms with a dizzying number of changes to fees and choices for developers. By opting-in, developers unlock new ways to distribute their app and charge users, but doing so comes with changes to and additions to fees paid to Apple. The changes are complex enough that developers have to analyze the implications very carefully.   🌀Fee Structure of the New Terms is a Complex Maze — Apple's new terms introduce a convoluted fee structure, where reduced commissions are coupled with the Core Technology Fee (CTF), where developers pay €0.50 for the first annual install over a 1M threshold. The CTF includes not just first-time installs, but first annual re-installs and updates from first and third-party app stores as well. This install fee effectively means that any high volume low average revenue per user (ARPU) app is likely to lose out by accepting the new terms.  🛑 Third-party App Stores Unviable for All but the Biggest Players — The new terms aren’t so rosy for potential new “marketplace apps”, either. New app stores will not be exempt from the CTF, making the first 3M downloads of the marketplace app itself cost the operator €1M — €0.50 per install over the 1M download threshold. And then apps within that marketplace also have to pay the CTF fee. This means that opening a third-party app store is unviable except for the very biggest attempts or for stores that have a high-charge per install (e.g. a game marketplace where users pay a relatively high one-off fee per game).      🔍 There Might Be Strategic Opportunities, but They Remain to Be Seen — Yes, most apps seem to be better off sticking with the original terms. But there might be opportunities for niche apps. For example, apps that have a low volume of installs but high ARPU (by having a costly yearly subscription, for example) might be able to absorb the CTF, even considering yearly updates. An additional as-yet unexplored change is that Apple has introduced 600 new APIs, meaning that there’s an opening for new third-party applications and integrations.    About Guests 📱Gabriel Savit is CEO of Runway, a release platform for iOS and Android apps. Find Gabriel on X and on LinkedIn. 💲Nico Wittenborn is Founder of Adjacent, an early-stage VC firm. Find Nico on X and on LinkedIn. 😺Jens-Fabian Goetzmann is Head of Product at RevenueCat Links & Resources These aren’t the only concessions Apple has recently had to make. Earlier this month, the Supreme Court ordered that Apple needed to allow developers to link to alternative payment methods in the US. Read more about what those changes mean.On the RevenueCat blog, we’ve written up an overview of this podcast and included additional d