Clarification on Mobius Controller

[rajdheepak]

    @pettermahlen We are mostly using mobius loops with viewmodel across our app. 

What is the use case for a mobius controller?

Can Mobius Controller be thought of an equivalent to VM with loop?

Could you give me actual example use cases for Using Mobius controller over VM with loop?

Originally posted by @rajdheepak in #157 (comment)

[togi]

The controller it's just an utility to be able to interrupt and continue a loop from its last state, plus it helps set up the cyclic dependency between UI and business logic. The controller predates MobiusLoopViewModel, and if you use MLVM then there is no need to have a controller.

[rajdheepak]

Any thoughts/suggestions on how does Mobius architecture glue into the android paging library? I am guessing you must have a lot of paging stuff in spotify, some insights please.

What are we doing now? TLDR- VM holding the loop is supplied to the data source which uses VM instance to dispatch events and observe states which eventually updates data on callbacks in loadBefore/loadAfter.

@togi