Publishing Your App on the App Store and Google Play: Step by Step

The app is ready, tested, and the team is happy, but your customers do not have it on their phones yet. Publishing an app on the App Store and Google Play is a separate stage with its own accounts, documents, a store page and a review. If you approach it unprepared, the release drags on because of rejections and resubmissions. Below is a step-by-step walkthrough of the process, focused on what the app owner needs to know.

Developer accounts first

In both stores, apps are published through a developer account. It is better to open it in advance: verification can take time.

Apple Developer Program

With Apple you can register as an individual or as an organization. For an organization, company details are requested, including a D-U-N-S number. Membership is paid and renewed regularly; see Apple's official page for current prices and terms.

Google Play Console

Registration on Google Play is also paid and requires verification of an individual or an organization. For new personal accounts, a requirement may apply to run closed testing before publishing for everyone. The rules change from time to time, so check Google Play's official help.

Whose name to register the account under

Open the accounts in your company's name and add the development team as members. If the app is released under a contractor's or a stranger's account, transferring or updating it later can become a problem. The app is your asset, and it should sit in your account.

Materials for the store page

Before publishing the app on the App Store and Google Play, prepare:

• a name: short, clear and consistent with your brand;
• short and full descriptions: what the app does and how it helps, separately in Russian and Uzbek;
• an icon: legible even at a small size;
• screenshots: for different screen sizes, showing key features;
• a privacy policy: a page available at a public link;
• support contacts: an email or website;
• an age-rating questionnaire: answers to questions about the content;
• a data section: what data the app collects and why;
• a test account: if a login is needed to sign in, demo access for the reviewer.

The privacy policy is usually placed on the company website. If there is no website, a simple page is enough, and this can be solved together with website development.

Publishing steps on the App Store and Google Play

1. Building and signing the release version. The app is signed with special keys. Store them securely: if a key is lost, updating the app on Google Play can become a serious problem.
2. Internal testing. The App Store has TestFlight, and Google Play has internal and closed testing tracks. Employees and loyal customers check the app on real phones.
3. Filling in the page. Texts, images and questionnaires are entered, and the countries where the app will be available are selected.
4. Submitting for review. The store checks compliance with its rules.
5. The result. The app is approved, or a rejection is sent with the reason.
6. Release. The app can be opened to everyone at once or gradually, to part of the users. A phased release helps catch a bug early.

How the App Store and Google Play differ

Aspect	App Store	Google Play
Account	Apple Developer Program, regular membership	Google Play Console
Testing	TestFlight	Internal, closed and open tracks
Review	Considered stricter, with human involvement	A mix of automated and manual
Data section	App Privacy	Data safety
Phased release	Phased release	Staged rollout
Installation without the store	Heavily limited	Possible for internal tasks

Why apps get rejected

A rejection is a normal thing, not a catastrophe. But if you know the most common reasons, most of them can be avoided:

• Crashes and bugs. The reviewer opens the app on different devices.
• Unfinished sections. Empty "coming soon" screens and buttons that do not work.
• The reviewer cannot sign in. A login is required, but no demo account is provided, or the SMS code goes only to a local number.
• No privacy policy, or the link does not open.
• The description and screenshots do not match the app.
• Unjustified permissions. Access to the camera, contacts or location is requested without explaining why.
• No account deletion. If the app has registration, it must also allow deleting the account.
• A copy of the website. Apps that simply show a web page can be rejected for lack of value.
• Payment for digital content. The stores have special rules for paying for digital services; if you sell subscriptions or content, study the current requirements in advance.

What to do if you are rejected

Read the response carefully: it usually names a specific rule and the problem. Fix the issue, add a comment if needed and resubmit. If you think the reviewer misunderstood something, you can send an explanation or an appeal. The main thing is to build in a time reserve for review before announcing a release date.

Updates and store visibility

Every new version also goes through review, so plan updates in advance. Update the page from time to time as well: an accurate name and description, quality screenshots and replies to reviews help the app show up in search and get more installs.

UFLEX not only develops the app but also takes over publishing on the App Store and Google Play completely: we prepare the materials, submit for review and respond to the comments. More details are on the mobile app development page.

FAQ

How long does the review take?

The timing depends on the store and the period and changes. So when planning a release, allow a reserve for review and possible fixes.

Do I have to open the account myself?

Yes, it is better for the account to be registered to your company. The developers are added as members and do all the technical work.

Can I release the app only in Uzbekistan?

Yes, in both stores you can choose the countries and regions where the app will be available.

If you need help publishing your app, leave a request or message us on Telegram, and the UFLEX team will take the process from start to finish.