Method and system for constructing mobile application based on low-code platform
Through the low-code platform of low-code platform, the problems of poor portability and high labor costs of traditional mobile application development in multi-platform development are solved, and the rapid online and multi-terminal reuse of mobile application pages are achieved, which reduces development costs and supports Multi-terminal unified UI and experience.
Patent Information
- Application Number
- CN202410940125.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-15
- Publication Date
- 2024-11-12
AI Technical Summary
Traditional mobile application development has problems such as poor portability, high labor costs and poor page dynamics. Especially when multi-platform development, multiple sets of code need to be written, which has high maintenance costs and is difficult to respond to business changes quickly.
Using a low-code platform, a general component definition data model is formed by abstracting mobile application page UI and business modules, a unified Schema specification is defined, and a visual designer is used for page configuration, supporting customized component development, and realizing multi-terminal reuse of page configuration at one time.
It has achieved rapid online launch of mobile application pages, reduced development costs, supported multi-terminal unified UI and experience, quickly responded to business changes, reduced human development needs, and achieved precise operation push.
Smart Images

Figure CN118939248A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of mobile application development technology, and in particular to a method and system for building a mobile application based on a low-code platform. Background Art
[0002] Traditional mobile application development is pure native application development, which is to develop mobile applications on mobile platforms such as Hongmeng, Android, iOS, or WeChat and Alipay mini-program development systems using official development languages, development libraries, and development tools. For example, Android App refers to an App developed by directly calling the Android SDK API on the development tools of Eclipse or Android Studio using the Java or Kotlin development languages; and iOS App refers to an App developed by directly calling the iOSSDK API on the development tools of Xcode using the Objective-C or Swift development languages. Mini-programs refer to platform-specific applications developed by calling the SDK or functions provided by the platform on the platform-specified development tools using the development languages specific to the mini-program platform.
[0003] The construction of traditional mobile applications requires the establishment of a development environment, software coding, platform application compilation, release review, and listing, which have the following significant problems:
[0004] 1) Traditional mobile application development has poor portability. When a mobile application needs to be developed for multiple platforms, Hongmeng, Android, iOS, WeChat applet, Alipay applet or other platform applet must be developed separately, and the same logic and interface need to be written in multiple sets.
[0005] 2) Different platforms need to maintain different codes, and developers with different specialties need to be recruited, which results in high manpower costs. High development costs.
[0006] 3) The content of mobile application pages is relatively fixed and not very dynamic. In most cases, if a major change is needed to the page content, it can only be re-released after the development of each platform is completed. After waiting for each platform to review and release it, users can only see the final effect after the App or Mini Program is updated and distributed in the App Store. It is difficult to respond quickly to business changes. Summary of the invention
[0007] In view of this, the purpose of the present invention is to provide a method and system for building mobile applications based on a low-code platform, so as to improve the efficiency of building mobile applications and reduce the difficulty of mobile application development.
[0008] To achieve the above-mentioned object of the invention, the first aspect of the present invention provides a method for building a mobile application based on a low-code platform, the method comprising the following steps:
[0009] S101, forming a data model for defining common components by abstracting common mobile application page UIs and business modules, where the data model is data describing mobile application page UIs and business modules;
[0010] S102. Define a unified Schema specification to agree on the specification for describing page configuration, component configuration, and data rendering configuration;
[0011] S103, define basic page information, where the basic page information describes page title, page code, page description, page channel and page tag;
[0012] S104, performing visual configuration of the page through a visual mobile application page designer;
[0013] S105. Release page is online.
[0014] Furthermore, the page tag includes configuration of multiple tag items, and the configuration of the tag items includes the following steps:
[0015] S201. When defining basic information of a page, display all configurable tag items through a tag configuration module. The configurable tag items include a display name, a unique code, and a weight.
[0016] S202: Configure configurable tag items and tag values according to business requirements.
[0017] Furthermore, the visual configuration of the page is performed through the visual mobile application page designer, including:
[0018] Configure the page layout generated according to the Schema specification. The page layout configuration includes page style configuration and component layout configuration;
[0019] Configure component parameters, including component style configuration, business attribute page style configuration, and page display data configuration;
[0020] Data binding, including configuring the data source of the component;
[0021] Configure the interaction between component content and mobile applications, which is used to describe how to call the client capabilities exposed by mobile applications to achieve corresponding business goals when users click on the component.
[0022] Configure the persistent page and save the generated visualization page configuration information in the data storage layer to form the page version configuration;
[0023] Configure the page version. Based on the existing page version configuration, copy the new page configuration to generate a new page version. Persist the page configuration after modification. Set different version states for the page version, including default, official, grayscale, and draft.
[0024] Furthermore, the data source of the component includes statically configured component parameters and / or a dynamic data source from a third-party interface.
[0025] Furthermore, the release page was launched, including:
[0026] When a page in the draft state is switched to the default or grayscale state, the default or grayscale page version with the original unique code of the same page is automatically set as the draft version, so that the page version in the default or grayscale state is unique;
[0027] When a page in the draft state is switched to the official state, the official version with the same unique code and the same page tag configuration data is set as the draft version, so that the page version in the official version state and with the same page tag configuration data is unique;
[0028] The mobile application obtains the page configuration data to determine its uniqueness;
[0029] The mobile application obtains the page configuration data of the default or official version status based on the unique code of the page, sets the basic style of the page based on the page style configuration data, renders the page components from top to bottom based on the page layout configuration data, dynamically renders the component UI and adjusts the business logic based on the component configuration data, and dynamically renders the component display data based on the data binding configuration.
[0030] Furthermore, when the release page is online, the mobile application also requests the official version page configuration data corresponding to the corresponding page tag based on the specified business demand information, and performs matching and weighted calculations based on the page tag data of the basic information of the page and the weights of the page tag options to obtain the page version that best suits the current business scenario.
[0031] Furthermore, when the general components cannot meet the page generation requirements, secondary development based on component configuration is carried out, including:
[0032] Define the basic information of the customized component, including the component name, component unique code, component applicable channel, component introduction and sample diagram;
[0033] Define the component configuration of the customized component to describe the style, business logic and component display data of the customized component;
[0034] On the client side corresponding to the component applicable channel, configure the UI rendering and business logic of the customized component based on business requirements and component configuration information;
[0035] When configuring the page visualization, configure the customized components that have completed secondary development into the page layout, and complete the parameter configuration of the customized components according to business needs;
[0036] When rendering a page, the client corresponding to the component applicable channel detects whether there is a customized component in the page. If so, it renders the component UI according to the component parameter data and implements the corresponding business logic.
[0037] Furthermore, before step S105, the following steps are included:
[0038] Based on the unified Schema specification, all components in the common component library are rendered and adapted on the clients of various channels;
[0039] Based on the interaction configuration between component content and mobile applications, clients of various channels can adapt platform-specific interaction functions to the interaction.
[0040] After the page configuration is completed, copy the page configuration data generated based on the unified Schema specification, and paste the copied page configuration data in the visual mobile application page designer of the new other page channel.
[0041] A second aspect of the present invention provides a system for building a mobile application based on a low-code platform, the system being used to implement the method described in the first aspect, the system comprising a design subsystem and a rendering subsystem, the design subsystem comprising:
[0042] Visual mobile application page designer, which is used to complete page creation and preview by dragging and dropping page components provided by the component library, setting page layout, component parameters, dynamic data sources, interaction configuration, and page tags according to Schema specifications;
[0043] Mobile application Tab module, used to customize the bottom Tab bar of mobile applications and the rendering page when selected;
[0044] Tag configuration module, used to configure optional tag items on the page;
[0045] The custom component module is used to create custom components for dragging and dropping in the visual mobile application page designer;
[0046] Page template module, used to save page configuration data as page templates;
[0047] Dynamic data source management module, used to manage the third-party interface dynamic data source and its mapping relationship with component configuration data;
[0048] The rendering subsystem includes:
[0049] Mobile application base, including Hongmeng App, Android App, iOS App, WeChat Mini Program, and Alipay Mini Program;
[0050] Page rendering module, used to load page configuration data and dynamically render pages;
[0051] Page layout rendering module, used to dynamically render page component layout;
[0052] Component rendering module, dynamically rendering components based on Schema specifications;
[0053] The general component rendering module is based on the abstracted business models of general components of various mobile applications and dynamically renders general components based on component configuration data;
[0054] The customized software rendering module is used to build a general logic for processing customized component configuration information based on the Schema specification.
[0055] Compared with the prior art, the present invention has the following beneficial effects:
[0056] 1. The present invention defines a unified page configuration specification, uses a visual mobile application page designer, drags components, and adjusts page and component parameters to quickly create pages or adjust original online pages, thereby quickly launching mobile application pages, avoiding the lengthy process of mobile application development, construction, review, and release, reducing human development costs, and quickly responding to business changes.
[0057] 2. Based on the unified Schema specification defined in the present invention, the development function of customized components is realized. Developers can develop customized components according to special business requirements to meet the needs of page construction in various scenarios.
[0058] 3. The present invention realizes one-time configuration of the page and supports multi-terminal multiplexing, so that clients of different channels have a consistent UI and usage experience.
[0059] 4. The present invention is based on a page tag module and can realize accurate operation and push pages.
[0060] 5. The mobile application base natively supports low-code page rendering adaptation and supports interaction between pages and native capabilities of mobile platforms. BRIEF DESCRIPTION OF THE DRAWINGS
[0061] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only preferred embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0062] Figure 1 It is a schematic diagram of the overall process of a method for building a mobile application based on a low-code platform provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0063] The principles and features of the present invention are described below in conjunction with the accompanying drawings. The enumerated embodiments are only used to explain the present invention and are not used to limit the scope of the present invention.
[0064] Embodiment 1
[0065] Reference Figure 1 , this embodiment provides a method for building a mobile application based on a low-code platform, the method comprising the following steps:
[0066] S101. By abstracting common page UIs and business modules of mobile applications, a data model for defining common components is formed. The data model is data for describing the mobile application page UIs and business modules.
[0067] S102. Define a unified Schema specification to agree on specifications for describing page configuration, component configuration, and data rendering configuration.
[0068] S103. Define basic page information, which describes the page title, page code, page description, page channel and page tag. The page code is the unique identifier of the page. Page channels are divided into App (including Hongmeng, Android and iOS, and can be expanded to other system platform application types), mini-programs (including WeChat and Alipay, and can be expanded to other mini-program platform types) and h5 (applicable to modern mobile browsers).
[0069] S104, performing visual configuration of the page through a visual mobile application page designer;
[0070] S105. Release page is online.
[0071] In this embodiment, the page tag supports configuring multiple tag items. The configuration of the tag items includes the following steps:
[0072] S201. When defining basic information of a page, all configurable tag items are displayed through a tag configuration module. The configurable tag items include a display name, a unique code, and a weight.
[0073] S202: Configure configurable tag items and tag values according to business requirements. Exemplarily, the page tag data is an array, the array elements represent non-null value tag items, the array elements are object types, the cade of the object is the unique code of the tag item, and the value of the object is the value of the tag item.
[0074] As an optional implementation, the visual configuration of the page is performed through a visual mobile application page designer, including:
[0075] Configure the page layout generated according to the Schema specification. The page layout configuration includes page style configuration and component layout configuration. Page style configuration is used to describe the top, bottom, left, and right margins, background color, and background image related information of the current page; component layout configuration is used to describe the display order and hierarchical structure of components.
[0076] Exemplarily, the component layout configuration data is an array, the array elements represent components, and the mobile page components are arranged in a top-down order; the array elements are object types, the object type is the component category identifier, the code is the component unique code, and the id is the component unique identifier on the page, that is, the same type of components may be configured on the page, and their ids are different. Items is a list of sub-items, which is used to describe the style and data configuration information of repeated UI or business modules in the component.
[0077] Configure component parameters, including component style configuration, business attribute page style configuration and page display data configuration. Exemplarily, component parameters are JSON objects, the key of the JSON object is the unique identifier of the component parameter, and the value is the configuration data of the component parameter.
[0078] Data binding, including configuring the data source of the component. Exemplarily, the data source of the component includes statically configured component parameters and / or dynamic data sources from third-party interfaces. When adding a dynamic data source, it is necessary to configure the third-party interface link, request method, request parameters, and jolt rule configuration for converting response data into component configuration information; test and verify whether the third-party data can be normally obtained and converted into JSON data that complies with the component Schema specification. When configuring data binding, you can select a data source that complies with the current component Schema specification from the configured dynamic data source. The mobile application will apply the dynamic data obtained in real time from the dynamic data source when rendering the corresponding component.
[0079] Configure the interaction between component content and mobile applications, which is used to describe how to call the client capabilities opened by mobile applications to achieve corresponding business goals when a user clicks on a certain area of the component, such as jumping or redirecting pages, pulling up system phone calls, pulling up navigation, jumping to mini programs, jumping to native pages, or jumping to system photo albums.
[0080] Configure the persistent page and save the generated visualization page configuration information in the data storage layer to form the page version configuration.
[0081] Configure page versions. Users can quickly copy new page configurations to generate new page versions based on existing page version configurations, persist page configurations after modification, and set different version states for page versions, including default, official, grayscale, and draft. Draft version page configurations are only used for the development of page visualization configurations. Draft versions can be freely switched to default, official, or grayscale states.
[0082] As an optional implementation, the publishing page is online, specifically including:
[0083] When a page in the draft state is switched to the default or grayscale state, the default or grayscale page version with the original unique code of the same page is automatically set as the draft version, so that the page version in the default or grayscale state is unique;
[0084] When a page in the draft state is switched to the official state, the official version with the same unique code and the same page tag configuration data is set as the draft version, so that the page version in the official version state and with the same page tag configuration data is unique;
[0085] The mobile application obtains the page configuration data to determine its uniqueness;
[0086] Mobile applications (including apps, mini-programs, and h5 pages) obtain page configuration data of the default or official version status based on the page's unique code, set the basic page style based on the page style configuration data, render page components from top to bottom based on the page layout configuration data, dynamically render component UI and adjust business logic based on component configuration data, and dynamically render component display data based on data binding configuration.
[0087] As an optional implementation, in order to achieve the effect of displaying different pages for different people, when the release page goes online, the mobile application also requests the official version page configuration data corresponding to the corresponding page tag based on the specified business demand information, and performs matching and weighted calculations based on the page tag data of the basic information of the page and the weights of the page tag options to obtain the most accurate and most suitable page version for the current business scenario.
[0088] As an optional implementation method, when the general components cannot meet the page generation requirements, secondary development based on component configuration is performed, including:
[0089] Define the basic information of the customized component. The basic information of the customized component includes the component name, component unique code, component applicable channels (including App, mini program and h5, multiple selections are allowed), component introduction and example pictures.
[0090] Define the component configuration of the customized component. Define the component configuration according to business requirements to describe the style, business logic, component display data and other information of the customized component.
[0091] On the client corresponding to the component's applicable channel, configure the UI rendering and business logic of the customized component based on business requirements and component configuration information.
[0092] During the page visualization configuration, the customized components that have completed secondary development will be configured into the page layout, and the parameter configuration of the customized components will be completed according to business needs.
[0093] When rendering a page, the client corresponding to the component applicable channel detects whether there is a customized component in the page. If so, it renders the component UI according to the component parameter data and implements the corresponding business logic.
[0094] As an optional implementation, in order to achieve multi-terminal adaptation of the page, realize one-time configuration of the page and multiple clients can reuse it, before step S105, the following steps are also included:
[0095] Based on the unified Schema specification, all components in the common component library are rendered and adapted on the clients of various channels to ensure that the same type of components have consistent UI performance and business logic experience across multiple terminals (clients).
[0096] Based on the interaction configuration between component content and mobile applications, clients of various channels adapt platform-specific interaction functions to ensure that the same interaction type has consistent functions across multiple terminals and similar user experience.
[0097] After the page configuration is completed, copy the page configuration data generated based on the unified Schema specification, and paste the copied page configuration data in the new visual mobile application page designer of other page channels, so as to achieve one-time configuration and multi-terminal reuse.
[0098] As an optional implementation, in order to realize the rapid development and construction of similar pages or pages with similar layouts, the method further includes the following steps:
[0099] Select the completed page in the visual mobile application page designer;
[0100] Set the selected page as a page template, set the template name and template description;
[0101] When creating a new page, view all created page templates for the selected page channel, select one of the page templates, set other page information, and generate the corresponding page based on the selected page template. According to business needs, modify and adjust the page generated based on the page template in the visual mobile application page designer to complete the rapid development and construction of the page.
[0102] On the basis of the above-mentioned embodiment, in order to flexibly manage the mobile application tab page, including the displayed tab, clicking the rendered page corresponding to the tab includes the following steps:
[0103] Define the basic information of the mobile application tab set, including applicable channels (including apps, mini-programs, and h5 pages), notes, and multiple languages.
[0104] Define a Tab collection. Exemplarily, the Tab collection is an array, and the array elements are the configuration information of each Tab, including the Tab display name, Tab icon, Tab selected icon, Tab font color, Tab selected font color, font size, whether login is required, and the unique code of the page displayed when the user selects the current Tab.
[0105] After creating the Tab collection information, you can configure it online. When a user opens the mobile app or h5 page corresponding to the applicable channel, the online Tab collection configuration information will be obtained, and the bottom Tab bar will be evenly tiled from left to right in the order of the Tab collection array. When the user selects a Tab, the selected icon and font color will be switched, and the page content corresponding to the unique page code in the Tab configuration information will be dynamically rendered and displayed.
[0106] Embodiment 2
[0107] This embodiment provides a system for building mobile applications based on a low-code platform, the system is used to implement the method described in the aforementioned method embodiment, and the system includes a design subsystem and a rendering subsystem.
[0108] The design subsystem includes:
[0109] The visual mobile application page designer is used to complete page creation and preview according to Schema specifications by dragging and dropping page components provided by the component library, setting page layout, component parameters, dynamic data sources, interaction configuration, and page tags.
[0110] Mobile application Tab module, used to customize the bottom Tab bar of mobile applications and the rendering page when selected;
[0111] The tag configuration module is used to configure optional tag items on the page.
[0112] The custom component module is used to create custom components for dragging and dropping in the visual mobile application page designer.
[0113] The page template module is used to save page configuration data as page templates.
[0114] The dynamic data source management module is used to manage the third-party interface dynamic data source and its mapping relationship with component configuration data.
[0115] The rendering subsystem includes:
[0116] Mobile application base, including Hongmeng App, Android App, iOS App, WeChat Mini Program, and Alipay Mini Program.
[0117] The page rendering module is used to load page configuration data and dynamically render pages.
[0118] Page layout rendering module, used to dynamically render page component layout.
[0119] The component rendering module dynamically renders components based on the Schema specification.
[0120] The universal component rendering module is based on the abstracted universal component business models of various mobile applications and dynamically renders universal components based on component configuration data.
[0121] Exemplarily, the general components include:
[0122] Image types: image sliding component, image carousel component, image tile component, and double-column tile component.
[0123] Text type: text area component, text list component.
[0124] Title type: main title component, subtitle component, text list component.
[0125] Graphics and text types: grid component, horizontal grid component, graphic and text area component, graphic and text details component, graphic and text horizontal component, graphic and text vertical component, and graphic and text carousel component.
[0126] Separation type: separator component, blank component.
[0127] Container type: column container component, tab container component.
[0128] The customized software rendering module is used to build a general logic for processing customized component configuration information based on the Schema specification.
[0129] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims
1. A method and system for building mobile applications based on a low-code platform, characterized in that: The method comprises the following steps: S101, forming a data model for defining common components by abstracting common mobile application page UIs and business modules, where the data model is data describing mobile application page UIs and business modules; S102. Define a unified Schema specification to agree on the specification for describing page configuration, component configuration, and data rendering configuration; S103, define basic page information, where the basic page information describes page title, page code, page description, page channel and page tag; S104, performing visual configuration of the page through a visual mobile application page designer; S105. Release page is online.
2. According to a method for building a mobile application based on a low-code platform according to claim 1, it is characterized in that: Page tags include the configuration of multiple tag items. The configuration of tag items includes the following steps: S201. When defining basic information of a page, display all configurable tag items through a tag configuration module. The configurable tag items include a display name, a unique code, and a weight. S202: Configure configurable tag items and tag values according to business requirements.
3. According to the method of claim 1, the method for building a mobile application based on a low-code platform is characterized in that: Use the visual mobile application page designer to configure the page visually, including: Configure the page layout generated according to the Schema specification. The page layout configuration includes page style configuration and component layout configuration; Configure component parameters, including component style configuration, business attribute page style configuration, and page display data configuration; Data binding, including configuring the data source of the component; Configure the interaction between component content and mobile applications, which is used to describe how to call the client capabilities exposed by mobile applications to achieve corresponding business goals when users click on the component. Configure the persistent page and save the generated visualization page configuration information in the data storage layer to form the page version configuration; Configure the page version. Based on the existing page version configuration, copy the new page configuration to generate a new page version. Persist the page configuration after modification. Set different version states for the page version, including default, official, grayscale, and draft.
4. A method for building a mobile application based on a low-code platform according to claim 3, characterized in that: The data sources of the components include statically configured component parameters and / or dynamic data sources from third-party interfaces.
5. According to claim 3, a method for building a mobile application based on a low-code platform is characterized in that: The release page is online, including: When a page in the draft state is switched to the default or grayscale state, the default or grayscale page version with the original unique code of the same page is automatically set as the draft version, so that the page version in the default or grayscale state is unique; When a page in the draft state is switched to the official state, the official version with the same unique code and the same page tag configuration data is set as the draft version, so that the page version in the official version state and with the same page tag configuration data is unique; The mobile application obtains the page configuration data to determine its uniqueness; The mobile application obtains the page configuration data of the default or official version status based on the unique code of the page, sets the basic style of the page based on the page style configuration data, renders the page components from top to bottom based on the page layout configuration data, dynamically renders the component UI and adjusts the business logic based on the component configuration data, and dynamically renders the component display data based on the data binding configuration.
6. A method for building a mobile application based on a low-code platform according to claim 5, characterized in that: When the publishing page goes online, the mobile application also requests the official version of the page configuration data corresponding to the corresponding page tag based on the specified business demand information, and performs matching and weighted calculations based on the page tag data of the basic information of the page and the weights of the page tag options to obtain the page version that best suits the current business scenario.
7. A method for building a mobile application based on a low-code platform according to claim 1, characterized in that: When general components cannot meet the requirements of page generation, secondary development based on component configuration is carried out, including: Define the basic information of the customized component, including the component name, component unique code, component applicable channel, component introduction and sample diagram; Define the component configuration of the customized component to describe the style, business logic and component display data of the customized component; On the client side corresponding to the component applicable channel, configure the UI rendering and business logic of the customized component based on business requirements and component configuration information; When configuring the page visualization, configure the customized components that have completed secondary development into the page layout, and complete the parameter configuration of the customized components according to business needs; When rendering a page, the client corresponding to the component applicable channel detects whether there is a customized component in the page. If so, it renders the component UI according to the component parameter data and implements the corresponding business logic.
8. A method for building a mobile application based on a low-code platform according to claim 1, characterized in that: Before step S105, the following steps are included: Based on the unified Schema specification, all components in the common component library are rendered and adapted on the clients of various channels; Based on the interaction configuration between component content and mobile applications, clients of various channels can adapt platform-specific interaction functions to the interaction. After the page configuration is completed, copy the page configuration data generated based on the unified Schema specification, and paste the copied page configuration data in the visual mobile application page designer of the new other page channel.
9. A system for building mobile applications based on a low-code platform, characterized in that: The system is used to execute the method according to any one of claims 1 to 8, and the system comprises a design subsystem and a rendering subsystem, wherein the design subsystem comprises: Visual mobile application page designer, which is used to complete page creation and preview by dragging and dropping page components provided by the component library, setting page layout, component parameters, dynamic data sources, interaction configuration, and page tags according to Schema specifications; Mobile application Tab module, used to customize the bottom Tab bar of mobile applications and the rendering page when selected; Tag configuration module, used to configure optional tag items on the page; The custom component module is used to create custom components for dragging and dropping in the visual mobile application page designer; Page template module, used to save page configuration data as page templates; Dynamic data source management module, used to manage the third-party interface dynamic data source and its mapping relationship with component configuration data; The rendering subsystem includes: Mobile application base, including Hongmeng App, Android App, iOS App, WeChat Mini Program, and Alipay Mini Program; Page rendering module, used to load page configuration data and dynamically render pages; Page layout rendering module, used to dynamically render page component layout; Component rendering module, dynamically rendering components based on Schema specifications; The general component rendering module is based on the abstracted business models of general components of various mobile applications and dynamically renders general components based on component configuration data; The customized software rendering module is used to build a general logic for processing customized component configuration information based on the Schema specification.
