All Build Log posts
Build Log

What went wrong with app icons

I spent four hours on app icons before I realized I was solving the wrong problem entirely. Here is the full story.


What happened

  • The Play Store rejected my first submission because of the app icon — not the design, the format.
  • I had generated a great-looking icon with an AI image tool, exported it as PNG, and submitted.
  • The resolution was wrong. The safe zone was wrong. The format was wrong in three different ways.
  • I did not know any of those requirements existed.

Four hours of the wrong approach

  • I spent four hours going back and forth between AI tools, the Play Store docs, and Android Studio.
  • I asked Claude to help. I asked Codex to help.
  • Neither gave me the correct answer — the Play Store requirements had been updated in 2025 and neither knew.
  • Going back and forth between three tools trying to fix the same problem is a warning sign.

The twelve-minute fix

  • Android Studio has a built-in tool called Image Asset Studio.
  • You give it one high-resolution image and it generates every icon size and format automatically.
  • The right tool for the job was already installed — I had ignored it completely.
  • Twelve minutes from opening Image Asset Studio to a passing submission.
  • Four hours vs twelve minutes. I try to remember that gap every time I reach for AI first.

The real lesson: AI does not replace platform tools

  • AI can help with a lot. It cannot replace tools designed specifically for a platform's own requirements.
  • Android Studio's built-in features, Xcode's asset catalogs, the Play Store dashboard — these exist for a reason.
  • I now keep a list of "use the right tool first" reminders for areas where I know I am tempted to ask AI instead.
  • App icons is on that list. Database migrations is on that list. Signing and certificates is on that list.
  • Check whether the platform already has a built-in answer before reaching for AI.
What went wrong with app icons — NonDev Apps