Trace is open source and community-driven. See what contributors have built, learn how to get involved, and preview upcoming features shaped by user feedback.
One month after launch, Trace has grown beyond what we imagined. The community has contributed bug fixes, feature requests, documentation improvements, and thoughtful feedback that's shaping the roadmap. This post highlights what the community has built and how you can get involved.
Since launching on TestFlight:
These numbers represent real developers solving real problems. Every bug report and feature request helps make Trace better for everyone.
@nicklockwood
Community member @developernotes submitted a PR adding the ability to save and share filter presets. This shipped in version 1.1 and has been one of the most-used features.
Example presets:
@kishikawakatsumi
@tanaka-dev contributed a complete Japanese localization, making Trace accessible to Japanese-speaking developers. This inspired localization efforts for other languages—we now have partial translations in Chinese, Korean, and Spanish.
@groue
Several community PRs improved memory usage in the Network Extension:
These changes reduced extension memory usage by ~30% in typical capture sessions.
Dozens of contributors have fixed typos, clarified confusing sections, and added examples to the docs. Special thanks to everyone who improved the certificate installation guide—it's now much clearer thanks to your feedback.
The most-requested features are now prioritized on the roadmap:
Multiple requests for complex filtering like:
(domain contains "api" AND status >= 400) OR method = "POST"
We're designing a filter expression language that's powerful but not overwhelming.
Users want to diff two requests side-by-side to spot differences in headers or body. This is especially useful when debugging "works in one case, fails in another" scenarios.
Several users asked to import HAR files exported from other tools. This enables comparing Trace captures with desktop tool captures or sharing sessions across teams.
Sync captures and configuration across devices. Work on your iPhone during testing, review captures on your iPad later.
Trace is open source under the MIT license. Contributions are welcome in several forms:
See the Contributing guide for detailed instructions.
Found a bug? Open an issue with:
Good bug reports get fixed faster.
Have an idea? Open a discussion in GitHub Discussions:
We prioritize features based on how many users would benefit and implementation complexity.
Documentation is code. Improvements to the docs are just as valuable as code contributions:
Not a developer? You can still help:
We're working on several major features for 2026:
Q1: Advanced filtering, request comparison, saved filter presets
Q2: Performance optimizations for large sessions, background capture, export format improvements
Q3: Collaboration features, iCloud sync, annotations
Q4: Enterprise features, security policies, advanced CA management
The full roadmap is public at /roadmap and shaped by community feedback.
Building Trace wouldn't be possible without the community. Every bug report, feature request, PR, and piece of feedback makes it better.
Special thanks to early adopters who reported critical bugs in the first week—your patience and detailed reports were invaluable.
If you're using Trace and finding it helpful, consider:
Let's build the best iOS network debugger together.
@Trace-iOS
Thank you for being part of the Trace community.