Arnauld Neo Store has the same apps as F-droid. It also has 3rd party repositories that you can enable built-in within the app, but those can also be added on the official F-droid client as well.

    So, just for me to understand, there is a general consensus against using F-Droid at all? Because I believed to this day, that F-Droid is the holy grail of FOSS and security.

      tpax It's up to you whether you use F-Droid, but it has significant security issues in comparison to other methods of obtaining apps and isn't really recommended. For reference, https://wonderfall.dev/fdroid-issues/.

      If you do use F-Droid I would suggest using Droid-ify/NeoStore as a client instead of the official one to mitigate some of its problems.

      tpax For apps which have the same functionality on F-Droid and Play Store, I prefer Play Store (or Aurora Store). Some apps have a slightly different feature set on F-Droid, because there are features which are not allowed on Play Store. In that case I use Neo Store with the developer's repository or in case that's not available from the izzyondroid repo. In the latter case, I double check if the APK is truly from the developer's GitHub.

        5 days later

        Alright so I gave this some thought because it turns out I do have to use some apps from the f-droid repository.
        This is not a solution to the problem of f-droid not having a feed which people can use to get notified about updates.
        This may only work for apps on GitHub as I don't know how/whether other version control systems implement support for RSS/Atom feed.
        It's pretty straightforward. Subscribe to the GitHub repository from which f-droid builds. (Ideally the developer themselves would provide a release APK.) Create a Calendar/Task management app entry to keep track of it periodically to see when f-droid releases it's update.
        This is quite cumbersome but at least it mitigates some of the problem. And it is really not worth installing a whole-ass app store to get updates for 2 apps. So hope this long-winding insubstantial "solution" helps someone lol

          ayaen Sounds cumbersome. Why not install the APK from the developer and then update via the izzyondroid repo? If you do it this way, signature checks will make sure, that izzyondroid doesn't tamper with it.

            TheGodfather the joy of it all is that you're the Captain of your own ship and we can all make things as complex or convenient as we like. It's just good to have the community here and elsewhere to riff off of and help each other with the all the possible ways to do something. We're aren't all doing the same jigsaw.

            TheGodfather Ah, maybe I didn't make it clear. This is when the developer does not make app builds available themselves. This is the case with OsmAnd. It does not support pro features without play store.
            So I am forced to use the f-droid build.
            For me the order now is:

            Developer build from App source code VCS > Developer build from elsewhere > [Play Store] > F-droid

            5 days later
            4 months later

            TheGodfather Hi, so is it right, that the Apps in tje izzyondroid repo are exact the versions from Github? But with that repo it is not necessary to manually load updates via github?
            That would be great!

            Using your install routine sound good, too!

            Best regards?