Using Scenarios for A/B testing and remote configuration
Last updated
Last updated
Kiwi offers a way for you to test different behaviors on your app without requiring you to deploy a new version. With this feature you have the flexibility to do A/B testing or even delivering functionality remotely to a group of users.
Scenario provides you a way to describe app events that triggers some action and all the data that is needed for the action to be performed. It is composed of the following data structures:
Structure
Description
Parameters
Defines global configurations that does not depend on an action to be triggered.
Event Types
Defines the events that the app can trigger. This will allow you to customize the action that should be executed when the event is triggered.
Event Actions
Defines an action that should be performed after an event is triggered. The action is composed of one or more contexts that provides the data necessary for the action to be executed.
Example Use Case:
Application description: A video player app that offers free and paid content. When a user clicks on a paid content and is not a current subscriber the app displays a popup offering the user to become a subscriber and have access to the paid content.
Scenario configuration
Event Type: Non subscriber clicked on paid video.
Event Action: Shows subscription offer popup.
Action Context: popup title, subscription callout text and subscription plan to be offered.
With the above scenario you could remotely change the content of the popup and the SKU to be used on the subscription without having to deploy a new app version.
Access your application on
On settings, make sure Scenario Module is enabled.