Would you recommend Growthbook to be used for perm...
# announcements
m
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
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
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
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
the projects are just a way to organize features in the platform, the feature calls will return all the features per environment
๐Ÿ‘ 1