Reduce React Native Android Size Without Removing Required ABIs

Establish an equivalent release baseline

Follow the React Native release guide and record whether you are measuring a universal APK, an architecture-specific APK or a Play device download.

Do not compare a debug build with a store-generated release and attribute the difference to one optimization.

Inspect the largest contributors

The Android size guide provides packaging context. Removing an ABI can reduce a universal file while excluding devices; it is not a free optimization.

Treat Hermes as a measured choice

The Hermes guide describes the engine and release bytecode. Do not switch engines solely because a generic benchmark claims a smaller app. Measure your app's size, startup and memory together.

Rebuild from source

Do not delete native libraries from a signed APK and rezip it. Use supported build settings so dependency consistency and signing remain valid.

After removing a module, check initialization, autolinking/code generation and feature fallback paths. An unused-looking native dependency may still support a rarely used screen.

Verify the delivered experience

Test supported architectures and the actual Play-delivered artifact when using bundles. APKLint's APK Size Analyzer and React Native Analyzer can locate package contributors, but they do not guarantee a particular download saving. Report before/after sizes for clearly named equivalent artifacts and retain functional test evidence.