Android support

[kra-mo]

Status

• An APK builds and is available in Releases.
• Publishing to the Play Store brings with it a fee of ~25 USD. (Please donate!)
• Publishing to F-Droid could be valuable.

[licaon-kter]

F-Droid thoughts:

• publish the APKs directly. not a ZIP
• Signer #1 certificate DN: C=US, O=Android, CN=Android Debug: generate a proper key, keep it safe, read: https://f-droid.org/2023/09/03/reproducible-builds-signing-keys-and-binary-repos.html
• your APKs have DependencyInfoBlock so apply this fix: https://gitlab.com/fdroid/fdroidserver/-/issues/1056#note_1218193185
• put versionCode here: https://github.com/kra-mo/sly/blob/v0.2.2/pubspec.yaml#L5 eg. version: 0.2.2+1
• setup per-ABI versionCode to have the arch number at the end, eg. for versionCode 1 you'll have arm64 APK with versionCode 1002 not the current 2001, up to 3.19.x it was as easy as: https://github.com/MateusRodCosta/vidya_music/blob/v1.4.0/android/app/build.gradle#L107-L127 but starting from 3.22 it's like this I guess: https://github.com/lollipopkit/flutter_server_box/blob/v1.0.1034/android/app/build.gradle#L104-L113
• have the Flutter version easy to find, not just https://github.com/kra-mo/sly/blob/v0.2.2/.github/workflows/ci.yml#L30 an ever changing stable, eg. static version that one can grep

[kra-mo]

Thank you, I will apply your suggestions :)