{"id":47171901,"title":"Show HN: Made First Android game using Codespaces and AI, now in AdMob purgatory","points":1,"user":"apocryphal","time":1772139363,"time_ago":"7 hours ago","type":"link","content":"

Two months ago, I had zero mobile development or publishing experience. I wanted to see if I could build and ship a complete game using only a browser-based workflow and AI assistance.

The process:

Built entirely in GitHub Codespaces using an AI Copilot.

Wrote the core game for the web, then wrapped it into an Android APK/AAB.

Pushed through 100+ versions to fix edge cases.

Passed Google Play review with no policy violations.

The game is a tough 2D platformer called Bionic Biome. To make the "impossible mode" bearable, I integrated a rewarded AdMob ad as a Continue/Revive mechanic. It’s an opt-in lifeline, not a forced pop-up.

Here is the weird hurdle I’ve hit:\nTest ads worked perfectly. But in production, the AdMob dashboard just says "No data" and returns "Ad not ready." My core revive mechanic is effectively disabled because Google's algorithm won't serve real ads until it sees enough "organic" traffic to trust the account.

It's a strange psychological shift. For weeks it was "build, fix, upload." Now, the AI code works, the wrapper works, the integration works, but the core mechanic is held hostage by a silent third-party algorithm waiting for strangers to play it.

Has anyone else here launched a first app and hit this AdMob cold-start wall? How long did it take for your first live ad to actually fill?

If you are curious to see what an AI-coded, web-wrapped game built entirely in a browser actually plays like on Android, the link is below. (No pressure to play, just sharing the technical journey).

https://play.google.com/store/apps/details?id=com.pollitopro...","url":"item?id=47171901","comments":[],"comments_count":0}