App Deployment and Compliance Guide for Google Play and Apple App Store

Publishing an app on Google Play and Apple App Store requires more than uploading the app build.

You must prepare developer accounts, business verification details, app metadata, privacy information, and platform compliance details before submission.

This guide explains what the client must prepare, what Mobikul handles, and which issues can delay app publishing.

Before You Start

Before app submission, make sure your Apple Developer Program and Google Play Console accounts are ready.

Your business details, app metadata, privacy policy, screenshots, and compliance declarations should also be prepared in advance.

Important:

App review, account verification, and policy approval timelines are controlled by Apple and Google. Mobikul cannot reduce or override these timelines.

Choose the Correct Developer Account

The developer account type is important because it affects app ownership, verification, team access, and store listing identity.

For company-owned apps, Mobikul recommends using an organization account on both Apple Developer Program and Google Play Console.

An organization account shows the registered company name as the seller or developer identity. It is better suited for business apps and branded apps.

Apple Developer Account Comparison

Source:

Apple Developer Program membership comparison: https://developer.apple.com/support/compare-memberships/

Important:

Using an individual account for a company-owned app may create identity or brand verification issues during review.

Note:

If the Apple source link does not work, Apple may have updated the page. In that case, check the latest membership details directly on Apple’s official developer website.

Google Play Console Account Comparison

Google Play Console also supports personal and organization account types.

The right account type should be selected before app publishing starts.

Source:

Google Play Console account verification details: https://support.google.com/googleplay/android-developer/answer/13628312

Mobikul Recommendation:

Create an organization account on Google Play Console if the app represents a business, brand, or registered company.

Note:

If the Google source link does not work, Google may have updated the page. In that case, check the latest requirements directly from Google Play Console Help.

Prepare the D-U-N-S Number

A D-U-N-S number may be required when creating an organization account for Apple or Google.

It is used to verify the legal identity of your business.

The business name and address linked with your D-U-N-S number should match your developer account details exactly.

Important:

Even a small mismatch in company name, address, punctuation, or formatting can delay account verification.

Mobikul Recommendation:

If you are applying for a new D-U-N-S number for Apple publishing, start the process from the Apple Developer portal.

Provide Google Play Console Access Early

Google may require package name registration before the Android test build can be generated.

The package name is the unique digital identity of your Android app.

Mobikul can complete this step if access to the Google Play Console account is provided early.

Important:

If package registration is not completed on time, Google Play submission may be delayed by up to 72 hours.

This package registration step is separate from the final Google Play review process.

Completing package registration early does not reduce the standard review time taken by Google after final submission.

Understand Google Testing Requirements

Google personal developer accounts may require closed testing before production release.

As of April 2026, this requirement applies to personal accounts. Google may update this policy in the future.

For personal accounts, Google may require 12 testers to remain opted in for 14 consecutive days.

Important:

The testers must be real users. Bots, fake testers, or inactive testers may be flagged during review.

If testers leave before the required testing period is complete, production access may be delayed.

If you want Mobikul to assist with tester arrangement and testing analysis, it may be handled as a separate paid service.

Complete EU DSA Compliance

If the app is distributed in the European Union, Apple and Google may require Digital Services Act compliance details.

You may need to declare your trader status and provide public business contact information.

This may include your business address, phone number, and other company details.

Important:

Apple may apply EU trader compliance checks more strictly. Complete these details before app submission to avoid regional publishing restrictions.

Prepare App Store Metadata

The client must provide all app store metadata before submission.

Metadata is used to create the app listing on Google Play and Apple App Store.

Metadata Required From the Client

• App name
• Short description
• Long description
• Keywords
• App icon
• Screenshots
• Banners
• App category
• Tags
• Support email
• Contact details
• Privacy policy URL
• Demo login credentials, if the app requires login

Client Action Required:

All metadata and store listing assets must be provided by the client.

Mobikul does not create app descriptions, icons, banners, promotional graphics, or marketing content by default.

Mobikul can assist with screenshots of the actual app on request.

Note:

Designing assets, writing metadata, creating promotional graphics, or preparing marketing content is a separate service.

Prepare Privacy and Data Safety Details

Apple and Google require accurate privacy and data safety information.

If your app collects user data, the store listing must clearly declare it.

This may include email, phone number, address, location, payment details, order history, device information, or other user data.

Important:

If the app asks for data but the store listing says no data is collected, the app may be rejected.

The client should provide a valid privacy policy URL before submission.

The privacy policy should match the actual app behavior and data usage.

What Mobikul Handles Under Standard Coverage

Mobikul handles the technical build and submission support covered under the standard scope.

Note:

Technical issue resolution does not include content changes, metadata corrections, business logic changes, policy consulting, or design asset creation by default.

What Mobikul Handles If Publishing Service Is Purchased

If app publishing service is purchased, Mobikul can assist with store submission tasks.

Important:

Mobikul can guide and assist with the publishing process, but Apple and Google make the final approval decision.

What the Client Must Handle

Some publishing requirements must be completed directly by the client.

Client Action Required:

Complete account verification, metadata preparation, privacy details, and compliance requirements before requesting final submission.

If Publishing Service Is Not Purchased

If app publishing service is not purchased, Mobikul will provide release-mode files only.

For Android, Mobikul will provide the release .aab file for Google Play Store submission.

For iOS, Mobikul may upload the build to the provided Apple Developer account when required.

All other publishing activities must be managed by the client.

This includes metadata entry, app listing setup, compliance declarations, review communication, and final store submission.

Common Reasons for App Publishing Delays

App publishing can be delayed even when the app build is technically correct.

Most delays are caused by account verification, missing metadata, incomplete compliance details, or platform policy issues.

Account Verification Failure

Apple and Google are strict about identity and business verification.

Blurry ID scans, incomplete documents, or mismatched business details can delay account approval.

D-U-N-S Mismatch

The company name and address on the D-U-N-S record should match the developer account details exactly.

Even minor differences can create verification loops.

Missing iOS Certificates

For iOS apps, the correct distribution certificates and Apple account access are required.

Without these, the iOS build cannot be uploaded properly.

Google Testing Not Completed

Google personal developer accounts may require closed testing before production access.

If the required testers are not maintained for the full testing period, production release may be delayed.

Incomplete EU Compliance

If EU trader status and public contact details are not completed, app availability in the European Union may be blocked.

Incorrect Data Safety Details

The data safety section must match the actual app behavior.

Wrong or incomplete data declarations can lead to rejection.

Content and Metadata Issues

Placeholder screenshots, dummy text, trademarked names, misleading claims, or incomplete descriptions can cause app rejection.

Final Checklist Before App Submission

Use this checklist before requesting app submission.

• Apple Developer account is created and verified
• Google Play Console account is created and verified
• Organization account is used for business or brand apps
• D-U-N-S details are available and accurate
• Google Play Console access is provided early
• Package name registration is completed
• App name and descriptions are ready
• Keywords and category details are ready
• App icon, screenshots, and banners are ready
• Privacy policy URL is available
• Data safety details are accurate
• Demo login credentials are available, if required
• EU trader status is completed, if applicable
• Google closed testing is completed, if required
• Client has confirmed whether publishing service is purchased

Official References

For the latest publishing rules, refer to the official Apple and Google documentation.

Note:

Apple and Google may update their policies, documentation links, and publishing requirements. Always verify the latest rules from the official platform documentation before submission.

Conclusion

App publishing depends on account readiness, business verification, app metadata, privacy details, and platform compliance.

Preparing these items early helps reduce avoidable delays during Google Play and Apple App Store submission.

Mobikul supports the technical deployment and publishing process based on the purchased service.

Client-side account setup, verification, metadata, privacy details, and compliance requirements must be completed on time for smooth app submission.