Skip to content

Feature Experimentation

Categories

JUMP TO ANOTHER FORUM

4 results found

  1. Similar to Optimizely Web, capture basic segmentation (browser, device, ...) out of the box.

    3 votes
    New  ·  0 comments  ·  SDKs  ·  Admin →
    How important is this to you?
  2. If Optimizely's CDN goes down or is inaccessible, the SDKs don't have a default fallback mechanism to evaluate feature flags without access to the datafile hosted on the CDN.

    It's possible to initialize the SDK with a cached datafile, but that requires custom logic. Ideally, Optimizely could provide a default mechanism to provide a fallback datafile (e.g., a "relay proxy" service that caches the datafile, or a default mechanism within the SDKs).

    1 vote
    New  ·  0 comments  ·  SDKs  ·  Admin →
    How important is this to you?
  3. Currently, user profile service (UPS) maintains a map of user IDs to the experiment IDs they've previously been exposed to and the variation ID they received. The SDKs continuously append to the UPS without any cleanup, even if an experiment has been concluded and is no longer relevant.

    Customers have in the past implemented diff logic to compare the live experiment IDs in the datafile vs UPS and remove experiment IDs from the UPS that are no longer in the datafile.

    1 vote
    New  ·  0 comments  ·  SDKs  ·  Admin →
    How important is this to you?
  4. Make SDKs compatible with OpenFeature standard.

    1 vote
    New  ·  0 comments  ·  SDKs  ·  Admin →
    How important is this to you?
  • Don't see your idea?