Code entities and strings
The code comparison counts parseable entities and string signals instead of relying only on file names.
| Area | What is compared | What the report shows |
|---|---|---|
| Types and structure Classes, extensions / categories, protocols, enums and structs | Swift and Objective-C types, extensions, protocol members, enum cases and struct members. | Totals on both sides, matching counts and similarity; display-only rows are marked explicitly. |
| Members and functions Properties, methods, functions and global symbols | Properties, methods, global functions, global symbols, protocol properties and protocol methods. | Matching names such as contentView, delegate and titleLabel. |
| Text signals Literals, domains and API paths | String literals, domains, API-like paths, string constants and macros. | Signals that reveal shared copy, domains, paths or structure; the minimum string length is configurable. |
Resources, configuration and dependencies
Resource comparison goes beyond same-name files. It can compare content hashes, folder names, Plist keys, localization keys and values, layout nodes and media files.
| Area | What is compared | Question it helps answer |
|---|---|---|
| Files and folders | File names, file hashes, folder names, folder hashes and other file types. | Do the projects share naming or directory structure, or identical file content? |
| Configuration and copy | Plist files, keys and values, .strings / .xcstrings localization keys and values. | Do they share configuration keys, error messages, login copy or localized resources? |
| UI and media | .storyboard, .xib, .xml layout data, image, audio and video names and hashes. | Do interface resources or media share names, content or structural nodes? |
| Dependencies | System libraries and external dependency directory names. | Do the projects rely on the same external or system components? |
Real report example: A sanitized run from April 9, 2026 found 18 matching properties, 45 matching string literals, 353 matching localization keys and 14 matching folder names. The homepage lets visitors switch between HTML, JSON and LOG views.
How results are presented
Every summary row answers the same questions: how many items are in Project A, how many in Project B, how many match, which names match, and what similarity is reported.
- HTML: human-readable summaries, matching items and local path relationships.
- JSON: structured data for automation, archiving or custom analysis.
- LOG: the scan, parse, compare and write timeline.
The website only publishes a sanitized summary and representative names. Absolute local paths, source snippets and complete raw reports stay private on the local machine.