Create Custom Triggers
Last updated
Last updated
In this section we guide you through the implementation of optional custom triggers that allow you to launch features of our API directly within your codebase.
The following events are supported:
When you create project in the portal, it comes with the default triggers of Shake and ScreenGrab, so the SDK captures a recording when your user shakes the device or takes a screenshot - actions considered as triggers. You can extend this capability by incorporating your own additional triggers by creating another in the portal which will then have an action type of Custom.
For instance, you might want to capture a video when your user presses a button in your app or completes a specific sequence.
Learn how in the section.
The SDK displays the introduction screen during the very first app launch, considering this the trigger. This feature enables you to add extra triggers and also allows you to disable the default app launch trigger.
For instance, you may choose to present the introduction screen at the end of your onboarding screens or provide an option to show it again from a help menu.
Learn how in the section.