Improve app versioning in protonapps.com
Hello,
First off, thanks to the Proton team for having such an amazing resource for us to easily download apps from (https://protonapps.com/). I have a suggestion for improvement please.
Could you add the app version to the actual file name of all apps you allow direct download so that we know when we should download a new version of the app?
For example, Proton Pass .deb and .rpm files both have a generic name: ProtonPass.deb and ProtonPass.rpm and this doesn't help us figure out the current app version.
Adding the app version would also mean that we could then use apps like Obtanium to easily notify us of new released (I believe), keeping us all secure and potentially reducing unnecessary traffic in your website.
-
Kek
commented
Thank you D for gathering the links to some of the most important suggestions.
Obtainium and AppVerifier is the way to go, for me. I'm hoping that we can soon download Proton Authenticator and Lumo from somewhere else than Google Play Store. Preferably from Protonapps.com or from Github.
-
D
commented
100%. Otherwise protonapps.com is useless. Furthremore, the publication of apk's is highly inconsistent. Some only appear on protonapps.com (Calendar, Drive, Wallet), some only on google play (Authenticator, Lumo), some both on protonapps and on f-droid (VPN, Pass), some on protonapps and github (Mail, VPN).
Those of us on GrapheneOS often use Obtainium for .apk's. With Obtainium, the following solutions work:
(1) include the version number on the protonapps page, so we can identify when the app needs to be updated. Automated or no, right now we can't tell. It would work just as well if the version number were included in the .apk URL. That is this request:
https://protonmail.uservoice.com/forums/945460-general-ideas/suggestions/50070162-improve-app-versioning-in-protonapps-com(2) publish everything to github. Note this request:
https://protonmail.uservoice.com/forums/945460-general-ideas/suggestions/48103700-include-android-apks-in-all-github-releases(3) publish everything to f-droid. Note the following requests. This is not optimal unless you're doing reproducible builds and keeping your own keys.
https://protonmail.uservoice.com/forums/945460-general-ideas/suggestions/47229965-publish-all-android-apk-to-fdroid
https://protonmail.uservoice.com/forums/945460-general-ideas/suggestions/47173612-official-f-droid-repository