Getting a build through review
We review the build, store information and test results against the relevant requirements, then help resolve issues before submission. The platform makes the approval decision.
Run the readiness checklist
App Store Launch & ASO
Take your Unity game through the technical steps towards an App Store or Google Play release. We help with builds, store listings, beta testing, submission and review feedback.
Taking Pocket Factory to iOS and Android
Developed by Ocean View Games for Mojo Games.
Pocket Factory is a hyper-casual merge game developed for Mojo Games. Our work covered the core gameplay, monetisation and release on iOS and Android.
Preparing a release brings the build, purchase flows, store information and testing together. We use that delivery experience to help teams work through their own submissions.
An unfinished brief is fine. The first conversation helps establish scope.
What are you starting with?
Getting the game built is only half the battle. Getting it approved, optimised and visible is where projects stall. Tell us where you are.
Already been rejected
Privacy manifest errors, data safety mismatches, guideline 4.3, login walls. We interpret the specific rejection code, implement the required fix and handle the resubmission.
Common rejections and fixesLive but not converting
Review your store copy, screenshots and available conversion data to identify changes worth testing. We help the listing explain the game clearly to the intended audience.
Explore monetisationOur launch and submission lifecycle
Check the build, prepare the listing and work through submission feedback. Store approval and review timing remain with the platform.
1. Technical compliance audit
Validate the build before the store page: 64-bit and target API levels, privacy manifests and tracking declarations, and file size so users can actually download the game.
2. ASO and asset production
Treat the store page as a sales funnel. Keyword research for genre, mechanic and comparison terms, gameplay-first screenshots, and video previews where they help explain the experience.
3. Submission and review resolution
Age ratings, content declarations and export compliance, then direct communication with the review teams, interpreting rejection guidelines and turning around fixes so you do not have to.
Store launches we have run
Games taken through store submission and release by Ocean View Games.
Pocket Factory
Dual-store launch
The Challenge: Ship a merging strategy game to the App Store and Google Play for Mojo Games.
The Result: Both submissions taken through review to release alongside the core game build.
Nova Blast
Adding a store without disrupting one
The Challenge: Bring Foil Hat Games' live iOS title to Google Play without breaking the existing release schedule.
The Result: A Google Play submission and Android release alongside the existing iOS build.
What the launch service covers
The whole pipeline, from the store listing to the weeks after launch. The rejection patterns below are the ones we design submissions to avoid.
Store listing and ASO
Title and keyword optimisation, screenshot design that shows gameplay in the first two frames, video previews, and localised listings for target markets.
Privacy and compliance
Review SDK data use, required privacy declarations, tracking permissions and content ratings with the people responsible for your privacy policy and store accounts.
Submission management
Binary upload and build configuration, IAP and subscription product setup with review screenshots, review notes and demo accounts, and managing resubmission cycles.
Launch day and beyond
Staged and percentage rollouts, launch-day monitoring of crash, ANR and review sentiment, and a hotfix submission process established before launch, with review timing controlled by the store.
Common Apple rejections
Review feedback can concern privacy declarations, purchase flows, launch crashes, app functionality or incomplete metadata. We investigate the specific notice against the submitted build.
Common Google Play rejections
Review feedback can concern data safety, target API requirements, audience settings, permissions or build configuration. We check the requirements that apply to your submission.
Working together
Start with a conversation about what you are launching, which stores you are targeting and where you need help getting the build through the final requirements.
If you have already been rejected, send us the rejection notice. Most are one of a handful of patterns, and we can usually tell you quickly what the fix involves.
David and Adam stay close to the technical and submission work. We communicate with the review teams directly, so you are not interpreting cryptic rejection codes.
After release, we can help monitor crashes, prepare updates and review store feedback. The support period and responsibilities are agreed before launch.
Meet the teamPlan your launch
Free tools and guides to check readiness before we talk.
Platform Readiness ChecklistCheck whether your game meets App Store and Google Play requirements before submission.Explore →Game Development Cost EstimatorA ballpark for launch support based on your platforms and submission scope.Explore →Read: platform readiness before launchThe technical and store requirements that stall submissions.Explore →Mobile developmentThe development side, if the build itself still needs work.Explore →
Frequently Asked Questions
Yes. Share the rejection notice, build version and review correspondence. We assess the stated issue, explain the changes required and scope the fixes and resubmission work. Approval and review timing remain with Apple or Google.
The estimate depends on the stores, build condition, purchase systems, listing assets and any unresolved review issues. We agree who supplies the copy, artwork and declarations, and which submission and post-launch tasks are included.
Yes. We can help with relevant keywords, store descriptions, screenshots and previews, using available listing data to identify changes worth testing. ASO can improve how clearly a listing presents the game; it cannot guarantee a ranking or number of downloads.
Your organisation should own the developer accounts and store listings. You grant the access needed for the agreed work, retain control of the release and provide the business and policy information required for submission.
Yes. We can configure test tracks, distribute builds and help collect and prioritise feedback before submission. We agree the testers, devices and acceptance criteria with your team.
We start with the build or source project, target stores, account access and release plan. We also review the available icons, screenshots, descriptions, privacy policy, audience information and purchase details, then identify anything missing.
We can scope Steam build preparation and store setup separately from mobile submission. Tell us what is already configured and whether you need technical release support, listing assets or both.
Preparing a game for release?
Tell us what you are launching, which stores you are targeting and where you need help getting the build through the final technical and submission requirements.
Discuss your launch