What this rejection means
Guideline 4.2 is about how much an app offers, not about bugs. It is a judgement call, and the message rarely says what would be enough.
What is at stake
A 4.2 rejection questions the app itself, not a detail. Without a clear answer, resubmissions keep failing and the project can stall for weeks.
When to talk to us
- The message doesn't make clear what to change
- You resubmitted and got the same answer
- A launch, an update or a campaign is waiting on this
- You're not sure whether to reply, resubmit or appeal
Why it takes more than a quick fix
There is no checklist for "enough". What to change, and how to present it to the reviewer, is a product decision as much as a technical one.
How we help
- You send us the caseThe reviewer's message, the app and what changed since the last approved version.
- We find the real causeWe look at your case the way the store does, and find what is really behind it.
- You get a clear planWhat has to change, written for your team, or we work on it with them.
- We help you answerYour reply to the reviewer or your appeal, and follow-up until the review is closed.
Questions
Can an app built with web technology be approved?
Yes, many are. What matters is what your app offers and how it is presented. Whether yours is there yet depends on the app.
Can you guarantee approval?
No one outside Apple and Google can promise how a review will go. What we can do is find the real cause, remove what we can see would block approval and give the reviewer everything they need.
Do you need access to our accounts?
It helps, but it is your choice. We can work from screenshots, exports and a build, or with a limited role you add and remove yourself.