Go to stores knowing what's in your build
A methodical, per-platform review of how your game packages for each store — with a clear checklist and honest notes on anything worth addressing before you submit.
A second, careful look before the final push
A per-platform checklist
Each platform reviewed against its own requirements — store guidelines, file structure, metadata, asset specs — not a generic pass applied to all of them.
File and asset review
A look at your bundle contents and assets for anything that's likely to cause rejection or affect performance on a given platform — caught before submission rather than after.
Clear, prioritised notes
Observations delivered as practical notes — what to address, why it matters for each platform, and roughly how much effort each item involves. Easy to prioritise and act on.
Build issues at submission time are stressful and slow
The final stretch of a release is rarely when you want surprises. But store submissions have a habit of surfacing problems that weren't visible during development — asset specifications that differ between platforms, metadata that's missing or wrong, bundle sizes that put you outside acceptable ranges on one target but not another.
For cross-platform releases, the surface area for these issues is larger. Each platform has its own submission process, its own requirements, and its own ways of rejecting builds. Catching those things before submission — rather than through a rejection notice — saves time and the particular stress of trying to fix things when you thought you were already done.
Methodical, platform-by-platform, without fuss
The Build & Bundle Check works through your game's packaging on each platform you're targeting. We look at bundle contents, asset specifications, metadata completeness, and the configuration details that stores are known to reject or flag — using a structured checklist for each platform rather than a single pass.
The output is a set of notes for each platform: what looks fine, what's worth addressing, and what the priority level is for each observation. We aim to keep the notes actionable rather than exhaustive — something your team can work through without having to decipher what the feedback actually means.
Light on your time, thorough in coverage
Share your builds
You send us your current builds and the platforms you're targeting. A brief note on anything you're already concerned about is useful but not required.
We review each platform
Each build is reviewed against its platform's checklist. Bundle contents, assets, metadata, and configuration all get a careful look.
Notes compiled and delivered
You receive a set of per-platform notes — what was reviewed, what looks fine, and what's worth addressing, each with a priority level.
Your team acts on what matters
You decide what to address and in what order. The notes are yours — no follow-up required from our side unless you want it.
Priced simply, scoped clearly
Build & Bundle Check
One-time review service
The service covers up to three platforms. If you're targeting more, reach out and we'll discuss the scope before confirming anything. The review is a one-time service — there's no retainer or expectation of further work unless you'd like it.
The case for a second look
Stores review differently
Apple, Google, Steam, and console stores each have different automated checks and human review patterns. What passes on one is sometimes flagged on another. Knowing this ahead of submission is useful.
Build fatigue is real
The team that built the game is usually deep in the details of the game itself by release time. That context is valuable for development and less useful for methodical package review — which is a different kind of attention.
Small issues compound
A single missing icon size, a bundle identifier mismatch, or an asset over a platform's recommended limit can each independently delay submission. Finding several at once, before submission, saves more time than finding them one at a time through rejections.
What this review does and doesn't cover
The Build & Bundle Check focuses on packaging — how your game is bundled, structured, and presented to each store. It doesn't cover gameplay quality, performance profiling, or functional testing. If those are concerns you'd also like addressed, reach out and we can discuss whether the scope needs to be adjusted.
Honest notes, no pressure
We keep the notes actionable
We don't deliver a lengthy report with unclear implications. Each observation comes with a priority level and enough context that your team understands what to do with it — or whether to do anything at all.
No follow-up required from our side
The review is complete when you receive the notes. You don't need to check back in with us, and there's no ongoing engagement. If questions come up while acting on the notes, you're welcome to reach out — but it's not expected.
Not sure if the timing is right?
The check is most useful when your builds are close to what you'd submit — not necessarily final, but representative. If you're not sure whether you're at that stage yet, ask. We'll give you an honest read.
Three steps to a reviewed build
Go to submission with a clearer picture
If you're nearing release and want a careful, impartial look at your packaging before it goes to stores — this is a low-friction way to get one.
Two more ways Bridgeplay can help
Platform Fit Consultation
A focused planning session to help you decide which platforms genuinely suit your game, with a short written roadmap delivered after.
Single-Codebase Setup
A tidy shared project structure with input handling for touch and controller, and a sample build on two targets — a clean start you can extend at your own pace.