1. Home
  2. Case studies
  3. App stores

Case study · Apple App Store + Google Play

The app works. Apple and Google can still stop the launch.

Rejected builds are only part of it. We have seen launches delayed by artwork, screenshots, reviewer access, metadata, subscription rules, billing, developer accounts and the way an app needs to be distributed. We work through the store problem that is actually holding the release up.

£30k+Existing app investment protected
6 weeksRejected build to both stores
4Blockers in one Apple review
2Different store processes
Stores
Apple App Store + Google Play
Platforms
iOS + Android
Blockers
Review, artwork, billing + access
Engagement
Release and submission support

The situation

Getting the app built is only half the launch.

An app can be working, tested and ready to go, then sit waiting because Apple or Google will not let the release move forward.

We have dealt with rejected builds, rejected artwork and screenshots, reviewer login problems, store metadata issues, subscription compliance, billing requirements, developer account setup and private distribution. Each one has delayed a client for a completely different reason.

Sometimes the fix is in the code. Sometimes it is in App Store Connect or Google Play Console. Sometimes it is the screenshots, a legal link, an account agreement or the route the app is being distributed through.

What has held releases up

  • Apple rejecting an app before launch
  • Artwork and screenshots not meeting store review requirements
  • Reviewer credentials preventing Apple from accessing the app
  • Google Play references appearing in Apple-facing metadata
  • Paid features being unlocked outside the required purchase flow
  • Missing subscription, Terms of Use or renewal information
  • Developer accounts, agreements and billing not ready for submission
  • Private apps needing a completely different distribution route
The app can be technically ready and still be nowhere near release. The store process is part of the build.
Apple and Google release work · App-store release support

What can delay a launch

The blockers do not all look technical.

Store approval sits across the app, the listing, the commercial model and the accounts behind it. Any one of them can stop the release moving.

  1. The app

    A working build can still be rejected

    We took over an iOS app after Apple rejection with more than £30,000 already invested. We kept what was worth saving, moved it to Flutter and got it live on both stores in six weeks.

  2. The artwork

    Screenshots can stop the submission too

    We have had App Store artwork rejected because the screenshots did not meet the review requirements. The creative had to be rebuilt around the actual app experience, correct devices and the store's required presentation.

  3. The review

    Apple has to be able to access and understand the app

    Invalid reviewer credentials, Google Play references in Apple-facing metadata and missing information have all created review blockers that had nothing to do with whether the core app worked.

  4. The money

    Subscriptions and paid access bring another set of rules

    Coupon codes unlocking paid functionality, in-app purchase requirements, Google Play Billing, pricing, renewal wording and Terms of Use all need to match the way the app charges users.

  5. The release

    Accounts and distribution can hold everything up at the end

    Developer enrolment, company accounts, agreements, billing setup and private distribution through Apple Business Manager or Managed Google Play all have to be in place before the app can reach the right users.

£30k+ existing investment protected
6 weeksrejected build to both stores
4different blockers in one Apple review
2stores with different release rules

The app was not always the thing holding the launch back. Store assets, accounts, billing and distribution have all delayed releases we have worked on.

What was at stake

  • Completed apps sitting unavailable to users
  • Existing development investment unable to generate value
  • Launch dates slipping because of review and account blockers
  • Paid features and subscriptions unable to go live compliantly
  • Rejected app recovered and launched
  • Artwork rebuilt around store requirements
  • Review and metadata blockers worked through
  • Billing, account and distribution routes put in place
Built does not mean launch-ready.

We work through the last-mile problems that stop apps reaching Apple, Google and the people they were built for.

Talk to us about your app

Apple App Store

The rejection might not be about the code.

Apple reviews the whole release. That includes what the screenshots show, whether the reviewer can log in, how the listing describes the product, how paid functionality is unlocked and whether subscription and legal information is complete.

We have worked through rejected artwork, invalid reviewer access, metadata problems, subscription requirements and purchase-flow issues alongside the app itself.

Artwork is part of the submission

App Store screenshots are not just marketing graphics. They need to represent the current app clearly, fit the required devices and satisfy the review requirements for the build being submitted.

Google Play

A second store means a second release process.

Google Play is not the Apple submission copied into another console. It has its own developer account, organisation, billing, testing and distribution requirements.

We have seen releases delayed while the correct Google account was created, organisation setup was completed, billing was configured and private app access was prepared for the people who actually needed the app.

Store release support can include

  • Rejected build and review diagnosis
  • Screenshot and artwork preparation
  • Reviewer access, metadata and listing checks
  • Apple IAP and Google Play Billing
  • Developer account and agreement setup
  • Public and private distribution routes
View support options →

Questions

Apple and Google release FAQs

Can Apple reject app screenshots or artwork?

Yes. Store screenshots need to meet Apple's current device, content and presentation requirements. We have had to rework artwork and screenshots where the submitted creative did not meet review requirements.

Can reviewer access delay an App Store submission?

Yes. If reviewer credentials or demo access do not work, Apple cannot properly review the app and the submission can be held up until access is corrected.

Can subscriptions or billing stop an app being approved?

Yes. Apple and Google have platform-specific requirements around paid access, subscriptions, billing, pricing, renewal information and legal links.

Can you help with private business apps?

Yes. We can help prepare the correct private distribution route, including Apple Business Manager Custom Apps and Managed Google Play where appropriate.

More questions? See our full FAQ →

Talk to us

App built, but still not through the store?

Send us the rejection, review message or blocker. We can work through the build, artwork, metadata, billing, account setup and distribution route that is holding the release up.

Launch blocked right now? Bring us the problem →

Hartlepool, UK. Working with clients across the UK, US, Middle East and Asia.