Google mocks Epic’s proposed reforms to end Android app market monopoly

jeffw@lemmy.world to Technology@lemmy.world – 137 points –
Google mocks Epic’s proposed reforms to end Android app market monopoly
arstechnica.com
34

You are viewing a single comment

F-Droid supports adding third-party repos, no need to create another app, right? Right?

F droid is dificult, the landing page is senseless and searching isnt intuitive. Feels a bit disjointed

They probably don't have a designer, but as a platform they're actually solid. App devs can't pull a switcheroo like uploading malicious apk because they can only upload source code (which will be made public), not binary. You can be sure apps you download there 100% generated from the published source code, unlike downloading from, say, release page on some random github repo.

Use Droidify or Neo Store. Both are in F-Droid repo, and both are better IMO.

Ahbso Droidify is a kind of store. I was wondering why I had it installed on my phone. I don't think I would ever try to repackage things or how they explained it.

Installed Neo Store. It's a joke IMO, for one single reason.

The app starts up and asks me for two permissions. "The app works better without battery optimizations." Alright? I'm not willing to sacrifice battery life for random app updates. I'll check for updates manually, and regularly, thank you.
And: "Please allow notifications if you want notifications." No.

If I want neither of those, there's no way to proceed. I press the back button, it closes the app.

Fastest uninstall ever. 😐

With a lacking thought process like that, I don't trust the store at all because the devs clearly don't have a lot of forethought.

So...a repo manager asks to notify you of updates, and check for them in the background...and that requires an essay long screed?

FYI I have battery optimizations enabled, and notifications disabled. App works great.

But whatever, I genuinely give no shits if you use it, or don't.

Neither of those permissions should be required for an app store. If someone wants to check for updates manually they should be able to do that.

Required means not optional... which both are....

Also, it's not unusual for a repo manager to request the ability to check for background updates, or send notifications....which again, are both optional.

You reply with an eSsAy sCoLdInG mE about this, and you give "no shits"?

lol ok. What a Reddit reply.

I'm just saying, sure, I bet I could enable the things it asks for and then turn them off and it'd work as I want it to, but if you design the shit like this, it's an instant turn-off for me. Like what else in the code is as shit as the very start of the UX? Other repo apps don't force these things on me so why should I accept this app to? I could, but I won't.