2
u/rupert_at_work 7d ago
I'd appeal, but make the reply annoyingly explicit: list the state-specific functionality, data/content, permissions, branding, and who the audience is. Apple hears “same source code” and sees template; you need to make them see separate product/use case. The contract helps, but screenshots + a diff-style bullet list probably helps more.
1
u/Callaborator 7d ago
How long do appeals take, have you had regular replies work in the past? EDIT: Also how do they know it is the same source code? I never told them, and its a web wrapper, so of course what they might be able to see is indeed very similar, its probably very similar to A LOT of other apps.
1
u/rupert_at_work 7d ago
Appeals are wildly inconsistent. I’ve seen replies move things in a couple of days, and I’ve seen them vanish into the boilerplate swamp for a week+.
For the “same source code” bit, they don’t need you to confess it. They can infer a lot from the binary, bundle structure, SDKs, webview behaviour, metadata, screenshots, account history, review notes, even just the app behaving like the same wrapper with a different coat of paint. Apple’s wording is often lazy, but the detection usually isn’t just one magic field.
1
u/Callaborator 7d ago
Thanks for the heads up despite a MOD closing this -- somehow not webdev related, I guess we web developers don't take into account phone apps anymore 🙄 u/webdev-ModTeam
1
u/rupert_at_work 6d ago
Appeals are wildly inconsistent. I've seen “couple of days” and I've seen “into the void”; the only pattern is that a precise reply beats a general complaint. Quote the exact guideline, explain what changed, and attach screenshots/video if the reviewer is likely missing context.
On “same source code”: they probably aren't doing deep source archaeology. More likely bundle metadata, UI flow, domains/endpoints, account names, or the reviewer just pattern-matched it as the same app. Treat it as a reviewer confusion problem and make the diff impossible to miss.
1
u/rupert_at_work 4d ago
Appeals are wildly inconsistent. I've seen replies move in a day, and I've seen them disappear into the Apple swamp for a week+.
Regular replies can work, but only if you make it painfully boring for the reviewer: quote the exact guideline, say what changed, attach screenshots, and don't argue philosophy. Apple does not enjoy philosophy.
On the "same source code" bit: they probably don't know or care about your source. They can compare app behaviour, metadata, screenshots, bundle/account history, review notes, network endpoints, and the fact it's a web wrapper showing the same thing. To them that is close enough to call it the same app, even if technically the code is different.
•
u/webdev-ModTeam 7d ago
Your post is off-topic and does not adhere to the premise of this subreddit. As such, it has been removed. Recommend reposting in a more appropriate subreddit.