Information processing device, storage medium and control method

Abstract

The present invention discloses an information processing device, a storage medium and a control method. A method for an information processing device, in which a hybrid application having two functions, the function of a native application and the function of a network application, is run, and the information processing device can communicate with a server, the method comprising: after accepting a predetermined user operation, sending a request for obtaining information about the network application to the server, reading information about the native application pre-stored in the hybrid application, and displaying information generated from the information obtained as a response to the obtaining request and the read information as a result of the predetermined user operation.

Description

Technical Field

[0001] The present invention relates to an information processing device, a storage medium and a control method. Background Art

[0002] In recent years, many commercial enterprises have developed their own products using open source software (OSS). The use of OSS has advantages such as reducing development costs and applying the latest technology. Japanese Patent Publication No. 2016-157282 describes a method for stably fulfilling the obligations involved in OSS licenses. Software applications using OSS must display the license texts of multiple OSS used (hereinafter referred to as license information). Such software applications also need to present the content of the agreement between the software developer and the purchaser, called the End User License Agreement (EULA). Therefore, many applications (hereinafter referred to as applications) are configured to provide license information and EULA from menus or help.

[0003] For example, OSS is widely used in the development of mobile applications (hereinafter referred to as mobile applications) to be installed in mobile terminals to expand the functions of mobile terminals. After installation in the mobile terminal, some mobile applications act as "native applications" that can be run without accessing a server, while other mobile applications access a network server to execute "network applications" on the network server. Generally, native applications save license information in them, and network applications save license information in the network server.

[0004] In recent years, hybrid mobile applications (hereinafter referred to as hybrid applications) that function as both native applications and web applications have achieved widespread popularity. Basically, hybrid applications usually run when they can communicate with the server that provides resources, but some hybrid applications can perform certain functions even in a non-communication state.

[0005] Taking OSS as an example, hybrid applications need to allow the display of both license information about the OSS used in native applications and license information about the OSS used in network applications. If both types of license information are stored in the hybrid application, like traditional native applications, not only when the OSS used in the native application is changed, but also when the OSS used in the network application is changed, the mobile application in the mobile terminal for updating the license information needs to be updated. That is, the frequency with which mobile applications need to be updated increases, which brings development burdens to application providers and inconveniences to users. On the other hand, if both types of license information are stored in the network server as in traditional network applications, each time the license information is to be displayed, it is necessary to obtain both types of license information from the server. This increases the amount of communication and may result in a reduced response speed to user operations.

[0006] Therefore, the present invention is directed to providing a method of appropriately displaying information about a native application and information about a network application without reducing user convenience. Summary of the invention

[0007] According to one aspect of the present invention, a method for an information processing device, in which a hybrid application having two functions, namely, functions of a native application and functions of a network application, runs in the information processing device, and the information processing device can communicate with a server, the method comprising: after accepting a predetermined user operation, sending a request for obtaining information about the network application to the server, reading information about the native application pre-saved in the hybrid application, and displaying information generated from the information obtained as a response to the obtaining request and the read information, as a result of the predetermined user operation.

[0008] Further features of the present invention will become apparent from the following detailed description of exemplary embodiments with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 It is the overall picture of the system.

[0010] Figure 2 It is a hardware block diagram of a mobile device.

[0011] Figure 3 This is the hardware block diagram of the server.

[0012] Figure 4 It is the software block diagram of the entire system.

[0013] Figure 5 It is a diagram showing online screen transition of a mobile application.

[0014] Figure 6 It is a diagram showing offline screen transition of a mobile application.

[0015] Figure 7 is a flow chart of a license display process in a mobile application.

[0016] Figure 8 is a flow chart of the update process in the mobile app.

[0017] Fig. 9 It is a flowchart of background processing in mobile applications. DETAILED DESCRIPTION

[0018] Exemplary embodiments for implementing the present invention will be described with reference to the accompanying drawings. Note that the exemplary embodiments described below do not limit the present invention to the scope of the claims, and all combinations of features described with respect to the exemplary embodiments are not necessarily essential to the solutions of the present invention.

[0019] [System Configuration]

[0020] Figure 1 1 is a diagram showing the overall configuration of a system according to a first exemplary embodiment. The information processing system includes a mobile terminal 110 and a server 120. The mobile terminal 110 is communicably connected to a server 120 such as a A server 120 provides various services on the Internet through a local area network (LAN) or a wide area network (WAN).

[0021] The mobile terminal 110 has various functions such as phone, mail, web browser, and camera, and is a smart phone or tablet computer. The mobile terminal 110 is an example of an information processing device, which may be a personal computer (PC) or the like. The server 120 is an example of a server, which has a function of saving files in various formats such as Hypertext Markup Language (HTML) for describing web pages, JavaScript, images, and texts. The server 120 provides web pages and various types of information in response to requests from external terminals such as the mobile terminal 110.

[0022] The information processing system in the present exemplary embodiment is formed of the mobile terminal 110 and the server 120 , but the information processing system is not limited to this structure.

[0023] [Hardware configuration of mobile terminal]

[0024] Figure 21 is a hardware block diagram of the mobile terminal 110. The mobile terminal 110 includes a control unit 210 and a display and operation unit 220. The control unit 210 includes a central processing unit (CPU) 211, a read-only memory (ROM) 212, a random access memory (RAM) 213, a solid state drive (SSD) 214, a display and operation unit interface (I / F) 215, and a network I / F 216 described below to control the operation of the entire mobile terminal 110. The CPU 211 reads a control program stored in the ROM 212, etc. to execute and control various functions of the mobile terminal 110, such as a camera and communication. The RAM 213 is used as a temporary storage area such as a main memory or a work area of ​​the CPU 211. In the present exemplary embodiment, one CPU 211 uses one memory (RAM 213 or SSD 214) to perform the processing described below with reference to the flowchart, but the present invention is not limited thereto. For example, multiple CPUs and multiple RAMs or SSDs can cooperate to perform processing. The SSD 214 is a large-capacity storage unit that stores HTML files, JavaScript files, image data, text data, various programs, etc. The display and operation unit I / F 215 is an interface for connecting the display and operation unit 220 and the control unit 210. The display and operation unit 220 includes a touch panel display and hardware keys to accept operations, inputs and instructions from the user, or output a screen to be presented to the user. The network I / F 216 is an interface for connecting the control unit 210 (mobile terminal 110) to a network such as a wireless LAN or WAN. The mobile terminal 110 uses the network I / F 216 to send or receive various types of information, such as images and text, to services on the Internet.

[0025] [Server hardware configuration]

[0026] Figure 3 is a hardware block diagram of the server 120 .

[0027] The server 120 includes a CPU 311, a ROM 312, a RAM 313, a hard disk drive (HDD) 314, and a network I / F. When the menu screen displays the text of the license, the mobile application 400 obtains the network license information on the server side from the server. The CPU 311 reads the control program stored in the ROM 312 and performs various processes to control the entire operation. The RAM 313 is used as a temporary storage area such as the main memory or work area of ​​the CPU 311. The HDD 314 is a large-capacity storage unit for storing HTML files, JavaScript files, image data, text data, various programs, etc. The network I / F 315 is an interface for connecting the server 120 to the Internet. After receiving a processing request from another device, the server 120 sends / receives various types of information to / from another device (such as the mobile terminal 110) via the network I / F 315.

[0028] [Software configuration of information processing system]

[0029] Figure 4 211 reads a control program stored in the ROM 212 or the SSD 214 , or reads a control program stored in the ROM 312 or the HDD 314 , and the functional units are implemented by the CPU 211 reading a control program stored in the ROM 212 or the SSD 214 , or by the CPU 311 reading a control program stored in the ROM 312 or the HDD 314 .

[0030] The mobile application 400 is an application installed on the mobile terminal 110 (hereinafter, the term application will be abbreviated as app). Generally, some mobile applications act as native applications, while other applications execute network applications maintained in the server. The native application operates using the application screen information pre-installed on the mobile terminal, and can perform functions specific to the mobile terminal (camera, access to files in the mobile terminal, etc.). The native application can operate when the mobile terminal is not connected to the network. On the other hand, in order to execute the network application, the mobile terminal accesses the server via the network each time to obtain application screen information, etc., and displays the information on the network browser. The network application is based on network technology and is maintained in the server. In order to execute the network application, the mobile terminal needs to be connected to the network and access the server. In addition, some mobile applications combine the functions of the native application and the functions of the network application (hereinafter referred to as hybrid applications). The hybrid application contains a network layer and a native layer, in which the network application is executed by accessing the server in the network layer, and in which the functions that cannot be processed in the network layer and are unique to the mobile terminal are executed in the native layer. The following description is based on the assumption that the mobile application 400 is a hybrid application with a "native" layer and a "network" layer.

[0031] The mobile application 400 has a communication unit 410, a control unit 411, a data management unit 412, and a screen display unit 413, and is formed of a network layer 414 and a native layer 415. The communication unit 410, the control unit 411, and the screen display unit 413 are included in each of the network layer 414 and the native layer 415, and the data management unit 412 is included in the native layer 415. Functional units included in these layers are not limited to these units.

[0032] The communication unit 410 requests the server 120 to perform various processes. For example, in response to a request from the mobile application 400, the communication unit 410 sends a request for screen layout information (HTML file, JavaScript file, etc.) necessary for screen display to the server 120. The communication unit 410 also requests open source software (OSS) license information. The license information here includes the text (text file, etc.) of the OSS license. The communication unit 410 communicates with the server 120 using a protocol such as Representational State Transfer (REST) ​​or Simple Object Access Protocol (SOAP), but another communication method may be used.

[0033] The control unit 411 performs general control processing such as issuing communication instructions, screen display instructions, and data management instructions, or executes a control method in the mobile application 400. When the mobile application 400 is started, the control unit 411 obtains screen layout information from the server 120 via the communication unit 410, and issues a screen display instruction to the screen display unit 413 based on the screen layout information.

[0034] The data management unit 412 manages general information about the mobile application 400, such as the end user license agreement (EULA) and OSS license information of the mobile application 400. In the present exemplary embodiment, the data management unit 412 saves and manages the text of the licenses of multiple OSSs used in the native application on the mobile side (hereinafter referred to as the native license information) and the text of the licenses of multiple OSSs used in the network application on the server side (hereinafter referred to as the network license information) in the program. For the license information, when the mobile application is installed, the latest data is pre-saved in the data management unit 412. When the mobile application 400 is updated, the native license information saved in the data management unit 412 is updated as needed. When the user issues an instruction for displaying the license information, the network license information saved in the data management unit 412 is updated, and, under the instruction from the control unit 411, the latest license information is obtained from the server 120 via the communication unit 410. In the present exemplary embodiment, various data are managed in the form of text files, but the method for managing data is not limited to this. In addition, the type of managed data is not limited to this.

[0035] The screen display unit 413 displays a user interface (UI) screen for accepting user operations on the liquid crystal display unit having a touch panel function of the display and operation unit 220 in the mobile terminal 110. The UI screen here is a screen provided by the server 120 and a screen pre-stored in the mobile application 400.

[0036] The server 120 has a request control unit 431 and a data management unit 432, and provides a network application to an external device that has accessed the server 120. The request control unit 431 is in a standby state in a state capable of receiving a request from an external device. Upon receiving a processing request, the server 120 instructs the data management unit 432 to appropriately perform processing according to the request. The data management unit 432 saves and manages screen layout information and license information of the OSS used on the server side. In the event that the OSS used is changed, the license information is also updated. In response to a request from a web browser running on an information processing device such as a mobile terminal 110 connected via the Internet, the data management unit 432 returns screen layout information or OSS license information required for screen display.

[0037] [Screen transitions in mobile applications (capable of sending / receiving information to / from the server)]

[0038] Figure 5 2 is a diagram showing an example of screen transitions in the mobile application 400 in a state where information can be sent / received to / from the server 120. The mobile application 400 is an application that instructs a printer (not shown) to print an image captured by the camera of the mobile terminal 110 or an image saved in the SSD 214 of the mobile terminal 110 via a screen provided by the server 120. The camera function and the function of accessing files in the mobile terminal 110 are performed in the native layer, while the display of the screen for the user to issue a print instruction and the execution of the print instruction are performed in the network layer. The mobile application 400 has both functions of a native application and a network application. Therefore, it is necessary to display both the license information of the OSS used in the native application and the license information of the OS used in the network application on the mobile application 400.

[0039] First, when the mobile application 400 is started, the mobile application 400 acquires screen layout information required for screen display from the server 120, and displays a web page in the display area of ​​the main screen 500. Then, when the menu button 501 on the main screen 500 is operated, a screen transition to the menu screen 510 is performed. Displayed on the menu screen 510 is a link menu 511 including links to EULA, third-party licenses, etc. associated with the mobile application 400. The link to the third-party license is a link for displaying text of the licenses of a plurality of OSSs used in the mobile application 400.

[0040] Next, when a third-party license in the link menu 511 is pressed, the screen transitions to a document screen 520 on which a third-party license 521 is displayed. Figure 5 An example of pressing a third-party license in the link menu 511 is shown. However, if another link is pressed, it switches to a screen corresponding to the pressed link. The displayed third-party license 521 includes the text of the licenses of multiple OSSs used in native applications and network applications (native license information 522 and network license information 523). When installing or updating a mobile application, the native license information is saved in the data management unit 412. The network license information can also be saved in the data management unit 412 when the mobile application is installed. In order to display the text of the license, the license information stored in the data management unit 412 is displayed. At this time, if the mobile terminal 110 is online and can communicate with the server 120, the mobile terminal 110 communicates with the server 120 to obtain the network license information, and displays the obtained network license information together with the pre-saved native license information.

[0041] In this way, if the mobile application 400 can communicate with the server 120 when the license information is displayed, the mobile application 400 obtains the network license information 523 from the server 120. At this time, the mobile application 400 can save the obtained network license information 523 to the data management unit 412, or can update the network license information saved in the data management unit 412 with the obtained network license information 523. In this way, when the mobile application 400 and the server 120 can communicate, the mobile application 400 can display the latest network license information 523.

[0042] Typically, a native application stores license information therein and updates the stored license information when the application is updated. If the mobile application 400 stores the native license information and the network license information therein like a native application, the mobile application 400 needs to request the user to update the application following each change of the network license information. The change frequency of the OSS used in the network application is higher than that in the native application, that is, the network license information changes frequently. Requesting the user to update the application like a native application will cause trouble to the user. Therefore, obtaining the network license information from the server when the mobile terminal is online makes it possible to avoid unnecessary updates.

[0043] Typically, a network application stores network license information in a server so that the mobile terminal accesses the server to obtain the license information. If both the local license information and the network license information of the mobile application 400 are stored in the server as in the case of the network application, the amount of communication data and the amount of processing time required to obtain the license will increase. Therefore, between the local license information and the network license information, storing the local license information in the mobile application makes it possible to reduce the amount of communication data and the amount of processing time required to obtain the license information.

[0044] [Screen transitions in mobile apps (cannot send / receive information to / from the server)]

[0045] Figure 6 4 is a diagram showing an example of screen transition in the mobile application 400 in a state where communication with the server 120 is impossible.

[0046] First, when the mobile application 400 is started, the mobile application 400 displays a network connection error screen 600 indicating that the mobile application 400 is offline.

[0047] When the menu button 601 in the network connection error screen 600 is pressed, the screen transitions to a menu screen 610. Displayed on the menu screen 610 is a link menu 611 including links to the EULA and third-party licenses associated with the mobile application 400, as in the case of the menu screen 510.

[0048] Next, when any link in the link menu 611 is pressed, the screen switches to the document screen 620 corresponding to the pressed link. Figure 6 , a third party license is pressed in the link menu 611, and then a third party license 621 is displayed on the document screen 620. As in the case of the third party license 521, the displayed third party license 621 includes the text of the license (the local license information 622 and the network license information 623).

[0049] If the mobile application 400 cannot communicate with the server 120 (for example, when the mobile application 400 cannot connect to the Internet or the mobile application 400 is turned off), the mobile application 400 displays the license information stored in the control unit 411. That is, the information in the control unit 411 is not updated. As described above, in the case where the network license information stored in the control unit 411 is updated because the license information was displayed online by the user in the past, the updated network license information can be displayed.

[0050] That is, by saving the network license information acquired when the mobile application is communicable with the server in the mobile application, the latest possible information can be displayed even when the mobile application is offline.

[0051] For the local license information 522 or 622, the information stored in the data management unit 412 is displayed regardless of the network status. If the text of the local license is changed, the mobile application needs to be updated because changing the text of the local license always involves changing the configuration of the mobile application. Therefore, when updating the mobile application, the text of the local license is changed.

[0052] [Software Processing and Flowchart in First Exemplary Embodiment]

[0053] Figure 7 4 is a flowchart showing details of a process for displaying the text of a license in the mobile application 400. The steps in the flowchart are implemented by the CPU 211 reading and executing a control program stored in the ROM 212 and the SSD 214. This process will now be described in detail.

[0054] This process is started by detecting that the menu screen 510 or 610 in the mobile application 400 is displayed.

[0055] In step S701, the screen display unit 413 of the mobile application 400 determines whether any link included in the link menu 511 or 611 displayed on the menu screen 510 or 610 has been pressed. If the screen display unit 413 determines that any link has been pressed ("Yes" in step S701), the process proceeds to step S702. If the screen display unit 413 determines that no link has been pressed ("No" in step S701), the process returns to step S701. In the present exemplary embodiment, any link is Figure 5 or Figure 6 "Third-Party License" is shown. However, the optional information is not limited thereto.

[0056] In step S702 , if the communication unit 410 of the mobile application 400 can communicate with the server 120 , the communication unit 410 sends a request for sending network license information to the server 120 .

[0057] In step S703, the control unit 411 of the mobile application 400 determines whether the network license information has been acquired as a response to the acquisition request in step S702. If the control unit 411 determines that the network license information has been acquired ("Yes" in step S703), the process proceeds to step S704. If the control unit 411 determines that the network license information has not been acquired ("No" in step S703), the process proceeds to step S705.

[0058] In step S704, the control unit 411 of the mobile application 400 saves the network license information received from the server 120 via the communication unit 410 into the data management unit 412, or updates the information in the data management unit 412 with the network license information received from the server 120. Therefore, even when the license information of the OSS used in the network application on the server 120 side has been updated, the latest license information can be saved into the data management unit 412. The processing in step S704 does not necessarily need to be performed every time, and may be performed only when a predetermined period of time has passed since the last execution or when a save instruction has been issued by the user.

[0059] In step S705 , the control unit 411 of the mobile application 400 acquires the network license information from the data management unit 412 .

[0060] In step S706 , the control unit 411 of the mobile application 400 acquires the native license information from the data management unit 412 .

[0061] In step S707, the control unit 411 of the mobile application 400 combines the license information acquired in steps S705 and S706, and displays the combined license information on the screen display unit 413 as a result of pressing the link in step S701 ( Figure 5 Third-party licenses shown in 521 or Figure 6 Third-party license 621 shown).

[0062] As described above with reference to the flowchart, each time the license information is displayed, if the mobile application 400 can communicate with the server 120, the mobile application 400 acquires and displays the network license information from the server 120. On the other hand, regarding the license information of the native application, the license information pre-saved in the mobile application (for example, when the mobile application is installed) is acquired and displayed. That is, when the information of the native application and the network application is displayed in the hybrid application, the information about the native application is acquired from the hybrid application, and the information about the network application is acquired from the server each time.

[0063] By saving the network license information acquired from the server 120 into the mobile application, the latest possible license information can be displayed in the mobile application even in an offline environment.

[0064] Will refer to Figure 8 A process of updating the native license information in the mobile application 400 is described. Figure 8 4 is a flowchart of a process in which the mobile terminal 110 receives an update request of the mobile application 400 and executes the update. The steps in the flowchart are implemented by the CPU 211 reading and executing a control program stored in the ROM 212 or the SSD 214.

[0065] In step S801, CPU 211 determines whether an update request for mobile application 400 has been received. If CPU 211 determines that an update request has been received ("Yes" in step S801), the process proceeds to step S802. If CPU 211 determines that an update request has not been received ("No" in step S801), CPU 211 repeats step S801. In step S802, CPU 211 notifies the user that mobile application 400 needs to be updated. In step S803, CPU 211 determines whether an update instruction for mobile application 400 has been accepted. If CPU 211 determines that an instruction has been accepted ("Yes" in step S803), the process proceeds to S804. If CPU 211 determines that an instruction has not been accepted ("No" in step S803), CPU 211 repeats step S803. In step S804, CPU 211 updates mobile application 400. At this time, the local license information stored in the data management unit 412 is updated.

[0066] As described above with reference to the flowchart, in the case where the mobile application 400 needs to be updated, the mobile application 400 can be updated by accepting a user operation. When the mobile application 400 is updated, the local license information in the application can be updated. In this example, the mobile application 400 is updated when the user operation is accepted. However, if automatic update is preset, the mobile application 400 can also be automatically updated without accepting a user operation. The license information in the application to be updated when the application is updated is not limited to the local license information, and the network license information can also be updated.

[0067] According to the above exemplary embodiment, when an application having both a native application function and a network application function receives an instruction for displaying license information, the application sends a request for acquiring the license information of the network application and reads the license information of the native application pre-stored in the application. Then, the application displays the license information of the network application acquired in response to the acquisition request and the read license information of the native application.

[0068] [Software Processing and Flowchart in Second Exemplary Embodiment]

[0069] According to the above method of displaying license information, when the user instructs the mobile application 400 to display the text of the license from the menu screen, the mobile application 400 obtains the network license information on the server side from the server 120. Therefore, there is a disadvantage that the network license information stored in the data management unit 412 is not updated unless the user instructs to display the license information.

[0070] Therefore, a method for solving the above-mentioned disadvantages will be described.

[0071] Fig. 9 2 is a flowchart showing in detail the update process of the license information in the mobile application 400 according to the second exemplary embodiment. The steps in the flowchart are implemented by the CPU 211 reading and executing the control program stored in the ROM 212 or the SSD 214. Hereinafter, the process will be described in detail.

[0072] The process is started by detecting that the mobile application 400 is running in the background. As long as the mobile application 400 is running in the background, the process in the flowchart is repeatedly executed at certain time intervals (for example, every day or two days).

[0073] In step S901, the control unit 411 of the mobile application 400 determines whether background processing can be performed. If the control unit 411 determines that background processing can be performed ("Yes" in step S901), the process proceeds to step S902. If the control unit 411 determines that background processing cannot be performed ("No" in step S901), the process returns to step S901.

[0074] In step S902 , the communication unit 410 of the mobile application 400 sends a request to obtain network license information to the server 120 .

[0075] In step S903, the control unit 411 of the mobile application 400 determines whether the network license information has been acquired in response to the acquisition request in step S902. If the control unit 411 determines that the network license information has been acquired ("Yes" in step S903), the process proceeds to step S904. If the control unit 411 determines that the network license information has not been acquired ("No" in step S903), the process terminates.

[0076] In step S904 , the control unit 411 of the mobile application 400 saves the network license information received from the server 120 via the communication unit 410 into the data management unit 412 , or updates the information in the data management unit 412 with the network license information received from the server 120 .

[0077] A method for updating the license information of the mobile application 400 has been described. In this way, even if the user has not displayed the license information, the network license information in the application can be updated at a certain time interval. Therefore, even if offline, the latest network license information obtained online can be displayed.

[0078] In this exemplary embodiment, the case where the mobile application 400 updates the license information at a certain time interval when running in the background is described as an example. However, the time of the update is not limited to this. Whenever the mobile application 400 is started, the mobile application 400 can update the network license information, or the server 120 can send a notification of the necessity of updating the license information to the mobile application 400.

[0079] In the above exemplary embodiment, the text of the license for OSS has been displayed as an example. However, the content to be displayed is not limited to the text of the OSS license. For example, the above exemplary embodiment is also applicable to the case of displaying EULA, etc. In addition, the present invention includes a system and its functions configured by appropriately combining the above exemplary embodiments.

[0080] Other embodiments

[0081] The embodiments of the present invention may also be implemented by providing software (program) for performing the functions of the above-described embodiments to a system or device via a network or various storage media, and a computer or a central processing unit (CPU) or a microprocessing unit (MPU) of the system or device reads and executes the program.

[0082] While the present invention has been described with reference to exemplary embodiments, it is to be understood that the invention is not limited to the disclosed exemplary embodiments.The scope of the following claims is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures and functions.

Claims

1. A method for an information processing device, wherein a hybrid application having functions related to a predetermined service is executed on the information processing device, wherein the hybrid application has both functions of a native application and functions of a network application in the functions related to the predetermined service, the method comprising: Receive predetermined user actions in hybrid applications, Acquiring first information about functions of a web application among functions related to a predetermined service from a server, and acquiring second information related to functions of a native application among functions related to the predetermined service and stored in advance in the hybrid application, wherein the first information is license information about the web application and the second information is license information about the native application; and displaying the first information and the second information, The license information about the web application is the license terms of the open source software OSS used in the web application, and the license information about the native application is the license terms of the OSS used in the native application.

2. The method according to claim 1, wherein The predetermined user operation is an instruction for displaying first information about the web application and second information about the native application on the information processing apparatus.

3. The method according to claim 1, further comprising: In the information processing apparatus, first information on the web application acquired in response to the acquisition request is stored.

4. The method according to claim 3, wherein: In a case where the first information about the web application cannot be acquired as a response to the acquisition request, the saved first information about the web application and the second information about the native application are read and displayed.

5. The method according to claim 3, comprising: Sending a request for obtaining the first information to the server at a predetermined time interval; as well as When saving, the first information acquired in response to the transmitted acquisition request is further saved.

6. The method according to claim 1, wherein When the hybrid application is updated, the second information about the native application that is pre-stored in the hybrid application is updated.

7. The method according to claim 1, wherein The information processing apparatus is a mobile terminal capable of instructing a printer to print an image stored in the mobile terminal.

8. An information processing device running a hybrid application having functions related to a predetermined service, wherein the hybrid application has both functions of a native application and functions of a network application, the device comprising: The display unit is configured to: receive a predetermined user operation in the hybrid application, obtain first information about functions of the web application among functions related to the predetermined service from a server, and obtain second information related to functions of the native application among functions related to the predetermined service and pre-stored in the hybrid application, wherein the first information is license information about the web application and the second information is license information about the native application, and display the first information and the second information; The license information about the web application is the license terms of the open source software OSS used in the web application, and the license information about the native application is the license terms of the OSS used in the native application.

9. A non-transitory computer-readable storage medium storing a program causing a computer to execute a method for an information processing device, wherein a hybrid application having functions related to a predetermined service is executed on the information processing device, wherein the hybrid application has both functions of a native application and functions of a network application, the method comprising: Receive predetermined user actions in hybrid applications, Acquiring first information about functions of a web application among functions related to a predetermined service from a server, and acquiring second information related to functions of a native application among functions related to the predetermined service and stored in advance in the hybrid application, wherein the first information is license information about the web application and the second information is license information about the native application; and displaying the first information and the second information, The license information about the web application is the license terms of the open source software OSS used in the web application, and the license information about the native application is the license terms of the OSS used in the native application.

Images