Fabric.io - what do you think?


#1

What do you think about using https://get.fabric.io/ in apps in general and especially for f-droid listed apps? Should we use it for app development or better try to prevent its usage?

Thanks for your opinions.
Rapha


#2

This is proprietary software, apps using it cannot be included into F-Droid main repo.


#3

Oops, I didn’t even notice that. I started contributing to https://github.com/Piwigo/Piwigo-Android and have seen, that fabric libs are used, so I decided to ask. I would also be interested in comments about other non-free dependencies in there, as I am also new to Android development it is hard for me to see all those suspicious things.
Chrashlytics I also identified as worth removing…

I am only willing to contribute to this app if it is fully free, so I am happy to get some help to see what needs to be cleaned up!


#4

And another idea: in case a project wants to use non-free libraries like Crashlytics in its PlayStore variant and still have a parallel version without, can anyone give advices to configure gradle scripts to support both, while f-droid will build the free variant?


#5

I did not have done this in the past, but searching for examples on GitLab is relatively easy. If you find out more about this, you’re invited to updated the F-Droid docs about this topic :slightly_smiling_face:


#6

You want to look at Gradle build Flavours:

https://developer.android.com/studio/build/build-variants.html#product-flavors


#7

Ok thanks. We now have a dedicated flavors
googlePlay and floss in which we replace the calls to nonfree libs by stubs. Is this enough? Or are there any conventions for f-droid in such cases e.g. for the flavor names?


#8

The flavour name is mentioned in the build recipe. Most apps use floss, foss or fdroid I guess.


#9

So with floss (what we use) it is fine, thanks @Bubu


#10