Anyone who has built a mobile app would probably agree that iterating and optimizing a mobile app is a slow process. It generally requires countless cycles of updating your app and then waiting for Apple to approve it before users can download the update and you can see whether your changes were positive. As a result, it's generally been easier to just link your app to an analytics suite like Mixpanel, Google Analytics, or Flurry and track changes over time than to actually use any of the mobile A/B testing platforms available today.
Today, A/B Testing Means Waiting for Updates
Today, mobile A/B tests must be written in code and then reviewed by Apple before your users can see them. When a platform says they allow you to push experiments without an App Store update, what they mean is that you can deliver the winning experiment to the rest of your users without an update. The real problem is that those experiments needed an update to get there in the first place. As a result, as your app evolves and you learn more about your users, you still need to do an app update to try a new A/B test.
What Should mobile A/B Testing Be Like?
Because of this limited benefit, few mobile teams actually do any A/B testing, even though it is generally accepted that testing can significantly increase conversions, engagement and retention of users. This begs the question, what would mobile A/B testing have to be like to actually get people to test on mobile? We think the answer is that it has to be dead simple, it can't require any coding and it has to maintain the performance of the app.
Introducing Taplytics One-Line SDK
We thought long and hard about the problems in mobile A/B testing and what the right platform should be and today we are delivering the mobile A/B testing platform that people will actually use. Because it is; dead simple, it requires no coding of experiments or goals, while completely maintaining the performance of your app. The Taplytics SDK requires that all you do is initialize the SDK with one line and from there do no more coding. To link elements to Taplytics all you have to do is touch, tap or click on them directly in the live app. Our SDK does all of the work for you, binding the elements to our platform and creating all of the event triggers for goal tracking.
The Nitty Gritties
If you haven't watched the video above yet, we strongly encourage that you do. It shows the open-source WordPress app running multiple variations, linking elements with just a tap and how changes can be viewed live on a series of dev devices. We clearly showed a simple test, just calls to action, position and color, but that simple test is actually quite powerful and a great place for anyone to start.
As mentioned in our previous post about mobile on-boarding, the vast majority of users are lost in the process of login. With our app you don't have to worry about taking a month to dream up a complex test for on-boarding. Because you can push tests instantly without writing code you should start small, see how positioning, messaging and highlighting elements changes the process and as you gather more information, Taplytics can scale in complexity with you.
Your simple content experiment can, with a few taps and clicks be modified into an experiment of your on-boarding flows, pushing segments of users through a different sequence of screens. The power that you can have to retain and engage your users with Taplytics is huge, but if it doesn't start somewhere simple and accessible, you will never get to the really powerful tests.
We are really excited that we can finally share this new SDK and feature set. We're also excited to see how people use this tool to improve their apps in endless ways, big and small. So please take the first step to getting more out of your mobile app by signing up for a free trial.