photos-app VS fdroiddata

ente - encrypted photo storage (version 0.7.92): ente is an end-to-end encrypted photo storage app

The format isn't natively supported on mobile, but we can transcode and render them. We have created an issue to track this: github.com/ente-io/photos-app/issues/1269

Hey, we've added an item to our roadmap to configure a lockscreen different from the system lockscreen: github.com/ente-io/photos-app/issues/1240

Hey, this is already on our radar: github.com/ente-io/photos-app/issues/1226

Hey, not sure how popular this feature will be, since all your metadata is end-to-end encrypted and only accessible to you, but have added this to our roadmap anyway: github.com/ente-io/photos-app/issues/1219

We don't automatically sync media movement from the device to ente, as users might have already organized their media on ente, possibly on a different device. However, we understand that this could be a valuable feature, perhaps as an album-level configuration. We've added this to our roadmap.

Hey, we recently added support to playback Motion Photos to our Flutter app.

We also wrote a guide to set it up. Our code is open source, so you can easily refer to the crowdin config and GitHub action config.

ente - encrypted photo storage (version 0.7.43): ente is an end-to-end encrypted photo storage app

Fork this repository.

For reference my app: project: https://github.com/balzack/databag merge request: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/12183

You should add a new entry in "Builds". Have a look at how Newpipe does it for each new version here for example.

To me it's not very clear whether those terms practically apply only to their app, since clearly they can't grab logs from Aurora if Aurora doesn't dump those logs for example... but if this is something the F-Droid team should look into, open an issue on https://gitlab.com/fdroid/fdroiddata/-/issues or inquire in one of their official channels on OFTC (#fdroid) or Matrix (#fdroid:f-droid.org).

OsmAnd~ from F-Droid not having Android Auto is a known bug: see the discussions at https://gitlab.com/fdroid/fdroiddata/-/issues/2567 , https://github.com/osmandapp/OsmAnd/issues/13514, https://github.com/osmandapp/OsmAnd/issues/3391 and https://github.com/osmandapp/OsmAnd/issues/15400

You can also get F-Droid Build Status which I believe will let you see apps that are being attempted to be built even if their build isn't succeeding yet, again for the "catching things early experience". Or, just keep an eye on the issues, merge requests and commits at fdroiddata which is where people actually add new metadata for new apps to be built by F-Droid, and it often takes a while between an app being first mentioned, and it being able to be included, for many possible reasons.