SubmitGate is a deterministic CLI that scans real mobile build artifacts (not just source code) and generates reports for issues that can slow down or complicate store submission. It’s focused on the gap between “the app builds” and “the app is actually safe to submit.”
Right now it scans iOS and Android artifacts and surfaces things like privacy manifest issues, ATS exceptions, required-reason-API related findings, permissions/configuration problems, and other release-time compliance risks. It also has a local report viewer so teams can inspect findings without uploading artifacts anywhere.
A few things I cared about while building it:
deterministic output
artifact-based scanning
CI-friendly reports
useful evidence/remediation instead of vague warnings
local-first workflow
I started this because I think too much mobile release pain comes from late discovery of things that are technically detectable earlier.
I’d especially love feedback from iOS/Android engineers, release managers, and teams that have dealt with App Store or Play review friction:
what findings would be most valuable?
what would be too noisy?
what should block vs just inform?
Happy to answer technical questions and tough feedback is welcome.