Skip to content

ParseConfig with A/B Testing #3148

Description

@supercharger

The SDK's ParseConfig documentation claims remote configs with A/B Testing feature. But I don't see support for A/B testing in the parse-server or the Dashboard.

Can you please let us know if this feature is implemented ( need doc on how to use it ) or if not the SDK documentation needs to be updated.

Activity

  1. flovilmart commented on Dec 1, 2016

    @flovilmart
    Contributor

    You don't A/B test your config, but you could store in your config for ex:

    experiment1 = { a: "some value", b: "other value" }

    Then in the clients read the values for those experiments.

  2. supercharger commented on Dec 1, 2016

    @supercharger
    Author

    I didn't mean A/B testing the configs. I want to use configs for A/B testings, based on user segmentation/bucket these configs value needs to be changed..

    The docs doesn't give any indication how to use it, But https://parseplatform.github.io/Parse-SDK-iOS-OSX/api/Classes/PFConfig.html says I can use this for A/B testing.

    From the client, I read the PFConfig, I will always get the same value, how to make this specific to experiment ?

    Also, In the dashboard, I only see the push segmentation, but I don't see any UI for changing the configs specific to user segmentation.

  3. flovilmart commented on Dec 1, 2016

    @flovilmart
    Contributor

    You can use the config as I explained above, then you'll need to assign your users to buckets/segments somewhere else.

    It is said you can use it for A/B testing but it's not an A/B testing framework.

  4. supercharger commented on Dec 1, 2016

    @supercharger
    Author

    You don't A/B test your config, but you could store in your config for ex:
    experiment1 = { a: "some value", b: "other value" }

    Is there a way to associate key with "experiment1" with some value to "user1" and another value to "user2", Is that supported parse , any way to make it work ?

    The Parse push notification supports user segmentation, it would be nice if this feature can be implemented too.

    Thanks for your help.

  5. flovilmart commented on Dec 1, 2016

    @flovilmart
    Contributor

    You can simply have a new column in the user table or a function that transforms the objectId into the correct experiment... I dunno, there are zillions of ways of doing that.

    Parse push notification supports user segmentation,

    When you assign a user property to the _Installation itself, yes.

    As it's not an issue with parse-server but more of a question, I suggest that you go ahead on stackoverflow for implementation details.

  6. supercharger commented on Dec 1, 2016

    @supercharger
    Author

    Yes, Thanks, But this is more of feature request. I think it is a valuable feature to support remote configs with explicit A/B testing.

  7. flovilmart commented on Dec 1, 2016

    @flovilmart
    Contributor

    Go ahead an open a pull request with that feature then :)

  8. supercharger commented on Dec 1, 2016

    @supercharger
    Author

    Yes, will be evaluating that, if I can do that in the time constraints.
    FYI, Basically I am talking about this feature, https://firebase.google.com/docs/remote-config/

    You can simply have a new column in the user table or a function that transforms the objectId into the correct experiment

    I think that can't be done for all use cases, one may not have user concept in the app, and it is just configs and associating a user is unnecessary.

  9. flovilmart commented on Dec 1, 2016

    @flovilmart
    Contributor

    So you can assign per _Installation object... Closing the convo as it's not going anywhere.

  10. locked and limited conversation to collaborators on Dec 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions