docker-phoenix-example VS growthbook

- https://github.com/nickjj/docker-phoenix-example

I updated my example Docker / Phoenix app from 1.6 to 1.7 this morning.

I put it all into 1 commit: https://github.com/nickjj/docker-phoenix-example/commit/3733...

There were a number of things not covered in the upgrade guide. Lots of small changes between what the new app generator provides, csrf tokens being set in a different way, etc..

If anyone is interested I updated my example Docker / Phoenix app to use 1.6 along with using HEEx templates, that's at https://github.com/nickjj/docker-phoenix-example.

Here's a link to a fully working set up: https://github.com/nickjj/docker-phoenix-example/tree/main/assets

Why did we choose GrowthBook?

I would not adopt a platform that did not support exclusions. I think you should create a marketing page explaining the ways you are superior to the competition. Right now I would pick https://www.growthbook.io/

Seems that no-one mentioned my favorite feature flagging + A/B testing open source tool: https://www.growthbook.io/

Currently have the task of spiking a technical setup for A/B testing within our team application. I've already been looking at Growthbook and react-ab-test, what other tools / sources of info do people normally reach for in their own experience?

What are the differences to Flagr, GrowthBook or Flagsmith?

I work in the marketing analytics field, so I'm not that deep into product (even though I'm dabbling and will jump at the opportunity when one presents itself). Feature flags are being used to roll out experiments. Essentially, you publish code/experiments to the app source code, and based on the flag it shows a control or variant. The flag is fetched from a server and the rollout can easily be disabled if issues crop up. https://www.growthbook.io/ is an open-source tool that seems to be getting a bit of traction.