Friday, November 28, 2014

Two apps, same functionality but different branding? (Product Flavors?)

There isn't anything like Product Flavours, but here's how I do it:


Put all your code in one (or more) project, and have separate solutions for your different app versions. These solutions can just contain the images, package info, resources, etc. for that 'brand', and the code will come from simply importing the project you keep all your code in.


Being a Universal App shouldn't make a difference - just have a separate Universal solution for each brand, and reference the shared code project as usual.


You could possibly have one solution including multiple brand projects (containing only data/images/etc. for that brand), then only enable the project for the brand you want to build the app for.


And if your branding is simple (i.e. not much graphics or large amounts of data) you could include it all in the same project/solution or perhaps use conditional compiling. I have an app with multiple brandings and all the data is kept in a single data file (the user can change the 'branding' at runtime, which changes the colours, online data sources, etc).




I'm a self-taught noob amateur. Please take this into account when responding to my posts or when taking advice from me.


No comments:

Post a Comment