Foldables Changed Phone Typing: Build a Split‑Thumbs Test for Inner vs Cover Screens

Foldables Changed Phone Typing: Build a Split‑Thumbs Test for Inner vs Cover Screens

Why foldables deserve their own typing test

If you’ve typed on a Galaxy Fold or Pixel Fold, you know the story: the tall, narrow cover screen encourages one‑hand swiping, while the tablet‑like inner display invites two‑thumb tapping—and often a split keyboard. Average smartphone typing speed clocks in around 36 WPM with about 2.3% uncorrected errors in a large study of 37,000 people, but posture matters: two‑finger (typically two‑thumb) typing is significantly faster than one‑finger or one‑thumb input. That means results on a slab phone don’t necessarily predict performance on a foldable’s two very different canvases. (userinterfaces.aalto.fi)

On hardware, the differences are real: for example, Samsung’s Galaxy Z Fold6 offers a 6.3‑inch cover display and a 7.6‑inch inner screen, pushing users toward different grips and reaches. (samsungmobilepress.com) Ergonomics research also shows a two‑handed grip affords better thumb motor performance than one‑handed, reinforcing why inner‑screen typing with both thumbs can feel faster and steadier. (stacks.cdc.gov)

Meanwhile, keyboards have evolved to match: Gboard added a split layout for foldables (with an option to duplicate keys on both halves), and SwiftKey includes a dedicated “Thumb (split) mode.” Samsung’s own keyboard lets you switch among standard, split, and floating modes and adjust height/size. (9to5google.com)

The unique angle: a Split‑Thumbs Test mode

Design a mobile test mode that runs on‑device and automatically measures performance across:

Your goal is to reveal where each setup excels. Expect patterns like “swipe wins on the narrow cover screen,” while “split + two thumbs wins on the inner screen,” but verify with data.

What to measure (and how)

Use the text‑entry community’s standard metrics so results are comparable:

For baseline context, cite the 37,000‑person study (≈36.2 WPM average; two‑finger faster than one) in your report pages so testers know where they stand. (userinterfaces.aalto.fi)

Implementation: detecting inner vs cover and layout states

Tip: mark each trial with detected state (Cover vs Inner), orientation, and window size class. That way one session can contain multiple comparable segments without forcing relaunches.

Building the test matrix

1) Layouts to compare

Expose a quick‑toggle bar so testers can change layouts between short trials (20–40 seconds each). Gboard’s split keyboard and its “duplicated keys” switch live under Preferences → Layout, while SwiftKey’s “Thumb” (split) mode is a built‑in keyboard mode. (9to5google.com)

2) Input methods

3) Tuning variables

Language‑switch scenarios that matter

Foldables are popular with multilingual users. Include tasks that require switching:

Implementation tips and user prompts:

Real‑world tasks (beyond pangrams)

Add short, goal‑oriented trials that expose where split layouts help or hurt:

Report per‑task WPM, UER, KSPC, and backspace ratio. Expect the cover screen + swipe to lower KSPC (fewer taps) but sometimes raise UER if the language model misses rare terms; expect inner screen + split + two thumbs to raise WPM and reduce backspaces. Validate these hypotheses with your logs.

Practical tuning tips for testers

How to present results

Why this matters

Foldables blur the line between phone and tablet. The cover screen favors one‑hand reach; the inner canvas rewards two‑thumb coordination. A proper Split‑Thumbs Test recognizes both contexts, uses standard text‑entry metrics, and respects platform realities (like language and glide support). Build it once, and you’ll give users and researchers an honest read on when split keyboards truly speed things up—and when they get in the way.

Foldables Changed Phone Typing: Build a Split‑Thumbs Test for Inner vs Cover Screens - article illustration

Ready to improve your typing speed?

Start a Free Typing Test