Here we walk through how to use in-app to guide your users through a product or feature tutorial.

In-app message editor

​
Step 1. Select the Tutorial Audience

In order to target new users, we can setup a segment of First Session less than 1 hour. If you have a signup flow, you can use triggers to start the in-app after the user signs in. If this is a new feature, we can setup a segment for users with session count greater than 2 and Last Session less than 1 hour ago. This way we don’t show the sequence for new users that might not be ready for the new feature.

​
Step 2. Walkthrough Trigger

If there is a sign up flow for your app that we don’t want to block, we can setup the in-app trigger to fire as soon as registration is complete. Another option is to setup the trigger to go off after 3 minutes (180 seconds). If you are introducing a new feature to users that are already registered, you can also have this sequence trigger “On app open”.

​
Step 3. Create the Walkthrough

Depending on how many screens the walkthrough contains, name the message based on the sequence to find it easier (Tutorial 1, Tutorial 2, etc…). If available, gif’s are highly recommended to animate your tutorial. You can add gif’s or images to the image field or use the entire message with the background field. It is up to you to add a button or not. Generally you would not need to add a button here since clicking the image or background will also set an Action to trigger the next message. Set the Click Action Name to be representative of the next tutorial to show and dismiss the message on click.

In-app message button editor

Add the click action to the InAppMessageClickHandler along with the tigger to the next message. 
class ExampleInAppMessageClickHandler implements OneSignal.InAppMessageClickHandler {
  // Example of an action id you could setup on the dashboard when creating the In App Message
  private static final String ACTION_ID_MY_CUSTOM_ID = "show_tutorial_2";

  @Override
  public void inAppMessageClicked(OSInAppMessageAction result) {
     if (ACTION_ID_MY_CUSTOM_ID.equals(result.clickName)) {
        Log.i("OneSignalExample", "Custom Action took place! Starting YourActivity!");
        //setup the trigger to the next tutorial window
        OneSignal.addTrigger(ACTION_ID_MY_CUSTOM_ID, 1);
     }
  }
}

​
Step 4. Tutorial Finish and Repeat

Once you schedule and confirm the message, you will repeat the process for the rest of the tutorial messages using the same audience segments. Make sure to change the trigger to be the name of the Action ID set in the previous message. In this example, the second tutorial message will have a trigger show_tutorial_2 is 1.

In-app message trigger editor

The second tutorial message will also have an Body Action Name of show_tutorial_3 and so on. Once you get to the last tutorial page, you can simply dismiss the final message upon body click.