I have an Android project where a single codebase is being used for different clients. I have created a flavour for each client. Now each client supports different environments such as release, staging, dev. This is managed through build variants.
Here is the complete relationship:
1 project -> Flavour 1 -> client 1 -> variant 1 -> 1 Dev
-> variant 2 -> 1 Staging
-> variant 3 -> 1 Release
-> Flavour 2 -> client 2 -> variant 1 -> 2 Dev
-> variant 2 -> 2 Staging
-> variant 3 -> 2 Release
-> Flavour 3 -> client 3 -> variant 1 -> 3 Dev
-> variant 2 -> 3 Staging
-> variant 3 -> 3 Release
and so on...
Now each variant has a unique application id, as an example:
client 1 -> variant 1 -> 1 Dev ->
com.client1.dev -> variant 2 -> 1 Staging -> com.client1.staging
-> variant 3 -> 1 Release -> com.client1.release
Please note that all the clients share same firebase configuration.
My question is what is the best way to accommodate the current App structure in Firebase console? Should I create one project per app, or one project per environment?
In both these approaches there would be a huge number of apps which would be created in firebase console.
Is there any recommended way to handle it elegantly?
Also is there any way where in place of managing so many apps it can be managed through lesser number of apps in Firebase console and project?