It's a very small concession. The high initial friction still means when someone comes to me with a problem and I tell them the solution is in F-Droid, they have to wait a day. Most give up and pick a different, less trustworthy solution from Google Play.
Given the Epic settlement means Google is allowing alternate app stores, and also the delay only applies for unregistered developers, I'm not certain it won't actually get easier to get folk set up on F-Droid.
It still remains to be seen what the actual requirements are, and even if F-Droid could become "approved" that doesn't mean they want to. Time will tell.
Why the hell should we "mother may I" with Google for running apps on our own phones if it isn't sourced from the Play Store?
The "security" rationale is horseshit given just how much malware is readily download able on the Play Store. Google never cleans its own house before going after others.
If you don't have the framework, you don't have to worry about any of this (you also don't get the benefits, bank apps that require validated OS, tap to pay etc, without the framework).
You still seem to need a Google account to be able to use the hardware you just paid for. I don't have one, don't want one either. I've been using Android without Google for about 15 years now but will hold off on getting a new device until I'm sure I can continue using it without getting a Google account.
How long before there is a "we've detected your account has been used multiple times to re-setup a phone.. we've re-enabled the Google Nanny Safety mode.. also we've locked your google account just in case.. "
I mean other than hackers, who has needed to factory reset their phone more than once in a year you must be doing something shady... right right?
There's not really a way to bypass Google if they don't want there to be, and that's what they're moving towards. The only long-term solution is to cut Google out entirely.
Motorola with GrapheneOS is an interesting prospect. The space is ready for disruption and the tools to do it are more available than ever. Maybe it will come from the EU. Who knows, but Google overplayed their hand, IMO.
Also, let's be clear about the mobile landscape right now. Many apps aren't written in Java or Swift, but instead are being transpiled from other languages like TypeScript and using UI libraries that aren't locked to the mobile platform itself.
When a new mobile platform enters the space it will require some react-native and capacitor glue code and we are in business.
WTF win? Sounds like I will need a tracking google account because it can "carry over" when I "upgrade my phone"
"Google giving a concession" is no win.
WTF Concession? Why are we asking google for permission to use the devices we bought as they see fit?
Ok, google is doing what is best for them, abusing users. But the manufacturers are really to blame here because the devices are by default locked to what google and them decide. There is no Market Choice here.
It still remains to be seen what the actual requirements are, and even if F-Droid could become "approved" that doesn't mean they want to. Time will tell.
The "security" rationale is horseshit given just how much malware is readily download able on the Play Store. Google never cleans its own house before going after others.
> Google’s been working hard to relive everyone’s fears...
For example, lots of people use phones without any google play framework installed. Without that framework, how does it "carry over"?
This just raises more questions about how this whole process works.
Is it only the play api doing so? If so, then if you de-google, this entire problem goes away?
If not, then how can you 'carry over' to a phone unless you also install the play framework? Seems like that's unhelpful.
Also, let's be clear about the mobile landscape right now. Many apps aren't written in Java or Swift, but instead are being transpiled from other languages like TypeScript and using UI libraries that aren't locked to the mobile platform itself.
When a new mobile platform enters the space it will require some react-native and capacitor glue code and we are in business.
WTF Concession? Why are we asking google for permission to use the devices we bought as they see fit?
Ok, google is doing what is best for them, abusing users. But the manufacturers are really to blame here because the devices are by default locked to what google and them decide. There is no Market Choice here.