Product Flavours and module dependency

Updated 18 December 2016


Product flavours are easy to implement once you start but the major issue android developers get is when they have to add one or few of the flavours to another module as a library dependency. Library dependency is an essential feature and every developer needs it once in a while. So how we will implement it with product flavours? How we will command our IDE to add this flavour and not this one?

Actually android developers have a solution for this also. The solution is a Compile setup in which you define/ compile only those library product flavours you need in your module.

Suppose I have two flavours flavour1 and flavour2 , now I had a higher level module app in which i have to add flavour1 as library. So the library’s build.gradle will be like

As you can see in the above file we have mentioned

Its because by default a library only publishes its release variants. So to enable the publishing of more variants we used this. You can read more about it here.

And your app’s build.gradle should be like this,

And this will add only flavour2 to your project. You can add more than one flavour , you just need <yourFlavourname><Debug/Release>Compile as your configuration.

. . .

Leave a Comment

Your email address will not be published. Required fields are marked*

Be the first to comment.

Start a Project

    Message Sent!

    If you have more details or questions, you can reply to the received confirmation email.

    Back to Home