Page MenuHomePhabricator

Use a Random number (instead of UUID) for feature flagging.
Closed, ResolvedPublic


Our current system of feature-flagging and a/b testing relies on the last digits of a UUID that is generated upon first launch of the app. (i.e. We rely on the UUID to be a random number, with a "granularity" of 1 in the last digit, so that we can take a modulo with another number for a/b/c/... testing)

HOWEVER: it turns out that the UUIDs that are generated in the field seem to have a granularity of 4, which breaks any feature flag that relies on modulo <=4.

It's better to switch to a simple pseudorandom number generated upon first launch, and use that for feature flagging.


Related Gerrit Patches:

Event Timeline

Dbrant created this task.Jun 9 2015, 1:19 PM
Dbrant raised the priority of this task from to High.
Dbrant updated the task description. (Show Details)
Dbrant added a subscriber: Dbrant.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 9 2015, 1:19 PM

Change 216973 had a related patch set uploaded (by Dbrant):
Use random number instead of UUID for feature flagging.

Change 216973 merged by jenkins-bot:
Use separate random number for feature flagging, instead of appInstallID.

Dbrant closed this task as Resolved.Jun 23 2015, 2:25 AM
Dbrant claimed this task.