React Native · Expo · cross-platform catalogs
React Native code uniqueness check
RN studios often ship dozens of reskinned apps from one JavaScript core. Store review looks past new icons: apporig compares TypeScript, JavaScript, React Navigation, StyleSheets, and package.json across every project in your workspace.
Why React Native apps get flagged for similarity
Guideline 4.3 and Google Play spam rules target apps that share the same bundle skeleton with different branding. Swapping colors and app names rarely helps if navigation, state, and API layers stay identical.
apporig parses JS/TS into structural fingerprints and cross-checks each build against your full catalog. COPY status on a sibling app is a clear signal to rewrite before submission.
Workflow for RN publishers
Upload each client build via ZIP or Git into one team workspace. Run analysis before every store upload, fix COPY pairs first, then rescan after refactors.
- JS/TS AST plus native Swift/Kotlin bridge files
- Expo and bare React Native projects
- COPY / RELATED / OK triage across the catalog
- Comparison layers: files, structure, naming, dependencies
FAQ
Can apporig analyze React Native projects?
Yes. apporig parses TypeScript and JavaScript with tree-sitter, compares React components, hooks, StyleSheet patterns, React Navigation structure, package.json overlap, and Expo app.config files across your workspace.
How do bulk React Native publishers use apporig?
Upload each client build via ZIP or Git, run analysis before every store submission, rewrite COPY-flagged navigation or shared modules, then rescan after refactors.
Does apporig support Expo projects?
Yes. Expo and bare React Native are supported. app.config/app.json is compared structurally alongside TS/JS source.