A React Native or Expo app feels like a native binary. Users install it from a store, open an icon, and never see a browser tab. The business logic you wrote in JavaScript or TypeScript still ships as a bundle inside that binary β or as Hermes bytecode that tools can unpack β and an interested person can pull it out of the APK, the IPA, or an OTA update.
This article is about what actually gets packaged, why "it's a mobile app" is not protection, and how to raise the cost of copying the proprietary part.
The bundle is in the package
A conventional release contains:
Native shells (Android / iOS) and whatever modules you linked.
A JavaScript bundle ( index.android.bundle , the Expo / Metro output, or an OTA payload from EAS Update or a similar channel).
If you use Hermes, a .hbc bytecode file instead of plain text JS β which is still a compiled form of your program, not a disappearance of it.
# conceptual Android inspection (your own build) unzip -l app-release.apk | grep -E "index.|hbc|bundle" # OTAβ¦