getyear.Start a project

Free tool · Private iOS release self-assessment

Is your iOS app actually ready to submit?

A practical evidence check for teams approaching TestFlight or App Review. Keep source, physical-device, privacy, commerce, distribution and launch proof separate—without uploading a project or giving up an email address.

The page and full result are free. Answers stay in this browser tab. The output is a self-reported planning snapshot, not certification or an App Review guarantee.
13–20
conditional evidence checks
06
distinct release layers
ZERO
uploads, logins or email gates

Free tool · About 7 minutes

Map the evidence before the release claim.

Choose the current state of each gate. Evidence coverage weights Verified as 1, Partial as 0.5, and Not yet or Not sure as 0. Required gates clear only with Verified; the result does not predict App Review approval.

App profile

Does the app let people create an account?
How does the iOS app sell digital access?
Will App Review need sign-in or gated access to reach core functionality?
Does review depend on a live backend or external service?
Does the app use a third-party or social login for its primary account?
01

Source, build and archive

0%
Release gateRequired evidenceThe intended Release configuration builds cleanly from the release source.

Dependencies, scheme, bundle identifier, capabilities and environment match the candidate you plan to distribute.

Release gateCritical product logic has repeatable automated evidence.

Tests cover the source of truth behind visible claims, including deterministic failure and recovery states.

Release gateRequired evidenceA signed archive for the intended app identity validates successfully.

The archive has the intended version, signing, entitlements and embedded frameworks—not a simulator-only build.

02

Device and critical journeys

0%
Release gateRequired evidenceThe release candidate's critical journey works on a physical target device.

Evidence includes a clean install and, when applicable, upgrade and persisted-data behavior.

Release gateRequired evidencePermissions, interruption, offline and recovery states have been exercised at the real layer.

Simulator fixtures are not being used as proof for hardware, live Apple services or real account authorization.

Release gateAccessibility, small-screen layout and release performance have a checked baseline.

The main path has been checked with Dynamic Type or VoiceOver as relevant, realistic content and crash diagnostics.

03

Privacy, accounts and release boundary

0%
Release gateRequired evidenceFirst- and third-party data flows match the App Store privacy answers.

The inventory covers analytics and SDK behavior as well as data used for core app functionality.

Release gateRequired evidencePrivacy manifests, required-reason APIs and included SDKs have been audited.

The packaged app contains valid declarations for the code that will actually ship.

Release gateRequired evidenceA person who creates an account can initiate complete account deletion inside the app.

The path handles associated data, active subscriptions and authentication-token revocation as applicable.

Release gateRequired evidenceThird-party primary-account login has an equivalent privacy-preserving option, or a documented Guideline 4.8 exception applies.

Verify the policy fit and shipped authentication flow. Do not enter provider names, credentials or user data in this checker.

Release gateRequired evidenceDebug fixtures, test accounts, staging endpoints and internal controls are absent from Release behavior.

Share, export, logs and public UI cannot expose simulated, secret or internal-only material.

04

Commerce and entitlements

0%
Release gateRequired evidenceThe required commercial agreements, tax and banking state are active for this release.

A local price screen does not substitute for the current App Store Connect commercial state.

Release gateRequired evidenceIn-app purchase identifiers and availability match App Store Connect.

Products load in the intended environment and the app handles unavailable or incomplete store state honestly.

Release gateRequired evidencePurchase, restore and entitlement recovery have worked through sandbox or TestFlight.

Local StoreKit remains useful deterministic evidence, but it is not being treated as account-backed transaction proof.

05

Candidate, store and review

0%
Release gateRequired evidenceThe exact build has finished processing in App Store Connect and is selected for the app version being submitted.

Verify bundle identity, version, build number, processing state and selected build. TestFlight can add useful evidence, but it is not a universal submission prerequisite.

Release gateRequired evidenceMetadata, screenshots, privacy, support and age-rating answers describe the submitted build.

Every public promise can be reached in the candidate without hidden setup or unsupported claims.

Release gateRequired evidenceApp Review has working access to every gated core path.

App Review information explains the shortest truthful path and supplies valid demo access or settings in App Store Connect. Never enter credentials in this checker.

Release gateRequired evidenceThe backend and external services needed during review are available for the selected candidate.

The review environment, required content and recovery path work without internal intervention, expired data or an unannounced maintenance window.

06

Launch operations

0%
Release gateCrashes, support, conversion-critical events and store feedback have named owners.

The first 72 hours have a decision cadence and a privacy-proportionate signal set.

Release gateThe team has a mitigation path and names every remaining external gate.

Rollback, feature containment or support response is defined; approval, retention and revenue are not inferred from technical proof.

Need the blocked path fixed?

Turn the top release risk into verifiable evidence.

Copy the summary above, open the project brief, then paste it into your outcome. The first scope follows the riskiest unproven gate—not a generic redesign.Copy above, then open the brief

01 / FAQ

Does a strong result guarantee App Review approval?

No. The result reflects only the answers selected in this browser. Apple makes the review decision, and this tool does not inspect the source, device, accounts or App Store Connect state.

02 / FAQ

Why is a TestFlight install separate from a local archive?

An archive proves a local packaging and signing state. A processed TestFlight build adds evidence that a specific uploaded candidate reached Apple's beta distribution path and could be installed by a tester, but TestFlight is not a universal App Review submission prerequisite.

03 / FAQ

Are audit answers uploaded or saved?

No. Answers and scoring stay in component memory in this browser tab and disappear on refresh. The page still makes ordinary document and asset requests to the hosting infrastructure.

04 / FAQ

What should a blocked team do next?

Start with the earliest required gate that lacks current evidence, reproduce it at the correct layer and close that narrow path before widening the claim or rerunning the whole release matrix.

SELECT COLLABORATIONS · 2026

What is the first unproven release gate?

Start with a short brief