Publish app to App Store
React Native & Flutter shipped to both stores
- Senior engineers · IST + EST overlap
- NDA on day 1
- 24-hour reply
Tell us what you need fixed
Reply in 24 hours · NDA on day 1 · No spam.
Publish app to App Store — done properly, by senior engineers
Everything needed to publish app to App Store and Google Play is covered here: developer accounts, code signing, store listings, privacy disclosures, review responses and the first staged release. Publishing is less about uploading a binary than about meeting two sets of account, signing and policy rules. On Apple’s side that means an organization developer account, which needs a D-U-N-S number, certificates and provisioning profiles for the capabilities you use, a privacy manifest for required-reason APIs, App Privacy labels, export compliance answers, in-app account deletion if users can sign up, and a working demo login for App Review. Google Play adds Play App Signing with a separate upload key, Android App Bundles, a Data safety form, target API level rules, sensitive permission declarations and, for new personal accounts, a closed test before production access. Signing moves into fastlane match or EAS credentials so it no longer depends on one laptop. Listings, screenshots and review notes are prepared to match what the app actually does, and rejections are answered with specific changes rather than appeals. After approval, Krapton configures phased release on iOS and staged rollout on Play, connects crash reporting, and leaves a release checklist for every future update.
What you're seeing
You're ready to ship but the App Store / Play Console maze — provisioning, certificates, signing, metadata, screenshots, review — keeps blocking the release.
Our approach
We handle the full release workflow: signing & certs, store listings, screenshots, privacy policy, App Review responses, and post-launch monitoring on both stores.
Symptoms teams come to us with
- Xcode archives fail to upload with provisioning profile, certificate or entitlement mismatch errors.
- App Review rejects the build for missing demo credentials, incomplete metadata or no account deletion option.
- Play Console blocks the production release until the Data safety form and policy declarations are complete.
- The only person who can sign releases has left, and the upload key or certificate went with them.
- App Store Connect emails warn about missing privacy manifest entries for SDKs bundled in the app.
What we check first
- Signing assets created by hand on one Mac, never stored in a shared, encrypted location.
- Privacy labels and Data safety answers that do not match what bundled analytics and ad SDKs collect.
- Login-gated features with no reviewer account, or backend features disabled in the review build.
- Digital goods sold through external payments where store rules in that region still require in-app purchase.
- Sensitive permissions such as background location or SMS requested without a declared, approved use case.
Concrete deliverables, no fluff
Every engagement ends with measurable, documented outcomes — no black-box agency reports.
- Reproduction of the bug or perf issue on a real device
- Implementation behind a PR you review
- Verified fix on iOS and Android (real hardware, not just simulator)
- Release notes + App Store / Play Store update checklist
What changes after we ship
Signing that survives staff changes
Certificates, profiles and the upload key live in fastlane match, EAS credentials or your secrets manager with documented access, and Play App Signing protects the app signing key itself.
Accurate privacy and policy disclosures
App Privacy labels, the Data safety form and privacy manifests are completed from an audit of your code and SDKs, which reduces rejections and policy warnings after release.
Store listings ready for review
Titles, subtitles, descriptions, keywords, screenshots and preview assets are prepared per store and locale, along with review notes and a demo account that exercises every gated feature.
Automated, repeatable release pipeline
fastlane or EAS Submit uploads builds to TestFlight and Play testing tracks from CI, so each update follows the same checked path instead of a manual upload from someone’s machine.
From brief to shipped fix
A transparent, low-risk process — a senior engineer reads your brief personally, and nothing starts until you approve a written plan and price.
01
Diagnose
A senior engineer reviews your brief, reproduces the issue, and pinpoints the real root cause — not the symptom — before any code is touched.
02
Scoped plan & quote
You get a written plan to publish App to App Store, a firm timeline, and a fixed quote. Nothing starts until you approve it — no surprise invoices.
03
Ship the fix
We implement on a branch and open a pull request you review, working to your code-review standards on your repo — never a black box.
04
Verify & hand off
We verify on staging and production, share before/after evidence where it applies, and leave you a short hand-off note so the fix sticks.
Situations we handle
First launch of a new app
A founder or agency-built app is feature-complete, but nobody on the team has shipped to either store and the accounts, signing and listings still need to be set up correctly.
Repeated App Review rejections
An app stuck in a rejection loop over guideline issues such as login services, in-app purchase, minimum functionality or metadata, where each resubmission fixes one point and surfaces another.
Transferring apps between accounts
Moving an app from a freelancer’s or agency’s developer account to your company’s, including App Store app transfer, Play Console transfer, signing keys and the credentials CI depends on.
Why teams hand this task to Krapton
Senior engineers only
Your brief is read and handled by a senior engineer — no junior hand-off, no sales-rep filter in between.
Root cause, not a patch
We reproduce and fix the underlying cause, then add a guard so the same class of issue does not quietly return.
Your repo, your standards
Every change lands as a pull request you review, on your repository, following your existing review process.
NDA on day one
Confidentiality and IP are covered before we look at a single line of code. All work stays in your accounts.
Fixed quote up front
You approve a written plan and price before work starts. If scope changes, we re-quote in writing — no surprise invoices.
Proof, where it applies
Performance, SEO and reliability work ships with before/after evidence so the result is measurable, not anecdotal.
Three ways to engage
No retainer required. Pick the model that matches the work — pricing for this task starts from $500, with a fixed quote before anything starts.
Per task
Most popular
One clearly-scoped fix at a fixed price. Best when you know exactly what is broken and want it handled end to end.
- Fixed quote up front
- One PR, reviewed by you
- No retainer required
Hourly
Pay only for the hours worked. Best for diagnostics, audits, or exploratory work where the scope is still emerging.
- Weekly timesheets
- Pay for what you use
- No minimum commitment
Per sprint
A focused 1–2 week sprint when the work is bigger than one fix but smaller than a full project.
- 1–2 week blocks
- Clear sprint goal
- Scale up or stop anytime
Industry-standard stack, no proprietary lock-in
Publish app to App Store — your questions, answered
How much does it cost to publish App to App Store?
Pricing starts from $500 and depends on the scope we find during the diagnostic. You get a fixed, written quote before any work begins — most engagements like this run 2–8 weeks.
How long does it take to publish App to App Store?
Typically 2–8 weeks for a focused engagement. After a short diagnostic we commit to a firm timeline so you know exactly what to expect.
What do we need before we publish app to App Store and Google Play?
You need developer accounts in your company’s name, a privacy policy URL, and accurate answers about data collection. For Apple, and for Google Play organization accounts, a D-U-N-S number is required, and it can take time to obtain, so start there. You also need final app icons, screenshots, a support URL and, if the app has logins, a demo account the reviewers can use.
Should the app be published under our account or the developer’s account?
Under your own account, always. The developer account owns the app listing, reviews, ratings and, on Google Play, the relationship to the signing key, so publishing under a vendor’s account makes you dependent on them. Krapton works inside your accounts through App Store Connect roles and Play Console user permissions, and transfers are possible later but take paperwork and coordination.
How do you handle an App Review rejection?
By fixing the cited guideline and explaining the change precisely in the App Store Connect reply. Most rejections name a guideline, such as App Completeness, Login Services or In-App Purchase, often with a screenshot or crash log. We reproduce what the reviewer saw, change the app or metadata, and resubmit with clear notes. An appeal to the App Review Board is used only when the rejection misreads how the app works.
Keep exploring
Related tasks and resources to plan your next step with Krapton.
Let's get this off your plate
Send a 60-second brief on Publish App to App Store and a senior engineer replies within 24 hours with a plan and a fixed quote. NDA on day one, no retainer required.