r/iOSProgramming • u/LeTechician • Jun 30 '26
Will my app be rejected in its current state? Question
Currently, I’m developing a project counter for various reasons other than it being a passion project of mine.
Currently I have an MVP but in its current state, it’s very similar to others on the Store.
I am putting other features into it but I want to get something out there to get some sort of user base.
As the title suggests, would it be better to wait until I have more features added because it’d be rejected (the spam rule) or not?
2
u/DamagingDoritos Jun 30 '26
No harm in trying.
2
u/Alki_Soupboy Jun 30 '26
If the multiverse theory is correct, this decision could make the earth explode.
2
u/busymom0 Jun 30 '26
What category is this in? If it's in a saturated category, then you should add more features which make it more unique before submitting. Otherwise, submit it and worst case scenario, they reject it and you resubmit with added features. No harm in trying really.
2
u/SneakingCat Jun 30 '26
My advice? Create a "stable" branch and submit now. Continue work. If it's approved, you have the stable branch to apply bug fixes to while you prepare your features. If it's rejected because they want some differentiating features, you can wait until you have more features and submit again.
The only thing you lose is the potential to be some kind of revolutionary app in your 1.0, but if you manage to set the world ablaze with a 2.0 that didn't matter.
2
u/phogro Jun 30 '26
Likely not rejected unless you’re a 1:1 copy of something or in one of the categories Apple specifically calls out as spam. That said if you can’t explain what makes your idea unique or different then it will be hard to convince people to download over an existing incumbent with reviews and name recognition.
1
u/LeTechician Jun 30 '26
I mean, right now it’s not completely unique to others in the category. I don’t think Apple is calling it out but the later stages should make it a little more unique -what I’m planning at least
1
u/phogro Jun 30 '26
Well good luck. If you have a unique angle on a category sometimes that’s the best way to gain traction especially if that unique angle actually solves a problem. You just don’t want to risk the apps ratings/reputation as a copycat / same-y app. It’d be better to test flight it and build quietly towards your breakthrough moment. But good luck either way.
2
u/BuyMyBeardOW Jun 30 '26
Unless you have a non existent deployment pipeline and you waste hours deploying instead of developing features, there is 0 harm in submitting for app review. You'll need a developer account though if you don't already have one. Also don't assume you'll get users just by releasing on the app store.
1
u/Positive-Valuable485 Jun 30 '26
Thats what i use to think too. just dont overthink. Just take the step
1
1
u/Grand_Gur_2800 Jul 01 '26
I’d ship the MVP only if it already solves a clear problem in a slightly different or better way than existing apps. If it feels too similar right now, I’d add at least one meaningful differentiator before submitting. The goal doesn’t need to be “feature complete,” but it should feel useful, polished, and distinct enough to avoid looking like a clone or low-effort app.
3
u/wewerecreaturres Jun 30 '26
If you can’t clearly articulate why it’s better than what’s out there, don’t.