Mobile business module componentization configuration method and system

Abstract

The invention provides a mobile business module componentization configuration method. The method comprises the steps of enabling module source codes to be independent of a project; configuring gradlescripts for independent compilation, debugging and running of modules; performing isolation processing on the codes; and performing optimization control on a version. The coupling degree of the codemodules can be effectively reduced, so that a code framework is clearer, and the modules can be subjected to independent development, running and debugging with the main project; and the modular compilation can effectively shorten the compilation time. The invention furthermore discloses a mobile business module componentization configuration system.

Description

technical field [0001] The invention relates to the technical field of mobile terminals, in particular to a method and system for configuring componentized mobile terminal service modules. Background technique [0002] In recent years, with the rise and prosperity of the mobile Internet, many companies have transplanted their business on the traditional platform to the mobile terminal. More and more codes are pouring into small clients, especially some carrier-level applications, on which various business modules need to be promoted. Regardless of the iOS system or the Android system, the volume of various clients has also become bloated and huge. In order to reduce the complexity and coupling degree of large-scale mobile client software development, and to meet the requirements of module reuse, multi-team parallel development and testing, etc., there is an urgent need for a technology that can divide the client into parts, and these modules can be freely combined , and wh...

AI Technical Summary

Problems solved by technology

[0004] To sum up, the shortcomings of the existing technology mainly include: 1. Code decoupling and isolation: Since the initial stage of module development is generally developed together with the main project in the form of source code, resulting in high coupling between the module and the main project, and the code is not isolated , the main project is easy to misreference the code and resources in the module, which may lead to some difficult-to-find problems

2. The module cannot be run and debugged separately: since the module exists in the form of a library in the project, it cannot be run and debugged separately

3. Long project compilation and construction time: every time the project is rebuilt, the source code of each module must be rebuilt and compiled, resulting in a long construction time for large multi-module projects, which affects development efficiency

Images