"Split gives me a lot of confidence in our releases as we are able to customize our rollouts, and even roll back quickly if needed. It also allows us to target certain segments that we’d like to release to prior to others.”
"Without Split it was hard to time the release of our web app, API, and mobile app – given app store approvals. Now we can group a change behind a feature flag, do a production dry run, and toggle it on for users."
"Before Split, our feature releases were cumbersome and time-consuming, requiring our product managers to make special requests to developers every time we wanted to launch new functionality."
“Split’s Azure DevOps integration has simplified our workflow by allowing our developers to create new flags directly in the boards. The linkage between work items and feature flags is a big plus because it streamlines the process of knowing when all work is completed for a single feature, helping us save time, increase our speed-to-market, and ensure a drama-free release.”
"Split has made us more confident in our release process and also more confident in our data decisions."
"As we improved our checkout process relying on Split to measure the impact of our changes, we saw an overall increase in conversion year over year, and that’s made a huge difference on our bottom line."
"Split’s full-stack experimentation platform has been built with engineering and product teams in mind. Its robust architecture and rich feature set integrates into our internal platforms and helps power experimentation across our entire engineering organization."
"It’s powerful to think about all features launched before Split and how many of those must have cost us money that we don’t know about."
"The system is very reliable, it has a good number of integrations already in place and works nicely with CDPs. The support team is amazing and they answer questions in a very timely manner. Also very helpful are the governance tools. The python Admin API has also been very helpful in organizing experiments and building tools around Split.io's service."
"Split's controlled release capability provides us a non-disruptive and dynamic way to ship features for testing and deployment. More importantly, it provides the data we need to quickly iterate on our product features in an informed manner.”
"Split gives us an easy and fast way to pull the plug if something goes wrong without a heavy involvement from engineers."
"At the point engineers make deployments live, they want to understand how the features are performing, from a customer experience, user value, and system standpoint. We know that one of the big challenges developers face in understanding impact is how to get all of the data in the first place. Together with Split, we can now make that easy."
"One of our first experiments was a great learning experience. It prevented us from introducing something that we thought was good, but actually would have likely given us a negative impact. We’re now doing another iteration to get it right."
"We use feature flags and run experiments a lot more because it’s easier now with Split. We can target a random sample size. We can increment the size of that sample really easily, and we can toggle it off immediately if there’s an issue."
“If we built this in-house, most engineers would look at this and say ‘feature rollout, it’s not that hard’. But when you think about having multiple environments, having a UI, conditional filters, an impression data pipeline, all that—it’s a whole team working for a very long time to be able to do all of that.”