Play Console & Publishing
Release tracks, rollouts, store listings, and the workflows that get an app live without surprises.
Android Developer & Google Play Console Specialist
Helping developers navigate Play Console since 2016 — publishing, policy, suspensions, and the problems with no documented answer.
Real questions from real developers — suspensions, closures, verification — answered publicly under the name MrHamo on Google's own support forum. Don't take my word for it; read the answers yourself.
About
I'm an Android developer who has been working inside the Google Play Console since 2016 — long enough to have watched its policies, its review systems, and its edge cases evolve first-hand.
That time has turned into deep, practical knowledge of how publishing actually works: what triggers a rejection, how the policy language maps to real enforcement, and what a review team is looking for when an app or an account gets flagged.
I use it to help other developers. When something goes wrong with publishing, policy, or an account, the documentation rarely tells you what to do next — I help fill that gap with answers grounded in what works in practice.
Expertise
Release tracks, rollouts, store listings, and the workflows that get an app live without surprises.
Reading Play policy the way it's actually enforced, and shaping an app so it stays on the right side of it.
Working out why an app was removed, and putting together an appeal that addresses the real reason.
Getting through developer identity checks, D-U-N-S requirements, and the verification errors that stall accounts.
A second pair of eyes for the problems that don't have a documented answer — and no obvious next step.
Services
Practical help with the parts of Google Play that cost developers the most time — grounded in what actually works, not what the docs say.
Getting a build live cleanly — tracks, rollouts, store listing, and the review pitfalls that hold releases up.
A read of your app against current Play policy before Google does it for you — and a plan for anything that looks risky.
Working out the real reason behind a removal or termination, then building an appeal that actually answers it.
Clearing the checks that stall developer accounts — identity, address, payments profile, and D-U-N-S.
A direct conversation about your specific situation, with a straight answer about what your options actually are.
A person to ask when something on Play doesn't behave the way the documentation says it should.
Process
No forms to fill in, no ticket queue. You email me, and a person who has seen the problem before reads it.
Send the details — your package name, the exact message from Google, and what you've already tried. The specifics matter more than the summary.
Policy notices are short and rarely say what actually triggered them. I work out which part of your app or account is the real problem.
What your options are, which one I'd take, and an honest read on your chances — including when the answer is that there isn't a route back.
Whether that's an appeal, a fix and resubmit, or a change to how the account is set up — you get help through the part that matters.
How I Can Help
Most Play Console trouble looks the same from the outside: a short message, a policy link, and no clear next step. These are the situations where experience saves weeks.
A release that keeps bouncing back, with a reason that doesn't explain what to actually change.
An app pulled from the store, and a policy citation that could mean several different things.
Identity, address, or D-U-N-S checks that fail or loop without a clear reason why.
One appeal, one shot — worth getting the reasoning and the evidence right before sending it.
FAQ
Often, yes — but it depends entirely on what triggered it. A policy violation that can be fixed and appealed is very different from a repeat violation or an account-level termination. The first job is working out which one you're actually dealing with, because that determines whether an appeal is worth filing at all.
Contact
Tell me what you're dealing with. Include your package name and the exact message you received — it makes the first reply far more useful.
Helping fellow developers is the point — there's no invoice at the end. Reach me whichever way is easier for you.