Brief introduction:How does a large front end team choose technology? How to get started quickly? How to collaborate effectively? Let’s take a look at how Kuacheng solves this problem.

The introduction

Since 2017, the GMTC Mobile Technology Conference has been renamed the Big Front-End Technology Conference. Up to now, mixed development, native development, front-end development and other concepts are deeply integrated to form a “big front-end” team.

How does a large front end team choose technology? How to get started quickly? How to collaborate effectively? Let’s take a look at how Kuacheng solves this problem.

It started with two places and three teams

Kuaisheng Technology is a leading technology enterprise in the field of online freight transportation, ranking the top three in the market. The platform has 3W + bulk commodity shippers, who issue the order to the platform, and the truck drivers with 60W + will take the order and carry the goods, generating 12 billion yuan of freight transaction volume every year.

Take the driver side as an example, it needs to undertake a series of services with strong correlation and long process chain, from the issue of orders to the entry and exit management, from the in-route monitoring to the financial white strip refueling and gas filling. These tasks are completed by three research and development teams in the two places.

In the 7*24 hour uninterrupted customer service and the high iteration of 2-3 releases per month, the bottleneck of the technical framework has gradually become prominent, specifically including:

• In terms of system framework, the initial framework is native APP +HTML5. Traditional Web has white screen and poor performance response, which greatly reduces user experience.
• In terms of release cycle, there are many R & D departments and long product chains. Some enterprises need more personalized customized services, leading to inconsistent expected release cycle. Frequent delivery updates not only reduce operational efficiency, but also bring customers trouble of frequent updates.
• In terms of experience consistency, native development depends on the system framework. Due to the different native characteristics, the multi-channel platforms of various manufacturers are highly differentiated, and the performance and experience of multi-platform are greatly different.
• In terms of multi-department collaboration, common development languages and front-end JavaScript frameworks are not the same, and technical personnel cannot be flexibly deployed for collaborative development according to the requirements of tension and DDL.

Under the background of rapid development of Kuaisheng Technology business, excellent technical architecture is the guarantee of “improving quality and efficiency”, so system restructuring is imperative. Soon becoming friends began to look for a good architecture to solve the problem of the scene.

Four Dimensions of Selection

In view of the problems found, four selection dimensions are discussed:

• Framework maturity: to put it simply, is whether the new technology is reliable, billions of business pressure, there is not too much room for trial and error;
• Migration cost: if we want to gain benefits from new technology, what cost should we pay, such as the learning cost of new technology, the transformation cost of original architecture, etc.;
• Community atmosphere: it mainly depends on whether there are enough people to follow up the technology, whether the documentation is rich, whether the problems can be helped, etc.
• Considerations are based on performance, cross-platform and dynamics.

After setting the goal of technology selection, the team conducted a series of surveys and demos on common cross-platform solutions such as React Native, Weex, Flutter and applet. Horizonwise comparisons are as follows:

Using the MPaaS applet container, it integrates the MPaaS framework, offline packages and reusable H5 plug-ins, relying on a powerful Web rendering engine
Give it a try
The entire playback
1. Multi-team cooperation

2. Real-world testing
`
`
3. Core problem solving

4. Elegant interaction

It should be a future




Copyright Notice: