Mobile integration checklist
Test an OmniLab experience inside your app on real devices, and know where to send each kind of problem.
2 min read
Work through this before you submit a release. Fixing a WebView defect that reached the app store costs a review cycle, which is usually longer than the campaign.
Before you build
- The campaign is published in Studio.
- Your release schedule leaves time for store review before the campaign starts.
- The permissions the experience needs are declared, with usage descriptions written.
- Your team has read WebView requirements.
Test on real devices
Simulators grant permissions differently, and pass where a real phone fails.
- Log the address your app builds, and check the language and identifier in it are percent-encoded.
- Run the full journey to the reward on the smallest phone you support.
- Test every form field against the keyboard: it shouldn't cover the field, and the view should scroll.
- Scroll a long page, then open a panel, and check it opens on screen.
- Test the camera, an upload or location, including when the participant refuses permission.
- Save a booking's calendar file or ticket, if your campaigns offer them, and check where it lands.
- Put the app in the background mid-experience, return, and check the participant is where they left off.
- Turn off the network mid-journey and check they can recover.
- If your app has a language setting, switch it and check the experience follows.
- If your app passes
fci, check the experience opens as that person. Without a recognition integration for the campaign, they see your customer-account sign-in first. - If participants sign in inside the experience, check the round trip stays in your app.
- Test your back control from several points in the journey.
Before you release
- If you tested on a Staging campaign or a duplicate, point the app at the live campaign's touchpoint link.
- If you tested on Staging, update the host list too: the live experience domain, and
<subdomain>.api.topage.coin place of<subdomain>.api.uat.topage.co. - Check rewards and prize stock are set up.
- Check the campaign dates allow for your store review time.
Where to send a problem
| What's happening | Contact first |
|---|---|
| The experience won't load, or the game misbehaves | OmniLab support |
| A reward is wrong, missing or out of stock | Your marketing team, in Studio |
| The keyboard covers a field, or the view is cropped | Your mobile team |
| The camera prompt never appears, or an upload button does nothing | Your mobile team: the app grants the permission and opens the file picker |
| The experience opens in the wrong language, or as the wrong person | Your mobile team: both come from the address the app builds |
If you're a partner, raise each problem through the centre's Studio admin. Send the campaign link, the touchpoint ID, the device, the time it happened and a console log.