I agree that we should avoid getters in presenters as much as we can. In this situation however I felt querying for number of elements in presenter is more natural as it works like routing the logic from the adapter to presenter in this example. You said presenter should call view methods so it’s testable and I agree with testability, but can’t see how this makes the presenter untestable. Also I am not tightly coupling views with presenters, as presenter is communicating with views trough interface always. Presenter knows when and what should be displayed, while view knows how to display it. Of course the data comes from model, but still this is the presenter’s responsibility to trigger data loading in Model and push it to the view whenever it feels its ready.

    Andrzej Chmielewski

    Written by

    Android Developer. Big fan of good quality software and UX.