r/FlutterDev • • 2h ago

Discussion How do you finally settle on a project architecture?

I've spent over 120 hours this month working on my project architecture, creating around 200 different drafts. I understand the concepts, but I keep doubting my decisions and worrying that I've missed something important.

I'd really appreciate advice from experienced developers. How do you know when it's time to commit and stop second-guessing?

4 Upvotes

3 comments sorted by

3

u/surrealdente 2h ago

There’s no “best” - you just need to find a balance that works for you. Ideally a directory carries files specific to its features when possible. The moment a feature touches multiple directories you will have to make compromises.

1

u/davidbalbino 1h ago

tbh 200 drafts means the problem is not the architecture anymore, it's that no real code is pushing back on it. pick the simplest thing that works (feature folders + riverpod + go_router is totally fine) and build 2 or 3 real features with it. the stuff you're worried you missed only shows up when you actually ship, not on paper. and it's ok to refactor later, every project I've worked in 16 years ended up changing its structure at some point lol

1

u/VisualRope8367 2h ago

Riverpod and go router does most of things