Sandocs

Environment Setup

Use whatever coding language or framework you prefer - whether developing with tools on Windows or with Linux tools on the Windows Subsystem for Linux, this guide will help you get set up and install what you need to start coding, debugging, and accessing services to put your work into production.

Set up on Windows #

This allows you to run your Native app on a physical device without setting up a development environment. If you want to run your app on the Simulator or an Virtual Device, please refer to the instructions for "Native CLI Quickstart" to learn how to install or set up your development environment.

Once you've set these up, you can launch your app on an Virtual Device by running npm run name, or on the Simulator by running npm run

Caveats #

Because you don't build any native code when create a project, it's not possible to include custom native modules beyond the Native APIs and components that are available in the client app.

If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll need to "eject" eventually to create your own native builds. If you do eject, the "Native CLI Quickstart" instructions will be required to continue working on your project.

Set up on Mac #

This allows you to run your Native app on a physical device without setting up a development environment. If you want to run your app on the Simulator or an Virtual Device, please refer to the instructions for "Native CLI Quickstart" to learn how to install or set up your development environment.

Once you've set these up, you can launch your app on an Virtual Device by running npm run name, or on the Simulator by running npm run

Caveats #

Because you don't build any native code when create a project, it's not possible to include custom native modules beyond the Native APIs and components that are available in the client app.

If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll need to "eject" eventually to create your own native builds. If you do eject, the "Native CLI Quickstart" instructions will be required to continue working on your project.