Take a different path to feature flags, A/B testing and multivariate testing for mobile apps, utilizing the power of controlled release to deliver the latest and greatest to your customers without app store delays.
Learn more about Split’s controlled rollout platform.
"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." Qingqing Ouyang, SVP Engineering
But what if you have a hybrid web-mobile or mobile-only stack? Controlled release is even more important. To illustrate this, consider what happens when a critical bug appears in a newly-released mobile feature: due to App Store approval delay, a fix can’t be delivered to customers in minutes; the minimum turnaround time is days. As customers keep experiencing app crashes, their trust erodes.
Controlled release can help you deliver a profoundly better customer experience, even on mobile, but it should meet the following criteria:
This approach has a number of advantages for our customers:
First, it ensures a uniformity of experience between mobile and web. Since the web app can also query the same service, our customers can be confident that their customers will either see a feature on or off, regardless of how they access the product - via mobile or web. Thus, calling home is portable.
Second, Split is a core piece of our customers’ infrastructure that is always improving. By hosting Split on the server-side, our customers can confidently upgrade their server-side Split library, without having to worry about older, possibly conflicting, versions of Split being used in older mobile apps. Thus, calling home avoids versioning headaches.
Lastly, by hosting the library on server side, our customers need never worry about increasing the footprint of their mobile app by adding Split’s library. Thus, calling home is safe.