Open Web Advocacy

In a significant win for smaller browsers, the open web, and the 🇪🇺EU’s Digital Markets Act (DMA), Google has agreed to place the browser selected through the EU browser choice screen directly in the Pixel homescreen hotseat (replacing Chrome).

https://open-web-advocacy.org/blog/google-backs-down--will-grant-hotseat-in-eu-browser-choice-screen/
🧵👇 (1/7)

⚠️ WRITE TO THE UK'S CMA BY TUESDAY 5pm ⚠️

Under the current proposal, Apple can keep iOS and iPhone functionality exclusive to its own apps and services.

If you want fair access to APIs for competing apps and browsers email 📧 mobilesms@cma.gov.uk

See: https://open-web-advocacy.org/blog/apples-interoperability-commitments-to-the-uk-cma-promise-nothing/

🧵👇️ (1/5)

The UK's CMA says that developers need access to key iOS features to build innovative products and services, so UK consumers do not miss out but Apple’s proposed interoperability commitments are so weak they are essentially meaningless.

Read the full analysis here:
https://open-web-advocacy.org/blog/apples-interoperability-commitments-to-the-uk-cma-promise-nothing/
🧵👇 (1/10)

On Tuesday, the CMA announced that Apple and Google have proposed app certainty and interoperable access commitments. Of particular interest to OWA was the interoperability requirements, as we have argued that the CMA should impose an equivalent to Article 6(7) of the DMA.

While it's good that the CMA has chosen to include interoperability requirements, the requirements that Apple has laid out are simply too weak to possibly be effective.