Remote Config for server side
Remote Config is extremely powerful, but to have the same features for server-side feature flagging and A/B testing we have to use something like LaunchDarkly which is a. Expensive b. Another set of SDK & libraries to add to both frontend and backend.
Where Firebase provides remote config, A/B testing, and personalization with the power of Google Analytics and Google's ML capability I think it's obvious Remote config Admin SDK will provide a significant benefit. Since analytics and remote config is already used in frontend it's a no-brainer to add them to the backend and provide a seamless end-to-end user experience.
Debkanchan Samadder
shared this idea
-
Dennis Kugelmann commented
This idea might be resolve now with the introduction of signals:
https://firebase.uservoice.com/forums/948424-general/suggestions/48435848-add-support-for-remote-config-conditions-on-server -
It's nice that custom signals now allow you to provide custom conditions.
It would be nice if you could, across the front end and back end, enable the same experiments for users.
Also for consistency sake when users sign-up on a different device they should be put into an experiment again if they were on the other device.This could probably be achieved by allowing us to provide a user identifier on each device to tailor which experiments are enabled for users.
With client and server Remote Config this gets more important.
-
Jen Harvey Hugg commented
Good news -- this has been launched in public preview and the team would love feedback!
https://firebase.google.com/docs/remote-config/server
https://firebase.google.com/docs/remote-config/solution-server -
Mark Goho commented
It was just announced at Google I/O that Remote Config would become a "full stack" feature flagging solution. So I think this one is "planned" or "started".
-
Philipp Bauer commented
Related Github issue:
https://github.com/firebase/firebase-js-sdk/issues/2242