[go: up one dir, main page]

WO2019029451A1 - 发布移动应用的方法和电子设备 - Google Patents

发布移动应用的方法和电子设备 Download PDF

Info

Publication number
WO2019029451A1
WO2019029451A1 PCT/CN2018/098573 CN2018098573W WO2019029451A1 WO 2019029451 A1 WO2019029451 A1 WO 2019029451A1 CN 2018098573 W CN2018098573 W CN 2018098573W WO 2019029451 A1 WO2019029451 A1 WO 2019029451A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
plug
mobile application
service
host
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.)
Ceased
Application number
PCT/CN2018/098573
Other languages
English (en)
French (fr)
Inventor
苏勇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Lianshang Network Technology Co Ltd
Original Assignee
Shanghai Lianshang Network Technology Co Ltd
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 Shanghai Lianshang Network Technology Co Ltd filed Critical Shanghai Lianshang Network Technology Co Ltd
Publication of WO2019029451A1 publication Critical patent/WO2019029451A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons

Definitions

  • the present application relates to the field of computer technologies, and in particular, to the field of Internet technologies, and in particular, to a method and an electronic device for distributing a mobile application.
  • the purpose of the embodiments of the present application is to provide an improved method and electronic device for distributing a mobile application to solve the technical problems mentioned in the above background art.
  • an embodiment of the present application provides a method for implementing a mobile application function, the method comprising: in response to activation of a mobile application, a host module of a mobile application loads at least one service plug-in of a mobile application to implement the mobile application Business function, wherein the host module is a non-business function module.
  • the method includes obtaining an installation package generated from the host file and installing the installation package to obtain a host module.
  • the host module includes a plugin load framework, a plugin upgrade framework, a public UI library, and a component interface.
  • the plugin file of the at least one business plugin is stored in a resource directory of the mobile application.
  • the host module loads at least one service plugin through a predetermined interface.
  • the predetermined interface includes a Fragment class
  • the plug-in file of the at least one service plug-in includes a service plug-in description file
  • each service plug-in description file is configured with a name of a Fragment class to be loaded.
  • the host module loads the at least one service plug-in through the predetermined interface, including: reading the name of the Fragment class in each service plug-in description file in the plug-in file of the at least one service plug-in, and initializing the Fragment class object by using the name of the Fragment class. And load the Fragment class object into the host module.
  • the method further comprises: in response to detecting a change in the service plug-in stored by the network device, transmitting a plug-in update request to the network device; receiving the changed service plug-in sent by the network device and reloading.
  • the embodiment of the present application provides a method for publishing a mobile application, where the method includes: acquiring a host file, where the host file is a non-service function file, and loading at least one service plug-in file to implement the service plug-in The business function of the mobile application associated with the file; the installation package is generated based on the host file; the installation package is released.
  • the method comprises:
  • An installation package is generated based on the host file and at least one business plug-in file.
  • the method further comprises: obtaining a new service plugin file for updating the mobile application; and transmitting a new service plugin file to the mobile terminal that has installed and launched the mobile application.
  • the method further comprises: acquiring a new service plug-in file for updating the mobile application; transmitting a plug-in update request to the mobile terminal that has installed and launching the mobile application; in response to receiving the update confirmation message sent by the mobile terminal, Send a new service plugin file to the mobile terminal.
  • an embodiment of the present application provides an electronic device, including: one or more processors; and a storage device, configured to store one or more programs, when one or more programs are executed by one or more processors Having one or more processors implement the method of any of the first aspect and the second aspect.
  • an embodiment of the present application provides a computer readable storage medium having stored thereon a computer program, wherein the program is executed by a processor to implement the method of any one of the first aspect and the second aspect .
  • the product server sends the installation package generated by the host file to the market server for publishing.
  • the host file is a non-service function file, and is configured to load at least one service plug-in file to implement a business function of the mobile application associated with the service plug-in file, and does not need to be updated for a long time after being released.
  • the real functions and features of the product are implemented by the business plug-in. Different services can be different plug-ins, and the plug-ins are dynamically loaded by the host program.
  • the business plug-in file can be obtained directly from the product server, so as to avoid the market server's review of the business plug-in file and improve the publishing efficiency of the mobile application.
  • FIG. 1 is an exemplary system architecture diagram to which the present application can be applied;
  • FIG. 2 is a flow diagram of one embodiment of a method of publishing a mobile application in accordance with the present application
  • 3a, 3b, and 3c are schematic diagrams of an application scenario of a method for distributing a mobile application according to the present application
  • FIG. 4 is a flow diagram of one embodiment of a method of implementing a mobile application function in accordance with the present application
  • FIG. 5 is a schematic structural diagram of a computer system suitable for implementing an electronic device of an embodiment of the present application.
  • FIG. 1 illustrates an exemplary system architecture 100 of an embodiment of a method of publishing a mobile application to which the present application may be applied.
  • system architecture 100 can include mobile terminals 101, 102, marketplace server 103, and product server 104. Between the mobile terminals 101, 102 and the market server 103, the market server 103 and the product server 104 are connected by a wired, wireless communication link or a fiber optic cable or the like.
  • the user can use the mobile terminal 101, 102 to interact with the market server 103 to download various mobile applications from the market server 103, such as a web browser application, a shopping application, a search application, an instant communication tool, a mailbox client, a social platform software, and the like. .
  • the mobile terminals 101, 102 may be various electronic devices having a display screen and supporting an Android or iOS operating system, including but not limited to a smartphone, a tablet, an e-book reader, and an MP3 player (Moving Picture Experts Group Audio Layer III, The motion picture expert compresses the standard audio layer 3), MP4 (Moving Picture Experts Group Audio Layer IV) player, laptop portable computer and desktop computer, and the like.
  • an Android or iOS operating system including but not limited to a smartphone, a tablet, an e-book reader, and an MP3 player (Moving Picture Experts Group Audio Layer III, The motion picture expert compresses the standard audio layer 3), MP4 (Moving Picture Experts Group Audio Layer IV) player, laptop portable computer and desktop computer, and the like.
  • Market server 103 can be a server that provides a variety of mobile applications.
  • the market server 103 can perform processing such as analysis of the received mobile application download request and the like, and feed back the processing result (for example, the installation package of the mobile application) to the mobile terminal.
  • the product server 104 uploads the compiled package of the completed mobile application to the marketplace server 103 for the mobile terminals 101, 102 to download from the marketplace server 103.
  • the product server 104 also provides the mobile plug-in 101, 102 with a service plug-in file for implementing the business function directly after the mobile terminal 101, 102 has installed the mobile application.
  • the method of publishing a mobile application includes the following steps:
  • step 201 a host file is obtained.
  • the electronic device (for example, the product server shown in FIG. 1) on which the method for publishing the mobile application runs can acquire the host file from the developer's terminal through a wired connection or a wireless connection.
  • the host file is a non-service function file, and is configured to load at least one service plug-in file to implement a business function of the mobile application associated with the service plug-in file.
  • the host file does not have the function of interacting with the user, and is used to dynamically load at least one business plug-in file, and the business plug-in implements a business function presented to the user and interacts with the user.
  • Business functions are encapsulated into business plug-ins. A programmer is responsible for several business plug-ins.
  • Each business plug-in consists of the interface, business logic and data access code involved in its corresponding function. Each business plug-in can be developed, tested, and deployed independently, eliminating the need to merge code between developers.
  • the host files include: 1. plug-in loading framework, 2. plug-in upgrade framework, 3. public UI (user interface) library and component interface.
  • the plugin loading framework can load business plugin files to implement business functions.
  • the plugin loading framework extends the CLR (Common Language Runtime) class loading so that it can be properly loaded into the plugin assembly from the plugin directory.
  • the plugin loading framework also needs to introduce a plugin description method to inform the current plugin's basic information, version identifier, and the assembly contained in the plugin.
  • the plug-in upgrade framework can support the update of the business plug-in. When a new version of the business plug-in appears on the product service, it can be automatically updated.
  • the public UI library and component interfaces are used to implement the loading of the plugin by the host.
  • the overall structure of the mobile application can be divided into: host + service plug-in 1 + service plug-in 2+ service plug-in 3 and the like.
  • the comprehensive plug-in solution specifically means that both core and non-core functions are business plug-ins. For example, usually there are 3 or more tabs (TABs) when the mobile app is opened, as shown in Figures 3a-3c.
  • TABs tabs
  • these three TABs are core functions and are integrated in In the main program of the application, some pages of the secondary menu, such as "shake”, “gift”, “tool” and other non-core functions are made into service plug-ins, and in this application, each TAB is a Business plug-ins, and as the business grows and deletes, the number of TABs can change.
  • the host file loads the at least one service plugin file through a predetermined interface.
  • Business plugins that implement the functionality of TAB need to inherit from the predetermined interface class.
  • the predetermined interface includes a Fragment class.
  • the plug-in file of at least one service plug-in includes a service plug-in description file, and each service plug-in description file defines a name of a Fragment class to be loaded by each service.
  • the host will read the business plug-in description file of each business plug-in.
  • the business plug-in description file configures the name of the Fragment class to be loaded by the service, and the host reads the names of the Fragment classes and initializes them.
  • the Fragment object is loaded and displayed in the host, so that each TAB is a business plugin, and the display is switched in the host interface.
  • Step 202 Generate an installation package according to the host file.
  • the host file can be packaged separately into an installation package of the mobile application without including any service plug-in files.
  • At least one business plug-in file may also be packaged with the host file, wherein at least one business plug-in file may be stored in a binary file form in the mobile application's resource directory.
  • Business plugins updated in subsequent developments are also stored in the mobile application's resource directory.
  • step 203 the installation package is released.
  • the user's mobile terminal can download the installation package from the market server.
  • mobile applications need to be reviewed by the market.
  • the audit time is 1 to 2 days, and the length is 1 week.
  • not all users will update after the online, which seriously affects the online speed of the new features of the product.
  • it can only be repackaged and released online, which seriously delays the time and affects the user, resulting in user loss.
  • the method further includes: acquiring a new service plug-in file for updating the mobile application; and sending a new service plug-in file to the mobile terminal that has installed and started the mobile application.
  • the method further includes: acquiring a new service plug-in file for updating the mobile application; sending a plug-in update request to the mobile terminal that has installed and starting the mobile application; and responding to receiving the mobile
  • the update confirmation message sent by the terminal sends a new service plug-in file to the mobile terminal. That is, the mobile terminal is notified that the service plug-in can be updated, and the user can select whether to update or not.
  • a new business plugin file is sent when the user agrees to the update.
  • Figures 3a-3c are schematic diagrams of application scenarios of a method of publishing a mobile application in accordance with the present embodiment.
  • the developer pre-divides the overall structure of the mobile application into: host + service plug-in 1 + service plug-in 2+ service plug-in 3.
  • the three tabs are respectively generated by the service plug-in 1, the service plug-in 2, and the service plug-in 3 that implement the core functions. Shown in Figure 3a is the interface of Service 1 displayed after the host has loaded Service Plugin 1. Shown in Figure 3b is the interface of Service 2 displayed after the host has loaded Service Plugin 2.
  • Figure 3c Shown in Figure 3c is the interface of the Service 3 displayed after the host has loaded the Service Plugin 3.
  • Figures 3a-3c show a first-level tab page where the user can switch between the three interfaces.
  • the above electronic device acquires the four parts of the file, but does not integrate the business plug-in into the main program of the application, but only uploads the host to the market server, and stores the three business plug-in files in the product server.
  • the market server is officially released after reviewing the host main program, and the mobile terminal can download and install the installation package of the mobile application from the market server.
  • three business plugins are loaded from the resource directory of the mobile application of the product server into the host.
  • the business plug-in file is updated, it does not need to be uploaded to the market server, but can be directly sent to the mobile terminal.
  • the method provided in the foregoing embodiment of the present application divides the mobile application into a host and a service plug-in, uploads the host to the market server for review, and stores the service plug-in file in the product server, and the service plug-in file in the product server does not need to be audited. Directly sent to the mobile terminal to achieve a full plug-in of the mobile application, thereby improving the publishing efficiency of the mobile application.
  • the process 400 of the method for implementing a mobile application function includes the following steps:
  • step 401 the mobile application is started.
  • the mobile device After the electronic device (for example, the mobile terminal shown in FIG. 1) on which the mobile application method is implemented has installed the mobile application including the host module and the at least one service plug-in loaded by the host module, the mobile device is started.
  • the host module is a non-service function module, and does not implement any business function, and is used to dynamically load at least one service plug-in file.
  • the mobile terminal may acquire an installation package generated according to the host file from the network device; and install the installation package to obtain the host module.
  • the installation includes the inclusion of only the host module, and may also include a host module and at least one business plugin file.
  • the host module obtained by installing the installation package includes: 1. a plug-in loading framework, a plug-in upgrade framework, a public UI (User Interface) library, and a component interface.
  • the plugin loading framework can load business plugin files to implement business functions.
  • the plugin loading framework extends the CLR (Common Language Runtime) class loading so that it can be properly loaded into the plugin assembly from the plugin directory.
  • the plugin loading framework also needs to introduce a plugin description method to inform the current plugin's basic information, version identifier, and the assembly contained in the plugin.
  • the plug-in upgrade framework can support the update of the business plug-in. When a new version of the business plug-in appears on the product service, it can be automatically updated.
  • the public UI library and component interfaces are used to implement the loading of the plugin by the host.
  • At least one service plug-in file is copied from the resource directory of the mobile application to the resource directory of the mobile application when the mobile application is started for the first time.
  • the host module loads the at least one service plug-in through a predetermined interface.
  • the predetermined interface includes a Fragment class
  • the plug-in file of the at least one service plug-in includes a service plug-in description file
  • each service plug-in description file is configured with the required information.
  • step 402 the host module loads at least one service plugin.
  • the host module loads the at least one service plug-in file through the predetermined interface, so that the mobile application can implement the function of each service plug-in.
  • the host module loads the at least one service plug-in file by using a predetermined interface, including: reading a name of a Fragment class in each service plug-in description file in the plug-in file of the at least one service plug-in, The name of the Fragment class initializes the Fragment class object and loads the Fragment class object into the host module.
  • each TAB is a business plug-in, and the display is switched in the host interface.
  • the method further includes: sending a plug-in update request to the network device in response to detecting that the service plug-in file stored by the network device changes; receiving the changed service plug-in sent by the network device File and reload.
  • the network device can be a market server or a product server.
  • the mobile terminal may be notified to update, or the updated service plug-in file may be directly pushed to the mobile terminal to cause the host of the mobile terminal to reload the service plug-in file.
  • the mobile application on the mobile terminal may also initiate a service plug-in file detection to the network device. When it detects that the service plug-in file is updated, the new service plug-in file is downloaded and reloaded.
  • the flow 400 of the method for implementing the mobile application function in the present embodiment highlights the step of loading the service plug-in file by the mobile terminal as compared with the embodiment corresponding to FIG. Thereby, the update speed of the mobile application on the mobile terminal is improved.
  • FIG. 5 there is shown a block diagram of a computer system 500 suitable for use in implementing the electronic device of the embodiments of the present application.
  • the electronic device shown in FIG. 5 is merely an example, and should not impose any limitation on the function and scope of use of the embodiments of the present application.
  • the electronic device shown in FIG. 5 may be a mobile terminal that implements a mobile application function, including but not limited to a smart phone, a tablet computer, an e-book reader, and an MP3 player (Moving Picture Experts Group Audio Layer III, The motion picture expert compresses the standard audio layer 3), MP4 (Moving Picture Experts Group Audio Layer IV) player, laptop portable computer and desktop computer, and the like.
  • the electronic device shown in FIG. 5 may also be a device for publishing a mobile application, including but not limited to a smart phone, a tablet computer, a laptop portable computer, a desktop computer, and the like.
  • computer system 500 includes a central processing unit (CPU) 501 that can be loaded into a program in random access memory (RAM) 503 according to a program stored in read only memory (ROM) 502 or from storage portion 508. And perform various appropriate actions and processes.
  • RAM random access memory
  • ROM read only memory
  • RAM 503 various programs and data required for the operation of the system 500 are also stored.
  • the CPU 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504.
  • An input/output (I/O) interface 505 is also coupled to bus 504.
  • the following components are connected to the I/O interface 505: an input portion 505 including a keyboard, a mouse, etc.; an output portion 507 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), and the like, and a storage portion 508 including a hard disk or the like. And a communication portion 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the Internet.
  • Driver 510 is also coupled to I/O interface 505 as needed.
  • a removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory or the like is mounted on the drive 510 as needed so that a computer program read therefrom is installed into the storage portion 508 as needed.
  • an embodiment of the present disclosure includes a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for executing the method illustrated in the flowchart.
  • the computer program can be downloaded and installed from the network via the communication portion 509, and/or installed from the removable medium 511.
  • the computer program is executed by the central processing unit (CPU) 501, the above-described functions defined in the method of the present application are performed.
  • the computer readable medium described herein may be a computer readable signal medium or a computer readable storage medium or any combination of the two.
  • the computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the foregoing.
  • a computer readable storage medium may be any tangible medium that can contain or store a program, which can be used by or in connection with an instruction execution system, apparatus or device.
  • a computer readable signal medium may include a data signal that is propagated in the baseband or as part of a carrier, carrying computer readable program code. Such propagated data signals can take a variety of forms including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the computer readable signal medium can also be any computer readable medium other than a computer readable storage medium, which can transmit, propagate, or transport a program for use by or in connection with the instruction execution system, apparatus, or device.
  • Program code embodied on a computer readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
  • each block of the flowchart or block diagram can represent a module, a program segment, or a portion of code that includes one or more of the logic functions for implementing the specified.
  • Executable instructions can also occur in a different order than that illustrated in the drawings. For example, two successively represented blocks may in fact be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending upon the functionality involved.
  • each block of the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts can be implemented in a dedicated hardware-based system that performs the specified function or operation. Or it can be implemented by a combination of dedicated hardware and computer instructions.
  • the present application further provides a computer readable medium, which may be included in an electronic device described in the above embodiments, or may be separately present without being assembled into the electronic device.
  • the computer readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to publish a mobile application or implement a mobile application function.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请公开了发布移动应用的方法和电子设备。该方法的一具体实施方式包括：获取宿主文件，其中，宿主文件为非业务功能文件，用以加载至少一个业务插件文件来实现与该业务插件文件关联的移动应用的业务功能；根据宿主文件生成安装包；发布安装包。该实施方式提高了移动应用的发布效率。

Description

发布移动应用的方法和电子设备 技术领域
本申请涉及计算机技术领域，具体涉及互联网技术领域，尤其涉及发布移动应用的方法和电子设备。
背景技术
目前移动应用主要分为Android(安卓)应用和iOS(由苹果公司开发的移动操作系统)应用，在传统的移动应用开发过程中，都是按照功能模块划分好，分配到不同的人员开发，最后合并代码编译打包，上线发布。但是随着公司规模越来越大，业务越来越多，业务变更频繁的情况，这种开发方案就会显现弊端。每个新的特性由不同开发人员实现，上线之前需合并代码，接着编译打包准备上线，由于移动应用上线是需要市场的审核，这个时间多则1～2天，长则1个星期，另外，上线之后不是所有用户都会更新，这些都严重影响产品新特性的上线速度。另外，如果线上应用出现紧急问题的时候，也只能重新打包发布上线，严重耽误时间，降低了移动应用的发布效率。
发明内容
本申请实施例的目的在于提出一种改进的发布移动应用的方法和电子设备，来解决以上背景技术部分提到的技术问题。
第一方面，本申请实施例提供了一种实现移动应用功能的方法，该方法包括：响应于移动应用的启动，移动应用的宿主模块加载移动应用的至少一个业务插件，以实现所述移动应用的业务功能，其中，该宿主模块为非业务功能模块。
在一些实施例中，该方法包括：获取根据宿主文件生成的安装包，安装该安装包以获得宿主模块。
在一些实施例中，宿主模块包括插件加载框架、插件升级框架、 公共UI库和组件接口。
在一些实施例中，至少一个业务插件的插件文件存储于移动应用的资源目录中。
在一些实施例中，宿主模块通过预定接口加载至少一个业务插件。
在一些实施例中，预定接口包括Fragment类，至少一个业务插件的插件文件包括业务插件描述文件，每个业务插件描述文件里面配置有其所要被加载的Fragment类的名称。
在一些实施例中，宿主模块通过预定接口加载至少一个业务插件，包括：读取至少一个业务插件的插件文件中每个业务插件描述文件中Fragment类的名称，通过Fragment类的名称初始化Fragment类对象，并将Fragment类对象加载到宿主模块中。
在一些实施例中，该方法还包括：响应于检测到网络设备存储的业务插件发生变化，向网络设备发送插件更新请求；接收网络设备发送的发生变化的业务插件并重新加载。
第二方面，本申请实施例提供了一种发布移动应用的方法，该方法包括：获取宿主文件，其中，宿主文件为非业务功能文件，用以加载至少一个业务插件文件来实现与该业务插件文件关联的移动应用的业务功能；根据宿主文件生成安装包；发布安装包。
在一些实施例中，该方法包括：
获取所述移动应用的至少一个业务插件文件；
以及根据所述宿主文件生成安装包包括：
根据所述宿主文件以及至少一个业务插件文件生成安装包。
在一些实施例中，该方法还包括：获取用于更新移动应用的新业务插件文件；向已经安装并启动移动应用的移动终端发送新业务插件文件。
在一些实施例中，该方法还包括：获取用于更新移动应用的新业务插件文件；向已经安装并启动移动应用的移动终端发送插件更新请求；响应于接收到移动终端发送的更新确认消息，向移动终端发送新业务插件文件。
第三方面，本申请实施例提供了一种电子设备，包括：一个或多 个处理器；存储装置，用于存储一个或多个程序，当一个或多个程序被一个或多个处理器执行，使得一个或多个处理器实现如第一方面和第二方面中任一的方法。
第四方面，本申请实施例提供了一种计算机可读存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现如第一方面和第二方面中任一的方法。
本申请实施例提供的发布移动应用的方法和电子设备，产品服务器将由宿主文件生成的安装包发送到市场服务器进行发布。其中，宿主文件为非业务功能文件，用以加载至少一个业务插件文件来实现与该业务插件文件关联的移动应用的业务功能，发布之后长时间不需要更新。而产品真正的功能和特性由业务插件来完成，不同的业务可以是不同的插件，插件由宿主程序动态加载。移动终端安装了移动应用之后，就可直接从产品服务器获取业务插件文件，以避免市场服务器对业务插件文件的审核，提高了移动应用的发布效率。
附图说明
通过阅读参照以下附图所作的对非限制性实施例所作的详细描述，本申请的其它特征、目的和优点将会变得更明显：
图1是本申请可以应用于其中的示例性系统架构图；
图2是根据本申请的发布移动应用的方法的一个实施例的流程图；
图3a、3b、3c是根据本申请的发布移动应用的方法的一个应用场景的示意图；
图4是根据本申请的实现移动应用功能的方法的一个实施例的流程图；
图5是适于用来实现本申请实施例的电子设备的计算机系统的结构示意图。
具体实施方式
下面结合附图和实施例对本申请作进一步的详细说明。可以理解 的是，此处所描述的具体实施例仅仅用于解释相关发明，而非对该发明的限定。另外还需要说明的是，为了便于描述，附图中仅示出了与有关发明相关的部分。
需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。下面将参考附图并结合实施例来详细说明本申请。
图1示出了可以应用本申请的发布移动应用的方法的实施例的示例性系统架构100。
如图1所示，系统架构100可以包括移动终端101、102，市场服务器103和产品服务器104。移动终端101、102和市场服务器103之间，市场服务器103和产品服务器104之间，通过有线、无线通信链路或者光纤电缆等等连接。
用户可以使用移动终端101、102与市场服务器103交互，从市场服务器103下载各种移动应用，例如网页浏览器应用、购物类应用、搜索类应用、即时通信工具、邮箱客户端、社交平台软件等。
移动终端101、102可以是具有显示屏并且支持安卓或iOS操作系统的各种电子设备，包括但不限于智能手机、平板电脑、电子书阅读器、MP3播放器(Moving Picture Experts Group Audio Layer III，动态影像专家压缩标准音频层面3)、MP4(Moving Picture Experts Group Audio Layer IV，动态影像专家压缩标准音频层面4)播放器、膝上型便携计算机和台式计算机等等。
市场服务器103可以是提供各种移动应用的服务器。市场服务器103可以对接收到的移动应用下载请求等数据进行分析等处理，并将处理结果(例如移动应用的安装包)反馈给移动终端。
产品服务器104将编译完成的移动应用的安装包上传至市场服务器103，以便移动终端101、102从市场服务器103下载。产品服务器104还在移动终端101、102安装了移动应用后直接向移动终端101、102提供用于实现业务功能的业务插件文件。
应该理解，图1中的移动终端、网络和服务器的数目仅仅是示意性的。根据实现需要，可以具有任意数目的移动终端、网络和服务器。
继续参考图2，示出了根据本申请的发布移动应用的方法的一个实施例的流程200。该发布移动应用的方法，包括以下步骤：
步骤201，获取宿主文件。
在本实施例中，发布移动应用的方法运行于其上的电子设备(例如图1所示的产品服务器)可以通过有线连接方式或者无线连接方式从开发人员的终端获取宿主文件。其中，宿主文件为非业务功能文件，用以加载至少一个业务插件文件来实现与该业务插件文件关联的移动应用的业务功能。宿主文件不具有与用户交互的功能，其用于动态加载至少一个业务插件文件，而业务插件实现了呈现给用户，与用户进行交互的业务功能。业务功能被封装到业务插件中，一个程序员负责若干个业务插件，每一个业务插件由其相应功能涉及的界面、业务逻辑和数据访问等代码组成。每一个业务插件可以独立开发、测试和部署，开发者间不再需要对代码进行合并。宿主文件包括：1.插件加载框架，2.插件升级框架，3.公共UI(User Interface，用户界面)库和组件接口。插件加载框架可以加载业务插件文件实现业务功能。插件加载框架对CLR(Common Language Runtime，公共语言运行库)类加载进行扩展，使其能够从插件目录中正确加载到插件程序集。插件加载框架还需要引入插件描述方法，它来告知当前插件的基本信息、版本标识、以及这个插件所包含的程序集。插件升级框架可以支持业务插件的更新，当发现产品服务品上出现新版本业务插件时，可以自动更新。公共UI库和组件接口用于实现宿主对插件的加载。
在本申请中，可把移动应用整体架构分成：宿主+业务插件1+业务插件2+业务插件3等。全面插件化方案具体指，核心功能和非核心功能都是业务插件。比如，通常移动应用打开后会有3个或者多个标签页(TAB)，如图3a-3c所示，在传统的移动应用插件方案中，这3个TAB都是核心功能，都是集成在应用的主程序当中，而把二级菜单的一些页面，比如“摇一摇”，“礼物”，“工具”等非核心功能做成业务插件，而在本申请中，每个TAB都是一个业务插件，而且随着业务的增加和删除，TAB的个数也可以随之变化。
在本实施例的一些可选的实现方式中，宿主文件通过预定接口加 载所述至少一个业务插件文件。实现TAB的功能的业务插件都需要继承于预定接口类。
在本实施例的一些可选的实现方式中，在Android的解决方案中，预定接口包括Fragment类。至少一个业务插件的插件文件包括业务插件描述文件，各业务插件描述文件里面配置了各业务所要被加载的Fragment类的名称。移动应用启动的时候，宿主会去读取每个业务插件的业务插件描述文件，业务插件描述文件里面配置了该业务所要被加载的Fragment类的名称，宿主读取这些Fragment类的名称，通过初始化Fragment对象，并加载显示在宿主里面，从而达到每个TAB都是业务插件，且在宿主界面里面切换显示。
步骤202，根据宿主文件生成安装包。
在本实施例中，可以将宿主文件单独打包成移动应用的安装包，而不包括任何业务插件文件。也可将至少一个业务插件文件与宿主文件一起打包，其中，至少一个业务插件文件可以二进制文件形式存储在移动应用的资源目录中。后续开发中更新的业务插件也存储在移动应用的资源目录中。
步骤203，发布安装包。
在本实施例中，上述电子设备需要将安装包上传至市场服务器并且经审核通过后由市场服务器发布后，用户的移动终端才能从市场服务器下载该安装包。通常移动应用上线是需要市场的审核，审核时间多则1～2天，长则1个星期，另外，上线之后不是所有用户都会更新，这些都严重影响产品新特性的上线速度。另外，如果线上应用出现紧急问题的时候，也只能重新打包发布上线，严重耽误时间，影响了用户，导致用户流失。
在本实施例的一些可选的实现方式中，该方法还包括：获取用于更新移动应用的新业务插件文件；向已经安装并启动该移动应用的移动终端发送新业务插件文件。在产品新功能迭代的时候或在产品出现问题需要紧急修复时，不需要重新发版本，无需市场审核等待的时间，直接云端新增业务插件向移动终端推送，让用户无感知的实现了问题修复，使其自动下载更新。
在本实施例的一些可选的实现方式中，该方法还包括：获取用于更新移动应用的新业务插件文件；向已经安装并启动移动应用的移动终端发送插件更新请求；响应于接收到移动终端发送的更新确认消息，向移动终端发送新业务插件文件。即，通知移动终端可以更新业务插件，用户可自行选择是否进行更新。用户同意更新时才发新业务插件文件。
继续参见图3a-3c，图3a-3c是根据本实施例的发布移动应用的方法的应用场景的一个示意图。在图3a-3c的应用场景中，对于实现3个业务的移动应用，开发人员预先把移动应用整体架构分成：宿主+业务插件1+业务插件2+业务插件3。如图3a-3c所示，这3个标签页分别由实现核心功能的业务插件1、业务插件2、业务插件3生成。图3a中所示的是宿主加载了业务插件1后显示的业务1的界面。图3b中所示的是宿主加载了业务插件2后显示的业务2的界面。图3c中所示的是宿主加载了业务插件3后显示的业务3的界面。图3a-3c显示的都是一级标签页面，用户可在这三个界面之间切换选择。上述电子设备获取这4部分的文件，但没有将业务插件集成在应用的主程序当中，而是仅将宿主上传至市场服务器，将这3个业务插件文件存储在产品服务器中。市场服务器对宿主主程序进行审核后正式发布，移动终端可从市场服务器下载安装该移动应用的安装包。当用户安装并启用该移动应用时，从产品服务器的移动应用的资源目录获取3个业务插件加载到宿主中。当业务插件文件更新时，无需再上传到市场服务器，而直接发送给移动终端即可。
本申请的上述实施例提供的方法通过将移动应用分成宿主和业务插件，将宿主上传至市场服务器进行审核，并将业务插件文件存储在产品服务器中，产品服务器中的业务插件文件不用审核即可直接发给移动终端，实现移动应用的全面插件化，从而提高了移动应用的发布效率。
进一步参考图4，其示出了实现移动应用功能的方法的一个实施例的流程400。该实现移动应用功能的方法的流程400，包括以下步骤：
步骤401，启动移动应用。
在本实施例中，实现移动应用的方法运行于其上的电子设备(例如图1所示的移动终端)已经安装包含宿主模块及宿主模块加载的至少一个业务插件的移动应用后，启动该移动应用以实现所述移动应用的业务功能。其中，该宿主模块为非业务功能模块，不实现任何业务功能，其用于动态加载至少一个业务插件文件。
在本实施例的一些可选的实现方式中，移动终端可从网络设备获取根据宿主文件生成的安装包；安装该安装包以获得宿主模块。安装包括可只包括宿主模块，也可包括宿主模块和至少一个业务插件文件。
在本实施例的一些可选的实现方式中，安装安装包获得的宿主模块包括：1.插件加载框架，2.插件升级框架，3.公共UI(User Interface，用户界面)库和组件接口。插件加载框架可以加载业务插件文件实现业务功能。插件加载框架对CLR(Common Language Runtime，公共语言运行库)类加载进行扩展，使其能够从插件目录中正确加载到插件程序集。插件加载框架还需要引入插件描述方法，它来告知当前插件的基本信息、版本标识、以及这个插件所包含的程序集。插件升级框架可以支持业务插件的更新，当发现产品服务品上出现新版本业务插件时，可以自动更新。公共UI库和组件接口用于实现宿主对插件的加载。
在本实施例的一些可选的实现方式中，安装完该安装包之后，首次启动移动应用的时候从移动应用的资源目录中拷贝至少一个业务插件文件至移动应用的资源目录中。
在本实施例的一些可选的实现方式中，宿主模块通过预定接口加载所述至少一个业务插件。
在本实施例的一些可选的实现方式中，在Android的解决方案中，预定接口包括Fragment类，至少一个业务插件的插件文件包括业务插件描述文件，每个业务插件描述文件里面配置了其所要被加载的Fragment类的名称。
步骤402，宿主模块加载至少一个业务插件。
在本实施例中，拷贝至少一个业务插件文件至移动应用的资源目录中之后，宿主模块通过预定接口加载至少一个业务插件文件，使得 移动应用能够实现每个业务插件的功能。
在本实施例的一些可选的实现方式中，宿主模块通过预定接口加载至少一个业务插件文件，包括：读取至少一个业务插件的插件文件中每个业务插件描述文件中Fragment类的名称，通过Fragment类的名称初始化Fragment类对象，并将Fragment类对象加载到宿主模块中。从而达到每个TAB都是业务插件，且在宿主界面里面切换显示。
在本实施例的一些可选的实现方式中，该方法还包括：响应于检测到网络设备存储的业务插件文件发生变化，向网络设备发送插件更新请求；接收网络设备发送的发生变化的业务插件文件并重新加载。网络设备可以是市场服务器，也可以是产品服务器。网络设备上的业务插件文件发生变化时，可通知移动终端进行更新，也可直接向移动终端推送更新后的业务插件文件以使得移动终端的宿主重新加载业务插件文件。可选的，移动终端上的移动应用也可向网络设备主动发起业务插件文件检测，当检测到业务插件文件发生更新时，下载新的业务插件文件并重新加载。
从图4中可以看出，与图2对应的实施例相比，本实施例中的实现移动应用功能的方法的流程400突出了移动终端加载业务插件文件的步骤。由此，提高了移动终端上的移动应用的更新速度。
下面参考图5，其示出了适于用来实现本申请实施例的电子设备的计算机系统500的结构示意图。图5示出的电子设备仅仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。
需要说明的是，图5示出的电子设备可以为实现移动应用功能的的移动终端，包括但不限于智能手机、平板电脑、电子书阅读器、MP3播放器(Moving Picture Experts Group Audio Layer III，动态影像专家压缩标准音频层面3)、MP4(Moving Picture Experts Group Audio Layer IV，动态影像专家压缩标准音频层面4)播放器、膝上型便携计算机和台式计算机等等。此外图5示出的电子设备还可以为发布移动应用的设备，包括但不限于智能手机、平板电脑、膝上型便携计算机和台式计算机等等。
如图5所示，计算机系统500包括中央处理单元(CPU)501，其 可以根据存储在只读存储器(ROM)502中的程序或者从存储部分508加载到随机访问存储器(RAM)503中的程序而执行各种适当的动作和处理。在RAM 503中，还存储有系统500操作所需的各种程序和数据。CPU 501、ROM 502以及RAM 503通过总线504彼此相连。输入/输出(I/O)接口505也连接至总线504。
以下部件连接至I/O接口505：包括键盘、鼠标等的输入部分505；包括诸如阴极射线管(CRT)、液晶显示器(LCD)等以及扬声器等的输出部分507；包括硬盘等的存储部分508；以及包括诸如LAN卡、调制解调器等的网络接口卡的通信部分509。通信部分509经由诸如因特网的网络执行通信处理。驱动器510也根据需要连接至I/O接口505。可拆卸介质511，诸如磁盘、光盘、磁光盘、半导体存储器等等，根据需要安装在驱动器510上，以便于从其上读出的计算机程序根据需要被安装入存储部分508。
特别地，根据本公开的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本公开的实施例包括一种计算机程序产品，其包括承载在计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中，该计算机程序可以通过通信部分509从网络上被下载和安装，和/或从可拆卸介质511被安装。在该计算机程序被中央处理单元(CPU)501执行时，执行本申请的方法中限定的上述功能。需要说明的是，本申请所述的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本申请中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者 与其结合使用。而在本申请中，计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：无线、电线、光缆、RF等等，或者上述的任意合适的组合。
附图中的流程图和框图，图示了按照本申请各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，该模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
作为另一方面，本申请还提供了一种计算机可读介质，该计算机可读介质可以是上述实施例中描述的电子设备中所包含的；也可以是单独存在，而未装配入该电子设备中。上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被该电子设备执行时，使得该电子设备发布移动应用或实现移动应用功能。
以上描述仅为本申请的较佳实施例以及对所运用技术原理的说明。本领域技术人员应当理解，本申请中所涉及的发明范围，并不限于上述技术特征的特定组合而成的技术方案，同时也应涵盖在不脱离所述发明构思的情况下，由上述技术特征或其等同特征进行任意组合而形成的其它技术方案。例如上述特征与本申请中公开的(但不限于) 具有类似功能的技术特征进行互相替换而形成的技术方案。

Claims (14)

  1. 一种实现移动应用功能的方法，其特征在于，所述方法包括：
    响应于移动应用的启动，移动应用的宿主模块加载移动应用的至少一个业务插件，以实现所述移动应用的业务功能，其中，该宿主模块为非业务功能模块。
  2. 根据权利要求1所述的方法，其特征在于，所述方法包括：
    获取根据宿主文件生成的安装包；
    安装所述安装包以获得所述宿主模块。
  3. 根据权利要求1所述的方法，其特征在于，所述宿主模块包括：插件加载框架、插件升级框架、公共UI库和组件接口。
  4. 根据权利要求1所述的方法，其特征在于，所述至少一个业务插件的插件文件存储于所述移动应用的资源目录中。
  5. 根据权利要求1所述的方法，其特征在于，所述宿主模块通过预定接口加载所述至少一个业务插件。
  6. 根据权利要求5所述的方法，其特征在于，所述预定接口包括Fragment类，所述至少一个业务插件的插件文件包括业务插件描述文件，每个业务插件描述文件里面配置有其所要被加载的Fragment类的名称。
  7. 根据权利要求6所述的方法，其特征在于，所述宿主模块通过预定接口加载所述至少一个业务插件，包括：
    读取所述至少一个业务插件的插件文件中每个业务插件描述文件中Fragment类的名称，通过Fragment类的名称初始化Fragment类对象，并将所述Fragment类对象加载到所述宿主模块中。
  8. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    响应于检测到网络设备存储的业务插件发生变化，向所述网络设备发送插件更新请求；
    接收所述网络设备发送的发生变化的业务插件并重新加载。
  9. 一种发布移动应用的方法，其特征在于，所述方法包括：
    获取宿主文件，其中，所述宿主文件为非业务功能文件，用以加载至少一个业务插件文件来实现与该业务插件文件关联的移动应用的业务功能；
    根据所述宿主文件生成安装包；
    发布所述安装包。
  10. 根据权利要求9所述的方法，其特征在于，该方法还包括：
    获取所述移动应用的至少一个业务插件文件；
    以及根据所述宿主文件生成安装包包括：
    根据所述宿主文件以及至少一个业务插件文件生成安装包。
  11. 根据权利要求9-10之一所述的方法，其特征在于，所述方法还包括：
    获取用于更新所述移动应用的新业务插件文件；
    向已经安装并启动所述移动应用的移动终端发送所述新业务插件文件。
  12. 根据权利要求9-10之一所述的方法，其特征在于，所述方法还包括：
    获取用于更新所述移动应用的新业务插件文件；
    向已经安装并启动所述移动应用的移动终端发送插件更新请求；
    响应于接收到所述移动终端发送的更新确认消息，向所述移动终端发送所述新业务插件文件。
  13. 一种电子设备，包括：
    一个或多个处理器；
    存储装置，用于存储一个或多个程序，
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-12中任一所述的方法。
  14. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现如权利要求1-12中任一所述的方法。
PCT/CN2018/098573 2017-08-08 2018-08-03 发布移动应用的方法和电子设备 Ceased WO2019029451A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710669169.XA CN107463406A (zh) 2017-08-08 2017-08-08 发布移动应用的方法和电子设备
CN201710669169.X 2017-08-08

Publications (1)

Publication Number Publication Date
WO2019029451A1 true WO2019029451A1 (zh) 2019-02-14

Family

ID=60548515

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/098573 Ceased WO2019029451A1 (zh) 2017-08-08 2018-08-03 发布移动应用的方法和电子设备

Country Status (2)

Country Link
CN (1) CN107463406A (zh)
WO (1) WO2019029451A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107463406A (zh) * 2017-08-08 2017-12-12 上海连尚网络科技有限公司 发布移动应用的方法和电子设备
CN109032651B (zh) * 2018-08-24 2022-06-10 深圳创维－Rgb电子有限公司 应用更新方法、智能终端及计算机可读存储介质
CN111124525A (zh) * 2018-10-31 2020-05-08 北京国双科技有限公司 一种网站功能实现方法和装置
CN109656558B (zh) * 2018-12-19 2022-04-19 四川虹美智能科技有限公司 一种生成ui插件的方法及装置
CN109739551A (zh) * 2018-12-29 2019-05-10 上海连尚网络科技有限公司 应用程序发布系统、方法及装置，计算设备及存储介质
CN113032039B (zh) * 2021-03-12 2024-07-05 中国工商银行股份有限公司 应用的插件化改造方法、装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013006226A1 (en) * 2011-07-01 2013-01-10 Exxonmobil Upstream Research Company Plug-in installer framework
CN105653335A (zh) * 2015-12-31 2016-06-08 北京锐安科技有限公司 一种插件程序的控制方法和装置
CN105867956A (zh) * 2015-10-28 2016-08-17 乐视网信息技术（北京）股份有限公司 在宿主应用页面中展现插件视图元素的方法及装置
CN106569869A (zh) * 2016-11-14 2017-04-19 平安科技（深圳）有限公司 插件化打包方法及装置
CN106681718A (zh) * 2016-12-16 2017-05-17 武汉中地数码科技有限公司 一种基于工具集的桌面端插件框架及实现方法
CN107463406A (zh) * 2017-08-08 2017-12-12 上海连尚网络科技有限公司 发布移动应用的方法和电子设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104391716B (zh) * 2014-11-14 2018-06-05 百度在线网络技术（北京）有限公司 基于插件的应用程序实现方法及装置
CN104714828B (zh) * 2015-03-31 2017-06-09 北京奇虎科技有限公司 应用安装、运行方法及装置
CN106775793A (zh) * 2015-11-23 2017-05-31 卓望数码技术（深圳）有限公司 一种安卓应用免安装启动的方法、装置及终端
CN105872708A (zh) * 2015-12-30 2016-08-17 乐视致新电子科技（天津）有限公司 一种显示桌面生成方法、显示桌面生成系统和智能电视
CN105740033A (zh) * 2016-03-15 2016-07-06 广州彩瞳网络技术有限公司 一种终端设备、插件加载运行装置及插件加载运行方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013006226A1 (en) * 2011-07-01 2013-01-10 Exxonmobil Upstream Research Company Plug-in installer framework
CN105867956A (zh) * 2015-10-28 2016-08-17 乐视网信息技术（北京）股份有限公司 在宿主应用页面中展现插件视图元素的方法及装置
CN105653335A (zh) * 2015-12-31 2016-06-08 北京锐安科技有限公司 一种插件程序的控制方法和装置
CN106569869A (zh) * 2016-11-14 2017-04-19 平安科技（深圳）有限公司 插件化打包方法及装置
CN106681718A (zh) * 2016-12-16 2017-05-17 武汉中地数码科技有限公司 一种基于工具集的桌面端插件框架及实现方法
CN107463406A (zh) * 2017-08-08 2017-12-12 上海连尚网络科技有限公司 发布移动应用的方法和电子设备

Also Published As

Publication number Publication date
CN107463406A (zh) 2017-12-12

Similar Documents

Publication Publication Date Title
US11467816B1 (en) Method and system of running an application
CN106598667B (zh) 用于修复内核漏洞的方法和装置
WO2019029451A1 (zh) 发布移动应用的方法和电子设备
CN108346028A (zh) 一种业务审批处理方法、装置及系统
CN110554876A (zh) 用于编译安卓工程的方法和装置
CN111782231B (zh) 服务部署方法和装置
CN113138768B (zh) 应用程序包生成方法、装置、电子设备以及可读存储介质
CN113076163A (zh) 一种卡片渲染方法和装置
CN112835568B (zh) 一种项目构建方法和装置
CN112015384B (zh) 一种接口映射方法和装置
CN110895471A (zh) 安装包生成方法、装置、介质及电子设备
CN110928571A (zh) 业务程序开发方法和装置
CN114625479A (zh) 边缘计算中云边协同应用管理方法及对应的装置
CN115098082A (zh) 基于Jenkins插件的流水线脚本生成方法、系统、设备及介质
CN107809470B (zh) 应用程序自动化部署的方法和装置
CN115328627A (zh) 一种数据处理的方法和装置
CN112256326B (zh) 信息的处理方法、装置、设备及存储介质
CN109840073B (zh) 业务流程的实现方法和装置
CN109218338B (zh) 信息处理系统、方法和装置
WO2022237826A1 (zh) 用户界面的测试方法、系统、集群、介质及程序产品
CN113805878B (zh) 插件工程化方法、装置、计算机系统和介质
CN107247661B (zh) 支持对应用的安装包进行自动化验证的方法和系统
CN113407203B (zh) 一种部署应用的方法和装置
CN117762564A (zh) 函数处理方法及装置、电子设备和计算机可读存储介质
CN104461557A (zh) Puppet配置数据的处理方法及装置

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: 18843767

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 12/05/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18843767

Country of ref document: EP

Kind code of ref document: A1