[Flutter] Clean architecture and repositories

Lately for the Flutter projects I have been working on, I have decided to adopt a feature-driven architecture using Clean Architecture. With a software design done in great detail it turns out to be very suitable in the division of logic.

These days, however, a question has arisen for me regarding the use of repositories. In an application where Firestore is used and repositories are the layer where I interact with such data is it right to have a division of them on the various features while still going to work on the same collections? (Different parts consisting of different features but touching the same collection of data). At the end of the work I might find several repository classes with the same code even though they belong to different features.

Clarification would be greatly appreciated! Thanks in advance

Continue reading...