SOURCE CHECKED · 26 SEPT 2026 · DEVICE SUPPORT NOT GUARANTEED
Set the right expectation first.
Early-access discussion has described mobile access as experimental rather than a fully equivalent desktop experience. Device size, touch controls, graphics capability and browser memory can all change the result.
Look for the car-summon button
The current public client tells touch users to hold the car icon to summon a vehicle. Wait for the character and world to be ready, then follow that prompt if it appears. Summoning a vehicle is different from entering one; use the mobile controls guide for the touch actions.
Use a modern browser
Close other heavy tabs, use a stable connection, and ensure your browser is up to date before loading a graphics-heavy real-world area.
Switch to desktop for first use
If the summon control, touch input, performance, or the location selection flow gets in the way, try a desktop browser with a keyboard. It is the clearer environment for learning the live controls.
Check the failed stage, not just the device name.
Opening the homepage is not proof that a phone can complete a driving session. Test one familiar location: can you load the world, summon a car, enter it and move? If the scene is black or repeatedly reloads, follow the loading checklist. If the scene works but a touch action does not, compare the current Help overlay before changing browsers.
We have not completed a current iPhone and Android device test matrix. The presence of mobile controls in source code confirms an input path, not smooth performance on every phone. Do not install an unverified app or modified client to solve a browser problem.