I’ve been happily doing this client project with iOnic 2 right now, now what we already expected, they are asking about making a “white-label” out of this application.
Our client has many sub brands / clients and would like to implement these exact same features just with a different skin/styling.
That being said. Is there anything going such as Flavors and Targets when building native apps?
In short I’d switch around some configs, maybe some files (Like the file I use for translations etc.), these can be dependant on config variables for all I care. And of course some images, style, icons and splash screens.
+1 for this question. I am facing a similar issue, but what I need is the ability to change the config.xml as well as the ressources folder on build time.
It would be really great if anybody had the same issue, solved it and could elaborate on a solution.
Thanks in advance
I am evaluating ionic for building an app for our multi-tenant service. We will like to publish a separate app for each of our clients. I can easily create tenant specific favor for native android app using gradle’s flavors feature. I an not able figure out how to do this for ionic apps.
As far as I can see, it’s not really that easy to make true flavours, but it would be possible to use different webpack configs for building which will build different scss files. (for styling only but also you could do something manually with loading certain files in certain webpack configs.
This is however quite a difficult process to set up but could work. You could load in certain folders based on different flavors when building your application.
I’m not going to provide an example because it’s not trivial.
For the flavours are critical, not so much for different styling, but more for the ability to put them in play store as different apps - one for each of our tenants. These will be “their” apps, that will talk to only their account in our multi-tenant application.
Well in that case you’re mostly talking about ability to change namespaces and such. You only need to edit one file for doing so (which is the cordova config.xml file). It would however be tedious to keep doing so, but a simple git branching technique will suffice if it’s only that file that gets changes.
Allthough I’m quite sure there will be tools which allow what you’re asking for. Ionic itself is a framework which runs inside an cordova app (and generates the needed cordova files), so if you are going to work with cordova anyway, iOnic should be fine. imo.
If you tier some solution even if unofficial I believe it will help many.
After some analysis I see that a good part (package name, application id, application name, etc.) of this problem can be solved with the possibility of creating config.xml, for flavors, that could be selected via parameters of build, run, etc, example: $ ionic run android --flavors=free, and config.xml could merge with base config.xml.
