User interface for application management for mobile device

The present invention relates to a user interface of a mobile device.

Traditional mobile devices often perform specific functions exclusively. For example, mobile phones provide telephone services, personal digital assistants (PDAs) provide a means of organizing addresses, contacts and notes, media players play content, and e-mail devices e-mail. -Provide email communication, a browser for surfing the Internet, etc. Modern mobile devices can include two or more of these functions.

More specifically, the mobile device can include a number of different applications that the user can access independently of other applications. For example, a mobile device can include one or more games, web applications, or production applications.

This specification describes techniques for user interfaces for mobile devices. In general, one aspect of the gist described herein is application management, including input to receive touch input to access an application management interface on a mobile device, present an application management interface, and install a particular application. It can be done in a way that involves receiving one or more inputs in the interface, installing the selected application, and presenting the installed application. Other embodiments of this aspect include corresponding systems, devices and computer program products.

These and other embodiments may optionally include one or more of the following features: Presenting an application management interface further includes presenting a menu portion and a display portion. The display portion includes one or more application objects corresponding to each application, and each application object presents information about each application. The menu portion contains multiple tabs, each giving access to specific features of the application management interface. Receiving one or more user inputs involves receiving a selection of a particular application object. The method also comprises migrating the display portion to present additional information about the selected application in response to the selection. Presenting additional information involves presenting one or more critiques of the selected application. The selected application object is an application update object associated with an update to an application previously installed on the mobile device. Installing the selected application involves presenting a placeholder object on the display of the mobile device, which contains an indicator of installation progress. The method also comprises receiving payment information from the user to purchase a particular application. The mobile device is equipped with a multi-touch sensing display.

In general, one aspect of the gist described herein comprises a processor and a user interface that provides interaction with the user, the user interface being a display containing one or more application objects corresponding to each application. A part that can be implemented in a system that includes a display part where each application object presents information about each application and a menu part that contains multiple tabs, each giving access to specific features of the application management interface. it can. Other embodiments of this aspect include corresponding methods, devices and computer program products.

Certain embodiments of the present invention can be implemented to achieve one or more of the following effects: Users can easily navigate the application store to identify and download applications for mobile devices. Users can be notified of updates to previously downloaded applications without navigating to the update interface. Users can quickly give feedback about the application, including rating the application and reporting identified issues. In addition, users can quickly and easily share information about specific applications of interest with other users. Selecting an application allows the user to access other features and applications of the mobile device while waiting for the application to be downloaded.

One or more embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Other features, aspects and effects of the present invention will become apparent from the following description, accompanying drawings and claims.

<figref num="1">It is a block diagram of a normative mobile device.</figref><figref num="2">It is a block diagram of the normative user interface of the mobile device after calling the application store display object.</figref><figref num="3">It is a block diagram of the normative user interface of the mobile device after selecting the staff favorite button.</figref><figref num="4">It is a block diagram of the normative user interface of a mobile device for giving information related to a specific application.</figref><figref num="5">It is a block diagram of the normative user interface of a mobile device for notifying another user of an application.</figref><figref num="6">FIG. 6 is a block diagram of the normative user interface of a mobile device, including menus that provide information related to the selected application.</figref><figref num="7">It is a block diagram of the normative user interface of a mobile device for criticizing a selected application.</figref><figref num="8">FIG. 6 is a block diagram of a mobile device normative user interface for reporting on selected applications.</figref><figref num="9">FIG. 6 is a block diagram of a mobile device normative user interface exemplifying an application store following a category tab selection.</figref><figref num="10">FIG. 1000 is a block diagram 1000 of the normative user interface of the mobile device 100 illustrating an application object of a particular category selected.</figref><figref num="11">FIG. 6 is a block diagram of a mobile device normative user interface exemplifying an application store following a selection on the Top 25 tab.</figref><figref num="12">It is a block diagram of the normative user interface of a mobile device exemplifying the application store "Top 25" in which free applications are hidden.</figref><figref num="13">FIG. 6 is a block diagram of a mobile device normative user interface illustrating an application store following a search tab selection.</figref><figref num="14">FIG. 6 is a block diagram of a mobile device normative user interface illustrating available updates after invoking an application store display object.</figref><figref num="15">FIG. 6 is a block diagram of a mobile device normative user interface exemplifying an application store following an update tab selection.</figref><figref num="16">It is a block diagram of the normative user interface of a mobile device exemplifying an application download.</figref><figref num="17">It is a flowchart which illustrates the normative process of navigating an application store using a mobile device.</figref><figref num="18">FIG. 6 is a block diagram of a mobile device normative user interface illustrating an available application for deletion.</figref><figref num="19">FIG. 6 is a block diagram of a mobile device normative user interface exemplifying a rating prompt.</figref><figref num="20">It is a flowchart which illustrates the normative process for removing an installed application using a mobile device.</figref><figref num="21">It is a block diagram of the normative network operating environment for the mobile device of FIG.</figref><figref num="22">It is a block diagram of the normative embodiment of the mobile device of FIG.</figref>

In the various accompanying drawings, the same elements are designated by the same reference number and designation.

FIG. 1 is a block diagram of the normative mobile device 100. The mobile device 100 includes, for example, a handheld computer, a personal digital assistant, a cellular phone, a network device, a camera, a smartphone, an enhanced general line radio service (EGPRS) mobile phone, a network base station, a media player, a navigation device, an e-mail device. , A game console, or a combination of two or more of these data processing devices or other data processing devices.

<u style="single">Outline of mobile device</u> In certain embodiments, the mobile device 100 comprises a touch-sensitive display 102. The touch-sensitive display 102 can implement liquid crystal display (LCD) technology, luminescent polymer display (LPD) technology, or other display technology. The touch-sensitive display 102 can sense tactile and / or tactile contact with the user.

In certain embodiments, the touch-sensitive display 102 can include a multi-touch-sensitive display 102. The multi-touch sensing display 102 can process a plurality of simultaneous touch points, including processing data related to pressure, angle and / or position of each touch point, for example. Such processing facilitates multiple finger gestures and finger interactions, chording, and other interactions. Other touch-sensitive display technologies can also be used, such as displays that make contact using a stylus or other pointing device. Some examples of multi-touch sensitive display technology are described in US Pat. Nos. 6,323,846, 6,570,557, 6,677,932, and US Patent Publication No. 2002/0015024A1.

In certain embodiments, the mobile device 100 can display one or more graphic user interfaces on the touch-sensitive display 102 to provide user access to various system objects and to carry information to the user. In certain embodiments, the graphic user interface can include one or more display objects 104, 106. In the example shown here, display objects 104 and 106 are graphic representations of system objects. System objects include, for example, device functions, devices, windows, files, alerts, events, or other identifiable system objects.

<u style="single">Normative mobile device function</u> In certain embodiments, the mobile device 100 is a telephone device designated by telephone object 110, an e-mail device represented by e-mail object 112, a network data communication device represented by web object 114, and Wi-Fi based. Multiple device functions such as the station device (not shown) and the media processing device shown in the media player object 116 can be performed. In certain embodiments, specific display objects 104, such as the telephone object 110, the e-mail object 112, the web object 114, and the media player object 116, can be displayed in the menu bar 118. In certain embodiments, device functions can be accessed from a top-level graphic user interface, such as the graphic user interface shown in FIG. Touching one of the objects 110, 112, 114 or 116 can, for example, call the corresponding function.

In certain embodiments, the mobile device 100 can perform a network distribution function. For example, this function allows a user to carry a mobile device 100 and access its associated network while traveling. In particular, the mobile device 100 can extend Internet access (eg, Wi-Fi) to other wireless devices in its vicinity. For example, the mobile device 100 can be configured as a base station for one or more devices. Therefore, the mobile device 100 can allow or deny network access to other wireless devices.

In certain embodiments, when invoking a function of the device, the graphic user interface of the mobile device 100 is altered, augmented, or augmented to facilitate user access to a particular function associated with the corresponding device function. Replaced by another user interface or user interface element. For example, in response to a user touching a phone object, the graphic user interface of the touch-sensitive display 102 presents display objects associated with various phone functions, as well as touching the e-mail object 112. Causes the graphic user interface to present display objects associated with various e-mail functions, and touching web object 114 causes the graphic user interface to present display objects associated with various web surfing functions. Touching the media player object then causes the graphic user interface to present display objects associated with various media processing functions.

In certain embodiments, the top-level graphic 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 certain embodiments, each corresponding device function has a corresponding "home" display object displayed on the touch-sensitive display 102, and by pressing this "home" display object, the graphic user interface environment of FIG. Can be recovered.

In one embodiment, the top-level graphic user interface is an additional display object 106, such as a short messaging service (SMS) object, calendar object, photo object, camera object, calculator object, stock object, weather object, map object. It can include 144, memo objects, clock objects, address book objects, configuration objects, and application store objects 132. For example, touching an SMS display object can call the SMS messaging environment and support environment, and similarly, selecting each display object can call the corresponding object environment and function.

The graphic user interface of FIG. 1 can also display additional and / or different display objects. For example, if device 100 acts as a base station for other devices, one or more "connection" objects will appear in the graphic user interface to direct the connection. In certain embodiments, the display object 106 can be configured by the user, for example, the user can specify which display object 106 is to be displayed, and / or other functions and their corresponding display objects. You can download additional applications or other software that gives you.

In certain embodiments, 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 can be included to facilitate voice enable functions such as telephone and voice mail functions. In certain embodiments, an up / down button 184 for volume control of the speaker 160 and the microphone 162 can be included. The mobile device 100 may also include an on / off button 182 for an incoming / outgoing ring indicator. In certain embodiments, a speaker 164 can be included to facilitate a hands-free voice function, such as a speaker telephone function. An audio jack 166 can be included for use with headphones and / or microphones.

In one embodiment, the user can easily detect that the mobile device 100 is located near the user's ear, and in response, dissociate the touch-sensitive display 102 to prevent accidental function calls. , The proximity sensor 168 can be included. In certain embodiments, the touch-sensitive display 102 can be turned off to store additional power when the mobile device 100 is near the user's ear.

Other sensors can also be used. For example, in certain embodiments, the ambient light sensor 170 can be used to easily adjust the brightness of the touch-sensitive display 102. Also, in certain embodiments, the accelerometer 172 can be used to detect the movement of the moving device 100, as indicated by the directional arrow 174. Thus, display objects and / or media can be presented based on detected orientations, such as portraits or landscapes. In some embodiments, the mobile device 100 is provided by a Global Positioning System (GPS) or other positioning system (eg, a system that uses a Wi-Fi access point, television signal, cellular grid, uniform resource locator (URL)). Circuits and sensors may be provided to support such positioning capabilities. In certain embodiments, a positioning system (eg, a GPS receiver) can be integrated into the mobile device 100, or it can be provided as a separate device and coupled to the mobile device 100 via an interface (eg, port device 190). You can also access location-based services.

The mobile device 100 may also include a camera lens and a sensor 180. In certain embodiments, the camera lens and sensor 180 can be located on the back of the mobile device 100. The camera can capture still footage and / or video.

The mobile device 100 may also include one or more wireless communication subsystems such as 802.11b / g communication device 186 and / or Bluetooth® communication device 188. Also, other 802.x communication protocols (eg WiMax, Wi-Fi, 3G), code split multiplex access (CDMA), global systems for mobile communications (GSM®), enhanced data GSM environment (EDGE), It can also support other communication protocols, including.

In certain embodiments, port devices 190, such as universal serial bus (USB) ports, or docking ports, or other wired port connections can also be included. The port device 190 establishes a wired connection to 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. Can be used for. In certain embodiments, the port device 190 allows the mobile device 100 to synchronize with the host device using one or more protocols, such as TCP / IP, THHP, UDP and other known protocols. To do. In one embodiment, TCP, as described in U.S. Patent Application No. 11 / 770,691 entitled "Multiplexed Data Stream Protocol" filed June 28, 2007, and later U.S. Patent Application Publication No. 20080304486. / IP over USB protocol can be used.

FIG. 2 is a block diagram 200 of the normative user interface of the mobile device 100 after calling the application store display object (app store display object 132 in FIG. 1). For example, the user can use the touch-sensitive display 102 (eg, by pressing the app store display object 132) to access the app store display object 132 and cause a transition to the application store interface. In one embodiment, touching the app store display object 132 in FIG. 1 results in an animated transition to the application store interface.

The user interface for the application store includes a display portion 236 and a menu portion 226. The menu portion 226 can include a large number of tabs. In particular, the menu portion 226 includes a characterized tab 216, a category tab 218, a top 25 tab 220, a search tab 222, and an update tab 224. Each of the tabs in menu part 226 can be used to access different features of the application store, each of which is described in detail below. In some embodiments, other tabs may be provided and / or the order of the tabs may be changed, for example, as determined by the application store, mobile device, or based on input received from another remote location. can do.

The display portion 236 displays the characterization interface 203 associated with the characterization tab 216 shown as a highlight in the display portion 236. The characterization interface 203 includes a title bar 201. The title bar 201 includes a Recently Added button 202 and a Staff Favorites button 204. These recently added buttons 202 and staff favorite buttons 204 are shown as separate buttons. However, these buttons can take other forms, including, for example, a single toggle button that can be switched from one to the other by touching the button more than once.

The characterization interface 203 also includes one or more application objects 240. The recently added button 202 is shown as currently selected (eg, 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 recently added application in the application store.

In certain embodiments, recently added applications are specified by the time period from when the particular application was included in the application store. For example, recently added applications include applications that are available in the app store within the last 30 days. However, in some embodiments, the recently added application is the most recently added number of applications (eg, 25) to the application store, regardless of the actual elapsed time.

Application objects 240 can be ordered within display portion 236 based on one or more criteria. For example, application objects can be ordered based on date order, alphabetical order, or user rating added to the application store.

In particular, the application object 240 shown in display portion 236 includes application objects 210, 212 and 214. Further, when the display portion 236 cannot display all the application objects 240 at one time, the user can scroll (238) up or down to see the additional application objects 240. The scroll 238 is indicated by a dotted arrow at a specific portion of the display portion 236, but the user can also scroll (238) from another point. In particular, the user can scroll across the touch-sensitive display 102 by gesturing in a particular direction (eg, up or down).

Each application object 240 contains information related to a particular application. For example, application object 210 contains application information 228. The application information 228 can include a video representing the application, an application name (eg, "application 1" for the application object 210), a developer name, and rating information. In certain embodiments, the rating information is represented by a specified number of stars. The stars are filled to indicate the average rating for the application (for example, 3 out of 5). In some embodiments, the stars are partially filled to represent the finer grain size of the average rating.

In other embodiments, different symbols are used to represent the rating information. For example, in some embodiments, small dots are used to represent unselected stars, which are replaced with stars up to the rating level so that there are only stars equal to the average rating. Also, in certain embodiments, the rating information includes a number of criticisms used to determine the average rating (eg, from individual users).

The application object 240 also includes purchase information 230. Purchase information indicates whether the application is free or must be purchased (eg, identified by a "free" or "purchase" label). In some embodiments, the purchase information dictates the cost of the application (eg, $ 5.00). In other embodiments, the application object 240 can indicate whether the user has already installed a particular application. For example, if the user has already installed the application identified by the application object 210, the purchase information 230 can be read as "installed" instead of "free". Alternatively, the purchase information 230 can be read as "uninstall", which indicates that the user can uninstall the already installed application.

The application object 240 can also include a "&gt;" directive (eg, the directive 232 of the application object 210). This directive 232 directs that when a particular application object is selected (eg, by touching the application object 210), the user interface is migrated to give additional information about the selected application. The transition can be animated.

Also, the display portion 236 can include one or more advertisements. In the display portion 236, the first advertisement 206 and the second advertisement 208 are shown in the vicinity of the title bar 201. In other embodiments, only a single ad is presented. Alternatively, additional advertisements can be presented. Further, one or more advertisements can be presented at different positions of the display portion 236 while the advertisements are displayed near the title bar 201.

FIG. 3 is a block diagram 300 of the normative user interface of the mobile device 100 after selecting the staff favorite button (eg, staff favorite button 204 in FIG. 2). As shown in FIG. 2, the title bar 201 includes both the recently added button 202 and the staff favorite button 204. When the staff favorite button 204 is selected, the display portion 236 presents the application object 340 as part of the characterization interface 303. The application object 340 may include one or more of the recently added application objects 240, or may be separate from the application object 240.

In one embodiment, application object 340 represents an application object selected by one or more individuals associated with an application store. For example, staff favorites can be selected by a group of individuals within a specified time period. Therefore, staff favorites can change on a regular basis, for example, every 30 days. In other embodiments, staff favorites are identified based on an application that receives the highest rating from a designated group of individuals. In certain embodiments, the number of application objects 340 identified as staff favorites is limited to a specified number (eg, the top 25 applications).

Application objects 340 can be ordered within characterization interface 303 by one or more criteria. For example, application objects can be ordered by date, alphabetical, or staff rating as they are added to the application store.

In particular, the application object 340 shown in display portion 236 includes application objects 302, 304 and 306. Further, when the display portion 236 cannot display all the application objects 340 at one time, the user scrolls up or down (238) to see the additional application objects 340 as described above with reference to FIG. )can do.

Each application object 340 contains information associated with each application. Similar to the application information 228 described above with reference to FIG. 2, the application information may include a video representing the application, an application name (eg, "application 4" for application object 302), a developer name, and rating information. it can. In certain embodiments, the rating information is represented by a specified number of stars indicating the average rating of the corresponding application.

The application object 340 also includes purchase information. The purchase information indicates whether the "Staff Favorites" application is free or must be purchased. In certain embodiments, the purchase information dictates the cost of a particular application (eg, $ 5.00). In other embodiments, the application object 340 can indicate whether the user has already installed a particular application. For example, if the user has already installed the application identified by application object 302, the purchase information can be read as "installed" instead of "free". Alternatively, the purchase information can be read as "uninstall", which indicates that the user can uninstall the already installed application.

The application object 340 can also include a "&gt;" specifier (eg, specifier 232 in FIG. 2). This directive directs that when a particular application object is selected (eg, by touching the application object 302), the user interface is migrated to give additional information about the selected application. The transition can be animated.

The characterization interface 303 can also include one or more advertisements. In particular, the display portion 236 presents the first advertisement 206 and the second advertisement 208 in the vicinity of the title bar 201. In other embodiments, only a single ad is presented. Alternatively, additional advertisements can be presented. Further, one or more advertisements can be presented at different positions of the display portion 236 while the advertisements are displayed near the title bar 201.

In each of FIG. 2 or FIG. 3, when a user selects an application object (eg, either application object 240 or 340), the user interface will provide additional information about the application associated with that selected application object. Can be migrated to.

FIG. 4 is a block diagram 400 of the normative user interface of the mobile device 100 for providing information relevant to a particular application. In particular, the application information interface 403 corresponds to the user selection of the application object 210 in FIG.

The application information interface 403 includes an information display portion 410 and a menu portion 226. The menu portion 226 includes a characterization tab 216, a category tab 218, a top 25 tab 220, a search tab 222 and an update tab 224. In some embodiments, the menu portion 226 is hidden when the application information interface 403 is presented.

The display portion 410 includes a title bar 401. The title bar 401 identifies the user interface as an application information interface. In addition, the title bar 401 can include a back button 402 and a "tell a friend" 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 (eg, the user interface for the application store shown in FIG. 2 or 3). The "tell a friend" button 404 allows the user to send information about the selected application. In particular, touching the "tell a friend" button 404 transitions the user interface to an interface for notifying another individual about a particular application. The interface for notifying another individual about the selected application is described in detail below with reference to Figure 5.

The display portion 410 also includes application information 406, purchase information 408, application screenshot 412, and critique 414. The application information 406 includes, for example, the application name and the developer. The application information 406 can also include video representing a particular application and 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.

Purchase information 408 identifies whether the selected application is free or available for purchase. Alternatively, the purchase information 408 can also indicate the price of the application (eg, $ 5.00). In certain embodiments, the user can purchase the application in exchange for credit. For example, a user may have a gift card, coupon or other credit that can be used to purchase an application at the app store. In one embodiment, a "redeem" button is presented to the user in the application interface. Touching this redemption button creates an interface that allows the user to enter account information corresponding to the credits applied.

Further, in one embodiment, touching purchase information 408 initiates the process for downloading the application. For example, if the application is free, the download process can be initiated without further user input. Alternatively, if a purchase is required, the user account can be accessed to purchase the application. In certain embodiments, the user can purchase the application in exchange for a coupon or similar credit. In other embodiments, the user is required to provide an account or other credentials before purchasing the application.

In another embodiment, the purchase information 408 indicates whether the user has already installed the application (eg, by including the text "installed" or "uninstall" in the purchase information 408).

Screenshot 412 can provide a screen capture image of the application interface. In certain embodiments, a detailed description of the application is given in lieu of or in addition to screenshot 412. For example, the detailed description can include application features and other information. In one embodiment, two or more screenshots 412 are given. Alternatively, in other embodiments, additional screenshots can be provided as thumbnails that can be displayed when selected by the user.

Criticism 414 includes application rating information and individual critiques. Rating information can include a graphic representation of the average rating (eg, using a star rating). In addition, the number of individual criticisms used to determine the average rating can be given. The average rating is followed by one or more individual critiques of the application. In one embodiment, all criticisms are listed. In other embodiments, only a specified number of criticisms are listed. In certain embodiments, the user can scroll (238) to see additional critiques that are not presented within the visible portion of application information interface 403.

The critique 414 portion of the application information interface 403 may also include a critique button 418 that allows the user to give critiques or other reports related to the application. Giving a critique of the application is explained below with reference to Figures 6-8.

FIG. 5 is a block diagram 500 of the normative 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 can be presented in response to the user selecting the "tell a friend" button 404 in FIG.

The notification interface 502 includes a title bar 501. The title bar 501 identifies the notification interface 502 (eg, as "tell a friend"). Further, the title bar 501 includes a back button 504 and a submit button 506. The back button 504 cancels the notification interface 502 and allows the user to return to the previous user interface (eg, application information interface 403). The submit button 506 allows the user to submit application information to another individual.

Notification interface 502 can provide preconfigured e-mail messages containing links to application information in the application store. The notification interface 502 includes a "destination" field 508, a "source" 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 can enter, for example, an e-mail address or name corresponding to a contact or address book entry. The Source field 510 allows the user to identify the sender of the notification to the recipient. In certain embodiments, the "source" field 510 is automatically populated based on user profile or account information. In other embodiments, the "source" field 510 is not presented to the user and is automatically added to the notification. The Subject field 512 allows the user to specify a subject for the recipient, eg, "Check out this application". In certain embodiments, the subject field 512 is automatically populated with the name of the application or other text, for example by the application store.

The text box 514 provides additional space for the user to provide additional text (eg, the message body) to the user. In certain embodiments, the text box 514 has a maximum number of allowed characters for user input.

Input to each field and text box 514 can be given using keyboard 516. Keyboard 516 has a full QWERTY layout of keys for typing. The user inputs text on the touch-sensitive display 102 by touching individual keys based on the desired text. After entering information in one or more fields, the user can send a notification by touching the submit button 506 described above. In one embodiment, sending a notification causes the user interface to transition to the front user interface (eg, application information interface 403).

FIG. 6 is a block diagram 600 of the normative user interface of the mobile device 100, which includes a menu 602 for giving information related to the selected application. In particular, menu 602 can be overlaid on a portion of application information interface 403. Menu 602 is partially transparent so that the overlay portion of application information interface 403 can be partially seen. In one embodiment, the menu 602 is presented in response to the user selecting the critique button 418 of the application information interface 403. In another embodiment, menu 602 is not provided as a partial overlay, but is completely replaced by application information 403.

Menu 602 includes a critique write button 604, a problem report button 606 and a cancel button 608. The write critique button 604 allows the user to write a critique of the application on the application information interface 403. In particular, when the user touches the critique write button 604, the user interface transitions to the critique interface (eg, using animated migration). The critique interface is described in detail below with reference to Figure 7.

The problem report button 606 allows the user to report problems associated with the application shown in the application information interface 403. In particular, when the user touches the problem report button 606, the user interface transitions to the reporting interface (eg, using animated migration). The report interface is described in detail below with reference to Figure 8.

The cancel button 608 allows the user to cancel menu 602 and return to the application information interface 403 of FIG.

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

The critique interface 702 includes a title bar 701 that identifies the interface as a critique interface. The title bar 701 further includes a back button 704 and a submit button 706. The back button 704 cancels the critique interface 702 and allows the user to return to the previous user interface (eg, application information interface 403). The submit button 706 allows the user to submit a critique.

The critique interface 702 includes a rating of 708. Rating 708 allows the user to specify a rating value for the application. For example, the user can specify a specified number of stars to the application from the maximum possible range (eg, stars 0 to 5). In particular, the user can specify the star using gesture motion on the touch-sensitive interface 102. For example, the user slides his or her finger in the first direction to increment the number of stars (up to the maximum number, eg 5, 5), or slides the finger in the second direction to increase the number of stars (up to 5, for example, 5). It can be reduced to a minimum number, eg 0) increments.

The critique interface 702 also includes a "source" field 710, a "title" field 712, and a "criticism text box 714. The" source "field 710 allows the user to identify who gives the critique. In certain embodiments, the "source" field 710 is automatically populated based on user profile or account information. In other embodiments, the "source" field 710 is not presented to the user and is automatically added to the critique. The "Title" field 712 allows the user to identify the profession or qualification to make the critique. In some embodiments, the "Title" field 712 is not provided.

The text box 714 provides additional space for the user to form critique text beyond the rating value. In certain embodiments, the text box 714 has a maximum allowed number of characters for user input.

Input to each field and text box 714 can be given using keyboard 516. Keyboard 516 has a full QWERTY layout of keys for typing. The user inputs text on the touch-sensitive display 102 by touching individual keys based on the desired text. After entering information in one or more fields, the user can submit a critique by touching the submit button 706 described above. In one embodiment, submitting a critique shifts the user interface to the front user interface (eg, application information interface 403).

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

The report interface 802 includes a title bar 801 that identifies the interface as a report interface. The title bar 801 further includes a back button 804 and a submit button 806. The back button 804 cancels the report interface 802, for example, and allows the user to return to the previous user interface (eg, the application information interface 403). Submit button 806 allows the user to submit a report.

The critique interface 802 includes a menu button that suggests a problem to report. In particular, the critique interface 802 includes a bug report button 808, a button 810 that reports discomfort, and a button 812 for unlisted issues. The user can select one of the menu buttons by touching a specific menu button in the critique interface 802. In some embodiments, when the user selects a particular menu button, the selected menu button is highlighted. In another embodiment, when the user selects a menu button, an icon indicating the selection, for example, a check mark, is displayed.

In addition, a text box 814 is presented. Text box 814 allows the user to arbitrarily explain the problem being reported. In certain embodiments, the text box 814 has a maximum allowed number of characters for user input.

Input to text box 814 can be given using keyboard 516. Keyboard 516 has a full QWERTY layout of keys for typing. The user inputs text on the touch-sensitive display 102 by touching individual keys based on the desired text. After entering the information in the text box 814, the user can submit the report by touching the submit button 806 described above. In one embodiment, submitting a report causes the user interface to transition to the front user interface (eg, application information interface 403).

In some embodiments, the keyboard 516 is not presented to the report interface 802 until the user selects the text box 814 (eg, by touching the text box 814).

FIG. 9 is a block diagram 900 of the normative user interface of mobile device 100 exemplifying an application store following the selection of a category tab (eg, category tab 218 of FIG. 2). For example, the user can use the touch-sensitive display 102 (for example, by pressing the application store display object 132) to access the application store display object 132 and migrate to the application store interface. In one embodiment, touching the application store display object 132 in FIG. 1 results in an animated transition to the application store interface.

The user interface for the application store includes a display portion 902 and a menu portion 226. The menu portion 226 can include a large number of tabs. In particular, the menu portion 226 includes a characterization tab 216, a category tab 218, a top 25 tab 220, a search tab 222 and an update tab 224. Each of the tabs in menu part 226 can be used to access different features of the application store.

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

Category interface 903 includes one or more category buttons. In particular, the category interface 903 includes a game button 904, an entertainment button 906, a news button 908, a productivity button 910, a sports button 912, and a travel button 914. The displayed categories can be arranged in any order (eg, alphabetical order, popularity order, etc.). In addition, other categories can be displayed in place of or in addition to the illustrated categories. In certain embodiments, the user can see additional categories by scrolling (238) the category button.

Each category button allows the user to navigate to an interface that gives application objects associated with a particular category. For example, selecting the game button 904 can transition the category interface to a game object interface that contains one or more application objects that correspond to the game or one associated with the game category.

FIG. 10 is a block diagram 1000 of the normative user interface of the mobile device 100 illustrating the selected specific category of application objects. In particular, FIG. 10 shows a game object interface 1003 presented in response to a user's category selection (eg, user selection of game button 904 in FIG. 9).

The user interface includes a display portion and a menu portion 226. Menu portion 226 includes a large number of tabs. In particular, the menu portion 226 includes a characterization tab 216, a category tab 218, a top 25 tab 220, a search tab 222 and an update tab 224. In particular, category tab 218 is shown as a highlighted state.

The display portion 1002 displays the game object interface 1003 related to the selection of the game category. The GameObject Interface 1003 features a title bar 1001 that includes a recently added button 1004 and a staff favorite button 1006. The recently added button 1004 and staff favorite button 1006 are shown as separate buttons, but can take other forms, including, for example, a single toggle button that can be switched from one to the other.

GameObject Interface 1003 also includes one or more GameObjects 1040. The recently added button 1004 is shown as currently selected (eg, based on user input to the touch-sensitive display 102). When the recently added button 1004 is selected, the displayed GameObject 1040 corresponds to a GameApplication recently added to the App Store with respect to the GameObject, similar to that described above with reference to Figure 2. Similarly, when the Staff Favorites button 1006 is selected or toggled, the displayed GameObject 1040 is a game selected by one or more individuals associated with the application store as described above with reference to Figure 2. Corresponds to the application.

Game object 1040 shown in display portion 1002 includes game objects 1012, 1014 and 1016. Further, when the display portion 1002 cannot display all the game objects 1040 at one time, the user can scroll (238) up or down to see the additional game objects 1040.

Each game object 1040 contains information related to a particular game application. For example, the game object 1012 contains game application information 1018. The game application information 1018 can include a video representing a game application, a game application name (game 1), a developer name, and rating information. In certain embodiments, the rating information is represented by a specified number of stars. Stars are filled to indicate the average rating of the game (for example, 3 out of 5). In some embodiments, the stars can also be partially filled to represent the finer grain size of the average rating.

The game object 1040 also includes purchase information 1022. This purchase information 1022 indicates whether the application is free or must be purchased. In some embodiments, the purchase information dictates the cost of the game (eg, $ 5.00). In other embodiments, each game object (eg, game objects 1012, 1014 and 1016) can indicate whether the user has already installed a particular game. For example, if the user has already installed the game identified by GameObject 1012, purchase information 1022 can be read as "installed" instead of "free". Alternatively, the purchase information 122 can be read as "uninstall", which indicates that the user can uninstall the already installed game application.

The game object 1040 can also include a "&gt;" directive 1020. This directive 1020 directs that when a particular game object is selected (eg, by touching the game object 1012), the user interface is migrated to give additional information about the selected game application. The transition can be animated.

Also, the display portion 1002 can include one or more advertisements. In the display portion 1002, the first advertisement 1008 and the second advertisement 1010 are shown in the vicinity of the title bar 1001. In other embodiments, only a single ad is presented. Alternatively, additional advertisements can be presented. Further, one or more advertisements can be presented at different positions on the display portion 1002 while the advertisements are displayed near the title bar 1001.

The user can select a particular game object 1040 and migrate to give information about the game associated with that selected game object. The game information is given in the same manner as the application information interface 403 described above with reference to FIG.

FIG. 11 is a block diagram 1100 of the normative user interface of the mobile device 100 exemplifying an application store following the selection of the "Top 25" tab (eg, "Top 25" tab 220). For example, the user can use the touch-sensitive display 102 (eg, by pressing the app store display object 132) to access the app store display object 132 and cause a transition to the app store interface. In one embodiment, touching the app store display object 132 in FIG. 1 results in an animated transition to the app store interface.

The user interface for the app store includes a display portion 1102 and a menu portion 226. The menu portion 226 can include a large number of tabs. In particular, the menu portion 226 includes a characterization tab 216, a category tab 218, a top 25 tab 220, a search tab 222 and an update tab 224. Each of the tabs in menu part 226 can be used to access different features of the application store.

The display portion 1102 displays the "top 25" interface 1103 associated with the "top 25" tab 220 highlighted in the display portion 236. Top 25 interface 1103 includes a title bar 1101 that identifies the user interface as the top 25 interface. 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 (highlighted in Figure 11), the Top 25 interface 1103 displays application objects 1140, including those related to applications that are available for free. When the "Hide Free" button 1106 is selected, the "Top 25" interface 1103 displays only application objects that require payment.

"Top 25" interface 1103 contains application object 1140. In particular, 25 application objects 1140 are listed. However, when all 25 application objects 1140 cannot be displayed in display portion 1102, the user can scroll (238) to see additional application objects. Further, in one embodiment, when the user scrolls to the bottom of the "top 25" list of application objects, the user may see another group of application objects (eg, "next 25" application objects). Buttons can be provided to allow this.

The illustrated application object 1140 includes application objects 1112, 1114 and 1116. Application objects 1140 are presented in a ranked order. Therefore, application object 1112 ranks above application object 1114. The rank of each application object is identified in the application object. For example, application object 1112 includes a rank identifier 1118 that identifies this application object 1112 as being ranked number one in the list of application objects 1140.

Each application object 1140 contains information related to a particular application. For example, application object 1112 contains application information 1122. The application information 1122 can include a video representing the application, an application name (application 5), a developer name, and rating information. In certain embodiments, the rating information is represented by a specified number of stars. Stars are filled to indicate the average rating of the game (eg 3/5). Also, in some embodiments, the stars may be partially filled to represent the finer grain size of the average rating.

The application object 1140 also includes purchase information 1124. This purchase information 1124 indicates whether the application is free or must be purchased. In some embodiments, the purchase information dictates the cost of the application (eg, $ 5.00). In other embodiments, each application object (eg, application objects 1112, 1114 and 1116) can indicate whether the user has already installed a particular application. For example, if the user has already installed the application identified by application object 1112, the purchase information 1124 can be read as "installed" instead of "free". Alternatively, the purchase information 1124 can be read as "uninstall", which indicates that the user can uninstall the already installed application.

Each application object 1140 can also contain a "&gt;" indicator 1124. This directive 1124 directs that when a particular application object is selected (eg, by touching the application object 1112), the user interface is migrated to give additional information about the selected application. The transition can be animated.

Also, the display portion 1102 can include one or more advertisements. In the display portion 1102, the first advertisement 1108 and the second advertisement 1110 are shown in the vicinity of the title bar 1101. In other embodiments, only a single ad is presented. Alternatively, additional advertisements can be presented. Further, one or more advertisements can be presented at different positions on the display portion 1102 while the advertisements are displayed near the title bar 1101.

Selecting a particular application object in the ranked list of application objects 1140 transitions the user interface to an interface that provides information about the application associated with that selected application object. Application information is given in the same manner as the application information interface 403 described above with reference to FIG.

FIG. 12 is a block diagram 1200 of the normative user interface of the mobile device 100 exemplifying the application store "Top 25" in which free applications are hidden. The application store user interface includes a display portion 1202 and a menu portion 226. The menu portion 226 can include a large number of tabs. In particular, the menu portion 226 includes a characterization tab 216, a category tab 218, a top 25 tab 220, a search tab 222 and an update tab 224. Each of the tabs in menu part 226 can be used to access different features of the application store.

The display portion 1102 displays the "top 25" interface 1203 associated with the "top 25" tab 220 highlighted in the display portion 236. Top 25 interface 1103 includes a title bar 1201 that identifies 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. As highlighted in Figure 12, when the "Hide Free" button 1106 is selected, the "Top 25" interface 1203 displays only application objects that require payment.

The "Top 25" interface 1203 contains the application object 1240. In particular, up to 25 application objects 1240 are listed. However, when there are more application objects 1240 that can be displayed in display portion 1202, the user can scroll (238) to see additional application objects. Further, in one embodiment, when the user scrolls to the bottom of the "top 25" list of application objects, the user may see another group of application objects (eg, "next 25" application objects). Buttons can be provided to allow this.

The illustrated application object 1240 includes application objects 1204, 1206 and 1208. Application objects 1240 are presented in a ranked order. Therefore, application object 1204 is ranked above application object 1206. The rank of each application object is identified in the application object. For example, application object 1204 includes a rank identifier 1118 that identifies this application object 1204 as being ranked number one in the list of application objects 1240. The ranking is based on, for example, the average star rating for each application or some other criterion.

Each application object 1240 contains information related to a particular application. For example, the application object 1240 can include a video representing the application, an application name (eg, application 2), a developer name, and rating information.

The application object 1240 also includes purchase information 1212. In particular, each application object 1240 requires payment after the "Hide Free" button 1106 is selected or toggled. When you select a particular application object in the ranked list of application objects 1240, the user interface transitions to an interface that provides information about the application associated with that selected application object. The application information is given in the same manner as the application information interface 403 described above with reference to FIG.

FIG. 13 is a block diagram 1300 of the normative user interface of mobile device 100 exemplifying an application store following a search tab selection. For example, the user can use the touch-sensitive display 102 (eg, by pressing the application store display object 132) to access the application store display object 132 and cause a transition to the application store interface. In one embodiment, touching the application store display object 132 in FIG. 1 results in an animated transition to the application store interface.

The application store user interface includes a display portion 1302 and a menu portion 226. The menu portion 226 can include a large number of tabs. In particular, the menu portion 226 includes a characterization tab 216, a category tab 218, a top 25 tab 220, a search tab 222 and an update tab 224. Each of the tabs in menu part 226 can be used to access different features of the application store.

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

The search interface 1303 includes a search field 1304 and a search button 1306. Search field 1304 allows the user to enter one or more search terms. For example, the user can enter keywords or other keywords that identify a particular application, developer, category. The search button 1306 executes an application search based on user input to the search field 1304. For example, the user can execute the search by touching the search button 1306.

The user can use the keyboard 516 to enter search terms in search field 1304. Keyboard 516 has a full QWERTY layout of keys for typing. The user inputs text on the touch-sensitive display 102 by touching individual keys based on the desired text.

Performing a search (eg, by touching the search button 1306) transitions the user interface to an interface that provides information about one or more applications related to the entered search term. Application information is given (eg, as a list of application objects) similar to the application information interface 403 described above with reference to FIG.

FIG. 14 is a block diagram 1400 of the normative user interface of mobile device 100 exemplifying available updates after invoking an application store display object. For example, the user can use the touch-sensitive display 102 (eg, by pressing the application store display object 132) to access the application store display object 132 and cause a transition to the application store interface. In one embodiment, touching the application store display object 132 in FIG. 1 results in an animated transition to the application store interface.

The application store user interface includes a display portion 236 and a menu portion 226. The menu portion 226 can include a large number of tabs. In particular, the menu portion 226 includes a characterization tab 216, a category tab 218, a top 25 tab 220, a search tab 222 and an update tab 224. Each of the tabs in menu part 226 can be used to access different features of the application store.

In particular, the display portion 236 displays the characterization interface 203 associated with the characterization tab 216 shown as a highlight in the display portion 236. The characterization interface 203 containing the application object was described above with reference to FIG.

Update tab 224 contains update badge 1402. This update badge 1402 identifies whether there are updates available for applications installed on mobile device 100. The user can identify if there are any updates available without selecting the update tab 224. For example, update badge 1402 is a symbol or graphic associated with update tab 224. As shown in FIG. 14, the update badge 1402 is a circle in which the numbers are superimposed on a portion of the graph that identifies the update tab 224. In addition, the update badge 1402 is only visible when updates are available. In certain embodiments, the update badge indicates the number of updates available (eg, by including a number within the badge). For example, the update badge 1402 indicates that there are two updates available.

FIG. 15 is a block diagram 1500 of the normative user interface of mobile device 100 exemplifying an application store following the selection of the update tab (eg, update tab 224). For example, the user can use the touch-sensitive display 102 (eg, by pressing the application store display object 132) to access the application store display object 132 and cause a transition to the application store interface. In one embodiment, touching the application store display object 132 in FIG. 1 results in an animated transition to the application store interface.

The application store user interface includes a display portion 1102 and a menu portion 226. The menu portion 226 can include a large number of tabs. In particular, the menu portion 226 includes a characterization tab 216, a category tab 218, a top 25 tab 220, a search tab 222 and an update tab 224. Each of the tabs in menu part 226 can be used to access different features of the application store.

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

Update interface 1503 contains update object 1540. In particular, two update objects 1506 and 1508 corresponding to the number of updates identified by the update badge 1402 in FIG. 14 are shown on update interface 1503. In other embodiments, there are more update objects 1540 that can be displayed in display portion 1502. When there are more additional update objects 1540 than can be displayed, the user can scroll to see the additional update objects. Further, in some embodiments, the user may be presented with a button that allows the user to see another group of update objects (eg, the next 25 update objects) after or without scrolling. it can.

In one embodiment, update object 1540 identifies a particular update available for applications already installed on mobile device 100. For example, update object 1506 identifies updates to "application A", while update object 1508 identifies updates to "application B". The user can select a particular update object (eg, by touching the update object or its associated update button 1514). You can instruct the download of updates by selecting the update object. Alternatively, selecting an update object can migrate the update interface 1503 to an information interface that provides additional information about the update, after which the user can decide whether to get the update. In one embodiment, a select all button is provided on update interface 1503 so that the user can obtain all application updates associated with the displayed update object 1540.

When one or more update objects 1503 are selected for download, the update interface 1503 is terminated and the previous interface can be restored or the user can be returned to the home screen. Alternatively, when the user selects a particular update object (eg, update object 1506), that object disappears from update interface 1503 (for example, only update object 1508 remains).

FIG. 16 is a block diagram 1600 of the normative user interface of the mobile device 100 exemplifying an application download. For example, the user can select a particular application in the application store, as described above. When the user selects an application object to download, the user interface can be transitioned to a home screen containing the display objects 104 and 106 described above with reference to FIG.

In addition, the download object 1602 is presented as one of the display objects 106. This download object presents a dim or shaded object placeholder for the downloaded application. The download object 1602 is placed in the next available position relative to the other display objects 106. In particular, the download object includes a "loading ..." indicator and a loading bar that replace the application title. The loading bar can be animated to show the progress of the download. When the download of the application is completed, "Loading ..." changes to the application title, and the video presented to the download object 1602 is changed to correspond to the downloaded application.

FIG. 17 is a flow chart illustrating the normative process 1700 for navigating an application store using a mobile device. Input is given to the mobile device requesting the application management interface (step 1702). The user can select, for example, the application store object shown in Figure 1 (eg, using a touch-sensitive display).

An application management interface is presented (step 1704). For example, one or more user interfaces can be presented in relation to the application store. The application management interface is a button that allows users to navigate between different user interfaces, identify and select application objects, and critique and report on applications, for example, as shown in Figures 2-15. , Toggle, or other user-acting elements.

You will receive input to select a particular application for installation (step 1706). This input can be received by the user touching a touch-sensitive display (eg, touch-sensitive display 102 in FIG. 1). For example, in a presented application management interface, the user can search for or identify an application using different criteria or lists provided by that application management interface. The user can select a specific application by touching the displayed application object corresponding to the specific application using the touch-sensitive display.

In other embodiments, other user inputs can be received. For example, you can critique an application, report problems with the application, notify others about the application, or receive input to update a previously installed application.

A decision is made as to whether payment is required for the selected application (step 1708). Some applications are free to users, while others require payment. If no payment is required, the application is installed on the mobile device (step 1710).

If payment is required, the payment will be collected (step 1712). Payments can be received, for example, by charging the user account, redeeming coupons or other credits, or receiving electronic payments from the user (eg, by credit card). In some embodiments, authentication is performed to verify the user.

The application is presented on the home screen of the mobile device (step 1714). The application can be presented as an object on the home screen. In some embodiments, the placeholder object is placed on the home screen (for example, at the next available location on the home screen) while the application is installed, and the placeholder object can be dim and dim. Includes other instructions that the application is not yet available (eg, give loading text). Placeholder objects can direct the progress of the installation (for example, using a loading bar animation).

In certain embodiments, the application store can include one or more location-specific applications. For example, a company or other entity can develop and provide applications within the network that are inaccessible to those outside the local network. In other embodiments, parental control can be activated (eg, using settings for mobile devices) to restrict access to applications in the application store or certain types of applications.

FIG. 18 is a block diagram 1800 of the normative user interface of the mobile device 100 illustrating an application that can be used for deletion. The user can identify the application available for deletion, for example by selecting display object 106 (eg, using a touch-sensitive display). For example, the user can touch and hold the display object 106 corresponding to a particular application (eg, application 1802) for a particular period of time to enter edit mode.

In response to holding an application, the held application can be edited (eg, moved to another position on the touch-sensitive display 102) along with one or more other display objects 106. ). A display object 106 can be deleted. The system can present in edit mode an indicator that identifies these display objects, eg, a badge that is presented with an "X" for a display object that can be deleted. As shown in FIG. 18, "Application 1" 1802 has a badge indicating that this application can be deleted. The user can select a badge to initiate the application removal process (eg by touching the "X" on the touch-sensitive display 102).

FIG. 19 is a block diagram 1900 of the normative user interface of the mobile device 100 exemplifying the rating prompt 1902. When the user selects an application for deletion (eg, application 1802 in FIG. 18), a rating prompt 1902 can be displayed, for example, on the user interface provided by the touch-sensitive display 102. In certain embodiments, the part of the user interface outside the rating prompt 1902 can be dimmed relative to the rating prompt 1902.

The rating prompt 1902 may include a request to critique the application, a rating scale (eg, a set of stars), and one or more buttons (eg, to submit a rating or downgrade the application). it can. The user can give an input (eg, using the touch-sensitive display 102) indicating a particular rating (eg, by selecting a certain number of stars). The user can submit a rating by selecting a certain number of stars, for example, using the "Rating" button. Alternatively, the user can downgrade the application, for example by selecting the "no thanks" button.

FIG. 20 is a flowchart illustrating the normative process 2000 for removing installed applications using a mobile device. Input is received to remove the installed application (step 2002). For example, a user can receive input by touching a touch-sensitive display (eg, touch-sensitive display 102 in FIG. 18). For example, the user may be given input indicating that a particular application should be selected and that the selected application should be deleted. In certain embodiments, the user can enter an edit mode that allows the user to identify an application that can be deleted and select a particular application for deletion. In certain embodiments, a confirmation prompt can be presented to the user when the user selects the application for deletion. The confirmation prompt will instruct the application to be deleted, including the saved data associated with the application, if continued. The confirmation prompt can also give the user the opportunity to cancel the deletion process.

A rating prompt is presented (step 2004). A rating prompt can be presented before completing the removal of the selected application. Rating prompts allow users to give feedback on applications that are being removed. For example, the user can enter a rating for the application (eg, by selecting a specified number of stars).

A decision is made as to whether the user has rated the application (step 2006). This decision can be made based on one or more user inputs. For example, it can be done based on whether the user has entered a rating or selected a button to indicate that the rating has been given. Alternatively, user input may indicate that no rating is given. For example, the user may select a button that indicates that no rating is given.

If it is determined that a rating has been given, rating information is sent to the remote location (step 2008). For example, rating information can be sent to a remote application store (eg, the application store described above). After submitting the rating information, the application is removed and the user interface can return to the home screen or other default interface (step 2010).

If it is determined that no rating is given, the application is removed and the user interface can return to the home screen or other default interface (step 2010).

<u style="single">Network operating environment</u> FIG. 21 is a block diagram of the normative network operating environment 2100 for the mobile device 100 of FIG. The mobile device 100 of FIG. 1 can, for example, communicate via one or more wired and / or wireless networks 2110 in data communication. For example, a wireless network 2112, such as a cellular network, can communicate with a wide area network (WAN) 2114, such as the Internet, by using gateway 2116. Similarly, an access point 2118, such as an 802.11g wireless access point, can provide communication access to the wide area network 2114. In certain embodiments, both voice and data communications can be established via the wireless network 2112 and access point 2118. For example, the mobile device 100a makes and receives phone calls (eg, using the VoIP protocol), sends and receives e-mail messages (eg, using the POP3 protocol), and (eg, TCP). Electronic documents and / or streams such as web pages, photos and videos can be retrieved via wireless network 2112, gateway 2116 and wide area network 2114 (using the / IP or UDP protocol). Similarly, the mobile device 100b can make and receive telephone calls, send and receive e-mail messages, and retrieve electronic documents via access points 2118 and wide area networks 2114. In certain embodiments, the mobile device 100 can be physically connected to access point 2118 using one or more cables, which is a personal computer. In this configuration, the mobile device 100 can be referred to as a "tethered" device.

The mobile devices 100a and 100b can also establish communication by other means. For example, the wireless device 100a can communicate with other wireless devices, such as other mobile devices 100, cellular phones, etc., via the wireless network 2112. Similarly, the mobile devices 100a and 100b are the Bluetooth shown in FIG.^TMBy using one or more communication subsystems, such as communication device 188, peer-to-peer communication 2120, such as a personal area network, can be established. Other communication protocols and topologies can also be implemented.

The mobile device 100 can communicate with, for example, one or more services 2130, 2140, 2150, 2160 and / or one or more content publishers 270 via one or more wired and / or wireless networks 2110. For example, the navigation service 2130 can 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 calls a map function, for example by pressing map object 144 on the top-level graphic user interface shown in Figure 1, and position "1 infinite loop, Cupertino, CA". I have requested and received a map of.

The messaging service 2140 can provide, for example, e-mail and / or other messaging services. Media service 2150 can provide access to media files such as song files, movie files, video clips, and other media data. One or more other services 2160 can also be utilized by the mobile device 100.

The mobile device 100 can also access other data and content via one or more wired and / or wireless networks 2110. For example, the mobile device 100 can access the application store 2170 to feed the application. Such access can be provided by invoking a web browsing function or application (eg, a browser) in response to the user touching a web object on the home screen of the mobile device 100.

<u style="single">Normative mobile device architecture</u> FIG. 22 is a block diagram 2200 of a normative embodiment of the mobile device 100 of FIG. The mobile device 100 can include a memory interface 2202, one or more data processors, a video processor and / or a central processing unit 2204, and a peripheral interface 2206. The memory interface 2202, one or more processors 2204 and / or the peripheral interface 2206 may be separate components or may be integrated into one or more integrated circuits. The various components within the mobile device 100 can be coupled by one or more communication buses or signal lines.

Sensors, devices and subsystems can be coupled to peripheral interface 2206 to facilitate multiple functions. For example, the motion sensor 2210, the optical sensor 2212 and the proximity sensor 2214 can be coupled to the peripheral interface 2206 to facilitate the orientation, lighting and proximity functions described with reference to FIG. Other sensors 2216 such as positioning systems (eg GPS receivers), temperature sensors, biometric sensors or other sensing devices can also be connected to peripheral interface 2206 to facilitate related functions.

Camera subsystem 2220 and optical sensor 2222, such as charge-coupled device (CCD) or complementary metal oxide semiconductor (CMOS) optical sensor, are used to facilitate camera functions such as recording photos and video clips. can do.

Communication functions can be facilitated through one or more wireless communication subsystems 2224, including high frequency receivers and transmitters, and / or optical (eg, infrared) receivers and transmitters. The specific design and implementation of communication subsystem 2224 depends on the communication network in which the mobile device 100 is intended to operate. For example, the mobile device 100 includes a GSM network, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, and Bluetooth.^TMIncludes communication subsystem 2224 designed to operate over the network. In particular, wireless communication subsystem 2224 includes a hosting protocol so that device 100 can be configured as a base station for other wireless devices.

Audio subsystem 2226 can be coupled to speaker 2228 and microphone 2230 to facilitate voice enable functions such as voice recognition, voice replication, digital recording and telephone functions.

The I / O subsystem 2240 may include a touch screen controller 2242 and / or other input controller 2244. The touch screen controller 2242 can be coupled to the touch screen 2246. The touch screen 2246 and the touch screen controller 2242 are, for example, any of a plurality of touch sensing technologies including, but not limited to, capacitive, resistive, infrared and surface acoustic technologies, and one or more with the touch screen 2246. Other proximity sensor arrays or other elements for determining contact points can be used to detect contact and movement or disconnection thereof.

The other input controller 2244 can be coupled to other input / control devices 2248, eg, pointer devices such as one or more buttons, rocker switches, thumbwheels, infrared ports, USB ports, and / or styluses. .. One or more buttons (not shown) can include up / down buttons for volume control of the speaker 2228 and / or microphone 2230.

In one embodiment, pressing a button during the first period dissociates the lock on the touch screen 2246, and pressing a second period button longer than the first period turns on or powers the mobile device 100. Can be switched off. The user can customize the function of one or more buttons. The touch screen 2246 can also be used, for example, to perform virtual or soft buttons and / or keyboards.

In certain embodiments, the mobile device 100 can present recorded audio and / or video files such as MP3, AAC and MPEG files. In certain embodiments, the mobile device 100 can include the function of an MP3 player, such as an iPod®. Therefore, the mobile device 100 includes a 32-pin connector compatible with the iPod. Other input / output and control devices can also be used.

Memory interface 2202 can be coupled to memory 2250. Memory 2250 includes fast 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 (eg, NAND, NOR). Can be done. Memory 2250 can store operating systems 2252 such as Darwin, RTXC, LINUX, UNIX®, OS X, WINDOWS®, or embedded operating systems such as VxWorks. Operating system 2252 handles basic system services and includes instructions for performing hardware-dependent tasks. In some embodiments, the operating system 2252 is a kernel (eg, a UNIX kernel).

Memory 2250 can also store communication instructions 2254 to facilitate communication with one or more additional devices, one or more computers, and / or one or more servers. Memory 2250 is a graphic user interface instruction 2256 to facilitate the processing of the graphic user interface, including presentation, navigation, and selection in the application store shown in Figures 2-16; sensor processing instructions to facilitate sensor-related processing and functions. 2258; Telephone instructions to promote phone-related processes and functions 2260; Electronic messaging instructions to promote electronic messaging-related processes and functions 2262; Web browsing instructions to promote web browsing-related processes and functions 2264; Media processing Media Processing Instructions 2266 to Promote Related Processes and Functions; GPS / Navigation Instructions 2268 to Promote Related Processes and Functions; Camera Instructions 2270 to Promote Camera Related Processes and Functions; and / or Others Includes other software instructions 2272 to facilitate the process and function of.

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

Embodiments of the present invention, and all functional operations described herein, include digital electronic circuits, or computer software, firmware or hardware, including the structures disclosed herein and their structural equivalents. Or, it can be embodied by a combination of one or more of them. Embodiments of the invention can be embodied as one or more computer program products, i.e., a computer encoded on a computer-readable medium to perform or control its operation by a data processor. It can be implemented as one or more modules of program instructions. A computer-readable medium is a machine-readable storage device, a machine-readable storage board, a memory device, a composition of substances acting on a machine-readable propagating signal, or a combination thereof. The term "data processor" includes all devices, devices and machines for processing data, including, for example, programmable processors, computers, or multiprocessors or computers. In addition to the hardware, the device contains code that creates an execution environment for the computer program, such as processor firmware, a protocol stack, a database management system, an operating system, or a combination thereof. be able to. Propagation signals are artificially generated signals, such as machine-generated electrical, optical, or electromagnetic signals generated to encode information for transmission to a suitable receiver.

Computer programs (also known as programs, software, software applications, scripts, or code) can be written in any form of programming language, including compilation or interpretation languages, as well as as stand-alone programs or modules. It can be deployed in any form as a component, subroutine, or other unit suitable for use in a computing environment. Computer programs do not necessarily correspond to files in the file system. A program can be stored in another program or part of a file that holds data (eg, one or more scripts stored in a markup language document) or in a single file dedicated to that program. It can also be stored in multiple matched files (eg, a file that stores one or more modules, subprograms, or parts of code). Computer programs can be deployed to run on one or more computers located at one site or distributed across multiple sites and interconnected by communication networks.

The processes and logical flows described herein can be performed by one or more programmable processors that execute one or more computer programs that perform functions by acting on input data to produce output . The process and logic flow can also be carried out by special purpose logic circuits such as FPGAs (Field Programmable Gate Arrays) or ASICs (Application Specific Integrated Circuits), and devices as such special purpose logic circuits. Can also be embodied.

Suitable processors for running computer programs include, for example, both general purpose and special purpose microprocessors and one or more processors of any type of digital computer. Generally, the processor receives instructions and data from read-only memory, random access memory, or both. An essential element of a computer is a processor for performing instructions and one or more memory devices for storing instructions and data. In general, computers also include one or more mass storage devices for storing data, such as magnetic, magneto-optical discs, or optical discs, or receive or transfer data from them. Operatively coupled, or both. However, the computer need not have such a device. In addition, computers can also be embodied in other devices such as mobile phones, personal digital assistants (PDAs), mobile audio players, and Global Positioning System (GPS) receivers, 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, such as semiconductor memory devices such as EPROM, EEPROM, and flash memory devices. Includes magnetic discs, such as internal hard disks or removable discs; magnetic optical discs; as well as CD-ROMs and DVD-ROM discs. The processor and memory can be captured by special purpose logic circuits or can be integrated into such logic circuits.

In order to interact with the user, embodiments of the present invention allow the user to provide input to a computer with a display device for displaying information to the user, such as a CRT (cathode tube) or LCD (liquid crystal display) monitor. It can be embodied in a computer having a keyboard and pointing device that allows it, such as a mouse or trackball. Other types of devices can also be used to interact with the user, for example, the feedback given to the user is in the form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback, and from the user. Input can be received in any form, including acoustic, speech, or tactile input.

Embodiments of the invention include, for example, a back-end component such as a data server, or, for example, a middleware component such as an application server, or a graphic user that allows an embodiment of the invention to interact with the user. It can be embodied in a computing system that includes front-end components such as a client computer with an interface or web browser, or that includes one or more combinations of such back-end, middleware, or front-end components. These components of the system can be interconnected by any form of digital data communication, such as a communication network. Communication networks include, for example, local area networks (LANs) and wide area networks (WANs), such as the Internet.

Computing systems can include clients and servers. Clients and servers are generally separated from each other and typically interact through a communication network. The client-server relationship arises from computer programs that run on each computer and have a client / server relationship with each other.

Although the specification includes a number of details, these should not be construed as limiting the scope of the claims and should be construed as an explanation of the characteristics specific to a particular embodiment. Some of the features described herein with respect to individual embodiments can also be combined and embodied in one embodiment. Conversely, the various features described with respect to one embodiment can also be embodied in multiple embodiments separately or in appropriate quasi-combinations. Further, those features are described to work in a combination and are initially claimed as such, but remove one or more features from the claimed combination, in some cases, from that combination. And can also direct the claimed combination to a quasi-combination or a variant of the quasi-combination.

Similarly, operations are shown in a particular order, but performing such operations in a particular order or sequential order shown, or all operations shown, in order to achieve the desired result. It should not be understood that it is necessary to carry out. In some environments, multitasking and parallel processing are convenient. Furthermore, the separation of the various system components in the embodiments described above should not be understood to require such separation in all embodiments, and the program components and systems described above are generally one. It should be understood that it can be integrated into a software product together or packaged into multiple software products.

Thus, a particular embodiment of the present invention has been described. Other embodiments are conceivable within the scope of the claims. For example, the actions described in the claims can be performed in different orders to achieve the desired result.

100: Mobile device 102: Touch-sensitive display 104, 106: Display object 110: Phone object 112: E-mail object 114: Web object 116: Media player object 118: Media bar 120: Button 132: Application store object 160: Speaker 162 : Microphone 166: Audio Jack 168: Approach Sensor 170: Ambient Light Sensor 172: Accelerator 180: Camera Lens and Sensor 182: On / Off Button 188: Bluetooth Communication Device 190: Port Device 201: Title Bar 202: Recently Added Button 216 : Characteristic tab 218: Category tab 220: Top 25 tab 222: Search tab 224: Update tab 226: Menu part 236: Display part 238: Scroll 240: Application object 303: Characteristic interface 340: Application object 402: Back button 403: Application information interface 404: "Tell a friend" button 406: Application information 408: Purchase information 410: Information display part 412: Application screenshot 414: Criticism