23 results found

1. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. 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.

   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… more

   45 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   5 comments  ·  Remote Config  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. 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 to always update the template.json values to match current PROD values before each deploy.

   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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Remote Config  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. 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.

   63 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   7 comments  ·  Remote Config  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. 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.2

   but the documentation states that above operators are only working with numeric values :

   "...
   For string values:
   exactly matches,
   contains,
   does not contain,
   contains regex

   For 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 implemented as intended and documentation should describe it properly the implementation details.

   We really need semver comparison, otherwise simple matching on string is not useful to provide conditions based on AppVersion.
   At the same time we don't want to use because it works now with the risk it may change in the future because is not described in the docs.

   Please describe if the semver is implemented as intended to clear doubts.

   🙏

   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.2

   but the documentation states that above operators are only working with numeric values :

   "...
   For string values:
   exactly matches,
   contains,
   does not contain,
   contains regex

   For 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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Remote Config  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. 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.

   29 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  Remote Config  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. 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

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Remote Config Emulator

    Provide a native emulator for Remote Config with A/B tests will be great, but is not critical.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. 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:

    1. 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 in IAM and generates the JWT for you, which it then returns and shows the user in their config json?). You suggest doing this via a Cloud Function, but many projects won't be on the Blaze plan (and can't), but this would still be useful for them. I know it's not much to ask to switch to Blaze for this, but then they also have to implement the Cloud Function and figure out how to do it for all authenticated accounts because there's no extension to set it up, which there should be (maybe that's a second request here).

    2. At least improve the documentation so that it's a lot more straight-forward to create a Service Worker Account in IAM and then generate a valid JWT for that SWA (I think it should be automatic and you should just be provided with it). I had to go through more than 10 steps to figure out how to do that, and the Firebase help person couldn't figure out an easier way to do it either (he just repeated back a bunch of the links I sent him to ask for help). Part of the issue is that the site you've selected to create the JWT is either different from when the docs were originally written, or it simply never worked and the person who wrote the docs was taking an extra step or two to make it work that aren't documented.

    There's also no indication after creating the JWT how to store it, which obviously is not up to you good folks, but the question I guess is whether or not letting it become public is secure. I know letting your private key become public isn't, but I wonder about the resultant JWT. With many applications that use the REST API, they are not encrypted in any way at rest, and so you end up having just an open JWT token that can be used with any permissions the SWA has - my GodotFirebase library being the primary example I can think of. I have mine locked down to just the RC read permission, but still, others might not know how to do this stuff inherently and make mistakes.

    Edit: I just realized that the Service Worker Account approach is really only intended for server-related work, which means it won't even work for my scenario. The documentation REALLY needs an update to make that clear. Now I have to suggest that if my users want to use my completely free and open source library, they have to go Blaze Plan and create a whole Cloud Function, and I have to supply the Cloud Function so they can automatically add Remote Config permissions to their user IDs that get returned. This is so, so ugly.

    Edit 2: I just realized what my issue is. I don't have access to the new Installations API through REST. Is it possible to allow that? That way, at least I can get an appropriate token to be able to send to the API without having to store the token somehow on my device, or force my users to use a Cloud Function and have to go paid while removing their ability to use A/B testing (the Admin SDK only returns the default template).

    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:

    1. 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… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Add support for Remote Config conditions on servers

    It's really nice to see Remote Config to come to the servers.

    For us it would be crucial to be able to use conditions in Remote Config on the server as well.

    Specifically we are looking at targeting by user properties (these could maybe be loaded and passed by us during evaluation).

    e.g. serverTemplate.evaluate({userProperties: { .. } })

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Possibility to download detailed report data on Personalization (value exposition etc...)
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. 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.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Remote config API

    use remote config firebase API to open remote config AB tests in an easy way from in house systems.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Send A/B Experiment name and User group along with values

    Unfortunately it seems impossible to determine on client side whether user is involved to test or in which group he is. It will be great to receive such data along with the value.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. 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)

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. 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.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close