Would you recommend Growthbook to be used for permanent toggles that you might want in an application (like a killswitch for example. that might need to be based on market, operating system or affect all users) or would you say itโs more suited for temporary ones to use when rolling out a feature or such? ๐
f
fresh-football-47124
06/21/2022, 7:09 AM
It's suited to use as permanent toggles, as there is no required API call, the feature lists can be cached to ensure app performance
๐ 1
fresh-football-47124
06/21/2022, 7:11 AM
If you're using GrowthBook as permanent toggles as well as more temporary ones or with A/B tests, you might want to make a separate project to keep things organized
๐ 1
m
miniature-agency-3305
06/21/2022, 7:19 AM
Yeah thatโs a good idea, thanks for your help ๐
Can you use two different GrowthBook projects in the same code?
Do I just have two different providers for it then? (React) ๐
f
fresh-football-47124
06/21/2022, 8:03 AM
the projects are just a way to organize features in the platform, the feature calls will return all the features per environment