TL;DR
Before you submit, run a polish pass: add the icon and screenshots, handle every edge case, check performance, and test the whole app on a real phone. It is the difference between approved and rejected.
The last day before you submit is not for new features. It is for polish. A final pass over the icon, screenshots, edge cases, and performance is what turns a working app into an approved one. Treat this like prepping an item before you put it up for sale: the finish is what people, and reviewers, judge first.
The pre-submission polish pass
- 1Add a real app icon that reads clearly at small sizes
- 2Create honest screenshots that show the actual app, not mockups
- 3Handle every empty state, error, and offline case
- 4Check the app feels fast, with no long unexplained loading
- 5Do one full run through every screen on a real phone
Icon and screenshots come first
Your icon and screenshots are what people see before they download and what reviewers see before they open the app. A clear icon and honest screenshots that show the real app set the right expectation. Misleading screenshots are a fast rejection, so show exactly what users will get.
Sweep the edges
Walk through the app as a brand-new user with no data, then as someone with a bad connection, then as someone who taps the wrong thing. Each of those is an edge a reviewer will hit. Handle them with clear messages and next steps rather than blank screens or freezes.
One last real-device run
Before you hit submit, do a complete run through every screen on your actual phone. This final walkthrough catches the crash or broken state that slips past everything else. It is the cheapest insurance against a rejection that would cost you days.
Common questions
What is a pre-submission polish pass?
A final round of finishing work before you submit: adding the icon and screenshots, handling every edge case, checking performance, and doing a full real-device run. It is not for new features; it is for turning a working app into an approved one.
Why do screenshots matter for approval?
They set expectations and are the first thing reviewers and users see. Honest screenshots that show the real app build trust and pass review. Misleading ones that show features you do not have are a fast rejection, so show exactly what users get.
What edge cases should I handle?
Empty states with no data, errors, offline or bad-connection cases, and wrong taps. Reviewers hit all of these. Handle each with a clear message and a next step instead of a blank screen or a freeze. Edge cases are where quality is judged.
Should I add features during polish?
No. Polish is for finishing, not building. Adding features at the last minute introduces new bugs right before submission. Lock the feature set, then spend your final day making what you have solid, clear, and reviewer-ready.
How important is the final device test?
Very. A complete run through every screen on your real phone catches the crash or broken state that everything else misses. Reviewers test on real hardware, so this last walkthrough is your cheapest protection against a costly rejection.
How long should the polish pass take?
Plan roughly a day. Icon, screenshots, edge cases, performance, and a full device run add up. It feels slow, but skipping it to submit early usually costs more time in rejections than the polish would have taken.
Keep going
Want your app polished against a reviewer-tested checklist before you submit?
Get the other 37 in the app user stack, plus the full App Store Launch Club community - $9/mo, cancel anytime.
Join the Club