HK1158789B

HK1158789B - Method and apparatus for application management

Info

Publication number: HK1158789B
Application number: HK11113270.1A
Authority: HK
Inventors: S．勒梅; S.凯利
Original assignee: 苹果公司
Priority date: 2008-06-06
Filing date: 2009-05-13
Publication date: 2017-09-01

Description

Application management method and system

Technical Field

The present disclosure relates to user interfaces for mobile devices.

Background

Conventional mobile devices are typically dedicated to performing specific functions. For example, mobile phones provide telephone service, Personal Digital Assistants (PDAs) provide a way to organize addresses, contacts, and notes, media players play content, email devices provide email communications, browsers are used for internet surfing, and the like. Modern mobile devices may include two or more of these functions.

In particular, the mobile device may include several different applications that the user may access independently of other applications. For example, a mobile device may include one or more games, web applications, or production applications (productions).

Disclosure of Invention

This specification describes technologies relating to user interfaces for mobile devices. In general, one aspect of the subject matter described in this specification can be embodied in methods that include the actions of: receiving a touch input to access an application management interface on a mobile device; presenting an application management interface; receiving one or more inputs within an application management interface, including an input to install a particular application; installing the selected application; and presenting the installed application. Other embodiments of this aspect include corresponding systems, apparatus, and computer program products.

These and other embodiments may optionally include one or more of the following features. Presenting the application management interface further includes presenting a menu portion and a display portion. The display portion includes one or more application objects corresponding to respective applications, each application object presenting information about the respective application. The menu portion includes a plurality of tabs, each tab providing access to a particular feature of the application management interface. Receiving one or more user inputs includes receiving a selection of a particular application object. The method also includes, in response to the selection, transitioning the display portion to present additional information about the selected application. Presenting the additional information includes presenting one or more comments on the selected application. The selected application object is an application update object associated with an update of an application previously installed on the mobile device. Installing the selected application includes presenting a placeholder object on a display of the mobile device, the placeholder object including an indicator of an installation progress. The method also includes receiving payment information from the user to purchase the particular application. The mobile device includes a multi-touch sensitive display.

In general, one aspect of the subject matter described in this specification can be embodied in systems that include a processor and a user interface for providing interaction with a user, the user interface including a display portion that includes one or more application objects corresponding to respective applications, each application object presenting information about the respective application, and a menu portion that includes a plurality of tabs, each tab providing access to a particular feature of an application management interface. Other embodiments of this aspect include corresponding methods, apparatus, and computer program products.

Particular embodiments of the invention can be implemented to realize one or more of the following advantages. The user can easily navigate through the app store to identify and download applications for the mobile device. The user may be notified of updates to the previously downloaded application without navigating to the update interface. The user can quickly provide feedback about the application, including scoring the application and reporting the identified problems. In addition, a user can quickly and easily share information about a particular application of interest with other users. Once an application is selected, the user may access other features and applications of the mobile device while waiting for the application to be downloaded.

The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the invention will become more apparent from the description, the drawings, and the claims.

Drawings

FIG. 1 is a block diagram of an example mobile device;

FIG. 2 is a block diagram of an example user interface of a mobile device after invoking an application store display object;

FIG. 3 is a block diagram of an example user interface of a mobile device after selecting a Mass preference button;

FIG. 4 is a block diagram of an example user interface of a mobile device for providing information associated with a particular application;

FIG. 5 is a block diagram of an example user interface of a mobile device for notifying another user of an application;

FIG. 6 is a block diagram of an example user interface of a mobile device including a menu for providing information associated with a selected application;

FIG. 7 is a block diagram of an example user interface of a mobile device for reviewing a selected application;

FIG. 8 is a block diagram of an example user interface of a mobile device for reporting a selected application;

FIG. 9 is a block diagram of an example user interface of a mobile device showing an application store after selection of a category tag;

FIG. 10 is a block diagram 1000 of an example user interface of the mobile device 100 showing application objects of a particular selection category;

FIG. 11 is a block diagram of an example user interface of a mobile device showing an application store after selecting the "top 25 (top 25)" tab;

FIG. 12 is a block diagram of an example user interface of a mobile device, illustrating a "top 25" of an application store that hides a free application;

FIG. 13 is a block diagram of an example user interface of a mobile device showing an application store after selection of a search tab;

FIG. 14 is a block diagram of an example user interface of a mobile device after invoking an application store display object and displaying available updates;

FIG. 15 is a block diagram of an example user interface of a mobile device showing an application store after selecting an update tag;

FIG. 16 is a block diagram of an example user interface of a mobile device illustrating application download;

FIG. 17 is a flow diagram illustrating an example process for navigating in an application store using a mobile device;

FIG. 18 is a block diagram of an example user interface of a mobile device showing applications available for deletion;

FIG. 19 is a block diagram of an example user interface of a mobile device showing scoring prompts;

FIG. 20 is a flow diagram illustrating an example process for deleting an installed application using a mobile device;

FIG. 21 is a block diagram of an example network operating environment for the mobile device of FIG. 1; and

FIG. 22 is a block diagram of an example implementation of the mobile device of FIG. 1.

Like reference symbols in the various drawings indicate like elements.

Detailed Description

Fig. 1 is a block diagram of an example mobile device 100. The mobile device 100 may be, for example, a handheld computer, a personal digital assistant, a cellular telephone, a network appliance, a camera, a smartphone, an Enhanced General Packet Radio Service (EGPRS) mobile phone, a network base station, a media player, a navigation device, an email device, a gaming terminal, or a combination of two or more of these and other data processing devices.

Overview of Mobile devices

In some implementations, the mobile device 100 includes a touch-sensitive display 102. The touch sensitive display 102 may use Liquid Crystal Display (LCD) technology, light emitting polymer display (LPD) technology, or some other display technology. The touch-sensitive display 102 may be sensitive to tactile and/or tactile contact by the user.

In some implementations, the touch sensitive display 102 may include a multi-touch sensitive display 102. The multi-touch sensitive display 102 may, for example, process multiple simultaneous touch points, including processing data regarding the pressure, extent, and/or location of each touch point. Such processing facilitates multi-finger gestures and interactions, chord interactions, and other interactions. Other touch sensitive display technologies may also be used, such as a display that is contacted using a stylus or other pointing device. Some examples of multi-touch sensitive display technology are described in U.S. Pat. Nos. 6,323,846, 6,570,557, 6,677,932, and U.S. patent publication 2002/0015024A 1.

In some implementations, the mobile device 100 can display one or more graphical user interfaces on the touch-sensitive display 102 to provide the user with access to various system objects and for communicating information to the user. In some implementations, the graphical user interface may include one or more display objects 104, 106. In the illustrated example, the display objects 104, 106 are graphical representations of system objects. Some examples of system objects include device functions, applications, windows, files, alarms, events, or other identifiable system objects.

Example Mobile device functionality

In some implementations, mobile device 100 can implement multiple device functions, such as a telephony device indicated with telephony object 110; an email device indicated with email object 112; a network data communication device indicated as a Web object 114; Wi-Fi base station equipment (not shown); and a media processing device indicated with media player object 116. In some implementations, particular display objects 104, such as phone object 110, email object 112, Web object 114, and media player object 116, may be displayed in menu bar 118. In some implementations, device functionality can be accessed from a top-level graphical user interface, such as the graphical user interface shown in FIG. 1. Touching one of the objects 110, 112, 114 or 116 may, for example, invoke a corresponding function.

In some implementations, the mobile device 100 can implement network distribution functionality. For example, the functionality may enable a user to use mobile device 100 and its associated network while traveling. In particular, the mobile device 100 may extend internet access (e.g., Wi-Fi) to other wireless devices in the vicinity. For example, the mobile device 100 may be configured as a base station for one or more devices. Thus, the mobile device 100 may allow or deny network access to other wireless devices.

In some implementations, after invoking a device function, the graphical user interface of mobile device 100 is changed, or another user interface or user interface element is added to or replaced by another user interface or user interface element, in order to facilitate user access to the particular function associated with the respective device function. For example, in response to a user touching the phone object 110, the graphical user interface of the touch-sensitive display 102 may present display objects related to various phone functions; similarly, touching email object 112 may cause the graphical user interface to present display objects related to various email functions; touching the Web object 114 may cause the graphical user interface to present display objects related to various Web surfing functions; and touching media player object 116 may cause the graphical user interface to present display objects related to various media processing functions.

In some implementations, the top-level graphical user interface environment or state of FIG. 1 can be restored by pressing a button 120 located near the bottom of the mobile device 100. In some implementations, each corresponding device function may have a corresponding "home" display object displayed on the touch-sensitive display 102, and the graphical user interface environment of fig. 1 may be restored by pressing the "home" display object.

In some implementations, the top-level graphical user interface may include additional display objects 106, such as a Short Message Service (SMS) object, a calendar object, a photo object, a camera object, a calculator object, a stock object, a weather object, a map object, a notepad object, a clock object, an address book object, a settings object, and an application store object 132. Touching the SMS display object may, for example, invoke an SMS messaging environment and support functions; similarly, each selection of a display object may invoke a corresponding object environment and function.

Additional and/or different display objects may also be displayed within the graphical user interface of FIG. 1. For example, if device 100 is acting as a base station for other devices, one or more "connection" objects may appear within the graphical user interface to indicate the connection. In some implementations, the user can configure the display objects 106, e.g., the user can indicate which display objects 106 are displayed, and/or can download additional applications or other software that provide other functionality and corresponding display objects.

In some implementations, the mobile device 100 can include one or more input/output (I/O) devices and/or sensor devices. For example, a speaker 160 and a microphone 162 may be included to facilitate voice-enabled functions, such as telephone and voicemail functions. In some implementations, up/down buttons 184 may be included for volume control of the speaker 160 and microphone 162. The mobile device 100 may also include an on/off button 182 for a ring indicator for incoming phone calls. In some implementations, a loud speaker 164 may be included to facilitate hands-free voice functionality, such as speakerphone functionality. An audio jack 166 for a headset and/or microphone may also be included.

In some implementations, a proximity sensor 168 can be included to facilitate detecting that the user has positioned the mobile device 100 proximate to the user's ear and, in response, to disconnect the touch-sensitive display 102 to prevent accidental function invocations. In some implementations, the touch-sensitive display 102 can be turned off when the mobile device 100 is near the user's ear in order to save additional energy.

Other sensors may also be used. For example, in some implementations, an ambient light sensor 170 may be used to facilitate adjusting the brightness of the touch sensitive display 102. In some implementations, movement of the mobile device 100 can be detected using the accelerometer 172, as indicated by the directional arrow. Thus, display objects and/or media may be presented according to the detected orientation, e.g., portrait or landscape. In some implementations, the mobile device 100 may include circuitry and sensors to support location determination capabilities such as provided by a Global Positioning System (GPS) or other positioning system (e.g., systems using Wi-FI access points, television signals, cellular grids, Uniform Resource Locators (URLs)). In some implementations, a positioning system (e.g., a GPS receiver) can be integrated within the mobile device 100 or provided as a separate device that can be connected to the mobile device 100 through an interface (e.g., the port device 190) to provide access to location-based services.

The mobile device 100 may also include a camera lens and sensor 180. In some implementations, the camera lens and sensor 180 can be located on the back of the mobile device 100. The camera may take still images and/or video.

Mobile device 100 may also include one or more wireless communication subsystems, such as 802.11b/g communication device 186 and/or Bluetooth^TMA communication device 188. Other communication protocols may also be supported, including other 802.x communication protocols (e.g., WiMax, Wi-Fi, 3G), Code Division Multiple Access (CDMA), global system for mobile communications (GSM), Enhanced Data GSM Environment (EDGE), and so forth.

In some implementations, a port device 190, such as a Universal Serial Bus (USB) port or a docking port, or some other wired port connection, is included. For example, port device 190 may be utilized to establish a wired connection with other computing devices, such as other communication devices 100, network access devices, personal computers, printers, or other processing devices capable of receiving and/or transmitting data. In some implementations, the port device 190 allows the mobile device 100 to synchronize with a host device using one or more protocols, such as, for example, TCP/IP, HTTP, UDP, and any other known protocols. In certain implementations, the TCP/IP over USB protocol described in U.S. patent application No.11/770,691 entitled "Multiplexed DataStreamProtocol" filed on 28.6.2007 and U.S. patent publication No.20080304486 may be used.

FIG. 2 is a block diagram 200 of an example user interface of mobile device 100 after invoking an application store display object (e.g., application store display object 132 of FIG. 1). For example, the user may access the application store display object 132 using the touch-sensitive display 102 (e.g., by pressing the application store display object 132), which results in transitioning to the application store interface. In some implementations, touching the application store display object 132 in FIG. 1 causes an animated transition to the application store interface.

The user interface of the application store includes a display portion 236 and a menu portion 226. Menu portion 226 may include several tabs. Specifically, the menu portion 226 includes a features tab (featuredbab) 216, a categories tab 218, a top25 (top25) tab 220, a search tab 222, and update tabs 224. Each of the tabs in menu portion 226 may be used to access different features of the application store, each of which will be described in more detail below. In some implementations, other tags may be provided and/or the tag order may be changed, for example, according to the determination of the application store, the mobile device, or based on input received from another remote location.

Display portion 236 displays feature interface 203 associated with feature tab 216, which is highlighted in display portion 236. The feature interface 203 includes a title bar 201. The title bar 201 includes a recently added button (RecentlyAdded)202 and a popular preferences (StaffFavorites) button 204. The recently added button 202 and the popular preference button 204 are shown as different buttons. However, these buttons may take other forms, including, for example, a single toggle button (toggle button) that can be toggled from one state to another by touching the button more than once.

The aspect interface 203 also includes one or more application objects 240. The recently added button 202 is shown as recently selected (e.g., based on user input to the touch-sensitive display 102). When the recently added button 202 is selected, the displayed application object 240 corresponds to the application that was recently added to the application store.

In some implementations, the most recently added application is specified in terms of a time period since a particular application was included within the application store. For example, recently added applications may include applications that have become available in an application store within the past 30 days. However, in some other implementations, the recently added application may be a specified number (e.g., 25) of recently added applications in the application store, regardless of the actual elapsed time.

The application objects 240 may be ordered in the display portion 236 according to one or more criteria. For example, the application objects may be ordered by date added to the application store, alphabetically, or by user rating.

In particular, application objects 240 shown in display portion 236 include application objects 210, 212, and 214. Additionally, when display portion 236 is unable to display all application objects 240 at once, the user may scroll 238 up or down to view additional application objects 240. While scrolling 238 is represented by a dashed arrow at a particular portion of display portion 236, the user may scroll 238 from other points. In particular, the user may scroll through gestures in a particular direction (e.g., up or down) on the touch-sensitive display 102.

Each application object 240 includes information associated with a particular application. For example, the application object 210 includes application information 228. The application information 228 may include an image representing the application, an application name (e.g., "application 1" of the application object 210), a developer name, and rating information. In some implementations, the scoring information is represented by a particular number of asterisks. These asterisks are filled in to indicate the average score of the application (e.g., 3 out of 5). In some implementations, the asterisks are partially filled in order to represent a finer degree of average score granularity.

In some other implementations, the scoring information is represented using different symbols. For example, in some implementations, dots are used to represent unselected asterisks, which are replaced with asterisks that reach a score level, so that there are only asterisks that equal the average score. In some implementations, the scoring information also includes several comments (e.g., from individual users) used to determine an average score.

The application object 240 also includes purchase information 230. The purchase information indicates whether the application is free or must be purchased (e.g., indicated with a "free" or "buy" label). In some implementations, the purchase information indicates a cost of the application (e.g., $ 5.00). In some other implementations, the application object 240 may indicate whether the user has installed a particular application. For example, if the user has installed an application indicated by application object 210, purchase information 230 may indicate "installed" rather than "free". Alternatively, purchase information 230 may indicate "uninstall" (uninstantall), indicating that the user may uninstall an already installed application.

The application object 240 may also include an ">" indicator (e.g., the indicator 232 of the application object 210). The indicator 232 indicates that selecting a particular application object (e.g., by touching the application object 210) will transform the user interface to provide additional information about the selected application. The transition may be an animated representation.

Display portion 236 may also include one or more advertisements. In the display portion 236, the first advertisement 206 and the second advertisement 208 are shown adjacent to the title bar 201. In other implementations, only a single advertisement is presented. Alternatively, additional advertisements may be presented. Additionally, although the advertisement is shown near the title bar 201, one or more advertisements may be presented at different locations on the display portion 236.

Fig. 3 is a block diagram 300 of an example user interface of the mobile device 100 after a mass preference button (e.g., the mass preference button 204 of fig. 2) is selected. As shown in fig. 2, the title bar 201 includes a recently added button 202 and a popular preference button 204. When the community preference button 204 is selected, the display portion 236 presents the application object 340 as part of the feature interface 303. The application objects 340 may include one or more recently added application objects 240, or may be different from the application objects 240.

In some implementations, the application object 340 represents one or more personally selected application objects associated with the application store. For example, a public preference may be selected by a group of individuals within a particular time period. Thus, the public preferences may change regularly, for example, every 30 days. In some other implementations, the public preferences are identified according to the application that received the highest score from a particular group of individuals. In some implementations, the number of application objects 340 identified as popular preferences is limited to a particular number (e.g., the top25 applications).

The application objects 340 may be ordered in the feature interface 303 according to one or more criteria. For example, application objects may be ordered by date added to the application store, alphabetically, or by person score.

In particular, application objects 340 shown in display portion 236 include application objects 302, 304, and 306. Additionally, when the display portion 236 is unable to display all of the application objects 340 at once, the user may scroll 238 up or down to view additional application objects 340 as described above with reference to FIG. 2.

Each application object 340 includes information associated with a respective application. Similar to the application information 228 described above with reference to fig. 2, the application information may include an image representing an application, an application name (e.g., "application 4" of the application object 302), a developer name, and rating information. In some implementations, the scoring information is represented by a particular number of asterisks that identify the average score of the respective application.

The application object 340 also includes purchase information. The purchase information indicates whether the "popular preference" application is free or has to be purchased. In some implementations, the purchase information indicates a cost (e.g., $5.00) for a particular application. In some other implementations, the application object 340 indicates whether the user has installed a particular application. For example, if the user has installed the application indicated by application object 302, the purchase information may indicate "installed" rather than "free". Alternatively, the purchase information may indicate "uninstall," indicating that the user may uninstall an already installed application.

The application object 340 may also include an ">" indicator (e.g., the indicator 232 of FIG. 2). The indicator indicates that selecting a particular application object (e.g., by touching application object 302) will transform the user interface to provide additional information about the selected application. The transition may be an animated representation.

The feature interface 303 may also include one or more advertisements. Specifically, the display portion 236 presents the first advertisement 206 and the second advertisement 208 adjacent to the title bar 201. In other implementations, only a single advertisement is presented. Alternatively, additional advertisements may be presented. Additionally, although the advertisement is shown near the title bar 201, one or more advertisements may be presented at different locations on the display portion 236.

In fig. 2 or 3, upon user selection of an application object (e.g., selection of one of application objects 240 or 340, respectively), the user interface may transition to provide additional information about the application associated with the selected application object.

FIG. 4 is a block diagram 400 of an example user interface of the mobile device 100 for providing information associated with a particular application. In particular, the application information interface 403 corresponds to a user selection of the application object 210 of FIG. 2.

The application information interface 403 includes an information display portion 410 and a menu portion 226. The menu portion 226 includes a features tab 216, a category tab 218, a top25 tab 220, a search tab 222, and an update tab 224. In some implementations, menu portion 226 is hidden when application information interface 403 is presented.

The display portion 410 includes a title bar 401. Title bar 401 identifies the user interface as an application information interface. In addition, the title bar 401 may include a Back button 402 and a tell friends button 404. The back button 402 allows the user to, for example, cancel the application information interface 403 and return to the previous user interface (e.g., the user interface of the application store shown in fig. 2 or 3). The tell friends button 404 allows the user to send information about the selected application. Specifically, touching the tell friends button 404 causes the user interface to transition to an interface for notifying another person of the particular application. An interface for notifying another person of the selected application is described in more detail below with reference to fig. 5.

Display portion 410 may also include application information 406, purchase information 408, application screen shots 412, and comments 414. The application information 406 includes, for example, an application name and a developer. The application information 406 may also include images representing particular applications as well as other information, such as the date the application was added to the application store. The application information 406 may also include a brief description of the application.

The purchase information 408 indicates whether the selected application is free or available for purchase. Alternatively, the purchase information 408 may indicate a price of the application (e.g., $ 5.00). In some implementations, the user may redeem points (redememcededit) in order to purchase the application. For example, the user may have a cash card, gift certificate, or other credit available for purchasing an application of the application store. In some implementations, a "redemption" button is presented to the user in the application information interface. Touching the redemption button creates an interface in which the user can enter account information corresponding to points to be applied.

Additionally, in some implementations, touching purchase information 408 initiates the process of downloading the application. For example, if the application is free, the download process may begin without other user input. Alternatively, if a purchase is required, the user account may be accessed in order to purchase the application. In some implementations, the user may redeem a coupon or similar credit in order to purchase the application. In some other implementations, the user is required to provide an account or other authentication information before purchasing the application.

In some alternative implementations, the purchase information 408 indicates whether the user has installed the application (e.g., by including the text "installed" or "uninstalled" in the purchase information 408).

Screen shot 412 may provide a screen capture image of an application interface. In some implementations, a more detailed description of the application is provided instead of or in addition to screen shot 412. For example, the detailed description may include characteristics of the application and other information. In some implementations, more than one screen shot 412 is provided. Alternatively, in some other implementations, additional screen shots may be provided as thumbnails that may be displayed when selected by the user.

Comments 414 include rating information for the application and personal comments. The scoring information may include a graphical illustration of the average score (e.g., using an asterisk score). In addition, the number of individual reviews used to determine the average score may also be provided. The average score may be followed by one or more personal reviews of the application. In some implementations, all comments are listed. In some other implementations, only a specified number of comments are listed. In some implementations, the user may scroll 238 to view additional comments that cannot be presented within the visual portion of the application information interface 403.

The comment 414 portion of the application information interface 403 may also include a comment button 418 that allows the user to provide comments or other reports associated with the application. Providing comments on the application is described below with reference to fig. 6-8.

FIG. 5 is a block diagram 500 of an example user interface of the mobile device 100 for notifying another user of an application. In particular, FIG. 5 includes a notification interface 502. The notification interface 502 may be presented in response to a user selection of the "tell friends" button 404 of FIG. 4.

The notification interface 502 includes a title bar 501. The title bar 501 identifies the notification interface 502 (e.g., "tell friend"). In addition, the title bar 501 includes a back button 504 and a send button 506. The back button 504 may cancel the notification interface 502 and allow the user to return to the previous user interface (e.g., the application information interface 403). A send button 506 allows the user to send application information to another person.

The notification interface 502 may provide a preconfigured email message that includes links to application information within the application store. Notification interface 502 includes a "to" field 508, a "from" field 510, a subject field 512, and a text box 514. The "to" field 508 allows the user to identify the recipient of the notification. The user may enter, for example, an email address or a name corresponding to a contact or address book entry. The from field 510 allows the user to identify the sender of the notification for the recipient. In some implementations, the from field 510 is automatically filled out based on the user profile or account information. In some other implementations, the "from" field 510 is not presented to the user, but is automatically added to the notification. The "subject" field 512 allows the user to indicate a subject for the recipient, e.g., "view this application". In some implementations, the subject field 512 is automatically filled in by the application store, for example, with an application name or other text.

The text box 514 provides additional space for the user to provide additional text (e.g., a message body) to the user. In some implementations, the textbox 514 has a maximum number of characters that the user is allowed to enter.

The keyboard 516 may be used to provide input for each field and text box 514. The keyboard 516 provides a full QWERTY key layout for typing. By touching a single key according to the desired text, the user enters the text with the touch sensitive display 102. After entering information into one or more fields, the user may send the notification by touching send button 506 as described above. In some implementations, sending the notification causes the user interface to transition to a previous user interface (e.g., application information interface 403).

FIG. 6 is a block diagram 600 of an example user interface of the mobile device 100 that includes a menu 602 for providing information associated with a selected application. Specifically, a portion of the application information interface 403 may overlap the menu 602. The menu 602 may be partially transparent so that the overlapping portion of the application information interface 403 is partially visible. In some implementations, the menu 602 is presented in response to a user selecting a comment button 418 within the application information interface 403. In some alternative implementations, the menu 602 completely replaces the application information 403, rather than being provided in partial overlap.

The menu 602 includes a write comments (WriteaReview) button 604, a report questions (ReportaProblem) button 606, and a Cancel (Cancel) button 608. A write comments button 604 allows a user to write comments to the application of the application information interface 403. Specifically, when the user touches the write comment button 604, the user interface transitions to a comment interface (e.g., using animation transitions). The review interface is described in more detail below with reference to FIG. 7.

A report problems button 606 allows the user to report problems with the application identified in the application information interface 403. Specifically, when the user touches the report problems button 604, the user interface transitions to a reporting interface (e.g., using an animation transition). The reporting interface is described in more detail below with reference to FIG. 8.

A cancel button 608 allows the user to cancel the menu 602 and return to the application information interface 403 of fig. 4.

FIG. 7 is a block diagram 700 of an example user interface of the mobile device 100 for reviewing a selected application. In particular, FIG. 7 shows a comment interface 702 presented, for example, in response to a user selecting the write comment button 604 (FIG. 6).

Review interface 702 includes a title bar 701 that identifies the interface as a review interface. The title bar 701 also includes a back button 704 and a send button 706. The back button 704 may cancel the comment interface 702. And allows the user to return to the previous user interface (e.g., application information interface 403). A send button 706 allows the user to submit comments.

Review interface 702 includes a score 708. The scoring 708 allows the user to assign a score value to the application. For example, the user may assign a particular number of stars (e.g., from 0 to 5 stars) of the most likely number of stars to the application. In particular, the user may assign an asterisk using a gesture action on the touch-sensitive interface 102. For example, the user may slide a finger in a first direction to incrementally increase the number of stars (to a maximum number, e.g., 5), or incrementally decrease the number of stars (to a minimum number, e.g., zero) in a second direction.

Comment interface 702 also includes a from field 710, a title field 712, and a comment text box 714. The from field 710 allows the user to identify who provided the comment. In some implementations, the from field 710 is automatically populated based on the user profile or account information. In some other implementations, the "from" field 710 is not presented to the user, but is automatically added to the comment. The "title" field 712 allows the user to identify the specialty or ability they provide comments. In some implementations, the "title" field 712 is not provided.

Textbox 714 provides additional space for the user to provide comment text in addition to the value of the comment. In some implementations, the text box 714 has a maximum number of characters that the user is allowed to enter.

The keyboard 516 may be used to provide input for each field and text box 514. The keyboard 516 provides a full QWERTY key layout for typing. By touching a single key according to the desired text, the user enters the text with the touch sensitive display 102. After entering information into one or more fields, the user may submit a comment by touching send button 706 as described above. In some implementations, submitting the comment causes the user interface to transition to a previous user interface (e.g., application information interface 403).

FIG. 8 is a block diagram 800 of an example user interface of the mobile device 100 for reporting a selected application. In particular, FIG. 8 shows a reporting interface 802 presented, for example, in response to a user selecting the report issue button 606 (FIG. 6).

The reporting interface 802 includes a title bar 801 that identifies the interface as a reporting interface. The title bar 801 also includes a back button 804 and a send button 806. The back button 802 may, for example, cancel the reporting interface 802 and allow the user to return to the previous user interface (e.g., the application information interface 403). A send button 806 allows the user to submit a report.

Review interface 802 includes a menu button with suggested questions to report. Specifically, the review interface 802 includes a report program error (bug) button 808, a report attack (Offensive) button 810, and other (concernuntriested) buttons 812. The user may select one of the menu buttons by touching a particular menu button within comment interface 802. In some implementations, when a user selects a particular menu button, the selected menu button is highlighted. In some other implementations, when a user selects a menu button, an icon is displayed to indicate the selection, e.g., a checkmark.

In addition, a text box 814 is presented. Text box 814 allows the user to optionally describe the reported problem. In some implementations, text box 814 has a maximum number of characters that the user is allowed to enter.

Keyboard 516 may be used to provide input for text box 814. The keyboard 516 provides a full QWERTY key layout for typing. By touching a single key according to the desired text, the user enters the text with the touch sensitive display 102. After entering information into text box 814, the user may submit the report by touching send button 806, as described above. In some implementations, submitting the report causes the user interface to transition to a previous user interface (e.g., application information interface 403).

In some implementations, the keyboard 516 is not presented in the reporting interface 802 until the user selects the text box 814 (e.g., by touching the text box 814).

FIG. 9 is a block diagram 900 of an example user interface of the mobile device 100 illustrating the application store after a category tag (e.g., category tag 218 of FIG. 2) is selected. For example, a user may access the application store display object 132 using the touch-sensitive display 102 (e.g., by pressing the application store display object 132), resulting in a transition to the application store interface. In some implementations, touching the application store display object 132 in FIG. 1 causes an animated transition to the application store interface.

The user interface of the application store includes a display portion 902 and a menu portion 226. Menu portion 226 may include several tabs. Specifically, menu portion 226 includes feature tab 216, category tab 218, top25 tabs 220, search tab 222, and update tab 224. Each tab in menu portion 226 may be used in order to access different features of the application store.

Display portion 236 displays a category interface 903 associated with category tab 218, which is highlighted in display portion 236. Category interface 903 includes a title bar 901 that identifies the user interface as a category interface. In some implementations, the title bar 903 includes one or more buttons, such as a back button that allows the user to access a previous user interface. Alternatively, by pressing button 120, the user can exit the application store and return to the "main menu" interface shown in FIG. 1.

The category interface 903 includes one or more category buttons. Specifically, category interface 903 includes a Games button 904, Entertainment button 906, News button 908, production button 910, Sports button 912, and Travel button 914. The displayed categories may be arranged in any order (e.g., alphabetically, by popularity, etc.). Additionally, other categories may be displayed instead of or in addition to the illustrated categories. In some implementations, the user can view additional categories by scrolling 238 the category button.

Each category button allows the user to transition to an interface that provides an application object associated with a particular category. For example, selecting the game button 904 may cause the category interface to transition to a game object interface that includes one or more application objects corresponding to games or other content associated with the game category.

FIG. 10 is a block diagram 1000 of an example user interface of the mobile device 100 showing application objects of a particular selection category. In particular, FIG. 10 shows a game object interface 1003 presented in response to a user category selection (e.g., a user selection of game button 904 in FIG. 9).

The user interface includes a display portion 1002 and a menu portion 226. Menu portion 226 includes a number of tabs. In particular, menu portion 226 includes feature tab 216, category tab 218, top25 tab 220, search tab 222, and update tab 224. Specifically, the category label 218 is highlighted.

The display section 1002 displays a game object interface 1003 associated with selection of a game category. The game object interface 1003 includes a title bar 1001 that includes a recently added button 1004 and a popular preference button 1006. The recently added button 1004 and the popular preference button 1006 are shown as distinct buttons, however, they may take other forms including, for example, a single two-state button that may transition from one state to another.

The game object interface 1003 also includes one or more game objects 1040. The recently added button 1004 is shown as having been currently selected (e.g., based on user input to the touch-sensitive display 102). When the recently added button 1004 is selected, the displayed game object 1040 corresponds to the game application that was recently added to the application store in a manner similar to that described above with reference to FIG. 2, but with respect to the game object. Similarly, when the community preference button 1006 is selected or triggered, the displayed game object 1040 corresponds to a game application that has been selected by one or more individuals associated with the application store in a manner similar to that described above in fig. 2.

The game objects 1040 shown in the display portion 1002 include game objects 1012, 1014, and 1016. Additionally, when the display portion 1002 cannot display all of the game objects 1040 at once, the user may scroll 238 up or down to view additional game objects 1040.

Each game object 1040 includes information associated with a particular game application. For example, the game object 1012 includes game application information 1018. The game application information 1018 may include an image representing a game application, a game application name ("game 1"), a developer name, and rating information. In some implementations, the scoring information is represented by a specified number of asterisks. These asterisks are filled in to indicate the average score of the game (e.g., 3 out of 5 stars). In some implementations, the asterisks may be partially filled in order to represent a finer degree of average score granularity.

The game object 1040 also includes purchase information 1022. The purchase information 1022 indicates whether the application is free or must be purchased. In some implementations, the purchase information indicates a cost of the game (e.g., $ 5.00). In some other implementations, each game object (e.g., game objects 1012, 1014, and 1016) may indicate whether the user has installed a particular game. For example, if the user has installed the game indicated by game object 1012, purchase information 1022 may indicate "installed" rather than "free". Alternatively, the purchase information 122 may indicate "uninstall," indicating that the user may uninstall an already installed game application.

Game object 1040 may also include an ">" indicator 1020. Indicator 1020 indicates that selecting a particular game object (e.g., by touching game object 1012) will transform the user interface to provide additional information about the selected game application. The transition may be an animated representation.

Display portion 1002 may also include one or more advertisements. In display portion 1002, a first advertisement 1008 and a second advertisement 1010 are shown adjacent to title bar 1001. In other implementations, only a single advertisement is presented. Alternatively, additional advertisements may be presented. Additionally, although the advertisement is shown near the title bar 1001, one or more advertisements may be presented at different locations on the display portion 1002.

The user may select a particular game object 1040 to transition to providing information regarding the game associated with the selected game object. The gaming information is provided in an application information interface 403 similar to that described above with reference to FIG. 4.

FIG. 11 is a block diagram 1100 of an example user interface for the mobile device 100, showing the application store after selecting the "top 25" tabs (e.g., "top 25" tabs 220). For example, a user may access the application store display object 132 using the touch-sensitive display 102 (e.g., by pressing the application store display object 132), resulting in a transition to the application store interface. In some implementations, touching the application store display object 132 in FIG. 1 causes an animated transition to the application store interface.

The user interface of the application store includes a display portion 1102 and a menu portion 226. Menu portion 226 includes a number of tabs. Specifically, menu portion 226 includes feature tab 216, category tab 218, top25 tabs 220, search tab 222, and update tab 224. Each tab in menu portion 226 may be used in order to access different features of the application store.

Display portion 1102 displays "top 25" interfaces 1103 associated with "top 25" tabs 220, which are highlighted in display portion 236. The top25 interfaces 1103 include a title bar 1101 that identifies the user interface as the top25 interfaces. The title bar 1101 also includes a "show free" button 1104 and a "hide free" button 1106.

When the "show free" button 1104 is selected (as highlighted in FIG. 11), the "top 25" interface 1103 displays application objects 1140, which include application objects associated with applications that are available free of charge. When the "hide free" button 1106 is selected, the "top 25" interfaces 1103 display only application objects that need to be paid for.

The "top 25" interfaces 1103 include application objects 1140. Specifically, 25 application objects 1140 are listed. However, when all 25 application objects 1140 cannot be displayed in display portion 1102, the user may scroll 238 to view additional application objects. Additionally, in some implementations, when the user scrolls to the bottom of the "top 25" list of application objects, a button may be provided that allows the user to view another set of application objects (e.g., "next 25 (next 25)" application objects).

Application objects 1140 are shown to include application objects 1112, 1114, and 1116. Application objects 1140 are presented in an ordered order. Thus, the application object 1112 is ranked higher than the application object 1114. A rank for each application object is identified within the application object. For example, the application object 1112 includes a rank identifier 1118 that identifies the application object 1112 as having a rank number 1in the list of application objects 1140.

Each application object 1140 includes information associated with a particular application. For example, the application object 1112 includes application information 1122. The application information 1122 may include an image representing an application, an application name ("application 5"), a developer name, and rating information. In some implementations, the scoring information is represented by a particular number of asterisks. These asterisks are filled in to indicate the average score of the game (e.g., 3 out of 5). In some implementations, the asterisks are partially filled in order to represent a finer degree of average score granularity.

Application object 1140 also includes purchase information 1124. The purchase information 1124 indicates whether the application is free or must be purchased. In some implementations, the purchase information indicates a cost of the application (e.g., $ 5.00). In some other implementations, each application object (e.g., application objects 112, 1114, and 1116) may indicate whether a user has installed a particular application. For example, if the user has installed an application indicated by application object 1112, purchase information 1124 may indicate "installed" rather than "free". Alternatively, purchase information 1124 may indicate "uninstall," indicating that the user may uninstall an already installed application.

Application object 1140 may also include an ">" indicator 1124. Indicator 1124 indicates that selecting a particular application object (e.g., by touching application object 1112) will transform the user interface to provide additional information about the selected application. The transition may be an animated representation.

Display portion 1102 may also include one or more advertisements. In the display portion 1102, a first advertisement 1108 and a second advertisement 1110 are shown adjacent to the title bar 1101. In other implementations, only a single advertisement is presented. Alternatively, additional advertisements may be presented. Additionally, although the advertisement is shown near the title bar 1101, one or more advertisements may be presented at different locations on the display portion 1102.

Selecting a particular application object within the ordered list of application objects 1140 transitions the user interface to an interface that provides information about the application associated with the selected application object. The application information is provided in a manner similar to the application information interface 403 described above with reference to fig. 4.

Fig. 12 is a block diagram 1200 of an example user interface for the mobile device 100, showing the "top 25" of the application store with the free application hidden. The user interface of the application store includes a display portion 1202 and a menu portion 226. Menu portion 226 may include several tabs. Specifically, menu portion 226 includes feature tab 216, category tab 218, top25 tabs 220, search tab 222, and update tab 224. Each tab in menu portion 226 may be used in order to access different features of the application store.

Display portion 1202 displays "top 25" interfaces 1203 associated with "top 25" tabs 220, which are highlighted in display portion 236. The top25 interfaces 1103 include a title bar 1201 identifying the user interface as the "top 25" interface. The title bar 1201 also includes a "show free" button 1104 and a "hide free" button 1106. Specifically, as highlighted in FIG. 12, a "hide free" button 1106 is selected. When the "hide free" button 1106 is selected, the "top 25" interfaces 1203 display only application objects that need to be paid for.

The "top 25" interfaces 1203 include application objects 1240. Specifically, up to 25 application objects 1240 are listed. However, when there are more application objects than application objects 1240 that may be displayed within display portion 1202, the user may scroll 238 to view additional application objects. Additionally, in some implementations, when the user scrolls to the bottom of the "top 25" list of application objects, a button may be provided that allows the user to view another set of application objects (e.g., "next 25" application objects).

Application objects 1240 are shown to include application objects 1204, 1206, and 1208. Application objects 1240 are presented in an ordered order. Thus, application object 1204 is ranked higher than application object 1206. A rank for each application object is identified within the application object. For example, application object 1204 includes a rank identifier 1210 that identifies application object 1204 as having a rank number of 1in a list of application objects 1240. The ranking may be based on, for example, the average asterisk score per application or some other criteria.

Each application object 1240 includes information associated with a particular application. For example, application object 1240 may include an image representing an application, an application name ("application 2"), a developer name, and rating information.

The application object 1240 also includes purchase information 1212. Specifically, each application object 1240 requires payment due to the selection and triggering of the "hidden free" button 1106. Selecting a particular application object in the ordered list of application objects 1240 transitions the user interface to an interface that provides information about the application associated with the selected application object. The application information is provided in a manner similar to the application information interface 403 described above with reference to fig. 4.

FIG. 13 is a block diagram 1300 of an example user interface of the mobile device 100 showing an application store after selection of a search tab. For example, a user may access the application store display object 132 using the touch-sensitive display 102 (e.g., by pressing the application store display object 132), resulting in a transition to the application store interface. In some implementations, touching the application store display object 132 in FIG. 1 causes an animated transition to the application store interface.

The user interface of the application store includes a display section 1302 and a menu section 226. Menu portion 226 includes a number of tabs. Specifically, menu portion 226 includes feature tab 216, category tab 218, top25 tabs 220, search tab 222, and update tab 224. Each tab in menu portion 226 may be used in order to access different features of the application store.

Specifically, display portion 1302 displays search interface 1303 associated with search tab 222, which is highlighted in display portion 236. Search interface 1303 includes a title bar 1201 that identifies the user interface as an application search interface.

Search interface 1303 includes search field 1304 and search button 1306. Search field 1304 allows a user to enter one or more search terms. For example, a user may enter keywords identifying a particular application, developer, category, or other keywords. Search button 1306 performs an application search based on user input to search field 1304. For example, the user may perform a search by touching search button 1306.

The user may enter a search term in search field 1304 using keyboard 516. The keyboard 516 provides a full QWERTY key layout for typing. By touching a single key according to the desired text, the user enters the text with the touch sensitive display 102.

Performing the search (e.g., by touching search button 1306) transforms the user interface into an interface that provides information about one or more applications associated with the input search term. The application information is provided in a manner similar to the application information interface 403 (e.g., application object list) described above with reference to fig. 4.

FIG. 14 is a block diagram 1400 of an example user interface of the mobile device 100 after invoking the application store display object and displaying the available updates. For example, a user may access the application store display object 132 using the touch-sensitive display 102 (e.g., by pressing the application store display object 132), resulting in a transition to the application store interface. In some implementations, touching the application store display object 132 in FIG. 1 causes an animated transition to the application store interface.

The user interface of the application store includes a display portion 236 and a menu portion 240. Menu portion 226 includes a number of tabs. Specifically, menu portion 226 includes feature tab 216, category tab 218, top25 tabs 220, search tab 222, and update tab 224. Each tab in menu portion 226 may be used in order to access different features of the application store.

Display portion 236 displays feature interface 203 associated with feature tab 216, which is highlighted in display portion 236. The feature interface 203 includes the application objects described above with reference to fig. 2.

Update tag 224 includes an update flag 1402. Update flag 1402 identifies whether there is an update available for an application installed on mobile device 100. The user may identify whether there are updates available without having to select the update tab 224. For example, update flag 1402 may be a symbol or graphic associated with update tag 224. As shown in fig. 14, the update flag 1402 is a circle with a number therein, which is superimposed on a portion of the graphic identifying the update tag 224. In addition, update flag 1402 is only visible when an update is available. In some implementations, the update flag indicates the number of updates that are available (e.g., by including a number within the flag). For example, update flag 1402 shows that there are two available updates.

FIG. 15 is a block diagram 1500 of an example user interface of the mobile device 100 illustrating the application store after selecting an update tab (e.g., update tab 224). For example, a user may access the application store display object 132 using the touch-sensitive display 102 (e.g., by pressing the application store display object 132), resulting in a transition to the application store interface. In some implementations, touching the application store display object 132 in FIG. 1 causes an animated transition to the application store interface.

The display portion 1502 displays an update interface 1503 associated with the update tab 224, which is highlighted in the display portion 236. Update interface 1503 includes a title bar 1501 that identifies the user interface as an update interface. The title bar 1501 also includes a selectable back button 1504. A back button 1504 allows the user to exit the update interface 1503 or application store and return to the previous user interface. Alternatively, by pressing button 120, the user can exit the application store and return to the "main menu" interface shown in FIG. 1.

Update interface 1503 includes update objects 1540. Specifically, two update objects 1506 and 1508 are shown in update interface 1503, which correspond to the number of updates identified by update flag 1402 in FIG. 14. In some other implementations, there are more update objects 1540 that can be displayed within the display portion 1502. When there are more additional update objects 1540 that can be displayed, the user can scroll to view the additional update objects. Additionally, in some implementations, the user may be provided with a button to allow the user to view another set of update objects (e.g., the next25 update objects) after scrolling or when no scrolling is required.

In some implementations, the update object 1540 identifies specific updates that are available to applications that have been installed on the mobile device 100. For example, update object 1506 identifies an update to "application A" and update object 1508 identifies an update to "application B". The user may select a particular update object (e.g., by touching the update object or an associated update button 1514). Selecting the update object may indicate an update download. Alternatively, selecting the update object may transition update interface 1503 to an information interface that provides additional information about the update, after which the user may decide whether to accept the update. In some implementations, a select all button is provided in the update interface 1503, which allows the user to accept all application updates associated with the displayed update object 1540.

After selecting one or more update objects 1503 for download, the update interface 1503 may end, restore the previous interface or return the user to the main menu screen. Alternatively, when a user selects a particular update object (e.g., update object 1506), the object disappears from update interface 1503 (e.g., only update object 1508 remains).

Fig. 16 is a block diagram 1600 of an example user interface of the mobile device 100 illustrating application download. For example, the user may select a particular application in the application store, e.g., as described above. When the user selects an application object for download, the user interface may transition to a main menu screen that includes display objects 104 and 106 described above with reference to FIG. 1.

In addition, the download object 1602 is presented as one of the display objects 106. The download object presents a dim or shadow object placeholder for the application being downloaded. The download object 1602 is located in the next available position relative to another display object 106. Specifically, the download object includes a "loading. -. (being downloaded)" indicator and a load bar in place of the application title. The load bar may be animated to show the download progress. Once the application download is complete, "loading." changes to the application title, and the image presented within the download object 1602 is modified to correspond to the downloaded application.

FIG. 17 is a flow diagram illustrating an example process 1700 for navigating in an application store using a mobile device. The mobile device is provided with input requesting an application management interface (step 1702). For example, a user may select (e.g., using a touch-sensitive display) an application store object such as that shown in FIG. 1.

An application management interface is presented (step 1704). For example, one or more user interfaces associated with an application store may be presented. The application management interface may include buttons, toggle switches, or other user-activated elements as shown, for example, in fig. 2-15 that allow a user to navigate between different user interfaces, identify and select application objects, and comment and report applications.

Input is received selecting a particular application for installation (step 1706). The input may be received, for example, from a user touching a touch-sensitive display (e.g., touch-sensitive display 102 of fig. 1). For example, a user may search for or identify applications within a presented application management interface or a list provided by the application management interface using different criteria. By touching the displayed application object corresponding to a particular application, the user can select the particular application using the touch sensitive display.

In some other implementations, other user inputs may be received. For example, input may be received to comment on an application, report a problem with an application, notify others of an application, or update a previously installed application.

A determination is made as to whether the selected application requires payment (step 1708). Some applications may be free for any user, while others require payment. If payment is not required, the application is installed on the mobile device (step 1710).

If payment is needed, the payment is selected (step 1712). Payment may be received, for example, by charging a fee from a user account, redeeming a coupon or other credit, or by receiving an electronic payment from a user (e.g., via a credit card). In some implementations, authentication is performed to verify the user.

The application is presented within the main menu screen of the mobile device (step 1714). The application may be presented as an object on the main menu screen. In some implementations, one placeholder object is positioned on the main menu screen (e.g., within the next available location on the main menu screen) while the application is being installed. The placeholder object may be dimmed and include other indications that the application has not yet been made available (e.g., providing loading text). The placeholder object may indicate the progress of the installation (e.g., animated using a load bar).

In some implementations, the application store may include one or more applications that are location specific. For example, a company or other entity may develop and provide applications within a network that are not accessible to others outside the local network. In some other implementations, a parental control may be activated (e.g., using a setting of the mobile device) to limit access to applications or particular types of applications within the application store.

Fig. 18 is a block diagram 1800 of an example user interface for the mobile device 100, showing applications that may be used for deletion. The user may identify applications that are available for deletion, for example, by selecting the display object 106 (e.g., using a touch-sensitive display). For example, a user may touch and hold a display object 106 corresponding to a particular application (e.g., application 1802) for a specified period of time in order to enter an editing mode.

In response to holding the application, the held application and one or more other display objects 106 may become editable (e.g., may be moved to other locations on the touch-sensitive display 102). Some display objects 106 may be deleted. The system may present indicators indicating these display objects in the edit mode, e.g., a flag with an "X" for these display objects that may be deleted. As shown in fig. 18, "application 1" 1802 has a flag indicating that this application can be deleted. The user may select the flag (e.g., by touching an "X" on the touch-sensitive display 102) to initiate the deletion process for the application.

Fig. 19 is a block diagram 1900 of an example user interface of the mobile device 100 illustrating a scoring prompt 1902. When the user selects an application to delete (e.g., application 1802 of fig. 18), a scoring prompt 1902 may be displayed, for example, on a user interface provided by touch-sensitive display 102. In some implementations, portions of the user interface outside of the scoring hints 1902 may be displayed faded relative to the scoring hints 1902.

The scoring hints 1902 can include a request for application reviews, a scoring metric (e.g., a set of asterisks), and one or more buttons (e.g., submit a score or reject a score to an application). The user may provide input (e.g., using the touch-sensitive display 102) indicating a particular score (e.g., by selecting a particular number of asterisks). Once the user has selected a particular number of asterisks, the user may submit a score using, for example, a "score" button. Alternatively, the user may decline to score the application by, for example, selecting the "not, thank you" button.

FIG. 20 is a flow diagram illustrating an example process 2000 for deleting an installed application using a mobile device. An input to delete the installed application is received (step 2002). Input may be received from, for example, a user touching a touch-sensitive display (e.g., touch-sensitive display 102 of FIG. 18). For example, a user may select a particular application and provide input indicating that the selected application should be deleted. In some implementations, the user may enter an edit mode that allows the user to identify applications that may be deleted and select a particular application to delete. In some implementations, when the user selects an application to delete, a confirmation prompt may be presented to the user. The confirmation prompt may indicate that continued operation will delete the application, including any saved data associated with the application. The confirmation prompt may also provide the user with an opportunity to cancel the deletion process.

Scoring cues are presented (step 2004). The scoring prompt may be presented prior to completing deletion of the selected application. The scoring prompt allows the user to provide feedback for the application being deleted. For example, the user may enter a score for the application (e.g., by selecting a particular number of asterisks).

A determination is made as to whether the user scored the application (step 2006). The determination may be made based on one or more user inputs. For example, based on whether the user has entered a rating, or selected a button indicating that a rating has been provided. Alternatively, the user input may indicate that no rating is being provided. For example, the user may select a button indicating that no rating is being provided.

If it is determined that a score has been provided, the scoring information is sent to a remote location (step 2008). For example, the scoring information may be sent to an application store (e.g., the application store described above) located at a remote location. After sending the rating information, the application may be removed and the user interface may return to the main menu screen or other default interface (step 2010).

If it is determined that a rating has not been provided, the application is removed and the user interface may return to the main menu screen or other default interface (step 2010).

Network operating environment

Fig. 21 is a block diagram of an example network operating environment 2100 for the mobile device 100 of fig. 1. The mobile device 100 of fig. 1 can communicate over one or more wired and/or wireless networks 2110, for example, in data communication. For example, a wireless network 2112, e.g., a cellular network, may communicate with a Wide Area Network (WAN)2114, such as the internet, using a gateway 2116. Similarly, an access point 2118, such as an 802.11g wireless access point, may provide communication access to the wide area network 2114. In some implementations, both voice and data communications can be established over the wireless network 2112 and the access point 2118. For example, the mobile device 100a may place and receive phone calls (e.g., using VoIP protocols), send and receive email messages (e.g., using POP3 protocols), and retrieve electronic documents and/or streams, such as web pages, photographs, and videos, over the wireless network 212, the gateway 2116, and the wide area network 2114 (e.g., using TCP/IP or UDP protocols). Similarly, the mobile device 100b may place and receive phone calls, send and receive email messages, and retrieve electronic documents over the access point 2118 and the wide area network 2114. In some implementations, the mobile device 100 can be physically connected to the access point 2118 using one or more cables, and the access point 2118 can be a personal computer. In such a configuration, the mobile device 100 may be referred to as a "tethered" device.

The mobile devices 100a and 100b may also establish communication by other means. For example, the mobile device 100a may communicate with other wireless devices, such as other mobile devices 100, cellular telephones, etc., over the wireless network 2112. Similarly, mobile devices 100a and 100b can communicate through the use of one or more communication subsystems, such as Bluetooth as shown in FIG. 1^TMThe communication device 188 establishes peer-to-peer communication 2120, such as a personal area network. Other communication protocols and topologies may also be implemented.

The mobile device 100 may communicate with one or more services 2130, 2140, 2150, and 2160 and/or one or more content publishers 2170, e.g., over one or more wired and/or wireless networks 2110. For example, the navigation service 2130 may provide navigation information, such as map information, location information, route information, and other information to the mobile device 100. In the illustrated example, the user of mobile device 100b has invoked a map function, for example by pressing map object 144 on the top-level graphical user interface shown in FIG. 1, and has requested and received a map of location "1 InfiniTiLoop, Cupertino, CA.".

The messaging service 2140 may, for example, provide email and/or other messaging services. The media service 2150 may, for example, provide access to media files, such as song files, movie files, video clips, and other media data. Mobile device 100 may also utilize one or more other services 2160.

The mobile device 100 can also access other data and content over the one or more wired and/or wireless networks 2110. For example, the mobile device 100 may access an application store 2170 to provide applications. Such access may be provided by invoking a web browsing function or application (e.g., a browser) in response to a user touching a web object on a main menu screen of mobile device 100.

Example Mobile device architecture

Fig. 22 is a block diagram 2200 of an example implementation of the mobile device 100 of fig. 1. The mobile device 100 may include a memory interface 2202, one or more data processors, image processors and/or central processing units 2204, and a peripherals interface 2206. Memory interface 2202, one or more processors 2204, and/or peripherals interface 2206 can be separate components or can be integrated within one or more integrated circuits. Various components in the mobile device 100 may be coupled by one or more communication buses or signal lines.

Sensors, devices, and subsystems can be coupled to peripherals interface 2206 to facilitate multiple functions. For example, the motion sensor 2210, the light sensor 2212, and the proximity sensor 2214 may be coupled to the peripherals interface 2206 to implement the orientation, lighting, and proximity functions described with reference to fig. 1. Other sensors 2216 may also be connected to the peripheral interface 2206, such as a positioning system (e.g., GPS receiver), temperature sensor, biometric sensor, or other sensing device, to facilitate related functions.

Camera subsystem 2220 and optical sensor 2222, such as a Charge Coupled Device (CCD) or Complementary Metal Oxide Semiconductor (CMOS) optical sensor, may be used to facilitate camera functions, such as recording photographs and video clips.

Communication functions may be facilitated by one or more wireless communication subsystems 2224, which may include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. The particular design and implementation of wireless communication subsystem 2224 may be dependent upon one or more communication networks on which mobile device 100 is intended to operate. For example, the mobile device 100 may include a network designed to operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, and Bluetooth^TMA communication subsystem 2224 operating on a network. In particular, wireless communication subsystem 2224 may include a host protocol such as base station that device 100 may be configured for other wireless devices.

Audio subsystem 2226 may be coupled to speaker 2228 and microphone 2230 to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions.

The I/O subsystem 2240 may include a touchscreen controller 2242 and/or one or more other input controllers 2244. A touch screen controller 2242 may be coupled to the touch screen 2246. The touch screen 2246 and touch screen controller 2242 may, for example, detect contact and movement or break of contact using any of a number of touch sensitive technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 2246.

One or more other input controllers 2244 may be coupled to other input/control devices 2248, such as one or more buttons, rocker switches, a thumb wheel, an infrared port, a USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) may include up/down buttons for volume control of the speaker 2228 and/or microphone 2230.

In one implementation, pressing the button for a first duration may unlock the touch screen 2246; and pressing the button for a second duration that is longer than the first duration may turn power to the mobile device 100 on or off. The user may be enabled to customize the functionality of one or more buttons. The touch screen 2246 may also be used, for example, to implement virtual or soft buttons and/or a keyboard.

In some implementations, the mobile device 100 can present recorded audio and/or video files, such as MP3, AAC, and MPEG files. In some implementations, the mobile device 100 may include an MP3 player such as an iPod^TMThe function of (c). Thus, the mobile device 100 may include an iPod^TMCompatible 32 pin connectors. Other input/output and control devices may also be used.

Memory interface 2202 can be coupled to memory 2250. The memory 2250 may include high-speed random access memory and/or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and/or flash memory (e.g., NAND, NOR). The memory 2250 may store an operating system 2252, such as Darwin, RTXC, LINUX, UNIX, OSX, WINDOWS, or an embedded operating system such as VxWorks. The operating system 2252 may include instructions for handling basic system services and for performing hardware related tasks. In some implementations, the operating system 2252 may be a kernel (e.g., UNIX kernel).

Memory 2250 may also store communication instructions 2254 to facilitate communications with one or more additional devices, one or more computers, and/or one or more servers. Memory 2250 may include graphical user interface instructions 2256 to facilitate graphical user interface processing, including presentation, navigation, and selection within an application store as shown in fig. 2-16; sensor processing instructions 2258 to facilitate sensor-related processing and functions; telephone instructions 2260 to facilitate telephone-related processing and functions; electronic messaging instructions 2262 to facilitate electronic messaging-related processes and functions; web browsing instructions 2264 to facilitate network browsing-related processes and functions; media processing instructions 2266 to facilitate media processing-related processes and functions; GPS/navigation instructions 2268 to facilitate GPS and navigation related processing and instructions; camera instructions 2270 to facilitate camera-related processing and functions; and/or other software instructions 2272 to facilitate other processes and functions.

Each of the instructions and applications identified above may correspond to a set of instructions for performing one or more functions described above. The instructions need not be implemented as separate software programs, procedures or modules. Memory 2250 may include additional instructions or fewer instructions. In addition, various functions of the mobile device 100 may be implemented in hardware and/or software, including one or more signal processing and/or application specific integrated circuits.

Embodiments of the invention and all of the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the invention can be implemented as one or more computer program products; i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more of them. The term "data processing apparatus" includes all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.

A computer program (also known as a program, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memories for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magneto-optical disks, or optical disks. However, the computer need not have these devices. Additionally, a computer may be embedded in another device, e.g., a mobile phone, a Personal Digital Assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, to name a few. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the invention can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other types of devices may also be used in order to provide for interaction with a user; for example, feedback provided to the user can be any form of sensor feedback, such as visual feedback, acoustic feedback, or tactile feedback; and input from the user may be received in any form, including acoustic, speech, or tactile input.

Embodiments of the invention can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the invention, or any combination of one or more such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network ("LAN") and a wide area network ("WAN"), such as the Internet.

The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

While this specification contains many specifics, these should not be construed as limitations on the scope of the invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of the invention. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. In addition, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a self-combination or a variation of a self-combination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Moreover, the division of various system components in the embodiments described above should not be considered as requiring such division in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Thus, particular embodiments of the invention have been described. Other embodiments are within the scope of the following claims. For example, the operations recited in the claims can be performed in a different order and still achieve desirable results.

Claims

1. A method for application management, comprising:

receiving, on a mobile device, a touch input to a first display object in a graphical user interface, the first display object associated with an application management interface on the mobile device;

in response to the received touch input, presenting the application management interface, the application management interface including a plurality of user-activated elements, wherein each user-activated element is associated with different criteria for presenting application objects corresponding to respective applications available for installation on the mobile device from an application store;

presenting a set of application objects within the application management interface according to criteria for a particular user-activated element of the plurality of user-activated elements, the set of application objects corresponding to respective applications available for installation on the mobile device;

presenting a plurality of interface elements, wherein each of the plurality of interface elements is associated with additional criteria for presenting application objects corresponding to a respective application available for installation;

detecting selection of a particular interface element of the plurality of interface elements; and

in response to detecting selection of a particular interface element of the plurality of interface elements, presenting a subset of application objects within the application management interface according to additional criteria for the particular interface element of the plurality of interface elements, the subset of application objects corresponding to respective applications available for installation on the mobile device.

2. The method of claim 1, wherein presenting an application management interface further comprises presenting a menu portion and a display portion.

3. The method of claim 2, wherein the display portion includes one or more application objects corresponding to respective applications, each application object presenting information about the respective application.

4. The method of claim 1, further comprising:

receiving one or more inputs within the application management interface including an input to install a particular application, wherein receiving the one or more inputs includes receiving a selection of a particular application object corresponding to the particular application;

installing the specific application; and

the specific application is presented.

5. The method of claim 4, further comprising:

presenting additional information about the particular application in response to the selection of the particular application object corresponding to the particular application.

6. The method of claim 5, wherein presenting additional information about the particular application comprises presenting one or more comments to the particular application.

7. The method of claim 4, wherein the particular application object is an application update object associated with an update of an application previously installed on the mobile device.

8. The method of claim 4, wherein installing the particular application comprises presenting a placeholder object on a display of the mobile device, the placeholder object comprising an indicator of an installation process.

9. The method of claim 1, further comprising:

payment information for purchasing a particular application is received from a user.

10. A system for application management, comprising:

means for receiving, on a mobile device, a touch input to a first display object in a graphical user interface, the first display object associated with an application management interface;

means for presenting the application management interface in response to the received touch input, the application management interface comprising a plurality of user-activated elements, wherein each user-activated element is associated with different criteria for presenting application objects corresponding to a respective application available for installation on the mobile device from an application store;

means for presenting a set of application objects within the application management interface according to the criteria for a particular user-activated element of the plurality of user-activated elements, the set of application objects corresponding to respective applications available for installation on a mobile device;

means for presenting a plurality of interface elements, wherein each of the plurality of interface elements is associated with additional criteria for presenting application objects corresponding to a respective application available for installation; and

means for detecting selection of a particular interface element of the plurality of interface elements; and

means for presenting, in response to detecting selection of a particular interface element of the plurality of interface elements, a subset of application objects within the application management interface according to additional criteria for the particular interface element of the plurality of interface elements, the subset of application objects corresponding to respective applications available for installation on the mobile device.

11. The system of claim 10, wherein presenting the application management interface further comprises presenting a menu portion and a display portion.

12. The system of claim 11, wherein the display portion includes one or more application objects corresponding to respective applications, each application object presenting information about the respective application.

13. The system of claim 10, further comprising:

means for receiving one or more inputs within the application management interface including an input to install a particular application, wherein the means for receiving the one or more inputs includes means for receiving a selection of a particular application object corresponding to the particular application;

means for installing the specific application; and

means for presenting the particular application.

14. The system of claim 13, further comprising:

means for presenting additional information about the particular application in response to the selection of the particular application object that corresponds to the particular application.

15. The system of claim 14, wherein presenting additional information comprises presenting one or more comments to the particular application.

16. The system of claim 13, wherein the particular application object is an application update object associated with an update of an application previously installed on the mobile device.

17. The system of claim 13, wherein installing the particular application comprises presenting a placeholder object on a display of the mobile device, the placeholder object comprising an indicator of an installation process.

18. The system of claim 10, further comprising:

means for receiving payment information from a user for purchasing a particular application.