android-mvp | Android MVP Reference Architecture and Video Tutorial | Reactive Programming library

I'm learning DI/MVP/Retrofit/Rx base of this tutorial Dagger 2 Retrofit MVp .

And everything work perfect but I've got problem with using context in Adapter which if it wasn't just about intent i could use some method to open activity without using context, but i'm using library that named Picasso.

I have a service like this

I have this method that I am trying to pull data from an API, and then update the text view. Everything works except getRecipeName doesn't finish after the "end Method" log. .getRecipeName() uses RetroFit to pull from an API.

I am currently learning MVP, Dagger, RxJava, and Butterknife all at once using Mindork's Github page on MVP Architecture

I commented out the .subscribeOn and .observeOn to see the result difference and nothing changed.

I'm building an Android application using MVP. One of the screen displays data in a sort of Master/Detail view (a content page embedding a player):

At the top, there is the player (fragment) and below is the content info (viewpager with fragments), and user can swipe between pages (ViewPager) to switch between contents. When the Viewpager position changes, the player is updated accordingly and starts playing the current content.

Data requested by the presenter comes from a repository, with local(database)/remote(Rest API) datasources.

How can I make the best use of MVP to avoid requesting the same data multiple times?

Should I have only one Presenter in my Activity, and persist/cache data requested for the Content Info Info somewhere, to pass it back to the player when the position is changed?

Or is it better to have a presenter for each ContentInfo, requesting its own data, and a presenter for the player, requesting the same data again when the play() method is called?

I found this related topic, but it doesn't really fit to my case, as the data is not updated in the player at the same time that it is requested in the Content Info fragment (I'm fetching the data onCreate of the fragment by the ViewPager to have it already loaded when the swipe is done).

I was implementing MVP in my new application, then I came across a problem. I needed to call a method of View, inside View (Activity) itself. It is by definition of MVP code separation, wrong thing to do.

By definition:

The Presenter is in charge of the the orchestration between the Model and the View. It basically receive events from both and act consequently. The Presenter is the only component that knows others. It has a reference to the View and a another to the Model. (source)

In the same article it was mentioned that View does not reacts to user interactions, it passes control to Presenter to do the job. I have also read this SOF post about dependency rules.

In my case, I am using custom AppTheme. AppTheme needs to be set before setContent() call, what I am doing is create a method in View interface called setAppTheme() which my Activity implements, and there is code to apply theme. Now the problem is, this is called within the app, which makes calling of a View method inside its implementation.

To sum up, what my understanding of MVP either one of the following should be true:

• Do call View method inside Activity, because setTheme() wont work after setContent() and our presenter.setView() is in onResume(), but will this satisfy MVP separation of M-V-P ?

• Do not make interface method for setAppTheme(), instead create a private method in Activity which sets theme. This method will have nothing to do with any layer of MVP. But question is, if project is using MVP pattern, is this practice valid?

Here is my MVP:

I am learning Kotlin and Dagger 2 simultaneously by attempting to convert some of Mindorks advanced MVP sample to Kotlin but am having Dagger2 compile issues. I am swimming in classes here but am very close! Don't mind the untidiness, I intend to comb over each class once it compiles. If something is missing please let me know. The error comes down to my presenter class not being correctly injected into the activity. The error reads as follows:

I am developing an Android application with MVP and RxJava. Well, I have a doubt:

When I am creating my presenter and interactor I can put me Schedulers in the presenter, like this:

Schedulers in the Presenter

Presenter: