May I ask what specifically you found frustration with LaunchDarkly?
I paid for some tier, didn't like off-prem, v1 didn't have vairant (was bool only), upgrade to v2 was bumpy, their php-client did some odd stuff (background shell_exec) the support didn't even know about.
CEO was nice enough, refunded some of my money.
The only thing I can think to suggest by way of improvement is some fairly prominent examples of the kinds of segmentation you can do with Flipt.
Do you see this being used for A/B testing as part of a pro version?
I agree I need some better examples/documentation on how to do A/B/n segmentation. Will work on that ASAP.
Thanks again for the feedback!
I know that it has been done (ex: Sidekiq has OSS, Pro and Enterprise versions).
My thought was to maintain a private fork for the pro version and continuously merge in changes from the OSS version, as well as add back any features into the OSS version that could be beneficial to everyone from the pro version.
But this does sound messy.. would love to know how others have done this in the past.
It would mean more work spelling all that out to your users, but you would make up for it by not having to hide/separate code as much. You'd have to be comfortable with 'showing all your code though.
-- offtopic: I'm working on something similar as well, but Toggles/Feature flags is "one of the parts" of the solution ( it's more a full blown development tool for handling settings, centralized services (eg. e-mail) and much more -> Eg. a support tool with forms which can be prepared by devs)
It's currently only dotnet ( and MVC) based though, but it's working.
Would welcome any feedback.
