Try a mobile app in an emulator

2 minute read · Projects & Git

Use Mobile Emulator to inspect a supported mobile project on an Android emulator or iOS Simulator. A phone-sized browser viewport tests a website layout; an emulator runs a mobile application. Neither is the same as pairing your phone with Vortex.

• Prepare the device tools
• Open the project's emulator panel
• Allow agent control separately
• Check the result

Prepare the device tools#

1. Open Settings → Mobile emulator and enable Enable Mobile Emulator.
2. Read Availability for Android SDK and iOS Simulator. Refresh checks this computer again.
3. If Android SDK was installed elsewhere, choose Locate SDK folder and select its actual directory. Selecting a directory does not install the SDK or create an emulator device.
4. For iOS, use macOS with full Xcode and a suitable simulator. If the interface offers Download iOS input helper, follow that setup and its requirements; stop active iOS sessions first. The current helper setup requires macOS 14 or newer.
5. Choose Default Device, or leave Auto-select device. A saved device can be unavailable on another computer; select a device detected here.

Opening settings or enabling the feature does not prove the project builds. Resolve the displayed platform/tooling error before trying to launch its app. Do not substitute an Android package for an iOS build.

Open the project's emulator panel#

Select the intended mobile project and open its Mobile Emulator action. Select an available device and use the offered start controls. Inspect the build or launch result before interacting with the screen. The supported actions depend on the selected platform and installed input helper.

Use the displayed emulator screen and the available Home, Back, Rotate and text-entry controls. Closing the panel and stopping the session are separate actions; use the session control when you want execution to end.

Allow agent control separately#

Agent Mobile Emulator Control lets coding agents operate the active emulator. Keep it disabled when you only want to test manually. The switch does not grant access to unrelated device data or override the chat's access mode.

Ask for a short flow: “Open the article screen, add a fictional title, return to the list and confirm it survives reopening.” The agent should report unsupported controls rather than claim the device was tested. Keep accounts and test records appropriate for an emulator.

Check the result#

Verify the intended device, orientation, input and saved state. An image of a launch screen is not proof that saving or navigation works. If setup fails, retain the exact device/tooling status and relevant build error. A check in one emulator does not establish behavior on every physical phone.

Related guides: Preview, checks before publishing, connect your phone.