Open source feature flagging and experimentation platform for stress free deployments, measured impact, and smarter decisions.

GrowthBook Users

Hi Jeremy, we have a few methods to avoid flickering <https://docs.growthbook.io/experiments#avoiding-flickering|here> including a white overlay&lt;.&gt; However for the best performance and flicker-free experience, we recommend using the <https://docs.growthbook.io/lib/edge/cloudflare|Edge SDK>.

Thanks <@U0758Q1HRCK>! I started working with the Edge SDK, but I don't have it implemented yet. I'm not sure if I'd want to always use the Edge SDK because I have some tests that only change a small part of the page. The rest of the page can be served in the initial static render while the component using an experiment can load later.

Overall, I was just wondering why GrowthBook returns the a value  based on just the feature flag initially, then later it will return the value based on the experiment?

I found the `useExperiment` hook, but it does the same, initially returns `false` until `trackingCallback` fires, then it returns `true` based on the experiment.

Just a follow up here, looks like this is an issue on my side and a late attributes update. Not a GrowthBook issue :sweat_smile:

Hi Jeremy, good morning. super glad to hear all is now resolved and thank you for the update :rocket: