The app works on the team's device and all that is left is "the store upload". In practice this is a stage with dependencies on both sides: some things only the client can do, because they require a legal identity, a bank account or a business decision. This guide is a checklist for the product owner: what to prepare and what to ask, so that the launch does not stall on a document nobody wrote.
If you are trying to understand what drives the cost of the whole project, store submission is only one factor — the app development cost guide breaks down all of them. What it costs to build an app — the cost drivers
Developer accounts: whose name they are registered under
To publish in the stores you need a developer account in each. The important decision is whose name it is opened under. An account opened under the vendor means the app "lives" with the vendor: if the relationship ends, moving an app to another account is a separate process, and it needs to be started in time. The practical recommendation is therefore that the accounts are registered in your business's name from day one, and the vendor is given access as a team member.
What can be quoted from the official documentation: Google Play Console Help states that "Google Play offers two developer account types: Personal and Organization", and that an organization is asked for a D-U-N-S number and must keep the account details consistent with its Dun & Bradstreet profile. Apple's App Review Guidelines (section 5.1.1(ix)) say that apps in highly regulated fields such as banking, healthcare and gambling "should be submitted by a legal entity that provides the services, and not by an individual developer". If your app is in such a field, that is one more reason to open an organization account. For the current registration terms (who may register, which documents, which costs), check Apple's and Google's enrolment pages rather than relying on memory.
- Who owns the account and who has authority to accept terms on the company's behalf?
- Who receives review and rejection notices — one person's email or a shared address?
- How does the vendor get access, and how is it removed when the project ends?
What the client prepares: documents and company details
Most items in the following table do not require development, but all of them need a decision or a signature from someone in the organization. Starting them in parallel with development saves the wait at the end.
| Item | Why the store needs it | Question to check |
|---|---|---|
| Company and tax details | The stores tie the account to a legal entity to allow publishing and payments | Who in the business knows the required details and can fill them in? |
| Privacy policy | Apple: "All apps must include a link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible manner" (5.1.1(i)) | Who writes it, and who confirms it matches the data the app actually collects? Check with legal counsel |
| A support page and a way to make contact | Apple, section 1.5: "Make sure your app and its Support URL include an easy way to contact you" | Who answers messages, and at which address? Google Play Console asks for a contact email address |
| Demo account | Apple, section 2.1(a): provide "demo account info (and turn on your back-end service!) if your app includes a login" | Is there a test user with data that does not expose real information? |
The store listing: name, descriptions and screenshots
The store listing is what a user sees before downloading. According to the Google Play Console help page, you fill in an app name, a short description and a full description, and add preview assets such as screenshots and videos. Apple has parallel fields in App Store Connect, with its own screenshot specifications per device type. Take the current dimensions and length limits from each store's official pages.
- Name and descriptions in Hebrew and English, if the app is aimed at both audiences
- Screenshots that show the screens that do the work, not only a splash screen
- Text that describes what the app actually does — what does not exist in this version stays out of the description
On our mobile app development page, the store launch is described as part of the project deliverables: screenshots, descriptions and handling of rejections. What is included in app development — including the store launch
What happens in review
Both stores check the app before it is published. Apple's "Submit for review" page states that "Each platform can have one app version submission under review at a time", and that the App Review information section can carry context that helps reviewers. The "Before You Submit" list in the guidelines also says: "Enable backend services so that they're live and accessible during review". In practice: do not submit while the server is under maintenance, or with a broken demo-account link.
| Before submitting | Why it matters |
|---|---|
| A build tested on real devices | A crash during review can send the build back, and every return is another round |
| A live, stable backend | The reviewer needs to see the app working, not a loading screen |
| A demo account and a short description of the main flow | A reviewer who cannot log in cannot approve |
| A privacy policy and support page that load | A broken link is an avoidable failure that is easy to prevent |
A rejection: what to do
A rejection does not mean the app failed. The message usually states which section was not met; you fix it and submit again. What matters is knowing in advance who receives the message, who decides whether to fix or appeal, and what the agreement covers: whether handling rejections is part of the project or extra work. On our service page, responding to rejections appears as part of the store launch.
Who holds the keys after handover
After launch the app lives in the accounts, the signing credentials and the services connected to it. Our service page states that the code and the store accounts belong to the client. With any vendor, including us, confirm this in the contract and check in practice that the access is with you.
| Item | What to confirm |
|---|---|
| Apple and Google Play accounts | Registered in the business's name; at least two people on your side with access |
| Signing certificates and keys | Stored somewhere you control, not only on a developer's machine |
| Connected services (notifications, analytics, server) | Accounts in your name or transferred to you |
| Source code | A repository you own, with access arranged at project end |
If you are receiving an app from a previous vendor, or want to check what you were handed, there is a separate handover audit guide. And what happens after launch — OS updates, fixes and maintenance — is covered in the maintenance guide. A checklist for taking over a software project from a previous vendor
OS updates and new store versions are a reason an app needs work even after it is published. App maintenance costs — what is included and what changes
What we do at this stage
The mobile app development page describes the store launch as part of the project: ASO, screenshots, descriptions and handling of rejections, with the code and store accounts belonging to the client. If you are before submission and want to go through this checklist against your own situation, you can bring it to a conversation. Mobile app development — what is included and delivered