zero
zero copied to clipboard
commitdev
A/B Testing integration
What's the scope for this feature?
- FE, BE, both?
I've generally seen this implemented at the code level; but an argument could be made that it should be centrally managed across FE and BE - at which point it starts to converge a bit with feature flagging.
Originally we wanted to keep this task separate from feature flagging as typically they have different requirements and feature sets, but if we are going to be using LaunchDarkly for the feature flagging stuff we should see how much of this epic overlaps, since they do have quite a few features that would probably meet the needs of an A/B testing solution.
