Expo buying guide: Where will you recover each native change after regeneration?
If you already maintain an iOS or Android native project, map the origin of each change before adopting Expo's native project generation. A change with an independent source and one kept only in an output directory have different migration costs.
If a native change is kept only in the generated project, where will you find it after the next regeneration? For an existing app, that matters more to the choice of Expo native project generation than how much code can be shared. The SDK 57 release notes say that this version's prebuild clears and recreates the iOS and Android native directories by default. They discuss projects that use continuous native generation separately from those that do not. That is not an instruction to treat native directories as disposable in every Expo project.
Rehearse the handoff with three rows before touching the project
Imagine a fictional photo album app with three native adjustments: the app display name on both platforms, an iOS-only album identifier, and an Android-only footer. Write down the expected result, where the change comes from, and who can hand it over for each one. Then assume you cannot see the native output directories and ask whether those sources alone explain what a regenerated project should contain.
Entry A points to versioned project configuration. Entry B points to an actively maintained iOS source file. Entry C says only that someone edited the generated directory by hand. A has a traceable candidate source. For B, the team must decide whether to retain the native project or move the change into a generation input with a clear owner. C is a direct migration gap. Version control gives you a way to retrieve the original edits; it does not make regeneration reapply them. The acceptance test is not whether every row has a note, but whether each points to an independent source and names who can confirm the result. This is a paper review, not a generation run or a project change.
Set the pilot boundary from where changes live
If version-controlled configuration and reproducible inputs are the main sources for the native project and the team treats generated files as output, evaluate Expo on an isolated sample project or a separately maintained pilot. A single screen is not a boundary that isolates native project generation. If both platforms have long-term maintainers and the customizations depend on native source files, keeping those files authoritative is the safer option. Estimate the cost of expressing each change in a new form and the cost of long-term maintenance on both platforms before changing project ownership. You need not migrate the whole existing native project just to share a few screens.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:expo.dev