Android APP is encapsulated into a third-party library

problem description

at present, the demand received from the product is to encapsulate the online APP into a third-party library for use by third-party companies

the biggest problem is not to generate packages, but how to change the existing business logic for others to access. It is really a difficult problem. Do you have any elegant implementation ideas?
currently uses the MVP architecture, how does the architecture need to be changed?

Jan.08,2022

plug-in? However, the premise of plug-in is that the other party uses the plug-in scheme; there is routing, so both of you have to use the routing scheme, and it should be easier to agree on some interface jumps than to provide an interface. This is actually more component-based development, so you can consider


for the universal necessary control library and component library, we can extract them into modules and make them into a third-party library that can be relied on by multiple projects.

the goal of the third-party library is to make it easy for users to use simple external configuration without knowing the internal logic, so the third-party library is suitable to use the MVP architecture to achieve "configuration decoupling".

for more information, please refer to my open source from 0 to 666 in 5 days)

Menu