App Store and Google Play Publishing

This package takes an app whose code is finished and gets it onto the App Store, Google Play or both: signed release builds, a complete store listing, privacy answers and the submission itself, all under developer accounts in your name. It suits founders whose developer has moved on, agencies without a Mac or store experience, and teams who have a working build but keep getting stuck at review.

Your accounts, my hands

You enroll in the Apple Developer Program and register a Google Play Console account, as a person or a company, and pay their fees directly. Company enrollment with Apple needs a D-U-N-S number, which can take days to arrive, so start early. You then invite me as a team member. I never publish a client app under my own account, because whoever holds the account controls the app's updates and its income.

What I prepare for the reviewers

• An Android App Bundle signed through Play App Signing, and an iOS build archived in Xcode on my Mac.
• Apple's App Privacy answers and Google's Data safety form, matched to what the app and its SDKs really collect.
• A demo login and review notes, so the reviewer can reach every screen.
• Permission texts that explain why the app asks for the camera, location or contacts.
• A check for in-app account deletion, which both stores expect when users can sign up; if it is missing, I flag it before submitting.

Where my part ends

Approval, review time and store ranking are Apple's and Google's decisions. When a build is rejected, I read the reviewer's note, explain the cause and resubmit within the plan's resubmission count. Changes to the app's code are not part of Starter or Business; Premium includes a few hours of them, and larger changes get their own quote. Google may ask a new personal account to run a closed test with a group of testers before production access opens, and that waiting time sits outside the plan's delivery days.