Hi Adrian,

I’m glad that this article helped you understand. Let me answer those for you.

I write Interactors when they handle specific use cases. You can absolutely avoid writing Interactors when you need to handle some Android specific logic. In your case, checking Wi-Fi state is something that is an implementation detail and should not go into Interactors.

You can put the class that checks Wi-Fi state anywhere in the outer layer. But you would use it in an Interactor when checking for connectivity if it is an actual part of your business logic. Of course, your Interactors would then call that class using an interface.

I will tackle long running tasks in the next article. But you are on the right track. You could create a singleton Presenter that stays alive when an Activity dies. This way the Interactor will not die as well. Then to notify the UI you could use an EventBus or you could give the Activity to the Presenter when it becomes alive.

I will cover this in more detail soon :)