Spending Hours Designing the UI? Or Just Telling AI the Pain Story

Cathy Lai Posted on May 31 Spending Hours Designing the UI? Or Just Telling AI the Pain Story # ai # uidesign # devjournal # buildinpublic AI-Assisted Garden Makeover App "Ez Garden Visualizer" - From Idea to Reality (9 Part Series) 1 How I Stopped Despairing Over the Backyard Mess and Started an AI Side Project 2 From the Concept to Reality: Building "Ez Garden Visualizer" in Stages ... 5 more parts... 3 "Hello World" OpenAI API Script for Image Edit 4 AI Assisted GUI Took Seconds 5 How I Got Users to Willingly Wait 1 Minute for an API Call (Without Over-Engineering) 6 How Adding People to My AI Garden Images Gave It a Personality (and Attracting the Right Users) 7 I Thought My One Sentence Is Creating a Perfect GPT Image; Until I Realized It Had Been Learning My "Taste" All Along 8 Garden Visualizer - Would Results Improve Using Example Images? (Screenshots Included) 9 Spending Hours Designing the UI? Or Just Telling AI the Pain Story Now that I get my backend API services in place, it's time to design a frontend! Just describe the mood to AI, right? I did, and it looked... fine. But it didn't feel right. It didn't match the soul of why I was building it. So, instead of looking at font pairing blogs for three hours, I sat down and told Gemini the personal story and frustration behind the app. Outdated Garden Styles I explained that as a busy professional, I felt completely alienated by the gardening world. Every time I looked up gardening advice on YouTube or blogs to fix up my yard, I was met with slow acoustic country music, rambling lectures full of jargons, and an aesthetic that felt like a grandmother giving advice. It felt old fashioned, inefficient, and totally out of touch with how my peers and I live. For example: ❌ Old fashion garden style We don't want a chaotic cottagecore wildflower patch that takes six hours a week to prune. Our design references are the sleek tech offices we work in, the boutique hotels we vis