Why Xcode Schemes Aren't in React Native 'Get Started' Docs

WHY IT EXISTS A brand new React Native developer wants one thing on day one, a running app on a phone or simulator. Xcode Schemes and Build Configurations are real, necessary iOS concepts, but explaining them upfront would bury that first win under native tooling most beginners never asked to learn. The Get Started docs route around this by defaulting to Expo, which owns the native project on your behalf.

THE MENTAL MODEL Picture the native ios and android folders as an engine bay. Expo's managed workflow keeps the hood closed, you write JavaScript and React, and a build service assembles the engine for you using sensible defaults. Xcode Schemes live under that hood. A Scheme tells Xcode what to build, which Build Configuration to use, and what to do when you run, test, profile, or archive. You only need to open the hood once you need to change how the engine itself is tuned.

HOW IT WORKS A Build Configuration, typically Debug or Release, is a named set of compiler flags, optimization levels, and preprocessor definitions. A Scheme wires a Configuration to specific actions, Run uses Debug, Archive uses Release, and can point at different bundle identifiers, API endpoints, or entitlements. Teams add custom configurations like Staging to ship separate builds side by side on one device. None of this is visible from a managed Expo project, because Expo Application Services builds against its own profile system instead, generating the native project and its schemes only at build time.

WHEN IT MATTERS It matters the moment a project needs behavior the managed workflow cannot express, a native SDK without an Expo module, a distinct staging app icon and bundle ID installed next to production, or CI that must archive and sign without a hosted build service. The footgun is discovering this mid project, after months of ignoring the ios folder, when a client suddenly needs three environments on one test device by next week.

ONE CONCRETE EXAMPLE A team moves off the managed workflow to add a native Bluetooth SDK. In Xcode they duplicate the Release configuration into Staging, add a flag for it, then create a new Scheme, MyApp Staging, that builds with the Staging configuration and a bundle ID suffixed staging. QA now installs the staging build alongside the App Store build without conflicts, something the original Get Started guide never had to mention.