From Spaghetti to Structure: Why I Migrated My Production Flutter App to Clean Architecture

"First make it work, then make it beautiful and robust." I'm a junior dev. I built a real app — Anahad — that real people use. And for a while, I was proud of it. Then it grew. And I wasn't so proud anymore. This isn't a textbook post about Clean Architecture. This is the story of what broke, why I finally made the switch, and what actually clicked for me — told by someone who was in the trenches with a messy codebase and had to ship features at the same time. The Mess I Was Living In Picture this: 6 features. Each with their own screens, widgets, blocs, services, and utils — all distributed across a directory structure that looked neat on day one and became a labyrinth by month three. Most screens were monoliths — all-in-one files with UI and logic tangled together. The ones that did use components? Everything went into a global widgets/ directory. So you'd have prop drilling across three levels just to pass something that one widget needed. Tracking the flow of data meant hopping bet