Open Projects from a Development Server
Expo Go connects an Android phone to an Expo development server so a developer can open a project without first creating a standalone app package. After starting the server from Expo CLI, users can scan the terminal QR code or supply the project address directly. This makes the phone a convenient preview target beside the computer where the code is being edited.
The Home screen keeps Scan QR code and Enter URL manually in the same Development servers panel, so either connection method is easy to find. Devices on the same Wi-Fi network usually provide the simplest path, while a tunnel connection can help when router settings prevent a local link. Once connected, the project opens inside the Expo Go container.
Preview React Native Changes on Device
Expo Go turns a physical Android device into a quick feedback surface for JavaScript and React Native work. Developers can edit a screen on the computer, let the development server send the updated bundle, and inspect the result on the phone. Fast Refresh helps many code changes appear without rebuilding the native app, which is useful for adjusting layouts, navigation, gestures, and animations during short iteration cycles.
Projects can also exercise modules already included in the Expo SDK, such as camera access, audio and video, location, and SQLite, when the project uses those capabilities. The loaded project determines which interface and permission prompts appear. This flexible sandbox is especially practical for tutorials, classroom exercises, prototypes, and early feature checks.
Accounts, Recent Projects, and Appearance
Signing in gives Expo Go a project-oriented home for developers who work across more than one experiment or collaborate through an Expo organization. The account area can surface projects associated with the signed-in user, reducing the need to re-enter a URL every time. Account-linked updates are limited to projects the user owns or projects held by an organization where that user is a member.
The app also includes a simple Settings area with Automatic, Light, and Dark theme choices. Automatic follows the device color scheme when the operating system supports it, while the two manual options keep the interface consistent regardless of system appearance. The same screen displays the client version and supported SDK, making compatibility information easy to check before opening a project.
Learn Quickly, Then Use a Development Build
Expo Go is best suited to learning, experimenting, and previewing projects that stay within the native capabilities bundled into its client. It removes much of the setup needed for a first on-device run, so students and developers can concentrate on components, state, navigation, and other JavaScript-driven behavior. It is also useful for sharing an early project URL with a teammate who has a compatible Expo Go client.
The sandbox has deliberate limits: third-party libraries that require custom native code cannot be added to the shared client, and SDK compatibility matters when opening a project. A custom development build is the better next step for production-oriented work, native configuration, or unsupported modules. Treating Expo Go as the starting point keeps prototypes simple while leaving room to move into a project-specific runtime.
