Cipher on phones and tablets
How Cipher keeps response quality honest across desktop, phones, tablets, and hybrids — by scoring the signals each device actually produces.
Most of Cipher's behavioral checks were built for a mouse and a keyboard. A phone or tablet has neither, so a naive system simply sees "no mouse movement, no keystrokes" and either flags an honest person or, worse, waves a bot through. Cipher takes a different approach: it first works out what kind of device the respondent is on, then scores the response on the signals that device actually produces — not the ones it can't.
Why this matters
Roughly half of survey traffic is mobile. Without a touch-native pipeline, that half of your data is graded on signals that were never collected. Cipher closes that gap rather than guessing — and a respondent on an iPhone is judged as fairly as one on a laptop.
Which device is it, exactly?
Before scoring anything, Cipher classifies every respondent into one of five device classes. This is the decision everything else branches on, because the absence of a signal only means something once you know whether that signal was ever possible.
| Class | What it is | How Cipher grades it |
|---|---|---|
| Desktop | Mouse + keyboard, no touch | Mouse dynamics, keystroke timing, scroll, hover |
| Mobile | A phone (coarse pointer, touch) | Touch, swipes, device motion, on-screen keyboard |
| Tablet | An iPad or Android tablet | Same touch-native signals as mobile, with a larger surface |
| Hybrid | A touch laptop / 2-in-1 (both a fine and a coarse pointer) | Whichever the person actually used — mouse and touch |
| Unknown | Class couldn't be determined | Scored conservatively; never auto-passed on thin evidence |
A couple of cases are deliberately handled rather than guessed:
- iPads that pretend to be desktops. Since iPadOS 13, Safari on an iPad reports itself as desktop Safari on a Mac. Cipher catches the tell — a "Mac" that also reports multiple touch points is an iPad — and classifies it as a tablet so it gets the touch pipeline, not the desktop one.
- Hybrids and 2-in-1s. A Surface or a touch-screen laptop can produce both mouse and touch input. Cipher recognizes it as hybrid and reads whichever signals the respondent actually generated, instead of assuming one and missing the other.
What each device gives us — and what it can't
Cipher's guiding principle is to score on the data a device produces, not mourn the data it doesn't. Each device class populates a different column, and Cipher grades on the column that's actually full.
| Signal | Desktop | Phone / Tablet | Hybrid |
|---|---|---|---|
| Mouse movement | ✓ | — | if used |
| Typing rhythm | ✓ | partial¹ | ✓ |
| Scrolling | ✓ | ✓ | ✓ |
| Touch | — | ✓² | if touched |
| Swipes | — | ✓ | if touched |
| Device motion | — | ✓³ | — |
| Orientation / tilt | — | ✓³ | — |
| On-screen keyboard lifecycle | — | ✓ | sometimes |
So a phone never loses points for having no mouse trail, and a desktop is never expected to report device motion. The score is always built from evidence that fits the device in the respondent's hand.
The touch-native signals
When a respondent answers on a touch device, Cipher reads signals a desktop session never produces: how the person touches and swipes, how the device is held, and how text gets into the answers through the on-screen keyboard. Taps, like clicks, are judged against the size and position of what was pressed, so your survey's layout never counts against anyone.
These run in the background while someone answers. They never interrupt the survey, and they add no visible step for the respondent.
Honest about what it cannot see
A touch device will not always give Cipher everything. iOS, for example, gates the motion sensor behind a permission prompt, and Surbee chooses not to surprise respondents with that prompt by default. So Cipher records a coverage profile for every response:
- Full. Touch and motion were both available.
- Partial. Touch was available but motion was not.
- Unavailable. No touch signals were produced.
Coverage is not cosmetic. On partial coverage Cipher leans less heavily on the touch signals it does have and lowers its own confidence, so a thin reading is never presented as a confident clean pass. A low score on partial coverage surfaces for review rather than being auto-accepted.
Built to not cry wolf
A false accusation against a real respondent is worse than a missed bot, and touch devices are full of innocent behavior that looks odd at first glance. Cipher is tuned so that ordinary phone use doesn't count against anyone: a phone resting on a table, hardware that doesn't report every sensor, a fast flick through a long survey, and voice dictation or autofill are all treated as normal.
Labeled the same way on every device
Scored responses are kept as labeled examples for training future versions of Cipher's model, and mobile responses are labeled with the same care as desktop ones:
- Features. Cipher distills the raw touch and motion streams into a fixed set of mobile features alongside the desktop ones. The device class is itself a feature, which is what lets a model learn that "no mouse" means bot on a desktop but is perfectly normal on a phone.
- Correct labels. The automatic labels are device-aware. The desktop "no mouse, no keyboard" rule is never applied to a phone; mobile responses are labeled by touch-native signals instead. Without this, every honest phone respondent would be mislabeled as fraud and a model trained on them would learn the wrong thing.
- Your verdicts. When you mark a flagged response as genuine or not in the dashboard, that human judgment becomes the highest-confidence label of all.
The result is a single engine that reads mouse and keyboard on a laptop and touch and motion on a phone, grades each response on evidence that fits the device, and tells you per response which device it was and how much it could see.