![]() Usually you will have no or just a single layer of flavors and two build types and you can just forget about this post. flavorDimensions "app", "environment" productFlavors So why would you need this?īe glad if you don’t. Because I actually have two different apps, each one has it’s own unique applicationId. The basic setup is simple and I define my flavor dimensions as well as my flavors. I also have a development and a production environment, because I don’t always test my code, but when I do, I test it in development! :) Both could be some sort of RSS reader and they share the same code base. ![]() Let’s assume I have a news and a blog app. But while having different settings for every flavor is simple enough, things start to get really tricky if you introduce flavor dimensions and find yourself dependent on combinations of different flavors and build types. They greatly increase maintainability, as well as publishing updates to multiple apps gets significantly easier. Flavors enable you to have multiple similar versions of your app within a single code base, like different colors, or the common example of a paid and a free version of the same app.
0 Comments
Leave a Reply. |