Mobile full-screen controls: what to check

The observation behind this checklist

David tested twelve platforms on 9 October 2026 and described the overall round positively. On Stripchat, however, he found it difficult to make the player full screen on mobile. His devices across the round were a MacBook Pro, a Samsung 7 and an iPhone 14. He did not identify which phone or browser was involved in that particular issue.

This is a useful usability observation, but not a diagnosis. It does not establish that the control fails on all phones, that a certain browser is responsible or that the same issue remains present after a later update.

Name the action before comparing results

Enlarging a player inside a page, rotating a phone and entering a dedicated full-screen view are different actions. A review that only says “full screen did not work” can leave the reader unsure which action was attempted. Describe the visible control and what happened after tapping it.

For a repeatable note, start with the same page and account state. Record whether the player was already running, which control was used, whether the layout changed and whether an account prompt appeared. This checklist is a proposed follow-up procedure, not a claim that David recorded each step.

A short record that makes the problem useful

A small amount of context is more useful than a broad claim that a mobile site is bad. The goal is to let another person understand the friction without exposing an account or broadcaster.

• Phone model, operating system and browser version.
• Page type and signed-in or guest state; omit account identifiers.
• The control tapped and the expected result.
• What appeared instead: no change, a larger page player, a new view or a prompt.
• Whether the observation was repeated, and the date of that repeat.

Do not turn a workaround into a platform verdict

If a second attempt behaves differently, record both attempts. A change after signing in, rotating the device or using another browser may help narrow the problem, but it does not by itself explain its cause. Avoid claiming that a purchase fixes a player issue unless the actual sequence establishes that connection.

David’s positive overall impression and his criticism can both be accurate. Our review preserves the mobile friction as a dated observation rather than erasing it because other parts of the visit went well.

What this adds to a review

A platform feature list answers whether mobile viewing is offered. A task-level note answers whether a particular person could use a particular control comfortably. Those are related questions, but one does not replace the other.

The original test account remains the source for the Stripchat observation. The checklist here explains what a more detailed follow-up should record; it adds no new device result, playback benchmark or private-session claim.