About mobile app integration
Understand how an OmniLab experience appears inside your native app, and what your mobile team owns.
Show an OmniLab experience inside your own app so participants stay in your branded shell instead of being pushed out to a browser. This page explains how the pieces fit before you brief your mobile team.
The experience loads into a WebView — an in-app browser view your app controls. Your navigation, tab bar, and app chrome stay exactly as they are; the experience fills the space you give it.
- 1Your app's navigation bar and back button
- 2The OmniLab experience, loaded in a WebView
- 3Games, forms, and rewards all run inside it
- 4Your app's tab bar stays available underneath
Your app keeps its own navigation. The OmniLab experience fills the screen between it.
When this is the right choice
- A loyalty or retail app should keep participants inside the app while they take part in a campaign.
- The experience should sit in your app's navigation — as a tab, a screen, or a card that opens one.
- You want the participant to already be recognised, because your app knows who they are. See Customer accounts.
If you only need the experience reachable from your app, a plain link that opens the device browser is simpler and needs no development. Choose a WebView when leaving the app would break the journey.
Who owns what
| Responsibility | Owner |
|---|---|
| The app screen the experience appears on | Your mobile team |
| The WebView and its settings | Your mobile team |
| Device permissions such as camera and location | Your mobile team, through the app |
| Back, close, and where the participant lands afterwards | Your mobile team |
| The experience itself: game, form, branding, reward | OmniLab |
| Campaign configuration and rewards | You, in OmniLab Studio |
What to give your mobile team
- The experience address from OmniLab Studio.
- Whether participants land on a campaign page or go straight into one experience.
- Which permissions the experience needs — camera for a scan game, location for a venue-based one.
- Whether participants should be recognised automatically because they are signed in to your app.
This needs an app release
A WebView screen ships with your app, so it follows your release cycle and app store review. Plan the campaign dates around that, not the other way round.