Information processing device, method for controlling the information processing device, and program

Abstract

To improve usability when updating applications placed on a portal application. [Solution] A portal application program that can be operated on an information processing device and launches at least one application, characterized in that the information processing device functions as a display control means capable of switching between displaying a first screen on which a first application and a second application can be placed and a second screen on which a second application can be placed, and an update control means that prioritizes the update processing of the second application placed on the first screen over the update processing of the second application placed only on the second screen.

Description

Technical Field

[0001] The present disclosure relates to an information processing apparatus, a control method for an information processing apparatus, and a program.

Background Art

[0002] Generally, when applying updates of a plurality of software to one device or system, it has been an issue to appropriately control the update timing of each software. In Patent Document 1, a method is disclosed in which the server stores information on the priority indicating which software update is to be performed first, and based on the information received from the server, updates are performed in order from the software with the highest priority.

[0003] Also, a portal application for providing software that provides each function to an information processing apparatus as individual applications for each function is known. Also, in each application arranged on the portal application, when the user downloads the application, the latest version of the application may be published on the server of the provider.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] It is required to improve the usability in updating applications arranged on the portal application.

Means for Solving the Problems

[0006] A program according to one aspect of the present disclosure is a portal application program for launching at least one application that operates on an information processing device, characterized in that the information processing device functions as a display control means capable of switching between displaying a first screen on which a first application and a second application can be placed and a second screen on which the second application can be placed, and an update control means that prioritizes the update processing of the second application placed on the first screen over the update processing of the second application placed only on the second screen. [Effects of the Invention]

[0007] According to this disclosure, it is possible to improve the usability of updating applications that are deployed on a portal application. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram shows the overall system configuration. [Figure 2] This is a diagram showing the configuration of the terminal device. [Figure 3] This is a diagram showing the printer configuration. [Figure 4] This is an example of the top screen of a portal application. [Figure 5] This is an example of the list of linked applications screen for a portal application. [Figure 6] This is an example of a customization screen for a portal application. [Figure 7] This is an example of a customization screen for a portal application. [Figure 8] This is an example of a customization screen for a portal application. [Figure 9] This is an example of a dialog box for selecting integrated applications in a portal application. [Figure 10] This is an example of a customization screen for a portal application. [Figure 11]This is a flowchart illustrating the update process for linked applications. [Figure 12] This is an example of application version information managed by the application distribution server. [Figure 13] This is an example of an application update confirmation dialog. [Figure 14] This is a flowchart representing the update order control process. [Figure 15] This is an example of a list showing the priority order for update processing of linked applications. [Modes for carrying out the invention]

[0009] Preferred embodiments of this disclosure will be described in detail below with reference to the attached drawings. Note that the following embodiments are not intended to limit the scope of this disclosure as claimed, and not all combinations of features described in these embodiments are necessarily essential to the solutions of this disclosure. Furthermore, in the attached drawings, the same or similar components are given the same reference numerals, and redundant descriptions are omitted.

[0010] <Embodiment 1> Generally, when there are many applications that require updating, the update process can take a long time. This can lead to delays when a user attempts to run a high-priority application, as the target application may not be updated. The process in this embodiment prioritizes updating applications that users are likely to use frequently, thereby reducing the likelihood of users experiencing delays. The details are explained below.

[0011] Figure 1 is a diagram showing the system configuration of this embodiment. The system of this embodiment consists of a terminal device (hereinafter also referred to as an information processing device) 100, a printer 200 (hereinafter also referred to as an image processing device), and an application distribution server 300. These devices are connected to each other so that they can communicate with one another. The terminal device 100 can communicate with the printer 200 via a LAN or USB cable. The terminal device 100 can also communicate with the application distribution server 300 via the Internet. The application distribution server 300 is a server for distributing applications that run on the terminal device 100.

[0012] FIG. 2 is a diagram showing the hardware configuration of the terminal device 100. The terminal device 100 includes an input interface 110, a CPU 111, a ROM 112, a RAM 113, an external storage device 114, an output interface 115, an input / output interface 116, and a network interface (NETIF) 120. Input devices such as a keyboard 118 and a pointing device 117 are connected to the input interface 110, and display devices such as a display unit 119 are connected to the output interface 115. The NETIF 120 controls data transfer with external devices via a network. In the example of FIG. 2, the display unit 119, the pointing device 117, and the keyboard 118 are described as examples of devices separate from the terminal device 100, but they may be included in the terminal device 100. Also, the display unit 119 may be a touch panel display having the function of an input / output device. An initialization program is stored in the ROM 112. Application programs, an OS (abbreviation for Operating System), print data generation software, and various other data are stored in the external storage device 114. In this embodiment, a terminal device 100 equipped with Microsoft's Windows (registered trademark) as the OS will be described as an example. The RAM 113 is used as a work memory and the like when executing various programs stored in the external storage device 114, enabling various programs to operate within the terminal device 100. In this embodiment, the CPU 111 executes the functions and processes described below in the terminal device 100 by performing processing according to the procedures of the programs stored in the ROM 112. The input / output interface 116 may be wired or wireless. Also, the terminal device 100 and the printer 200 may be connected via a WAN such as a LAN or the Internet.

[0013] FIG. 3 is a diagram showing the hardware configuration of the printer 200. As shown in FIG. 3, the printer 200, which is an output device, has a print unit 211, a scanner unit 212, a display unit 213, an operation unit 214, a communication unit 215, a CPU 216, a storage unit 217, and a timer 218 connected to each other. The print unit 211 executes a recording process of recording an image indicated by image data on a recording sheet. The scanner unit 212 executes a scanning process of reading an image recorded on a recording sheet and generating image data. The printer 200 may further execute a FAX process of transmitting and receiving FAX, a copying process of reading an image recorded on a recording sheet and recording it on another recording sheet, and the like. The display unit 213 includes a display screen for displaying various information. The operation unit 214 receives a user operation of selecting an object displayed on the display screen of the display unit 213.

[0014] The communication unit 215 is an interface for communicating with an external device through a communication network. The communication unit 215 according to the present embodiment is connected to the terminal device 100 and the Internet via USB, wireless LAN, or wired LAN. The CPU 216 controls the operation of the printer 200. The CPU 216 acquires and executes various programs described later from the storage unit 217 based on various information output from the operation unit 214 and various information acquired from an external device through the communication unit 215. The storage unit 217 has a program storage unit 217A and a data storage unit 217B. The program storage unit 217A stores an OS and a control program for controlling the operation of the printer 200. The data storage unit 217B stores information necessary for the execution of the control program or information on the result processed by the control program. The timer 218 counts the elapsed time since the timer was started. The program stored in the program storage unit 217A can acquire the elapsed time from the timer 218.

[0015] In this embodiment, the printer 200 is described as an inkjet printer that prints by ejecting ink onto the paper surface, but printing may be performed by other methods (e.g., electrophotography). Also, the terminal device 100 may be an information processing device such as a desktop computer, smartphone, tablet terminal, or laptop computer.

[0016] (About the portal application) Next, we will describe the portal application that operates on terminal device 100.

[0017] Figure 4 shows an example of the top screen (first screen) of the portal application. The top screen 400 is the first screen displayed when the portal application is launched. The portal application provides functions that can be used in common for multiple printers. For example, when the photo print button 401 is pressed, the portal application displays and controls a UI to receive instructions on which image file to print from the unillustrated image files stored in ROM 112. The portal application then reads the specified image file and executes printing to the printer driver of the selected printer. Similarly, when the document print button 402 is pressed, the portal application displays and controls a UI to receive instructions on which document file to print from the unillustrated document files stored in ROM 112. The portal application then reads the specified document file and executes printing to the printer driver of the selected printer. Furthermore, when the scan button 403 is pressed, the portal application instructs the printer 200 to perform a scan operation via the input / output interface 116. The printer 200 then operates the scanner unit 212 to acquire an image, saves the resulting image to the ROM 112 via the input / output interface 116, and notifies the portal application of the save location. The portal application displays the selected printer at 410 in Figure 4. In the example in Figure 4, printer A is selected. The portal application also maintains a list of selectable printers and switches the currently selected printer from the list when button 411 or button 412 in Figure 4 is pressed. The buttons for performing each function shown in Figure 4 may be called "icons" or "applications."

[0018] The list of selectable printers maintained by the portal application is created, for example, by obtaining a list of print queues managed by the OS and extracting only those printers whose printer driver names contain a specific string. This allows the portal application to create a list in which only printers manufactured by the developer's vendor are selectable. Furthermore, the portal application also has the function of launching other applications installed on the terminal device 100 (hereinafter referred to as linked applications or linked apps).

[0019] Figure 5 shows an example of a list screen (second screen) of linked applications that can be launched by the portal application. The linked application list screen 500 is displayed when the linked application list button 404 displayed on the top screen 400 is pressed. Note that the linked application list screen 500 may be displayed when any designated button is pressed, not just the linked application list button 404. Also, if the back button 501 is pressed while the linked application list screen 500 is displayed, the top screen 400 is displayed. When the launch button 502 for application 1 (App1) is pressed on the linked application list screen 500, the portal application reads the executable file for application 1 from ROM 112 and launches it. Similarly to buttons 502, the portal application reads the corresponding application executable file from ROM 112 and launches it when the button is pressed for buttons 503 to 509. The portal application also has a function to customize the function buttons displayed on the top screen.

[0020] Figure 6 shows the customization screen of the portal application. The customization screen 600 is displayed when the customization button 405 displayed on the top screen 400 is pressed, and allows the user to arbitrarily change whether or not the buttons displayed on the top screen 400 are shown, or their display position. The user can change the display position of the buttons by dragging and dropping the buttons 601 to 604 for each function shown in Figure 6.

[0021] Figure 7 shows the customization screen of the portal application. Specifically, Figure 7 shows the display positions of each button when the scan button 603 shown in Figure 6 is dragged and dropped to the left of the photo print button 601.

[0022] Figure 8 shows the customization screen 600. Specifically, Figure 8 shows the customization screen that appears when the delete button 610 is pressed by the user on the customization screen 600 in Figure 6. It can be seen that the scan button 603 is hidden when the delete button 610 is pressed.

[0023] Figure 9 shows the portal application selection dialog. Specifically, the selection dialog 900 shown in Figure 9 is displayed when the Add Function button 611 shown in Figure 6 is detected. When the portal application detects that the OK button 901 is pressed while the checkbox shown in Figure 9 is checked, it displays the launch button for the target application on the customization screen 600. For example, if the checkbox shown in 903 in Figure 9 is checked and button 901 is pressed, the portal application adds and displays the launch button for Application 2 (App2) as shown in Figure 10. Also, if 902 is pressed and the linked application selection dialog is closed, the portal application does not change the launch button of the application displayed on the customization screen. Then, when the OK button 612 on the customization screen 600 is pressed, the portal application confirms the function buttons to be displayed on the top screen 400, closes the customization screen 600, and displays the top screen 400 with the customization results reflected. Note that applications belonging to the "Function" group in Figure 9 are called the first type of application, and applications belonging to "Linked Application" are called the second type of application. Specifically, the first type of application is an application that performs standard functions on the printer 200 and is installed along with the portal application. The second type of application is an application that is installed externally after the portal application has been installed. Therefore, the top screen 400 is a screen where both the first and second type of applications can be placed, and the linked application list screen 500 is a screen where the second type of application can be placed. Furthermore, since the first type of application cannot be placed on the linked application list screen 500, it can also be said that the linked application list screen 500 is a screen where the first type of application cannot be placed.In this embodiment, we will explain using two different types of applications (the first type and the second type of application) as examples, but this embodiment can be broadly applied to two applications of the same type (the first and second applications). For example, even if they are both printing-related applications, this embodiment can be applied to two different applications.

[0024] (Update control processing for linked applications) Figure 11 is a flowchart showing the update control process for a linked application. The processes in this flowchart are performed by the portal application when the update process for the target linked application is executed. In this embodiment, these processes are performed at timings S1402 and S1405 in the flowchart of the linked application update sequence control process shown in Figure 14, which will be described later. The series of processes shown in this flowchart are performed by the CPU 111 of the terminal device 100 loading the program code stored in the ROM 112 into the RAM 113 and executing it. In the following descriptions of each process, "S" means a step in the flowchart, and the same applies to subsequent embodiments.

[0025] In S1101, the CPU 111 of the terminal device 100 communicates with the application distribution server 300 and obtains the version of the distributed application.

[0026] Figure 12 shows the application version information managed by the application distribution server 300. The application distribution server 300 manages the application versions distributed for each application in a table like the one shown in Figure 12. The portal application obtains the application version 1202 and download link 1203, which are associated with the application name 1201.

[0027] In S1102, the CPU 111 compares the application version installed on the terminal device 100 with the application version obtained from the application distribution server in S1101, and determines whether the application version obtained in S1101 is newer. In other words, the CPU 111 checks whether there is an updated version of the application on the server. The application version installed on the terminal device 100 is obtained from information stored in a non-volatile area such as the registry when the application is installed. If the CPU 111 determines that the application version obtained from the application distribution server is newer (an updated version is available), it proceeds to S1103. If it determines that this is not the case (no updated version is available), the CPU 111 terminates the processing of this flowchart. In S1103, the CPU 111 displays the update confirmation dialog 1300.

[0028] Figure 13 shows the update confirmation dialog 1300 in this embodiment. Further, in S1104, the CPU 111 determines whether the "Yes" button 1301 was pressed in the update confirmation dialog 1300. If it determines that the "Yes" button 1301 was pressed, the CPU 111 proceeds to S1105. If it determines that the "No" button 1302 was pressed, the CPU 111 terminates the processing of this flowchart without performing the update control process.

[0029] In S1105, CPU 111 deletes the old version of the application installed on terminal device 100. Then, in S1106, CPU 111 downloads and installs the latest version of the application from the server. At this time, the user has to wait until the uninstallation of the old version of the application and the installation of the new version are complete, which is undesirable from a usability standpoint. Alternatively, a check box could be added to the update confirmation dialog 1300, and if the "Yes" button 1301 is pressed after the check box is checked, CPU 111 could be controlled so that the update confirmation dialog 1300 is not displayed thereafter. Alternatively, if the update control process for the linked application is executed again, the process in S1103 could be skipped and the update could be performed immediately. This would eliminate the need for the user to check the update confirmation dialog 1300 every time there is an update for the linked application. The setting for whether or not to display the update confirmation dialog 1300 could be toggled on a separate screen in the portal application.

[0030] (Processing to control the update order of linked applications) Figure 14 is a flowchart for performing update order control processing for the linked application in this embodiment. The series of processes shown in this flowchart are performed by the CPU 111 of the terminal device 100 loading the program code stored in ROM 112 into RAM 113 and executing it. Furthermore, the update order control processing shown in Figure 14 is a process that starts by being executed in the background when the portal application is launched.

[0031] In S1401, the CPU 111 determines whether a linked application is placed on the top screen 400. If it is determined that it is placed, the CPU 111 proceeds to S1402; otherwise, it proceeds to S1404. In S1402, the CPU 111 executes the update process for the linked application. This is the process explained in Figure 11. In S1403, the CPU 111 determines whether all update control processes have been completed for the linked applications placed on the top screen 400. If it is determined that all update processes have been completed, the CPU 111 proceeds to S1404; otherwise, it continues the update control process in S1402.

[0032] In S1404, CPU 111 determines whether there are any applications that are only located on the linked application list screen 500. If it determines that such applications exist, CPU 111 proceeds to S1405; if it determines that such applications do not exist, it terminates the processing of this flowchart.

[0033] In S1405, the CPU 111 executes the update control process shown in Figure 11 for applications that are located only on the linked application list screen 500. In S1406, the CPU 111 determines whether all update control processes for applications located only on the linked application list screen 500 have been completed. If it determines that all update control processes have not been completed, the CPU 111 returns to S1403.

[0034] The above is a flowchart of the update order control process. Since users can freely change the launch buttons for linked applications placed on the top screen, it is conceivable that launch buttons for frequently used linked applications may also be placed on top screen 400. Therefore, by executing the update order control process shown in Figure 14, the portal application can prioritize the execution of update control processes for linked applications that are frequently used by the user. Furthermore, by executing the update order control process when the portal application is launched, the completion of the update control process can be accelerated.

[0035] As described above, this embodiment can improve the usability of the portal application. Specifically, by prioritizing updates for applications that users are likely to use frequently, the possibility of users having to wait can be reduced. This can be achieved by prioritizing the update control process for applications located on the top screen.

[0036] <Embodiment 2> In Embodiment 1, the portal application performed update order control processing upon startup, automatically executing update control processing before the user could use the linked application. However, for linked applications that are not frequently used by the user, update control processing may be unnecessary. For example, it is possible that the application may be updated multiple times while the user is not using it. In that case, although it would be sufficient to update to the latest version just before the user uses it, the update control processing would be performed every time there is an update, potentially resulting in wasted effort. This embodiment aims to control the execution of unnecessary update processing for applications that are not frequently used by the user.

[0037] In this embodiment, the portal application controls the system so that it does not pre-execute the update control process for applications that are placed only on the linked application list screen 500, which are considered to be used infrequently by users. To this end, the portal application starts the application update process in the background when it is launched. In the update order control process shown in Figure 14, when the update control process for all linked applications placed on the top screen is completed (determined as YES in S1403), the process is terminated. Then, for applications placed only on the linked application list screen 500, the system controls the system so that only the update control process shown in Figure 11 is executed after their respective launch buttons are pressed.

[0038] The above process makes it possible to control the execution of unnecessary update control processes for applications that are not frequently used by users. An application that is not frequently used may be, for example, an application that is used relatively less frequently than other applications, or an application that has been used less than a threshold number of times over a certain period. Furthermore, within the same portal application, the user may be able to switch between the update process described in Embodiment 1 and the update control process described in Embodiment 2. That is, the user can select which embodiment to use for the update control process using an unillustrated switch provided on the portal application screen. For example, even for an application that is not frequently used and whose launch button is only located on the linked application list screen, if the user wants to perform the update control process in advance, they can select to use the switch to perform the update control process using the configuration of Embodiment 1.

[0039] <Embodiment 3> Embodiments 1 and 2 described a method for controlling the priority of update control processing for each screen. However, they did not mention the priority order in which to update which application placed within each screen. On the other hand, it is desirable to execute update control processing in an order of priority according to the user's frequency of use, even among applications placed within the same screen. This embodiment describes a method for controlling the update order among applications placed within the same screen.

[0040] Figure 15 shows information about linked applications launched by users in the portal application. The table shown in Figure 15 is assumed to be stored in ROM 112. Item 1501 represents the application name of each linked application. Item 1502 represents the number of times each linked application has been launched. In the example in Figure 15, App1 has been launched 15 times and App2 has been launched 5 times. Item 1503 indicates whether the launch button for the application is located on the top screen. In the example in Figure 15, App1 and App4 have launch buttons located on the top screen, while the other apps only have launch buttons located on the linked app list screen. Item 1504 represents the priority of the update control process based on the number of launches and whether or not a launch button is located on the top screen. Here, as the priority for the update control process, apps with launch buttons located on the top screen are assumed to be frequently used and will be given priority in the update control process. Also, since apps with a high number of launches are also assumed to be frequently used, among App1 and App4, which both have launch buttons located on the top screen, App1, which has a higher number of launches, is given priority of 1. App4 is then assigned a priority of 2. Furthermore, among the applications that do not have a launch button on the top screen, App3, which has the most launches, is assigned a priority of 3. Similarly, among App2 and App5, which do not have a launch button on the top screen, App2 is assigned a priority of 4 and App5 is assigned a priority of 5, in order of the number of launches. Note that Figure 15 only shows information about App1 to App5, and omits information about other linked applications, but in reality, information is stored for all linked applications placed on the linked application list screen 500. The portal application executes the update control process shown in Figure 14 in the background when the application is launched, according to the aforementioned priority order, thereby enabling control of the update order according to the user's usage frequency even for applications on the same screen.

[0041] Through the above process, it becomes possible to control the update order between applications placed on the same screen, prioritizing them according to the user's frequency of use.

[0042] <Other Embodiments> The configuration for assigning priority to the update control process described in Embodiment 3 is not limited to the above. For example, there may be a configuration that refers to the usage history and performs the update control process in order of the newest history. In this configuration, the update control process of the application that the user has been using most frequently recently can be prioritized. Conversely, it can also be used to refer to the usage history in order of deepest (less used) and control the system so that the update control process of Embodiment 2 is not performed.

[0043] The embodiments 1, 2, and 3 described above may be combined as appropriate. For example, in embodiment 2, the update order between linked applications placed on the top screen may be executed according to the priority order described in embodiment 3, and updates to applications placed only on the linked application list screen may be executed after the launch button is pressed.

[0044] This disclosure can also be implemented by supplying a program that implements one or more of the functions of the above-described embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be implemented by a circuit (e.g., an ASIC) that implements one or more functions.

[0045] Furthermore, this disclosure includes the following components. (Composition 1) A portal application program for launching at least one application that runs on an information processing device, wherein the information processing device A display control means capable of switching between displaying a first screen on which a first application and a second application can be placed, and a second screen on which the second application can be placed. Update control means that prioritizes the update process of the second application located on the first screen over the update process of the second application located only on the second screen, A program characterized by being designed to function as such. (Configuration 2) The first application described above is an application that performs standard functions in a particular device, The program according to configuration 1, characterized in that the second application is an application that does not perform standard functions in a particular device. (Composition 3) The aforementioned first application is an application that is installed along with the portal application, The program according to configuration 1, characterized in that the second application is an application that is installed externally after the portal application has been installed. (Composition 4) The program according to Configuration 1, characterized in that the update control means checks with an external party that distributes the application whether an updated version of the application is available, and controls the application to start an update process in the background if an updated version is confirmed to be available. (Composition 5) The update control means is the program according to configuration 4, characterized in that it checks whether an updated version exists when the portal application is started. (Composition 6) The program according to configuration 1, characterized in that the update control means controls the program to execute the update process of the second application placed on the second screen after the update process of the second application placed on the first screen has been completed. (Composition 7) The program according to configuration 6, characterized in that the update control means controls the execution of update processing for each of the first screen or the second screen in order of the frequency of use of the second applications arranged therein. (Composition 8) The program according to configuration 6, characterized in that the update control means controls the execution of update processing for each of the first screen or the second screen in order of the usage history of the second application placed therein. (Composition 9) The update control means controls the program according to Configuration 1, wherein, for applications among the second applications arranged on the second screen that are used less frequently than other applications, the update process is not executed until the launch button for the less frequently used application is pressed. (Composition 10) The program according to configuration 1, characterized in that the information processing device further functions as a receiving means for receiving operations to place any second application, which is to be placed on the second screen, on the first screen. (Composition 11) The program according to any one of configurations 1 to 10, characterized in that the first screen is a screen displayed when the portal application is launched. (Composition 12) The program according to any one of configurations 1 to 11, characterized in that the display control means displays the second screen by detecting the pressing of a predetermined button located on the first screen. (Composition 13) The program according to configuration 2, characterized in that the aforementioned specific device is an image processing device. (Composition 14) A display control means capable of switching between displaying a first screen on which a first application and a second application can be placed, and a second screen on which the second application can be placed. Update control means that prioritizes the update process of the second application located on the first screen over the update process of the second application located only on the second screen, An information processing device characterized by comprising: (Composition 15) A display control step that enables switching between displaying a first screen on which a first application and a second application can be placed, and a second screen on which the second application can be placed. An update control step which prioritizes the update process of the second application located on the first screen over the update process of the second application located only on the second screen, A control method for an information processing device, characterized by comprising the following:

Claims

1. A portal application program for launching at least one application that runs on an information processing device, wherein the information processing device A display control means capable of switching between displaying a first screen on which a first application and a second application can be placed, and a second screen on which the second application can be placed. Update control means that prioritizes the update process of the second application located on the first screen over the update process of the second application located only on the second screen, A program characterized by being designed to function as such.

2. The first application described above is an application that performs standard functions in a particular device, The program according to claim 1, characterized in that the second application is an application that does not perform standard functions in a particular device.

3. The first application is an application that is installed along with the portal application when it is installed. The program according to claim 1, characterized in that the second application is an application that is installed externally after the portal application has been installed.

4. The program according to claim 1, characterized in that the update control means checks with an external party that distributes the application whether an updated version of the application is available, and controls the application to start an update process in the background if an updated version is confirmed to be available.

5. The program according to claim 4, characterized in that the update control means checks whether an updated version exists when the portal application is started.

6. The program according to claim 1, characterized in that the update control means controls the program to execute the update process of the second application placed on the second screen after the update process of the second application placed on the first screen has been completed.

7. The program according to claim 6, characterized in that the update control means controls the execution of update processing for each of the first screen or the second screen in order of the frequency of use of the second applications arranged therein.

8. The program according to claim 6, characterized in that the update control means controls the execution of update processing for each of the first screen or the second screen in order of the usage history of the second application arranged therein.

9. The update control means controls the program according to claim 1, wherein, with respect to the second application placed on the second screen, the application that is used less frequently than other applications, the update process is not executed until the launch button for the less frequently used application is pressed.

10. The program according to claim 1, characterized in that the information processing device further functions as a receiving means for receiving operations to place any second application, which is to be placed on the second screen, on the first screen.

11. The program according to claim 1, characterized in that the first screen is a screen displayed when the portal application is launched.

12. The program according to claim 1, characterized in that the display control means displays the second screen by detecting the pressing of a predetermined button located on the first screen.

13. The program according to claim 2, characterized in that the aforementioned specific device is an image processing device.

14. A display control means capable of switching between displaying a first screen on which a first application and a second application can be placed, and a second screen on which the second application can be placed. Update control means that prioritizes the update process of the second application located on the first screen over the update process of the second application located only on the second screen, An information processing device characterized by comprising:

15. A display control step that enables switching between displaying a first screen on which a first application and a second application can be placed, and a second screen on which the second application can be placed. An update control step which prioritizes the update process of the second application located on the first screen over the update process of the second application located only on the second screen, A control method for an information processing device, characterized by comprising the following:

Images