Answer the question
In order to leave comments, you need to log in
Android, clean architecture is it worth doing input, output interactor?
Hello. I am immersed in the study of clean architecture when writing an application, the question arose of whether it is worth splitting the interactor`s with which I rely on input and output in the presentation layer, namely the input will contain logic that, as a result of user interaction, the output will, for example, display a list of goods or something else in this kind? I just read a lot and only a couple of articles have written such an approach, but basically no one shares the logic ..... why it’s not clear, because we divide the logic into different classes, because for this we use all sorts of architectural patterns.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question