Publish to F-Droid

[robertgzr]

https://f-droid.org/en/docs/Inclusion_How-To/
https://f-droid.org/en/docs/Submitting_to_F-Droid_Quick_Start_Guide/

[davecraig]

Hi,

Thanks for creating the issue, I already took a quick look yesterday at what issues there might be. Currently we use Firebase and com.google.android.gms.location location providers, both of which we'd have to remove in order to be accepted by F-Droid. We also use FMOD under their Non-Commercial usage license, but we don't have access to the source and so that also causes a problem with F-Droid inclusion. These aren't insurmountable, but at this point I think we have to aim for completion of the app for the PlayStore audience first before moving on to the work required for F-Droid.

Thanks,

Dave.

[davecraig]

Actually there's another tougher issue, which is that it's not possible to have any 'secrets' within F-Droid apps. Soundscape is free to use, but we do have server costs and preserving the use of those servers so that they are only used by our app is only fair to our funders. If another app decided to use our mapping and geo-search that would cost us real money and so we prevent others from using them via 'secrets'. It's not clear how we could maintain this model whilst still making the app available on F-Droid - any backend scheme that I can think of e.g. rate limits, quotas, would mean that the servers could still be used by any other app and we wouldn't be able to distinguish between them and Soundscape.