are there any tricks/best practices when it comes to internal/beta testing experiments (specifically for a mobile app) that people have found? For context - we are in the habit of making quite fine grain feature flags which can then be combined into a larger experiment. For example - we might have separate feature flags for a new banner we will show in the apps home screen, along with a separate feature flag for a new modal which we'll pop up for users. This gives us lots of control both in terms of releasing and experimenting - we can easily toggle of certain things if they're broken or causing issues without requiring a fresh release. However - as this scales it makes our own internal QA/UAT process difficult. Right now i have 10 different feature flags that are part of a single experiment that i've configured. It seems like if i want to let my team test this i need to go feature by feature (10 times) and add a rule to toggle on/off for the saved group we created for our team. I'd love to know any tips/tricks or what i might be overlooking as i'm sure there are better ways to accomplish this.

Hi Lee

Thanks Graham 👍 happy to dig into our process / thinking if anyone is curious.