Service 3 — $360 USD
A second set of careful eyes before you release.
Your port is nearly there. This service takes a calm, thorough look at what's in front of you — performance, readability, and store requirements — and delivers clear notes so nothing small slips through at the end.
Request a polish passWhat this gives you
A release you can feel settled about
Getting to a finished port takes a long time and a lot of attention. By the end, it's genuinely hard to see your own work clearly. This pass is a way to hand that final review to someone who can look at it fresh — not to redo the work, but to catch the things that are easy to miss when you've been close to something for months.
Performance review notes
We note where frame rate, loading, or memory handling might cause problems on lower-end devices — with practical observations, not a benchmark spreadsheet.
Text sizing guidance
On-screen text that read fine during development can be a strain on an actual phone. We identify anything that could be improved and suggest sizing adjustments.
Store-prep checklist
A tidy checklist covering what the app stores expect — metadata, screenshots, age ratings, and the other requirements that are easy to overlook.
What gets missed
The end of a project is when small things fall through
Nobody ships a port hoping players will notice rough edges. But toward the end of a long project, attention spreads thin. The big decisions are made. The controls work. The game runs. It's tempting to call it done.
That's usually when the smaller things surface — a line of text too small to read comfortably, a moment where the frame rate dips on an older phone, a store submission that gets bounced because of a missing content descriptor. None of these are disasters on their own, but they add friction between your work and the players you're hoping to reach.
A polish pass isn't about doubting the work that's been done. It's about giving the final version the same careful attention the rest of the project received.
The readability drift
Text sizes set during desktop testing often need adjustment once the game is actually on a phone in someone's hands.
The device range gap
A game that runs smoothly on a current device can struggle on hardware from two or three years ago. The install base out there is wide.
The store checklist gap
App store submissions have specific requirements. Missing one or getting a category wrong can delay release by days while it's reviewed again.
What we do
A thorough look that respects the work already done
We're not here to question decisions that were made thoughtfully. We're looking for things that are genuinely worth addressing before players see them — and delivering those findings clearly so you can act on them.
1 You share the current build
We work from what you have — a build file, a video walkthrough, or ideally a device-testable version. Tell us what you're most uncertain about and we'll give that extra attention.
2 We review across three areas
Performance, text readability, and store readiness. Each area gets its own section in the output so findings are easy to act on without hunting through a single long document.
3 Findings are practical, not theoretical
We note what we observed, where, and what a reasonable fix would look like. No lengthy explanations of what could hypothetically go wrong — just what we actually saw.
4 You receive notes and a checklist
Delivered as a written document you can work through at your own pace. The store checklist is separate so you can use it directly when you're ready to submit.
What it feels like
A quiet, focused pass — nothing disruptive
You share the build and we get to work. There's no lengthy intake process, no back-and-forth that holds things up. We look carefully, note what we find, and return a document you can use.
Doesn't slow your schedule
The review is done independently. You don't need to set aside time during it — just share the build and we handle the rest.
Notes you can act on quickly
Findings are written to be useful, not exhaustive. You can work through them in a focused sitting and know what to prioritise.
A checklist that's yours to keep
The store-prep checklist is a reusable document — useful for this release and any future ones that follow a similar path.
The investment
$360 USD — a flat fee for the complete pass
The Mobile Polish Pass is $360 USD, covering everything described here as a single engagement. No scope creep, no retainer, no add-ons that weren't discussed.
For a project that's been months in the making, this is a modest final step to take before it reaches players. The cost of an avoidable delay or a batch of early negative reviews tends to be higher than the review itself.
If you've worked with us on earlier stages of the port, we'll carry that context into this pass. If you're coming to us fresh at this stage, that's equally fine — we work from what's in front of us.
What's included
- Performance review with device range observations
- On-screen text readability assessment with sizing guidance
- Store-prep checklist for iOS App Store and Google Play
- Written notes document organized by area
- One follow-up round if findings need clarification
$360 USD / one-time
How we approach it
Systematic, not superficial
We've seen enough ports reach this stage to know where things tend to need attention. The review follows a consistent structure, but what we actually look for is always shaped by the specific game in front of us.
Performance review covers
- Frame rate consistency in active gameplay
- Load times between sessions and scenes
- Memory handling over extended play sessions
- Battery draw observations where measurable
Store prep covers
- App metadata requirements (title, description, category)
- Screenshot and preview asset specifications
- Age rating questionnaire notes
- Common rejection causes to check against
Realistic timeline
The pass typically takes 4–6 working days from when we receive the build. If your release date is close, mention it when you reach out — we'll let you know whether the timing works before anything is agreed.
Our commitment
Honest findings, no padding
We can't guarantee your submission will be approved first time or that players will be satisfied with every aspect of the port. What we can commit to is that the review will be thorough and the notes will be genuine — not inflated to justify the fee, not softened to avoid discomfort.
If something in the notes isn't clear, or if you feel an area wasn't covered adequately, let us know. One follow-up round is included, and we take that seriously.
You're also welcome to reach out beforehand to describe your situation and hear whether this is a good fit. No obligation, no sales pressure — just a straight answer.
Genuine observations only
We note what we actually found. If something looks good, we'll say so.
Follow-up included
One clarification round after delivery. Use it if anything in the notes needs more context.
Pre-engagement chat available
Describe your situation first if you'd like. We'll tell you whether this service makes sense for where you are.
Getting started
How the pass works in practice
Reach out with your build
Use the contact form. Share what you have — a build file or a video walkthrough — and let us know your rough release timeline.
We confirm and begin
We'll confirm we can meet your timeline, ask any brief clarifying questions, and start the review. You can get on with other things in the meantime.
Notes delivered, you act
Within 4–6 working days, your notes and checklist arrive. Work through them at your pace before you submit.
Timing tight? Write to us first at info@summertidesandsunsets.com and we'll confirm whether we can work within your window.
Nearly ready to release? Let's take a careful look first.
Get in touch through the contact form. Tell us where you are in the process and share the build when you're ready. We'll do the rest.
Request a polish pass — $360Other services
Earlier in the process?
If your port is still being shaped, these two services cover the stages that come before this one.
Service 1
Port Feasibility Review
An honest assessment of how your arcade title might move to mobile — controls, screen fit, pacing — before you commit to development. A clear report to plan from.
Service 2
Touch Adaptation Build
The hands-on development work of remapping controls to touch and adjusting layout for mobile screens — delivered as a playable build that keeps the original feel.