Consider releasing android builds through FDroid

[carsonfarmer]

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

[steelman]

Or https://f-droid.org/en/docs/Setup_an_F-Droid_App_Repo/

[Bubu]

I opened (a very minimalistic) request for packaging issue here: https://gitlab.com/fdroid/rfp/issues/750

[andrewxhill]

Sweet thanks @Bubu! We just got our first automated apk release https://github.com/textileio/textile-mobile/releases/tag/android_1.6.14_262

Since Android is still pretty beta, how is F-droid for distributing new releases? Should we wait for a bit more stability or just go for it?

[steelman]

There is (I think) a way to mark releases as unstable. Sometimes a new version appears on a list, but it's not recommended for upgrade. On the other hand you may consider setting up your own repo (see my post above) to have maximum control.

[easyKL]

We are waiting for your F-Droid release... Bare in mind that F-Droid will not be able to build when you rely on JDK or other non-free tools. Still alpha? No worries! https://f-droid.org/docs/Inclusion_Policy/?title=Inclusion_Policy Doing it throught your own repo? Also an option!

[IzzySoft]

In its current state, the app has a show-stopper:

    compile('com.crashlytics.sdk.android:crashlytics:2.9.5@aar') {
        transitive = true;
    }

That's not acceptable at F-Droid. If you really want that, we'd need a separate FOSS build flavor for F-Droid that comes without this.

[sanderpick]

Makes sense. We can probably make this configurable at build time and make two releases, one with and one without Crashlytics. @asutula ?