Skip to content
ENS.EG

Publishing an App on Google Play and the App Store: Accounts, Rejection and Ownership

31 Oct 2026

A finished build is not a published app. The developer account belongs to your company, the listing has to match the binary, and a rejection is answered from the written reason. This guide separates what ENS prepares from what only the client can own.

Publishing is a separate job from building. A finished app can still miss a launch date because the developer account sits in the wrong name, the listing describes a feature the build does not contain, or the reviewer cannot sign in. Companies in Egypt often meet that gap in the last week, after a branch or a franchise partner has already been given a date. The account, the listing and the review belong in the scope, and each one needs an owner inside your company.

Google Play and the App Store record who has the right to publish. If that record is in the name of the software company, a later change of vendor stalls, replies to user reviews never reach your staff, and taking the app down is not your decision. An organization account asks for the company papers: commercial register, tax card, and authority for the person who accepts the invite. Those documents are yours. We do not draft a register that does not exist. Any fee for opening the account is paid by you to the store. The figure changes and is published on the store site, so it does not belong in a build quote.

What you own

  • A Google Play account and an Apple account in the company name, with a person who can accept an invite and read the verification code.
  • A support email and a phone number that an employee actually reads, because reviewers and users write to the address on the listing.
  • A privacy policy on a URL you control, describing the data this app collects.
  • A demo login for the reviewer when the app is closed to the public, filled with data that looks like a working day.
  • The decision on the app name, the category and the countries where it will be offered, before the build is uploaded.

The listing is a product page

Many people see only the name, the short text and the screenshots before they install. If the text says payment happens inside the app and the build has no payment, the review fails or the first week brings a low rating. Write the description from the screens that exist today. Category changes what the reviewer expects: a restaurant ordering app is not judged as an internal staff tool. The icon and the name have to match what opens after install, rather than a campaign that was postponed.

Phones set to Arabic are common among people installing from Egypt. Screenshots in English only, or a marketing poster whose sentence never appears inside the app, make the listing look unfinished. Capture the Arabic interface on a phone-sized frame: the first screen, the screen where the main action happens, and a result screen such as an order being tracked. If you publish English as well, repeat the set from the English interface. Do not place a price, a phone number or another company logo in a screenshot unless it is really visible in the build you submit.

Why a review comes back rejected

  • The reviewer cannot get past the login, or the demo account is empty.
  • The app asks for location or photos with no sentence, in the screen or in the listing, that explains why.
  • The privacy policy link is broken, or the page describes a different product.
  • The build crashes on the first path the reviewer tries, or it is a website stretched to full screen with no app behaviour.
  • The description mentions financial, medical or child-directed use that the build and the policy do not support.

A rejection is a message with a reason. The useful response is a new build or a corrected listing that answers that reason, then a short note in the review reply that says what changed. Arguing in the note with no change rarely moves the review. We read the message, map it to a screen or a listing field, and resubmit. What still waits on you is anything only your company can send: a document, a domain, or a login that belongs to your staff.

What we prepare, and what stays with you after launch

We prepare the release build, the screenshots from that build, and the listing text with you. We upload to the accounts you own, answer the review with the technical change, and name the item that is blocked on a paper or an email only your employee can send. After launch we do not keep ownership of the account. An update, a reply to a one-star review, and the decision to hide the app stay with the person you name inside the account. If that person leaves and nobody else was added, the next update waits even when the build is ready.

The week you submit, settle three practical points. Who receives the store message on a phone they actually carry. Where the privacy policy lives, on a page that will still resolve after the campaign site is switched off. Whether the legal name on the company papers matches the name the user will see. A one-letter gap between the register and the app name is not fixed from a design screen. Also name the first country. Offering every country before you have tried registration or checkout with a real user in Egypt widens the review and adds no customer.

Two published references, and a different path for each product

Al-Thawra Restaurants is a system we designed and built for the menu, online ordering and delivery, with an iOS app and an Android app on the App Store and Google Play where the customer orders and tracks the order. The website is live at elsawra.net. That is a customer app on both stores, and it shows the publishing shape. It is not a template for every project. Ownership is clearer on the ordering system that is rebranded in the restaurant name: a website on the restaurant domain, an iOS app, an Android app and an operations dashboard, submitted under the restaurant developer accounts. The same checks apply when the app is for drivers, staff or patients: the account is in the publisher name, and the listing matches the build.

Do both stores have to ship on day one?

In the Egyptian market Android covers a wide share of the phones used in daily trade, and iPhone users still expect the App Store when the brand is a chain or a clinic they already know. Shipping one store first is reasonable when the other account is waiting on a document. Write that in the plan. Do not lock two dates until both accounts can receive a build.

Is a file in a chat enough?

A file on WhatsApp is not a store listing. Android can be installed from a file for a closed staff pilot. iPhone distribution outside the store is a different account setup, and a weak path when the user is a customer. A public app goes through the stores. An internal staff tool may use a private distribution list, and that decision is separate from a consumer launch.

See the customer app published on both stores in Al-Thawra Restaurants, and publishing under the restaurant accounts in the white-label ordering system. Timing for the build and the first submission is in how long a mobile app takes, and the service is mobile app design and development.

Send who will own the accounts, whether both stores are required together, and whether a privacy page already exists, from start your project. The WhatsApp button at the bottom of this page opens a chat tied to this guide, which is the right place for a photo of a past rejection or of the account screen.

Have an idea or a system that needs building?

Tell us about your project in three short steps. We will review it and contact you to agree on the next step.

Start a project