For developers: your first week on an inherited codebase
A calm, day-by-day plan for your first week on someone else's code: secure access, make backups, learn the system, add safety nets, then report in writing.
ReadReact Native apps share most of their code between iOS and Android, written in JavaScript or TypeScript with React. Many projects use Expo, building through EAS Build and shipping JavaScript fixes with EAS Update; others are bare projects with hand-managed ios and android folders, CocoaPods and Gradle. Either way the Metro bundler serves the code during development.
Version drift is the classic problem. An app left alone for a while may sit several React Native releases behind, with native modules that do not support the New Architecture, a Podfile that no longer resolves and an Android build blocked by Gradle plugin changes. Navigation libraries and state management may have been swapped midway, leaving two patterns in the codebase. Push notifications and deep links are frequently half configured.
Say whether the app uses Expo or is bare, which React Native version it is on, and whether it has been published. List the native features it needs, such as camera, payments, maps or background location. Share the repository and any EAS project through your own Expo organisation. The dependency freshness check shows how far behind the packages are, which shapes the upgrade estimate.
Be the first rescue specialist here
Developers and agencies who finish other people's projects can create a free profile and list this as a specialty.
A calm, day-by-day plan for your first week on someone else's code: secure access, make backups, learn the system, add safety nets, then report in writing.
ReadPackage your half-built project so a new developer can run, change and deploy it without guessing: accounts, code, setup, known issues and a clean access plan.
ReadExpo projects use Expo's tooling to manage native configuration and builds, while bare projects keep the full ios and android folders under direct control. Many apps mix the two through prebuild. Your package.json and app config files show which you have.
Over-the-air tools such as EAS Update can deliver JavaScript and asset changes to installed apps. Changes to native code still need a new build and store submission, and store rules on what may change remotely still apply.