35 results found
-
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…
50 votesWe are considering this feature; however, we would like to connect with you to understand your needs a bit better. Please sign up here to register your interest in connecting with us for a feedback / product deep dive session.
-
Increase the size of remote config from 1MB to 10MB
Why not increase the file size for remote config? Right now it only holds 1MB of text, but if you zip a 1MB plain text file you can reduce it to 100kb or less. So, why not increase the configuration size to 10MB?
1MB remoteconfig.json ==> compress file ==> 80kb remoteconfig.zip
14 votes -
Trigger Functions on changes to server side Remote Config
Currently Functions (gen 1 & 2) support triggering only on changes to the client side Remote Config. Being able to trigger functions on updates to the server side Remote Config is important to maintain feature parity with the client side support and also has many generally helpful use cases.
13 votes -
Remote Config Emulator
Provide a native emulator for Remote Config with A/B tests will be great, but is not critical.
13 votes -
Remote Config rollouts conditions for firebase-admin
Recently there was the inclusion of remote config rollouts. Rollouts were introduced to the REST API documentation under the RemoveConfigParameterValue as seen here: https://firebase.google.com/docs/reference/remote-config/rest/v1/RemoteConfig#RemoteConfigParameterValue.
But the same isn't true for the Firebase-admin package https://firebase.google.com/docs/reference/admin/node/firebase-admin.remote-config.md#remoteconfigparametervalue.
Would be interesting to have the types that are now available under the rest api to also be available on server side libraries so the usage of rollouts wouldn't impact current implementations that make usage of firebase-admin
7 votes -
Create Firebase A/B Testing Experiments through Firebase API or Firebase SDK
Create Firebase A/B Testing Experiments through Firebase API or Firebase SDK
Please provide some provision to create A/B testing experiments programmatically. Apart from Firebase console, it is good to create A/B testing experiments through API or SDK or any other way?
Please check.
7 votes -
Remote config API
use remote config firebase API to open remote config AB tests in an easy way from in house systems.
7 votes -
Remote Config conditions for Web Preview Channels
It would be great to be able to have different remote config configurations (e.g. feature flags) for different preview channels.
This is important to be even able to use/test/QA the preview channel build if we don't want to rollout the feature globally yet (mostly in the last stages of development).Note: For native apps we solved this by using specific version numbers (that are used only for preview builds), but for web apps the version condition is greyed out.
7 votes -
Allow For Different Rollout Percentages
Currently, the highest allowed rollout percentage is 50% (before going to 100%). While we understand that higher percentage won't allow to compare the groups correctly, having an ability to gradually release a feature from 50% to 100% would be a very nice and common requirement.
6 votes -
Remote Config create nested groups
We should be able to create groups inside groups to create a clean hierarchy and looks. As the app gets bigger, configuration gets bigger as well. Currently you are left to "Control + F" and scroll among hundreds of config variables to find what you are looking for
6 votes -
Remote Config REST API Improve Documentation
For the Remote Config REST API, the documentation is fairly ugly around how to go about safely getting a valid ID token for a user to be able to use it. I'm suggesting you put the Remote Config API behind a set of user rules, similar to other Firebase technologies. If that cannot happen for some reason, then one of two things should:
There should be some sort of option in Remote Config or Authentication to automatically give new users a valid credential that allows them to only retrieve the Remote Config (perhaps it automatically creates a Service Worker Account…
6 votes -
Simultaneously adding multiple configurations to a/b-experiment
I would like to be able to add multiple configurations to experiment a/b at once that have been previously selected or marked. Or create an experiment based on multiple selected configurations.
Right now, if you add configurations manually, you have to do it one at a time.5 votes -
Remote Config should be protected from man in the middle attacks
Currently Remote Config can be sniffered and there is no option to configure protection from "man in the middle attacks" in client side.
The best solution is to add support of Certificate Transparency.5 votes -
A/B Testing is limited to 24 simultaneous experiments.
A/B Testing is limited to 24 simultaneous experiments. I want to run more experiment. How to increase the limit for concurrent experiment. Also I want to target all the users in same experiment (App= Android & iOS)
5 votes -
4 votes
-
Remote Config fetch data from only selected groups
Current data fetch is not filtered at query level and all of your config fetches to your frontend. This means for example, IOS app fetches IOS, Android and Web config if all apps fall under the same project.
4 votes -
A/B testing and Conditional Rollout on event params
Currently, Firebase allows A/B testing to be created on the remote config parameter with the optimization metric on any event being fired on the Firebase Analytics. Unfortunately, it does not allow the metric to be one of the event_params sent on that event. This limits us in running refined experiments on certain attributes.
Secondly, A/B testing and conditional rollout do not allow the creation of refined conditions on the basis of event parameters. This limits further in creating rolling out a feature in controlled manner
4 votes -
Add support to document Why change was published
There should be an optional note field when publishing changes to explain why these changes to the config were published. Moreover, it would be great to have a simple history view of what changes were published with notes.
Right now, we can only see WHEN and WHO published the latest changes, but we don't know WHY
3 votes -
Improve RemoteConfig conditions documentation
Documentation about conditions for iOS and Android is lacking proper description for semver logic on parameter 'AppVersion'
It seems that the condition properly evaluate operators
>
>=
<
<=
when the app version is a semver string i.e. 1.18.10 > 1.18.2but the documentation states that above operators are only working with numeric values :
"...
For string values:
exactly matches,
contains,
does not contain,
contains regexFor numeric values:
<, <=, =, !=, >, >=
..."The logic behind semver is very important and specific.
To use it safetly we really need to be sure that the comparison is…3 votes -
Multi-line strings when A/B testing
In firebase remote config you can have a multi-line string (ie have new lines), but as far as I can tell this isn't possible when setting up the variant in an A/B test this means we can't make small A/B test changes to multi-line text
3 votes
- Don't see your idea?