30 results found
-
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.
10 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 -
1 vote
-
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.
5 votes -
Remember sort order for remote config view.
Remember sort order for remote config view so you don't have to change the sort every time the console page is refreshed.
1 vote -
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
12 votes -
Allow Events with Reserved Names as A/B Test Goals
We have several events with the prefix "Firebase_" for irrelevant reasons. These events were successfully added to Google Analytics by sending them via mParticle.
We can view statistics for these events, but we cannot use them as goals for A/B tests. The UI displays the following error:
"Error: Error saving experiment: Can't validate experiment data."
The server response states:
"Cannot use reserved event name: '<event name>'."The suggested workaround is to create new events with non-reserved names based on these existing events. However, there are limits on the number of events you can create, and this adds unnecessary work.
Since…
1 vote -
Option to clear remote config locally stored data
Remote config fetched values are not encrypted and it's kept as plain text. Is there any function that can be used to clear this data after a successful fetch? At least we can keep the data safe on our own if there's a way to clear the local file content. I know currently it keeps the last fetched time in the same file but a clear function can clear all values except values like last fetch time. Will be very useful for those who want to use remote config data securely
1 vote -
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…
48 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
3 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
4 votes -
A/B Testing with Remote Config for Web
It would be useful to allow creating A/B tests based on Remote Config for the web platform, since Google Optimize is going to be sunset later this year.
68 votes -
Provide an option to only deploy new parameters
Consider the scenario where you create a new Remote Config parameter in your template.json file and deploy it via the Firebase CLI to TEST and PROD environments with a default value. You then modify the value in PROD via the Firebase console. The next time you deploy Remote Config to PROD the value is overwritten. It would be useful for CI/CD deployments to have an option that would only deploy new parameters and would NOT overwrite the values for existing parameters. This would allow you to structure your template.json file to have default values for new non-PROD environments without having…
1 vote -
Add real time support to the Firebase Javascipt SDK for Remote Config
Real time fetches are currently supported for all platforms except the Javascript SDK. I'd like to be able to fetch in real time across all of my apps: iOS, Android, and Web.
36 votes -
Remote Config Emulator
Provide a native emulator for Remote Config with A/B tests will be great, but is not critical.
5 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…1 vote -
2 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.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
1 vote -
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…
3 votes
- Don't see your idea?