How to check someone actually knows Apple and Google's rules

Getting your app into the Apple App Store or Google Play Store looks straightforward until it isn't. A skilled submission support person knows the stores' actual rules—not rumour, not shortcuts—and can steer you away from costly mistakes. But "knows the rules" is a claim too easy to make and too hard to verify over email. Here's how to tell if someone has genuine, current expertise before you hand them your app.

Spot Real Knowledge in Their Answer to a Specific Question

Don't ask "Do you know Apple's guidelines?" Ask something narrow and current: "What's Apple's current rule on location data permissions for a fitness app that tracks outdoor routes?" or "Google Play recently changed its rules on financial apps and device admin permissions. What changed and why does it matter for us?"

Someone who works with this regularly will give you a concrete answer tied to actual store policy, and often mention why the rule exists—privacy, user safety, fraud prevention. They might say, "Apple requires explicit permission UI before accessing location, and you can't use it for ad targeting in fitness apps. Google Play's updated financial services policy now requires specific compliance certifications if you're handling payments." That specificity matters. If they hedge, generalize, or say "I'll check and get back to you," it's a yellow flag.

Ask a second question about a different store. Someone billing themselves as expert in both platforms should handle both. If they're only confident on one, they're honest—but you need to know whether they can actually support your app on your chosen store.

Request Proof That They've Done This Recently

App store rules change quarterly, sometimes faster. A person whose last app submission was three years ago might be working from outdated knowledge without realizing it. Ask them:

• "What's the most recent app you've helped submit, and when?"
• "Which store did it go to, and did it pass review on the first submission?"
• "Can you share a screenshot or reference details from that submission so I can understand the scope?"

They won't share the client's app name or sensitive data—and you shouldn't ask them to—but they should be able to say something like "I helped a SaaS onboarding app to Google Play in September; it cleared review in two weeks, no rejections." If they push back on giving you *any* recent example, that's a sign they don't have one.

For references, ask specifically: "Can I speak to someone who used your help for an Apple Store submission in the last six months?" Time matters. A success from 18 months ago might reflect rules that have since shifted.

Ask What Happens if They Get It Wrong

This separates people who take their expertise seriously from those who don't. If your app gets rejected because of bad advice, will they help you resubmit at no extra cost? Will they cover the delay, or is that your problem?

Their answer won't be a legal guarantee—app stores make final decisions—but it tells you whether they stand behind their knowledge. Someone confident in their expertise will have a clear stance: "If the rejection is due to advice I gave and I missed something in the current guidelines, I resubmit free." Someone vague about responsibility is signalling they're less certain.

Check How They Stay Current

Ask: "How do you keep up with Apple and Google's guideline changes?" Real answers include: they subscribe to Apple Developer news and Google Play newsletters, they attend WWDC or Google I/O notes, they review rejection reports from their other clients to spot trends, they're part of developer Slack groups where changes are discussed. Generic answers—"I read online," "I stay informed"—don't tell you much.

You're not hiring a researcher; you're hiring someone whose job depends on knowing what changed and why. Their process for staying current should feel like an actual job, not a hobby.

Bring a Sample Question to Your First Call

Before you commit, write down a technical question about your app's core functionality and how it might interact with store rules. Their live answer—how they think through the problem, what they ask you in return, what trade-offs they mention—is worth more than any email exchange. A sharp hire will ask clarifying questions, tie your specific feature to the relevant policy, and suggest preventive steps.

When you're ready to find someone with this kind of concrete, current expertise, Strove lets you vet submissions specialists in your area, see their past work, and confirm their knowledge before you brief them on your app.