Yes that's how the game goes. The regulator has to keep plugging holes that the non compliant corporate entity finds until there are no more holes worth exploiting by the corporate entity.
It is an exhausting and practically unending task to defend consumers against malfeasant operators but it is one that governments can and must do.
That's a completely different fight from what the DMA targets though. Referring to this as an Android/Google Play thing is a red herring here, this is just bog standard DRM, which just so happens to be made by Google (and maybe gets some special hardware support; so, if anything, DMA here would be an argument for allowing other app suppliers to be able to make equivalent DRM!).
The verification that the user downloaded the app from the Play Store has hardly anything to do with DRM.
They claim its raison d'etre is allowing "better download metrics" and control on the kinds of devices allowed to run the app; those reasons hardly justify forcing going through the Play Store (and having, and associating, a Google account).
Indeed there's no benefit to users from an app being arbitrarily tied to the Play Store, but that's entirely equivalently so to how there's no benefit to users from any sort of DRM.
Perhaps "digital rights management" isn't exactly the thing to use here, but it's still the same general concept of "author of a specific piece of media/content/app adds an arbitrary technological restriction that doesn't directly benefit users in any way (while ideally not affecting intended proper users) but still potentially helps the author".
It's harder to see for free apps, but for paid ones it's utterly trivial - of course you're gonna have to buy it through the Play Store with a Google account if the author has decided to only sell it on the Play Store; and afterwards wanting to use it without Google Play interference is equivalent to wanting to access media without DRM after having bought it (i.e. reasonable desire, perhaps not even illegal to attempt to achieve through arbitrary means, but owners of the respective thing can still try their damnedest to prevent you from it).
Well, here the app authors as well gain very little, they usually enable it just because they want the maximum "security", and are led to believe that this will help we with that
To be fair, a manufacturer also has a right to choose how they distribute their product. If one is philosophically ok with piracy, then you can choose to ignore that, but I don't think you should expect the developer to actively facilitate that.
Their rights stop at that border, how they choose to distribute. They have no rights after that beyond the copy right.
Software is out of step with hardware at the moment but we do have principles that means "warranty void if removed" stickers are toothless decorations, and Keurig has no right to actually enforce their wishes about what coffee you brew in your machine. We don't currently have software analogs for those, but the principles hold the same.
I am suggesting a scenario where a regulator decides that they no longer have that right because the regulator feels that the needs of the consumer outweigh the needs of the manufacturer.
This would be similar to how regulations around interoperability and accessibility where the regulator decides that imposing such obligations on developers leads to a better society.
