Development and Production Mode
Your project will always run in one of two modes: development or production. By default, running your project locally with
expo start runs it in development mode, whereas a published project (via
expo publish), or any standalone apps, will run in production mode.
Production mode minifies your code
and better represents the performance your app will have on end users' devices. Development mode includes useful warnings and gives you access to tools that make development and debugging easier. Let's look at each of these modes more in detail and learn how you can toggle between them.
. Development mode also performs validations while your app is running to give you warnings if, for example, you're using a deprecated property or if you forgot to pass a required property into a component. This video shows the Element Inspector and Performance Monitor in action, on both Android and iOS simulators:
This comes at a cost: your app runs slower in development mode. You can toggle it on and off from Expo Dev Tools and Expo CLI. When you switch it, just close and re-open your app for the change to take effect. Any time you are testing the performance of your app, be sure to disable development mode.
To enable development mode, make sure the "Production mode" switch is turned off:
In the terminal with your project running in Expo CLI (initiate this with
expo start), press
p to toggle production mode.
The Developer Menu gives you access to a host of features that make development and debugging much easier. Invoking it depends on the device where you are running your application:
- Terminal UI: Press
m in the terminal to open the menu on connected iOS and Android
- iOS Device: Shake the device a little bit.
- iOS Simulator: Hit
Ctrl-Cmd-Z on a Mac in the emulator to simulate the shake gesture, or press
- Android Device: Shake the device vertically a little bit.
- Android Emulator: Either hit
Cmd+M, or run
adb shell input keyevent 82 in your terminal window.
Production mode is most useful for two things:
- Testing your app's performance, as Development slows your app down considerably
- Catching bugs that only show up in production 🐛
The easiest way to simulate how your project will run on end users' devices is with the command
expo start --no-dev --minify
Besides running in production mode (which tells the Metro bundler to set the
__DEV__ environment variable to
false, among a few other things) the
--minify flag will minify your app, meaning it will get rid of any unnecessary data (comments, formatting, unused code). If you're getting an error or crash in your standalone app, running your project with this command can save you a lot of time in finding the root cause.