React Native · Expo · cross-platform catalogs
React Native code uniqueness check
Madalas mag-ship ang RN studios ng dose-dosenang reskinned apps mula sa isang JavaScript core. Mas malalim ang store review kaysa bagong icons: ihahambing ng apporig ang TypeScript, JavaScript, React Navigation, StyleSheets, at package.json sa bawat project sa workspace mo.
Bakit na-flag ang React Native apps dahil sa similarity
Tina-target ng Guideline 4.3 at Google Play spam rules ang apps na pareho ang bundle skeleton pero iba ang branding. Hindi sapat ang pagpapalit ng kulay at app name kung pareho pa rin ang navigation, state, at API layers.
Ipi-parse ng apporig ang JS/TS sa structural fingerprints at iche-check ang bawat build laban sa buong catalog. Ang COPY status sa sibling app ay malinaw na signal na kailangan i-rewrite bago mag-submit.
Workflow para sa RN publishers
I-upload ang bawat client build via ZIP o Git sa isang team workspace. Mag-run ng analysis bago bawat store upload, ayusin muna ang COPY pairs, tapos mag-rescan pagkatapos ng refactor.
- JS/TS AST plus native Swift/Kotlin bridge files
- Expo at bare React Native projects
- COPY / RELATED / OK triage sa buong catalog
- Comparison layers: files, structure, naming, dependencies
Mga madalas itanong
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.