Edit this page
List of non-obvious terms used within the documentation, related to Expo or cross-platform development in general.
The mobile operating system that is sponsored by Google for use with Android devices.
A file named app.json, app.config.json, app.config.js, or app.config.ts in the root project directory. For more information, see app config configuration.
This file is used for the following purposes:
npx expo prebuild generates native code.An app config file.
Cloud services that are provided by Apple. These services must be enabled for an application in the Apple Developer Portal.
Apple's official website for managing application code signing. EAS Credentials automate most of the common reasons a developer might visit this website when developing an app.
A feature of EAS Build that automatically enables or disables Apple capabilities based on the project's entitlements file. Learn more.
A cross-platform tool for automatically linking native modules to native apps via native package managers.
pod install.There are two versions of Autolinking: Expo Autolinking, and Community Autolinking.
The default Prebuild template includes support for Expo Autolinking, and the Community Autolinking fork.
Transpiler used for removing language features that aren't available in the runtime's JavaScript engine. Metro uses Babel internally.
Projects can configure how Babel is used by modifying the babel.config.js file in the project directory. This file is optional when using Expo CLI. Expo projects should extend the default Babel preset babel-preset-expo.
Describes the approach when the native projects (in the android and ios directories) are versioned in Git and maintained manually. It's typical for existing "bare" React Native apps where you manually make changes to the native projects. There is freedom to customize them but also high maintenance overhead.
This is in contrast to using app config and prebuild, where the native projects are not versioned. Instead, they are generated on demand using the npx expo prebuild, which is the recommended approach.
A JavaScript runtime and a drop-in alternative for Node.js. For more information about usage with Expo and EAS, see using Bun guide.
The iOS package manager that is used to link native modules to the native iOS project. This package manager is configured using the ios/Podfile file and updated when a user runs pod install in the ios directory.
This refers to the React Native community fork of the Expo Autolinking. The requirements for linking a module are different from Expo Autolinking, however, the implementation is the same.
A process for evaluating the results of npx expo prebuild in-memory without persisting any code changes. This is used in Auto Capability Signing to determine what the entitlements file will look like without generating any native code. This process is also used in the VS Code Expo extension to debug Config Mods.
Async functions that are appended to the app config for use in Prebuild. These functions are given a single native file to modify such as AndroidManifest.xml or Info.plist. Config mods are chained together and come from the package @expo/config-plugins. For more information, see Config plugins.
A JavaScript function that is used to append config mods to the app Config for use in Prebuild. For more information, see Config Plugins.
An abstract concept that describes the process of generating native projects from a set of inputs. In the context of Expo, CNG is implemented via the prebuild command. See CNG and Expo Prebuild for more information.
A standalone command line tool (CLI) for bootstrapping new React Native apps with the expo package installed. See create-expo-app reference for more information.
A standalone command line tool (CLI) for bootstrapping new React Native apps with the expo package installed and the native code generated. This CLI also enables the use of bootstrapping from an example project in expo/examples.
This package can be used by running any of the following commands:
npx create-expo-appyarn create expo-appnpm create expo-appConfig modifiers that apply unstable changes to a native project during prebuild. Using these modifiers is unpredictable and prone to breaking changes between major version bumps in Expo SDK.
A development build is a debug build of your app that contains the expo-dev-client package. It's like an evolution of Expo Go which doesn't have Expo Go's limitations and can be customized to your application's needs.
This is the recommended approach for building production-grade apps with Expo. For more information, see Development builds.
expo-dev-client is a library that allows you to create a development build and includes useful development tools. You might also come across "custom dev client", a synonym for Development builds.
A development server (or dev server) is a server that is started locally, usually by running npx expo start from Expo CLI.
The development server is typically hosted on http://localhost:8081. It hosts a manifest from / which the client uses to request the JavaScript bundle from the bundler.
Expo Application Services (EAS) are deeply integrated cloud services for Expo and React Native apps, such as EAS Build, EAS Submit and EAS Update.
The command-line tool for working with EAS.
The eas.json file used to configure EAS CLI. For more information, see Configuring EAS Build with eas.json.
A command-line tool for uploading and downloading Apple App Store metadata as JSON. This tool is available in the EAS CLI package and should be used to improve the iOS submission process. For more information, see EAS Metadata.
eas update from EAS CLI used to publish static files to the cloud hosting service.Emulator is used to describe software emulators of Android devices on your computers. Typically, iOS emulators are referred to as Simulators.
The entry point usually refers to the initial JavaScript file used to load an application. In apps using Expo CLI, the default entry point is ./node_modules/expo/AppEntry.js which simply imports the App.js file from the root project directory and registers it as the initial component in the native app.
A synonym for an app that usually implies something more single-use and smaller in scope, sometimes artistic and whimsical.
The original Autolinking system is designed for projects using expo-modules-core. This system links modules based on the existence of an expo-module.config.json in the library's root directory.
The command-line tool for working with Expo. This term now refers to the Local Expo CLI, but historically referred to the Global Expo CLI. For more information, see Expo CLI.
The former name for the Expo Go app.
Refers to the command npx expo export from Expo CLI. This command is used to bundle the app's JavaScript and assets, and then export them into a static folder that can be uploaded to a hosting service like EAS Update, and embedded in a native runtime for offline use.
The Android and iOS app that serves as a sandbox for learning and experimenting with React Native.
Due to its limitations (such as the inability to include custom native code), it's not recommended for building and distributing production apps. Instead, use a development build.
Refers to the command npx expo install from Expo CLI. This command is used to install npm packages containing native modules that work with the currently installed version of expo in the project. Not all packages are supported. This command wraps the globally installed package managers.
A file named expo-module.config.json that lives in the root directory of a native module. For more information, see Module Config.
A collection of npm packages containing native modules that provides access to device/system functionality such as camera, push notification, contacts, file system, and more.
Refers to the command npx expo start from Expo CLI. This command is used to start a local development server that a client connects to interact with the Metro bundler.
The React Native rendering system which is used to create and manage native views. For more information, see Fabric Renderer.
A mobile app debugger used internally at Meta. It was previously recommended for use with React Native, but the integration is now deprecated and no longer supported by the React Native team (RFC-0641).
Sometimes referred to as Expo FYI, is a collection of tailored solutions to complex issues that live at expo.fyi. FYI links are utilized throughout Expo's developer tooling to help provide a better developer experience to users.
The package expo-cli was installed globally on the user's machine and used across all projects. This CLI was introduced in SDK 30 (2018), and deprecated in favor of the Local Expo CLI in SDK 46 (2022).
Gradle is a build automation tool for multi-language software development. It's used to build Android apps. It controls the development process in the tasks of compilation and packaging to testing, deployment, and publishing.
A JavaScript engine developed by Meta specifically for use with React Native. Hermes features ahead-of-time static optimization and compact bytecode to improve performance with focus on mobile devices, and is the default JS engine.
The operating system used on iPhone, iPad, and Apple TV. Expo Go currently runs on iOS for iPhone and iPad.
A native package that can evaluate JavaScript on-device. In React Native, we predominantly use Hermes by Meta. Other options include JavaScriptCore by Apple, and V8 by Google.
A JavaScript engine developed by Apple and built-in to iOS. React Native for Android also can use a version of JavaScriptCore for parity. Debugging with JavaScriptCore is less sophisticated than V8 or Hermes which implement the Chrome DevTools Protocol.
Linking can mean deep linking into apps similar to how you link to websites on the web or autolinking.
The package @expo/cli is installed with the expo package. This is sometimes referred to as the "Versioned Expo CLI" because it is installed inside the user's project as opposed to the now deprecated expo-cli which was installed globally.
An Expo app manifest is similar to a web app manifest. It provides information that Expo Go needs to know how to run the app and other relevant data.
Formerly Facebook, Meta is the group that develops React Native, Metro Bundler, Hermes Engine, Yoga and more. The Expo team collaborates with Meta to deliver the best possible developer experience.
The bundler used for converting JavaScript files and assets into a format that runs on a native runtime. This bundler is maintained by Meta and used for React Native (including web) apps. For more information, see Metro documentation.
The metro.config.js file used to configure Metro bundler. This should extend the package @expo/metro-config when using Expo CLI. For more information, see Customizing Metro.
A project that has multiple sub-projects which are all linked together via the package manager. A monorepo is a great way to maintain codebase for a cross-platform app.
The React Native ecosystem has thousands of libraries. Without a purpose-built tool, it's hard to know what the libraries are, to search through them, to determine the quality, try them out, and filter out the libraries that won't work for your project (some don't work with Expo, some don't work with Android or iOS). React Native Directory is a website that aims to solve this problem, we recommend you use it to find packages to use in your projects.
A module written in native code that exposes native platform functionality to the JavaScript engine via the JS global. This functionality is usually accessed via import { NativeModules } from 'react-native';.
A native application containing a JavaScript engine, and is capable of running a React application. This includes Expo Go, development build, standalone apps, and even web browsers like Chrome.
npm is a package manager for JavaScript and the registry where the packages are stored. An alternative package manager, which we use internally at Expo, is yarn.
Automates the process of installing, upgrading, configuring, and removing libraries, also known as dependencies, from your project. See npm and yarn.
Platform extensions are a feature of the Metro bundler which enables users to substitute files on a per-platform basis given a specific filename. For example, if a project has a .index.js file and a .index.ios.js file, then the index.ios.js will be used when bundling for iOS, and the index.js file will be used when bundling for all other platforms.
By default, platform extensions are resolved in @expo/metro-config using the following formula:
The process of generating the temporary native android and ios folders for a React Native project based on the app config. This process is performed by running the command npx expo prebuild from Expo CLI in a project directory.
See Prebuild template and Autolinking for further information.
The React Native project template is used as the first step of Prebuilding. This template is versioned with the Expo SDK, and the template is chosen based on the installed version of expo in a project. After the template is cloned, npx expo prebuild evaluates the app config and runs the Config mods which modify various files in the template.
Although the template can be changed by using the npx expo prebuild --template /path/to/template flag, the default prebuild template contains important initial defaults that the npx expo prebuild command makes assumptions about.
The default template currently lives at expo-template-bare-minimum.
We use the word "publish" as a synonym for "deploy". When you publish an app, it becomes available at a persistent URL from Expo Go, or in the case of Standalone apps, it updates the app.
React Native lets you build mobile apps using only JavaScript. It uses the same design as React, letting you compose a rich mobile UI from declarative components.
A high-performing abstraction on top of react-dom that enables core primitives from React Native to run in the browser. React Native for web (RNW) was developed at X and is currently used for their main website. Expo SDK and Expo CLI have first-class support for RNW.
The preferred navigation library for React Native apps, developed and sponsored by the Expo team.
Remote Debugging is a deprecated way of debugging React Native apps. A better alternative today is to use Hermes, as you can connect Chrome Dev Tools to it.
Also known as Async Chrome Debugging, it was an experimental system for debugging React Native apps. The system works by executing the application JavaScript in a Chrome tab's web worker, then sending native commands over a websocket to the native device.
An emulator for iOS devices that you can run on macOS (or in Snack) to work on your app without having to have a physical device handy.
slug in the [app config]((#appjson) is a URL-friendly name for your project. It is unique across your Expo account.
Snack is an in-browser development environment where you can build Expo experiences without installing any tools on your phone or computer.
A development agency in Kraków, Poland. Maintainers of react-native-gesture-handler, react-native-screens, and react-native-reanimated. The platform team at Expo is composed of a number of contractors from Software Mansion. All of Software Mansion's core React Native libraries are supported in Expo Go.
Synonymous with "Production build". An application binary that can be submitted to the Google Play Store or Apple App Store. For more information, see Build your project for app stores or Run builds locally or on your own infrastructure.
The store.config.json file used to configure EAS Metadata. This file can be generated from an existing App Store entry using eas metadata:pull.
The Swift and Kotlin API for writing React Native modules. This API is provided by the library expo-modules-core which is shipped with the expo package. For more information, see Module API.
TypeScript is a strongly typed programming language that builds on JavaScript, giving you better tooling at any scale. The Expo SDK is written in TypeScript, and we highly recommend using it. For more information, see our TypeScript guide.
Traditionally, apps for Android and iOS are updated by submitting an updated binary to the App and Play stores. Updates allow you to push an update to your app without the overhead of submitting a new release to the stores. For more information, see Publishing documentation.
The VS Code extension for improving the developer experience of working with app config files. This extension provides autocomplete and intellisense for the app config, Store Config, Expo Module Config, and EAS Config. For more information, see the VS Code Expo Tools extension.
The file watcher used by Metro to perform hot reloads during development. Watchman contains native code and may cause issues when installed globally. Watchman is maintained by Meta.
The deprecated bundler used by Expo CLI for developing react-native-web apps.
A package manager for JavaScript. For more information, see Yarn documentation.
The monorepo solution we recommend for Expo users. See Working with Monorepos for more information on how to configure Yarn workspaces.
A native cross-platform library used by React Native internally to provide CSS FlexBox support to native views. React Native styles are passed to Yoga to lay out and style elements on the screen. For more information, see Yoga documentation.