Component based learning (1) idea and Implementation

1. Introduction to componentization

I think componentization , The whole project consists of app Shell , Several business components , And common basic components . As shown in the figure

I think the most obvious feature of componentization is ： There is no direct horizontal dependency between business modules .

significance ： Don't depend on each other , But they can interact with each other ; Highly decoupled ; Free disassembly

2. Componentized deployment

About how to componentize the project , There are a lot of learning resources on the Internet , I recommend an article , It's super detailed ： This is the article

3. Communication between components ：

Of course, the most commonly used is Alibaba open source ARouter. I won't introduce more about this , But in addition to this way , There are several other more primitive ways

① Use EventBus

shortcoming ：EventBus Maintenance costs are high , Poor management

② Use radio

shortcoming ： Broadcasting is not easy to manage , Once the message is not handled , The unification was sent out

③ Use implicit intent

shortcoming ： stay AndroidManifest.xml It's configured inside xml That's too much

④ Use class loading

shortcoming ： It is easy to write wrong package name and class name
principle ： become involved apk When the package , It opens at dex file , Find that the modules are together , Pictured
So this is the inspiration of this kind of loading method

⑤ Use global Map（ Low profile version ARouter）

shortcoming ： To register a lot of objects .
every last Activity At the time of creation , To the overall situation Map Register inside . When you need to jump , From this overall situation Map Internal basis key Go and get the corresponding Activity object , This completes the communication