CN110908704A - Method and device for calling cross-platform native function of mobile terminal - Google Patents
Method and device for calling cross-platform native function of mobile terminal Download PDFInfo
- Publication number
- CN110908704A CN110908704A CN201911113120.1A CN201911113120A CN110908704A CN 110908704 A CN110908704 A CN 110908704A CN 201911113120 A CN201911113120 A CN 201911113120A CN 110908704 A CN110908704 A CN 110908704A
- Authority
- CN
- China
- Prior art keywords
- interface
- target
- platform
- mobile terminal
- function
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 71
- 230000006870 function Effects 0.000 claims description 173
- 230000008569 process Effects 0.000 claims description 7
- 238000012545 processing Methods 0.000 claims description 4
- 238000011161 development Methods 0.000 abstract description 34
- 238000010586 diagram Methods 0.000 description 6
- 230000008901 benefit Effects 0.000 description 2
- 238000009877 rendering Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000002035 prolonged effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a method and a device for calling a cross-platform native function of a mobile terminal, and the method and the device are used for obtaining an application request, wherein the application request is used for indicating calling of the native function of the mobile terminal platform, and the application request comprises preset interface parameters. And determining the type of the mobile terminal platform according to the application request. And determining a target interface based on the type of the mobile terminal platform. The target interface is an interface corresponding to the type of the mobile terminal platform in each pre-packaged interface, and the interface is used for communicating with a native function plug-in of the mobile terminal platform. And calling the native function corresponding to the interface parameter by using the target interface. According to the method and the device, the type of the mobile terminal platform is determined according to the application request, and for different types of mobile terminal platforms, the native function corresponding to the interface parameter related to the application request is called by using the corresponding interface packaged in advance, so that the calling of the native function of the mobile terminal across platforms is realized, the code development amount of the application is effectively reduced, and the development cost and the development period of the application are reduced.
Description
Technical Field
The application relates to the field of cross-platform mobile application development, in particular to a method and a device for calling cross-platform native functions of a mobile terminal.
Background
Mobile end platforms aimed at mobile application development are many, for example, popular Android system platforms and iOS system platforms. When application development is performed on different mobile end platforms, corresponding application versions, such as an Android application version and an iOS application version, are usually developed by using a native language provided by the mobile end platform. However, the same application is developed into two or even more application versions, so that the development cost is obviously increased, the development period is prolonged, and the economic benefit of the application is influenced.
At present, a framework of a mobile end cross-platform is adopted, and the same application is developed aiming at different mobile end platforms. Based on the framework of the cross-platform of the mobile terminal, when the application is run on the mobile terminal platform, the running of the application is supported by calling the native function (such as acquiring equipment information, dialing a telephone, calling a network interface and the like) of the mobile terminal platform, so that the code development amount of the application is reduced. However, the script languages of different mobile end platforms are different from each other, that is, since the mobile end platforms to be docked are different, it is also necessary to develop multiple versions for the application. Therefore, the development cost still increases, the development period is still too long, and the economic benefit of the application is not improved.
Disclosure of Invention
The application provides a method and a device for calling a cross-platform native function of a mobile terminal, and aims to solve the problems of high application development cost and long development period.
In order to achieve the above object, the present application provides the following technical solutions:
a method for calling a native function of a mobile terminal cross-platform comprises the following steps:
acquiring an application request, wherein the application request is used for indicating to call a native function of a mobile terminal platform and comprises preset interface parameters;
determining the type of the mobile terminal platform according to the application request;
determining a target interface based on the type of the mobile terminal platform, wherein the target interface is an interface corresponding to the type of the mobile terminal platform in each pre-packaged interface and is used for communicating with the mobile terminal platform;
and calling the native function corresponding to the interface parameter by using the target interface.
Optionally, in the method for calling the cross-platform native function of the mobile terminal, the mobile terminal platform is any one of an Android system platform, an iOS system platform and a web system platform.
Optionally, in the method for calling a native function of a mobile end cross-platform, the calling a native function corresponding to the interface parameter by using the target interface includes:
determining a target method in a target class based on the interface parameters, wherein the target class is a class corresponding to the native function in each class indicated by a function module of the mobile terminal platform, and the target method is a method corresponding to the native function in each method of the target class;
and calling a target method in the target class by using the target interface.
Optionally, in the method for calling a native function of a mobile-end cross-platform, the interface parameter indicates a unique native function.
Optionally, in the method for calling the native function of the mobile end cross-platform, the interface is used for a process of communicating with the mobile end platform, and the process includes:
and sending an access request to a function plug-in of the mobile terminal platform through the interface, so that the function plug-in calls a native function corresponding to the access request, wherein each function plug-in calls a unique native function.
Optionally, in the method for calling a native function of a mobile end cross-platform, the calling a native function corresponding to the interface parameter by using the target interface includes:
and sending an access request to a target function plug-in by using the target interface, so that the target function plug-in calls a target native function, wherein the target function plug-in is the function plug-in indicated by the application request, and the target native function is the native function corresponding to the interface parameter.
An apparatus for invoking native functions of a mobile end-to-end platform, comprising:
the mobile terminal comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring an application request, the application request is used for indicating to call a native function of a mobile terminal platform, and the application request comprises preset interface parameters;
a first determining unit, configured to determine a type of the mobile end platform according to the application request;
a second determining unit, configured to determine a target interface based on a type of the mobile end platform, where the target interface is an interface corresponding to the type of the mobile end platform in each interface that is packaged in advance, and the interface is used for communicating with the mobile end platform;
and the calling unit is used for calling the native function corresponding to the interface parameter by using the target interface.
Optionally, in the invoking device for native functions of a mobile end cross-platform, the invoking unit is specifically configured to:
determining a target method in a target class based on the interface parameters, wherein the target class is a class corresponding to the native function in each class indicated by a function module of the mobile terminal platform, and the target method is a method corresponding to the native function in each method of the target class; and calling a target method in the target class by using the target interface.
Optionally, in the invoking device for native functions of a mobile end cross-platform, the invoking unit is specifically configured to:
and sending an access request to a target function plug-in by using the target interface, so that the target function plug-in calls a target native function, wherein the target function plug-in is the function plug-in indicated by the application request, and the target native function is the native function corresponding to the interface parameter.
A mobile terminal application, the mobile terminal application comprises a stored program, wherein the program executes a calling method of the mobile terminal cross-platform native function.
The method and the device for calling the cross-platform native function of the mobile terminal obtain an application request, wherein the application request is used for indicating calling of the native function of the mobile terminal platform and comprises preset interface parameters. And determining the type of the mobile terminal platform according to the application request. And determining a target interface based on the type of the mobile terminal platform. The target interface is an interface corresponding to the type of the mobile terminal platform in each pre-packaged interface, and the interface is used for communicating with a native function plug-in of the mobile terminal platform. And calling the native function corresponding to the interface parameter by using the target interface. According to the application, the type of the mobile end platform is determined according to the application request, and the native function corresponding to the interface parameter related to the application request is called by using the corresponding interface packaged in advance aiming at different types of mobile end platforms. Therefore, the same native function on different types of mobile end platforms can be called only by developing the application with the only version, the calling of the native function of the mobile end cross-platform is realized, the code development amount of the application is effectively reduced, and the development cost and the development period of the application are reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application 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 some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic diagram of a method for calling a cross-platform native function of a mobile terminal according to an embodiment of the present application;
fig. 2 is a schematic diagram illustrating a specific implementation manner of invoking native functions corresponding to interface parameters by using a target interface according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an apparatus for invoking native functions of a mobile end cross-platform according to an embodiment of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, 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 application.
As can be seen from the background art, when the native function of the mobile end platform is called in the prior art, different versions of calling programs or applications need to be developed for different types of mobile end platforms, the cost of the whole application development still increases, and the development period is still too long. Therefore, the application provides a method for calling the native function of the mobile terminal cross-platform, which realizes that the same native function is called on different types of mobile terminal platforms aiming at the application of the unique version, thereby avoiding additional development of applications or calling programs of other versions.
As shown in fig. 1, a schematic diagram of a method for calling a native function of a mobile end cross-platform provided in an embodiment of the present application includes the following steps:
s101: an application request is obtained.
The application request is used for indicating to call the native function of the mobile terminal platform, and the application request comprises preset interface parameters. Native functions specifically refer to: the mobile terminal platform provides application functions for the mobile terminal, such as application functions of acquiring device information, acquiring network information, calling a network interface, positioning, making a call, sending a short message, and the like.
Optionally, the interface parameter indicates a unique native function.
It should be noted that the interface parameters corresponding to the same native function on different types of mobile end platforms are consistent. For example, if the interface parameter corresponding to the "make call" function on the Android system platform is 1, the interface parameter corresponding to the "make call" function on the iOS system platform is also 1.
S102: and determining the type of the mobile terminal platform according to the application request.
The types of the mobile end platform include, but are not limited to: any one of an Android system platform, an iOS system platform and a web system platform.
S103: and determining a target interface based on the type of the mobile terminal platform.
The target interface is an interface corresponding to the type of the mobile terminal platform in each pre-packaged interface, and the interface is used for communicating with the mobile terminal platform. The interfaces corresponding to different types of mobile end platforms are different from each other, for example, an Android system platform corresponds to an Android interface, and an iOS system platform corresponds to an iOS interface.
It should be noted that the native Software Development Kit (SDK) of the mobile platform provides a basis for communicating with the mobile platform through an interface. The development language of the interface may be a script language such as Javascript and LUA, and the embodiment of the application is not limited.
Optionally, the process of the interface for communicating with the mobile terminal platform includes:
and sending an access request to a function plug-in of the mobile terminal platform through the interface, so that the function plug-in calls a native function corresponding to the access request. Wherein each functional plug-in calls a unique native function.
It should be noted that, an interface (for example, an Android interface or an iOS interface) is used to send an access request to a corresponding functional plug-in under the mobile platform, for example, the Android interface is used to send an access request to a functional plug-in of an Android system platform, or the iOS interface is used to send an access request to a functional plug-in of an iOS system platform. In addition, the technical means of the function plug-in provided by the mobile terminal platform to call the corresponding native function is common knowledge in the technical field, and is not described herein again.
S104: and calling the native function corresponding to the interface parameter by using the target interface.
The interface parameters of the same native function on the different types of mobile end platforms are consistent, and the corresponding target interfaces are inconsistent.
Specifically, the interface parameter of the "send message" function of the Android system platform is 1, and the interface parameter of the "send message" function of the IOS system platform is also 1. Therefore, for the Android system platform, the Android interface is used for calling the function of sending short messages. And for the IOS system platform, an IOS interface is utilized to call a short message sending function.
It should be noted that the above specific implementation process is only for illustration.
Optionally, a specific implementation manner of the process of calling the native function corresponding to the interface parameter by using the target interface may refer to the following explanation shown in fig. 2 and fig. 2.
In the embodiment of the application, an application request is obtained, where the application request is used to instruct to invoke a native function of a mobile end platform, and the application request includes preset interface parameters. And determining the type of the mobile terminal platform according to the application request. And determining a target interface based on the type of the mobile terminal platform. The target interface is an interface corresponding to the type of the mobile terminal platform in each pre-packaged interface, and the interface is used for communicating with a native function plug-in of the mobile terminal platform. And calling the native function corresponding to the interface parameter by using the target interface. According to the application, the type of the mobile end platform is determined according to the application request, and the native function corresponding to the interface parameter related to the application request is called by using the corresponding interface packaged in advance aiming at different types of mobile end platforms. Therefore, the same native function on different types of mobile end platforms can be called only by developing the application with the only version, the calling of the native function of the mobile end cross-platform is realized, the code development amount of the application is effectively reduced, and the development cost and the development period of the application are reduced.
Optionally, as shown in fig. 2, a schematic diagram of a specific implementation manner of invoking a native function corresponding to an interface parameter by using a target interface provided in an embodiment of the present application includes the following steps:
s201: and determining a target method in the target class based on the interface parameters.
The target class is a class corresponding to the native function in each class indicated by the function module of the mobile terminal platform, and the target method is a method corresponding to the native function in each method of the target class.
It should be noted that the interface parameters of the same native function on different types of mobile end platforms are consistent, but the target class and/or the target method corresponding to the native function may be different.
Specifically, the interface parameter corresponding to the "location" function of the Android system platform is 2, and the interface parameter corresponding to the "location" function of the IOS platform is also 2. However, the "location" function of the Android system platform corresponds to the first method in the first class, and the "location" function of the IOS system platform corresponds to the first method in the second class.
It should be noted that the above specific implementation process is only for illustration.
S202: and sending an access request to the target function plug-in by using the target interface, so that the target function plug-in calls a target method in the target class.
The target function plug-in is a function plug-in indicated by the application request, and the target native function is a native function corresponding to the interface parameter.
It should be noted that different types of mobile end platforms use different interfaces, and an interface corresponding to any type of mobile end platform has a problem, and the use of interfaces corresponding to other types of mobile end platforms and the normal use of native functions of the mobile end platform are not affected. Thus, the workload of the later application maintenance is reduced.
In the embodiment of the application, a target method in a target class is determined based on interface parameters, and an access request is sent to a target function plug-in by using a target interface, so that the target function plug-in calls the target method in the target class. Therefore, native functions corresponding to the same interface parameters on different types of mobile end platforms are realized only by using different interfaces, new applications or calling programs do not need to be additionally re-developed for the different types of mobile end platforms, calling of the native functions of the mobile end cross-platform is realized, code development amount of the applications is reduced, and development cost and development period of the applications are reduced.
Corresponding to the method for calling the native function of the cross-platform of the mobile end provided by the embodiment of the present application, as shown in fig. 3, a schematic structural diagram of a device for calling the native function of the cross-platform of the mobile end provided by the embodiment of the present application includes:
the obtaining unit 100 is configured to obtain an application request, where the application request is used to instruct to invoke a native function of the mobile end platform, and the application request includes preset interface parameters.
The first determining unit 200 is configured to determine the type of the mobile end platform according to the application request.
A second determining unit 300, configured to determine a target interface based on the type of the mobile platform, where the target interface is an interface corresponding to the type of the mobile platform in each interface that is packaged in advance, and the interface is used for communicating with the mobile platform.
The invoking unit 400 is configured to invoke, by using the target interface, the native function corresponding to the interface parameter.
The specific implementation manner of the calling unit 400 using the target interface to call the native function corresponding to the interface parameter includes: and determining a target method in a target class based on the interface parameters, wherein the target class is a class corresponding to the native function in each class indicated by a function module of the mobile terminal platform, and the target method is a method corresponding to the native function in each method of the target class. And calling a target method in the target class by using the target interface.
The specific implementation manner of the calling unit 400 using the target interface to call the native function corresponding to the interface parameter includes: and sending an access request to the target function plug-in by using the target interface so that the target function plug-in calls the target native function. The target function plug-in is a function plug-in indicated by the application request, and the target native function is a native function corresponding to the interface parameter.
In the embodiment of the application, an application request is obtained, where the application request is used to instruct to invoke a native function of a mobile end platform, and the application request includes preset interface parameters. And determining the type of the mobile terminal platform according to the application request. And determining a target interface based on the type of the mobile terminal platform. The target interface is an interface corresponding to the type of the mobile terminal platform in each pre-packaged interface, and the interface is used for communicating with a native function plug-in of the mobile terminal platform. And calling the native function corresponding to the interface parameter by using the target interface. According to the application, the type of the mobile end platform is determined according to the application request, and the native function corresponding to the interface parameter related to the application request is called by using the corresponding interface packaged in advance aiming at different types of mobile end platforms. Therefore, the same native function on different types of mobile end platforms can be called only by developing the application with the only version, the calling of the native function of the mobile end cross-platform is realized, the code development amount of the application is effectively reduced, and the development cost and the development period of the application are reduced.
Optionally, based on the method and the device for calling the cross-platform native function of the mobile terminal provided in the embodiment of the present application, an embodiment of the present application further provides a mobile terminal application. The mobile-side application includes a stored program, wherein the program performs the steps of:
the method comprises the steps of obtaining an application request, wherein the application request is used for indicating to call the native function of the mobile terminal platform, and the application request comprises preset interface parameters. And determining the type of the mobile terminal platform according to the application request. And determining a target interface based on the type of the mobile terminal platform, wherein the target interface is an interface corresponding to the type of the mobile terminal platform in each pre-packaged interface, and the interface is used for communicating with the mobile terminal platform. And calling the native function corresponding to the interface parameter by using the target interface.
It should be noted that, in the embodiment of the present application, the mobile end application is developed based on the IPU framework. The IPU framework provides loading and rendering conditions of the mobile terminal across the platform front-end interface for the mobile terminal application, so that the mobile terminal application does not need to perform secondary development aiming at the loading and rendering of the front-end interface, and the code development amount of the whole mobile terminal application is reduced.
It should be emphasized that, based on the method for calling the cross-platform native function of the mobile terminal provided in the embodiment of the present application, only a mobile terminal application of a unique version needs to be developed, and the mobile terminal application can realize calling of the same native function (for example, a "send short message" function provided by both an Android system platform and an IOS system platform) on different types of mobile terminal platforms. Therefore, mobile end applications of different versions do not need to be developed for different types of mobile end platforms (such as an Android system platform and an IOS system platform), and only a unique version is released to a large number of users. Therefore, the code development amount of the application is reduced, and the development cost and the development period of the application are reduced.
In addition, the mobile terminal platform provides a large number of native functions, so that the requirements of the user on the mobile terminal application are completely met, and a new functional program does not need to be additionally written for the mobile terminal application. In addition, as the native function of the mobile terminal platform is executed, the response speed of the mobile terminal application is obviously improved, and the use experience of the user is improved.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. 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 application. Thus, the present application 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 (10)
1. A method for calling a native function of a mobile terminal cross-platform is characterized by comprising the following steps:
acquiring an application request, wherein the application request is used for indicating to call a native function of a mobile terminal platform and comprises preset interface parameters;
determining the type of the mobile terminal platform according to the application request;
determining a target interface based on the type of the mobile terminal platform, wherein the target interface is an interface corresponding to the type of the mobile terminal platform in each pre-packaged interface and is used for communicating with the mobile terminal platform;
and calling the native function corresponding to the interface parameter by using the target interface.
2. The method according to claim 1, wherein the mobile-end platform is any one of an Android system platform, an iOS system platform and a web system platform.
3. The method according to claim 1, wherein the invoking, by the target interface, the native function corresponding to the interface parameter comprises:
determining a target method in a target class based on the interface parameters, wherein the target class is a class corresponding to the native function in each class indicated by a function module of the mobile terminal platform, and the target method is a method corresponding to the native function in each method of the target class;
and calling a target method in the target class by using the target interface.
4. The method of claim 1, wherein the interface parameter indicates a unique native function.
5. The method of claim 1, wherein the interface is used for a process of communicating with the mobile end platform, and comprises:
and sending an access request to a function plug-in of the mobile terminal platform through the interface, so that the function plug-in calls a native function corresponding to the access request, wherein each function plug-in calls a unique native function.
6. The method according to claim 5, wherein the invoking, by the target interface, the native function corresponding to the interface parameter comprises:
and sending an access request to a target function plug-in by using the target interface, so that the target function plug-in calls a target native function, wherein the target function plug-in is the function plug-in indicated by the application request, and the target native function is the native function corresponding to the interface parameter.
7. A calling device for native functions of a mobile end cross-platform is characterized by comprising:
the mobile terminal comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring an application request, the application request is used for indicating to call a native function of a mobile terminal platform, and the application request comprises preset interface parameters;
a first determining unit, configured to determine a type of the mobile end platform according to the application request;
a second determining unit, configured to determine a target interface based on a type of the mobile end platform, where the target interface is an interface corresponding to the type of the mobile end platform in each interface that is packaged in advance, and the interface is used for communicating with the mobile end platform;
and the calling unit is used for calling the native function corresponding to the interface parameter by using the target interface.
8. The apparatus according to claim 7, wherein the invoking unit is specifically configured to:
determining a target method in a target class based on the interface parameters, wherein the target class is a class corresponding to the native function in each class indicated by a function module of the mobile terminal platform, and the target method is a method corresponding to the native function in each method of the target class; and calling a target method in the target class by using the target interface.
9. The apparatus according to claim 7, wherein the invoking unit is specifically configured to:
and sending an access request to a target function plug-in by using the target interface, so that the target function plug-in calls a target native function, wherein the target function plug-in is the function plug-in indicated by the application request, and the target native function is the native function corresponding to the interface parameter.
10. A mobile-side application, characterized in that the mobile-side application comprises a stored program, wherein the program executes the method for calling the native function of the mobile-side cross-platform of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911113120.1A CN110908704A (en) | 2019-11-14 | 2019-11-14 | Method and device for calling cross-platform native function of mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911113120.1A CN110908704A (en) | 2019-11-14 | 2019-11-14 | Method and device for calling cross-platform native function of mobile terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110908704A true CN110908704A (en) | 2020-03-24 |
Family
ID=69816609
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911113120.1A Pending CN110908704A (en) | 2019-11-14 | 2019-11-14 | Method and device for calling cross-platform native function of mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110908704A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112035097A (en) * | 2020-08-25 | 2020-12-04 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | C + + adaptation layer based on Yinhua operation system of Galaxy |
| CN112882690A (en) * | 2021-01-28 | 2021-06-01 | 北京字节跳动网络技术有限公司 | Application development method and device |
| CN113515895A (en) * | 2021-07-30 | 2021-10-19 | 北京中网易企秀科技有限公司 | Cross-platform model prediction method and device |
| CN114416202A (en) * | 2022-01-17 | 2022-04-29 | 赞同科技股份有限公司 | Mobile terminal SDK calling method and system |
| WO2022213496A1 (en) * | 2021-04-09 | 2022-10-13 | 武汉天喻信息产业股份有限公司 | Method for accessing nfc smart card by using web application program, and middleware |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104572042A (en) * | 2013-10-15 | 2015-04-29 | 航天信息股份有限公司 | Cross-platform middleware device of mobile terminal equipment and implementation method of cross-platform middleware device of mobile terminal equipment |
| CN104636147A (en) * | 2015-03-09 | 2015-05-20 | 北京恒华伟业科技股份有限公司 | Cross-platform mobile application implementation method and cross-platform mobile application implementation system |
| KR101684454B1 (en) * | 2015-07-02 | 2016-12-08 | 주식회사 엘지씨엔에스 | Hybrid application and event handling method thereof |
| WO2017219833A1 (en) * | 2016-06-22 | 2017-12-28 | 中兴通讯股份有限公司 | Method and apparatus for developing and managing application program page |
| CN107870821A (en) * | 2016-09-26 | 2018-04-03 | 平安科技（深圳）有限公司 | The cross-platform call method and system of application program |
| CN107957911A (en) * | 2016-10-18 | 2018-04-24 | 腾讯科技（深圳）有限公司 | Method and apparatus, the method and apparatus of module data processing of component call |
| CN108694040A (en) * | 2017-02-15 | 2018-10-23 | 百度在线网络技术（北京）有限公司 | Calling processing method and device, communication system |
| US10296309B1 (en) * | 2018-01-25 | 2019-05-21 | Walmart Apollo, Llc | Systems and methods for automatic API generation for bi-directional communication between native and web-based components of a mobile application |
| CN109976831A (en) * | 2019-03-28 | 2019-07-05 | 山东浪潮通软信息科技有限公司 | Data interactive method between a kind of JavaScript and primary APP |
-
2019
- 2019-11-14 CN CN201911113120.1A patent/CN110908704A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104572042A (en) * | 2013-10-15 | 2015-04-29 | 航天信息股份有限公司 | Cross-platform middleware device of mobile terminal equipment and implementation method of cross-platform middleware device of mobile terminal equipment |
| CN104636147A (en) * | 2015-03-09 | 2015-05-20 | 北京恒华伟业科技股份有限公司 | Cross-platform mobile application implementation method and cross-platform mobile application implementation system |
| KR101684454B1 (en) * | 2015-07-02 | 2016-12-08 | 주식회사 엘지씨엔에스 | Hybrid application and event handling method thereof |
| WO2017219833A1 (en) * | 2016-06-22 | 2017-12-28 | 中兴通讯股份有限公司 | Method and apparatus for developing and managing application program page |
| CN107870821A (en) * | 2016-09-26 | 2018-04-03 | 平安科技（深圳）有限公司 | The cross-platform call method and system of application program |
| CN107957911A (en) * | 2016-10-18 | 2018-04-24 | 腾讯科技（深圳）有限公司 | Method and apparatus, the method and apparatus of module data processing of component call |
| CN108694040A (en) * | 2017-02-15 | 2018-10-23 | 百度在线网络技术（北京）有限公司 | Calling processing method and device, communication system |
| US10296309B1 (en) * | 2018-01-25 | 2019-05-21 | Walmart Apollo, Llc | Systems and methods for automatic API generation for bi-directional communication between native and web-based components of a mobile application |
| CN109976831A (en) * | 2019-03-28 | 2019-07-05 | 山东浪潮通软信息科技有限公司 | Data interactive method between a kind of JavaScript and primary APP |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112035097A (en) * | 2020-08-25 | 2020-12-04 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | C + + adaptation layer based on Yinhua operation system of Galaxy |
| CN112035097B (en) * | 2020-08-25 | 2023-10-13 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | C++ adaptation layer device based on Galaxy Ruihua operating system |
| CN112882690A (en) * | 2021-01-28 | 2021-06-01 | 北京字节跳动网络技术有限公司 | Application development method and device |
| CN112882690B (en) * | 2021-01-28 | 2024-04-19 | 抖音视界有限公司 | Application development method and device |
| WO2022213496A1 (en) * | 2021-04-09 | 2022-10-13 | 武汉天喻信息产业股份有限公司 | Method for accessing nfc smart card by using web application program, and middleware |
| CN113515895A (en) * | 2021-07-30 | 2021-10-19 | 北京中网易企秀科技有限公司 | Cross-platform model prediction method and device |
| CN113515895B (en) * | 2021-07-30 | 2024-03-01 | 北京中网易企秀科技有限公司 | Cross-platform model prediction method and device |
| CN114416202A (en) * | 2022-01-17 | 2022-04-29 | 赞同科技股份有限公司 | Mobile terminal SDK calling method and system |
| CN114416202B (en) * | 2022-01-17 | 2023-08-04 | 赞同科技股份有限公司 | Mobile terminal SDK calling method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110908704A (en) | Method and device for calling cross-platform native function of mobile terminal | |
| CN107967139B (en) | Hot updating method and device for game | |
| CN108647028B (en) | Application information processing method and device | |
| CN108345531A (en) | A kind of test method, apparatus and system | |
| CN104821954A (en) | Cross-platform remote procedure call method | |
| CN111212142A (en) | Service processing method, integrated open docking platform and computer storage medium | |
| CN104615462A (en) | Cross-platform mobile application generating server side and system | |
| CN104572054A (en) | Capability calling method and capability calling equipment | |
| CN104965723A (en) | Application program operation method and apparatus | |
| CN111625371A (en) | Text transmission method, device, PC (personal computer) terminal, mobile terminal and system | |
| CN108958785B (en) | Application program upgrading method and device | |
| CN111666199B (en) | Debugging method executed on intelligent terminal and software debugger | |
| JP2006211638A (en) | Scenario editing apparatus, dummy base station test simulator for wireless communication, dummy terminal test simulator for wireless communication, scenario editing method, test processing method, computer readable storage medium with program stored thereon, and program | |
| CN111050333A (en) | Base station automatic test method and system | |
| CN106294119B (en) | Test scheduling system and method and terminal equipment | |
| JP2005228183A (en) | Program execution method and computer system for executing the program | |
| CN110806856A (en) | Data loading method and device and electronic equipment | |
| CN106815006B (en) | Page calling method and device and page management server | |
| CN108009084B (en) | Testing method, device and system for hybrid mobile application | |
| CN111629020A (en) | Remote input method, device, PC (personal computer) terminal, android device and system | |
| CN108920218B (en) | Reflection calling method, device, terminal and computer readable storage medium | |
| CN111722850A (en) | Method, device and system for processing application among multiple systems | |
| CN113190565B (en) | Data updating method and device, storage medium and electronic device | |
| CN107704279B (en) | Data loading method and device | |
| CN115291933A (en) | Method, device and equipment for constructing small program data packet and storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200324 |
|
| RJ01 | Rejection of invention patent application after publication |