Also, it is getting harder to avoid using Google Play Services in your apps since they are putting more Android features behind that iron curtain as well.
1. As you stated, Google forces devs to rely on presence of the Google Play Services
2. Devs don't care: I don't see why e.g. Discord should not run properly on MicroG (I get push messages after logging in, but the app itself shows all friends as offline, no servers and a "can not connect to discord" message; from what I found online, it doesn't seem to be intermittent).
3. I wouldn't even know which 3rd party app store to use (okay, besides F-Droid for FOSS and some Google Play Store Proxy)
Not forcing per se. Google just provides a convenient services that devs are happy to use.
I might be an outlier though.
Google Cloud Messaging was then set to be the only service that could wake the device up when it was sleeping. Supposedly it batches messages and sends them at optimal times to save battery.
But it seems these maintenance windows aren't frequent enough (every 15 minutes?) for some apps.
Do you want to use a messenger or any other social media app where the worst case scenario is that it takes 15 minutes for the message to reach the recipient?
Certainly not, so the app vendor is forced to use FCM to display notifications immediately even if the recipient's device is in Doze mode.
The Google Play Services moves are unfortunate, but required. Most device manufacturers do not provide updates for Android on time, so any code that is part of Android itself becomes harder to update.
Only because Google lets the device manufacturers off the hook. It's a problem of Googles own invention. Trading away customer security for market share.
Adding: very successfully too, this isn't the first time I hear how you should almost feel sorry for Google that they have to put so much into google services instead of Android, all because of the evil device manufacturers! Nothing can be done no... wrings hands
Maybe it will change a little but now that Huawei happened.
It is not a problem that is retroactively fixable by other means than by what they are doing now.
They could take Android closed source and put a restrictive license on it demanding that timely updates as a condition of use. All that would achieve is that the large vendors will either stick with the old, still free to use, Android or start working on their own systems they would control again - Samsung's Tizen, Huawei is developing their own, etc. It doesn't take much to piss a large vendor like Samsung off sufficiently to jump ship. They aren't married to Android and have plenty of resources to pour into proprietary alternatives. Google doesn't have much leverage there.
The result would be only a market fragmentation, collapse of the app market and loss of market share for Google. That would benefit exactly nobody.
Phone vendors are not interested in system updates - that's a pure cost they don't want to pay, they would rather have you buy a new phone or at least not have to spend money and engineering time on preparing patches.
Google could for instance not allow the manufacturer to connect to their Google Play store unless the manufacturer played ball.
But where does this all put us? We are OK with crap, insecure devices being shoved all over the markets? What can be done.
Very true but I think the point GP was trying to make was that Samsung is bigger bthan Apple and would have enough influence to get a lot developers to work on its platform instead.
"Must keep firmware updated with security fixes."
They are still dark patterns, that they also have found excuses for those dark patterns does not make them any better. In fact most of the stuff (not just Google's) we see nowadays that take control away from the users - very often in ways that entrench monopolies and the status quo - use "but security" as their primary defense.
Note that since Android P or so, only explicitly whitelisted apps are even allowed to ask for app install. There's a user setting for each. So this is effectively already in place.