Do you have specific improvement suggestions for copy, or should I just get some people who are good with this and ask them for help?
The all users thing is a nice idea. I'll have to think a bit about how it implement this.
Do you have specific improvement suggestions for copy, or should I just get some people who are good with this and ask them for help?
The all users thing is a nice idea. I'll have to think a bit about how it implement this.
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?
Exception tracking is not built in, but you could use something like sentry, and send the flavor value as metadata.
"Ablator is a Service that enables you to roll out functionalities in a controlled way, and perform good A/B testing."
To: Ablator enables you to roll out features in a controlled way and measure their impact.
I'm sure this can be improved and once you gain traffic you can use your own service to optimize it, but I like to use the language my audience uses (features v functionalities) and strip out unnecessary parts
Btw, I created an issue for that at https://github.com/ablator/ablator/issues/95