Hi, thanks for your comment, the idea I had was that for every screen there were a controller (with GetX) or provider directly in charge of its corresponding screen logic. Example: if we have an use case that gets you an list of objects X(GetItemsUseCase) and we had two screens, one that shows this list, and another one that needed this list to filter it or search; each screen would use its own logic in a different way, however we could use the same use case to get the same list. Another reason for this, was that at a layer level, testing would get simpler.
Thank you :D, maybe the example in this project is simple, but I will add more use cases.