About mobile app integration
Understand how an OmniLab experience appears inside your native app, and what your mobile team owns.
The experience loads in a WebView, an in-app browser view your app controls. Participants stay in your branded app instead of being sent to a browser. Your navigation, tab bar and app chrome stay as they are, and 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 navigation bar and tab bar. The OmniLab experience fills the screen between them.
When to use a WebView
- A loyalty or retail app should keep participants in the app while they take part in a campaign.
- The experience belongs in your app's navigation: as a tab, a screen, or a card that opens one.
- Your app already knows who the participant is, and they should be recognised. See Customer accounts.
If the experience only needs to be reachable from your app, a plain link that opens the phone's 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 Studio |
What to give your mobile team
- The touchpoint link from Studio, or the campaign link if a landing page presents several touchpoints.
- What the experience asks of the phone: the camera for a QR scan, photos for a receipt upload, location for a location check.
- Whether participants should be recognised because they're 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.