Show HN: Ablator – Switch features on or A/B test them inside your app

Re:Show HN: Ablator – Switch features on or A/B test them in... by CodeWriter23 on Saturday September 09, 2017 @06:06PM (#15209402)

Two things. In response to your request for suggestions, maybe a little more explanation about how it works. For example, does my code have to manage the dispatch to the "flavor"? Or is this in the client-side ablator libraries.

Second, this is a feature question or suggestion. Does the client side library track exceptions or have a way to report errors in a particular "flavor"? Or how does one decide to increase the roll out coverage of a new feature?

[ Parent | on HN ]

Re:Show HN: Ablator – Switch features on or A/B test them in... by breakthesystem on Sunday September 10, 2017 @06:37AM (#15211626)

Thanks, I'll clear that up in the copy! But in short, the ablator server decides which user gets whic flavor. Right now, this happens randomly, but I'm thinking of adding more rules in the future.

Exception tracking is not built in, but you could use something like sentry, and send the flavor value as metadata.

[ Parent | on HN ]