App store publishing and management

We prepare your app for the App Store and Google Play in developer accounts your company owns, then handle the day-to-day work in them. On Google Play we release it for you; on the App Store we prepare every submission in full and a person on your team sends it. We prepare the paperwork and guide the person who signs for your company through every step, on a call or in person. Then we join your store team, look after the listings, and prepare the store review and every update. The accounts, the app, its users and its ratings stay yours.

Who it is for

Companies with an app ready for the stores, built by us or by another team, and companies whose app is already live and needs someone to run its listings and updates. It suits a business that wants its own name on the store page without learning two store consoles.

It is for registered companies: both stores identify a company by its D-U-N-S number from Dun & Bradstreet, and Apple does not accept trade names or branches. Building the app and running its servers are separate services.

What we handle

• Accounts and papers. The D-U-N-S request, the Apple Developer Program enrolment and the Google Play organisation account, with your legal name and address matching in every record. Apple needs a working website on a domain your company owns and a work email on it, and Google asks for a contact email on the same domain. If you have neither, we can build the site and set up the email, with the domain in your company’s name.
• Listings in Arabic and English. Texts and screenshots for each store, Apple’s privacy details and Google’s Data safety form. You approve them, because your company answers to the store for what they say.
• Review and release. Signed builds; test versions prepared for TestFlight, which your team sends, and Google Play testing tracks; notes and a demo account for the reviewers; and fixes and replies when a build is rejected. Apple and Google make the final decision on approval.
• After launch. Updates, crash reports, store reviews, and store requirements that change, such as the Android version Google Play requires new apps and updates to target.

How it works

1. Check. On the free call we see what your company already has, find what is missing and agree with you which route suits you.
2. D-U-N-S number. If you do not have one, we prepare the request. The contact on it is someone at your company, because Dun & Bradstreet may ask them for your business registration documents.
3. Your signatory opens the accounts. This is the step we cannot do for you. A person who can legally bind your company, such as an owner, founder or executive, enrols with Apple and registers with Google Play. They use their own Apple Account with two-factor authentication and their own Google Account, give their real legal name and, for Google, their official ID, then accept each store’s agreement and pay its fee in the company’s name. If they are not the owner or founder, Apple asks for a colleague who confirms their authority. We prepare every form and guide them through every step, on a call or in person.
4. They invite us. Our engineers join your accounts with their own logins and only the roles the work needs. We never ask for your password, and you can remove our access at any time.
5. Review and release. We prepare the listing and build and sign the app. On Google Play we send it for review and release it. On the App Store, Apple asks the company that owns the app to submit it, so a person on your team presses Submit, for review or for TestFlight testing, on a submission we have prepared in full.
6. After launch. We release updates on Google Play and prepare each App Store update for your team to send, check crash reports and store notices for the period your scope covers, and tell you when your account holder must act, such as accepting Apple’s updated agreements or renewing the yearly membership.

Your own accounts keep the app yours. Your company appears as the seller on the App Store and as the developer on Google Play, and no other company’s app shares the account, so a problem with another company’s app is far less likely to reach yours. If we stop working together, nothing has to move: you remove our access and replace the keys we used, and your live apps stay in the stores.

For Android only, we can instead publish your app in our own Google Play account if you prefer, with your written permission to use your brand. Google Play then shows our company’s name and contact details as the developer, and a problem with any app in our account can affect every app in it. Apps that sell anything in the store stay in your own account. When you ask, we start Google’s transfer to your own Google Play account; it needs your own account, and both accounts in good standing. We agree the route with you on the free call. iPhone apps always go in your own Apple account, because Apple requires the company that owns an app to publish it. This option is not available for financial, health or government apps.

Timeline and cost

Part of the wait is outside our control and yours: Dun & Bradstreet and both stores check your company first, and neither store gives a total time for that check. Time and cost depend mostly on:

• what your company already has, such as a D-U-N-S number, a website and work email;
• one store or both, and how many apps;
• whether the app sells anything in the store, which adds agreements, tax forms and a bank account in your company’s name;
• whether the app is in a regulated field such as finance or health, where Google Play asks for licences or proof of permission;
• how long you want us to run the accounts.

In your own accounts, Apple’s yearly membership fee and Google’s one-time registration fee are paid by your company, in its name, and are separate from our price.

After the free call, you get a written scope with the timeline and the price, before you pay any deposit.