Multi-platform multi-application adaptation method and device, development platform, equipment and medium

Abstract

The present disclosure provides a multi-platform multi-application adaptation method and device, a development framework platform, an electronic device and a computer readable storage medium, and relates to the technical field of mobile software development. The method comprises the following steps: providing native container bases corresponding to different operating systems, each native container base providing a unified native container standard capability application programming interface (API), providing various end container bases, the end container bases being integrated based on the native container standard capability API, and providing corresponding end container APIs, and developing applications based on the end container APIs. The embodiments of the present disclosure can smooth the problems of different ends, different app protocol standards and the like, the standard API protocols are unified, and the adaptation of multi-platform multi-applications can be realized.

Description

Technical Field

[0001] This disclosure relates to the field of mobile software development technology, and in particular to a multi-platform and multi-application adaptation method, apparatus, development framework platform, electronic device, and computer-readable storage medium. Background Technology

[0002] Developers on each platform use their own technology stack to write business code, which requires a lot of adaptation development work. For example, they need to write adaptation code to adapt to different app protocols and different platform protocols. Developers on each platform and app administrators need to communicate extensively to adapt to the protocols, which is time-consuming and labor-intensive. They cannot directly use native capabilities and cannot focus on developing upper-level business.

[0003] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0004] This disclosure provides a multi-platform, multi-application adaptation method, apparatus, development framework platform, electronic device, and computer-readable storage medium, which at least to some extent overcomes the problem of large development volume of adaptation protocols in related technologies.

[0005] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0006] According to one aspect of this disclosure, a multi-platform and multi-application adaptation method is provided, comprising: providing native container bases corresponding to different operating systems, each native container base providing a unified native container standard capability application programming interface (API); providing various end container bases, each end container base integrating based on the native container standard capability API and providing a corresponding end container API; and developing applications based on the end container APIs, thereby achieving multi-platform and multi-application adaptation.

[0007] In one embodiment of this disclosure, the end-container API includes: routes, containers, channels, degradation, bridges, or components.

[0008] In one embodiment of this disclosure, the native container standard capability API includes: routing, permission and privacy management, lifecycle management, container stack management, template management, service management, event message management, or application context.

[0009] In one embodiment of this disclosure, the native container standard capability API further includes a data reporting component, which includes crash, anomaly analysis, performance analysis, or event tracking components.

[0010] In an embodiment of the present disclosure, the end container base comprises: a Flutter, RN, H5 or applet corresponding container base; and the operating system comprises: an Android, iOS or Harmony.

[0011] In an embodiment of the present disclosure, the developing an application based on the end container API to achieve multi-platform and multi-application adaptation comprises: developing a micro application based on the end container API to create a Bundle project package; and merging the Bundle project package through a Portal project to generate an application.

[0012] In an embodiment of the present disclosure, the method further comprises: entering a start page by starting the micro application; obtaining configuration information of a user, the configuration information comprising: program identification and key information; starting a target micro-service application according to the configuration information, and generating a corresponding service instance.

[0013] In an embodiment of the present disclosure, the method further comprises: obtaining user instruction information, and managing the target micro-service application through a container manager.

[0014] According to another aspect of the present disclosure, a multi-platform and multi-application adaptation device is also provided, comprising:

[0015] a Bundle project package generation module configured to develop a micro application based on an end container API to generate a Bundle project package;

[0016] an application merging module configured to merge the Bundle project package through a Portal project to generate an application.

[0017] According to another aspect of the present disclosure, a development framework platform is also provided, comprising:

[0018] a plurality of native container bases corresponding to different operating systems, each of the native container bases providing a unified native container standard capability API;

[0019] one or more end container bases integrated based on the native container standard capability API, and providing a corresponding end container API, so as to develop an application based on the end container API to achieve multi-platform and multi-application adaptation.

[0020] According to another aspect of the present disclosure, an electronic device is also provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the above-mentioned multi-platform and multi-application adaptation method via executing the executable instructions.

[0021] According to another aspect of the present disclosure, a computer readable storage medium is also provided, which stores a computer program. The computer program is executed by a processor to implement the multi-platform multi-application adaptation method according to any one of the above aspects.

[0022] The multi-platform multi-application adaptation method, device, development framework platform, electronic device and computer readable storage medium provided by the embodiments of the present disclosure provide native container bases corresponding to different operating systems, each of which provides a unified native container standard capability application programming interface (API), provides various end container bases, and integrates the end container bases based on the native container standard capability API and provides corresponding end container API. The application is developed based on the end container API, which smoothes the differences between different ends and different app protocol standards, and the standard API protocol is unified, so that the adaptation of multi-platform multi-application can be achieved.

[0023] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and are not limiting to the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0024] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure. Obviously, the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creative labor on the basis of these drawings.

[0025] Figure 1 A flow chart of a multi-platform multi-application adaptation method in an embodiment of the present disclosure is shown;

[0026] Figure 2 A flow chart of an application installation package generation method in an embodiment of the present disclosure is shown;

[0027] Figure 3 A schematic diagram of an application installation package generation device in an embodiment of the present disclosure is shown;

[0028] Figure 4 A flow chart of a micro-application life cycle management running method in an embodiment of the present disclosure is shown;

[0029] Figure 5 A micro-application life cycle management state diagram in an embodiment of the present disclosure is shown;

[0030] Figure 6 A development framework platform diagram in an embodiment of the present disclosure is shown;

[0031] Figure 7 A multi-platform multi-application adaptation device diagram in an embodiment of the present disclosure is shown;

[0032] Figure 8 Fig. 1 shows a schematic diagram of a multi-platform multi-application adaptation system according to an embodiment of the present disclosure; and

[0033] Figure 9 Fig. 2 shows a structural block diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0034] Example implementations will now be described more fully with reference to the accompanying drawings. Example implementations can be implemented in any

[0035] In addition, the drawings are to be considered in all respects as illustrative and not restrictive; identical reference numerals have been used, where possible, to denote identical or similar features, and thus repetition of the description therefor will be omitted. Some of the blocks in the drawings are functional blocks, and can not necessarily correspond to physical or logical entities. These functional blocks can be implemented in software, hardware, or a combination thereof, in one or more hardware or integrated circuit devices, or in different network and / or processor devices and / or microcontroller devices.

[0036] For the convenience of understanding, the following first explains several terms related to the present disclosure as follows:

[0037] API (Application Programming Interface) is a set of pre-defined functions, which aims to provide the ability for an application to access a set of routines based on a certain software or hardware without accessing the source code or understanding the details of the internal working mechanism.

[0038] SDK (Software Development Kit) is a set of development tools used by software engineers to create applications for a specific software package, software framework, hardware platform, operating system, etc. It can simply provide some files of application programming interface API for a certain programming language, but it can also include complex hardware that can communicate with some embedded systems, example code, supporting technical annotations, or other supporting documents that clarify doubts for basic reference materials.

[0039] OSGi (Open Service Gateway Initiative) is a dynamic modular specification for the Java technology platform that defines the architecture for developing and deploying modular applications and libraries.

[0040] The following detailed description of this exemplary implementation method is provided in conjunction with the accompanying drawings and embodiments.

[0041] First, this disclosure provides a multi-platform, multi-application adaptation method, which can be executed by any electronic device with computing power.

[0042] Figure 1 This diagram illustrates a flowchart of a multi-platform, multi-application adaptation method according to an embodiment of the present disclosure, such as... Figure 1 As shown, the multi-platform, multi-application adaptation method provided in this embodiment includes the following steps:

[0043] S102 provides native container docks for different operating systems, and each native container dock provides a unified native container standard capability application programming interface (API).

[0044] In one embodiment, the operating system includes, but is not limited to: Android, iOS, and HarmonyOS.

[0045] In one embodiment, an API (Application Programming Interface) is a set of predefined functions designed to provide applications and developers with the ability to access a set of routines based on certain software or hardware. Native container standard capability APIs are defined, unified standard interface layers that provide a unified standard interface to upper-layer cross-platform containers, addressing different implementations across different operating systems. Upper-layer cross-platform containers can directly call this standard interface without needing to perform compatibility checks with the underlying native containers. Native container standard capability APIs include, but are not limited to: routing, permission and privacy management, lifecycle management, container stack management, template management, service management, event message management, application context, or data reporting components. Data reporting components include, but are not limited to: crash detection, exception analysis, performance analysis, or event tracking components.

[0046] For example, the performance analysis component is divided into an SDK (Software Development Kit) end and a service end. The SDK end is the client code of the component, which collects the performance information of the app, and then calls the interface of the service end to report to the service end for calculation, analysis and storage. Then, the management end of the website can see the performance information of the app, such as startup performance and app freezing, so as to analyze and optimize the running of the app. The container architecture is adopted, and the performance analysis component and other basic common functions can be directly used without developing components according to different operating systems, reducing human resources.

[0047] In S104, a plurality of end container bases are provided, and the end container bases are integrated based on a native container standard capability API set and provide corresponding end container APIs.

[0048] In one embodiment, the end container base includes, but is not limited to, a container base corresponding to Flutter, RN, H5 or a small program. Flutter is an open source cross-platform UI framework that can quickly build high-quality native user interfaces on platforms such as Android and iOS. RN (React Native) is an open source cross-platform mobile application development framework that uses the Javascript language to build user interfaces. It realizes responsive and component-based development of data and supports iOS and Android platforms. H5 (Hyper Text Markup Language 5) can adapt to mobile terminals and is equivalent to a link and a page. The specific requirement is to cooperate with mobile APP development and write some H5 pages embedded in the app. A small program is an application program between a web page and a native app.

[0049] In one embodiment, the end container API includes, but is not limited to, routing, container, channel, degradation, bridge or component.

[0050] The end container API is a standard API interface that has been implemented and integrated in the end container base. The business code in the upper layer can safely call these standard APIs, because these standard APIs also call the underlying native container standard capability API. This ensures that a set of code can run on different system platforms and different apps, because the standards are unified.

[0051] For example, the routing strategy is different in each end. If there is no unified routing strategy standard, the business development often needs to write a set of IOS routing strategy adaptation code and a set of Android routing strategy adaptation code, which will waste a lot of manpower.

[0052] S106, develop the application based on the end container API, so as to realize the adaptation of multiple platforms and multiple applications.

[0053] In one embodiment, the micro application is created by developing the application based on the end container API, and a Bundle project package is generated; the Bundle project package is merged by a Portal project to generate an application.

[0054] In the above embodiment, each native platform and each app integrates a container base, and the adaptation work has been done in the container base framework; after the business code is developed by each end developer, a large amount of adaptation code no longer needs to be written, and a large amount of communication and adaptation agreement between the end developer and the app manager no longer needs to be performed, time and energy are saved, the standard API protocol is unified, once writing can realize multiple platforms and multiple applications, and a large number of basic components are deposited to output the capability to the upper layer container through the service registration system, so that a large amount of repeated development of middleware is avoided.

[0055] Figure 2 A flowchart of an application installation package generation method in the embodiment of the present disclosure is shown as follows. Figure 2 As shown in the flowchart, the application installation package generation method provided in the embodiment of the present disclosure includes the following steps.

[0056] S202, create a micro application by developing the application based on the end container API, and generate a Bundle project package;

[0057] The mPaaS divides an app into one or more Bundle projects and a Portal project framework based on the OSGi (Open Service Gateway Initiative) technology, the Portal project is equivalent to the shell of the app product, and is the entrance of the entire app product; one product has one Portal shell project, and the Bundle project package can be added to the Portal shell project at will, and the Bundle project package is equivalent to various business components; the mPaaS manages the life cycle and dependency of each Bundle project, the Bundle project package is compiled in the Portal, the Portal project combines all the Bundle project packages into a runnable.apk package through the mPaaS plug-in.

[0058] In one embodiment, the application manager can automatically create a Portal shell project when creating one application on the platform, and integrates a container framework base; the container framework base is a base integrating a native container base and an end container base, directly takes over the life cycle of the application, is responsible for the entire application startup hosting, application life cycle management, processing and distribution of agent events of the app, unified management of business modules such as micro applications and services, and can assign permissions to the micro application developer.

[0059] In one embodiment, the plurality of micro-application developers develop application based on the assigned permissions and the end container API to create micro-applications to generate Bundle code, and the Bundle code and Portal shell project are stored in the code repository; and the Bundle code is packaged and built into a Bundle project package.

[0060] S204, uploading the Bundle project package to the artifact repository;

[0061] The Bundle project package is an apk project file packaged and generated based on the Bundle code, and the artifact repository stores one or more Bundle project packages.

[0062] S206, when receiving a request for integrating micro-applications into an application, merging the Bundle project package in the artifact repository through the Portal project to generate an application.

[0063] In one embodiment, the application manager submits micro-applications for application integration, triggers app building, and packages into a final apk.

[0064] In one embodiment, Figure 3 An application installation package generation device is shown in the embodiments of the present disclosure, which includes a code repository 301, an artifact repository 302, and a final apk 303;

[0065] The plurality of micro-application developers develop application based on the assigned permissions and the end container API to create micro-applications to generate first Bundle code and second Bundle code, and the first Bundle code, the second Bundle code, and the Portal shell project are stored in the code repository 301;

[0066] The first Bundle code and the second Bundle code are packaged and built into a first Bundle project package and a second Bundle project package, and the artifact repository 302 stores one or more Bundle project packages;

[0067] The application manager submits micro-applications for application integration, triggers app building, and packages into a final apk 303. The application manager can view and manage all technical stack business modules of the application in one system and uniformly manage integration, reducing communication and integration testing work with technical developers.

[0068] In the above embodiments, since the micro-application and the application both integrate the container framework base, the end container development standard API and the native container base standard API are unified, and the problems of different end, different app protocol standards are smoothed out. The standard API protocol is unified, so that one-time writing of multiple platforms and multiple applications can be realized.

[0069] Figure 4 A flow chart of a micro application life cycle management running method in the embodiment of the present disclosure is shown in FIG. 1. Figure 4 As shown in the figure, the micro application life cycle management running method provided in the embodiment of the present disclosure includes the following steps:

[0070] S402, starting the micro application to enter a start page;

[0071] The micro application is essentially an application program, which is a kind of desktop launcher, and can be a launcher micro application. After the app is started, the container framework base takes over the life cycle management of the micro application. After the app is started, the launcher micro application is started first to enter the start page, and then other micro applications will be opened according to the user's operation. For example, the launcher micro application is started first after the app is opened, which is equivalent to the home page of the app. There are many links and buttons in the home page, such as clicking the shopping cart to trigger the opening of the shopping cart micro application, and clicking the product to open the product detail micro application.

[0072] S404, obtaining the configuration information of the user, the configuration information including program identification and key information;

[0073] In an embodiment, each micro service application corresponds to a program identification and key information. The configuration information is used when the app requests the server interface. The server authenticates the configuration information, and after passing the authentication, the configuration information is analyzed and stored. Otherwise, it will be discarded directly.

[0074] S406, starting the target micro service application according to the configuration information, and generating the corresponding service instance.

[0075] In an embodiment, after verifying the user according to the configuration information, the user clicks the micro application to trigger the start request to start the target micro application, and trigger the search and creation of the service instance corresponding to the target micro service application.

[0076] S408, obtaining user instruction information, and managing the target micro service application through the container manager.

[0077] In an embodiment, the micro application to be started is triggered, the micro application is started, and the micro application runs in the foreground. When the user switches the micro application, the micro application is paused and enters the background. When the user switches back to the application, the micro application is activated and enters the foreground. Finally, the micro application is exited. Each micro application or service can go through one or more processes from starting to destroying, without limitation.

[0078] In the above embodiment, the micro application independent running environment realizes micro application life cycle management, realizes one development and multi-platform and multi-application running management, and the business micro application can be published on multiple terminals and across Apps; the business is developed in the micro application mode, and is independently developed and run, and the development and coordination of the business do not affect each other, thereby solving the problems that the business team is too large, the developers and managers need to communicate a lot, and the integration test workload is huge and time-consuming and labor-consuming.

[0079] Figure 5 A micro application life cycle management state diagram in the embodiment of the present disclosure is shown, as shown in Figure 5 The Bundle micro application 503 includes a launcher micro application 5031, other service 5032, and other business micro application 5033.

[0080] The Bundle micro application 503 includes a launcher micro application 5031, other service 5032, and other business micro application 5033.

[0081] The container framework base standard API 501 provides a unified native container standard capability API and an end container base integrated based on the native container standard capability API, and provides a corresponding end container API; the input and output parameters and functions of the container framework base interface API are consistent, and therefore, the API is called a standard API.

[0082] The launcher micro application 5031 is equivalent to the home page of the app, and the home page has many links and buttons, for example, clicking the shopping cart triggers the opening of the shopping cart micro application, and clicking the product opens the product detail micro application.

[0083] The other service 5032 refers to the background service code for providing basic general functions, for example, a basic control service responsible for reading and managing all icons; a login state service is code responsible for maintaining the expiration time of the login state.

[0084] The other business micro application 5033 refers to the page-based independently running business code, for example, a shopping cart micro application, a product detail micro application, and a settlement page micro application.

[0085] The Bundle is a micro application container, and starting a micro application is starting a Bundle; the container manager 502 is a service for managing the starting, pausing, activating, and exiting of the Bundle; for example, the container manager 502 reads the configuration information after the application is started, starts the target micro service application, and generates the corresponding service instance.

[0086] The above embodiment is an example of a state after running multiple micro-applications. The micro-applications run in an independent environment, realize micro-application lifecycle management, realize one-time development, multi-platform and multi-application operation management, and business micro-applications can be deployed to multiple terminals and across apps. Businesses are developed and run independently in the form of micro-applications facing the container. The development and operation of businesses are coordinated and run without affecting each other. This solves the problem of excessively large business teams, which require developers and managers to do a lot of communication and integration testing, resulting in a huge workload and time and effort.

[0087] Figure 6 This diagram illustrates a development framework platform according to an embodiment of the present disclosure, such as... Figure 6 As shown, the development framework platform includes:

[0088] Native container docks 601 corresponding to different operating systems, each native container dock 601 provides a unified native container standard capability API;

[0089] One or more end container bases 602, which are integrated based on native container standard capability APIs and provide corresponding end container APIs to enable application development based on end container APIs, thereby achieving multi-platform and multi-application adaptation.

[0090] In one embodiment, the Android native container base 6011 corresponding to the Android operating system provides Android native container standard capability APIs, and the iOS native container base 6012 corresponding to the iOS operating system provides iOS native container standard capability APIs. The Android native container standard capability APIs and the iOS native container standard capability APIs are unified native container standard capability APIs. The unified native container standard capability APIs include, but are not limited to: routing, permission and privacy management, lifecycle management, container stack management, template management, service management, event message management, application context or crash, exception analysis, performance analysis or instrumentation statistics components. The basic components are assembled through service registration-based building blocks to output capabilities to the upper-layer container, solving the problems of businesses having nowhere to find underlying capabilities and having to repeatedly develop a large amount of middleware.

[0091] In one embodiment, the H5 container base 6021, Flutter container base 6022, Rn container base 6023, and mini-program container base 6024 are integrated based on the Android native container standard capability API and the iOS native container standard capability API, and provide H5 container API, Flutter container API, Rn container API, and mini-program container API. The H5 container API, Flutter container API, Rn container API, and mini-program container API support different technology stacks. For example, the H5 container API and mini-program container API include, but are not limited to: degradation, bridging, components, etc.; the Flutter container API and Rn container API include, but are not limited to: routing, containers, channels, etc.

[0092] In the above embodiments, developers on each end develop applications based on the end container API, avoiding the problem of having to bridge the required native capabilities themselves. This enables developers to write code once and submit it for integration to multiple platforms and applications without having to write a lot of adaptation code to adapt to different platforms and different apps. Application administrators can view and manage all technology stack business modules under the application and manage integration in a unified system, reducing communication and integration testing work with developers on each end. Moreover, mobile capabilities are standardized, and the basic components of the mobile end are unified, such as crash, performance, anomaly analysis, and event tracking statistics. The basic components are assembled through service registration and output capabilities to the upper-layer container, which enables component reuse and eliminates the need for a lot of redundant middleware development.

[0093] The development framework platform can be applied to terminal devices. The network is used as a medium to provide a communication link between the terminal device and the server, and it can be a wired network or a wireless network.

[0094] Optionally, the wireless or wired networks described above use standard communications technologies and / or protocols. The network typically connects to the Internet but can also include hardwired and / or wireless networks that are wired / wireless, duplex, simplex, half-duplex, etc. The network can be any combination of networks, including but not limited to local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), mobile, wired or wireless networks, private networks or virtual private networks (VPNs), any combination thereof, etc. In some embodiments, data exchanged over the one or more networks is represented using technologies and / or formats including, but not limited to, hypertext markup language (HTML), extensible markup language (XML), etc. In addition, all or some links can be encrypted using conventional encryption technologies, such as, but not limited to, secure socket layer (SSL), transport layer security (TLS), virtual private networks (VPNs), Internet Protocol security (IPsec), etc. In other embodiments, custom and / or proprietary data communications technologies and / or formats can be employed.

[0095] The terminal device can be various electronic devices, including but not limited to a smart phone, a tablet computer, a laptop computer, a desktop computer, etc.

[0096] Optionally, the application clients installed in different terminal devices are the same, or are clients of the same type of application based on different operating systems. Depending on the terminal platform, the specific form of the application client can also be different, for example, the application client can be a mobile phone client, a PC client, etc.

[0097] The server can be a server that provides various services, such as a background management server that provides support for the device operated by the user using the terminal device. The background management server can analyze and process received request data, etc., and feed back the processing result to the terminal device.

[0098] Optionally, the server can be a standalone physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and basic cloud computing services such as big data and artificial intelligence platforms. The terminal can be a smart phone, a tablet computer, a notebook computer, a desktop computer, etc., but is not limited thereto. The terminal and the server can be connected directly or indirectly through wired or wireless communication, which is not limited in the present application.

[0099] According to actual needs, there can be any number of terminal devices, networks, and servers. The present disclosure embodiments do not limit this.

[0100] Based on the same inventive concept, the present disclosure embodiments also provide a multi-platform multi-application adaptation device, as follows. Since the principles of the device embodiments for solving problems are similar to the above-mentioned method embodiments, the implementation of the device embodiments can be referred to the implementation of the above-mentioned method embodiments, and the repeated parts will not be described here.

[0101] Figure 7 A schematic diagram of a multi-platform multi-application adaptation device in the present disclosure embodiments is shown, as shown in the figure, the multi-platform multi-application adaptation device 7 includes: a Bundle project package generation module 701, an application merging module 702; Figure 7

[0102] The Bundle project package generation module 701 creates micro-applications based on the development of applications by the end container API, and generates a Bundle project package;

[0103] The application merging module 702 merges the Bundle project package through the Portal project to generate an application.

[0104] In one embodiment, the native container foundation corresponding to different operating systems provides a unified native container standard capability application programming interface API, the end container foundation is integrated based on the native container standard capability API, and the corresponding end container API is provided, and the application is developed based on the end container API.

[0105] ​In the above embodiments, each native platform and each app integrates a container base, and the adaptation work has been done in the container base framework. After the business code is developed by each end developer, a large amount of adaptation code no longer needs to be written, and a large amount of communication and adaptation agreement between the end developer and the app manager no longer needs to be performed. Standard API protocols are unified, and once writing can be implemented for multiple platforms and multiple applications. A large number of basic components are deposited through a service registration system to avoid a large amount of repeated development of middleware.

[0106] Based on the same inventive concept, the embodiments of the present disclosure also provide a multi-platform and multi-application adaptation system, as follows. Since the principles of the embodiments of the system for solving the problem are similar to the above-mentioned method embodiments, the implementation of the system embodiments can be referred to the implementation of the above-mentioned method embodiments, and the repeated parts will not be described again.

[0107] Figure 8 A schematic diagram of a multi-platform and multi-application adaptation system in the embodiments of the present disclosure is shown, as shown in the figure, the multi-platform and multi-application adaptation system includes: an H5 micro application 801, a Flutter micro application 802, an Rn micro application 803, a small program micro application 804, an end container base 805, a native container base 806, a first IOS application 807, a second IOS application 808, a first Android application 809, and a second Android application 810. Figure 8

[0108] The end container base 805 includes: an H5 end container base 805, a Flutter end container base 805, an Rn end container base 805, and a small program end container base 805. The end container base 805 provides H5 end container API, Flutter end container API, Rn end container API, and small program end container API. The H5 end container API, the Flutter end container API, the Rn end container API, and the small program end container API.

[0109] The H5 developer develops the H5 micro application 801 through the H5 end container API, the Flutter developer develops the Flutter micro application 802 through the Flutter end container API, the Rn developer develops the Rn micro application 803 through the Rn end container API, and the small program developer develops the small program micro application 804 through the small program end container API.

[0110] ​The end container base 805 is integrated based on a native container standard capability API set, each native container base 806 provides a unified native container standard capability API, and different native container bases 806 correspond to different operating systems; for example, a first Android application 809 and a second Android application 810 are generated based on an Android native container standard capability API; a first IOS application 807 and a second IOS application 808 are generated based on an IOS native container standard capability API, and an app manager manages the first Android application 809, the second Android application 810, the first IOS application 807, and the second IOS application 808.

[0111] In the above embodiment, the container framework base shields the differences between platforms and ends, provides host app and monitoring, routing, and other container base capabilities upward, front-end developers do not change the technology stack, can use existing mobile end basic capabilities, unified API standards, reduce the development of adaptive protocols, and can reuse basic components.

[0112] Those skilled in the art can understand that various aspects of the present disclosure can be implemented as a system, a method, or a program product. Therefore, various aspects of the present disclosure can be embodied as a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, which can be collectively referred to as "circuitry", "module" or "system" here.

[0113] The electronic device 900 according to this embodiment of the present disclosure will be described below with reference to Figure 9 Figure 9 The electronic device 900 shown is merely an example and should not impose any limitations on the functions and use range of the embodiments of the present disclosure.

[0114] As shown in Figure 9 The electronic device 900 is in the form of a general computing device. The components of the electronic device 900 can include, but are not limited to, the at least one processing unit 910 described above, the at least one storage unit 920 described above, and a bus 930 connecting different system components, including the storage unit 920 and the processing unit 910.

[0115] The storage unit stores program code that can be executed by the processing unit 910, so that the processing unit 910 performs the steps described in the "Exemplary Method" section above according to various exemplary embodiments of the present disclosure.

[0116] ​For example, the processing unit 910 can perform the following steps in the above method embodiment: providing native container bases corresponding to different operating systems, each native container base providing a unified native container standard capability application programming interface (API); providing various end container bases, each end container base integrating based on the native container standard capability API and providing corresponding end container APIs; developing applications based on the end container APIs, thereby achieving multi-platform and multi-application adaptation.

[0117] For example, the processing unit 910 can execute the following steps in the above method embodiment: the Android native container base corresponding to the Android operating system provides Android native container standard capability APIs, and the iOS native container base corresponding to the iOS operating system provides iOS native container standard capability APIs; the Android native container standard capability APIs and the iOS native container standard capability APIs are unified native container standard capability APIs, which include, but are not limited to: routing, permission and privacy management, lifecycle management, container stack management, template management, service management, event message management, application context or crash, exception analysis, performance analysis or instrumentation statistics components;

[0118] The H5 container platform, Flutter container platform, Rn container platform, and mini-program container platform are integrated based on the standard API capabilities of Android native containers and iOS native containers. They provide H5 container API, Flutter container API, Rn container API, and mini-program container API, supporting different technology stacks.

[0119] Storage unit 920 may include readable media in the form of volatile storage units, such as random access memory (RAM) 9201 and / or cache memory 9202, and may further include read-only memory (ROM) 9203.

[0120] Storage unit 920 may also include a program / utility 9204 having a set (at least one) program module 9205, such program module 9205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0121] Bus 930 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0122] The electronic device 900 can also communicate with one or more external devices 940 such as a keyboard or pointing device, a Bluetooth device, or a device that enables a user to interact with the electronic device 900. Additionally, the electronic device 900 can further communicate with one or more devices that enable a user to interact with the electronic device 900 or with one or more devices that enable the electronic device 900 to communicate with one or more other computing devices. Such communication can occur via an input / output (I / O) interface 950. Still yet, the electronic device 900 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), or a public network such as the Internet, via a network adapter 960. As depicted, the network adapter 960 is in communication with the other components of the electronic device 900 through the bus 930. It should be appreciated that various other peripherals can be connected to the electronic device 900, such as a printer, scanner, and the like. It is also contemplated that the electronic device 900 can have additional features or functionality, and / or can be a part of a group of electronic devices that cooperate, such as connected over a computer network, such as the Internet, a local area network, a wide area network and / or a wireless network such as a cellular telephone network, an IEEE 802.11 wireless network, and / or a IEEE 802.16 wireless network.

[0123] Through the above description of the embodiments, those skilled in the art can easily understand that the example embodiments described herein can be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solutions according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a U disk, a mobile hard disk, or the like) or a network, and includes a number of instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to perform the methods according to the embodiments of the present disclosure.

[0124] In the example embodiments of the present disclosure, a computer readable storage medium is also provided, which can be a readable signal medium or a readable storage medium. A program product capable of implementing the above method of the present disclosure is stored thereon. In some possible embodiments, various aspects of the present disclosure can also be implemented in the form of a program product, which includes program codes for causing a terminal device to perform the steps according to various example embodiments of the present disclosure described in the above "example method" section of the specification when the program product is run on the terminal device.

[0125] For example, the program product in the embodiments of the present disclosure, when executed by a processor, implements the method of the following steps: creating a micro application based on an end container API development application to generate a Bundle project package; uploading the Bundle project package to a product warehouse; when receiving a request for integrating the micro application into an application, merging the Bundle project package in the product warehouse through a Portal project to generate the application.

[0126] For example, the program product in the embodiments of the present disclosure is executed by the processor to implement the method of the following steps: starting a micro application to enter a start page; obtaining configuration information of a user, the configuration information including: program identification and key information; starting a target micro service application according to the configuration information, and generating a corresponding service instance; obtaining user instruction information, and managing the target micro service application through a container manager.

[0127] For example, the program product in the embodiments of the present disclosure is executed by the processor to implement the method of the following steps: providing a native container base corresponding to different operating systems, each native container base providing a unified native container standard capability application programming interface (API); providing each end container base, the end container base being integrated based on the native container standard capability API, and providing a corresponding end container API; developing an application based on the end container API, thereby realizing the adaptation of multiple platforms and multiple applications.

[0128] More specific examples of the computer readable storage medium in the present disclosure can include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0129] In the present disclosure, the computer readable storage medium can include a data signal carried in a baseband or as a part of a carrier wave, in which readable program codes are borne. Such a propagated data signal can take multiple forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the foregoing. The readable signal medium can also be any readable medium that is not a storage medium, which can send, propagate or transmit programs for use by or in connection with an instruction execution system, apparatus or device.

[0130] Optionally, the program codes contained on the computer readable storage medium can be transmitted by any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0131] In particular embodiments, the program code utilized by the program code instructions can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++, or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computing device, partly on the user's computing device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server. In the latter scenario, the remote computing device can be connected to the user's computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computing device, such as through the Internet using an Internet Service Provider. The application programming interface (API) server can be used to facilitate the communication between the client and the server.

[0132] It should be noted that, although several modules or units of the devices for action execution are mentioned in the foregoing detailed description, such division is not mandatory. Indeed, features and functionalities of two or more modules or units described above can be embodied in one module or unit according to embodiments of the present disclosure. Conversely, features and functionalities of one module or unit described above can be further divided into multiple modules or units.

[0133] Furthermore, although the various steps of the methods in the present disclosure are described in a particular order in the drawings, this does not require or imply that the steps must be performed in that particular order, or that all of the steps must be performed to achieve the desired result. Additionally or alternatively, certain steps can be omitted, multiple steps can be combined into one step, one step can be split into multiple steps, etc.

[0134] From the above description of the embodiments, those skilled in the art will readily perceive that the example embodiments described herein can be implemented by software and / or by hardware and / or by a combination of software and hardware. Accordingly, the technical solutions according to the embodiments of the present disclosure can be embodied in the form of a software product. The software product can be stored in a non-volatile storage medium, such as a CD-ROM, a USB flash drive, a mobile hard disk, or the like, or on a network, and includes a number of instructions for causing a computing device (such as a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the methods according to the embodiments of the present disclosure.

[0135] Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the features disclosed herein. It is intended that the disclosure be construed as including any patents, patent applications, publications, publications, or other disclosure of complementary subject matter that is within the scope of the disclosure. It is intended that the specification and examples be considered exemplary only, with the true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A multi-platform multi-application adaptation method, characterized by, The application relates to a multi-platform multi-application adaptation device and method. Providing native container bases corresponding to different operating systems, each of the native container bases providing a unified native container standard capability application programming interface API; the native container standard capability application programming interface API is a defined unified standard interface layer, and different implementation codes for different operating systems provide a unified standard interface to a cross-terminal container in an upper layer, so that the cross-terminal container in the upper layer directly calls the unified standard interface. Providing various terminal container bases, the terminal container bases being integrated based on the native container standard capability application programming interface API and providing corresponding terminal container APIs. Developing applications based on the terminal container APIs, so that multi-platform multi-application adaptation is realized.

2. The multi-platform multi-application adaptation method of claim 1, wherein, The terminal container API includes routing, containers, channels, degradation, bridges or components.

3. The multi-platform multi-application adaptation method of claim 1, wherein, The native container standard capability application programming interface API includes routing, permission privacy management, life cycle management, container stack management, template management, service management, event message management or application context.

4. The multi-platform multi-application adaptation method of claim 3, wherein, The native container standard capability application programming interface API further includes a data reporting component, and the data reporting component includes a crash, exception analysis, performance analysis or burying point statistics component.

5. The multi-platform multi-application adaptation method of claim 1, wherein, The terminal container base includes a Flutter, RN, H5 or applet corresponding container base; and the operating system includes Android, iOS and Hongmeng.

6. The multi-platform multi-application adaptation method of claim 1, wherein, The developing applications based on the terminal container APIs, so that multi-platform multi-application adaptation is realized includes: Developing micro-applications based on the terminal container APIs to generate a Bundle project package; Merging the Bundle project package through a Portal project to generate an application.

7. The multi-platform multi-application adaptation method of claim 6, wherein, Further including: Entering a start page by starting a micro-application; Obtaining configuration information of a user, the configuration information including program identification and key information; Starting a target micro-service application according to the configuration information and generating a corresponding service instance.

8. The multi-platform multi-application adaptation method of claim 7, wherein, Further including: Obtaining user instruction information and managing the target micro-service application through a container manager.

9. A multi-platform multi-application adaptation apparatus, characterized by comprising: The multi-platform multi-application adaptation device is used for: Providing native container bases corresponding to different operating systems, each of the native container bases providing a unified native container standard capability application programming interface API; the native container standard capability application programming interface API is a defined unified standard interface layer, and different implementation codes for different operating systems provide a unified standard interface to a cross-terminal container in an upper layer, so that the cross-terminal container in the upper layer directly calls the unified standard interface. Providing various terminal container bases, the terminal container bases being integrated based on the native container standard capability application programming interface API and providing corresponding terminal container APIs. Developing applications based on the terminal container APIs, so that multi-platform multi-application adaptation is realized.

10. The multi-platform multi-application adaptation apparatus according to claim 9, wherein Further including: A Bundle project package generation module that develops micro-applications based on terminal container APIs to generate a Bundle project package; An application merging module that merges the Bundle project package through a Portal project to generate an application.

11. A development framework platform, characterized by, Further including: A native container base corresponding to different operating systems, each of the native container bases providing a uniform native container standard capability application programming interface API; the native container standard capability application programming interface API is a defined uniform standard interface layer, and different implementation codes for different operating systems provide a uniform standard interface to an upper cross-end container, so that the upper cross-end container directly calls the uniform standard interface; One or more end container bases integrated based on the native container standard capability application programming interface API, and providing a corresponding end container API, so as to develop an application based on the end container API, thereby realizing multi-platform and multi-application adaptation.

12. An electronic device, comprising: Comprise: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the multi-platform and multi-application adaptation method of any one of claims 1-8 by executing the executable instructions.

13. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to realize the multi-platform and multi-application adaptation method of any one of claims 1-8.

Images