TRANSMISSION 011 · 12 JUL 2026 ARCHIVE: ZONE 2 — MOBILE / ANDROID · REFLECTION

What the Digital Markets Act Means for Solo App Developers

The Weaver — an edict at the city gates
a set of scales bearing the title of the Digital Markets Act (DMA)
Fig. 1 Weighing the pros and cons of the DMA

The city gates didn't open on their own. An edict came down from a distant council in Brussels, ordering the guards to let through even those who don't pay the main toll. The guards complied — but they also wrote a new rulebook, in small print, on how you get through the side doors. I went back to the gates to read it.

What the Digital Markets Act is, in brief

The Digital Markets Act (DMA) is the European regulation, in force since 2023 and fully applied since 2024, that imposes competition rules on the big digital platforms designated as gatekeepers[1] — among them Apple's App Store and Google Play. The stated goal: stop whoever controls the gate to billions of users from also dictating the only rules of the game inside it. For a developer, the part that matters isn't the antitrust theory, but the practical consequences for how you distribute and sell an app inside the European Union.

What actually changes if you publish an app

From a technical standpoint, the DMA's obligations have produced a few concrete openings, available only to users in the European Union:

The price of a gate that opens

None of these openings is free, and this is where the regulation stops being a newspaper headline and becomes a spreadsheet to read carefully:

Zone note All of this applies only to users physically located in the European Union (or the EEA). An app published by a solo developer today effectively lives under two different sets of commercial rules depending on where the person downloading it is — a fork that simply didn't exist before the DMA.

My take

It's tempting to read the DMA as the lone craftsperson's victory over the gate monopoly. In part it is: being able to link your own site for a commission-free payment, or distribute an iOS app outside the App Store, are possibilities that until recently didn't exist at all. But for those of us developing solo, the extra freedom almost always arrives disguised as another decision to make: which business model to pick on Apple, whether to enable alternative billing on Google, whether it's worth running two payment systems and the related VAT bookkeeping for an app that might bring in a few hundred euros a month.

The side gate is open, but it has its own form to fill out. For a legal team it's one more line in the spreadsheet; for someone publishing alone in the evening after dinner, it's time taken away from writing code. That's no reason to ignore it — it's a reason to evaluate it before publishing, not after, exactly like the fourteen days of closed testing I wrote about in this zone.

root@survival:~$ status --regulation dma --scope eu-only
> app-store-ios: sideloading + alternative stores available
> google-play: alternative billing, requires business status
> fees: reduced BUT new items (CTC / billing fee)
> geographic validity: EEA/EU USERS ONLY
> moral: MORE CHOICES = MORE DECISIONS TO WEIGH

Frequently asked questions

Does the Digital Markets Act apply to apps by a single developer?

Yes: the regulation imposes obligations on the gatekeepers (Apple, Google and other large platforms), and it has no minimum threshold for the developer who publishes. The new possibilities — alternative stores, your own billing, telling users about external offers — are available to anyone publishing an app for users in the EU, regardless of team size.

Is it worth enabling alternative billing on Google Play or Apple?

It depends on your sales volume and your ability to handle invoicing and support yourself: below a certain revenue threshold, the savings on commissions are unlikely to make up for the time spent running a second payment system and the tax obligations that come with it.

Does the DMA apply outside the European Union?

No. It's a European regulation: the openings it imposes (sideloading, alternative stores, your own billing) only apply to users located in the EU/EEA. For the rest of the world, Apple's and Google's ordinary rules remain in force.

The regulation has opened a gap in the wall. I haven't yet decided whether going through it makes sense at my scale, but at least now I know where it is, and what it asks in return.

Notes

  1. Gatekeeper — in DMA terminology, a large digital platform designated by the European Commission based on thresholds of users, turnover and market position, subject to specific openness and non-discrimination obligations. ↑ back to text
  2. Core Technology Commission (CTC) — the commission Apple charges, under the new single model in force since 1 January 2026, on transactions for digital goods and services generated by an app in the EU, regardless of the payment channel used. The details (thresholds, percentages) are updated periodically by Apple: always check the official developer documentation before planning. ↑ back to text

// FROM THE SAME ZONE

TRANSMISSION 034 29 SEP 2026
ZONE 2 — MOBILE / ANDROID · DECISION GUIDE

Your phone already knows how to call for help: turn these features on

Emergency SOS and emergency contacts are already built into Android and iPhone. Here's how to switch them on.

TRANSMISSION 023 05 AUG 2026
ZONE 2 — MOBILE / ANDROID · MANIFESTO

Three apps, three pillars of survival

BioRadar, EcoSurvivor and HotSummer share a common thread I only found afterwards: know nature, don't waste resources, face the extremes.

TRANSMISSION 022 01 AUG 2026
ZONE 2 — MOBILE / ANDROID · REFLECTION

Ownership vs. Subscription

Why "publisher, not seller" doesn't mean "I don't sell": a reflection on one-time purchases, subscriptions, and what's still yours after you buy an app.