It’s great that you’re researching clean architecture and design patterns, but when you come across BLoC, MVVM, MVC, etc., it can get overwhelming. The key takeaway here is: You don’t have to stick to just one approach. But if you set up a solid foundation from the beginning, you won’t feel the need to scrap your project later on.

Here’s my best recommendation for you: Use MVVM + Clean Architecture.

MVVM (Model-View-ViewModel) helps separate UI from business logic, making your code more readable and maintainable. Clean Architecture structures your code into layers, which helps you manage complexity as the project grows. If you combine these two, you’ll have a strong foundation for scalable projects. For state management, you can go with BLoC or Riverpod. BLoC is more structured but can feel a bit heavy, while Riverpod is easier to work with and more flexible.

Here are two great articles that might help:

1️⃣ https://medium.com/@fkurt97/flutter-b%C3%BCy%C3%BCmeye-a%C3%A7%C4%B1k-proje-yap%C4%B1s%C4%B1-8342f3696696

2️⃣ https://medium.com/@Emmadex/flutter-uygulama-geli%C5%9Ftirme-mvc-ve-mvvm-mimarileri-643bb444a277

To sum it up: If you start with the right architecture, you won’t have to throw away your project later. Go with Clean Architecture + MVVM, and choose either BLoC or Riverpod for state management. The most important thing is finding what works best for you. You can try different approaches on smaller projects to see which one feels most comfortable.