Can you supply a build for fdroid?

[agardener]

Can you create a build for the fdroid opensource repository? I use an alternative android OS which does not ship with the playstore. http://fdroid.org is the goto opensource package repository. I see you also offer a APK for download which I will use for now, but it would be nice to not have to enable 'developer privileges' on my device. Also this will make it easier if you build any updates. Thanks for your help!

[puerile]

thanks for the suggestion, we'll look into it!

[feilen]

This would be a fantastic addition!

[heyakyra]

This depends on #34 to be completed

[nicolasmaia]

@Rudloff can you see any blockers here? (apart from licensing)

[Rudloff]

The repository contains a prebuilt JAR file. F-Droid does not allow that.

Also, the app uses Crashlytics which is a non-free library.

[LilithWittmann]

OK we heavily rely on TarsoDSP and it will be really hard to build this by ourselves. Regarding crashalytics, it's really helpfull for bugfixes, so I would prefer to not remove it.

But at least I added a license.

[feilen]

You could throw together a F-droid repo of your own in the mean time, it just wouldn't quite reach the same audience, so I'm not sure how useful that'd be.

[nicolasmaia]

@LilithWittmann there are other free analytics software you might want to check out :)

[LilithWittmann]

Would it be an option to just have an f-droid branch?
But if the TarsoDSP lib is really the issue, than that would be pretty hard. (OK I have since 3 years the plan to rewrite all the TarsoDSP stuff but because of lack of time and money, I didn't manage to do it… :-/ )

[LilithWittmann]

@picsi any recommendations for something easy to integrate that I don't have to host by myself and that has similar capabilities for tracking crashes?

[Rudloff]

Instead of a separate branch, we encourage app author to add a build flavor that builds the app without Crashlytics.

[LilithWittmann]

@Rudloff but a compiled jar in the repo would be still an issue right?

[Rudloff]

We can have our build recipe remove the JAR from the repository and rebuild it from source before building the app (so we are sure it corresponds to the provided source code).
It means more work for us but it is certainly something we can do.