AU2017200210A1

AU2017200210A1 - Method of and device for managing applications

Info

Publication number: AU2017200210A1
Application number: AU2017200210A
Authority: AU
Inventors: Jae-Young Lee; Jang-Woo Lee; Yong-Gook Park; Jong-Hyun Ryu
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2013-01-31
Filing date: 2017-01-12
Publication date: 2017-02-02
Anticipated expiration: 2034-01-22
Also published as: AU2014213204B2; AU2014213204A1; AU2017200210B2; AU2014213204C1; KR102101876B1; RU2015136859A; IN2014MU00229A; RU2622873C2; KR20140099166A

Abstract

Abstract Provided are a method of and device for managing applications installed on the device. The device includes: a user 0 interface configured to display the plurality of applications; and a controller configured to monitor use history of each of the plurality of applications, and control the user interface to change a visual representation of at least one application from among the plurality of applications based on the monitored use history.

Description

Title of Invention: METHOD OF AND DEVICE FOR MANAGING APPLICATIONS

The present application is a divisional application from Australian Patent Application No. 2014213204, the entire disclosure of which is incorporated herein by reference.

Technical Field

Methods, and apparatuses consistent with exemplary embodiments relate to managing applications.

Background Art

Mobile (portable) devices, such as smart phones, tablet devices, and personal digital assistants (PDAs), are in wide use worldwide. Like in the case of other devices, such as personal computers (PCs) and laptops, the users may directly install various types of applications on the mobile devices. Accordingly, the users may be able to perform various operations, for example, they may watch content, such as a moving images or a picture, manage a personal schedule, write an email, play a game, etc. However, because the storage capacity of these devices is limited, the number of applications that can be installed is limited as well. Also, if many applications are installed, it may be difficult to find and delete select applications one by one. Thus, a method of efficiently managing applications in a mobile device may be implemented.

Disclosure of Invention Technical Problem

One or more exemplary embodiments provide a method of and device for of managing applications and a device for managing applications. Also, one or more exemplary embodiments provide a computer-readable recording medium having recorded thereon the method.

Solution to Problem

According to a first aspect, the present invention provides a device having a plurality of applications installed thereon, the device comprising: a display configured to display a plurality of icons corresponding to the plurality of applications; and a controller configured to monitor use history of each of the plurality of applications, determine an application from among the applications whose monitored use history satisfies a first level or a second level based on the monitored use history of the each of the plurality of applications, and control the processor to perform a first operation corresponding to the first level or a second operation corresponding to the second level on the determined application, wherein the first operation comprises terminating an automatic update of the determined application, and the second operation comprises providing a user interface inquiring about whether to completely delete the determined application from the device.

The controller may be further configured to change the visual representation of the at least one application displayed by the user interface by overlapping a layer of an object representing the at least one application with a layer of another object.

The controller may be further configured to change the visual representation of the at least one application displayed by the user interface by changing an object representing the at least one application.

The controller may be further configured to control the user interface to change the visual representation to identify a management state of the at least one application from among the plurality of applications.

The controller may include a determiner configured to determine at least one application, from among the plurality of applications, whose monitored use history satisfies a pre-set display change condition, and an uninstaller configured to change the visual representation of the determined at least one application.

The pre-set display change condition may include detailed conditions of a plurality of levels that are classified based on a degree of not using an application, and the controller may be further configured to control the user interface to change the visual representation of the determined at least one application by determining a detailed condition of a level, from among the detailed conditions of the plurality of levels, is satisfied by the monitored use history.

The controller may be further configured to control the user interface to change the determined at least one application to different types of visual representations according to the plurality of levels.

The controller may be configured to determine the at least one application by applying different types of display change conditions according to attributes of the plurality of applications.

The attributes of the plurality of applications may be classified according to at least one of capacities of the plurality of applications, update frequencies of the plurality of applications, memory resource capacities occupied by the plurality of applications, and types of the plurality of applications.

The controller may be further configured to control the user interface to change the visual representation of the at least one application by displaying a predetermined symbol overlapped on an object representing the at least one application.

The user interface may be configured to change the visual representation of the at least one application by displaying an additional layer showing a predetermined visual effect and overlapped on an object representing the at least one application.

The additional layer may include at least one of a layer for differently showing a color, a brightness, a chroma of the object, a luma of the object, a layer for showing the object as dark, a layer for showing the object as foggy, a layer for showing the object in a grayscale, a layer for showing dotted lines on a boundary of the object, a layer for showing the object as visually concave, a layer for showing the object as visually convex, and a layer for showing the object as shabby.

The controller may be further configured to determine, based on the monitored use history, at least one of an application that has not been used for a predetermined threshold time, an application that is not used repeatedly a threshold number of times until a predetermined point of time, an application that is not used when a location of the device is outside a range of a predetermined place, and an application that has not been commonly used with another device for a threshold time, and change the visual representation of the determined at least one application.

The controller may further include an uninstaller configured to delete user data that is stored in the device while the at least one application is used, and backing up the stored user data in a server, with respect to the at least one application.

According to a second aspect, the present invention provides a method of managing a plurality of applications installed on a device, the method comprising: displaying a plurality of icons corresponding to the plurality of applications through a display; monitoring a use history of each of the applications; determining an application from among the applications whose monitored use history satisfies a first level or a second level based on the monitored use history of the each of the plurality of applications; and performing a first operation corresponding to the first level or a second operation corresponding to the second level on the determined application, wherein the first operation comprises terminating an automatic update of the determined application, and the second operation comprises providing a user interface inquiring about whether to completely delete the determined application from the device.

The controlling the user interface may include controlling the user interface such that a layer of an object representing the at least one application is displayed as overlapping below a layer of another object, or such that the object representing the at least one application itself is changed.

The controlling the user interface may include determining an application from the plurality of applications whose monitored use history satisfies a pre-set display change condition, and changing the visual representation of the determined application.

The pre-set display change condition may include detailed conditions of a plurality of levels that are classified based on a degree of not using an application, and the controlling the user interface includes changing the visual representation of the determined at least one application by determining whether the monitored use history satisfies a detailed condition of which level from among the detailed conditions.

The controlling the user interface may include changing the determined at least one application to different types of visual representations according to the plurality of levels.

The controlling the user interface may include changing the visual representation of the at least one application by displaying at least one of a predetermined symbol and an additional layer for showing a predetermined visual effect, the additional layer being overlapped on an object representing the at least one application.

Advantageous Effects of Invention

As described above, according to the one or more of the above exemplary embodiments, applications installed on a device, such as a smart phone or a mobile phone, are managed such that a display state of an application that is seldom used or not used at all by a user is changed in stages or data and information related to such an ap- plication is deleted in stages, thereby efficiently managing a limited storage capacity of the device or enabling the user to easily manage the applications.

Brief Description of Drawings

The above and/or other aspects will beebme apparent and more readily appreciated from the following description of the exemplary embodiments, taken in conjunction with the accompanying drawings in which; FIGS, 1A and. I B are diagrams showing use patterns of a user using applications installed on a device, according to an exemplary embodiment; FIG. 2 is a block, diagram of a device for managing applications, according to an exemplary embodimeri t; FIG, 3 is a table showing a result of a monitor monitoring use histories of applications installed on a device, according to an exemplary embodiment; FIG, d is a diagram for describing uninstalling of an application according to a location of a device* according to an exemplary embodiment; FIG. 5 is a table for describing uninstall operations performed at each uninstall level, according.'!© ah exemplary embodiment; FIG. 6 A illustrates a user interface (UI) screen displaying applications in stalled on a device, according to an exemplary embodiment; PIG, 6B illustrates- a UI screen where an uninstall operation is applied to applications installed oh a de vice, according to an exemplary embodiment; FIG, 6C iilnstrates a UI semen where an uninstall operation is applied to applications installed on a device, according to another exemplary embodiment; FIG. SO illustrates a DF screen where an uninstall operation is applied to applieatipm installed on a device, according to another exemplary embodiment; FIG. 6E illustrates a UI screen where an uninstall operation is applied to applications installed on a device, according to another exemplary embodiment; FIG, 6F illustrates a UI screen where an uninstall operation is applied to applications installed on a device, according to another exemplary embodiment; FIG, 7A is a diagram for describing a first uninstall operation preformed at a first uninstall level, according to an exemplary embodiment; FIG. 7B is a diagram for describing a second uninstall operation -preformed at a second uninstall level, according to an exemplary embodiment; FIG. 7C is a diagram for describing a third uninstall operation preformed at a third uninstall level, according to an exemplary embodiment; FIG, S is a detailed block diagram of a device for managing applications, according to an exemplary embodiment; FIG. 9 is a flowchart illustrating a method of managing applications installed on a device, according to an exemplary embodiment: FIG. 10 is a flowchart illustrating a method of managing applications installed on a device, according to another exemplary embodiment; FIG, 11 is a flowchart illustrating a method of managing applications installed on a device, according to another exemplary embodiment; and FIG. 12 is a flowchart illustrating a method of managing applications installed on a device, according to another exemplar)·' embodiment.

Best Mode for Carrying out the Invention According to an aspect of an exemplary embodiment,there is provided a device having a plurality of applications installed theieon, the device mcluding a user interface configured to display the plurality of applications,-and a controller configumd to monitor use history of each of the plurality of applications, and control the user interlace to change a visual representation of atleast one application from among the plurality of:applications based oil. the monitored use history.

According to an aspect of another exemplaiy embodiment, there Is provided a method of managing a plurality of applications installed on a device, the method including displaying the plurality of applications through auser interface, monitoring a use history of each of the plurality of applications, and controllingsthe user interface to change a visual representation of at least one application based on the monitored use history.

Mode for the Invention

Reference will now he made in detail,:ippmb0^:fiiients,,examples of which are il· lustrated in the accompanying drawings, wherein like reference numerals refer to like element:; throughout, In this regard, the present embodiments may have different forms and should not be construed as being limited to the descriptions set forth herein.

Particular exemplary embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present exemplary embodiments to particular modes of practice, and it will to be appreciated that: ail changes, equivalents, and substitutes that: do not depart from the spirit and technical scope are encompassed. In the description, certain detailed explanations of related art are omitted when it is deemed that they may unnecessarily obscure the essence of the one or more exemplary embodiments.

As used herein, the term “and/or” includes any and ail .combinations of one or more of the associated listed items. Expressions such as“at least one of,’’ when preceding a iist of elements, modify the entire list of Clements and do not modify the individual elements of the list.

While such terms as “first,” “second,” etc., may be used to describe various components, such components must Pot be limited by the above terns. The above terms are used only to distinguish one component from another.

All terms including descriptive or technical terms which ace used herein should be copstrned as having meanings foal mo known to one of ordinary skill in the ait. However, the terras may have different meanings according to an intention of one of ordinary skill in the art, precedent cases, or the appearance of new technologies. Also, some terras may he arbitrarily selected by the applicant, aud io this case, the meaning of the selected terras will be described in detail in the detailed description. Thus, the terras used herein have to be defined based on the meaning of the terras together with the description thrOughont the specification.

Also, when a part ‘‘includes” or “comprises” an element, unless there is a pmticulaf description contrary thereto, the part, can further include other '.elements, not excluding the: other elements. In the following description, terms such.as “unit” and “module” indicate a unit for processing at least one function or operation, wherein the unit and the block may be embodied as hardware or soft warn or embodied by combining hardware and software, A “device” mentioned th roughout one or more exemplary embodimentsmay be a smart phone, a mobile phone, a personal digital assistant (PDA ), a laptop, a media player, a global positioning system (GPS), or another mobile or non-mobile computing device, but is not limited thereto. It will be readily understood by one of ordinary skill In the art that the device may alternatively be any one of various devices capable of receiving a touch input, such as an elecuonie biaekboard or a touch table.

Information Jhputtuble to a device according to one or more exemplary embodiments includes user input information, and for example, may be touch-based user input information. The touch-based user input information may be a request o f the user, a selection of the user , such as selection of one piece of application-rel ated information being displayed, or a command of the user, such as a delete command based on application-related information being displayed, but is not; limited thereto, A touch-based input may be dependent on a touch-based gesture of a user. Examples of the touch-based gesture include tap (or touch), long tap (or long touchy touch and hold, touch and drag, double tap, drag, panning, ilick, drag and drop, and sweep, but are not limited thereto.

An input is not limited to the touch-based gesture. For example, the input may be motion-based or vision-based. A motion-based hmtd may be based on a gesture of a user based on moving a device, for example, shaking or hitting the device. For example, a gesture of tilting the device to a location where a virtual space that will be described later is displayed or of hitting the device twice may be set as an input for requesting to register selected application-related information in the virtual space. A vision-based input may be based on a gesture of a user recognized by analyzing an inputimage obtained by using a camera, without having to contact a device. For example, a space gesture of making a V sign by using an index finger and a middle finger tnay be set as an input tor requesting to delete application-related itdbmtaiion in a virtual space that will be described later,

One or more exemplary embodiments will now be deseribed. in detail with reference to accompanying drawings. FIGS, J Λ and I B are diagrams showing use patterns of a user using applications 20 installed on a device ! 0, according to an exemplary embodiment.

Referring to FIG. 1A, use patterns of the user on a date 11 dated J anuary 15, a date 12 dated March 17th, and a date 13 dated June 23rd are described, but. these dates are only examples and am not limited thereto. Also, user interfaces (Uls) shown in FIG, 1B are in slightly different tile; Shapes from Uls in FIG, 1. A, and thus descriptions on. FIG, 1A may also apply to BIG, I B, In other words, various Uls of the device 10 may exist other than those shown in FIG, i A, and one or more exemplary embodiments may include various Uls.

Various types of the applications 20 may be pre-installed on the device 10 or are installed by the user. Also, a list of the applications 20 may be displayed on the Uf of the device 10.

In one or more exemplary embodiments, the applications 20 denote a series of computer program (software) groups designed to perform certain operations. A.O eordingly, since one ofofoinary skill in foe art will readily understand that examples of foe applications 20 described herein include a game application, a utility application, a musical instrument playing application, a moving image reproducing application, a map apldieaiion, a broadcast application, an exercise supporting application, a payment application etc,, details thereof will be omitted herein.

Referring to FIG. 1 A, based on the use pattern on the date 11 dated January fifteenth, it may be assumed that a first application 21 from among the applications 20 installed on the device 10 is frequently used.

However, based on foe use pattern on the date 12 dated March ITth ihat is two months after foe date 11 dated January 15th, it is assumed that a first application 22 is seldom used compared to the first application 21.

Moreover, based on foe use pattern on the date 13 dated June 23rd that is three month after foe date 12 dated March 17th, it is assumed that a first application 23 Is not used at all.

As such, an application from among the applications 20 installed on the device 10 may be initially frequently used but gradually used less and less as the users Interest $as£fes away, like the first application 21.

General devices, such as smart phones and mobile phones, only manage installation of applications, and do not. separately manage how the applications are used or which applications are ciniently not used dr seldom used.

In detail, according to an increase in types of applications directly installable on devices, such as smart phones and mobile phones, it may be difficult for the user to manage the applications simultaneously, Also, because storage capacities of the devices are limited, if many applications are installed, the storage capacities may not be sufficient to additionally store oilier information. Moreover, if the user wants to delete applications that are no longer used or unnecessary, it may be inconvenient for the user to delete the applications one by one.

According to the current embodiment, the device 10 may have a function of monitoring and separately managing the first application 21 that is seldom used or not used, unlike other applications 20. In detail, according to the eurmhf nxemplm^ embodiment, the device 10 has a function of performing operatlortsJsr managing the first' application 21 in stages, for example, uninstall operations.

For example, as described above, the first application 21 is frequently used on the date 11 dated January 15th, but the first '.application 22 is seldom, used on the date 1:2 dated March 17th that is two months after the date 11 dated January 15th,

The device 10 monitors a use history of the user on the first application 21 or 22 between the date 11 dated January 15th and the date 12 dated March 17th. if it. is monitored that the first application 22 is not frequently used on the date 12 dated March 17th, the device 10 performs an. uninstall operation corresponding to a eeftain uninstall level on the first application 22. and displays identification information indicating that the first application 22 is at the certain uninstall level.

Here, in order to indicate that the first application 22 is at the certain uninstall level on the date 11 dated March 17th, the device 10 may insert and display a padlock symbol on an. icon of the first application 22. Accordingly, the user may immediately recognise that the first application 22 is not frequently used.

Then, the device IQ monitors the use pattern of the user on the first application 22 or 23 between the date 12 dated March 1.7th and the date 13 dated June 23rd. If It is monitored that the first application 23 is no longer used on the date 13 dated June 23rd, the device 1.0 may perform an uninstall operation corresponding to another uninstall level higher than the certain uninstall level on the date 12 dated March 17th on die first application 23. For example, the device 10 may perform an uninstall operation of completely deleting all data related to the first application 23 on the date 13 dated June 23rd.

Generally, the term Aminstall” Includes only a process of completely deleting an ap- plication, Itowever, in one or more exemplary embodiments, the· t#iji:“unijni8t®ir includes uninstall operations in stages for changing an indication (visual representation) of an application or for deleting or erasing data of the application. In other words, the meaning of “uninstall” is not limited to a general meaning in one of more embodiments, as will be described in detail later.

Hereinafter, structures, functions, and .operations of the device 10for managing the applications 20 installed oh the device 100, will be described in detail, FIG. 2 is a block diagram of the device 10 for managing applications, according to an exemplary embodiment. Referring to FIG, 2, the device 1.0 may include a controller 110 and a user interface ( 03) 120.

For clarity, only hardware components related to the cuirent embodiment will be described in FIG. 2. Howe ver, it will be readily understood·by One of ordinary skill in the art that general-use hardware components other than those shown in FIG, 2 may also be included in the device HI

Referring to FIG. 2, the controller 110 may include a monitor 1 1 1, a determiner 112, and an uninstaller 113, In the device 10, the controller 110 may correspond to a processor, such as a central processing unit (CPU), The processor may be realized by using an array of a plurality of logic gates or may be a general-use microprocessor. In other words, the processor may be realized in any shape of hardware or software module.

The monitor 111 may monitor a use history of eaeh application installed on the device 10, The use history' may be defined as a concept including use patterns or use habits accumulated with respect to locations or rimes of using the application .

In detail, the monitor 1. ll may monitor how often the application has been used during a threshold time pre-set through the device, or how many times the application has not been used until a pre-set: point of time, in other words, the monitor 111 may monitor the use history by collecting information about a use habit and use frequency of each application.

As shown in FIG. 3., the monitor 111 may manage a monitoring result according to applications, lit other words, the monitor 111 may monitor different texts of applications, such as use frequencies, used locations, and people using (sharing) corresponding applications, according to types of applications. FIG. 3 is a table showing a result of the monitor 111 monitoring use histories of applications installed on the device 10, according to an exemplary embodiment.

Referring to FIG. 3, uninstall conditions for determining an uninstall level include a condition wherein an application is not used for a pre-set threshold time, a condition wherein an unused state of an application is repeated a threshold number of times or more until a pre-set point of time, a condition wherein a location of the device 10 is outside a pre-set range, and a condition wherein an application is not shared with another device fora threshold time. However, it will he readily understood by one of ordinary skill in the art that the uninstall conditions may include other similar' application is used by «se history.

The monitor 111 may monitor-that a use frequency of a first application is 0 times, a use frequency of a second application is 2 times, a use frequency of a thind application is 38 times, and a use frequency of a fourth application is 0 times during a threshold time pre-set in the device 10* Here, the pre-set threshold time may be directly set by the user by manipulating the device 10 or may be a default value assigned in an operating system (0$) of the device 10.

Also, the monitor 111 may monitor that an unused number of times of the first application is 4 times, an unused number of times of the second application is 1 time, mi unused number pf times of the thhd application Is 0 times, and an unused number of times ofthefomth application is 0 times at a certain point of time, pre-set in the device 10. Here, similarly, the pre-set certain point of time may be directly set by the user by manipulating the device 10, Or may correspond to a default value assigned by the OS of the device 10.

Also, the monitor 111 may monitor an average time of using each of the first through fourth applications.

Moreover, the monitor 111 may monitor a place the second application is mostly used, unlike the first, third, and fourth applications. In other words, the monitor 111 may monitor that the place the second application is mostly used is, lor example, Gangnam, Seoul Also, by contihuously momtoriug the place where the device 10 is currently located, the monitor 11 1 may monitor that the second application is seldom used or not used at all in areas other than Gangnam.

Also, the monitor 1 1 1 may monitor that the fourth application is an application used only when connected to another device in a wireless communication manner, such as Bluetooth or Wi-Fi direct, unlike the first, second, and third applications. Thus, the monitor 111 may monitor the use history of tbefotirth application by also monitoring a connection frequency to the other device via wireless communication.

Referring back to FIG, 2, the determiner 112 determines at least one application satisfying the pre-set uninstall conditions ifom among the applications installed in the device 10, based on the monitored usehistories as shown in FIG, 3.

In other words, the determiner 112 may determine at least one application corresponding to at least one uninstall leye!: from among a plurality of uninstall levels, based, on the monitored usehistories. Also, the determiner 112 may additionally -cfetermi«e":dn uninstall level corresponding to an application determined based on the monitored use histones.

The unin stall conditions may include detailed conditions in stages for classifying uninstall levels to he applied to applications based on a degree of not using the applications. In detail, when the uninstall conditions are satisfied, visual representations of the applications may also be changed, and thus, the uninstall conditions may also be referred to as display state change conditions,

According to the current exemplary embodiment, for convenience of description, the uninstall levels include three levels, Le., a first .uninstall level, a second uninstall level, and a third uninstall level. However, it will be readily understood by one of ordinary: skill in the art the uninstall levels tnay include two or more uninstall levels by sub-diyiding or combining uninstall operations included in the three uninstall levels described below.

One of the reasons that the uninstall conditions may be: subdivided to include detailed conditions in stages is to change an indication (or a visual representation) of an application in stages or to delete data until an unused application is finally completely deleted,

An exemplary embodiment when the uninstall Condition is a condition wherein an application is not used for a pre-set threshold time as described above will now he described. In this exemplary embodiment, it may be assumed that the pre-set threshold time is one month but is not limited thereto.

When it Is detemiined that the first application, for example, the first application 21 Of FIG. I A, is not used for one month that is thethreshold time based on the monitoring result of the monitor 111:, the determiner 11.2 may determine that the first application is at the first uninstall level, which is a lowest uninstall level, after one month.

After it is determined (hat the fir$ .application when it is determined that the first application is again not used for one month based on the monitoring result of the monitor .111, the determiner 112 may determine that the first application is at the second uninstall level that is a next uninstall level after another one month (total two months).

After it is determined that the first application is at the second uninstall level, and when it is determined that the first application is eontiniiously not used for one month based on the monitoring result of .fhe:monitcadll,t the determiner 112 tnay determine that the first application is at the third uninstall level that is a last uninstall level after another one month (total three months). As will be described above, in one or more embodiments, in the mird uninstall level, an uninstall opemtiOn of completely deleting the first application may he performed. As a result, the fimt application at the third uninstall level may be pennanently removed .from the device 10,

Alternatively,: an exemplary embodiment where the uninstall condition Is a condition wherein an unused state of an application is repeated a t hreshold number of times up to a pre-set point of time will now'be described. In this exemplary embodiment, U may be assumed that the pre-set point of time is after one week and the threshold number of times is 4. Meanwhile, the pre-set point of time may be arbitrarily set based on a use history of an application used by the user in the device 10, Alternatively, the pre-set point of time may be directly set by the user.

When it is detemilned that the first application, for example, the first application 21 of FIG. 1 A, is not used for four weeks based on the monitoring result of the monitor Π1, the first application is repeated 4 times that is the threshold number of times. As a result, the determiner 112 determines that the first application is at the first uninstall level that Is the lowest uninstall level, at the point of time after 4 weeks.

However, on the other hand, if 4 weeks are passed and the first application is used once only at the third week, the fofoshpld rinmbef of times Of 4 times is not satisfied, and thus the first application may not be in the first uninstall level.

After his determined that the first application is at foe first uninstall level, when it is determined foat the first application is again hot used for 4 weeks based on the monitoring result of the monitor 111, the determiner 112 may determine that the first application is at the second uninstall level that is a neat uninstall level at a point of time after another 4 weeks (total 8 weeks).

After it is determined foat the first application is at the second uninstall level, when it is determined that the first application is continuously not used for 4 weeks based on the monitoring result of the monitor 111, foe determiner 112 may determine that foe first application is at the third uninstall level that is a last uninstall level at a point of time after another 4 weeks (total 12 weeks).

Ih fhi s exemplary embodiment, even when the first application is at the first or second uninstall level, the first or second uninstall level may be canceled whenever the user starts to frequently use the first application again. However, if foe third uninstall level is applied and the first application is completely deleted, the user may have to install foe first application again on foe device 10.

An exemplary embodiment where foe uninstall condition is a condition wherein foe location of foe device 10 is outside the pre-set place will now be described with reference to FIG. 4, FIG, 4 is adiagram for describing uninstalling of an application according to foe location of the device 10, according to an exemplary embodiments

The monitor 111 may, for example, monitor foat a place where a bus application 401 is mostly used is Gangnam 404 in Seoul 405. For example, when it is assumed foal the bus application 401 is an application for showing bus routes and times within

Gangnam 404, the bus application 401. may not be used in Seoul 4G5 and a capital area 406 other than Gangnam 4G4,

Upon monitoring the location of the device 10 of FIG. 2, the monitor 111 may momibr that the device 1.0 is outside Gangnam 4G4 but still within Seoul 405 at a certain point of time. At thi s time, the determiner .112 may determine that a. bus application 402 is at the first uninstall level that is a lowest uninstall level

However, upon monitoring the location of the device 10, the monitor 111 may monitor that the device 10 is in the capital area 406 of Seoul 405. At this time, the determiner 112 may determine that a bus application 403 is at the second uninstall level that is a next uninstall level.

However, when the device 10 is again within Seoul 405 based oh the monitoring result of the monitor ill, the bus application 403 at the second uninstall level may be restored to the bus application 402 at the first uninstall level. Also, when the device 10 is again in Gangnam 404 based on the monitoring XI, the bus application 402 at the first uninstall level may be restored to the bus application 401 without any uninstall level.

Referring back to FIG. 2, an exemplary embodiment where the uninstall condition is a condition wherein an application is not shared with another device for a threshold time will now be described. Here, it may he assumed that the threshold time is one month.

For example, it may be assumed that the fourth application in FIG. 3 is a game application used only when the device 10 and another device me connected in a wireless eonmiuhicatioh manner, such as Bluetooth or WriFi direct. In other words, the fourth application cannot be executed by the device 10 only.

The monitor 11L may monitor the use history of the fourth application by monitoring the use: frequency of the fourth application and the connection frequency to the other device in a, wireless communication manner. As a result, the monitor 111 may monitor that the connection frequency is 0 times for one month of the threshold time. In this case, the determiner 112 may determine that the fourth application is at the first uninstall level.

After the fourth application is determined to be at the first uninstall level, when the monitor 111 monitors that the connection frequency of the fourth application to the other device is again 0 times for one month, the determiner 112 may determine that the fourth application is at the second uninstall level thatIs a next uninstall level at a point of time after another one month (total two months).

However, even when the fourth application is at the first or second uninstall level, the first or second uninstall level may be canceled at any time when the fourth application is frequently used by being connected to the other device in a wireless communication maimer.

As a result, when the uninstall condition is a condition wherein an application is not used for a pi»-set threshold time, the determiner 112 detennines at least one application that is not used for the pre-set threshold time based on monitoring results.

Alternatively , when the uninstall condition Is a condition wherein an unused state of an application is repeated a threshold number of times or more until a pre-setpoint of time, the determiner 112 determines at least one application whose unused State repeats at least the threshold number of times until the pre-set point of time based on monitoring results.

Alternatively, when the uninstall condition is a used location or a connection frequency to another device, the determiner 112 may deterniine an uninstall level of each application based on monitoring results. In other words, the uninstall level of each application may be deteimined by moni toring different contexts, such as use frequencies, used locations, and people using (sharing) corresponding applications, according to types of applications.

The uninstaller 113 may change an icon of a determined application to a display stale corresponding fojfo unmstaU the determined application. Here, the UI120 may display the icon having the display state oil a 1.11 screen.

At the same time, the uninstaller 113 performs an uninstall operation corresponding to the uninstall level of the determined application on the determined application.

First, uninstall operations performed on a determined application In uninstall levels will be described in detail. FIG, 5 is a fable for describing uninstall operations performed at each uninstall level, according to mi exemplary embodiment, Inferring to FIG. 5, uninstall operations performed at each of the .first uninstall level, the second uninstall level , and the third uninstall level are described. For convenience of description. It is assumed that an; application determined by the determiner 112 is the first application 21 of FIG, IA in FIG, 5.

When the first application is determined to be at foe first uninstall level, the uninstaller 113 performs a first uninstall operation corresponding to foe first uninstall level on the first application.

In detail, foe uninstaller 113 performs the first uninstall operation of ending functions of foe device 10 required to drive foe first application, Here, foe ended functions include a function of exchanging infoiiriation between the device 10 and a server (not shown) for providing a service of the first application through a network, a function of automatically updating foe first application, and a background process of foe first application.

In other words, the uninstaller 113 does not delete the first application Itself, but performs the first uninstall operation by slopping a network fcatfit© or.n#sv0ii;'.meiSS8ge generated by the first application, ending processes executed in a background of the device 10 for the first application, and ends an automatic update of the first application.

However, if the first application is used again by the user after the first uninstall operation is performed, the uninstaller 113 activates functions of the first application ended through the first uninstall operation.

When the first application is determined to be at the second uninstall level, the uninstaller i 13 performs a second uninstall operation corresponding to the second uninstall level on the fimt application.

In detail, the uninstaller 113 performs the second uninstall operation by deleting user data stored in the device 10 while using the first application, while maintaining only an icon of the first application displayed on the HI screen, and backing up the user data stored in the device 10 on a server.

Here, the user data includes basic setting information for driving the first application, login information of the first application, contents stored while using the first application history infonnation, and transaction information.

However, if the first application is used again by the user after the second uninstall operation is performed, the uninstaller 113 may restore (or roll back) the user data of the first application backed up in the server to the device 10.

When the first application is determined to be at the third uninstall level, the uninstaller Π3 performs a third uninstall operation corresponding to the third uninstall level on the first application.

In detail, the uninstaller 113 performs the third uninstall operation by deleting the icon of the first application and entire information about the first, application.

However, in the third uninstall operation, because the first application is completely deleted from the device 10, the device 10 may bepre-set such as to receive a user selection about whether to finally perform the Ibiindi, to completely delete the first application, through the HI 120. In this case, the uninstaller 1130 may perform the third uninstall operation only when the user requests to perform the third uninstall operation through the Ul 120.

It wi ll be readily understood by one of ordinary skill in the art that other operations for accomplishing purposes of the first through third uninstall operations performed in the first through third uninstall levels described herein are within the scope of one or more exemplary embodiments, even if not described.

Referring back to FIG, 2, as described above, the uninstaller 113 changes the icon of the first appUedtion to a display state epraespondhig to an uninstall level of the first application (determined application), and the Hi 120 displays the icon having the changed display state on foe HI screen.

When an uninstall operation crpespondmg to an uninstall level is performed on the first application, the 111 120 may insert mid display a predetermined symbol on a part of the icon of.'the. first application. Hem, the insetted symbol may have a padlock shape Or an exclamation mark, but is hot limited thereto.

Alternatively, when an uninstall operation corresponding to an uninstall level is performed on the first application, the U1120 may adjust and display at least one of a color, brightness, chroma, and luma of the lebn of the first application.

Alternatively, when an uninstall operation corresponding to an uninstall level is pieiformed on the .fet-a^iication, the til 120 may apply and display a predetennined visual effect to the icon of the first application.

Examples of the changed display state of the icon displayed through the III 120 include a state wherein a symbol is inserted into a part of the icon, a state wherein the icon is dark, a state wherein the icon is foggy, a state wherein the icon is in a grayscale, a state; wherein dotted lines are inserted to a boundary of the icon, a state wherein the icon is visually concave, a state wherein the icon is visually convex, and a state wherein the icon is shabby , but are not limited thereto. A changed display State of an icon to which an uninstall operation is applied (in an uninstall le vel ) is not limited as long as the icon Is distinguished from icons of other applications to which an uninstall operation is not applied (not in an uninstall level).

This Will he described in detail with reference to FIGS. 6Λ through hi·. In FIGS. 6A through 6F, UI screens viewed in front of the device 10 in a poin t of view of the user. Here, applications shown in FIGS, 6A through 6F may be results of changing displays of icons of the applications, orresults of overlapping layersof others object, on layers of the icons of the applications without changing the displays of the icons of the applications. Also, even when display stmes of the icons are changed as above, the user may perceive the same visual effects because (he user only sees the front of the device 10. FIG. 6A illustrates a HI screen displaying the applications 20 installed in the device 10, aecmriing to an exemplary embodiment. Referring to FIG. 6A, the applications 20, such as a bus application, a calendar application, a box application, a weather application, a phone application, and a note application, are installed in the device 10, and icons corresponding to objects representing the applications 20 may be displayed on the HI screen. The UI screen of FIG. 6A is only an example and is not limited thereto.

Meanwhile, the applications 20 may include applications that are basically installed along with the OS of the device 10, such as the calendar application, the phone application, and the note application, in other words, the basically installed applications are not directly installed by the user who is using the device 10, but may be installed via an imtiallb^oting of the device 10 so as to perform basic functions prOvMed by the device IQ, such as a phone call, a text, ami a memo. Accordingly, such basically 'mstaUed.ajpj}Hc.^dnS'inay not be managed according to one or more exemplary embodiments. In Other words, the controller 110 including the monitor 111, the determiner 112, and the uninstaller 113 may be set to operate'Whle:''mtOit^mg''dte:. basically installed applications. However, alternatively, operations and functions of the controller 110 may also be applied to the basically 'msttallod;to n setting of the user. FIG. 6:B illustrates a Ul screen where an uninstall operation is applied to the plications 20 instalied on the device 10, according to an exemplary embodiment. Referring to FIG, 6B, a bus application 611 is at the first uninstall level and a box application 612 at in the second uninstall level.

As described above, the determiner 112 may determine that the bus application 611 is at the first uninstall level based on a monitored use history of the bus application 611. Also, the determiner 112 may determine that the box application 612 is at the second uninstall level based on a monitored use history of the box application 612.

The uninstaller 113 changes a display s taie of an icon of the bus application 611 at the first uninstall level such that a padlock symbol Is inserted to die icon. Then, the Ul 120 displays the icon of the bus application 611 into which the, padlock symbol is inserted aihhi^hf tdp ihb-ϋϊ.Screen. Thus, the user may recognize that the bus application 611 is currently at the firstuninstall level and the first uninstall Operation is applied to the bus application 611.,

Meanwhile, the changing of the display stateifylpal.nepiklpn^ icon of the bus application 611 may be performed by inserting the padlock symbol to the icon of the bus application 611, Alternatively, the changing of the display state of the icon of the bus application 611 may be performed by additionally overlapping a layer of the padlock symbol that is another object on a layer of the Icon of the bus application 611. In other words, the current embodiment is not limited by any one of the above.

As described above, such methods are applied to change a display state (visual representation) of an application described here, and may be applied to change the display state such that an exclamation mark symbol is inserted to an icon (object) of the application, the icon is shown dark, the icon is shown blurry, a boundary of the icon is in dotted lines, or the icon is shown concave.

The uninstaller 113 may change the display state of the icon of the box application 612 at. the second uninstall level such that an exclamation mark symbol is inserted to the icon of the box application 612. Then, the 111 120 displays the icon of the box application 612 into which the exclamation mark symbol is inserted in a top right corner on the Ul screen, Accordingly, the user may recognize that the, box application 6121s currently at the; second uninstall level and the second uninstall operation is applied to the box application 612.

As such, the device 10 according to the current embodiment manages applications that are seldom used or not used by changing display states of the applications so that the user is able to easily manage the applications. lit detail the device 10 changes the display states of the applications according to uninstall levels so that the user is able to easily recognize a state of the applications and manage the applications. FIG. 6C illustrates a U3 screen where an uninstall operation is applied to the applications 20 installed in the device 10, according to another exemplary .embodiment Referring to FIG. 6C, bus and box applications 620 are at the first uninstall level.

As described above, the determiner I 12 may determine that the bus and box applications 620 are in the first uninstall level based on monitored use histories of the bus and box applications 620.

The uninstaller 113 may change display states of icons of the bus and box applications 620 in the first uninstall level such that the icons are shown as being darker. Then, the UI120 displays the Icons of the bus and box applications 620, which are shown darker, on the UI screen. Accordingly, the user may recognize that the bus and box applications 620 are currently at the first uninstall level and the first uninstall operation is applied to the bus and box applications 620.

According to FIG. 6C, it i s assumed that the bus and box applications 620 are at the same first uninstall-level. However, if the bus and box applications 620 are at different uninstall levels, the UI 120 may display icons of the bus and box applications 620 at different degrees of darkness for classification. FIG. 6D illustrates a UI screen where an Uninstall operation is applied to the applications 20 installed in the device 10, according to another exemplary embodiment. In FIG. 6D, bus and box applications 630 are at the first uninstall level.

As described above, the determiner 112 may determine that the bus and box applications 630 am at the first uninstall level based on monitored use histories of the bus and box applications 630,

The uninstaller 113 may change: display states of icons of the bus and box applications 630 in the first uninstall level such that the icons are shown blurry. Then, the UI 120 di splays the icons of the feus and box applications 630, which are shown blurry , on the UI screen, Accordingly, the user may recognize that the bus and box applications 630 am cmTCntly at the first uninstall level and: the first uninstall operation is applied to the bus and box applications 630.

According to FIG. 6D, it is assumed that the bus and box applications 630 are at the same first uninstall level . However, if the bus and box applications 630 are at different uninstall levels, the UI 120 may display icons of the bus and box applications 630 in different degrees of blurriness for classification, PIG, 6E illustrates a UI screen where an uninstall operation is applied to the applications 20 installed in the device 10, according to another exemplary embodiment, Referring to PIG. 6E, it is assumed that bus and box applications 040 are at the first uninstall level.

As described above, the determiner 112 may determine that, the bus and box applications 640 am at the first uninstall level based on monitored use histories of the bus and box applications 640.

The uninstaller 113 may change display states of icons of the bus and box applications 640 at the first uninstall level such that boundaries of the icons are in dotted ilfies, Then, the UI 120 displays the icons of the bus and, box applications 640 whose boundaries are in dotted lines on the UI screen. Accordingly, the user may recognize that the bus and box applications 640 are currently at the first uninstall level and the first uninstall operation is applied to the bus and box applications 640, PIG, 6F Illustrates a UI screen in which ah uninstall operation is applied to the applications 20 installed in the device 10, according to another exemplary embodiment. Referring to PIG. 6F, it is assumed that bus and box applications 650 are at the first uninstall level.

As described above, the determiner 112 may determine that the bus and box applications 650 are at the first uninstall level based on monitored use histories of the bus and box applications 650,

The uninstaller 113 may change display states of icons of the bus and box applications 650 in the first uninstall level such that the icons are shown concave. Then, the UI 120 displays the icons of the bus and box applications 650 shown concave on the UI screen. Accordingly, the user may recognize that the bus and box applications 650 are euffently at the first uninstall level and the first uninstall operation is applied to the bus and box applications 650.

It will be readily understood by one of ordinary skill in the art that the UI screens showm in FIGS, 6A through 6F are only examples for describing display states of icons of applications, and thus are not limited thereto, FIG. 7A is a diagram for describing the first uninstall operation preformed at the first uninstall level, according to an exemplary embodiment. Referring to PIG. 7A, it is assumed that a bus application 710 is at the first uninstall level.

As described above, the determiner 112 may determine that the bus application 710 is at the first uninstall level based on monitored use history of the bus application 710.

The uninstaller 113 may change a display state of an icon of the bus application 710 at the first uninstall level such that a padlock symbol is added onto the icon of the bus application 710, Then, die UI 120 displays the icon of thebus application. 710 onto which the padlock ."symbol, is inserted in a top right corner On the Ui screen.

Moreover, the uninstaller 113 performs the first uninstall Operation of ending functions of the device 10 required to drive the bus application 710. The ended functions includes a ihnctioh of exchanging information between the device 10 and a server for providing a service of the bus application 710 through a network, a function of automatically updating foe bus application 710, and a background process of the bus·: application 710.

The uninstaller 113 may not delete the bus application 710 but performs the first uninstal l operation by stopping a network traffic or network message generated by the bus application 710, ending processes executed in the background of foe device 10 for the bus application 710, and ends an automatic update of the bus application 710.

However, if the bus application 710 is used again by the user after the first uninstall operation Is performed, the uninstaller 113 may again activate foe functions of the bus application 710 ended through the first uninstallopemtion. FIG, 7B is a diagram for describing the second uninstall operation preformed at the second uninstall level, according to an exemplary embodiment..Referring· to FIG, 7B, it is assumed that a box application 720 is at the second uninstall level.

As described above, the determiner 112 may determine that the box application 720 is at the second uninstall level based on monitored use history of the box application 720.

The uninstaller 113 may Change a display state of an Icon of the box application 720 at the second uninstall level such that an exclamation mark symbol is inserted in the icon of foe box application. 720. Then, the UI 120 displays the icon of the box application 720 into which the exclamation mark symbol is inserted in a top right corner on the UI screen.

Moreover, the uninstaller 113 performs the second uninstall operation by maintaining only the icon of the box application 720 for displaying the box application 720 on the UI screen while deleting user data stored In the device 10 while using the box application 720 and backing up the user data stored In the device 10in a cloud 71 or a server 72.

The User data may include basic setting information for dri ving the box application 720, login Information of the box application 720, a content stored while using the box application 720, history information, and transaction information,

However, if foe box application 720 is used again by the user alter the second: uninstall operation is performed, the uninstaller 113 may again restore (or roll back) foe user data of the box application 720 backed up in the Cloud 71 of foe server 72 to the device 10. FIG. 7C is a diagram for describing foe third uninstall operation preformed at the third uninstall level, accordingto anexemphuy mnb^ Referring to FIG, 7C, it is assumed that a box application 730 is at the third uninstall level.

As described above, the determiner 112 nniy determine that the box application 730 is at the third uninstall level based on monitored use history of the box application 730. lire uninstaller 113 peddrins the third uninstall operation by deleting an icon of the box application 730 and entire information about the box application 730* in other 'Widsith0;b^4ppltcad^.'730 may be completely deleted not only from the UI screen but also from the device 10 and the cloud 71 or server 72 of FIG, ?B.

However, in the third uninstall operatipn, because the box application 730 is completely deleted from the device 10, the device 10 may be pre-set such as to receive a user selection about whether to finally perform the third uninstall operation, i.e., whether to completely delete the box application^730, through the UI 120* In this case, the: uninstaller 1130 may perform the third uninstall operation only when the user requests to perform the third uninstall operation through the UI 120. FIG, 8 is a detailed block diagram of the device IQ ibr managing applications, according to an exempl arv embodiment. Components included in the device 10 of FIG. 2 described above may also be included in the device 10 of FIG. 8, A mobile communicator 1001 may perform call setting, data communication, or the like with a base station dirough a cellulai' netw?oift, such as 3rd generation (3G) or 4th generation (4G). A sub-commhhicator 1002 performs a function for short distance communication, such as Bluetooth or near field communication (NFC). A broadcasting unit 1003 receives a digital multimedia broadcasting (UMB) signal. A camera 1004 tnay include lens and optical devices lor capturing an Image or moving image. A sensor unit 1.005 may include a gravity sensor for detecting movement of the device 10, an illumination sensor for detecting light brightness,a proximity sensor for detecting a proxiniity degree of a person, and a motion sensor lor detecting movement of a person , A global positioning system (GPS) receiver 1006 may receive a GPS signal from a satellite· Various services may be provided to the user by using the GPS signal An inpurfoutput unit 1010 may provide an interface with ah external device or a person, and includes a button :1:011, a microphone 1012, a speaker 1013, a vibration tnotor 1014, a connector 1015* and a keypad 1016, A touch screen 1018 may receive a touch input of the user . Also, a touch screen controller 1017 transmits the touch Input received through the touch screen 1018 to a controller 1050. A power supply 1019 is connected to a battery or external power source to supply power required for the device 1.0.

The input/output unit 1010 and. the touch screen 1018 may correspond to detailed components of (he IJI120 of FIG. 2.

Tlie controller 1050 may execute programs stored in a memory 1060 to execute an object on a display and display a result of executing, according to an exemplary embodiment.

The controller 1050 may correspond to tile controller 110 of FIG, 2 including foe monitor 1 1 1, the determiner 112, and thes uninstaller 113.

Ijie memory 1060 may store results processed or performed by the device 10. For example, the memory 1060 may store monitoring results of the monitor 111, determining results of the detenniner 11.2, and uninstalling results of the uninstaller 113.

Programs stored in the memory 1060 may he classified into a plurality of modules according to functions, for example, into a mobile communication module 1061, a WiFi module 1062, a Bluetooth module 1063, a DMB module 1064, a camera module 1065, a sensor module 1066, a GPS module 1067, a moving image reproducing module 1068, an audio reproducing module 1069, a power module 1070, a touch screen module 1071, a U1 module 1072, and an application module 1073,

For example, the mobile communication module 1061, the Wi-Fi module 1062, and the Bluetooth module 1063 may ihfoim$Ubh about an object from another device or a server by using at least One of the mobile communicator 1.001,-the sub-communicator 1002, and the broadcasting unit 1003.

Also, for example, the touch screen module 1071 may receive a touch input of the user through a screen of the device 10.

Also-, for example, the application module 1073 may determine a type of the touch input of the user and determine whether to expand an object according to toe touch input. Also, For example, the application module 1073 may determine whether a size of the expanded object is equal to or alK>ve a threshold value, and determine which in-formation to bedisplayed.:o&JbG expanded object. Also, for example, the application module 1073 may determine lmw to process a display screen according to the expansion of the object,..

Also, tor example, toe UI module 1072 may expand and display an object on toe display screen, and display predetermined information on the expanded object based on the determination of the application module 1073, Also, for example, the 111 module 1072 may fix and display the expanded object, or reduce the expanded object based on the determination of the application module 1073,

Functions of each module may be intuitively inforned by one of ordinary skill in the art based on its name, and each module may correspond to a group of commands for performing at least one function, described herein.

Commands do not have to be executed in separate software programs, procedures, or modules. The memory 1060 may include more or less commands. Moreover, various functions of the device 10 may be executed by hardware and/or software including at least one signal processing and/or application specified integrated circuit fid). BIG. 9 is a flowchart illustpting a method of managing applications installed on the device If), aeceadmg to an exemplary embodiment. Referring to FIG. 9, the method may include operations processed by the device 10 of FIG. 2 or 8 in time series, and thus, detads described above with reference to FIGS, 1A through 8 may also apply to the method of FIG. 9 even if omitted.

In operation 901, the controller 110 controls the monitor i l l to monitor use histories of applications installed in the device 10.

In operation 902, the controller 110 controls the determiner 112 to determine at least one application satisfying a pre-set uninstall condition, from among the installed applications based on the monitored use histories.

In operation 903, the 0! 120 displays an icon of the determined at least one application On the III screen after changing a display state of the icon. FIG, 10 is a flowchart illustrating a method of managing applications installed on the device 10, according to another exemplary embodiment. Referring to FIG. 10, the method includes operations processed by the device 10 of FIG. 2 or 8 in time series, and thus, details described above with reference to FIGS. .1A through 8 may also be applied to the method of FIG. 10 even if omitted.

In operation I00!. the controller 110 controls the monitor 111 to monitor use histories of the applications installed in the device 10, in operation 1002, the controller 1.10 controls die determiner 112 to determine at least one application corresponding to at least one of a pre-set plurality of uninstall levels, based on the monitored use histories.

In Operation 1003, the controller controls the uninstaller 113 to perform an uninstall operation corresponding to an uninstall level satisfied by the determined at least one application on the determined at least one application, FIG. 11 is a flowchart illustrating a method of managing applications installed on the device .10,. according to another exemplary embodiment, FIG. 11 is a detailed flowchart of the methods of FIGS . 9 and 10, Referring to FIG, 11, the method includes operations processed by the device 10 of FlG, 2 or 8 in time series, and thus, details described above with reference to FIGS. 1A through 8 may also apply to the method of FIG, 11 even if omitted.

In operation 1101, the device 10 sets an uninstall condition for each uninstall level, according to a user input through the UI120. Also, if the uninstall condition is not set by the user, the device 10 may Ore uninstall condition to a default value assigned by the OS of the device 10,

In operation 1102, the controller 110 controls the monitor 111 to monitor use hi stories of the applications installed in the device 10.

In operation 1103, the controller! 10 controls the deterfftlner 112 to determine· whether at least one application satisfying the pre-set uninstall condition exists thorn atnong the installed applications based on the monitored nSC histories.

If the at least one application exists, the controller 110 performs operation 1104. However, if the at least one application does not exist, the controller 110 performs operatic® 1102 to continuously monitor the use histories. in operation 1104, the controller 110 controls the determiner 112 to determine whether the at least one application is in the first uninstall level based on the monitored use histories.

If the at least one application is at the first uninstall level, the controller 110 performs operation 1105, However, if the at least one application Is not at. the first uninstall level, the controller 1.10 performs operation 1106,

In operation 1105. the controller controls the uninstaller 113 to perform the first uninstall operation on the at least one application,

After the first uninstall operation is performed, the controller 110 performs operation 1102 to aga in con tin uousi y monitor the use hi stories,

In operation 1106, the controller 11,0 controls the determiner 112 to determine whether die at. least, one application is in the. second uninstall level based on the mOhitored use histories.

If the at least one application Is at the second uninstall level the controller 110 performs operation 1107. However, if the at least one application is not at the second uninstall level, the controller 110 performs operation 1108.

In operation 1J 07, the controller 110 controls the uninstaller 113 to perform the second uninstall operation on the at least one application.

After die second uninstall operation is performed, die controller 110 performs operation 1102 to again continuously monitor the use histories.

In operation 1.108, the controller 110 controls the determiner 112 to determine whether the at least one application is at the third uninstall level based on the monitored use history. lithe at least one application is at the third uninstall level, the controller 110 performs operation 1109. However, If the at least one application is not at the third uninstall level the controller 110 performs operation 1102.

In operation 1109, the controller, 110 controls the uninstaller 113 to perform the third uninstall operation on the at least one application.

Meanwhile, in the current exemplary embodiment, it may be assumed that three uninstall levels exist. Thus, after the third uninstall operation is performed, the at least one application is completely deleted from the device 10, and thus, no more uninstall operation is perfdrined. However, as described above, the three uninstall levels are assumed for convenience of description in die current embodiment and thus, there may be more or less number of un in stall levels by subdividing or combining the first; through third uninstall levels described herein.

In operation .11.1.0,. if it is ..determined that there is no appHcadoh corresponding to ati uninstall level in operation 1103, the. controller 1 IQ determines whether there is an application whose uninstall level needs to be canceled. In other words, when an uninstall level: was applied to an application because a user did not use the application but the user is currently using the application, the uninstall level of the application may need to be released, Accordingly, the controller 1.10 determines whether to. release the uninstall level of the application to which the uninstall level was applied.

If the uninstall l e vel is to be released, the controller 110 performs operation 1111. However, if the uninstall level is not to be .released, the controller 110 performs Operation 1102.

In operation 1111, the controller 110 cancels the uninstall level of the application determined in operation 1110. Then, the controller 110 performs operation 1102 again. FIG, 1:2 is a flowchart illustrating a method of managing applications installed on the device 1.0, according to another exemplary embodiment, inferring to FIG, .1.2;, the method includes operations performed by the device 10 of FIG. 2 or 8 in time series, and thus, details described above with reference to FIGS. 1A through 8 may also apply to the method of FIG, 12. hi operation 1201, the III 120 displays the applications installed on the device 10.

In operation 1202, the controller 110 controls die monitor 111 to monitor use histories of the installed applications.

In operation 1203, the controller -1 lO eontrols the uninstaller 113 to control the UI 120 such that visual representation of at least one application is changed based on the monitored use histories.

As described above, according to the one or more of the above exemplary embodiments, applications installed on a device, such as a smart phone or a mobile phone, are managed such that a display state of an application that is seldom used of not used at all by a user is changed in stages Or data and information related to such an application is deleted in stages, thereby efficiently managing a limited storage capacity of the device or enabling the user to easily manage the applications.

The exemplary embodiments can be written as computer programs and. can be implemented in general-use digital computers that execute the programs using a computer readable recording medium, Examples of the computer readable recording medi um include magnetic storage: media (e;gl, ROM, floppy disks, hard disks, etc.), optical recording media (e.g,, CD-ROMs, or DVDs), etc.

While one or more exemplary embodiments have been described with reference to the figures, "it will be understood by those of drdinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope as defined by the following claims.

Claims

The claims defining the invention are as follows:

1. A device having a plurality of applications installed thereon, the device comprising: a display configured to display a plurality of icons corresponding to the plurality of applications; and a controller configured to monitor use history of each of the plurality of applications, determine an application from among the applications whose monitored use history satisfies a first level or a second level based on the monitored use history of the each of the plurality of applications, and control the processor to perform a first operation corresponding to the first level or a second operation corresponding to the second level on the determined application, wherein the first operation comprises terminating an automatic update of the determined application, and the second operation comprises providing a user interface inquiring about whether to completely delete the determined application from the device.
2. The device of claim 1, wherein the processor is further configured to change a visual representation of an icon corresponding to the determined application by overlapping a layer of an object representing the icon with a layer of another object.
3. The device of claim 1, wherein the processor is further configured to change a visual representation of an icon corresponding to the determined application by changing an object representing the icon.
4. The device of claim 1, wherein the processor is further configured to control the display to change a visual representation of an icon corresponding to the determined application to identify the first level of the determined application from among the plurality of applications.
5. The device of claim 1, wherein the first level and the second level are classified based on a time period for which an application has not been used.
6. The device of claim 1, wherein the processor is configured to determine the application by applying different types of display change conditions according to attributes of the plurality of applications.
7. The device of claim 6, wherein the attributes of the plurality of applications are classified according to at least one of capacities of the plurality of applications, update frequencies of the plurality of applications, memory resource capacities occupied by the plurality of applications, and types of the plurality of applications.
8. The device of claim 1, wherein the processor is further configured to control the display to change a visual representation of an icon corresponding to the determined application by displaying a predetermined symbol overlapped on the icon.
9. The device of claim 1, wherein the display is configured to change a visual representation of an icon corresponding to the determined application by displaying an additional layer showing a predetermined visual effect and overlapped on the icon.
10. The device of claim 9, wherein the additional layer comprises at least one of a layer for differently showing a color, a brightness, a chroma of the icon, a luma of the icon, a layer for showing the icon darkened, a layer for showing the icon as foggy, a layer for showing the icon in a grayscale, a layer for showing dotted lines on a boundary of the icon, a layer for showing the icon as visually concave, a layer for showing the icon as visually convex, and a layer for applying a vintage effect to the icon.
11. The device of claim 1, wherein the processor is further configured to determine, based on the monitored use history, at least one of an application that has not been used for a predetermined threshold time, an application that is not used repeatedly a threshold number of times until a predetermined point of time, an application that is not used when a location of the device is outside a range of a predetermined place, and an application that has not been used with another device for a threshold time, and change a visual representation of an icon corresponding to the determined application.
12. The device of claim 1, wherein the processor is further configured to delete user data that is stored in the device while the determined application is used, and backing up the stored user data in a server, with respect to the determined application.
13. A method of managing a plurality of applications installed on a device, the method comprising: displaying a plurality of icons corresponding to the plurality of applications through a display; monitoring a use history of each of the applications; determining an application from among the applications whose monitored use history satisfies a first level or a second level based on the monitored use history of the each of the plurality of applications; and performing a first operation corresponding to the first level or a second operation corresponding to the second level on the determined application, wherein the first operation comprises terminating an automatic update of the determined application, and the second operation comprises providing a user interface inquiring about whether to completely delete the determined application from the device.
14. The method of claim 13, further comprises controlling the display such that a layer of an object representing an icon corresponding to the determined application is displayed as overlapping below a layer of another object, or such that the object representing the icon corresponding to the determined application itself is changed.
15. The method of claim 13, wherein the first level and the second level are classified based on a time period for which an application has not been used.
16. The method of claim 13, further comprises changing a visual representation of an icon corresponding to the determined application by displaying at least one of a predetermined symbol and an additional layer for showing a predetermined visual effect, the additional layer being overlapped on an object representing the icon corresponding to the determined application.