Release

App Store submission, handled.

Signing, metadata, privacy disclosures, review correspondence and rejections. The unglamorous week that decides whether anything launches.

Stack

App Store ConnectTestFlightPlay ConsoleFastlane

01Scope

What release management covers.

Everything between a finished build and a live listing.

Signing and pipelines
Certificates, provisioning, Play App Signing and a CI pipeline so releasing is a command rather than an afternoon.
Privacy labels and disclosures
App privacy details, tracking declarations and the Data Safety form, answered accurately — the most common cause of a late rejection.
Listing and assets
Title, subtitle, keyword field, screenshots and preview video, written for how people actually search the store.
Review and appeals
We answer reviewer questions and appeal rejections. Guideline 4.3 and 5.1.1 rejections are survivable with the right response.

02Store search

App Store Optimisation is not web SEO.

The store has its own ranking model, and the title and keyword fields carry most of it.

Title, subtitle and keyword field
Thirty characters, thirty characters and a hundred, weighted very differently. Wasting them on your brand name is the usual mistake.
Conversion beats impressions
Screenshots and the first two lines of the description move installs more than any keyword change, and installs feed ranking.

03FAQ

App Store submission: common questions.

How long does App Store review take?

Typically 24–48 hours for a straightforward submission, longer for a first release, an account-related change or anything touching payments, health or user-generated content. Plan a week for a first launch.

Our app was rejected. Can you fix it?

Usually. Most rejections are guideline 2.1 completeness, 4.3 spam, 5.1.1 privacy or metadata issues, and most are answerable with a change plus a written response rather than a rebuild.

Do you handle Google Play too?

Yes — Play Console setup, Data Safety, staged rollouts, pre-launch reports and target-SDK compliance.

Tell us what you're building.

Send the rough version. A senior engineer reads every brief and replies within one business day.