Only policy-relevant changes are raised.
Review the package, not just the source diff.
Mobile Release Auditor compares Android and iOS release candidates at the package level, exposing permission, entitlement, SDK, architecture, metadata, symbol, and size changes before submission day.
- FIRST SCOPE
- One repository / target
- FIRST RESULT
- Within one week
- DEPLOYMENT
- Your existing CI
A release-candidate diff that separates expected configuration changes from the SDK or packaging surprises most likely to delay review.
The signals worth stopping for.
The first pilot uses the subset that matches your workflow. The rest stay out of the way until they earn their place.
Permissions & entitlements
Show additions, removals, and policy-sensitive changes with their originating package context.
Native SDK inventory
Diff embedded frameworks, libraries, Maven dependencies, and identifiable versions.
Architectures
Verify expected ABIs and slices, and flag accidental simulator or unsupported architecture content.
Package metadata
Compare identifiers, versions, URL schemes, minimum OS, capabilities, and manifest values.
Symbols & diagnostics
Check expected symbol artifacts and surface stripping or debug-content changes where inspectable.
Payload growth
Break down package growth by the native, managed, asset, and resource sections the format exposes.
A narrow pilot, built around your real pipeline.
No platform migration and no quarter-long rollout. We start with one decision your team currently has to make without enough evidence.
Choose the review point
Agree on one repository, target, baseline, CI job, and the signals that should be visible.
Connect the artifacts
Wire a read-only analysis step into the current workflow and produce an example report.
Review the evidence
Run it against representative changes, tune noise, and decide whether the next scope is justified.
Does this submit builds to the stores?+
No. It inspects produced packages before submission. Store delivery remains in your current release pipeline, so the auditor never needs store credentials.
Can it identify every SDK version?+
Only where the package contains reliable version evidence. Unknown or heuristic identifications are labeled as such instead of being turned into confident claims.
What can be ready in one week?+
A first candidate-versus-baseline report for either Android or iOS, using packages from your existing pipeline and the checks most relevant to your release process.
Bring us the workflow
you cannot see clearly.
We will tell you what a useful one-week pilot can cover—and what it cannot.
outreach@xesoft.dev ↗