Publish APK files and tag releases on GitHub

[IzzySoft]

Just wondering if you could tag releases and attach the APKs to them, starting with the latest one – so that Abysner could be available to the folks outside of PlayStore as well? Thanks in advance!

[Rolf-Smit]

@IzzySoft Thanks for your interest in this project!

I understand that not everyone uses the Play Store. Since Abysner is open-source under AGPL-3.0, anyone is free to build and share APK files (as long as it’s non-commercial). Right now, my focus is on improving the app, so I won’t be prioritizing publishing APKs to GitHub at this time. If there’s enough community interest, I might reconsider in the future (maybe when the apps comes out of beta). Thanks for your understanding!

[IzzySoft]

Thanks for your swift reply! While I could build the APK for myself and sign it for myself (and as a diver, would have use for it myself), my intention was rather to add it to the IzzyOnDroid repo to make it available to other non-Googlers for easy access. At IzzyOnDroid, we always ship the APKs provided by their resp. developers (after having sent them through multiple scans). We also provide Reproducible Builds (see e.g. Reproducible Builds, special client support and more at IzzyOnDroid for some background on that) – which independently proves that your APK was indeed built from the source it claims to, with nothing added or taken away.

Running IzzyOnDroid since 2013 – and especially with the extra security measures, increased interest and all, having just a very small team, I totally understand what "have to focus" means. So thanks for leaving the issue open, even at low-prio. Once you have an APK ready at releases (signed by you, not by Google, as Google usually adds things to the APKs when signing), just give me a ping – and we can pick up again.

All the best for your development until then – and of course for you personally!