(DevCycle Co-Founder & CTO here) The truth of the Feature Flagging market is the vast majority of engineering teams aren't using a third-party tool for Feature Flagging. Most teams are using an internal system (Environment Variables, Database flags, S3 files ect.) or not doing any feature flagging. The potential for the Feature Flagging market is as large as any other developer tools market, and the challenge is to build a product with a better developer experience that encourages the adoption of feature flags and integrates with team's workflows.
We've been in the A/B + Feature flagging space for about ten years with our visual A/B testing-focused product Taplytics (W14), so I'd say we have lots of experience running Feature Flags + A/B tests at scale. We've learned a lot from our customers over the years and were excited to build DevCycle as a green-field project from those lessons. If you are interested, try it out and we are always open to direct feedback.
Why should I pick you, when there are so many alternatives? I have more candidates than I can try:
DevCycle,
enrolla,
FeatureHub,
Featurevisor,
Flagsmith,
Flipt,
Flux,
GrowthBook,
LaunchDarkly,
Prefab,
Split,
Unleash
100% there are some great options on the market right now and I can't imagine anyone trying all of them.
The reality is that most of the products on that list are tackling the problem in a different way, targeting their own specific niche.
I would only recommend looking at the products that resonate with your needs.
With us for example, if our focus on Developer Experience and fitting into your coding workflow resonates, that's great, you should try us out in comparison to the others that position that way.
But if that doesn't resonate and say Growthbook's focus on analytics and data warehouse connections is more important to you, you should look at them and others like them instead.
We're definitely not trying to be all things for all potential users of feature flags, but we're hoping that what we're offering matters to small teams of developers that care about embedding feature flagging into their development process
We've been in the A/B + Feature flagging space for about ten years with our visual A/B testing-focused product Taplytics (W14), so I'd say we have lots of experience running Feature Flags + A/B tests at scale. We've learned a lot from our customers over the years and were excited to build DevCycle as a green-field project from those lessons. If you are interested, try it out and we are always open to direct feedback.