Mobile vs. web in A/B testing
The web console and the mobile app both show your Experiences, but only one of them lets you create and configure a test. Here's the split.
Overview
Intempt lets you work with A/B tests and personalizations, Experiences, from both the web console and the mobile app, but the two surfaces aren't equivalent. The web console is where you create and configure an experience: variants, targeting, scheduling, and metrics. The mobile app is a monitoring and lifecycle-control surface. You can view an experience's setup, check its results, and start, pause, resume, or stop it, but you can't create one or edit its configuration there. Every experience you see on mobile was created and configured on the web.
What you can do on the web
The web console is where an experience starts. The create-experience dialog offers two active types, Client-side Experiment and Client-side Personalization, and from there you configure:
- Variants. Add, rename, duplicate, or delete variants, and set each one's traffic allocation.
- The visual editor. Build a variant's on-page changes without writing code.
- Targeting. Audience, frequency, devices, and URL conditions.
- Scheduling. An activation period plus a daily schedule.
- Metrics. One primary metric and any number of secondary metrics.
What you can do on mobile
Mobile has no create-experience flow, no variant editor, no targeting editor, no scheduling editor, and no metric picker. Its Setup tab shows the same variants, metrics, schedule, and targeting the web console configured, but read-only. What mobile does let you do:
- View the Setup, Result, and Summary tabs: distribution charts, cumulative-exposure charts, and the metrics scorecard.
- Control the experience's lifecycle: Start, Pause, Resume, and Stop, each behind its own confirmation dialog.
- Rename the experience.
📘 Good to know
Mobile also shows a swipe-to-delete action with its own confirmation dialog, but deleting an experience on mobile doesn't currently do anything. The handler behind it is a placeholder, and the underlying delete request is never sent. Delete only works from the web console today.
Web vs. mobile at a glance
| Web | Mobile | |
|---|---|---|
| Create an experience or personalization | Yes | No |
| Configure variants, targeting, schedule, metrics | Yes | View only |
| Visual editor | Yes | No |
| Start / Pause / Resume / Stop | Yes | Yes |
| Extend a running experience | Yes | No |
| Delete | Yes | No (the action is in the UI, but the request isn't wired up yet) |
Which one should you use?
Set up and configure experiences on the web. Once an experience is running, use mobile to check in on it and make lifecycle calls, like pausing a losing variant or stopping a test, without needing your laptop.
Where to go next
Mobile experiments
Mobile experiment is a form of A/B testing experimentation in which the variations of a test are rendered directly on the web server, before it is delivered to the client. This is distinguished fro...
Multivariate testing
Test more than two variants against a single control in one experience, then compare all of them side by side in Results.