Home > Mobile >  Android modular architecture how to solve the problem of interaction between each module?
Android modular architecture how to solve the problem of interaction between each module?

Time:09-21

Android componentized purpose is to make the decoupling between each module, contradictory, but in daily development is to avoid not call each other, how to efficiently solve the problem?
That is plan should consider memory footprint, and response time.

CodePudding user response:

Through ARuoter routing framework implementations have to do is to call each other, an example of https://github.com/979451341/MDemo

CodePudding user response:

ARuoter is to start the Activity plan with method calls between each module is not the same

CodePudding user response:

It is best not to directly call module, in this case, modular separation does not make sense, use the middle module implementation,

CodePudding user response:

Use the observer pattern, RxAndroid can understand

CodePudding user response:

EventBus RxBus LiveDataBus

CodePudding user response:

Aidl to also go

CodePudding user response:

Process more than the thread
  • Related