Application development method and device

Abstract

The present disclosure is about an application development method and device. It relates to the field of software development and solves the problem that the quick application development solution cannot realize the quick application scenario. The method includes: receiving an editing request for a negative one-screen quick application; starting the development environment of the requested quick application on the client; receiving an editing instruction in the development environment of the requested quick application; editing and modifying the quick application according to the editing instruction to generate a personalized quick application. It realizes the development and use of quick applications with high flexibility and high adaptability.

Description

Technical Field

[0001] The present disclosure relates to the field of software development, and in particular to an application development method and device. Background Art

[0002] Quick apps are a new type of application based on mobile phone hardware platforms. They do not require installation and are ready to use. They also have native application experience (performance, system integration, interaction, etc.). At the same time, quick apps have achieved standardization among mobile phone manufacturers in terms of development specifications, capability access, developer services, etc. since their inception, greatly reducing the adaptation costs of developers.

[0003] Compared with traditional applications, quick applications have the following characteristics:

[0004] Instant: Click and use, users do not need to wait;

[0005] Everywhere: Deeply integrated with the usage scenarios of mobile phones, with entry points everywhere (search, smart assistant, smart recommendation, application market, browser, etc.);

[0006] Efficient: Quasi-front-end development method, high efficiency.

[0007] It should be noted that the quick application corresponds to the native application. Optionally, the application data of the quick application is provided by the background server of the native application. Therefore, the terminal calls the API of the native application of the quick application through the application programming interface (Application Programming Interface, API) of the quick application and obtains the application data through the API of the native application. Among them, the API of the quick application is obtained by encapsulating the API of the native application.

[0008] The front-end design of the quick app draws on and integrates the design ideas of mainstream front-end frameworks (Vue, React, etc.): building applications in a componentized way, using the MVVM design mode with data binding as the core, improving performance with V-DOM, and choosing a concise and clear Vue-like template. At the same time, the layout has been streamlined accordingly. From the perspective of new application forms, mapping native UI, and open capabilities, a set of components and API specifications need to be defined to facilitate the development of this quick development application.

[0009] As a complete application form, quick applications can be deeply integrated with the system, run like native applications, and interact with the system. Quick applications currently have two forms: full-screen independent application form and embedded card form. In the form of independent applications, the user experience is just like that of native applications, with complete life cycle management, page management, routing, etc. Quick applications can parasitize on Android Activities, pages parasitize on Fragments, and instances are managed and controlled through independent background Services. Cards are another form, which are embedded in various corners of the system as an independent local control through embedded SDKs to display dynamic content in a lightweight manner. In terms of security isolation, better security can be achieved through sandbox mechanisms, process isolation, permission control, and combined with support from the operating system layer.

[0010] The negative first screen is an entrance to quick apps. When users operate mobile terminals such as mobile phones, they can swipe to bring up the negative first screen, and perform operations such as quick search, opening quick apps, and browsing recommended quick app information in the quick app list on the negative first screen. The negative first screen can display multiple quick app cards, and the display content and interface layout of each card are fixed. Users have strong personalized needs for quick apps, and quick app cards with a single interface cannot meet user needs. For example, users have specific preferences for interface colors, or want to display certain function buttons and hide certain function buttons. However, general quick app development solutions do not provide interfaces to other developers, and cannot implement quick app scenarios to meet application needs in different scenarios. Summary of the invention

[0011] In order to overcome the problems existing in the related art, the present disclosure provides an application development method and device.

[0012] According to a first aspect of an embodiment of the present disclosure, there is provided an application development method, including:

[0013] Receive an edit request for the negative one screen quick application;

[0014] Start the development environment of the requested quick application on the client;

[0015] In the development environment of the requested quick application, receiving an editing instruction;

[0016] The quick app is edited and modified according to the editing instruction to generate a personalized quick app.

[0017] Preferably, the step of receiving an edit request for the negative one-screen quick application includes:

[0018] An edit request including a Uniform Resource Locator (URL) for the negative one-screen quick application is received.

[0019] Preferably, the step of receiving an editing request for a negative one-screen quick application and starting a development environment for the requested quick application includes:

[0020] According to the editing request, a software development kit (SDK) of the quick app is returned for the user to edit the quick app.

[0021] Preferably, the step of receiving the editing instruction in the development environment of the requested quick application includes:

[0022] According to the editing instructions input through the SDK of the quick app.

[0023] Preferably, the editing instruction at least involves any one or more of the following:

[0024] Modify the navigation bar content, modify the navigation bar position, and customize the icon.

[0025] Preferably, after the step of editing and modifying the quick app according to the editing instruction to generate a personalized quick app, the step further includes:

[0026] The personalized quick application is submitted to the cloud for release through the development environment of the quick application.

[0027] Preferably, before the step of receiving an edit request for the negative one screen quick application, the method further includes:

[0028] The editing permission of at least one quick application in the negative first screen is opened, and a development environment is configured for each quick application for which the editing permission is opened.

[0029] According to a second aspect of an embodiment of the present disclosure, there is provided an application development device, including:

[0030] A request receiving module, used to receive an edit request for the negative one screen quick application;

[0031] The development environment loading module is used to start the development environment of the requested quick application on the client;

[0032] An editing instruction receiving module, used for receiving an editing instruction in the development environment of the requested quick application;

[0033] The application editing and development module is used to edit and modify the quick application according to the editing instruction to generate a personalized quick application.

[0034] Preferably, the request receiving module includes:

[0035] The request receiving unit is used to receive an edit request containing a URL for the negative one-screen quick application.

[0036] Preferably, the development environment loading module includes:

[0037] The development tool providing unit is used to return the SDK of the quick application according to the editing request, so that the user can edit the quick application.

[0038] Preferably, the editing instruction receiving module includes:

[0039] The SDK instruction receiving unit is used to input the editing instruction through the SDK of the quick application.

[0040] Preferably, the device further comprises:

[0041] The application publishing module is used to submit the personalized quick application to the cloud for publishing through the development environment of the quick application.

[0042] Preferably, the device further comprises:

[0043] The development environment configuration module is used to open the editing permission of at least one quick application in the negative one screen, and configure the development environment for each quick application with the opened editing permission.

[0044] According to a third aspect of an embodiment of the present disclosure, there is provided a computer device, including:

[0045] processor;

[0046] a memory for storing processor-executable instructions;

[0047] Wherein, the processor is configured to:

[0048] Receive an edit request for the negative one screen quick application;

[0049] Start the development environment of the requested quick application on the client;

[0050] In the development environment of the requested quick application, receiving an editing instruction;

[0051] The quick app is edited and modified according to the editing instruction to generate a personalized quick app.

[0052] According to a fourth aspect of an embodiment of the present disclosure, a non-transitory computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is enabled to execute an application development method, the method comprising:

[0053] Receive an edit request for the negative one screen quick application;

[0054] Start the development environment of the requested quick application on the client;

[0055] In the development environment of the requested quick application, receiving an editing instruction;

[0056] The quick app is edited and modified according to the editing instruction to generate a personalized quick app.

[0057] The technical solution provided by the embodiments of the present disclosure may include the following beneficial effects: receiving an editing request for a negative one-screen quick application, starting the development environment of the requested quick application on the client, allowing the user to edit the quick application, and then receiving an editing instruction in the development environment of the requested quick application, and then editing and modifying the quick application according to the editing instruction to generate a personalized quick application. By opening up the permissions of quick application development resources, different users can develop and customize personalized quick applications, thereby achieving highly flexible and adaptable quick application development and use, and solving the problem that the quick application development solution cannot achieve quick application scenarioization.

[0058] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0060] Figure 1 The invention is a flowchart of an application development method according to an exemplary embodiment.

[0061] Figure 2 The invention is a block diagram of an application development device according to an exemplary embodiment.

[0062] Figure 3 It is a structural diagram of a request receiving module 201 according to an exemplary embodiment.

[0063] Figure 4 It is a schematic diagram showing the structure of a development environment loading module 202 according to an exemplary embodiment.

[0064] Figure 5 FIG. 2 is a schematic diagram showing the structure of an editing instruction receiving module 203 according to an exemplary embodiment.

[0065] Figure 6 The invention is a block diagram of an application development device according to an exemplary embodiment.

[0066] Figure 7 The invention is a block diagram of an application development device according to an exemplary embodiment.

[0067] Figure 8 It is a block diagram of a device according to an exemplary embodiment (general structure of a mobile terminal). DETAILED DESCRIPTION

[0068] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.

[0069] As a complete application form, quick applications can be deeply integrated with the system, run like native applications, and interact with the system. Quick applications currently have two forms: full-screen independent application form and embedded card form. In the form of independent applications, the user experience is just like that of native applications, with complete life cycle management, page management, routing, etc. Quick applications can parasitize on Android Activities, pages parasitize on Fragments, and instances are managed and controlled through independent background Services. Cards are another form, which are embedded in various corners of the system as an independent local control through embedded SDKs to display dynamic content in a lightweight manner. In terms of security isolation, better security can be achieved through sandbox mechanisms, process isolation, permission control, and combined with support from the operating system layer.

[0070] The negative first screen is an entrance to quick apps. When users are operating mobile devices such as mobile phones, they can swipe to bring up the negative first screen, where they can perform operations such as quick search, opening quick apps, and browsing recommended quick app information in the quick app list on the negative first screen.

[0071] The negative one screen can display multiple quick app cards, and the display content and interface layout of each card are fixed. Users have strong personalized needs for quick apps, and quick app cards with a single interface cannot meet user needs. For example, users have specific preferences for interface colors, or want to display certain function buttons and hide certain function buttons. However, general quick app development solutions do not provide interfaces to other developers, and cannot implement quick app scenarios to meet application needs in different scenarios.

[0072] In order to solve the above problems, the embodiments of the present disclosure provide an application development method and device. By opening up the permissions of quick application development resources, different users can develop and customize personalized quick applications, thereby achieving highly flexible and highly adaptable quick application development and use, and solving the problem that the quick application development solution cannot realize the quick application scenario.

[0073] An exemplary embodiment of the present disclosure provides an application development method, using the method to complete the application development process such as Figure 1 As shown, including:

[0074] Step 101: Receive an edit request for a negative one screen quick application.

[0075] The negative first screen is an interface implementation for accessing quick apps. It is usually displayed on the leftmost screen of the mobile phone desktop, providing users with search, application suggestions, quick services, scenario intelligence and other services. The negative first screen can contain multiple quick app card displays, and you can display the interface of a certain card or edit the card display of a certain type of quick app. The negative first screen supports user customization, and users can choose the content displayed on the negative first screen according to their usage habits.

[0076] In this step, the client of a mobile terminal such as a mobile phone that supports quick applications receives an edit request for the quick application through the negative one screen. The edit request can be issued by long pressing the quick application card to bring up the menu and then clicking on the relevant option.

[0077] Specifically, a URL may be configured for the development environment of the quick application. When a user issues an edit request, the user actually issues an access request to the URL to obtain data related to the development environment of the quick application, so as to enter the development environment to edit and configure the quick application.

[0078] In this step, an edit request including a development environment URL for the negative one-screen quick application is received.

[0079] Step 102: Start the development environment of the requested quick application on the client.

[0080] In this step, the development environment of the requested quick application is started on the client. Specifically, according to the editing request, the software development tool SDK of the quick application can be returned for the user to edit the quick application.

[0081] SDK is a collection of documents, examples, and tools that assist in the development of a certain type of software. By downloading and installing the SDK, you can support the editing and development of the corresponding quick app, greatly shortening the development and debugging process.

[0082] In this step, the SDK returned by the remote server is received to prepare for the customization of the personalized quick application.

[0083] Step 103: Receive an editing instruction in the development environment of the requested quick application.

[0084] In this step, in the development environment, an editing instruction issued by a user is received. Specifically, the editing instruction input by the user through the SDK of the quick application is received.

[0085] Step 104: Edit and modify the quick app according to the editing instruction to generate a personalized quick app.

[0086] In this step, the user uses the SDK to perform editing operations, modifies the quick app based on the user's operations, generates a personalized quick app that adapts to the user's usage scenarios and habits, and completes the development of the quick app.

[0087] The editing operation involves at least one or more of the following:

[0088] Modify the navigation bar content, modify the navigation bar position, customize the icon message bar position, and message prompt content.

[0089] It should be noted that the content that can be edited is not limited to the above items. The corresponding editable content can be customized according to the specific quick application to meet the application needs to the greatest extent.

[0090] For example, if the navigation bar of a quick app card is at the top of the display interface and users are used to using the navigation bar at the bottom, they can edit and modify it to move the navigation bar to the bottom and other icons to the top. Users can also customize the icons of function buttons, such as changing images or display colors.

[0091] An exemplary embodiment of the present disclosure also provides an application development method, using which, after generating a personalized quick application, the personalized quick application can be submitted to the cloud for release through the development environment of the quick application. Specifically, a URL can also be assigned to the personalized quick application for other users to access and add to the terminal for local use.

[0092] An exemplary embodiment of the present disclosure also provides an application development method, using which the open permissions of different quick applications can be managed. Specifically, for a client, its system may support multiple quick applications. Different quick applications can be managed separately, the editing permissions of some or all quick applications can be opened, and the development environment can be configured separately for the quick applications with open editing permissions (such as adding SDKs associated with each quick application separately), and the editing and development of quick applications with open editing permissions can be supported through the SDK.

[0093] An exemplary embodiment of the present disclosure also provides an application development device, the structure of which is as follows: Figure 2 As shown, including:

[0094] The request receiving module 201 is used to receive an editing request for the negative one screen quick application;

[0095] The development environment loading module 202 is used to start the development environment of the requested quick application on the client;

[0096] An editing instruction receiving module 203, configured to receive an editing instruction in the development environment of the requested quick application;

[0097] The application editing and development module 204 is used to edit and modify the quick application according to the editing instruction to generate a personalized quick application.

[0098] Preferably, the structure of the request receiving module 201 is as follows: Figure 3 As shown, including:

[0099] The request receiving unit 301 is used to receive an edit request including a uniform resource locator URL for the negative one-screen quick application.

[0100] Preferably, the structure of the development environment loading module 202 is as follows: Figure 4 As shown, including:

[0101] The development tool providing unit 401 is used to return the software development tool SDK of the quick application according to the editing request, so that the user can edit the quick application.

[0102] Preferably, the structure of the editing instruction receiving module 203 is as follows: Figure 5 As shown, including:

[0103] The SDK instruction receiving unit 501 is used to receive the editing instruction input through the SDK of the quick app.

[0104] Preferably, the structure of the device is as follows Figure 6 As shown, it also includes:

[0105] The application publishing module 205 is used to submit the personalized quick application to the cloud for publishing through the development environment of the quick application.

[0106] Preferably, the structure of the device is as follows Figure 7 As shown, it also includes:

[0107] The development environment configuration module 206 is used to enable the editing permission of at least one quick application in the negative one screen, and configure the development environment for each quick application with the enabled editing permission.

[0108] The above device can be integrated into terminals such as mobile phones and computers, and the corresponding functions are realized by the terminals. Regarding the device in the above embodiment, the specific way in which each module performs the operation has been described in detail in the embodiment of the method, and will not be elaborated here.

[0109] An exemplary embodiment of the present disclosure further provides a computer device, including:

[0110] processor;

[0111] a memory for storing processor-executable instructions;

[0112] Wherein, the processor is configured to:

[0113] Receive an edit request for the negative one screen quick application;

[0114] Start the development environment of the requested quick application on the client;

[0115] In the development environment of the requested quick application, receiving an editing instruction;

[0116] The quick app is edited and modified according to the editing instruction to generate a personalized quick app.

[0117] Figure 8 8 is a block diagram of an apparatus 800 for application development according to an exemplary embodiment. For example, the apparatus 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0118] Reference Figure 8 , the device 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output (I / O) interface 812 , a sensor component 814 , and a communication component 816 .

[0119] The processing component 802 generally controls the overall operation of the device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0120] The memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0121] The power component 806 provides power to the various components of the device 800. The power component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 800.

[0122] The multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0123] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the device 800 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

[0124] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0125] The sensor assembly 814 includes one or more sensors for providing various aspects of status assessment for the device 800. For example, the sensor assembly 814 can detect the open / closed state of the device 800, the relative positioning of components, such as the display and keypad of the device 800, and the sensor assembly 814 can also detect the position change of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, the orientation or acceleration / deceleration of the device 800, and the temperature change of the device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0126] The communication component 816 is configured to facilitate wired or wireless communication between the device 800 and other devices. The device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0127] In an exemplary embodiment, the apparatus 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.

[0128] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the device 800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0129] A non-transitory computer-readable storage medium, when instructions in the storage medium are executed by a processor of a mobile terminal, enables the mobile terminal to execute an application development method, the method comprising:

[0130] Receive an edit request for the negative one screen quick application;

[0131] Return the SDK of the quick app so that the user can edit the quick app;

[0132] According to the user's editing operation, a personalized quick app is generated based on the quick app.

[0133] The embodiments of the present disclosure provide an application development method and device, which receives an editing request for a negative one-screen quick application, starts the development environment of the requested quick application on the client, allows the user to edit the quick application, and then receives an editing instruction in the development environment of the requested quick application, and then edits and modifies the quick application according to the editing instruction to generate a personalized quick application. By opening up the permissions of quick application development resources, different users can develop and customize personalized quick applications, thereby achieving highly flexible and adaptable quick application development and use, and solving the problem that the quick application development solution cannot achieve quick application scenarioization.

[0134] The technical solution provided by the embodiments of the present disclosure simplifies the development and debugging process of quick applications and provides a developer-friendly development environment.

[0135] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses or adaptations of the present invention that follow the general principles of the present invention and include common knowledge or customary techniques in the art that are not disclosed in this disclosure. The specification and examples are to be considered exemplary only, and the true scope and spirit of the present invention are indicated by the following claims.

[0136] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. An application development method, characterized in that: include: Receive an edit request for the negative one screen quick application, and send an access request to the URL of the development environment configuration requested by the edit request; Launching the development environment of the requested quick application on the client; In the development environment of the requested quick application, receiving an editing instruction; The quick app is edited and modified according to the editing instruction to generate a personalized quick app.

2. The application development method according to claim 1, characterized in that: The step of editing and modifying the quick app according to the editing instruction to generate a personalized quick app receiving an editing request for the negative one-screen quick app includes: An edit request including a uniform resource locator URL for the negative one-screen quick application is received.

3. The application development method according to claim 1, characterized in that: The step of receiving an editing request for a negative one-screen quick application and starting a development environment for the requested quick application includes: According to the editing request, the software development tool SDK of the quick application is returned for the user to edit the quick application.

4. The application development method according to claim 3, characterized in that: The step of receiving the editing instruction in the development environment of the requested quick application includes: Receive an editing instruction input by the user through the SDK of the quick app.

5. The application development method according to claim 1, characterized in that: The editing instruction at least involves any one or more of the following: Modify the navigation bar content, modify the navigation bar position, customize the icon, message bar position, and message prompt content.

6. The application development method according to claim 1, characterized in that: After the step of editing and modifying the quick app according to the editing instruction to generate a personalized quick app, the method further includes: The personalized quick application is submitted to the cloud for release through the development environment of the quick application.

7. The application development method according to claim 1, characterized in that: Before the step of receiving the editing request for the negative one screen quick application, the method further includes: The editing permission of at least one quick application in the negative first screen is opened, and a development environment is configured for each quick application for which the editing permission is opened.

8. An application development device, characterized in that: include: A request receiving module, used to receive an edit request for the negative one screen quick application, and send an access request to the URL of the development environment configuration requested by the edit request; A development environment loading module, used to start the development environment of the requested quick application on the client; An editing instruction receiving module, used for receiving an editing instruction in the development environment of the requested quick application; The application editing and development module is used to edit and modify the quick application according to the editing instruction to generate a personalized quick application.

9. The application development device according to claim 8, characterized in that: The request receiving module comprises: The request receiving unit is used to receive an editing request containing a uniform resource locator URL for the negative one-screen quick application.

10. The application development device according to claim 8, characterized in that: The development environment loading module includes: The development tool providing unit is used to return the software development tool SDK of the quick application according to the editing request, so that the user can edit the quick application.

11. The application development device according to claim 10, characterized in that: The editing instruction receiving module comprises: The SDK instruction receiving unit is used to receive the editing instruction input through the SDK of the quick application.

12. The application development device according to claim 8, characterized in that: The device also includes: The application publishing module is used to submit the personalized quick application to the cloud for publishing through the development environment of the quick application.

13. The application development device according to claim 8, characterized in that: The device also includes: The development environment configuration module is used to open the editing permission of at least one quick application in the negative one screen, and configure the development environment for each quick application with the opened editing permission.

14. A computer device, characterized in that: include: processor; a memory for storing processor-executable instructions; Wherein, the processor is configured to: Receive an edit request for the negative one screen quick application, and send an access request to a URL of the development environment configuration requested by the edit request; Launching the development environment of the requested quick application on the client; In the development environment of the requested quick application, receiving an editing instruction; The quick app is edited and modified according to the editing instruction to generate a personalized quick app.

15. A non-transitory computer-readable storage medium, when instructions in the storage medium are executed by a processor of a mobile terminal, enables the mobile terminal to perform an application development method, the method comprising: Receive an edit request for the negative one screen quick application, and send an access request to a URL of the development environment configuration requested by the edit request; Launching the development environment of the requested quick application on the client; In the development environment of the requested quick application, receiving an editing instruction; The quick app is edited and modified according to the editing instruction to generate a personalized quick app.

Images