This repository was archived by the owner on Dec 23, 2024. It is now read-only.
Consider replacing F-Droid with Droidify on Android 12 #58
Unanswered
TommyTran732
asked this question in
Ideas
Replies: 2 comments 5 replies
-
Perhaps, I can consider just for 12 branch.
It'd be nice to see the functionality upstreamed into F-Droid instead.
|
Beta Was this translation helpful? Give feedback.
2 replies
-
I disagree. Using a third party F-Droid client would mean depending on both F-Droid and that third party, and what happens if the guy maintaining Droidify stops working on the client? Or if the main F-Droid client gains support for seamless updates? I believe that defaults should be strong and stable, and unfortunately many small OSS apps/projects have neither of those qualities :/ |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The current F-Droid client is quite bad as it still targets API 25 and does not work with the new Android 12 feature supporting seamless update with third party app stores.
I think that replacing the F-Droid client with Droidify when you update to Android 12 would be a great idea, since it removes the need for the privileged extension (Droidify supports seamless updates on Android 12 just fine), and does not target an ancient API.
Beta Was this translation helpful? Give feedback.
All reactions