CN112214214A - Low code development system, device and medium for android native APP - Google Patents
Low code development system, device and medium for android native APP Download PDFInfo
- Publication number
- CN112214214A CN112214214A CN202011180971.0A CN202011180971A CN112214214A CN 112214214 A CN112214214 A CN 112214214A CN 202011180971 A CN202011180971 A CN 202011180971A CN 112214214 A CN112214214 A CN 112214214A
- Authority
- CN
- China
- Prior art keywords
- designer
- metadata
- android
- platform
- event
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000011161 development Methods 0.000 title claims abstract description 52
- 238000000034 method Methods 0.000 claims abstract description 13
- 238000012800 visualization Methods 0.000 claims abstract description 11
- 230000000007 visual effect Effects 0.000 claims abstract description 10
- 230000015654 memory Effects 0.000 claims description 26
- 230000006870 function Effects 0.000 claims description 15
- 238000013461 design Methods 0.000 claims description 14
- 238000003860 storage Methods 0.000 claims description 12
- 238000004422 calculation algorithm Methods 0.000 claims description 8
- 238000005516 engineering process Methods 0.000 claims description 8
- 238000012545 processing Methods 0.000 claims description 7
- 230000009471 action Effects 0.000 claims description 4
- 230000000694 effects Effects 0.000 abstract description 7
- 230000008859 change Effects 0.000 abstract description 5
- 230000010354 integration Effects 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 238000007726 management method Methods 0.000 description 6
- 230000003993 interaction Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 238000004590 computer program Methods 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000011022 operating instruction Methods 0.000 description 3
- 238000009877 rendering Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000001902 propagating effect Effects 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012512 characterization method Methods 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 229910052802 copper Inorganic materials 0.000 description 1
- 239000010949 copper Substances 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000004513 sizing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/315—Object-oriented languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a low code development system, equipment and medium to android native APP, the system includes: the low-code development platform is used for generating metadata comprising forms and event configurations through visualization and uploading the metadata to the cloud database; the low code development platform comprises: a form designer, an event designer, and a service unit designer; and the android running platform is used for downloading, analyzing and dynamically generating the metadata from the cloud database to obtain application data containing different form pages and logics. The low-code development system for the android native APP can perform visual application development without coding aiming at the android running platform, and can meet the requirement of rapidly adapting to enterprise change; compared with a Web platform, the method has better selection in the aspects of the integration of future hardware devices and the presentation of page effects.
Description
Technical Field
The invention relates to the technical field of software development, in particular to a low-code development system, equipment and medium for android native APP.
Background
The application building of the traditional development platform needs the processes of software coding, compiling, publishing/deploying, and the following problems are easy to occur in the application process of an actual enterprise:
1) for different platforms, for example: desktop application programs, Web application programs, Android native apps and IOS native apps need to be developed respectively by using different development environments and development languages, and development cost is high;
2) enterprises maintain the application of traditional development receipt, professional talents are needed, ordinary business personnel are difficult to maintain, and the maintenance cost is high;
3) when the enterprise requirements change, the requirements for quickly adapting to the enterprise changes are difficult to meet through the complete process of encoding, compiling and deploying the curved needle to different terminals;
moreover, most development platforms are realized based on a WEB operation platform at present, but few enterprises are based on Android operation platforms, the interaction with hardware equipment interfaces is more frequent along with the gradual development of the trend of interconnection of everything, and the application of the native Android mobile phone terminal has natural advantages. Therefore, a low-code development platform providing visualization for an android runtime platform is needed.
Disclosure of Invention
In view of the above-mentioned shortcomings of the prior art, it is an object of the present application to provide a low code development system, device and medium for android native APP to solve at least one problem existing in the prior art.
To achieve the above and other related objects, the present application provides a low code development system for android native APP, the system comprising: the low-code development platform is used for generating metadata comprising forms and event configurations through visualization and uploading the metadata to the cloud database; the low code development platform comprises: a form designer, an event designer, and a service unit designer; and the android running platform is used for downloading, analyzing and dynamically generating the metadata from the cloud database to obtain application data containing different form pages and logics.
In an embodiment of the application, the form designer is configured to design layout and component elements of a form page in a visual dragging manner based on a business model; the event designer is used for designing functional logic of a form page after a component of the form page responds to an event in a visual dragging mode based on a business model; the service unit designer is used for designing business logic for data in a database in a visualization mode so as to form metadata containing forms and event configuration.
In an embodiment of the present application, the form designer designs the layout and components of the form page by defining attributes; the attributes include: any one or more of name, size, data source, action, appearance and layout mode; the attributes, and components of each of the forms designed or built in the form designer are stored in a predefined metadata format.
In an embodiment of the present application, the event designer includes: general design: for setting start or finish; logic design: is used for setting and judging; designing a UI: the system is used for setting an open form, an open loading frame, a close loading frame and a message; designing data: for setting component attributes, setting values, and obtaining data; and (3) processing and designing: for setting call store procedures, call events, start timers, stop timers, sleep, and custom code.
In an embodiment of the application, when a user requirement changes, the metadata can be modified or updated through a cloud end, so that the android running platform or the running engine can adjust a corresponding service function during running.
In an embodiment of the application, the android operating platform downloads, analyzes and dynamically generates different forms, functional logics and business logics from a database by loading an engine algorithm during running; and calling a component library and an API (application program interface) interface at the bottom layer of the android system by means of a memory management technology to form an interface function of the android native APP.
In an embodiment of the present application, the engine algorithm includes: opening a form analyzed from a database; judging whether form cache exists or not; if yes, downloading form data; and creating a form, a component, time and logic according to the metadata definition to complete the form loading.
To achieve the above and other related objects, the present application provides a computer apparatus, comprising: a memory, a processor, and a communicator; the memory is to store computer instructions; the processor executes computer instructions to implement the functionality of the platform as described above; the communicator is used for communicating with an external device.
To achieve the above and other related objects, the present application provides a computer readable storage medium storing computer instructions which, when executed, perform the functions of the platform as described above.
To sum up, the present application provides a low code development system, device and medium for android native APP, the system includes: the low-code development platform is used for generating metadata comprising forms and event configurations through visualization and uploading the metadata to the cloud database; the low code development platform comprises: a form designer, an event designer, and a service unit designer; and the android running platform is used for downloading, analyzing and dynamically generating the metadata from the cloud database to obtain application data containing different form pages and logics.
Has the following beneficial effects:
the low-code development system for the android native APP can perform visual application development without coding aiming at the android running platform, and can meet the requirement of rapidly adapting to enterprise change; compared with a Web platform, the method has better selection in the aspects of the integration of future hardware devices and the presentation of page effects.
Drawings
Fig. 1 is a block diagram illustrating a low code development system for android native APP according to an embodiment of the present application.
FIG. 2 is a schematic interface diagram of a form designer according to an embodiment of the present application.
FIG. 3 is a schematic interface diagram of an event designer according to an embodiment of the present application.
FIG. 4 is a schematic interface diagram of a service unit designer according to an embodiment of the present application.
FIG. 5 is a schematic diagram of an interface for creating metadata for a form through a form designer according to an embodiment of the present application.
FIG. 6 is a flow chart illustrating an engine algorithm according to an embodiment of the present application.
Fig. 7 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application is provided by way of specific examples, and other advantages and effects of the present application will be readily apparent to those skilled in the art from the disclosure herein. The present application is capable of other and different embodiments and its several details are capable of modifications and/or changes in various respects, all without departing from the spirit of the present application. It is to be noted that the features in the following embodiments and examples may be combined with each other without conflict.
It should be noted that the drawings provided in the following embodiments are only schematic and illustrate the basic idea of the present application, and although the drawings only show the components related to the present application and are not drawn according to the number, shape and size of the components in actual implementation, the type, quantity and proportion of the components in actual implementation may be changed at will, and the layout of the components may be more complex.
Throughout the specification, when a part is referred to as being "connected" to another part, this includes not only a case of being "directly connected" but also a case of being "indirectly connected" with another element interposed therebetween. In addition, when a certain part is referred to as "including" a certain component, unless otherwise stated, other components are not excluded, but it means that other components may be included.
The terms first, second, third, etc. are used herein to describe various elements, components, regions, layers and/or sections, but are not limited thereto. These terms are only used to distinguish one element, component, region, layer or section from another element, component, region, layer or section. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the scope of the present application.
Also, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms "comprises," "comprising," and/or "comprising," when used in this specification, specify the presence of stated features, operations, elements, components, items, species, and/or groups, but do not preclude the presence, or addition of one or more other features, operations, elements, components, items, species, and/or groups thereof. The terms "or" and/or "as used herein are to be construed as inclusive or meaning any one or any combination. Thus, "A, B or C" or "A, B and/or C" means "any of the following: a; b; c; a and B; a and C; b and C; A. b and C ". An exception to this definition will occur only when a combination of elements, functions or operations are inherently mutually exclusive in some way.
At present, a low-code development system or platform is mostly realized on a Web platform or based on the Web platform, and the rendering and generation of the Html are realized by means of technologies such as JavaScript or C # Blazor, dynamic compilation is not needed in the realization, and a user presents the Html by means of a mainstream browser during running, so that the effect of dynamically presenting a page is achieved, and the technical realization is relatively simple.
However, few low-code systems or platforms are currently converted to the Android platform, the main reasons may be: 1) most of application developers may consider that a Web end is available, and can cover terminals such as a PC (personal computer) and a mobile phone, and the developers do not need to repeatedly input to research and develop the native App presentation of the android system; 2) for most internet applications, the requirements and interfaces may be considered relatively simple, or differences in native APPs versus the Web, such as thought differences resulting from differences in the customer industry being served, may not be understood, and thus no longer may a low-code development system or platform for native APPs based on the android system be developed.
However, the application considers that the low-code development aiming at the android native APP is more commercial value and application prospect than the low-code development aiming at the Web platform. Therefore, the present application proposes a low code development system, device and medium for android native APP, which are different from the technical means of a Web-based low code development system or platform, to solve the above problems.
Fig. 1 is a block diagram of a low code development system for android native APP according to an embodiment of the present application. As shown, the system 100 includes:
the low-code development platform 110 is used for generating metadata comprising forms and event configurations through visualization and uploading the metadata to a cloud database; the low-code development platform 110 includes: a form designer 111, an event designer 112, and a service unit designer 113.
In the present application, the configuration of the metadata is mainly completed in a visual dragging manner through a designer on the low-code development platform 110, and the roles of the designers are respectively:
the form designer 111 is used for designing layout and component elements of a form page in a visual dragging mode based on a business model.
As shown in fig. 2, the form designer 111 designs the layout and components of the form page mainly by defining attributes; the attributes include: any one or more of name, size, data source, action, appearance, and layout. Corresponding to fig. 2, for each sub-layout module or component in the form page, a right mouse button may be clicked to enter the attribute setting window, and the main attribute column may include: an "all" box that can set all attributes; such as for name writing, sizing, or "general purpose" boxes; setting a data box of a data source; a "behavior" box that sets behaviors or actions; a "look" box that sets a look or style, and so on.
It should be noted that the attributes and components of each form designed or built in the form designer 111 in the present application are stored in a predefined metadata format. I.e., the format of selectable or settable items preset in the form designer 111, to form a metadata format in accordance with the preset.
And the event designer 112 is used for designing functional logic of the components of the form page after responding to the event in a visual dragging mode based on the business model. Such as click, load, etc.
For example, as shown in FIG. 3, opening the window of the event designer 112 can be seen to include, but is not limited to:
general design: for setting start or finish;
logic design: is used for setting and judging; the determination is a logical determination.
Designing a UI: the system is used for setting an open form, an open loading frame, a close loading frame and a message;
designing data: for setting component attributes, setting values, and obtaining data;
and (3) processing and designing: for setting call store procedures, call events, start timers, stop timers, sleep, and custom code.
It should be noted that, unlike the conventional common event designer 112, the event designer 112 described in the present application visualizes "logic". For example, it is originally implemented by logic statements of a programming language such as code-writing IF..
As shown in fig. 3, a start module is first set in the event designer 112, and then logical judgment modules are added, one of which judges a UI module corresponding to the open form is set, and the other judges a UI module corresponding to the open message is set, and respectively correspond to a last set completion module. It may be a simple functional logic designed by event designer 112 for components of a form page in response to an event.
The service unit designer 113 is configured to design business logic for data in a database in a visualization manner to form metadata including a form and an event configuration.
The metadata is data for the android native APP generation application. In the service unit designer 113, visual drag combination is performed through an existing component or file to realize business logic characterization for data.
For example, as shown in fig. 4, in the editing interface of the service unit designer 113, the left list does not include an established form or a commonly used form, a visualization component, and the like, and the right list europe includes a target file obj and a database file dbc, and then the corresponding service logic can be implemented by dragging a specific form to a corresponding obj or dbc position.
The implementation of a complete metadata by the low-code development platform 110 through the form designer 111, the event designer 112, and the service unit designer 113 as described herein can be illustrated as follows:
first, through form designer 111, a form "purchase receiving queue" is created, as shown in FIG. 5 below. Through the form designer 111, metadata of a form is created in the background, such as the values of the form name attribute: the queue of "procurement receipts," and other attributes, such as: "invoice", "supplier", "total number", "delivery date", "handle" button, etc. Similarly, other attributes of the form are, for example: size, data source, layout, etc. are stored in a metadata format that we have defined in advance, as are the components within the form. Functional logic of the form page after responding to the event can be designed through the event designer 112, and business logic is designed for data in the database through the service unit designer 113, so that metadata containing form and event configuration is formed, and the metadata is stored in the database, and therefore the metadata for running on the android native APP on the low-code development platform 110 is completed. With the above metadata, when the engine algorithm is loaded on different android operating platforms 120, the metadata can be downloaded from the database, analyzed, and different form pages and logics can be dynamically generated.
In this embodiment, when the user requirement changes, the metadata may be modified or updated through the cloud, so that the corresponding service function may be adjusted when the android runtime platform 120 or runtime engine runs. In brief, when the user requirement changes and the developed partial function design or interface design needs to be adjusted, the complete process of encoding, compiling and deploying to different terminals is not needed, and the application data can be updated when the android running platform 120 operates again only by adjusting or modifying through different designers on the basis of the low-code development system 100, so that the requirement for rapidly adapting to enterprise change can be met.
It should be noted that the application is characterized in that application data is generated by implementing loading on the android operating platform 120. Most designers are based on WEB designers at present, developed data files need to be realized on a Web operation platform, and dynamic compiling is not needed in the realization process based on a script language. The Web operation platform realizes the rendering and generation of the Html by reading the data file and by means of technologies such as a script language, e.g. JavaScript or C # Blazor, and the like, and a user displays the data file by means of a mainstream browser during operation, so that the effect of dynamically displaying the page is achieved.
Compared with the development system 100 for the operation on the Web platform, the low-code development system 100 for the android native APP has the following advantages:
1) the time required by the Web for loading the languages such as css \ JavaScript and the like is longer than that of the native App, so that the waiting time of the android native App page is shorter and less;
2) since most android operating platforms 120 operate on mobile phones and PAD mobile terminals, for example, metadata developed by the system 100 can operate on android native APPs, and can adjust a scanning function of a camera of a mobile phone local computer, or can also utilize an NFC interface of the mobile phone to realize interaction of data or information and the like;
3) for components of a Web platform, because the form functions of the components have theoretical upper limits, technical problems such as memory management and memory leak need to be considered, more memory management and optimization need to be considered, and great efforts need to be spent. In the application, the android native APP is used as a configuration operation platform, the form of the android native APP has no upper limit theoretically, and only timely memory cleaning and releasing need to be considered;
4) from the perspective of user experience, the App user experience of android native is better than the Web user experience. For example: the click of the button has feedback, and the feedback of the touch feeling can be brought by matching with the vibration and the sound of the equipment;
5) from the perspective of future everything interconnection, the interaction with the hardware device interface will be more frequent, and when involving direct interaction with the hardware device, the application of native android native App has the inherent advantages, which is simply said: the native App can be integrated with hardware equipment better, more efficiently and more stably, and the Web end is currently known to mainly rely on JavaScript to realize local interaction;
6) aiming at service client groups of the manufacturing industry, the requirements of manufacturing enterprises are relatively complex, the personalization is stronger, currently mainstream equipment is gradually transferred to the android operating system 100 in PDA industrial acquisition equipment of the manufacturing industry, data acquisition of an industrial field and personnel quality of operators in a workshop field directly require that a function or a page for data acquisition is simpler, more intelligent and better in user experience, and under the condition, the native App is a better choice for the integration of future hardware equipment and the presentation of page effects compared with a Web platform.
In the present application, the system 100 further comprises: and the android running platform 120 is used for downloading, analyzing and dynamically generating different form pages and logics from the cloud database.
In this embodiment, different from the loading of the Web platform, the android operating platform 120 downloads, analyzes, and dynamically generates different forms, functional logics, and business logics from a database by loading an engine algorithm during the running; and calling a component library and an API (application program interface) interface at the bottom layer of the android system by means of a memory management technology to form an interface function of the android native APP.
It should be noted that, the difference between the android operating platform 120 based on the low-code development system 100 described in the present application and the existing Web-based platform is mainly reflected in:
a) the Android running platform 120(Android App) does not generate Html through a scripting language, the non-scripting language is realized under the Android platform, but a page is presented by calling a component on the bottom layer of an Android operating system to generate an application, and a component library on the bottom layer of the Android is called by means of a memory management technology and a development mode similar to a desktop application program to form an interface function of the Android native App.
b) The two used technologies are completely different in implementation mode, like the difference between the traditional Web application program and the desktop application program, core mechanisms of the two are completely different, the Web operation platform is presented by means of parsing and rendering Html of a main stream browser, and the Android operation platform 120 is presented by means of an API (application programming interface) at the bottom layer of the Android operating system 100 and by means of memory management.
c) In development implementation, the two runtime engines use completely different technologies from the viewpoint of code writing, and call libraries with completely different mechanisms.
For example, as shown in fig. 6, the engine algorithm includes:
step S601: opening a form analyzed from a database;
step S602: judging whether form cache exists or not; if yes, downloading form data;
step S603: and creating a form, a component, time and logic according to the metadata definition to complete the form loading.
In brief, after the form in the metadata is analyzed, whether the form cache exists is judged, if yes, the form data is downloaded, and then the form, the component, the time and the logic are created according to the definition of the metadata so as to complete the loading of the form.
In summary, the low-code development system for the android native APP can perform visualized application development without coding for an android running platform, and can meet the requirement of rapidly adapting to enterprise changes; compared with a Web platform, the method has better selection in the aspects of the integration of future hardware devices and the presentation of page effects.
Fig. 7 is a schematic structural diagram of a computer device according to an embodiment of the present invention. As shown, the computer device 700 includes: a memory 701, a processor 702, and a communicator 703; the memory 701 is used for storing computer instructions; the processor 702 executes computer instructions to implement the functionality of the system described in FIG. 1; the communicator 703 is configured to communicate with an external device, such as a cloud database.
In some embodiments, the number of the memories 701 in the computer device 700 may be one or more, the number of the processors 702 may be one or more, the number of the communicators 703 may be one or more, and fig. 7 illustrates one example.
The Memory 701 may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The memory 701 stores an operating system and operating instructions, executable modules or data structures, or a subset thereof, or an expanded set thereof, wherein the operating instructions may include various operating instructions for performing various operations. The operating system may include various system programs for implementing various basic services and for handling hardware-based tasks.
The Processor 702 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
The communicator 703 is used for implementing communication connection between the database access device and other devices (such as a client, a read-write library and a read-only library). The communicator 703 may include one or more sets of modules of different communication modes, for example, a CAN communication module communicatively connected to a CAN bus. The communication connection may be one or more wired/wireless communication means and combinations thereof. The communication method comprises the following steps: any one or more of the internet, CAN, intranet, Wide Area Network (WAN), Local Area Network (LAN), wireless network, Digital Subscriber Line (DSL) network, frame relay network, Asynchronous Transfer Mode (ATM) network, Virtual Private Network (VPN), and/or any other suitable communication network. For example: any one or a plurality of combinations of WIFI, Bluetooth, NFC, GPRS, GSM and Ethernet.
In some specific applications, the various components of the computer device 700 are coupled together by a bus system that may include a power bus, a control bus, a status signal bus, etc., in addition to a data bus. But for clarity of illustration the various buses have been referred to as a bus system in figure 7.
In an embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored, which when executed by a processor implements the functionality of the system as described in fig. 1.
The present application may be embodied as systems, methods, and/or computer program products, in any combination of technical details. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for causing a processor to implement various aspects of the present application.
The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: 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), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.
The computer-readable programs described herein may be downloaded from a computer-readable storage medium to a variety of computing/processing devices, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.
The computer program instructions for carrying out operations of the present application may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine related instructions, microcode, firmware instructions, state setting data, integrated circuit configuration data, or source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, the electronic circuitry can execute computer-readable program instructions to implement aspects of the present application by utilizing state information of the computer-readable program instructions to personalize the electronic circuitry, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA).
To sum up, the present application provides a low code development system, device and medium for android native APP, the system includes: the low-code development platform is used for generating metadata comprising forms and event configurations through visualization and uploading the metadata to the cloud database; the low code development platform comprises: a form designer, an event designer, and a service unit designer; and the android running platform is used for downloading, analyzing and dynamically generating the metadata from the cloud database to obtain application data containing different form pages and logics.
The application effectively overcomes various defects in the prior art and has high industrial utilization value.
The above embodiments are merely illustrative of the principles and utilities of the present application and are not intended to limit the invention. Any person skilled in the art can modify or change the above-described embodiments without departing from the spirit and scope of the present application. Accordingly, it is intended that all equivalent modifications or changes which can be made by those skilled in the art without departing from the spirit and technical spirit of the present invention be covered by the claims of the present application.
Claims (9)
1. A low code development system for android native APP, the system comprising:
the low-code development platform is used for generating metadata comprising forms and event configurations through visualization and uploading the metadata to the cloud database; the low code development platform comprises: a form designer, an event designer, and a service unit designer;
and the android running platform is used for downloading, analyzing and dynamically generating the metadata from the cloud database to obtain application data containing different form pages and logics.
2. The system of claim 1, wherein the form designer is configured to design layout and component elements of a form page by visual drag based on a business model;
the event designer is used for designing functional logic of a form page after a component of the form page responds to an event in a visual dragging mode based on a business model;
the service unit designer is used for designing business logic for data in a database in a visualization mode so as to form metadata containing forms and event configuration.
3. The system of claim 1, wherein the form designer designs the layout, and components, of the form page by defining properties; the attributes include: any one or more of name, size, data source, action, appearance and layout mode; the attributes, and components of each of the forms designed or built in the form designer are stored in a predefined metadata format.
4. The system of claim 1, wherein the event designer comprises:
general design: for setting start or finish;
logic design: is used for setting and judging;
designing a UI: the system is used for setting an open form, an open loading frame, a close loading frame and a message;
designing data: for setting component attributes, setting values, and obtaining data;
and (3) processing and designing: for setting call store procedures, call events, start timers, stop timers, sleep, and custom code.
5. The system of claim 1, wherein when a user demand changes, the metadata can be modified or updated through a cloud end, so that the android runtime platform or runtime engine can adjust corresponding business functions.
6. The system of claim 1, wherein the android runtime platform loads an engine algorithm to download, parse, and dynamically generate the metadata from the database into different forms, functional logic, and business logic during runtime; and calling a component library and an API (application program interface) interface at the bottom layer of the android system by means of a memory management technology to form an interface function of the android native APP.
7. The system of claim 6, wherein the engine algorithm comprises:
opening a form analyzed from a database;
judging whether form cache exists or not; if yes, downloading form data;
and creating a form, a component, time and logic according to the metadata definition to complete the form loading.
8. A computer device, the device comprising: a memory, a processor, and a communicator; the memory is to store computer instructions; the processor executes computer instructions to implement the functions of the system according to any one of claims 1 to 7; the communicator is used for communicating with an external device.
9. A computer-readable storage medium having stored thereon computer instructions which, when executed, perform the functions of the system of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011180971.0A CN112214214A (en) | 2020-10-29 | 2020-10-29 | Low code development system, device and medium for android native APP |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011180971.0A CN112214214A (en) | 2020-10-29 | 2020-10-29 | Low code development system, device and medium for android native APP |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112214214A true CN112214214A (en) | 2021-01-12 |
Family
ID=74057512
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011180971.0A Pending CN112214214A (en) | 2020-10-29 | 2020-10-29 | Low code development system, device and medium for android native APP |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112214214A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113656012A (en) * | 2021-08-17 | 2021-11-16 | 广州新科佳都科技有限公司 | Low code development system of rail transit visual interface |
| CN113835691A (en) * | 2021-09-27 | 2021-12-24 | 工银科技有限公司 | iOS application development method, system, device, medium and program product |
| CN114064040A (en) * | 2021-11-30 | 2022-02-18 | 上海汇付数据服务有限公司 | Terminal code automatic generation method and platform based on visual interface |
| CN114168121A (en) * | 2021-12-07 | 2022-03-11 | 济南红旗信息科技有限公司 | Software system, terminal and storage medium based on code factory mode development |
| US11330070B1 (en) * | 2021-01-29 | 2022-05-10 | Salesforce.Com, Inc. | Containerized workflow engines executing metadata for user-defined applications |
| CN115328458A (en) * | 2022-10-12 | 2022-11-11 | 共道网络科技有限公司 | Business application development method and device |
| CN116483955A (en) * | 2023-06-20 | 2023-07-25 | 北京中科朗易科技有限责任公司 | Operation and maintenance method, device and equipment based on operation and maintenance work order and readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150142949A1 (en) * | 2013-11-18 | 2015-05-21 | Nuwafin Holdings Ltd | System and method for collaborative designing, development, deployment, execution, monitoring and maintenance of enterprise applications |
| TW201835759A (en) * | 2017-03-17 | 2018-10-01 | 葉振忠 | Development platform of mobile native applications |
| CN110221848A (en) * | 2019-04-23 | 2019-09-10 | 五八有限公司 | APP method for updating pages, device, electronic equipment and storage medium |
| CN110543343A (en) * | 2019-06-13 | 2019-12-06 | 银联商务股份有限公司 | Financial interaction page generation method and device based on native android application |
| CN110825362A (en) * | 2019-11-04 | 2020-02-21 | 广东道一信息技术股份有限公司 | Low-code application software development system and method |
-
2020
- 2020-10-29 CN CN202011180971.0A patent/CN112214214A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150142949A1 (en) * | 2013-11-18 | 2015-05-21 | Nuwafin Holdings Ltd | System and method for collaborative designing, development, deployment, execution, monitoring and maintenance of enterprise applications |
| TW201835759A (en) * | 2017-03-17 | 2018-10-01 | 葉振忠 | Development platform of mobile native applications |
| CN110221848A (en) * | 2019-04-23 | 2019-09-10 | 五八有限公司 | APP method for updating pages, device, electronic equipment and storage medium |
| CN110543343A (en) * | 2019-06-13 | 2019-12-06 | 银联商务股份有限公司 | Financial interaction page generation method and device based on native android application |
| CN110825362A (en) * | 2019-11-04 | 2020-02-21 | 广东道一信息技术股份有限公司 | Low-code application software development system and method |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11330070B1 (en) * | 2021-01-29 | 2022-05-10 | Salesforce.Com, Inc. | Containerized workflow engines executing metadata for user-defined applications |
| CN113656012A (en) * | 2021-08-17 | 2021-11-16 | 广州新科佳都科技有限公司 | Low code development system of rail transit visual interface |
| CN113656012B (en) * | 2021-08-17 | 2022-05-03 | 广州新科佳都科技有限公司 | Low code development system of rail transit visual interface |
| CN113835691A (en) * | 2021-09-27 | 2021-12-24 | 工银科技有限公司 | iOS application development method, system, device, medium and program product |
| CN114064040A (en) * | 2021-11-30 | 2022-02-18 | 上海汇付数据服务有限公司 | Terminal code automatic generation method and platform based on visual interface |
| CN114168121A (en) * | 2021-12-07 | 2022-03-11 | 济南红旗信息科技有限公司 | Software system, terminal and storage medium based on code factory mode development |
| CN115328458A (en) * | 2022-10-12 | 2022-11-11 | 共道网络科技有限公司 | Business application development method and device |
| CN115328458B (en) * | 2022-10-12 | 2023-02-03 | 共道网络科技有限公司 | Business application development method and device |
| CN116483955A (en) * | 2023-06-20 | 2023-07-25 | 北京中科朗易科技有限责任公司 | Operation and maintenance method, device and equipment based on operation and maintenance work order and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112214214A (en) | Low code development system, device and medium for android native APP | |
| US10628132B2 (en) | Inversion of control framework for multiple behaviors of a process | |
| Paterno et al. | One model, many interfaces | |
| US8561048B2 (en) | Late and dynamic binding of pattern components | |
| US20140173454A1 (en) | Method and system for designing, deploying and executing transactional multi-platform mobile applications | |
| US10331765B2 (en) | Methods and apparatus for translating forms to native mobile applications | |
| EP3726373B1 (en) | Creating an app method and system | |
| US11893218B2 (en) | Intelligent manipulation of dynamic declarative interfaces | |
| CN112540763A (en) | Front-end page generation method and device, platform equipment and storage medium | |
| US11194450B2 (en) | Definition of a graphical user interface dashboard created with manually input code and user selections | |
| US10489167B2 (en) | Dynamically binding data in an application | |
| Snell et al. | Microsoft Visual Studio 2012 Unleashed: Micro Visua Studi 2012 Unl_p2 | |
| WO2019039255A1 (en) | Terminal device, ui extension method, and ui extension program | |
| WO2020242591A1 (en) | Ingesting and processing content types | |
| US10678561B2 (en) | Virtualizing extension code in an application | |
| JP2016066355A (en) | Web application generating system, control method of web application generating system, program for web application generating system, web application generating device, control method of web application generating device, and program for web application generating device | |
| US20180074663A1 (en) | Dynamic process model palette | |
| Sprogis | ajoo: WEB Based Framework for Domain Specific Modeling Tools. | |
| TWI582696B (en) | Method of projecting a workspace and system using the same | |
| KR102382703B1 (en) | Multi-Channel Integration Platform Authoring Device and Method Thereby | |
| US11526366B2 (en) | Dynamically binding data in an application | |
| US20210149646A1 (en) | Orthogonal path renderer for natural looking sequence flows | |
| TWI609272B (en) | Terminal device and terminal operating system thereof and cloud device and cloud operating system thereof | |
| KR20240054362A (en) | Methods and systems for managing apps, especially developing apps that include event artifacts | |
| TWI581117B (en) | Cooperative work method on webpage |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |