Introduce the system
I am currently engaged in technical research and development in a loan assistance company. The company's main business is loan super, that is, to obtain intended customers through investment flow. After the user downloads our APP, he fills in his personal information and conducts real-name authentication, and finally matches the suitable lending product.
Docking mode
As a loan super platform, we mainly use the API model (semi-process, full process). Currently, semi-process accounts for more than half, but starting this year, full-process products are gradually increasing. It is expected that full-process products will become the mainstream in the future, while semi-process products may be gradually eliminated. The reason is that the semi-process product experience is poor, and users need to switch between multiple APPs, which is easy to reduce usage rate; although the full process model perfectly solves this problem, it requires high technical capabilities of the team. If the technical team is insufficient, the R&D cost and cycle will be greatly increased when the number of products increases. Therefore, team managers need to pay attention to technical competence assessment and invest more energy in system design.
Trends in APP Design
The company's current Dianchao APP uses native development to display all pages. The advantage is that after the user opens the APP, the page loads very quickly, because all display pages are stored on the phone when downloaded. The disadvantage is that once an error occurs in the APP operation, the technical team cannot directly repair it through the background, and can only require users to actively upgrade the APP; and the review cycles of each application store are different, which may cause the problem to exist online for a long time.
Non-native development method (H5 display method): Unlike the native method, the H5 display method only pre-installs basic functions such as login, homepage, personal center, etc. after the user downloads the APP. Other pages such as borrowing and repayment, record query and other process pages are loaded on the background server. When the user enters the loan page, the system loads the latest page from the server in real time to ensure that the information is updated in time. If a problem occurs, the technical team can immediately fix it in the background, which will be almost unaware of the user. At present, mainstream APPs have adopted this mature technology method.
API product docking mechanism
Finally, let’s talk about the product docking mechanism. Currently, it takes about 5-8 days to access a semi-process product, while the entire process cycle takes 8-10 days, and development and testing each take about half of the time. This is mainly because the system docking standards of the loan platform and each product party are different, and it needs to be adapted according to the standards of the product party, resulting in the average period of access to a product exceeding one week.
I think the test time is long, and the main reason is that each docking requires not only verification of the borrowing and repayment data, but also comprehensive testing of functions and programs. In fact, the loan process of the APP is basically the same, and the difference is mainly due to the interaction standards of the two parties' systems. If you add an [Interaction Standard Compatibility Layer] between the two systems, you only need to configure this layer, which can basically solve the problem of differences in interaction standards such as data standards and data units (such as segments and elements). After the configuration is completed, future new products can even directly copy the standard configuration of similar products. If the product party does not have special requirements and does not even require technical personnel to participate, the operation or system administrator can operate the configuration and go online to verify.
The above are some of my understanding of the business I am responsible for. If you have any questions, please feel free to ask for exchanges and corrections. I will share some content related to technology, management, and growth from time to time. If you have any relevant interests, please feel free to communicate vx: EasonChean