Today, the @EUCommission opened a process under the #DMA to regulate how #Google handles #interoperability within #Android
-
Today, the @EUCommission opened a process under the #DMA to regulate how #Google handles #interoperability within #Android
The
FSFE has been working intensively over the last two years to improve DMA interoperability against gatekeepers like #Apple and Google.We will monitor how the Commission implements the interoperability rules further, ensuring DMA enforcement is Free Software-friendly.
https://ec.europa.eu/commission/presscorner/detail/en/ip_26_202
-
Today, the @EUCommission opened a process under the #DMA to regulate how #Google handles #interoperability within #Android
The
FSFE has been working intensively over the last two years to improve DMA interoperability against gatekeepers like #Apple and Google.We will monitor how the Commission implements the interoperability rules further, ensuring DMA enforcement is Free Software-friendly.
https://ec.europa.eu/commission/presscorner/detail/en/ip_26_202
Earlier, in June 2025, we took part in the workshop organised by the Commission on #Google's #DMA compliance, where we raised issues related to #interoperability.
In particular, similar problems #FreeSoftware developers are facing with #Apple, like discretionary power to deny interoperability, the lack of transparency, and anti-competitive practices.
-
Earlier, in June 2025, we took part in the workshop organised by the Commission on #Google's #DMA compliance, where we raised issues related to #interoperability.
In particular, similar problems #FreeSoftware developers are facing with #Apple, like discretionary power to deny interoperability, the lack of transparency, and anti-competitive practices.
In the period of August-November 2025, the FSFE took part in a comprehensive study regarding #Google’s control over #interoperability in #AOSP.
In particular, the study focused on how the company's limiting access to critical interoperability can hinder Free Software projects.
The study was discussed in the @article19 #DMA Symposium and reviewed by the @EUCommission
A summary of the discussions conducted at the Symposium was later published at https://www.techpolicy.press/making-the-digital-markets-act-developer-friendly/
-
In the period of August-November 2025, the FSFE took part in a comprehensive study regarding #Google’s control over #interoperability in #AOSP.
In particular, the study focused on how the company's limiting access to critical interoperability can hinder Free Software projects.
The study was discussed in the @article19 #DMA Symposium and reviewed by the @EUCommission
A summary of the discussions conducted at the Symposium was later published at https://www.techpolicy.press/making-the-digital-markets-act-developer-friendly/
The @EUCommission's decision is a sign of progress in enforcing #interoperability obligations, tackling anti-competitive behaviour from these companies.
Taken together, such regulatory procedures should make interoperability effective, so #FreeSoftware developers have a chance to participate and innovate in digital markets.
-
Today, the @EUCommission opened a process under the #DMA to regulate how #Google handles #interoperability within #Android
The
FSFE has been working intensively over the last two years to improve DMA interoperability against gatekeepers like #Apple and Google.We will monitor how the Commission implements the interoperability rules further, ensuring DMA enforcement is Free Software-friendly.
https://ec.europa.eu/commission/presscorner/detail/en/ip_26_202
@fsfe @EUCommission
An issue for many danish users of degoogled androids is that we can not access apps that use the Google Play Integrity API - typically banking related apps and some public apps, like drivers licence, MitID etc.The API is a bad case of gatekeeping, holding people away from using safe mobile phone operating systems.
-
@fsfe @EUCommission
An issue for many danish users of degoogled androids is that we can not access apps that use the Google Play Integrity API - typically banking related apps and some public apps, like drivers licence, MitID etc.The API is a bad case of gatekeeping, holding people away from using safe mobile phone operating systems.
@anderslund actually, that is encouraging making degoogled devices insecure, to try to bypass that.
-
@anderslund actually, that is encouraging making degoogled devices insecure, to try to bypass that.
@nieldk I believe that would be hard. And I feel more encouraged to try to convince them to fix it
-
S simonjust@mstdn.dk shared this topic
-
@nieldk I believe that would be hard. And I feel more encouraged to try to convince them to fix it
@anderslund @nieldk not *that* hard. I had a rooted android phone successfully running MitID. All this "protection" can be spoofed. MitID never stopped working on that phone, but Google Wallet, which is relying on more serious checks, was flaky and would drop dead at random times. (Now i just have an nfc-enabled card taped to the back of the phone as a permanent hardware fix)
What is a bit ironic that i also have a piece of crap Samsung phone that i bought specifically to be a live backup of those difficult to set up apps—and it never managed to register in MitID. It is so seriously underpowered, although it is not even too old, that whenever MitID opened a webview the OS would clear the main MitID process in the background, resetting the whole progress.
So rooted phone worked, "secure" vanilla Samsung did not. -
@anderslund @nieldk not *that* hard. I had a rooted android phone successfully running MitID. All this "protection" can be spoofed. MitID never stopped working on that phone, but Google Wallet, which is relying on more serious checks, was flaky and would drop dead at random times. (Now i just have an nfc-enabled card taped to the back of the phone as a permanent hardware fix)
What is a bit ironic that i also have a piece of crap Samsung phone that i bought specifically to be a live backup of those difficult to set up apps—and it never managed to register in MitID. It is so seriously underpowered, although it is not even too old, that whenever MitID opened a webview the OS would clear the main MitID process in the background, resetting the whole progress.
So rooted phone worked, "secure" vanilla Samsung did not.@dzm
I'm not sure what the problem with MitID is, since I have had a totp display device with it all the time.With MobilePay, the problem is the app uses Google Play Integrity API, and I do not have google play installed.
-
@anderslund @nieldk i also have the totp device. It is safe (less likely to just stop working), but a bit less convenient. Mobilepay, Sundhedskortet, Rejsebillet et al do not have a viable alternative, and that is upsetting.
-
@anderslund @nieldk i also have the totp device. It is safe (less likely to just stop working), but a bit less convenient. Mobilepay, Sundhedskortet, Rejsebillet et al do not have a viable alternative, and that is upsetting.
