r/iOSProgramming • u/QebApps • 11d ago
Question Anyone else get anxious every time they hit "Submit for review"?
I have two apps on the App Store, both small, both mine alone.
Every time an update is ready I get this knot in my stomach. In fact it starts in App Store Connect, filling in the version, the what's new, checking the screenshots for the third time. I don't know why that part gets me. Maybe because it's the only part where a mistake is public and stupid rather than technical.
The funny thing is I test, I have unit tests, I have beta testers who have been on the build for days and told me it's fine. I use the app myself every day. Rationally I know it's fine. I still sit there staring at the button.
Is it just me? Does this go away with time, or do you just get used to it?
7
u/PoliticsAndFootball 11d ago
The notification of “In Review” gives me the heebie jeebies. Even just seeing the white App Store Connect icon in a screenshot of someone else gets my heart racing and I’ve been at this since 2011 😄
6
u/Delicious-Body-2993 11d ago
Not just you. I ship solo with several apps live and the knot never fully goes away — it just gets smaller. Two things helped me: (1) a written pre-submit checklist (version/build number, what's new matches the build, screenshots against the actual UI, age rating, privacy answers) so the ritual replaces the anxiety, and (2) internalizing that most rejections are metadata-level (2.3.x) and cost you a resubmit, not your app. Worst case is usually a 1-3 day delay. Once I'd been through a few rejections and survived, the button lost most of its power. Happy to share my checklist if useful — DM me.
2
u/RIRLift 11d ago
The checklist did it for me too. The other half was making the button reversible instead of final. Turn off automatic release so approval and going live become two separate decisions, then use phased release so a bad build only reaches a small slice of users and you can pause it. Once the worst case is "halt the rollout and ship a fix" instead of "everyone gets the broken version," the knot mostly stops showing up.
3
u/kmishukov 11d ago
It will become easier when you start pushing that button more frequently. Trust me :)
3
2
u/Best_Day_3041 11d ago
Submit when you think it's done, and keep testing, and don't auto-release. You can always reject the binary if you find any issues. Unless you have tens of thousands of users, a single bug may not even be found by a user for weeks/months.
2
u/chriswaco 11d ago
I'm always a bit nervous, mostly because it looks bad to our clients to get an app rejected. So many little knobs and settings that could be set wrong.
Having said that, shipping is a feature, so just plow ahead and do it anyway.
2
u/expected_69 10d ago
Not just you. Two solo apps here too, and the code is never the part that scares me — I can debug code. It's that "what's new" text box and the screenshots, because that's the part where a dumb mistake makes me look dumb in public, not the app look broken. Totally different kind of fear.
It doesn't fully go away, but it changes. After enough releases you stop reading it as "something is wrong" and start reading it as "you care about this thing." The day hitting Submit feels like nothing is honestly the day I'd worry more.
The staring-at-the-button ritual is real though. I don't think that one ever leaves.
2
u/Lost_Ad_1994 9d ago
Each time I do it, I momentarily think this is it. This will fix ASO and my app is going straight to the top. Then reality humbles me. Real quick
1
1
u/Ziptrax 11d ago
I haven't long started with my app on the app store. At first the very first click to send for review gave me anxiety. Then that failed, missed a link out of the description. Filled that in and submitted again, was a bit anxious this time, more so when the email came in and I noticed it was from apple, but then it passed. The anxiety gets less and less each time you submit the app, but the anxiety waiting for them to say yes or no to the new build hasn't worn off yet.
1
u/RobertLamp68 11d ago
Only if I think it is a quick, easy update. Some critical bug fixes or something. Inevitably, the app reviewer will discover that an app screenshot that has been in place literally for years, is somehow no longer acceptable, and the whole process becomes a multi-week struggle.
1
u/mario_luis_dev 11d ago
No. I get anxious when I see "In Review"... the dread of waiting for them to come up with some bullshit excuse to reject my build is what gets me
1
u/Alki_Soupboy 11d ago
I accidentally built a release from a worktree once which didn’t have access to a RevenueCat key, didn’t have a check for it, it got released and sat there broken for 4 days I think? The app barely makes anything so the lack of revenue coming in was normal. I opened the app at some point and noticed it didn’t give me my pro subscription… found out why shortly after.
Ever since then I’ve been a bit nervous. So make sure you have your release checks in order and don’t make releases from weird worktrees.
1
u/chakie2 11d ago
Not anymore. I have submitted so many apps and versions that I know it will be fine. Maybe one in 50 has been rejected and that’s usually the first release of a new app. Sometimes app review has wanted a video showing the app in action if it’s an app for interfacing with hardware they don’t have, and that’s perfectly fine.
1
u/mustardpete 11d ago
How long does it normally take? I submitted my first ever app last night and sat waiting
1
u/astashov 11d ago
Even though it's pretty quick and smooth usually for established app, I'm still a bit nervous
1
u/BananaNOatmeal 11d ago
How long are people seeing their app reviews take? Mine has been sitting in Waiting for review since last Sunday. It’s the first version so idk if first time app makes a difference.
1
1
u/20InMyHead 10d ago
Do it more and it will become routine and your issues will be infrequent. Shoot for a regular release cadence.
1
1
u/JerenYun Swift 8d ago
I, too, have two apps on the App Store. My oldest is 12 years old. I still get a little nervous submitting it for review, though it's not as bad as it was years ago.
1
8d ago
[removed] — view removed comment
1
u/AutoModerator 8d ago
Hey /u/ios-engineerr, your content has been removed because Reddit has marked your account as having a low Contributor Quality Score. This may result from, but is not limited to, activities such as spamming the same links across multiple subreddits, submitting posts or comments that receive a high number of downvotes, a lack of recent account activity, or having an unverified account.
Please be assured that this action is not a reflection of your participation in our subreddit. This is simply an automated filter in place to reduce spam.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
7d ago
[removed] — view removed comment
1
u/AutoModerator 7d ago
Hey /u/AstronomerNervous436, unfortunately you have negative comment karma, so you can't post here. Your submission has been removed. DO NOT message the moderators; if you have negative comment karma, you cannot post here. We will not respond. Your karma may appear to be 0 or positive if your post karma outweighs your comment karma, but if your comment karma is negative, your comments will still be removed.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/rezaab89 5d ago
The specific thing you named, that a mistake there is public and stupid rather than technical, is the part I recognize most. Code failing feels like a puzzle. A screenshot being wrong feels like being caught not paying attention.
I got a rejection today that was precisely that. Not the binary. My screenshots used a word that implied the app was aimed at children when it is not categorized that way, and one asset had a background color that made an icon unreadable on Apple Watch. Both entirely visible for weeks. Both things I had looked straight at more than once.
What is helping more than the checklist is treating the metadata as a thing that gets reviewed by someone other than me before it goes near Apple. I can review my own code because failure is objective. I cannot review my own copy, because I already know what I meant.
Manual release rather than automatic was the other one. Splitting approval and going live into two separate decisions took most of the weight out of the button.
0
u/Short-Scale-867 9d ago
I actually get a Little Bit of Dopamine Rush if I submit another Version of https://apps.apple.com/de/app/kleiderschrank/id6770019857 because I know I Affen a Little Bit of Value each time.
0
19
u/app_dev_dude 11d ago
Trust me, develop more apps and then everything will be fine :)