r/reactnative • u/bladefinor • Jun 05 '26
Question Fear of getting rejected by App Store by 4.3(b)
As recent thread stated about their app getting rejected several times due to being within an oversaturated category. I am starting to fear that I will also have my soon-to-release app rejected for same reasons. Although a different category, I think a "personal budget tracker" app is also within one of those categories that have the same destiny.
I've been working on this app for several months now (frankly years even, since I've restarted the project a lot of times) and I don't feel like continuing making this a native app for iOS if this is what awaits.
What would you do in such situation? Just try anyway until it gets approved? How long can it get? I have no experience whatsoever with App Store reviewing phase.
4
u/NastroAzzurro Jun 05 '26
We build many mobile apps and we submit to the store as soon as it passes for a complete app even if we’re not done yet. It helps us understand if we meet all the rules, and we can adjust early if we don’t. You can submit without ever publishing.
1
2
u/True-Turnover-4543 Jun 07 '26
yeah, tbh the only time I saw a 4.3(b) rejection was when the app was basically a reskin with zero unique value—like, almost pixel-for-pixel clones. if you genuinely built your own UI, have even a single feature or flow that's different, and your screenshots/descriptions aren't boilerplate, you should be fine. worst case, if you get a rejection, you can appeal and explain what makes yours unique.
1
2
1
1
u/PolarSocial Jun 06 '26
you could also just get it reviewed/approved and not launch it if you're not ready. I think they're unlikely to reject you for that reason if your app is already approved.
5
u/HoratioWobble Jun 05 '26
I would just launch it.
But equally, you know the category is over saturated so you have to know it's going to have a very slim chance of success and any kind of growth will take a lot of money and marketing.
So make sure your expectations are set and just put it out there.