"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."
“By decoupling experimentation decision-making from engineering Resources [with Dynamic Configuration], product teams become empowered to make fast and flexible changes to the product with little to no technical knowledge.”
“If we build it we have to test it to make sure it’s doing the right thing. When we conduct backend experiments, we have to know the system will remain reliable. We have to make sure the backend behaves in a way that doesn’t impact the user experience.”
"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.”
"With Feature Monitoring, our engineering team can deploy rapidly while ensuring that new functionality won’t negatively impact our core KPIs such as page load time and errors per user."
"90% of our changes are behind a split (feature flag)."
"The kill button is super easy. Now I just, ‘whoop’, kill it. If we are seeing something wonky, it makes it so easy to turn off. When we’ve triaged the feature we can go back and re-enable it."
"Split has made us more confident in our release process and also more confident in our data decisions."
"Split has been instrumental in our push to true agile processes. The ability to divorce deployment from release via feature flags has had an outsized impact in our ability to deliver new products to market faster than our competitors. With the addition of configurations we can externalize values and settings in split directly allowing our product team to pivot quickly and make changes immediately.”
"Split has enabled us to move much faster. We can ship code straight through to Production knowing that our users won’t see it until we’re ready to show them.”
"Using Split with FullStory allowed us to humanize our experiments and empathize with our customers by validating the quantitative results with real user sessions that revealed how customers felt when interacting with our features."
“The integration with Amazon S3 helps us track all the events that happen offline. In our case, an example is someone investing money on our own bank account. That cannot be tracked through Segment, but we obviously aware of when someone sends us the money. An integration with Amazon S3 means that we can simply provide a data feed to our S3. Importing the data into Split and then being able to see how many people deposited money and how much they deposited in all the features that we have or we are A/B testing.”
"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."
"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."
"Split gives us an easy and fast way to pull the plug if something goes wrong without a heavy involvement from engineers."