React Native · Expo · 跨平台目录

React Native 代码独特性检测

RN 工作室常从一个 JavaScript 核心推出数十款换皮应用。商店审核会看图标之外的内容：apporig 在工作区内对比每个项目的 TypeScript、JavaScript、React Navigation、StyleSheet 和 package.json。

免费检测代码面向工作室与批量发布团队

React Native 应用为何因相似度被标记

指南 4.3 和 Google Play 垃圾应用规则针对共享同一包骨架、仅换品牌的应用。若导航、状态和 API 层相同，换颜色和名称通常不够。

apporig 将 JS/TS 解析为结构指纹，并对照整个目录交叉检查每次构建。与姊妹应用出现 COPY 状态是提交前需要重写的明确信号。

RN 发行商工作流

通过 ZIP 或 Git 将每个客户构建上传到同一团队工作区。每次商店上传前运行分析，先处理 COPY 配对，重构后重新扫描。

JS/TS 抽象语法树加原生 Swift/Kotlin 桥接文件
Expo 与裸 React Native 项目
目录内 COPY / RELATED / OK 分级
对比维度：文件、结构、命名、依赖

常见问题

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.

Does apporig detect shared JavaScript bundles in RN apps?

Yes. JS/TS AST fingerprints, component and hook names, JSX structure, StyleSheet definitions, and npm dependencies are compared project to project in one team 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.