Nice product guys! When we evaluating this, I have a little suggestion about adding override rules. I found when I add new override rule, it seems like being taken effect immediately. better to default

disabled

or add an option when added new override rule to control. So that we can enable the change after we adjusted the rule order and being confident before it take effect.

you would like the rule to be disabled, or change the flag to be disabled?

We're adding the ability soon to have separate rules for dev and production. Would it solve this issue if you first added a rule in dev and once you are happy with it, copy it over to production? Or would you still want it to start disabled?

you would like the rule to be disabled, or change the flag to be disabled?

Just change flag to not make it take effect is ok.

Not sure if it’s useful. Firebase RemoteConfig is using a “draft” approach. After several changes in both “features” and “rules/conditions” one will have to publish all changes or discard them. See screenshot.

Cool~ that also works. it should be a standard way for solving this.

Yeah. That's another good approach. We'll think through the different options and figure something out.