For teams publishing mobile apps at scale
Code uniqueness check
apporig checks how unique your source code is across projects and revisions. Upload ZIP or Git, compare Swift, Kotlin, React Native, Flutter, and other supported stacks, and read COPY / RELATED / OK before store review.
Why bulk publishers need automated checks
Studios that ship many apps per month cannot manually review every repository. Store rejections for template or duplicate code waste release slots and delay revenue.
apporig scales code uniqueness checks to dozens of projects in one team workspace with human-readable reports.
- Cross-check every app in a shared team workspace
- COPY / RELATED / OK status for fast prioritization
- Swift, Kotlin, Java, Objective-C, React Native, and Flutter
- ZIP or Git upload, plus Jira Automation for release tickets
- Whitelist rules to exclude SDK and boilerplate from scores
How source code uniqueness analysis works
Analysis combines file hashing, AST structural similarity, naming patterns, and comparison layers (structure, data flow, dependencies). Cosmetic refactors with renamed types but the same architecture still show up as RELATED or COPY.
FAQ
What is a code uniqueness check for mobile apps?
A code uniqueness check compares your app source against other projects to find copied files, structural clones, and cosmetic refactors. apporig automates this with file hashing, AST analysis, and token winnowing – giving COPY, RELATED, and OK signals before App Store or Google Play review.
How is apporig different from other services?
apporig is built for mobile app catalogs: tree-sitter parsers for Swift, Kotlin, Java, React Native, and Flutter, team workspaces, Git and Jira ingest, whitelist rules, and COPY / RELATED / OK reports for high-volume publishers.
How is apporig different from git diff?
Git diff shows changes within one repository. apporig cross-compares different projects in your workspace, detects structural similarity even when files are renamed, and produces an overall risk score for store moderation.
Can I upload ZIP archives for analysis?
Yes. Upload Xcode or Android Studio projects as ZIP files. apporig runs similarity analysis, deletes the uploaded archive after analysis, and keeps analysis results in your team workspace for comparison with other apps.
Does apporig support Git repositories?
Yes. Connect HTTPS Git repositories for ongoing analysis. Each new revision is compared against other projects in your workspace – useful for weekly release trains.
What languages does apporig analyze?
Today: Swift, Objective-C, Kotlin, Java, React Native (TypeScript/JavaScript with Expo), and Flutter (Dart with widget, navigation, theme, and pubspec analysis). C#, Go, and PHP are on the roadmap.
Is apporig free to try?
Yes. During early access you get a free workspace with Starter-level limits – upload projects, run analysis, and review similarity reports. Limited spots include three months of Starter at no charge.
How does AST structural similarity work?
apporig parses source code into abstract syntax trees and compares structural fingerprints. This catches refactors where class and function names change but the underlying architecture stays the same.
Can I check many apps in a batch?
Yes. Upload multiple ZIP or Git projects into one team workspace. apporig compares every project against every other project – the standard workflow for studios publishing 10–50 apps per month.
Does apporig help prevent App Store rejections?
apporig helps you find duplicate or template code before submission. Many App Store Guideline 4.3 rejections cite similar binaries – proactive code checks reduce surprise rejections.
How long does a code uniqueness analysis take?
Most projects produce a report within minutes depending on repository size. Large monorepos may take longer, but typical mobile app projects complete quickly after upload.