roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for Expo interviews on how a React Native app is generated, built and updated. Covers prebuild and development builds, the SDK, Expo Router, config plugins, EAS Build and over-the-air updates.
210 of 210 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 210 new. 0 cut, outside your plan.
Expo seldom gets a loop of its own. It comes up inside React Native interviews, most often in the technical conversation about how your last app was set up and shipped, and sometimes in a take-home that starts from create-expo-app. The questions tend to arrive as small incidents. A teammate adds a library with native code and the app stops opening in Expo Go. Someone edits Info.plist by hand and the change is gone after the next prebuild. An update published in the afternoon crashes on launch for users still on an older binary. A value read from an EXPO_PUBLIC_ variable turns up in the shipped bundle.
Behind all four sits one question: does this change live in JavaScript, in the generated native project, or in the binary already installed on the phone? Candidates who have only run an app in a simulator answer with commands. Candidates who have shipped one explain why Expo Go cannot load arbitrary native modules, why native edits belong in a config plugin, and why an update should reach a build only when their runtime versions match, then say what they would check first and how they would take the bad update back.
The plan opens with a decision: whether a new app should start on a framework at all, and what a team gives up by going bare. Workflows and prebuild follow, because the line between Expo Go and a development build, and the idea that native folders are generated rather than owned, come back in most later answers.
The middle of the plan is the code you write inside the app. The SDK is the native surface, from compatible installs and permission hooks to modules of your own, and push handling sits beside it, since Expo's notifications package is the usual way an Expo app obtains a token and reacts to a delivery. Storage comes next: SQLite for structured data, SecureStore for secrets and the file system for documents and downloads. Navigation then arrives in two steps. React Navigation goes first, its navigators, how they nest and how a stack keeps earlier screens mounted, because a layout file in Expo Router usually renders one of those navigators, and many of the router's surprises are really theirs.
From there the plan asks what turns that code into something a phone or a browser can run. Metro resolves, transforms and caches the bundle the Expo CLI serves, and React Native Web is what the same components become in a browser.
The last stretch works on the native project and the release. Config plugins are how a project with no committed native folders still changes them, so they precede EAS Build and Submit, which turns profiles and credentials into signed binaries. Over-the-air updates close the plan because they only make sense against those binaries: each build carries its channel, and its runtime version decides which updates it may load.
Coming from bare React Native, read the opening module as an argument to test rather than a lesson, and spend your hours on prebuild, config plugins and the update model, where Expo departs furthest from what you know. If you come from web development, Expo Router will look familiar from file-based routing on the web, so start with the workflow and the SDK, and give Metro extra time: its resolver and cache behave differently from the web bundlers you know. With two weeks or less, cut level down to the range you are applying at and leave only must know in importance. With more time, switch study order to by topics and follow the plan down, since the release modules lean on the workflow and plugin ones. The plan stays on Expo's side of the stack. Components, lists, styling, animation, performance, testing and the runtime underneath them belong to the [React Native roadmap](/roadmaps/react-native), which carries Expo as one of its modules and is the better fit when the interview is for the whole mobile role rather than the toolchain.
Coming from bare React Native, read the opening module as an argument to test rather than a lesson, and spend your hours on prebuild, config plugins and the update model, where Expo departs furthest from what you know. If you come from web development, Expo Router will look familiar from file-based routing on the web, so start with the workflow and the SDK, and give Metro extra time: its resolver and cache behave differently from the web bundlers you know. With two weeks or less, cut level down to the range you are applying at and leave only must know in importance. With more time, switch study order to by topics and follow the plan down, since the release modules lean on the workflow and plugin ones.
The plan stays on Expo's side of the stack. Components, lists, styling, animation, performance, testing and the runtime underneath them belong to the React Native roadmap, which carries Expo as one of its modules and is the better fit when the interview is for the whole mobile role rather than the toolchain.