Super application building method

Abstract

To provide a super application building method.SOLUTION: A super application building method includes selecting a master application and one or more slave applications through an application development tool, and establishing, by the master application, an information transmission manager and a background application programming interface executor. The method includes storing, by the information transmission manager, data content to be transmitted by applications in the super application, and causing the applications to read the data content through the information transmission manager. The method includes invoking, by the background application programming interface executor, the details of background application programming interface execution master files of the other applications and executing them on the background of the master application. The plurality of applications can thus be integrated into one super application.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a method for building an application (APP), and more particularly to a method for building a super application (Super APP). [Background technology]

[0002] A super app is a single application that provides multiple services, meets multiple user needs, and provides a one-stop solution. A super app is established by integrating various functions into a single app. However, at present, it is not possible to create a super app by simply importing a combination of existing apps. Current app development methods make it difficult to directly modularize an app and integrate it into other app projects. Instead, developers must either independently develop modules or use functions provided by JavaScript tool libraries (e.g., libraries). Furthermore, integrating third-party services can lead to reliability and security issues, and third-party application programming interfaces (APIs) may be subject to change. Summary of the Invention [Problem to be solved by the invention]

[0003] The present invention provides a method for building a super app that enables developers to easily build and manage multiple apps on a single platform while ensuring high app interoperability. [Means for solving the problem]

[0004] A method for constructing a super APP of the present invention is suitable for execution using a processor, and the method includes the steps of establishing a first super APP through an APP development tool, the first super APP including a plurality of first APPs, each of which includes a master APP and at least one slave APP. The first super APP establishment step includes selecting a master APP through the APP development tool, establishing an information transmission manager and a background Application Programming Interface (API) executor in the master APP in response to the selection of the master APP, selecting at least one slave APP through the APP development tool when the APP development tool selects the master APP, establishing a transmission path between the master APP and each slave APP through the information transmission manager, and establishing a call association between the master APP and a background API execution master file of each slave APP through the background API executor.

[0005] In one embodiment of the present invention, the step of establishing a transmission path between the master APP and each slave APP through the information transmission manager includes establishing a directory path corresponding to each slave APP in the master APP through the information transmission manager, and storing each slave APP in the corresponding directory path, so that the information transmission manager stores data content transmitted from the master APP and each slave APP respectively through the directory path, and the master APP and each slave APP can read the data content stored through the directory path.

[0006] In one embodiment of the present invention, when an APP development tool is running a master APP, after selecting a slave APP through the APP development tool, an object corresponding to each slave APP can be added to a specified page of the first super APP and associated with the directory path of the corresponding slave APP.

[0007] In one embodiment of the present invention, when the APP development tool selects a master APP, the method further includes selecting a second super APP through the APP development tool, wherein the second super APP includes multiple second APPs, one of which is the master APP of the second super APP, and importing the second super APP into the first super APP and making the second APPs included in the second super APP slave APPs of the first super APP, and this step also includes establishing a transmission path between the master APP of the first super APP and each second APP of the second super APP through the information transmission manager of the first super APP, and establishing a call association between the master APP of the first super APP and the background API execution master file of each second APP of the second super APP through the background API executor of the first super APP.

[0008] In one embodiment of the present invention, a background API executor is used to call the background API execution master file of each slave APP.

[0009] In one embodiment of the present invention, the step of establishing a transmission path between the master APP of the first super APP and each second APP of the second super APP through the information transmission manager of the first super APP includes establishing a directory path corresponding to each second APP in the master APP of the first super APP through the information transmission manager, and storing each second APP in the corresponding directory path.

[0010] In one embodiment of the present invention, a background API executor is used to call the background API execution master file of each slave APP.

[0011] In one embodiment of the present invention, the method for building a super app further includes adding backend management functions to the first super app through an app development tool. [Effects of the Invention]

[0012] Based on the above, when designing a super APP, an existing APP can be combined with a new APP to form a completely new super APP, and the APPs in the super APP can transfer data between each other or call API functions. An existing super APP can also be expanded into a new super APP by adding one or more new APPs. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a schematic diagram illustrating the architecture of an application according to an embodiment of the present invention. [Figure 2] FIG. 1 is a schematic diagram of the architecture of a super app according to one embodiment of the present invention. [Figure 3] 1 is a flowchart of a method for building a super app according to an embodiment of the present invention. [Figure 4] FIG. 2 is an architecture schematic diagram of a transmission path in a super APP according to an embodiment of the present invention; [Figure 5] FIG. 2 is an architecture schematic diagram of call association in a super APP according to one embodiment of the present invention; [Figure 6] FIG. 1 is an architectural schematic diagram of integrating multiple super APPs according to one embodiment of the present invention. [Figure 7A] 1 is a schematic diagram of an interface of an APP development tool according to one embodiment of the present invention. [Figure 7B] 1 is a schematic diagram of an interface of an APP development tool according to one embodiment of the present invention. [Figure 7C] 1 is a schematic diagram of an interface of an APP development tool according to one embodiment of the present invention. [Figure 8] 1 is a schematic diagram of a member page of a super APP according to an embodiment of the present invention; [Figure 9]1 is a schematic diagram of an APP list page of a super APP according to an embodiment of the present invention; DETAILED DESCRIPTION OF THE INVENTION

[0014] In the following embodiments, the method for building a super app can be implemented using any electronic device with computing capabilities, such as a personal computer, a notebook computer, a server, etc. The electronic device includes at least a processor and a storage, and the processor is connected to the storage.

[0015] The processor may be implemented by a Central Processing Unit (CPU), a Physics Processing Unit (PPU), a programmable microprocessor, an embedded control chip, or a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or other similar device.

[0016] The storage may be implemented using any type of fixed or removable random access memory (RAM), read-only memory (ROM), flash memory, hard disk, or other similar device, or a combination thereof. The storage may include one or more program code fragments, which, after being installed, are executed by a processor to implement a method for constructing a super application (Super APP).

[0017] FIG. 1 is a schematic diagram of an application architecture according to an embodiment of the present invention. Referring to FIG. 1, in one embodiment, an application (APP) includes a startup file 110, a background application programming interface (API) execution master file 120, and a program logic master file 130. For example, the startup file 110 is an “index.html” file that launches the APP and is used to set parameters. The program logic master file 130 is a functional file that is actually executed and consists of one or more pages, each of which contains functions (e.g., API functions) and variables. The program logic master file 130 is, for example, a “.vue” or “.js” file. The background API execution master file 120 is a main file used to enable API functions to be executed in the background. The background API execution master file 220 is, for example, a “.vue” or “.js” file. In one embodiment, the background API execution master file 120 can be an API function, such as a “Web Work,” that can be executed independently in the background without affecting the original HTML page.

[0018] A super app can import multiple apps to provide services, and each app can be regarded as a website service established on a mobile phone. For example, a super app can provide services such as communication, e-commerce, shopping, ordering, travel, ride-hailing, and remittance. Each service is provided by an app.

[0019] FIG. 2 is a schematic diagram of the architecture of a super app according to an embodiment of the present invention. In this embodiment, the super app 20 is established through an application (app) development tool. Referring to FIG. 2, the super app 20 is composed of multiple apps, one of which is a master app 200 and the other apps are slave apps 100. When the super app 20 starts, the master app 200 is the first app to start. The architecture of the slave app 100 is the same as that shown in FIG. 1. The architecture of the master app 200 is similar to that of the slave app 100, and includes a startup file 210, a background API execution master file 220, and a program logic master file 230. It also includes an information transmission manager 240 and a background API executor 250. The information transmission manager 240 is a web storage such as "localStorage" or "sessionStorage." The information transmission manager 240 is responsible for storing data content transmitted by each app in the super app. Furthermore, each app can read data content transmitted from other apps through the information transmission manager 240. Background API executor 250 is, for example, a function, program code fragment, etc. that allows a master APP to call a slave APP to run in the background.

[0020] To improve security, the information transmission manager 240 may further perform encryption and decryption operations on the received data content.

[0021] The following example further describes each step of establishing the super APP 20. Figure 3 is a flowchart of a method for building a super APP according to one embodiment of the present invention. Referring to Figures 2 and 3, in step S305, a master APP 200 is selected through an APP development tool. For example, in one embodiment, a user can select one of the APP projects as the master APP 200 through the APP development tool.

[0022] Next, in step S310, in response to the selection of the master APP, an information transmission manager 240 and a background API executor 250 are established in the master APP 200. In step S315, in a situation where the master APP 200 has been selected in the APP development tool, at least one slave APP 100 is selected through the APP development tool.

[0023] In step S320, a transmission path between the master APP 200 and each slave APP 100 is established through the information transmission manager 240. Specifically, a directory path corresponding to each slave APP 100 is established in the master APP 200 through the information transmission manager 240, and each slave APP 100 is stored in the corresponding directory path. The information transmission manager 240 can store data content transmitted by the master APP 200 and each slave APP 100 through the directory path, and allows the master APP 200 and each slave APP 100 to read the data content stored in the directory path. Each slave APP 100 is located in the corresponding directory path of the master APP 200. Therefore, by accessing the directory path of the startup file 210, the corresponding slave APP 100 can be executed.

[0024] For example, if the location path of the master APP 200 is "file: / / xxx / www / ," the path corresponding to the startup file 210 of the master APP 200 (e.g., the file "index.html") is "file: / / xxx / www / index.html." When the super APP 20 is started, the startup file 210 of the master APP 200 is executed from "file: / / xxx / www / index.html." Furthermore, if the corresponding directory path is set with the name "APP1" of the slave APP 100, the directory path of the slave APP 100 is set as "file: / / xxx / www / APP1 / " under the corresponding location path of the master APP 200, and the directory path corresponding to the startup file 110 of the slave APP 100 (e.g., the file "index.html") is "file: / / xxx / www / APP1 / index.html." The master APP 200 can execute the startup file 110 of the slave APP 100 from "file: / / xxx / www / APP1 / index.html."

[0025] FIG. 4 is a schematic diagram of a transmission path architecture in a super APP according to an embodiment of the present invention. Referring to FIG. 4, this embodiment uses three slave APPs (100-1, 100-2, and 100-3) as an example for illustrative purposes, but is not limited thereto. Slave APP 100-1 includes a startup file 110-1, a background API execution master file 120-1, and a program logic master file 130-1. Slave APP 100-2 includes a startup file 110-2, a background API execution master file 120-2, and a program logic master file 130-2. Slave APP 100-3 includes a startup file 110-3, a background API execution master file 120-3, and a program logic master file 130-3. The master APP 200 establishes directory paths 411-1, 411-2, and 411-3 corresponding to the slave APPs 100-1, 100-2, and 100-3 through the information transmission manager 240. The slave APP 100-1 is stored in the directory path 411-1, the slave APP 100-2 is stored in the directory path 411-2, and the slave APP 100-3 is stored in the directory path 411-3.

[0026] 3, in step S325, a call association is established between the master APP 200 and the background API execution master file 120 of each slave APP 100 (e.g., slave APPs 100-1, 100-2, and 100-3) through the background API executor 250. Thus, the master APP 200 can call the background API execution master file 120 of the slave APP 100 through the background API executor 250 as needed.

[0027] 5 is a schematic architecture diagram of a call association in a super APP according to one embodiment of the present invention. Referring to FIG. 5, this embodiment uses three slave APPs 100-1, 100-2, and 100-3 (which may be collectively referred to as the slave APP 100) as an example for illustrative purposes, but is not limited thereto. As shown in FIG. 5, the background API executor 250 of the master APP 200 can call the background API execution master files 120-1, 120-3, and 120-4 (which may be collectively referred to as the background API execution master file 120) of the slave APPs 100-1, 100-2, and 100-3, respectively.

[0028] When the super APP 20 starts up, it executes the startup file 210 of the master APP 200, and the startup file 210 first executes the program logic master file 230, and if it needs to execute at least one slave APP 100 in the background (e.g., at least one of the slave APPs 100-1, 100-2, and 100-3), it can call the background API execution master file 120 of one or more slave APPs 100 that it wants to execute in the background through the background API executor 250.

[0029] Furthermore, the super APP 20 can not only be combined with one or more APPs, but also with other super APPs. When the super APP 20 is combined with another super APP, the combined super APP is regarded as a normal APP, and the information transmission manager and background API executor of its own master APP are canceled (for example, the information transmission manager and background API executor of the master APP of the combined super APP are disabled), and the control is changed to that of the super APP 20. The following example illustrates the architecture of importing another super APP into the super APP 20.

[0030] 6 is a schematic architecture diagram of integrating multiple super APPs according to one embodiment of the present invention. Referring to FIG. 6, in this embodiment, a super APP 600 (second super APP) is selected through an APP development tool. The super APP 600 includes multiple APPs (two APPs are used as an example, but not limited to, one of which is a master APP 601 and the other is a slave APP 602). Next, the super APP 600 is imported into the super APP 20 (first super APP), and the second APPs (master APP 601 and slave APP 602) included in the super APP 600 become slave APPs 610 and 620 of the super APP 20.

[0031] In other words, when Super APP600 is imported into Super APP20, the original information transmission manager and background API executor of Master APP601 (corresponding to Slave APP610) of Super APP600 are disabled and no longer operate, and are diverted to use Information Transmission Manager 240 and Background API Executor 250 of Super APP20 to control Slave APP610 and Slave APP620.

[0032] Specifically, the information transmission manager 240 of the super APP 20 establishes a transmission path between the master APP 200 of the super APP 20 and each second APP (master APP 601, slave APP 602) of the super APP 600. As shown in Fig. 6, the master APP 200 establishes directory paths 611 and 621 corresponding to the master APP 601 and slave APP 602 of the super APP 600, respectively, through the information transmission manager 240, and stores the master APP 601 in the directory path 611 and the slave APP 602 in the directory path 621. Therefore, the master APP 601 and slave APP 602 of the super APP 600 become slave APP 610 and APP 620 of the super APP 20, respectively. The slave APP 610 includes a startup file 610-1, a background API execution master file 610-2, and a program logic master file 610-3. The slave APP 620 includes a startup file 620-1, a background API execution master file 620-2, and a program logic master file 620-3.

[0033] Furthermore, the background API executor 250 of the super APP 20 establishes a calling association between the master APP 200 of the super APP 20 and the background API execution master files 610-2, 620-2 of the slave APPs 610, 620 of the super APP 600. Thus, the master APP 200 can execute at least one of the slave APPs 610 and 620 in the background through the background API executor 250 as needed.

[0034] 7A-7C are interface schematic diagrams of an app development tool according to one embodiment of the present invention. In this embodiment, the app development tool 700 is, for example, a no-code cross-app web development tool. As shown in FIG. 7A, in the project menu of the app development tool 700, a "Shopping App Project" can be selected as the master app. Next, as shown in FIG. 7B, a project is selected as the slave app in the app list of the app development tool 700. Here, the projects listed in the app list are already established apps. After selecting the slave app, the name "Shopping App Project" corresponding to the master app and the names "productAdmin" and "shopping" corresponding to the slave apps are displayed in the file list, as shown in FIG. 7C.

[0035] A login function is added to the member page, and the backend management function is provided after successfully logging in to the member account. In one embodiment, the backend management function can be added directly to a page of the master APP (e.g., the member page). In another embodiment, the backend management function can be implemented in the form of a single APP (backend APP), and the backend APP can be a slave APP in the super APP.

[0036] 8 is a schematic diagram of a member page of a super APP according to an embodiment of the present invention. Referring to FIG. 8, when a user logs in to a member account of the super APP, a member page 800 is displayed. The member page includes a welcome message 801, such as "Welcome: Andy," and buttons 802 corresponding to back-end management functions.

[0037] Furthermore, an object corresponding to each slave APP can be added to a designated page of the super APP 20 through the APP development tool and associated with the directory path of the corresponding slave APP. The object can be, for example, an icon, a function option, or a button. During use of the super APP 20, an object such as an icon, a function option, or a button on a designated page can trigger the execution of the corresponding slave APP. This allows for more flexible use of the super APP, and allows the user to determine which slave APP of the super APP to execute as needed when executing the master APP of the super APP. For example, FIG. 9 is a schematic diagram of an APP list page of a super APP according to an embodiment of the present invention. Referring to FIG. 9, APP list page 900 displays icons 901, 902, and 903 corresponding to three APPs. Note that this is an example and is not limiting.

[0038] Alternatively, in other embodiments, the execution order of the slave APPs may be set in advance during the construction stage of the super APP, without providing objects such as icons, function options or buttons.

[0039] In summary, the super app building method of the present invention allows developers to easily build and manage multiple apps on a single platform while ensuring high app interoperability. During the development phase of the super app, the super app can be easily built by simply importing existing apps. Furthermore, new functions can be integrated into the super app by establishing new apps as needed. [Industrial Applicability]

[0040] The super APP construction method of the present invention can meet the diverse needs of users and integrate multiple services such as communications, e-commerce, shopping, ordering, travel, car dispatch, and remittance, thereby realizing one-stop service. [Explanation of symbols]

[0041] 100, 100‐1, 100‐2, 100‐3, 602, 610, 620: Slave APP 110, 110‐1, 110‐2, 110‐3, 210, 610‐1, 620‐1: Startup files 120, 120‐1, 120‐2, 120‐3, 220, 610‐2, 620‐2: Background API execution master file 130, 130‐1, 130‐2, 130‐3, 230, 610‐3, 620‐3: Program logic master file 20.600:Super APP 200, 601: Master APP 240: Information Transmission Manager 250: Background API Executor 411‐1, 411‐2, 411‐3, 611, 621: Directory path 700: APP development tools 800: Member page 801: Welcome Word 802: Button 900:APP list page 901, 902, 903: Icon S305~S325: Step

Claims

1. Suitable for execution using a processor, establishing a first super app through an app development tool, wherein the first super app includes a plurality of first apps, and the plurality of first apps include a master app and at least one slave app; The step of establishing the first super app includes: selecting the master app through the app development tool; In response to the master app being selected, establishing an information transmission manager and a background application programming interface executor in the master app; selecting the at least one slave application through the application development tool when the application development tool has selected the master application; establishing a transmission path between the master application and each of the slave applications through the information transmission manager; and establishing a calling association between the master app and a background application programming interface execution master file of each of the slave apps through the background application programming interface executor.

2. establishing a transmission path between the master application and each of the slave applications through the information transmission manager; establishing a directory path corresponding to each of the slave applications in the master application through the information transmission manager; 2. The method of claim 1, further comprising: storing each of the slave apps in a corresponding directory path, causing the information transmission manager to store data content transmitted from the master app and each of the slave apps via the directory path, and allowing the master app and each of the slave apps to read the data content stored by the directory path.

3. 3. The method of claim 2, further comprising: after selecting the at least one slave app through the application development tool while the application development tool is launching the master app, adding objects corresponding to each of the slave apps to a designated page of the first super app and associating the objects with the directory paths of each of the corresponding slave apps.

4. When the application development tool selects the master application, Selecting a second super app through the app development tool, wherein the second super app includes a plurality of second apps, one of the plurality of second apps being a master app of the second super app; and importing the second super app into the first super app and setting the second apps included in the second super app as slave apps of the first super app; The step of importing the second super application into the first super application and setting the second applications included in the second super application as slave applications of the first super application includes: Establishing a transmission path between the master app of the first super app and each of the second apps of the second super app through the information transmission manager of the first super app; and and establishing a calling association between the master app of the first super app and a background application programming interface execution master file of each of the plurality of second apps of the second super app through the background application programming interface executor of the first super app.

5. establishing a transmission path between the master application of the first super application and each of the plurality of second applications of the second super application through the information transmission manager of the first super application, establishing a directory path corresponding to each of the plurality of second applications in the master application of the first super application through the information transmission manager; and storing each of the plurality of second apps in a corresponding one of the directory paths.

6. The method of claim 1 , wherein the background application programming interface executor is used to invoke the background application programming interface execution master file of each of the slave apps.

7. The method of claim 1 , further comprising adding backend management functionality to the first super app through the app development tool.

Images