TL;DR
Store reviewers and users judge apps on the basics: no crashes, handled empty and error states, a real icon, and speed. Getting these right is what separates a submitted app from an approved one.
A working app and a quality app are not the same thing, and reviewers know the difference. The gap between them is a handful of basics: the app does not crash, it handles the empty and error moments gracefully, it looks finished, and it feels fast. Get these right and you clear review and keep the users you win.
The quality checklist
- 1It never crashes on the main flows you will be tested on
- 2Empty states explain what to do instead of showing a blank screen
- 3Errors are handled with a clear message, not a freeze
- 4It has a real app icon and a finished, consistent look
- 5It feels fast, with no long unexplained waits
Handle the empty and error moments
New builders polish the happy path and forget the edges. A reviewer will open your app with no data and hit a blank screen, or lose connection and hit a freeze. Handle those moments with a friendly message and a next step. It is the fastest way to look professional and pass review.
Looks finished matters
A missing icon, mismatched fonts, or a half-styled screen signals an unfinished app, and reviewers reject those. You do not need a design degree. You need a real icon, consistent spacing, and screens that look like they belong together. Ask Claude Code to tidy the look before you submit.
Test the whole thing on a real phone
Run every screen on your actual device, including the empty states, the errors, and the slow-network case. Reviewers test on real hardware, so you should too. Finding a crash or a broken state yourself is far cheaper than a rejection days later.
Common questions
What quality basics do reviewers check?
That the app does not crash, handles empty and error states gracefully, has a real icon and finished look, and feels fast. Reviewers test the main flows on real hardware. Nailing these basics is what separates an approved app from a rejected one.
Why do empty states matter so much?
Because a reviewer or new user opens your app with no data first. A blank screen looks broken; a friendly message with a next step looks finished. Handling the empty moment well is one of the fastest ways to look professional and pass review.
How polished does the design need to be?
Finished, not fancy. You need a real icon, consistent spacing, and screens that look like they belong together. You do not need a design degree. Ask Claude Code to tidy the visuals before you submit, and avoid obvious half-styled screens.
Do I really need to test on a real phone?
Yes. Reviewers test on real devices, so code that looks right can still crash or freeze in practice. Run every screen, including empty and error states and slow-network cases, on your own phone. Finding issues yourself is far cheaper than a rejection.
What causes most quality rejections?
Crashes, broken or blank states, unfinished visuals, and features that do not work as described. These are all things you can catch by testing thoroughly on a real device before submitting. Most quality rejections are avoidable with a careful final pass.
How long should quality polish take?
Budget a full day near the end for it. Fixing crashes, handling edge cases, adding the icon, and tightening the look is not glamorous, but it is what gets you approved. Rushing this step is a common reason first submissions bounce.
Keep going
Want a pre-submission quality checklist reviewers rarely reject?
Get the other 37 in the app user stack, plus the full App Store Launch Club community - $9/mo, cancel anytime.
Join the Club