1. Prepare the projects
Place the repository or release bundle locally and confirm that start.py is available. The two iOS / Xcode projects can be separate projects or different versions of one project.
python3 start.py
Follow the CLI prompts to choose Project A, Project B and a configuration file. The homepage's copy-command button uses the same entry point.
2. Choose a configuration
Configuration controls file types and comparison rules. Start from an existing JSON example and adjust it for the projects at hand.
Useful options include:
- Parser strategy: the example report uses the compiler parser.
- Code types: .h, .m, .mm, .pch and .swift.
- Resource types: layout, image, audio and video extensions.
- Exclusions: directories such as Pods, build and DerivedData; hidden-file handling is configurable.
- String threshold: min_compare_string_length sets the minimum length for string comparison.
3. Read the output
When the run finishes, reports are written to the configured output directory. The example configuration uses output; filenames include the run time and project names.
| Output | Best for | Main contents |
|---|---|---|
| HTML | Browser review | Category summaries, totals, matching items, similarity and path relationships. |
| JSON | Automation and archiving | Overall similarity, code comparison, resource comparison and structured fields. |
| LOG | Run troubleshooting | Scan, parse, compare and write stages with timestamps. |
4. Local processing and privacy
This is not an online upload service. Project paths, configuration and analysis results are processed locally; the public website only provides product documentation and a sanitized real-report snapshot.
Before sharing a report: check for absolute paths, internal domains or matching strings that should remain private. The public example already removes local absolute paths.