Mobile 3D testing should cover loading, controls, reading, interruptions and exit paths. A working desktop demo is a starting point; acceptance needs representative devices, networks and complete visitor tasks.
Define the test matrix
Select representative iPhone and Android devices and record their operating systems and browser versions. Include relevant in-app browsers when visitors will arrive through messaging or social channels. Offer a route to a normal browser when needed. Document actual coverage rather than claiming that a small test represents every phone.
Observe the first visit
Test without previously cached assets and record when instructions appear and interaction becomes possible. Large scenes need useful loading feedback and a recovery option rather than an unexplained blank area. Distinguish the website’s controls becoming visible from the external viewer becoming ready so delays can be located accurately.
Check controls and reading together
Test rotation, movement, zoom, page scrolling and mission buttons for conflicting gestures. Inspect portrait and landscape layouts, especially text panels, captions, close buttons and bottom controls. After increasing text size, the main action should remain discoverable. Essential information should not depend solely on precise dragging inside the scene.
Treat interruptions as normal
Switch apps, lock the screen, reload and change network conditions. Check whether the visitor can resume, whether progress remains and when a reload is necessary. Clearly describe local-only progress instead of implying cross-device synchronisation. Empty or unavailable data must not produce a misleading completed state.
Accept a complete journey
Enter through the intended link, finish a task, leave, return and reach the inquiry or project page. For each issue, record the device, steps, visible result and reproducibility. Separate blocked journeys from cosmetic issues and fix completion blockers first, so the central experience works before visual refinement continues.
A quick commissioning checklist
- Which devices, versions and networks were actually tested?
- Are gestures, text, close controls and return paths usable?
- Have interruption, retry and full completion been exercised?