WO2016155388A1 - Procédé et dispositif d'installation et d'exécution d'application - Google Patents

Procédé et dispositif d'installation et d'exécution d'application Download PDF

Info

Publication number
WO2016155388A1
WO2016155388A1 PCT/CN2015/099591 CN2015099591W WO2016155388A1 WO 2016155388 A1 WO2016155388 A1 WO 2016155388A1 CN 2015099591 W CN2015099591 W CN 2015099591W WO 2016155388 A1 WO2016155388 A1 WO 2016155388A1
Authority
WO
WIPO (PCT)
Prior art keywords
plugin
plug
main application
application
main
Prior art date
Application number
PCT/CN2015/099591
Other languages
English (en)
Chinese (zh)
Inventor
许澎湃
郑相振
Original Assignee
北京奇虎科技有限公司
奇智软件（北京）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 北京奇虎科技有限公司, 奇智软件（北京）有限公司 filed Critical 北京奇虎科技有限公司
Publication of WO2016155388A1 publication Critical patent/WO2016155388A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating

Definitions

  • the present invention relates to the field of Internet applications, and in particular, to an application installation method and apparatus, and an application operation method and apparatus.
  • Android (Android) system has become one of the most commonly used operating systems for smart terminals due to its openness and compatibility.
  • the organizational structure of the Android system can be easily plugged and functionalized independently because of its good inter-component and inter-application communication mechanisms. However, these mechanisms are limited to installed applications.
  • the present invention has been made in order to provide an application mounting method, an application operating method, and a corresponding apparatus that overcome the above problems or at least partially solve the above problems.
  • an embodiment of the present invention provides an application installation method, including:
  • the main application is installed, wherein the main application can call different plugins according to requirements to implement different auxiliary functions.
  • an embodiment of the present invention further provides an application running method, including:
  • the plug-in corresponding to the selected plug-in identifier is invoked by the main application to implement a corresponding auxiliary function.
  • an embodiment of the present invention further provides an application installation apparatus, including:
  • a function determining module configured to determine, according to requirements, a plurality of types of functions to be implemented, wherein the plurality of types of functions include a primary function and an auxiliary function;
  • a classification configuration module configured to generate a main application for the main function, and generate a separate plug-in for each auxiliary function
  • the installation module is adapted to install the main application, wherein the main application can call different plugins according to requirements to implement different auxiliary functions.
  • an embodiment of the present invention further provides an application running device, including:
  • a startup module configured to open a main application having a main function, wherein the main application can invoke a plug-in having an auxiliary function other than the main function;
  • a selection module configured to select, according to requirements, a plug-in identifier corresponding to the auxiliary function in an interface of the main application
  • the calling module is adapted to use the plug-in corresponding to the selected plug-in identifier by the main application to implement a corresponding auxiliary function.
  • a computer program comprising computer readable code, when the computer readable code is run on a computing device, causing the computing device to perform any of the above described application installation methods, And/or, any of the above application execution methods.
  • a computer readable medium wherein the computer program described above is stored.
  • the functions corresponding to the requirements are divided into two categories, one is a main function implemented by the main application, and the other is an auxiliary function implemented by the plug-in.
  • the main application needs to be installed. If other auxiliary functions are needed, different plug-ins can be called in real time according to requirements by the main application to implement different auxiliary functions. That is, in the embodiment of the present invention, only the main application needs to be installed in an operating system in the form of a separate application, and the remaining plug-ins need not be installed to be used.
  • the main application can implement the corresponding function by calling the plug-in through a certain communication method.
  • the embodiments of the present invention divide the functions corresponding to the requirements, so that the requirements can be developed in a distributed manner, and each auxiliary function is implemented by a plug-in function, which can be directly used as a plug-in for other products, and further improves the practicability of the plug-in. .
  • the main application only the main application is installed, and the corresponding installation package only needs to contain the code and resources necessary for the application, which greatly reduces the application installation data package and can speed up the application installation data package.
  • the download process prevents the user from giving up the download by seeing the application too much, or giving up the download halfway because the download is too slow, which improves the user experience.
  • the plug-in since the plug-in is separated from the main application, the plug-in can be dynamically added, updated, and deleted according to the control command, and the system space can be fully utilized. And it is independent of the update process of the main application, and the update process of each plug-in is independent, thus making the update process more independent, and does not interfere with the update of other plug-ins or main applications.
  • FIG. 1 shows a process flow diagram of an application installation method in accordance with one embodiment of the present invention
  • FIG. 2 is a schematic diagram showing a specific example of an architecture between a main application and a plug-in according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram showing an interface of a plug-in display according to an embodiment of the present invention.
  • FIG. 4 shows a process flow diagram of an application mode of operation in accordance with one embodiment of the present invention
  • FIG. 5 is a schematic diagram showing a main application calling a plurality of plugins according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram showing a flow of implementing a plugin according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural view of an application mounting device according to an embodiment of the present invention.
  • FIG. 8 is a schematic view showing another structure of an application mounting device according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural view of an application running device according to an embodiment of the present invention.
  • Figure 10 is a schematic block diagram of a computing device for performing an application installation method and/or an application execution method in accordance with the present invention
  • Fig. 11 schematically shows a storage unit for holding or carrying program code implementing an application installation method and/or an application execution method according to the present invention.
  • FIG. 1 shows a process flow diagram of an application installation method in accordance with one embodiment of the present invention.
  • the application installation method includes at least steps S102 to S106:
  • Step S102 Determine, according to requirements, a plurality of types of functions to be implemented, where the plurality of types of functions include a primary function and an auxiliary function;
  • Step S104 generating a main application as a main function, and generating a separate plug-in for each auxiliary function;
  • Step S106 Install a main application, wherein the main application can call different plugins according to requirements to implement different auxiliary functions.
  • plug-in mentioned in the embodiment of the present invention is actually an independent application (apk), which internally includes resources and codes, and related android component definitions.
  • the functions corresponding to the requirements are divided into two categories, one is a main function implemented by the main application, and the other is an auxiliary function implemented by the plug-in.
  • the main application needs to be installed. If other auxiliary functions are needed, different plug-ins can be called in real time according to requirements by the main application to implement different auxiliary functions. That is, in the embodiment of the present invention, only the main application needs to be installed in an operating system in the form of a separate application, and the remaining plug-ins need not be installed to be used.
  • the main application can implement the corresponding function by calling the plug-in through a certain communication method.
  • the embodiments of the present invention divide the functions corresponding to the requirements, so that the requirements can be developed in a distributed manner, and each auxiliary function is implemented by a plug-in function, which can be directly used as a plug-in for other products, and further improves the practicability of the plug-in. .
  • the main application only the main application is installed, and the corresponding installation package only needs to contain the code and resources necessary for the application, which greatly reduces the application installation data package and can speed up the application installation data package.
  • the download process prevents the user from giving up the download by seeing the application too much, or giving up the download halfway because the download is too slow, which improves the user experience.
  • the plug-in since the plug-in is separated from the main application, the plug-in can be dynamically added, updated, and deleted according to the control command, and the system space can be fully utilized. And its The update process of the main application is independent, and the update process of each plug-in is independent, thus making the update process more independent, and does not interfere with the update of other plug-ins or main applications.
  • the plug-in may be selectively distinguished from the main application installation manner, for example, each of the auxiliary functions may be displayed in the foreground.
  • Plugins or you can silently load plugins with accessibility in the background.
  • the main application only needs to install the code and resources necessary to run its application.
  • Other functions can dynamically download the silent installation after the main application is installed, so that the application data package can be greatly reduced.
  • the purpose of slimming is to increase the download volume of the application, so that the application can be more widely accepted by users.
  • FIG. 2 shows a schematic diagram of a specific example of an architecture between a main application and a plug-in according to an embodiment of the present invention.
  • the main application is a search app
  • the corresponding auxiliary functions include novels, music, movies, news, skins, and the like.
  • Each auxiliary function exists in a separate plug-in form, and the search app can implement the dynamics of the plug-in through specific calls. load.
  • FIG. 3 shows an interface diagram of a plug-in display in accordance with one embodiment of the present invention. Referring to FIG.
  • auxiliary functions such as a title, news, video, novel, picture, map, application, music, and the like can be dynamically loaded.
  • search app can invoke the novel plug-in to transform into a novel app with functions such as a reader, a bookshelf, a library, and the like.
  • the presentation form of the plug-in in the main application interface includes at least one of the following: a card; a pop-up window; and a scrolling screen.
  • the update of each plug-in is also independent. It is not necessary to update the main application to update the resources of each plug-in.
  • the skin of the app can be dynamically switched through the plugin.
  • Each skin theme can be dynamically loaded and updated as a standalone plugin.
  • the skin library does not need to update the main app. It can flexibly produce various star versions, holiday versions, and even users. Customize skins, share skins, and more.
  • the plug-in may be stored in a different storage space separately from the main application, and the plug-in may be separately stored in the expansion space (for example, an expansion card, an SD card, a TF card), and Dynamic loading, deletion, or updating can be implemented in the extended space.
  • the commands for adding and deleting plug-ins are remotely controlled by the cloud, which further ensures the flexibility of the plug-ins.
  • each plug-in with auxiliary functions is loaded, including two parts, one is to load the plug-in code, and the other is to load the plug-in resource.
  • the plug-in code of each plug-in is loaded by the class loader of the main application, and the plug-in code of each plug-in is loaded into the memory, and the plug-in independent class loader is generated for each plug-in.
  • each plugin resource is loaded correspondingly using the class loader of each plugin.
  • an app can only have one resource object (Resource) and a class loader (ClassLoader) that loads the app code, so the resources and code used throughout the app are the main app. If you want to call the resources and code inside the plugin without limiting the original code structure and logic of the plugin, you must replace the main application's resource object and class loader (mResource, mClassLoader) with the plugin. Resources and class loaders, so plugins can use their own resources and code directly.
  • an embodiment of the present invention further provides an application running method, which is applied to an application installed by using the above application installation method.
  • 4 shows a process flow diagram of an application mode of operation in accordance with one embodiment of the present invention.
  • the application running method at least includes:
  • Step S402 the main application having the main function is enabled, wherein the main application can invoke a plug-in having other auxiliary functions besides the main function;
  • Step S404 selecting, according to requirements, a plug-in identifier corresponding to the auxiliary function in an interface of the main application;
  • Step S406 The plug-in corresponding to the selected plug-in identifier is used by the main application to implement the corresponding auxiliary function.
  • the functions corresponding to the requirements are divided into two categories, one is a main function implemented by the main application, and the other is an auxiliary function implemented by the plug-in.
  • the main application needs to be installed in an operating system in the form of a separate application, and the remaining plug-ins need not be installed to be used.
  • the main application can implement the corresponding function by calling the plug-in through a certain communication method.
  • the embodiments of the present invention divide the functions corresponding to the requirements, so that the requirements can be developed in a distributed manner, and each auxiliary function is implemented by a plug-in function, which can be directly used as a plug-in for other products, and further improves the practicability of the plug-in. .
  • the plug-in since the plug-in is separated from the main application, the plug-in can be dynamically added, updated, and deleted according to the control command, and the system space can be fully utilized. And it is independent of the update process of the main application, and the update process of each plug-in is independent, thus making the update process more independent, and does not interfere with the update of other plug-ins or main applications.
  • the plugin is actually a standalone application. It contains resources and code and related android component definitions. To make the main app call up the plugin, you need to simulate the environment in which the app is running and provide it to the plugin.
  • the key points include: plugin code. And resource loading, plugin resource injection, component hosting, and proxying.
  • plugin code And resource loading, plugin resource injection, component hosting, and proxying.
  • plugin resource injection And resource injection, plugin resource injection, component hosting, and proxying.
  • proxying In addition, in order for the plugin to maintain the original structure and code logic, we need to handle their specific calls: such as this, super call, system component property simulation (launch_mode, intent-filter, etc.).
  • the embodiment of the present invention adopts a processing method for establishing a managed plug-in component in a main application, wherein the managed plug-in component can simulate a non-independent plug-in generated when the same auxiliary function is implemented and embedded in the main application is generated. event. When any event is detected, the managed plug-in component is triggered to forward the event to the event handler function of the dependent plug-in for processing.
  • the managed plugin component is a proxy activity, which can simulate the Activity life cycle and the Activity event.
  • the proxy activity is passed through the reflection call to pass the Activity event to the handler corresponding to the plugin Activity event for processing. That is, define a dedicated proxy Activity (ProxyActivity) in the main app, the Activity is specifically used to proxy the plug-in Activity, simulate the life cycle of the plug-in Activity (onCreate, onStart, etc.) and various events, plug-ins
  • the Activity is created as an ordinary Java object, and the event is passed to the handler of the plugin Activity through a reflection call. The process is transparent to the plugin, and it still implements the logic of the Activity as usual.
  • ProxyActivity is not a real Activity. It does not have a plugin class loader and resources. The proxy activity can only solve the event that the simulation system initiates actively and the component passively receives. When the plugin activity uses the methods provided by the system such as this or super, Such as setContentView, etc., there will inevitably be problems.
  • the embodiment of the present invention defines a very simple plugin implementation specification: all activities used in the plugin must inherit a specific PluginActivity from the plugin sdk.
  • PluginActivity will rewrite the key methods of the system, and forward the calls of the subclass directly to ProxyActiviy. In this way, the more critical methods of the plugin Activity using this or super call will be handled by ProxyActivity, just like it is a real Activity. same.
  • an app can only have one resource object and a class loader that loads the app code, so the resources and code used throughout the app are both the main app. If you want to call the resources and code in the plugin without limiting the original code structure and logic of the plugin, you must force the plugin's resources and class loader into the context of the main application calling each plugin. In the main application to call each plugin.
  • the resource object and the class loader of the context of the main application are replaced by the reflection with the resource object and the class loader of the plugin; the resource object and the class loader of the plugin are respectively loaded by the plugin.
  • a plugin is generally a component of a plugin (Activity, Service, etc.).
  • the present invention is a component of the main application calling plugin, and the plugin is provided to the main application. Context, if the plugin is used directly, it must be wrong. Therefore, this embodiment uses the reflection to replace the resource object and the class loader (mResource, mClassLoader) and other objects in the context with the resources and classes of the plugin. The loader, so that the plugin can use its own resources and code directly.
  • the main application communicates with each plugin by setting a plugin interface on each plugin to implement a call to each plugin.
  • the plugin component provides a plugin interface (IPlugin) to the plugin to help the plugin communicate with the host.
  • the key methods are onLoad(), onCommand(), onLoad() when the plugin is loaded.
  • the plugin can perform some initialization work in the function.
  • onCommand() is called when the plugin receives the command.
  • the plugin can be in the function. Implement the processing of commands.
  • FIG. 5 shows a schematic diagram of a main application invoking a plurality of plugins in accordance with one embodiment of the present invention.
  • the embodiments of the present invention can enable plug-in functions of applications, such as application cards and application modules.
  • Blocks, application skins, etc. can be plug-in independent, so that application development can be distributed synchronously, increasing the value of existing products, and solving the problem of large application size, as well as some small updates also need to update the entire app. Problems, improve user experience and shorten user processes. specifically,
  • Plug-in resources and code dynamic loading solve the problem of plug-in dynamic update, so the plug-in does not need to be included in the installation package of the main app.
  • component proxy and hosting solve the problem of component definition in the plug-in, reduce the coupling between the plug-in and the host.
  • plug-in resources and class loader injection to ensure the original logic and resources of the plug-in, so that the plug-in can be run as a plug-in without major changes.
  • the implementation of the plugin interface provides a mechanism for the plugin to communicate with the host.
  • FIG. 6 shows a schematic diagram of a plug-in implementation flow according to an embodiment of the present invention.
  • the plugin manager manages the plugin, performs preprocessing such as initialization operations and preloading. This process is independent and asynchronous with the startup process of the main app.
  • the plugin call is initiated through the app function interface, and the required plugin is called to the plugin manager.
  • the plugin then launches and loads and displays the new plugin feature interface on the app's function interface.
  • an embodiment of the present invention further provides an application installation device.
  • Figure 7 is a block diagram showing the construction of an application mounting device in accordance with one embodiment of the present invention. Referring to Figure 7, the device includes at least:
  • the function determining module 710 is adapted to determine a plurality of types of functions to be implemented according to requirements, wherein the plurality of types of functions include a primary function and an auxiliary function;
  • the classification configuration module 720 is coupled to the function determination module 710, is adapted to generate a main application for the main function, and generates a separate plug-in for each auxiliary function;
  • the installation module 730 is coupled to the classification configuration module 720 and is adapted to install a main application, wherein the main application can call different plug-ins according to requirements to implement different auxiliary functions.
  • FIG. 8 shows another schematic structural view of an application mounting apparatus according to an embodiment of the present invention.
  • the application installation device may further include:
  • the plug-in loading module 740 is respectively coupled to the configuration module 720 and the installation module 730, and is adapted to display the plug-ins with auxiliary functions in the foreground after the installation of the main application is finished; or to silently load the plug-ins with auxiliary functions in the background. .
  • the plug-in loading module 740 is further configured to:
  • Each plugin resource is loaded correspondingly by the class loader of each plugin.
  • the plugin code and resources of each plugin are loaded to simulate the plugin runtime environment when the plugin is called;
  • the plug-in manager After the plug-in is loaded, the plug-in manager uninitifies and manages the plug-ins.
  • FIG. 9 is a block diagram showing the structure of an application running device according to an embodiment of the present invention.
  • the device includes at least:
  • the startup module 910 is adapted to enable a main application having a main function, wherein the main application can invoke a plug-in having an auxiliary function other than the main function;
  • the selection module 920 is coupled to the startup module 910, and is adapted to select a plug-in identifier corresponding to the auxiliary function according to requirements in an interface of the main application;
  • the calling module 930 is coupled to the selection module 920, and is adapted to use the plug-in corresponding to the selected plug-in identifier by the main application to implement the corresponding auxiliary function.
  • the calling module 930 is further configured to:
  • the managed plugin component can simulate an event generated when a non-independent plugin that implements the same auxiliary function and is embedded in the main application is called;
  • the managed plug-in component When any event is detected, the managed plug-in component is triggered to forward the event to the event handler function of the dependent plug-in for processing.
  • the managed plug-in component is a proxy activity, which can simulate the Activity life cycle and Activity event;
  • the proxy activity is passed through the reflection call to pass the Activity event to the handler corresponding to the plugin Activity event for processing.
  • the hosted plugin component is implemented by the following steps:
  • the call to the subclass is forwarded by the PluginActivity to the managed plugin component.
  • the hosted plugin component is transparent relative to its corresponding plugin.
  • the calling module 930 is further configured to:
  • the resource objects and class loaders of each plug-in are forcibly injected into the context used by the main application to call each plug-in for the main application to call each plug-in.
  • the calling module 930 is further configured to:
  • the resource object and the class loader of the context of the main application are replaced by the reflection with the resource object and the class loader of the plugin;
  • the resource object and code of the plugin are respectively loaded by the resource object and the class loader of the plugin, and the auxiliary function of the plugin is executed.
  • the functions corresponding to the requirements are divided into two categories, one is a main function implemented by the main application, and the other is an auxiliary function implemented by the plug-in.
  • the main application needs to be installed. If other auxiliary functions are needed, different plug-ins can be called in real time according to requirements by the main application to implement different auxiliary functions. That is, in the embodiment of the present invention, only the main application needs to be installed in an operating system in the form of a separate application, and the remaining plug-ins need not be installed to be used.
  • the main application can realize the phase by calling the plug-in through a certain communication method. The function should be.
  • the embodiments of the present invention divide the functions corresponding to the requirements, so that the requirements can be developed in a distributed manner, and each auxiliary function is implemented by a plug-in function, which can be directly used as a plug-in for other products, and further improves the practicability of the plug-in. .
  • the main application only the main application is installed, and the corresponding installation package only needs to contain the code and resources necessary for the application, which greatly reduces the application installation data package and can speed up the application installation data package.
  • the download process prevents the user from giving up the download by seeing the application too much, or giving up the download halfway because the download is too slow, which improves the user experience.
  • the plug-in since the plug-in is separated from the main application, the plug-in can be dynamically added, updated, and deleted according to the control command, and the system space can be fully utilized. And it is independent of the update process of the main application, and the update process of each plug-in is independent, thus making the update process more independent, and does not interfere with the update of other plug-ins or main applications.
  • modules in the devices of the embodiments can be adaptively changed and placed in one or more devices different from the embodiment.
  • the modules or units or components of the embodiments may be combined into one module or unit or component, and further they may be divided into a plurality of sub-modules or sub-units or sub-components.
  • any combination of the features disclosed in the specification, including the accompanying claims, the abstract and the drawings, and any methods so disclosed, or All processes or units of the device are combined.
  • Each feature disclosed in this specification (including the accompanying claims, the abstract and the drawings) may be replaced by alternative features that provide the same, equivalent or similar purpose.
  • the various component embodiments of the present invention may be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof.
  • a microprocessor or digital signal processor may be used in practice to implement some or all of the functionality of some or all of the application mounting devices, application operating devices, in accordance with embodiments of the present invention.
  • the invention may also be embodied as a device or device program (eg, a computer program and a computer) for performing some or all of the methods described herein. Program product).
  • Such a program implementing the invention may be stored on a computer readable medium or may be in the form of one or more signals. Such signals may be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.
  • Figure 10 illustrates a computing device that can implement an application installation method and/or an application operation method in accordance with the present invention.
  • the computing device conventionally includes a processor 1010 and a computer program product or computer readable medium in the form of a memory 1020.
  • the memory 1020 may be an electronic memory such as a flash memory, an EEPROM (Electrically Erasable Programmable Read Only Memory), an EPROM, a hard disk, or a ROM.
  • the memory 1020 has a memory space 1030 for executing program code 1031 of any of the above method steps.
  • storage space 1030 for program code may include various program code 1031 for implementing various steps in the above methods, respectively.
  • the program code can be read from or written to one or more computer program products.
  • Such computer program products include program code carriers such as hard disks, compact disks (CDs), memory cards or floppy disks.
  • Such a computer program product is typically a portable or fixed storage unit as described with reference to FIG.
  • the storage unit may have storage segments, storage spaces, and the like that are similarly arranged to memory 1020 in the computing device of FIG.
  • the program code can be compressed, for example, in an appropriate form.
  • the storage unit includes computer readable code 1031', ie, code that can be read by, for example, a processor such as 1010, which when executed by a computing device causes the computing device to perform each of the methods described above step.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention concerne un procédé et un dispositif d'installation et d'exécution d'une application. Le procédé d'installation d'une application consiste à : déterminer, conformément à des demandes, de multiples types de fonctions qu'il est nécessaire de mettre en œuvre, les multiples types de fonctions comprenant une fonction majeure et des fonctions auxiliaires ; générer une application majeure pour la fonction majeure et générer indépendamment des modules d'extension pour les diverses fonctions auxiliaires ; et installer l'application majeure, l'application majeure pouvant appeler différents modules d'extension conformément aux demandes de façon à mettre en œuvre différentes fonctions auxiliaires. La présente invention permet à une application majeure d'être indépendante de modules d'extension d'applications auxiliaires, ce qui permet de réduire la taille d'un progiciel d'installation, d'augmenter la vitesse d'installation et de réduire l'occupation de l'espace système.
PCT/CN2015/099591 2015-03-31 2015-12-29 Procédé et dispositif d'installation et d'exécution d'application WO2016155388A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510150236.8A CN104714828B (zh) 2015-03-31 2015-03-31 应用安装、运行方法及装置
CN201510150236.8 2015-03-31

Publications (1)

Publication Number Publication Date
WO2016155388A1 true WO2016155388A1 (fr) 2016-10-06

Family

ID=53414198

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/099591 WO2016155388A1 (fr) 2015-03-31 2015-12-29 Procédé et dispositif d'installation et d'exécution d'application

Country Status (2)

Country Link
CN (1) CN104714828B (fr)
WO (1) WO2016155388A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107220059A (zh) * 2017-06-14 2017-09-29 北京小米移动软件有限公司 应用界面的显示方法及装置

Families Citing this family (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104714828B (zh) * 2015-03-31 2017-06-09 北京奇虎科技有限公司 应用安装、运行方法及装置
CN106484445A (zh) * 2015-08-27 2017-03-08 阿里巴巴集团控股有限公司 移动终端应用程序的页面展示方法和装置
CN106557343A (zh) * 2015-09-30 2017-04-05 阿里巴巴集团控股有限公司 生成功能应用及加载资源的方法及装置
CN106909406A (zh) * 2015-12-23 2017-06-30 北京奇虎科技有限公司 一种加载应用程序的apk插件的方法及装置
CN105872708A (zh) * 2015-12-30 2016-08-17 乐视致新电子科技（天津）有限公司 一种显示桌面生成方法、显示桌面生成系统和智能电视
CN105700886B (zh) * 2016-01-14 2019-02-26 腾讯科技（北京）有限公司 插件界面的显示方法及终端
CN105760160B (zh) * 2016-02-04 2020-03-03 百度在线网络技术（北京）有限公司 一种从插件添加卡片的方法、装置和系统
CN107092494B (zh) * 2016-02-18 2020-09-01 腾讯科技（深圳）有限公司 访问apk资源的方法和装置
CN105740033A (zh) * 2016-03-15 2016-07-06 广州彩瞳网络技术有限公司 一种终端设备、插件加载运行装置及插件加载运行方法
CN107203524A (zh) * 2016-03-16 2017-09-26 阿里巴巴集团控股有限公司 一种打包APK文件的方法、加载Bundle文件的方法及系统
CN105955787B (zh) * 2016-05-18 2019-11-22 深圳市掌玩网络技术有限公司 一种用于Android系统的插件加载方法及装置
CN106055330A (zh) * 2016-05-31 2016-10-26 深圳卡尔拓客科技有限公司 一种应用程序的管理方法及系统
CN106131612B (zh) * 2016-06-30 2019-03-05 武汉斗鱼网络科技有限公司 安卓app动态加载资源功能模块的方法及系统
CN106325923A (zh) * 2016-08-17 2017-01-11 北京奇虎科技有限公司 功能插件的管理方法及装置
CN106371874A (zh) * 2016-08-31 2017-02-01 广州品唯软件有限公司 一种插件数据加载方法及设备
CN106815044A (zh) * 2016-12-12 2017-06-09 广州视源电子科技股份有限公司 软件功能扩展的方法、装置及系统
CN106886437B (zh) * 2017-01-24 2021-08-31 北京奇虎科技有限公司 应用程序更新方法与装置
CN106775916B (zh) * 2017-02-17 2020-02-28 北京金山安全软件有限公司 减小应用安装包的方法、装置及电子设备
CN107015800A (zh) * 2017-03-14 2017-08-04 宇龙计算机通信科技(深圳)有限公司 显示方法、装置及设备
CN107193609B (zh) * 2017-05-27 2021-05-07 北京奇虎科技有限公司 应用中功能模块调用方法及装置、电子设备
CN107463406A (zh) * 2017-08-08 2017-12-12 上海连尚网络科技有限公司 发布移动应用的方法和电子设备
CN109408133B (zh) * 2017-08-16 2021-12-14 阿里巴巴集团控股有限公司 一种启动组件的方法和设备
CN107992308B (zh) * 2017-11-22 2020-10-20 竞技世界（北京）网络技术有限公司 一种安卓终端应用程序的插件化管理方法
CN108388453B (zh) * 2018-01-15 2020-08-11 珠海格力电器股份有限公司 插件管理、应用程序形成方法、装置及服务器
CN108595220B (zh) * 2018-04-25 2021-04-16 上海掌门科技有限公司 应用组件的处理方法、设备及计算机可读存储介质
CN110427198A (zh) * 2018-04-27 2019-11-08 中兴通讯股份有限公司 应用程序的热修复方法、装置及终端、存储介质
CN108804082A (zh) * 2018-05-10 2018-11-13 北京酷我科技有限公司 一种插件化JSBridge的实现方法
CN109656592B (zh) * 2018-12-06 2022-02-08 Oppo广东移动通信有限公司 卡片管理方法、装置、终端及计算机可读存储介质
CN110531961B (zh) * 2019-07-24 2023-05-23 百度在线网络技术（北京）有限公司 智能服务破壳系统及其方法
CN110515673B (zh) * 2019-07-24 2022-10-11 百度在线网络技术（北京）有限公司 插件化系统及其方法
CN110908734A (zh) * 2019-11-15 2020-03-24 网易（杭州）网络有限公司 基于插件化的应用组合方法、装置、终端设备及存储介质
CN111435313A (zh) * 2019-12-09 2020-07-21 杭州海康威视数字技术股份有限公司 一种软件换肤的方法及装置
CN111857765B (zh) * 2020-06-16 2024-06-28 深圳晶泰科技有限公司 用于药物设计系统的插件系统及其生成方法和更新方法
CN114528048A (zh) * 2022-02-18 2022-05-24 Oppo广东移动通信有限公司 应用执行方法、应用执行架构、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103530156A (zh) * 2013-10-17 2014-01-22 北京奇虎科技有限公司 动态加载和调用程序的方法及装置
US20150046424A1 (en) * 2012-08-06 2015-02-12 Hsiu-Ping Lin Methods and systems for searching software applications
CN104391716A (zh) * 2014-11-14 2015-03-04 百度在线网络技术（北京）有限公司 基于插件的应用程序实现方法及装置
CN104714828A (zh) * 2015-03-31 2015-06-17 北京奇虎科技有限公司 应用安装、运行方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104123151B (zh) * 2013-04-28 2018-07-10 百度在线网络技术（北京）有限公司 移动终端中应用程序的插件管理方法、装置和移动终端
CN103970573A (zh) * 2014-05-21 2014-08-06 百度在线网络技术（北京）有限公司 用于移动设备的轻应用程序系统及其程序加载系统和方法
CN104021024B (zh) * 2014-06-25 2017-06-06 广州市久邦数码科技有限公司 一种桌面系统功能屏幕的加载方法及其系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150046424A1 (en) * 2012-08-06 2015-02-12 Hsiu-Ping Lin Methods and systems for searching software applications
CN103530156A (zh) * 2013-10-17 2014-01-22 北京奇虎科技有限公司 动态加载和调用程序的方法及装置
CN104391716A (zh) * 2014-11-14 2015-03-04 百度在线网络技术（北京）有限公司 基于插件的应用程序实现方法及装置
CN104714828A (zh) * 2015-03-31 2015-06-17 北京奇虎科技有限公司 应用安装、运行方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107220059A (zh) * 2017-06-14 2017-09-29 北京小米移动软件有限公司 应用界面的显示方法及装置
EP3428790A1 (fr) * 2017-06-14 2019-01-16 Beijing Xiaomi Mobile Software Co., Ltd. Procédé et dispositif d'affichage d'une interface d'application

Also Published As

Publication number Publication date
CN104714828B (zh) 2017-06-09
CN104714828A (zh) 2015-06-17

Similar Documents

Publication Publication Date Title
WO2016155388A1 (fr) Procédé et dispositif d'installation et d'exécution d'application
US9934005B2 (en) Dynamically building locale objects or subsections of locale objects based on historical data
US11467816B1 (en) Method and system of running an application
US9588657B1 (en) Seamless integration of non-native windows with dynamically scalable resolution into host operating system
US20210303108A1 (en) System and method for on-screen graphical user interface encapsulation and reproduction
US9317195B1 (en) Seamless integration of non-native windows with dynamically scalable resolution into host operating system
US10580051B2 (en) Background element associated with an application installed in a browser application
US9619304B2 (en) Automatic connections between application components
US9058193B2 (en) Methods and systems for providing compatibility of applications with multiple versions of an operating system
US10019298B2 (en) Middleware interface and middleware interface generator
US20220365773A1 (en) Run-Time Application Modification
CN104704468A (zh) Web应用程序的跨系统安装
WO2019090994A1 (fr) Procédé d'exécution automatisée de test de script, appareil, équipement et support d'enregistrement
US10908948B2 (en) Multiple application instances in operating systems that utilize a single process for application execution
US9558014B2 (en) System, method and apparatus for transparently enabling software applications with adaptive user interfaces
CN110716720A (zh) 一种实现应用热部署的方法和装置
CN103034495A (zh) 对网页中插件进行隔离的浏览器及网页插件的隔离方法
US8161456B2 (en) Management of heterogeneous software artifacts through a common representation
US20230169138A1 (en) Rendering primitive child elements corresponding to child components of a user interface without instantiating the child components
US9141353B2 (en) Dynamically building locale objects at run-time
US9785560B2 (en) Scene-isolated internet application
CN114911541A (zh) 配置信息的处理方法、装置、电子设备及存储介质
KR20080027293A (ko) 데이터 언어에서 다수 언어들의 관리
CN105183491A (zh) 跨平台的桌面gis系统及其启动方法
CN117453302A (zh) 导入软件开发包的方法、装置、设备及计算机可读介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15887337

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15887337

Country of ref document: EP

Kind code of ref document: A1