Now this seems very confusing when it comes to Riverpod. How we separate the business logic from the UI?
Well, I’d consider Riverpod or any state management as part of the controller layer in terms of managing app logic and state, because it does what “controllers” are meant to do, pass information between the views and the models, but since the invention of these architectures didn’t really have flutter in mind, so, they would not have considered state management, I’d still practically keep the state management in a separate folder just to maintain a clean and organized codebase, I mean at the end of the day, the architectures don’t necessarily mean you MUST only have Model View Controller folders, you can also have some extra, but the underlying Logic of communication will go from controller to view and so on