The practice of short video SDK mainly involves some things, among which the most important is the architecture design of short video SDK, including the architecture design concept, architecture diagram, overall data flow, module architecture design, etc. Today xiaobian will briefly introduce the short video APP development, what kind of manufacturers to choose, manufacturers SDK architecture design concept.
First, the design concept of SDK must mention the naming specification. Just like Tencent’s corporate philosophy, their naming specification is unified, simple and refined. For example, they use PLShortVideo as the prefix for external core classes and name modules such as recording, editing and editing. Parameter configuration classes are named according to PLxxxSetting standard. The interface callback classes are named PLxxxListener
Second, they follow the concept of highly modular, pluggable modules; High modularity requires that each class and each method “live up to its name” and “do its job” in order to write clearer logic; High modularity can also promote high reuse and reduce duplicate code; The transcoding core class in SDK can achieve a high reuse because editing and editing require a decoding and re-encoding process at the end of saving.
Package division of short video SDK, they can clearly see the function division of each package, different functions are placed in different packages. Instead of using FFMPEG’s soft solution and soft solution, they tried to use Android and iOS system API for hard solution, which not only reduced the package size, but also made it much faster. Although it would add a lot of technical difficulties and involve a lot of holes, we still chose this solution. When third-party libraries are introduced, they are configured and tailored to strictly control the package size, so that all packages can be “small and precise” (1.5m). The last built-in filter module in the table, in which the filter resources can be selectively copied, SDK will automatically determine. Here are some ideas about module design.
The third point is to decoupled from UI. In the screenshots from different apps, we can see that each App has its own design. As a short video SDK, it is absolutely not allowed to limit the user’s play in UI. Some short video SDKS on the market have written down the UI as part of the SDK, which is very unfriendly to the customer in designing the UI interface. Instead, the SDK decoupled from the UI, and the client’s UI was customizable. There was only one place in the SDK that accepted the View:
And then scalability, we follow the concept of high scalability, openness. In the recording and editing process, there will be data callback and support third-party library for beauty, filters, stickers, special effects and other functions.
Finally, it is about the design of configurable parameters. In addition to the general parameters, such as camera resolution, frame rate, microphone sampling rate, etc., which can be configured, the parameters including beauty can also be configured.
Only by selecting a scientific and reasonable short video SDK, can a stable short video system be developed with short video APP. Short video APP development combined with short video SDK can create a complete set of short video system functions.