The Play Store rejected my first submission because of the app icon. Not the icon itself — the format. I had generated a great-looking icon using an AI image tool, exported it as a PNG, and submitted it. The resolution was wrong. The safe zone was wrong. The format was wrong in three different ways I did not know were requirements.
I spent the next four hours going back and forth between AI, the Play Store documentation, and Android Studio. I asked Claude to help. I asked Codex to help. Neither of them knew exactly what Play Store required in 2025 because the requirements had been updated.
The actual fix took twelve minutes once I found the right tool. Android Studio has an Image Asset Studio built in. You give it one high-resolution image and it generates every icon size you need, in every format, automatically. It is the right tool for the job and I had ignored it completely.
The lesson here is not about icons. It is about tools. When you are building with AI, it is easy to think AI can do everything. It cannot. Native development tools — Android Studio's built-in features, Xcode's asset catalogs, the Play Store dashboard itself — are designed to solve specific problems that AI assistance does not replace.
I now keep a list of "use the right tool" reminders for the places I know I am tempted to ask AI when I should be using a native feature instead. App icons is on that list. So is database migrations. So is signing and certificates.
Four hours. Twelve minutes. I try to remember that gap every time I reach for AI before I have checked whether the platform already has a built-in answer.