AI can write my entire app but it can't get Microsoft to approve it

The silence already lied to you once, so it can't be read as pending.

That's the part Gal's visibility point and Asad's two clocks both route around. Setting it down works when no news means no news. Yours failed silently on attempt one, which means no news and dead look identical from where you sit, and that's why you keep opening the dashboard.

The thing you control isn't the waiting, it's the sampling. A fixed cadence you decide in advance, once a day at a set time, turns silence into a checked state instead of an open question. Same information, but the ambiguity stops living in your head all day.

Did the first rejection show up in the dashboard eventually, or did you only catch it because you happened to look?

Certification queues are one of the few remaining places where the bottleneck is a person's attention, not throughput, so no amount of model capability touches it. Longest for me was a payment provider's compliance review, and the only thing that ever moved it was finding an actual human to email directly...

Then the only thing left is the order you do them in.

If attempt two goes in before the ticket comes back, you lose the answer either way. It passes and you never learn whether the name was actually the cause, or it fails and you are guessing again with one fewer attempt spent. The ticket is the only step in this whole process that produces a reason, so let it produce one, then resubmit against a confirmed cause instead of a strong hunch.

Worth watching that they do not close the ticket as superseded if a new validation is already in flight when someone picks it up.

The App Store version got me too, but going through it changed how I read the rejection. Mine came back on a launch hang — stalled on a cold start on a device class I'd never tested, flagged under 2.1. First instinct was Gal's: opaque human gate, coin flip, nothing I can do. But the reviewer hadn't read a policy doc differently, they'd literally run my app on older hardware with a cold cache and hit a freeze I never saw, because I only ever launched it warm on my own phone. Once I clocked that, a chunk of "the human gate" stopped being a queue I'm helpless in front of and became a free QA pass on the exact matrix I was too lazy to test: oldest device, cold start, no network, first-ever launch. The truly uncontrollable ones are the policy calls — yours, Gal's payments case — where the clock-reset is the whole tax. But for the crash/hang class, the lever I pull now is "run it the way the least forgiving reviewer will," and the round-trips mostly stopped. Yours is upstream of even that, though: identity validation with no reason and no email is a worse black box than review, since review at least coughs up the guideline eventually.

This is such a perfect example of the new reality we're living in — AI has democratized BUILDING, but not DISTRIBUTION or TRUST.

The irony is almost poetic: you can generate an entire functional app in hours (something that would've taken months before), but you're stuck at a gatekeeper that doesn't care about your code quality — they care about reputation and trust signals that AI can't fake for you.

A few thoughts from someone who just launched their first product today:

🔑 The bottleneck shifted — Used to be: can I build this? Now it's: can I get permission to distribute this? The hard problems are no longer technical; they're bureaucratic and trust-based.

🤝 Human-in-the-loop is now about compliance, not coding — You still need humans, but for different things: account verification, app store reviews, domain reputation building, community trust.

💡 Possible workarounds to consider:

- Start with web-only distribution (no MS approval needed) while building trust signals

- Use a publisher or established partner who already has store access

- Build an audience first (social media, PH launch, etc.) so Microsoft sees you as legitimate

- Consider alternative stores or sideloading options

🚨 The bigger question: As more people use AI to build apps, will platform gatekeepers become even stricter? This feels like the beginning of a new kind of "app inequality" — where having a verified developer account becomes as valuable as the code itself.

Thanks for sharing this openly. It's a warning sign all indie builders need to see. The AI revolution isn't "build anything you want" — it's "build anything, good luck getting anyone to trust it."

app store review is the one that gets me every time. spent two weeks once waiting on Apple to re-review a payments-related update, got rejected for a guideline that wasn't even the reason they cited, resubmitted, waited again. no model helps with that because the bottleneck isn't code quality, it's a human on the other side reading a policy doc differently than you did. the annoying part is you can't even parallelize it, one submission at a time and the clock resets on every rejection.

The Microsoft queue is a particular kind of stuck, because the skill that got you this far stops working. Everything else in a build responds to effort. You push, it moves. A certification queue does not care how good you are, and that is the part that itches. Not the three weeks, but that your competence suddenly buys you nothing.

The longest I have been stuck was never on a hard problem, it was always a dependency on someone who had no reason to hurry. What helped was separating the two clocks. There is work time, where effort maps to progress, and there is queue time, where the only honest move is to set it down and go build the next thing, so the wait runs in the background of a good day instead of the foreground of a stalled one. Three new models shipping while you sit there stings, but none of them are stuck where you are either, and that gap is usually a moat rather than a threat. The approval lands on its own schedule. The only thing you control is whether it gets to sour the weeks around it.