CN109271148B - Mobile application generation method and device - Google Patents
Mobile application generation method and device Download PDFInfo
- Publication number
- CN109271148B CN109271148B CN201811149536.4A CN201811149536A CN109271148B CN 109271148 B CN109271148 B CN 109271148B CN 201811149536 A CN201811149536 A CN 201811149536A CN 109271148 B CN109271148 B CN 109271148B
- Authority
- CN
- China
- Prior art keywords
- component
- mobile application
- native
- target
- specific
- 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.)
- Active
Links
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/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Telephone Function (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a mobile application generation method and a mobile application generation device, which are used for determining a target mobile application platform to which a mobile application requested to be generated belongs by receiving a mobile application generation request; searching a target component set corresponding to the target mobile application platform based on a preset corresponding relation between the mobile application platform and the component set; the component set comprises at least one specific native component of the mobile application platform corresponding to the component set, wherein the specific native component indicates the commonality between the native components which represent the same meaning with the specific native component in different mobile application platforms; displaying at least one specific native component of the set of target components; the method comprises the steps of receiving selection operation of a specific native component in at least one specific native component to generate a view page for forming the mobile application, and further generating the mobile application, so that the development cost of the mobile application is reduced, and the condition that the operation and experience of the same mobile application distributed on different mobile application platforms are inconsistent is avoided.
Description
Technical Field
The invention relates to the technical field of computer software, in particular to a mobile application generation method and device.
Background
At present, mobile application platforms on the market are numerous (such as IOS, Android and the like), and the characteristics of native components of each mobile application platform are very different, so that the design and development of mobile applications for each mobile application platform independently will inevitably lead to a steep increase in the development cost of the mobile applications, and will cause inconsistent operation and experience of the mobile applications distributed on each mobile application platform.
In view of the above, it is an urgent need to provide a method and an apparatus for generating a mobile application to reduce the development cost of the mobile application and avoid the inconsistent operation and experience of the same mobile application distributed in different mobile application platforms.
Disclosure of Invention
In view of the above, the present invention provides a method and an apparatus for generating a mobile application, so as to reduce the development cost of the mobile application and avoid the situation that the operations and experiences of the same mobile application distributed on different mobile application platforms are inconsistent, which is a problem to be solved urgently.
The technical scheme is as follows:
a mobile application generation method, comprising:
receiving a mobile application generation request, and determining a target mobile application platform to which a mobile application generated by the request belongs;
searching a target component set corresponding to the target mobile application platform based on a preset corresponding relation between the mobile application platform and the component set; the component set comprises at least one specific native component of the mobile application platform corresponding to the component set, wherein the specific native component indicates the commonality between the native components which represent the same meaning with the specific native component in different mobile application platforms;
displaying at least one particular native component of the set of target components;
receiving a selection operation of a specific native component in the at least one specific native component, and generating a view page for composing the mobile application.
Preferably, the set of components further includes at least one generic component, the generic component in the set of components being generated in response to a selection and a business meaning assignment operation for any one or more specific native components of at least one specific native component in the set of components;
the displaying at least one particular native component of the set of target components, comprising: displaying at least one specific native component and at least one generic component in the set of target components;
the receiving a selection operation of a particular native component of the at least one particular native component, generating a view page for composing the mobile application, comprising: and receiving a selection operation of a specific native component and/or a general component in the at least one specific native component and the at least one general component, and generating a view page for composing the mobile application.
Preferably, the method for generating the component set includes:
determining each native component in different mobile application platforms;
determining target native components of different mobile application platforms representing the same meaning, and determining common characteristics among the target native components;
for each target native component, extracting code used for characterizing the common characteristics in the target native component, and generating a specific native component of the target native component; for each of the mobile application platforms, a particular native component of the respective target native components in the mobile application platform constitutes a component set corresponding to the mobile application platform.
Preferably, for each target native component, extracting the code in the target native component for characterizing the common features, and generating a specific native component of the target native component, includes:
for each target native component, extracting code used for characterizing the common characteristics in the target native component, and generating an initial specific native component of the target native component;
for each mobile application platform, giving the same style information to the initial specific native component of each native component in the mobile application platform, and generating the specific native component of the mobile application platform; the style information given to the initial specific one of the native components in different mobile application platforms is the same.
Preferably, the component set generating method further includes:
determining each particular native component in a set of components corresponding to the mobile application platform;
receiving selection operation of specific native components in the determined specific native components, and acquiring selected target specific native components;
generating a generic component comprised of each of the target-specific native components in response to a business meaning-assigning operation to each of the target-specific native components.
A mobile application generation apparatus, comprising:
a mobile application generation request receiving unit, configured to receive a mobile application generation request, and determine a target mobile application platform to which a mobile application requested to be generated belongs;
the target component set searching unit is used for searching a target component set corresponding to the target mobile application platform based on the preset corresponding relation between the mobile application platform and the component set; the component set comprises at least one specific native component of the mobile application platform corresponding to the component set, wherein the specific native component indicates the commonality between the native components which represent the same meaning with the specific native component in different mobile application platforms;
a target component set display unit for displaying at least one specific native component in the target component set;
and the mobile application generating unit is used for receiving a selection operation of a specific native component in the at least one specific native component and generating a view page for forming the mobile application.
Preferably, the set of components further includes at least one generic component, the generic component in the set of components being generated in response to a selection and a business meaning assignment operation for any one or more specific native components of at least one specific native component in the set of components;
the target component set display unit is specifically used for displaying at least one specific native component and at least one general component in the target component set;
the mobile application generating unit is specifically configured to receive a selection operation of a specific native component and/or a general component in the at least one specific native component and the at least one general component, and generate a view page for composing the mobile application.
Preferably, the system further comprises a component set generating unit, wherein the component set generating unit comprises:
the native component determining unit is used for determining each native component in different mobile application platforms;
the common characteristic determining unit is used for determining target native components which represent the same meaning by different mobile application platforms and determining common characteristics among the target native components;
the component set generating subunit is used for extracting the code which is used for characterizing the common features in each target native component, and generating a specific native component of the target native component; for each of the mobile application platforms, a particular native component of the respective target native components in the mobile application platform constitutes a component set corresponding to the mobile application platform.
Preferably, the component set generating subunit includes:
a first component set generating subunit, configured to, for each target native component, extract the code in the target native component for characterizing the common features, and generate an initial specific native component of the target native component;
the second component set generating subunit is used for giving the same style information to the initial specific native component of each native component in the mobile application platform aiming at each mobile application platform, and generating the specific native component of the mobile application platform; the style information given to the initial specific one of the native components in different mobile application platforms is the same.
Preferably, the component set generating unit further includes a general component generating unit, and the general component generating unit includes:
a specific native component determination unit for determining each specific native component in a set of components corresponding to the mobile application platform;
the specific native component selection unit is used for receiving selection operation of specific native components in the determined specific native components and acquiring selected target specific native components;
a common component generation subunit, configured to generate a common component configured from each of the target-specific native components in response to a business meaning assignment operation for each of the target-specific native components.
In the process of generating the mobile application, different component sets are provided for users according to different mobile application platforms to which the mobile application requested to be generated belongs, so that the users can generate the mobile application directly based on the displayed component sets, and further the development of the mobile application is realized under the condition of not switching the mobile application platforms (namely, the development of the separate mobile application is not required for different mobile application platforms), so that the development cost of the mobile application is reduced; and the component set comprises at least one specific native component of the mobile application platform corresponding to the component, wherein the specific native component indicates the commonality between the native components which represent the same meaning with the specific native component in different mobile application platforms, so that no difference exists between the specific native components which represent the same meaning in different mobile application platforms, and thus, the operation and experience of the same mobile application generated in different mobile application platforms are not inconsistent.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a mobile application generation method according to an embodiment of the present disclosure;
fig. 2 is a flowchart of another mobile application generation method provided in the embodiment of the present application;
fig. 3 is a flowchart of a method for generating a component set according to an embodiment of the present application;
FIG. 4 is a diagram illustrating a method for generating a specific native component according to an embodiment of the present disclosure;
FIG. 5 is a flowchart of another component set generation method provided in the embodiments of the present application;
FIG. 6 is a flowchart of a further component set generation method provided in the embodiments of the present application;
fig. 7 is a schematic structural diagram of a mobile application generating apparatus according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example (b):
in order to facilitate understanding of a mobile application generation method provided in the embodiments of the present application, some terms involved in the mobile application generation method will be explained first.
The mobile application platform refers to a mobile phone operating system, including but not limited to IOS, Android, and the like, and provides a basic environment for normal operation of a mobile phone application (the mobile phone application may be referred to as a mobile application).
Native components: the method refers to interface controls (buttons, text boxes and the like) provided by each mobile application platform, and the component attributes and the use standards are determined by the characteristics of each mobile application platform and are not influenced mutually. In a mobile application platform, a corresponding mobile application developed using native components runs most efficiently and the user experience is best.
The mobile application generation method provided by the embodiment of the present application is described in detail below with reference to the above terms, and specifically, please refer to fig. 1.
As shown in fig. 1, the method includes:
s101, receiving a mobile application generation request, and determining a target mobile application platform to which a mobile application generated by the request belongs;
in this embodiment of the present application, a mobile application generation request sent by a user may be received, and a mobile application platform to which a mobile application requested to be generated by the mobile application generation request belongs is determined (for convenience of distinction, the determined mobile application platform is referred to as a target mobile application platform temporarily).
For example, if the mobile application is an IOS mobile application, the mobile application platform to which the mobile application belongs is an IOS mobile application platform; and if the mobile application is the Android mobile application, the mobile application platform to which the mobile application belongs is the Android mobile application platform.
S102, searching a target component set corresponding to a target mobile application platform based on a preset corresponding relation between the mobile application platform and the component set; the component set comprises at least one specific native component of the mobile application platform corresponding to the component set, wherein the specific native component indicates the commonality between the native components which represent the same meaning with the specific native component in different mobile application platforms;
after the target mobile application platform to which the mobile application requested to be generated by the mobile application generation request belongs is determined, the preset corresponding relationship between the mobile application platform and the component set can be searched, and the component set corresponding to the target mobile application platform is searched (for convenience of distinguishing, the searched component set is temporarily referred to as a target component set).
In an embodiment of the application, the component set includes at least one specific native component of the mobile application platform corresponding to the component set, and the specific native component indicates commonality between native components of different mobile application platforms that characterize the same meaning as the specific native component.
For example, the correspondence between an IOS mobile application platform and an IOS component set is preset, and the correspondence between an Android mobile application platform and an Android component set is preset; if the target mobile application platform to which the mobile application requested to be generated belongs is determined to be the IOS mobile application platform, searching a preset corresponding relation between the mobile application platform and a component set, determining that the target component set corresponding to the target mobile application platform is the IOS component set, wherein the IOS component set comprises at least one specific native component of the IOS mobile application platform, and each specific native component in the IOS component set indicates the commonality between all native components which have the same meaning with the specific native component in all the mobile application platforms.
For example, if the mobile application platform 1, the mobile application platform 2, and the mobile application platform 3 exist, wherein the mobile application platform 1 corresponds to the component set 1, the mobile application platform 2 corresponds to the component set 2, and the mobile application platform 3 corresponds to the component set 3; for a particular native component of the set of components 1 corresponding to the mobile application platform 1, the particular native component indicates a commonality between the native component 1 of the mobile application platform 1 that characterizes the same meaning as the particular native component, the native component 2 of the mobile application platform 2 that characterizes the same meaning as the particular native component, and the native component 3 of the mobile application platform 3 that characterizes the same meaning as the particular native component. The commonality between the native component 1, the native component 2 and the native component 3 may be an intersection 1 of functions in the native component 1, the native component 2 and the native component 3, an intersection 2 of applicable scenarios in the native component 1, the native component 2 and the native component 3, and an intersection 3 of appearance patterns in the native component 1, the native component 2 and the native component 3; wherein the union of intersection 1, intersection 2 and intersection 3 can be regarded as the commonality between native component 1, native component 2 and native component 3.
The specific native component is a specific native component of the target mobile application platform, and the programming language of the specific native component is the same as the programming language supported by the target mobile application platform. For example, when a specific native component is a specific native component in the IOS mobile application platform, the programming language of the specific native component is a programming language supported by the IOS mobile application platform; when the specific native component is a specific native component in the Android mobile application platform, the programming language of the specific native component is a programming language supported by the Android mobile application platform.
S103, displaying at least one specific native component in the target component set;
in the embodiment of the application, after the target component set is determined, the target component set may be displayed to a user. That is, at least one specific native component of the set of target components is displayed to the user; wherein the displayed set of target components is operable by a user.
And S104, receiving a selection operation of a specific native component in the at least one specific native component, and generating a view page for forming the mobile application.
The mobile application is composed of at least one view page, and the generation mode of the view page in the mobile application can be as follows: and receiving a selection operation of a user on a specific native component in the displayed at least one specific native component so as to form the view page by the specific native component selected by the user.
Fig. 2 is a flowchart of another mobile application generation method according to an embodiment of the present application.
As shown in fig. 2, the method includes:
s201, receiving a mobile application generation request, and determining a target mobile application platform to which a mobile application generated by the request belongs;
s202, searching a target component set corresponding to a target mobile application platform based on a preset corresponding relation between the mobile application platform and the component set; the component set comprises at least one specific native component and at least one generic component of the mobile application platform corresponding to the component set;
in embodiments of the present application, a particular native component indicates commonality between various native components in different mobile application platforms that characterize the same meaning as the particular native component.
Optionally, the generic component of the set of components is generated in response to a selection of any one or more specific native components of the at least one specific native component of the set of components and the assignment of the business meaning to the operation.
For each component set, the component set may include at least one specific native component and at least one generic component, each generic component of the at least one generic component of the component set being generated in response to a selection and a business meaning assignment operation of any one or more specific native components of the at least one specific native component of the component set.
That is, if there exists a component set 1, the component set 1 includes a specific native component 1, a specific native component 2 and a specific native component 3, wherein a user may respond to a selection operation of any one or more specific native components of the specific native component 1, the specific native component 2 and the specific native component 3; and responding to the business meaning endowing operation of the selected specific native components by the user to generate a universal component in the component set 1. For example, a specific native component 1 (the specific native component 1 is a specific text-type component) and a specific native component 3 (the specific native component 3 is a specific picture-type component) in the component set 1 may be selected, and an operation may be given in response to a business meaning performed by a user on the specific native component 1 and the specific native component 3 to generate a pie chart presentation component (the pie chart presentation approach may be regarded as a general component in the component set 1).
S203, displaying at least one specific native component and at least one general component in the target component set;
s204, receiving selection operation of at least one specific native component and specific native components and/or general components in at least one general component, and generating a view page for composing the mobile application.
The mobile application is composed of at least one view page, and the generation mode of the view page in the mobile application can be as follows: and receiving a selection operation of the displayed at least one specific native component and a specific native component and/or a general component in the at least one general component to form the view page in the mobile application. For example, receiving a selection operation of a specific native component in the displayed at least one specific native component and at least one general component to compose the view page in the mobile application (in this case, the view page is composed of only the specific native component); or receiving a selection operation of the displayed at least one specific native component and a general component in the at least one general component to form the view page in the mobile application (at the moment, the view page only consists of the general components); or, receiving a selection operation of a specific native component and a general component in the displayed at least one specific native component and at least one general component to compose the view page in the mobile application (at this time, the view page is composed of the specific native component and the general component).
In order to facilitate understanding of the mobile application generation method provided in the embodiment of the present application, a detailed description will now be given of a generation method of a component set in the mobile application generation method provided in the embodiment of the present application.
Fig. 3 is a flowchart of a method for generating a component set according to an embodiment of the present application.
As shown in fig. 3, the method includes:
s301, determining each native component in different mobile application platforms;
in the embodiment of the application, each mobile application platform of a component set to be generated is determined; for example, if a component set corresponding to the IOS mobile application platform needs to be generated, each native component in the IOS mobile application platform needs to be determined; and if the component set corresponding to the Android mobile application platform needs to be generated, determining each native component in the Android mobile application platform.
The present application is described in terms of a component set corresponding to an IOS mobile application platform and a component set corresponding to an Android mobile application platform that need to be generated. Based on this, the native components in the IOS mobile application platform are determined and the native components in the Android mobile application platform are determined in step S301.
S302, determining target native components with the same meaning represented by different mobile application platforms, and determining common characteristics among the target native components;
in the embodiment of the application, different mobile application platforms are determined to represent all target native components with the same meaning, and common characteristics among all the target native components are determined. For example, the native component 11 in the IOS mobile application platform (the native component 11 is a text-type component) and the native component 21 in the Android mobile application platform (the native component 21 is a text-type component) may be determined as two target native components characterizing the same meaning, and thus, the common characteristic between the native component 11 and the native component 21 may be determined; the commonality characteristic between the native component 11 and the native component 21 indicates commonality between the native component 11 and the native component 21.
S303, extracting codes used for characterizing common features in the target native assemblies aiming at each target native assembly to generate specific native assemblies of the target native assemblies; for each mobile application platform, the specific native component of the target native components in the mobile application platform constitutes a component set corresponding to the mobile application platform.
In the embodiment of the present application, for a native component 11, extracting a code in the native component 11 for characterizing the common feature, and then constructing a specific native component 12 of the native component 11 from the extracted code in the native component 11 for characterizing the common feature (the specific native component 12 may be regarded as a specific text-type component in the IOS mobile application platform), where the specific native component 12 is a specific native component in a component set corresponding to the IOS mobile application platform; for a native component 21, code for characterizing a common feature in the native component 21 is extracted, and then a specific native component 22 of the native component 21 is formed by the extracted code for characterizing the common feature in the native component 21 (the specific native component 22 may be regarded as a specific text-class component in the Android mobile application platform), where the specific native component 22 is a specific native component in a component set corresponding to the Android mobile application platform.
Referring to fig. 4, fig. 4 is a schematic diagram of a method for generating a specific native component according to an embodiment of the present application. As can be seen from fig. 4, the text-type component (native component) in the IOS mobile application platform and the text-type component (native component) in the Android mobile application platform can be regarded as two target native components with the same meaning represented by different mobile application platforms, so as to determine the specific text-type component (specific native component) in the IOS mobile application platform and the characteristic text-type component (specific native component) in the Android mobile application platform; the method comprises the steps that a button type component (a native component) in an IOS mobile application platform and a button type component (a native component) in an Android mobile application platform are regarded as two target native components with the same meaning represented by different mobile application platforms, and then a specific button type component (a specific native component) in the IOS mobile application platform and a characteristic button type component (a specific native component) in the Android mobile application platform are determined; the picture component (native component) in the IOS mobile application platform and the picture component (native component) in the Android mobile application platform are regarded as two target native components with the same meaning represented by different mobile application platforms, and then the specific picture component (specific native component) in the IOS mobile application platform and the characteristic picture component (specific native component) in the Android mobile application platform are determined. Moreover, through research, it is found that there is one native component 4 in the IOS mobile application platform, and there is no native component in the Android mobile application platform that represents the same meaning as the native component 4, so that no operation is performed on the native component 4, that is, no specific native component of the native component 4 is generated.
Fig. 5 is a flowchart of another component set generation method provided in the embodiment of the present application.
As shown in fig. 5, the method includes:
s501, determining each native component in different mobile application platforms;
s502, determining target native components with the same meaning represented by different mobile application platforms, and determining common characteristics among the target native components;
the execution process of steps S501 to S502 provided in the embodiment of the present application is the same as the execution process of steps S301 to S302 provided in the above embodiment, and for the specific execution manner of steps S501 to S502, please refer to the detailed description of steps S301 to S302 in the above embodiment, which is not limited herein.
S503, extracting codes used for characterizing the common features in the target native assemblies aiming at each target native assembly, and generating initial specific native assemblies of the target native assemblies;
optionally, for each target native component, extracting code for characterizing the common features in the target native component, and constructing an initial specific native component of the target native component from the extracted code. For example, the specific native component 12 in the above embodiment may be regarded as an initial specific native component in the IOS mobile application platform, and the specific native component 22 in the above embodiment may be regarded as an initial specific native component in the Android mobile application platform.
S504, aiming at each mobile application platform, giving the same style information to the initial specific native component of each native component in the mobile application platform, and generating the specific native component of the mobile application platform; the style information given to the initial specific one of the native components in different mobile application platforms is the same.
In the embodiment of the present application, for each initial specific native component determined in step S503, style information is given to the initial specific native component to generate a specific native component of the initial specific native component; the style information given to each initial specific native component is the same for each initial specific native component determined in step S503.
For example, after a specific native component 12 is considered as an initial specific native component and style information is given to the initial specific native component, the specific native component may be generated, and the generated specific native component is a specific native component in the IOS mobile application platform; after a specific native component 22 is considered as an initial specific native component, and style information is given to the initial specific native component, a specific native component is generated, and the generated specific native component is a specific native component in the Android mobile application platform. Wherein the style information assigned to the particular native component 12 and the particular native component 22 is the same.
In the embodiment of the present application, preferably, the style information may be theme color, logo, and the like. The above is only a preferred mode of the style information provided in the embodiment of the present application, and the inventor may set the style information at will according to his own needs, which is not limited herein.
Further, fig. 6 is a flowchart of another component set generation method provided in the embodiment of the present application.
As shown in fig. 6, the method includes:
s601, determining each native component in different mobile application platforms;
s602, determining target native components with the same meaning represented by different mobile application platforms, and determining common characteristics among the target native components;
s603, extracting codes used for characterizing common features in the target native assemblies and generating specific native assemblies of the target native assemblies aiming at each target native assembly;
the execution process of steps S601-S603 provided in the embodiment of the present application is the same as the execution process of steps S301-S303 provided in the above embodiment, and for the specific execution mode of steps S601-S603, reference is made to the description of the execution process of steps S301-S303 in the above embodiment, which is not limited herein.
S604, determining each specific native component in the component set corresponding to the mobile application platform;
in the embodiment of the present application, for a mobile application platform, a specific native component of each target native component in the mobile application platform can be regarded as a specific native component in a corresponding component set of the mobile application platform.
If a user needs to generate a generic component of a mobile application platform for the mobile application platform, each specific native component in the mobile application platform needs to be determined first.
S605, receiving selection operation of specific native components in the determined specific native components, and acquiring selected target specific native components;
s606, responding to the business meaning endowing operation of each target specific native component, and generating a general component composed of each target specific native component.
For a mobile application platform, determining each specific native component in the mobile application platform, and if a general component in the mobile application platform needs to be generated, acquiring each specific native component selected by a user in response to a selection operation of the user on the specific native component in the mobile application platform (for convenience of distinction, each specific native component selected by the user is temporarily referred to as a target specific native component herein); and then, responding to the operation given by the user to the business meaning of each target specific native component, and giving the business meaning to each target specific native component, so that the universal component can be formed by each target specific native component given with the business meaning.
Fig. 7 is a schematic structural diagram of a mobile application generating apparatus according to an embodiment of the present application.
As shown in fig. 7, the apparatus includes:
a mobile application generation request receiving unit 71, configured to receive a mobile application generation request, and determine a target mobile application platform to which a mobile application requested to be generated belongs;
a target component set searching unit 72, configured to search a target component set corresponding to the target mobile application platform based on a preset correspondence between the mobile application platform and the component set; the component set comprises at least one specific native component of the mobile application platform corresponding to the component set, wherein the specific native component indicates the commonality between the native components which represent the same meaning with the specific native component in different mobile application platforms;
a target component set display unit 73 for displaying at least one specific native component in the target component set;
and a mobile application generating unit 74, configured to receive a selection operation on a specific native component of the at least one specific native component, and generate a view page for composing the mobile application.
In the embodiment of the present application, preferably, the component set further includes at least one common component, and the common component in the component set is generated in response to the selection and the business meaning assignment operation of any one or more specific native components in at least one specific native component in the component set; the target component set display unit is specifically used for displaying at least one specific native component and at least one general component in the target component set; and the mobile application generating unit is specifically used for receiving selection operation of at least one specific native component and at least one specific native component in the general components and/or the general components, and generating a view page for constituting the mobile application.
Further, an apparatus for generating a mobile application provided in an embodiment of the present application further includes a component set generating unit, where the component set generating unit includes:
the native component determining unit is used for determining each native component in different mobile application platforms;
the common characteristic determining unit is used for determining target native components with the same meaning represented by different mobile application platforms and determining common characteristics among the target native components;
the component set generation subunit is used for extracting codes used for characterizing the common features in the target native components and generating specific native components of the target native components; for each mobile application platform, the specific native component of the target native components in the mobile application platform constitutes a component set corresponding to the mobile application platform.
In the embodiment of the present application, preferably, the component set generating subunit includes:
the first component set generation subunit is used for extracting the code for characterizing the common features in the target native components and generating initial specific native components of the target native components;
the second component set generation subunit is used for endowing the initial specific native component of each native component in each mobile application platform with the same style information aiming at each mobile application platform, and generating the specific native component of the mobile application platform; the style information given to the initial specific one of the native components in different mobile application platforms is the same.
In this embodiment of the present application, preferably, the component set generating unit further includes a general component generating unit, and the general component generating unit includes:
a specific native component determination unit for determining each specific native component in the set of components corresponding to the mobile application platform;
the specific native component selection unit is used for receiving selection operation of specific native components in the determined specific native components and acquiring selected target specific native components;
a common component generation subunit for generating a common component configured by the target-specific native components in response to the business meaning assignment operation for each target-specific native component.
In the process of generating the mobile application, different component sets are provided for users according to different mobile application platforms to which the mobile application requested to be generated belongs, so that the users can generate the mobile application directly based on the displayed component sets, and further the development of the mobile application is realized under the condition of not switching the mobile application platforms (namely, the development of the separate mobile application is not required for different mobile application platforms), so that the development cost of the mobile application is reduced; and the component set comprises at least one specific native component of the mobile application platform corresponding to the component, wherein the specific native component indicates the commonality between the native components which represent the same meaning with the specific native component in different mobile application platforms, so that no difference exists between the specific native components which represent the same meaning in different mobile application platforms, and thus, the operation and experience of the same mobile application generated in different mobile application platforms are not inconsistent.
The method and the device for generating the mobile application provided by the invention are described in detail above, a specific example is applied in the text to explain the principle and the implementation of the invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include or include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (8)
1. A mobile application generation method, comprising:
receiving a mobile application generation request, and determining a target mobile application platform to which a mobile application generated by the request belongs;
searching a target component set corresponding to the target mobile application platform based on a preset corresponding relation between the mobile application platform and the component set; the component set comprises at least one specific native component of the mobile application platform corresponding to the component set, wherein the specific native component indicates the commonality between the native components which represent the same meaning with the specific native component in different mobile application platforms;
displaying at least one particular native component of the set of target components;
receiving a selection operation of a specific native component in the at least one specific native component, and generating a view page for composing the mobile application;
the set of components further includes at least one generic component, the generic component in the set of components generated in response to a selection and a business meaning assignment operation for any one or more specific native components in at least one specific native component in the set of components;
the displaying at least one particular native component of the set of target components, comprising: displaying at least one specific native component and at least one generic component in the set of target components;
the receiving a selection operation of a particular native component of the at least one particular native component, generating a view page for composing the mobile application, comprising: and receiving a selection operation of a specific native component and/or a general component in the at least one specific native component and the at least one general component, and generating a view page for composing the mobile application.
2. The method of claim 1, wherein the method for generating the set of components comprises:
determining each native component in different mobile application platforms;
determining target native components of different mobile application platforms representing the same meaning, and determining common characteristics among the target native components;
for each target native component, extracting code used for characterizing the common characteristics in the target native component, and generating a specific native component of the target native component; for each of the mobile application platforms, a particular native component of the respective target native components in the mobile application platform constitutes a component set corresponding to the mobile application platform.
3. The method of claim 2, wherein for each of the target native components, extracting code in the target native component for characterizing the common features, and generating a specific native component of the target native component comprises:
for each target native component, extracting code used for characterizing the common characteristics in the target native component, and generating an initial specific native component of the target native component;
for each mobile application platform, giving the same style information to the initial specific native component of each native component in the mobile application platform, and generating the specific native component of the mobile application platform; the style information given to the initial specific one of the native components in different mobile application platforms is the same.
4. The method of claim 3, wherein the component set generation method further comprises:
determining each particular native component in a set of components corresponding to the mobile application platform;
receiving selection operation of specific native components in the determined specific native components, and acquiring selected target specific native components;
generating a generic component comprised of each of the target-specific native components in response to a business meaning-assigning operation to each of the target-specific native components.
5. A mobile application generation apparatus, comprising:
a mobile application generation request receiving unit, configured to receive a mobile application generation request, and determine a target mobile application platform to which a mobile application requested to be generated belongs;
the target component set searching unit is used for searching a target component set corresponding to the target mobile application platform based on the preset corresponding relation between the mobile application platform and the component set; the component set comprises at least one specific native component of the mobile application platform corresponding to the component set, wherein the specific native component indicates the commonality between the native components which represent the same meaning with the specific native component in different mobile application platforms;
a target component set display unit for displaying at least one specific native component in the target component set;
a mobile application generating unit, configured to receive a selection operation on a specific native component of the at least one specific native component, and generate a view page for composing the mobile application;
the set of components further includes at least one generic component, the generic component in the set of components generated in response to a selection and a business meaning assignment operation for any one or more specific native components in at least one specific native component in the set of components;
the target component set display unit is specifically used for displaying at least one specific native component and at least one general component in the target component set;
the mobile application generating unit is specifically configured to receive a selection operation of a specific native component and/or a general component in the at least one specific native component and the at least one general component, and generate a view page for composing the mobile application.
6. The apparatus of claim 5, further comprising a component set generation unit, the component set generation unit comprising:
the native component determining unit is used for determining each native component in different mobile application platforms;
the common characteristic determining unit is used for determining target native components which represent the same meaning by different mobile application platforms and determining common characteristics among the target native components;
the component set generating subunit is used for extracting the code which is used for characterizing the common features in each target native component, and generating a specific native component of the target native component; for each of the mobile application platforms, a particular native component of the respective target native components in the mobile application platform constitutes a component set corresponding to the mobile application platform.
7. The apparatus of claim 6, wherein the component set generation subunit comprises:
a first component set generating subunit, configured to, for each target native component, extract the code in the target native component for characterizing the common features, and generate an initial specific native component of the target native component;
the second component set generating subunit is used for giving the same style information to the initial specific native component of each native component in the mobile application platform aiming at each mobile application platform, and generating the specific native component of the mobile application platform; the style information given to the initial specific one of the native components in different mobile application platforms is the same.
8. The apparatus of claim 7, wherein the component set generating unit further comprises a generic component generating unit, and wherein the generic component generating unit comprises:
a specific native component determination unit for determining each specific native component in a set of components corresponding to the mobile application platform;
the specific native component selection unit is used for receiving selection operation of specific native components in the determined specific native components and acquiring selected target specific native components;
a common component generation subunit, configured to generate a common component configured from each of the target-specific native components in response to a business meaning assignment operation for each of the target-specific native components.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811149536.4A CN109271148B (en) | 2018-09-29 | 2018-09-29 | Mobile application generation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811149536.4A CN109271148B (en) | 2018-09-29 | 2018-09-29 | Mobile application generation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109271148A CN109271148A (en) | 2019-01-25 |
| CN109271148B true CN109271148B (en) | 2022-03-01 |
Family
ID=65195821
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811149536.4A Active CN109271148B (en) | 2018-09-29 | 2018-09-29 | Mobile application generation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109271148B (en) |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090013246A1 (en) * | 2007-04-27 | 2009-01-08 | Bea Systems, Inc. | Web based application constructor using extensibility points for page components, page layouts/templates, security roles, shells, and associating data spaces with templates |
| CN102654833A (en) * | 2012-02-01 | 2012-09-05 | 中兴通讯（香港）有限公司 | Mobile phone application development method and system |
| US8997038B2 (en) * | 2012-03-30 | 2015-03-31 | Anypresence, Inc. | Systems and methods for building and deploying mobile applications |
| US11216253B2 (en) * | 2014-10-03 | 2022-01-04 | Kony, Inc. | Application prototyping tool |
| CN104484189B (en) * | 2014-12-31 | 2018-07-10 | 北京拼图科技有限公司 | The structure and design method of a kind of application interface |
| CN104636147B (en) * | 2015-03-09 | 2016-05-25 | 北京恒华伟业科技股份有限公司 | A kind of implementation method and system of cross-platform mobile application |
| CN104714830B (en) * | 2015-04-03 | 2018-03-30 | 普元信息技术股份有限公司 | The system and method for cross-platform exploitation is realized based on primary development language |
| CN105302558A (en) * | 2015-11-03 | 2016-02-03 | 北京京东尚科信息技术有限公司 | Content presentation system and method for multiple clients |
| CN106873991B (en) * | 2017-01-20 | 2019-01-11 | 腾讯科技（深圳）有限公司 | Page generation method and device |
| CN107577459B (en) * | 2017-08-21 | 2020-11-13 | 杰为软件系统(深圳)有限公司 | Dragging type cross-platform application development system and method based on componentization |
-
2018
- 2018-09-29 CN CN201811149536.4A patent/CN109271148B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN109271148A (en) | 2019-01-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109600672B (en) | Video content pushing method and device | |
| US11157959B2 (en) | Multimedia information processing method, apparatus and system, and computer storage medium | |
| US20140156277A1 (en) | Information processing device and content retrieval method | |
| TW202110143A (en) | Method and device for displaying reply message | |
| CN112256225A (en) | Screen projection method, server, terminal device and computer readable storage medium | |
| CN113779307A (en) | Information display method and device, computer equipment and storage medium | |
| CN101634930A (en) | Terminal and method thereof for assisting user in operation | |
| CN109542878B (en) | List creation method and device | |
| CN112241397A (en) | Multimedia file sharing method and device, electronic equipment and readable storage medium | |
| CN105302786A (en) | Editing method and device for data | |
| CN108170785B (en) | Method and device for guiding terminal search operation and computer readable storage medium | |
| CN109815407B (en) | Information resource pushing method, device, equipment and storage medium | |
| CN105718147A (en) | Input method panel enabling method and device and input method and input method system | |
| JP2011141617A (en) | Web page browsing system, control method thereof, and relay server | |
| CN110933772A (en) | Connection method of wireless device, mobile terminal and computer readable storage medium | |
| CN104216750A (en) | Mobile terminal and method and device for quickly starting application of mobile terminal | |
| CN102902751A (en) | Webpage input method and device in mobile terminal and mobile terminal | |
| CN109271148B (en) | Mobile application generation method and device | |
| CN104683483A (en) | Information and Internet of things intercommunicating method and device | |
| CN110633391A (en) | Information searching method and device | |
| CN107357481B (en) | Message display method and message display device | |
| CN110620841B (en) | Information processing method, multi-screen terminal and computer readable storage medium | |
| CN111124714A (en) | Address information filling method, device and computer readable storage medium | |
| CN114047855B (en) | Form editing method and device and terminal equipment | |
| CN107368376B (en) | Message sending method and device, expansion method and terminal |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |