About componentization
It is a kind of App architecture idea, which encapsulates the code and encapsulates it into components, which can be used independently. The components used in the project include the following
● Basic components (such as network request class, data cache, basic UI, basic Foundation)
● Functional components (such as image browser)
● Business components (such as login registration, home page, personal center, etc.)
Why do you need componentization?
The multi-terminal business is almost the same, and the supporting modules at the bottom of the business are also the same to save development costs. It is unnecessary to repeatedly write the same code to save testing costs. It is not necessary to test the same business multiple times. Business componentization is mainly for the independent operation of each business module ( Each carries out its own development work) without interfering with each other
● Decoupling
● Reuse, reduce code redundancy
● Ensure the code specification in the unit module, avoid the appearance as shown in the figure below
● Facilitate long-term iteration
● Facilitate testing
Our goal
● Single module runs independently
● Low coupling, high cohesion
● As low as possible dependencies
● …