US9965146B2 - User interface for application management for a mobile device - Google Patents

User interface for application management for a mobile device Download PDF

Info

Publication number
US9965146B2
US9965146B2 US14/279,168 US201414279168A US9965146B2 US 9965146 B2 US9965146 B2 US 9965146B2 US 201414279168 A US201414279168 A US 201414279168A US 9965146 B2 US9965146 B2 US 9965146B2
Authority
US
United States
Prior art keywords
application
mobile device
objects
corresponds
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US14/279,168
Other versions
US20140250015A1 (en
Inventor
Stephen O. Lemay
Sean B. Kelly
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Inc filed Critical Apple Inc
Priority to US14/279,168 priority Critical patent/US9965146B2/en
Publication of US20140250015A1 publication Critical patent/US20140250015A1/en
Application granted granted Critical
Priority to US15/974,510 priority patent/US10318119B2/en
Publication of US9965146B2 publication Critical patent/US9965146B2/en
Priority to US16/409,717 priority patent/US11320961B2/en
Priority to US17/705,179 priority patent/US11947776B2/en
Priority to US18/587,833 priority patent/US20240201828A1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0641Shopping interfaces
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/04817Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482Interaction with lists of selectable items, e.g. menus
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04842Selection of displayed objects or displayed text elements
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0487Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0488Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • G06F9/4446
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces
    • G06F9/453Help systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/12Payment architectures specially adapted for electronic shopping systems
    • G06Q20/123Shopping for digital content
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72469User interfaces specially adapted for cordless or mobile telephones for operating the device by selecting functions from two or more displayed items, e.g. menus or icons
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs

Definitions

  • the present disclosure relates to user interfaces for mobile devices.
  • a mobile phone provides telephony services
  • a personal digital assistant provides a way to organize addresses, contacts and notes
  • a media player plays content
  • email devices provide email communication, a browser to surf the Internet, etc.
  • Modern mobile devices can include two or more of these functions.
  • a mobile device can include a number of different applications, which a user can access independent of other applications.
  • the mobile device can include one or more games, web applications, or productivity applications.
  • This specification describes technologies relating to user interfaces for mobile devices.
  • 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 the 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.
  • 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 multiple tabs, each tab providing access to particular features of the application management interface.
  • Receiving one or more user inputs includes receiving a selection of a particular application object.
  • the method further includes, in response to the selection, transitioning the display portion to present additional information about the selected application.
  • Presenting additional information includes presenting one or more reviews 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 includes presenting a placeholder object on a display of the mobile device, the placeholder object including an indicator of installation progress.
  • the method further includes receiving payment information from a user to purchase the particular application.
  • the mobile device includes a multi-touch-sensitive display.
  • 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 including one or more application objects corresponding to respective applications, each application object presenting information about the respective application, and a menu portion including multiple tabs, each tab providing access to particular features of the application management interface.
  • Other embodiments of this aspect include corresponding methods, apparatus, and computer program products.
  • a user can easily navigate an application store to identify and download applications for a mobile device. Users can be notified of updates to previously downloaded applications without navigating to an update interface. Users can quickly provide feedback on applications including rating the applications and reporting identified problems. Additionally, users can quickly and easily share information on particular applications of interest with other users. Once an application is selected, the user can access other features and applications of the mobile device while waiting for the application to download.
  • FIG. 1 is a block diagram of an example mobile device.
  • FIG. 2 is a block diagram of an example user interface of the mobile device after invoking an application store display object.
  • FIG. 3 is a block diagram of an example user interface of the mobile device after selecting a staff favorites button.
  • FIG. 4 is a block diagram of an example user interface of the mobile device for providing information associated with a particular application.
  • FIG. 5 is a block diagram of an example user interface of the mobile device for notifying another user of an application.
  • FIG. 6 is a block diagram of an example user interface of the 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 the mobile device for reviewing a selected application.
  • FIG. 8 is a block diagram of an example user interface of the mobile device for reporting on a selected application.
  • FIG. 9 is a block diagram of an example user interface of the mobile device illustrating an application store following selection of a categories tab.
  • FIG. 10 is a block diagram 1000 of an example user interface of the mobile device 100 illustrating application objects of a particular selected category.
  • FIG. 11 is a block diagram of an example user interface of the mobile device illustrating an application store following selection of a “top 25” tab.
  • FIG. 12 is a block diagram of an example user interface of the mobile device illustrating an application store “top 25” with free applications hidden.
  • FIG. 13 is a block diagram of an example user interface of the mobile device illustrating an application store following selection of a search tab.
  • FIG. 14 is a block diagram of an example user interface of the mobile device after invoking an application store display object and illustrating available updates.
  • FIG. 15 is a block diagram of an example user interface of the mobile device illustrating an application store following selection of an updates tab.
  • FIG. 16 is a block diagram of an example user interface of the mobile device illustrating an application download.
  • FIG. 17 is a flowchart illustrating an example process for navigating an application store using a mobile device.
  • FIG. 18 is a block diagram of an example user interface of the mobile device illustrating an application available for deletion.
  • FIG. 19 is a block diagram of an example user interface of the mobile device illustrating a rating prompt.
  • FIG. 20 is a flowchart 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 .
  • FIG. 22 is a block diagram of an example implementation of the mobile device of FIG. 1 .
  • FIG. 1 is a block diagram of an example mobile device 100 .
  • the mobile device 100 can be, for example, a handheld computer, a personal digital assistant, a cellular telephone, a network appliance, a camera, a smart phone, an enhanced general packet radio service (EGPRS) mobile phone, a network base station, a media player, a navigation device, an email device, a game console, or a combination of any two or more of these data processing devices or other data processing devices.
  • EGPS enhanced general packet radio service
  • the mobile device 100 includes a touch-sensitive display 102 .
  • the touch-sensitive display 102 can implement liquid crystal display (LCD) technology, light emitting polymer display (LPD) technology, or some other display technology.
  • LCD liquid crystal display
  • LPD light emitting polymer display
  • the touch-sensitive display 102 can be sensitive to haptic and/or tactile contact with a user.
  • the touch-sensitive display 102 can comprise a multi-touch-sensitive display 102 .
  • a multi-touch-sensitive display 102 can, for example, process multiple simultaneous touch points, including processing data related to the pressure, degree and/or position of each touch point. Such processing facilitates gestures and interactions with multiple fingers, chording, and other interactions.
  • Other touch-sensitive display technologies can also be used, e.g., a display in which contact is made using a stylus or other pointing device.
  • the mobile device 100 can display one or more graphical user interfaces on the touch-sensitive display 102 for providing the user access to various system objects and for conveying information to the user.
  • the graphical user interface can include one or more display objects 104 , 106 .
  • the display objects 104 , 106 are graphic representations of system objects.
  • system objects include device functions, applications, windows, files, alerts, events, or other identifiable system objects.
  • the mobile device 100 can implement multiple device functionalities, such as a telephony device, as indicated by a phone object 110 ; an e-mail device, as indicated by the e-mail object 112 ; a network data communication device, as indicated by the Web object 114 ; a Wi-Fi base station device (not shown); and a media processing device, as indicated by the media player object 116 .
  • a telephony device as indicated by a phone object 110
  • an e-mail device as indicated by the e-mail object 112
  • a network data communication device as indicated by the Web object 114
  • a Wi-Fi base station device not shown
  • a media processing device as indicated by the media player object 116 .
  • particular display objects 104 e.g., the phone object 110 , the e-mail object 112 , the Web object 114 , and the media player object 116 , can be displayed in a menu bar 118 .
  • device functionalities can be accessed from a top-level graphical user interface, such as the graphical user interface illustrated in FIG. 1 . Touching one of the objects 110 , 112 , 114 or 116 can, for example, invoke corresponding functionality.
  • the mobile device 100 can implement network distribution functionality.
  • the functionality can enable the user to take the mobile device 100 and its associated network while traveling.
  • the mobile device 100 can extend Internet access (e.g., Wi-Fi) to other wireless devices in the vicinity.
  • mobile device 100 can be configured as a base station for one or more devices. As such, mobile device 100 can grant or deny network access to other wireless devices.
  • the graphical user interface of the mobile device 100 changes, or is augmented or replaced with another user interface or user interface elements, to facilitate user access to particular functions associated with the corresponding device functionality.
  • the graphical user interface of the touch-sensitive display 102 may present display objects related to various phone functions; likewise, touching of the email object 112 may cause the graphical user interface to present display objects related to various e-mail functions; touching the Web object 114 may cause the graphical user interface to present display objects related to various Web-surfing functions; and touching the media player object 116 may cause the graphical user interface to present display objects related to various media processing functions.
  • 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 .
  • each corresponding device functionality may have corresponding “home” display objects displayed on the touch-sensitive display 102 , and the graphical user interface environment of FIG. 1 can be restored by pressing the “home” display object.
  • the top-level graphical user interface can include additional display objects 106 , such as a short messaging service (SMS) object, a calendar object, a photos object, a camera object, a calculator object, a stocks object, a weather object, a maps object, a notes object, a clock object, an address book object, a settings object, and an app store object 132 .
  • SMS short messaging service
  • Touching the SMS display object can, for example, invoke an SMS messaging environment and supporting functionality; likewise, each selection of a display object can invoke a corresponding object environment and functionality.
  • Additional and/or different display objects can also be displayed in the graphical user interface of FIG. 1 .
  • the display objects 106 can be configured by a user, e.g., a user may specify which display objects 106 are displayed, and/or may download additional applications or other software that provides other functionalities and corresponding display objects.
  • the mobile device 100 can include one or more input/output (I/O) devices and/or sensor devices.
  • I/O input/output
  • a speaker 160 and a microphone 162 can be included to facilitate voice-enabled functionalities, such as phone and voice mail functions.
  • an up/down button 184 for volume control of the speaker 160 and the microphone 162 can be included.
  • the mobile device 100 can also include an on/off button 182 for a ring indicator of incoming phone calls.
  • a loud speaker 164 can be included to facilitate hands-free voice functionalities, such as speaker phone functions.
  • An audio jack 166 can also be included for use of headphones and/or a microphone.
  • a proximity sensor 168 can be included to facilitate the detection of the user positioning the mobile device 100 proximate to the user's ear and, in response, to disengage the touch-sensitive display 102 to prevent accidental function invocations.
  • the touch-sensitive display 102 can be turned off to conserve additional power when the mobile device 100 is proximate to the user's ear.
  • an ambient light sensor 170 can be utilized to facilitate adjusting the brightness of the touch-sensitive display 102 .
  • an accelerometer 172 can be utilized to detect movement of the mobile device 100 , as indicated by the directional arrows. Accordingly, display objects and/or media can be presented according to a detected orientation, e.g., portrait or landscape.
  • the mobile device 100 may include circuitry and sensors for supporting a location determining capability, such as that provided by the global positioning system (GPS) or other positioning systems (e.g., systems using Wi-Fi access points, television signals, cellular grids, Uniform Resource Locators (URLs)).
  • GPS global positioning system
  • URLs Uniform Resource Locators
  • a positioning system e.g., a GPS receiver
  • a positioning system can be integrated into the mobile device 100 or provided as a separate device that can be coupled to the mobile device 100 through an interface (e.g., port device 190 ) to provide access to location-based services.
  • the mobile device 100 can also include a camera lens and sensor 180 .
  • the camera lens and sensor 180 can be located on the back surface of the mobile device 100 .
  • the camera can capture still images and/or video.
  • the mobile device 100 can also include one or more wireless communication subsystems, such as an 802.11 b/g communication device 186 , and/or a BluetoothTM communication device 188 .
  • Other communication protocols can 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), etc.
  • 802.x communication protocols e.g., WiMax, Wi-Fi, 3G
  • CDMA code division multiple access
  • GSM global system for mobile communications
  • EDGE Enhanced Data GSM Environment
  • the port device 190 e.g., a Universal Serial Bus (USB) port, or a docking port, or some other wired port connection, is included.
  • the port device 190 can, for example, be utilized to establish a wired connection to other computing devices, such as other communication devices 100 , network access devices, a personal computer, a printer, or other processing devices capable of receiving and/or transmitting data.
  • the port device 190 allows the mobile device 100 to synchronize with a host device using one or more protocols, such as, for example, the TCP/IP, HTTP, UDP and any other known protocol.
  • a TCP/IP over USB protocol can be used, as described in U.S. Provisional Patent Application No. 60/945,904, filed Jun. 22, 2007, for “Multiplexed Data Stream Protocol,”, which is incorporated by reference here in its entirety.
  • FIG. 2 is a block diagram 200 of an example user interface of the mobile device 100 after invoking an application store display object (e.g., app store display object 132 of FIG. 1 ).
  • an application store display object e.g., app store display object 132 of FIG. 1
  • the user can access the app store display object 132 using the touch-sensitive display 102 (e.g., by pressing the app store display object 132 ), resulting in a transition to an application store interface.
  • touching the app store display object 132 in FIG. 1 causes 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 several tabs.
  • the menu portion 226 includes a featured tab 216 , a categories tab 218 , a top 25 tab 220 , a search tab 222 , and an updates tab 224 .
  • Each of the tabs in the menu portion 226 can be used to access different features of the application store, each of which will be described in greater detail below.
  • other tabs can be provided and/or the tab order can vary, for example, as determined by the application store, the mobile device, or based on input received from another remote location.
  • the display portion 236 displays a featured interface 203 associated with the featured tab 216 , which is shown as highlighted in the menu portion 226 .
  • the featured interface 203 includes a title bar 201 .
  • the title bar 201 includes a recently added button 202 and a staff favorites button 204 .
  • the recently added button 202 and staff favorites button 204 are shown as separate buttons. However, the 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 featured interface 203 also includes one or more application objects 240 .
  • the recently added button 202 is shown as currently selected (e.g., based on a user input to the touch-sensitive display 102 ).
  • the application objects 240 displayed correspond to applications that have been recently added to the application store.
  • the recently added applications are specified by a time period from inclusion of the particular application to the application store.
  • the recently added applications can include applications made available in the application store within the past thirty days. In some other implementations, however, the recently added applications can be a specified number (e.g., 25) of most recently added applications to the application store regardless of the actual elapsed time.
  • the application objects 240 can be ordered within the display portion 236 according to one or more criteria. For example, the application objects can be ordered by date added to the application store, alphabetically, or according to user ratings.
  • the application objects 240 shown in the display portion 236 include application objects 210 , 212 , and 214 . Additionally, when the display portion 236 cannot display all of the application objects 240 at one time, the user can scroll 238 up or down to view additional application objects 240 . While a scroll 238 is represented by a dotted arrow at a particular portion of the display portion 236 , the user can scroll 238 from other points. In particular, the user can scroll by gesturing in a particular direction (e.g., up or down) across the touch-sensitive display 102 .
  • Each application object 240 includes information associated with the particular application.
  • application object 210 includes application information 228 .
  • the application information 228 can include an image representing the application, the application name (e.g., “Application 1” for application object 210 ), a developer's name, and rating information.
  • the rating information is represented by a specified number of stars. Stars are filled to indicate the average rating (e.g., three out of five 5) for the application. In some implementations, stars are partially filled to represent a finer degree of granularity of the average rating.
  • the rating information different symbols are used to represent the rating information.
  • the small dots are used to represent unselected stars, which are replaced by stars up to the rating level, such that there are only stars equal to the average rating.
  • the rating information also includes a number of reviews used (e.g., from individual users) to determine the average rating.
  • the application objects 240 also include a purchasing information 230 .
  • the purchasing information indicates whether the application is free or must be purchased (e.g., identified by “free” or “buy” labels). In some implementations, the purchasing information indicates the cost of the application (e.g., $5.00). In some other implementations, the application object 240 can indicate whether or not the user has already installed the particular application. For example, if the user has already installed the application identified by application object 210 , the purchase information 230 can read “installed” instead of “free”. Alternatively, the purchase information 230 can read “uninstall” indicating that the user can uninstall the already installed application.
  • the application objects 240 can also include an “>” indicator (e.g., indicator 232 of application object 210 ).
  • the indicator 232 indicates that selecting a particular application object (e.g., by touching application object 210 ) will transition the user interface to provide additional information about the selected application. The transition can be animated.
  • the display portion 236 can also include one or more advertisements.
  • a first advertisement 206 and a second advertisement 208 are shown near the title bar 201 .
  • only a single advertisement is presented.
  • additional advertisements can be presented.
  • the advertisements are shown near the title bar 201 , one or more advertisements can 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 selecting a staff favorites button (e.g., staff favorites button 204 in FIG. 2 ).
  • a staff favorites button e.g., staff favorites button 204 in FIG. 2
  • the title bar 201 including both the recently added button 202 and the staff favorites button 204 .
  • the display portion 236 presents application objects 340 as part of the featured interface 303 .
  • the application objects 340 can include one or more of the recently added application objects 240 or can be distinct from the application objects 240 .
  • the application objects 340 represent application objects selected by one or more individuals associated with the application store.
  • the staff favorites can be selected by a group of individuals within a specified time period.
  • the staff favorites can change regularly, e.g., every 30 days.
  • the staff favorites are identified according to the applications receiving a highest ratings from a specified group of individuals.
  • the number of application objects 340 identified as staff favorites is limited to a specified number (e.g., top 25 applications).
  • the application objects 340 can be ordered within the featured interface 303 according to one or more criteria.
  • the application objects can be ordered by date added to the application store, alphabetically, or by staff rating.
  • the application objects 340 shown in the display portion 236 include application objects 302 , 304 , and 306 . Additionally, when the display portion 236 cannot display all of the application objects 340 at one time, the user can scroll 238 up or down to view additional application objects 340 as described above with respect to FIG. 2 .
  • Each application object 340 includes information associated with the respective application. Similar to the application information 228 described above with respect to FIG. 2 , the application information can include an image representing the application, the application name (e.g., “Application 4” for application object 302 ), a developer's name, and rating information. In some implementations, the rating information is represented by a specified number of stars identifying an average rating for the corresponding application.
  • the application objects 340 also include purchasing information.
  • the purchasing information indicates whether the “staff favorite” applications are free or must be purchased. In some implementations, the purchasing information indicates the cost of the particular application (e.g., $5.00). In some other implementations, the application object 340 indicates whether or not the user has already installed the particular application. For example, if the user has already installed the application identified by application object 302 , the purchase information can read “installed” instead of “free”. Alternatively, the purchase information can read “uninstall” indicating that the user can uninstall the already installed application.
  • the application objects 340 can also include an “>” indicator (e.g., indicator 232 of FIG. 2 ).
  • the indicator indicates that selecting a particular application object (e.g., by touching application object 302 ) will transition the user interface to provide additional information about the selected application.
  • the transition can be animated.
  • the featured interface 303 can also include one or more advertisements.
  • the display portion 236 presents a first advertisement 206 and a second advertisement 208 near the title bar 201 .
  • only a single advertisement is presented.
  • additional advertisements can be presented.
  • the advertisements are shown near the title bar 201 , one or more advertisements can be presented at different locations on the display portion 236 .
  • a user selection of an application object e.g., one of application objects 240 or 340 , respectively
  • the user interface can transition to provide additional information regarding 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.
  • an application information interface 403 corresponds to the user selection of application object 210 of FIG. 2 .
  • the application information interface 403 includes an information display portion 410 and the menu portion 226 .
  • the menu portion 226 includes the featured tab 216 , the categories tab 218 , the top 25 tab 220 , the search tab 222 , and the updates tab 224 .
  • 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. Additionally, 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 (e.g., the user interface for the app 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 causes the user interface to transition into an interface for notifying another person about the particular application. The interface for notifying another person about the selected application is described in greater detail below with respect to FIG. 5 .
  • the display portion 410 also includes application information 406 , purchase information 408 , an application screenshot 412 , and reviews 414 .
  • the application information 406 includes, for example, the application name and the developer.
  • the application information 406 can also include an image representing the particular application as well as other information, for example, the date the application was added to the application store.
  • the application information 406 can also include a brief description of the application.
  • the purchase information 408 identifies whether the selected application is free or available for purchase. Alternatively, the purchase information 408 can indicate the price of the application (e.g., $5.00).
  • the user can redeem credit to purchase the application. For example, the user can have a gift card, a coupon, or other credit that can be used toward purchasing applications on the application store.
  • the user is presented with a “redeem” button in the application information interface. Touching the redeem button generates an interface where the user can input account information corresponding to the credit to be applied.
  • touching the purchase information 408 initiates a process for downloading the application. For example, if the application is free, the download process can begin without further user input. Alternatively, if purchase is required, a user account can be accessed to purchase the application. In some implementations, the user can redeem a coupon or similar credit to purchase the application, In some other implementations, the user is required to provide account or other authentication information before purchasing the application.
  • the purchase information 408 indicates whether the user has already installed the application (e.g., by including text “installed” or “uninstall” in the purchase information 408 ).
  • the screenshot 412 can provide a screen capture image of the application interface.
  • a more detailed description of the application is provided in place of, or in addition to, the screenshot 412 .
  • the detailed description can include features of the application and other information.
  • more than one screenshot 412 is provided.
  • additional screenshots can be provided as thumbnails that can be displayed when selected by the user.
  • the reviews 414 includes rating information as well as individual reviews of the application.
  • the rating information can include a graphic illustration of an average rating (e.g., using a star rating). Additionally, the number of individual reviews used to determine the average rating can also be provided.
  • the average rating can be followed by one or more individual reviews of the application. In some implementation all reviews are listed. In some other implementations, only a specified number of reviews are listed. In some implementations, the user can scroll 238 to view additional reviews that are not presented within the visible portion of the application information interface 403 .
  • the reviews 414 portion of the application information interface 403 can also include a review button 418 that allows a user to provide a review or other report associated with the application. Providing a review of the application is described below with respect to FIGS. 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.
  • 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. 4 .
  • the notification interface 502 includes a title bar 501 .
  • the title bar 501 identifies the notification interface 502 (e.g., as “tell a friend”). Additionally, the title bar 501 includes a back button 504 and a send button 506 .
  • the back button 504 can cancel the notification interface 502 and allow the user to return to a preceding user interface (e.g., the application information interface 403 ).
  • the send button 506 allows the user to send application information to another person.
  • the notification interface 502 can provide a pre-configured e-mail message that includes a link to the application information in the application store.
  • the 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 can input, for example, an e-mail address or a name corresponding to a contact or address book entry.
  • the “from” field 510 allows the user to identify for the recipient the sender of the notification. In some implementations, the “from” field 510 is automatically populated based on user profile or account information.
  • the “from” field 510 is not presented to the user, but instead is automatically added to the notification.
  • the “subject” field 512 allow the user to specify a subject for the recipient, for example, “check out this application”. In some implementations, the subject field 512 is automatically populated by the application store, for example, with the name of the application or other text.
  • the text box 514 provides additional space for the user to provide additional text to the user (e.g., a message body).
  • the text box 514 has a maximum number of allowed characters for user input.
  • Input to each field and the text box 514 can be provided using keyboard 516 .
  • the keyboard 516 provides a full QWERTY layout of keys for typing.
  • the user inputs text with the touch-sensitive display 102 by touching individual keys according to the desired text.
  • the user can send the notification by touching the send button 506 as described above.
  • sending the notification causes the user interface to transition to the 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 including a menu 602 for providing information associated with a selected application.
  • a portion of the application information interface 403 can be overlaid with the menu 602 .
  • the menu 602 can be partially transparent such that the overlaid portion of the application information interface 403 is partially visible.
  • the menu 602 is presented in response to the user selecting the review button 418 in the application information interface 403 .
  • the menu 602 replaces the application information 403 entirely instead of being provided as a partial overlay.
  • the menu 602 includes a write a review button 604 , a report a problem button 606 , and a cancel button 608 .
  • the write a review button 604 allows the user to write a review for the application of the application information interface 403 .
  • the user interface transitions into a review interface (e.g., using an animated transition).
  • the review interface is described in greater detail below with respect to FIG. 7 .
  • the report a problem button 606 allows the user to report a problem with the application identified in the application information interface 403 .
  • the user interface transitions into a report interface (e.g., using an animated transition).
  • the report interface is described in greater detail below with respect to FIG. 8 .
  • the 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.
  • FIG. 7 shows a review interface 702 presented, for example, in response to the user selecting the write a review button 604 ( FIG. 6 ).
  • the review interface 702 includes a title bar 701 identifying the interface as a review interface.
  • the title bar 701 further includes a back button 704 and a send button 706 .
  • the back button 702 can cancel the review interface 702 and allow the user to return to a preceding user interface (e.g., the application information interface 403 ).
  • the send button 706 allows the user to submit the review.
  • the review interface 702 includes a rating 708 .
  • the rating 708 allows the user to assign a rating value to the application.
  • the user can assign a specified number of stars to the application out of a maximum possible (e.g., from zero to five stars).
  • the user can assign stars using a gesture motion on the touch-sensitive interface 102 .
  • the user can slide a finger in a first direction to incrementally increase the number of stars (to a maximum number, e.g., 5) or in a second direction to incrementally reduce the number of stars (to a minimum number, e.g., zero).
  • the review interface 702 also includes a “from” field 710 , a “title” field 712 , and a review text box 714 .
  • the “from” field 710 allows the user to identify who is providing the review. In some implementations, the “from” field 710 is automatically populated based on user profile or account information. In some other implementations, the “from” field 710 is not presented to the user, but instead is automatically added to the review.
  • the “title” field 712 allows the user to identify an occupation or capacity in which they are providing the review. In some implementations, the “title” field 712 is not provided.
  • the text box 714 provides additional space for the user to provide review text beyond the rating value.
  • the text box 714 has a maximum number of allowed characters for user input.
  • Input to each field and the text box 714 can be provided using keyboard 516 .
  • the keyboard 516 provides a full QWERTY layout of keys for typing.
  • the user inputs text with the touch-sensitive display 102 by touching individual keys according to the desired text.
  • the user can submit the review by touching the send button 706 as described above. In some implementations, submitting the review 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 on a selected application.
  • FIG. 8 shows a reporting interface 802 presented, for example, in response to the user selecting the report a problem button 606 ( FIG. 6 ).
  • the reporting interface 802 includes a title bar 801 identifying the interface as a reporting interface.
  • the title bar 801 further includes a back button 804 and a send button 806 .
  • the back button 802 can cancel the reporting interface 802 and allow the user to return to a preceding user interface (e.g., the application information interface 403 ).
  • the send button 806 allows the user to submit the report.
  • the review interface 802 includes menu buttons with suggested problems to report.
  • the review interface 802 includes a report a bug button 808 , a report as offensive button 810 , and a concern not listed button 812 .
  • the user can select one of the menu buttons by touching a particular menu button in the review interface 802 .
  • the selected menu button is highlighted.
  • an icon is displayed to indicate selection, for example, a checkmark.
  • a text box 814 is presented.
  • the text box 814 allows the user to optionally describe the reported problem.
  • the text box 814 has a maximum number of allowed characters for user input.
  • Input to the text box 814 can be provided using keyboard 516 .
  • the keyboard 516 provides a full QWERTY layout of keys for typing.
  • the user inputs text with the touch-sensitive display 102 by touching individual keys according to the desired text.
  • the user can submit the report by touching the send button 806 as described above.
  • submitting the report causes the user interface to transition to a previous user interface (e.g., application information interface 403 ).
  • 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 an application store following selection of a categories tab (e.g., categories tab 218 of FIG. 2 ).
  • the user can access the app store display object 132 using the touch sensitive display 102 (e.g., by pressing the app store display object 132 ), resulting in a transition to an app store interface.
  • touching the app store display object 132 in FIG. 1 causes an animated transition to the app store interface.
  • the user interface for the app store includes a display portion 902 and a menu portion 226 .
  • the menu portion 226 can include several tabs.
  • the menu portion 226 includes the featured tab 216 , the categories tab 218 , the top 25 tab 220 , the search tab 222 , and the updates tab 224 .
  • Each of the tabs in the menu portion 226 can be used to access different features of the application store.
  • the display portion 236 displays a categories interface 903 associated with the categories tab 218 , which is shown as highlighted in the display portion 236 .
  • the categories interface 903 includes a title bar 901 identifying the user interface as a categories interface.
  • the title bar 903 includes one or more buttons, for example, a back button allowing the user to access a 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 .
  • the categories interface 903 includes one or more category buttons.
  • the categories interface 903 includes a games button 904 , entertainment button 906 , news button 908 , productivity button 910 , sports button 912 , and travel button 914 .
  • the displayed categories can be arranged in any order (e.g., alphabetical, by popularity, etc.). Additionally, other categories can be displayed in place of or in addition to the categories shown. In some implementations, the user can view additional categories by scrolling 238 the category buttons.
  • Each category button allows the user to transition to an interface providing application objects associated with the particular category.
  • a selection of the games button 904 can cause the categories interface to transition to a game objects interface that includes one or more application objects corresponding to games or otherwise associated with the games category.
  • FIG. 10 is a block diagram 1000 of an example user interface of the mobile device 100 illustrating application objects of a particular selected category.
  • FIG. 10 shows a games objects interface 1003 presented in response to a user category selection (e.g., a user selection of the games button 904 in FIG. 9 ).
  • the user interface includes a display portion 1002 and a menu portion 226 .
  • the menu portion 226 includes several tabs.
  • the menu portion 226 includes a featured tab 216 , a categories tab 218 , a top 25 tab 220 , a search tab 222 , and an updates tab 224 .
  • the categories tab 218 is shown as highlighted.
  • the display portion 1002 displays a games objects interface 1003 associated with the selection of a games category.
  • the games objects interface 1003 includes a title bar 1001 including recently added button 1004 and staff favorites button 1006 .
  • the recently added button 1004 and staff favorites button 1006 are shown as separate buttons, however, they can take other forms including, for example, a single toggle button that can be switched from one to the other.
  • the games objects interface 1003 also includes one or more games objects 1040 .
  • the recently added button 1004 is shown as currently selected (e.g., based on a user input to the touch-sensitive display 102 ).
  • the games objects 1040 displayed correspond to game applications that have been recently added to the application store in similar manner as described above in FIG. 2 , but with respect to games objects.
  • the staff favorites button 1006 is selected or toggled, the games objects 1040 displayed correspond to game applications that have been selected by one or more individuals associated with the app store in a similar manner as 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 one time, the user can scroll 238 up or down to view additional game objects 1040 .
  • Each game object 1040 includes information associated with the particular game application.
  • game object 1012 includes game application information 1018 .
  • the game application information 1018 can include an image representing the game application, the game application name (“Game 1”), a developer's name, and rating information.
  • Game 1 the game application name
  • rating information is represented by a specified number of stars. Stars are filled to indicate the average rating (e.g., three out of five) of the game. In some implementations, stars can be partially filled to represent a finer degree of granularity of the average rating.
  • the game objects 1040 also include a purchasing information 1022 .
  • the purchasing information 1022 indicates whether the application is free or must be purchased. In some implementations, the purchasing information indicates the cost of the game (e.g., $5.00).
  • each game object e.g., game objects 1012 , 1014 , and 1016
  • the game objects 1040 can also include an “>” indicator 1020 .
  • the indicator 1020 indicates that selecting a particular game object (e.g., by touching game object 1012 ) transitions the user interface to provide additional information about the selected game application. The transition can be animated.
  • the display portion 1002 can also include one or more advertisements.
  • a first advertisement 1008 and a second advertisement 1010 arc shown near the title bar 1001 .
  • only a single advertisement is presented.
  • additional advertisements can be presented.
  • the advertisements are shown near the title bar 1001 , one or more advertisements can be presented at different locations on the display portion 1002 .
  • the user can select a particular game object 1040 in order to transition to provide information regarding the game associated with the selected game object.
  • the game information is provided in a similar manner to the application information interface 403 described above with respect to FIG. 4 .
  • FIG. 11 is a block diagram 1100 of an example user interface of the mobile device 100 illustrating an application store following selection of a “top 25” tab (e.g., “top 25” tab 220 ).
  • the user can access the app store display object 132 using the touch sensitive display 102 (e.g., by pressing the app store display object 132 ), resulting in a transition to an app store interface.
  • touching the app store display object 132 in FIG. 1 causes an animated transition to the app store interface.
  • the user interface for the app store includes a display portion 1102 and the menu portion 226 .
  • the menu portion 226 can include several tabs.
  • the menu portion 226 includes the featured tab 216 , the categories tab 218 , the top 25 tab 220 , the search tab 222 , and the updates tab 224 .
  • Each of the tabs in the menu portion 226 can be used to access different features of the application store.
  • the display portion 1102 displays a “top 25” interface 1103 associated with the “top 25” tab 220 , which is shown as highlighted in the display portion 236 .
  • the top 25 interface 1103 includes a title bar 1101 identifying the user interface as a top 25 interface.
  • the title bar 1101 also includes a “show free” button 1104 and a “hide free” button 1106 .
  • the “top 25” interface 1103 displays application objects 1140 including those associated with applications available for free.
  • the “hide free” button 1106 is selected, the “top 25” interface 1103 only displays application objects that require payment.
  • the “top 25” interface 1103 includes application objects 1140 .
  • 25 application objects 1140 are listed.
  • the user can scroll 238 to view additional application objects.
  • a button can be provided to allow the user to view another group of application objects (e.g., a “next 25” application objects).
  • the application objects 1140 shown include application objects 1112 , 1114 , and 1116 .
  • the application objects 1140 are presented in ranked order.
  • application object 1112 is ranked above application object 1114 .
  • the rank of each application object is identified in the application object.
  • application object 1112 includes a rank identifier 1118 that identifies the application object 1112 as being ranked number one in the list of application objects 1140 .
  • Each application object 1140 includes information associated with the particular application.
  • application object 1112 includes application information 1122 .
  • the application information 1122 can include an image representing the application, the application name (“Application 5”), a developer's name, and rating information.
  • the rating information is represented by a specified number of stars. Stars are filled to indicate the average rating (e.g., 3/5) of the game. In some implementations, stars can be partially filled to represent a finer degree of granularity of the average rating.
  • the application objects 1140 also include a purchasing information 1124 .
  • the purchasing information 1124 indicates whether the application is free or must be purchased. In some implementations, the purchasing information indicates the cost of the application (e.g., $5.00).
  • each application object e.g., application objects 1112 , 1114 , and 1116
  • the application objects 1140 can also each include an “>” indicator 1124 .
  • the indicator 1124 indicates that selecting a particular application object (e.g., by touching application object 1112 ) will transition the user interface to provide additional information about the selected application. The transition can be animated.
  • the display portion 1102 can also include one or more advertisements.
  • a first advertisement 1108 and a second advertisement 1110 are shown near the title bar 1101 .
  • only a single advertisement is presented.
  • additional advertisements can be presented.
  • the advertisements are shown near the title bar 1101 , one or more advertisements can be presented at different locations on the display portion 1102 .
  • Selecting a particular application object in the ranked list of application objects 1140 transitions the user interface to an interface providing information regarding the application associated with the selected application object.
  • the application information is provided in a similar manner to the application information interface 403 described above with respect to FIG. 4 .
  • FIG. 12 is a block diagram 1200 of an example user interface of the mobile device 100 illustrating an application store “top 25” with free applications hidden.
  • the user interface for the app store includes a display portion 1202 and the menu portion 226 .
  • the menu portion 226 can include several tabs.
  • the menu portion 226 includes the featured tab 216 , the categories tab 218 , the top 25 tab 220 , the search tab 222 , and the updates tab 224 .
  • Each of the tabs in the menu portion 226 can be used to access different features of the application store.
  • the display portion 1202 displays a “top 25” interface 1203 associated with the “top 25” tab 220 , which is shown as highlighted in the display portion 236 .
  • the top 25 interface 1103 includes a title bar 1201 identifying the user interface as a “top 25” interface.
  • the title bar 1201 also includes the “show free” button 1104 and the “hide free” button 1106 .
  • the “hide free” button 1106 is selected, as shown by the highlighting in FIG. 12 .
  • the “hide free” button 1106 is selected, as shown by the highlighting in FIG. 12 .
  • the “hide free” button 1106 is selected, the “top 25” interface 1203 only displays application objects which require payment.
  • the “top 25” interface 1203 includes application objects 1240 .
  • application objects 1240 In particular, up to 25 application objects 1240 are listed. However, when there are more application objects 1240 than can be displayed in the display portion 1202 , the user can 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 can be provided to allow the user to view another group of application objects (e.g., a “next 25” application objects).
  • the application objects 1240 shown include application objects 1204 , 1206 , and 1208 .
  • the application objects 1240 are presented in a ranked order.
  • application object 1204 is ranked above application object 1206 .
  • the rank of each application object is identified in the application object.
  • application object 1204 includes a rank identifier 1210 that identifies the application object 1204 as being ranked number one in the list of application objects 1240 .
  • the ranking can be based, for example, on the average star rating of each application or some other criteria.
  • Each application object 1240 includes information associated with the particular application.
  • the application objects 1240 can include an image representing the application, the application name (e.g., “Application 2”), a developer's name, and rating information.
  • the application objects 1240 also include a purchasing information 1212 .
  • a purchasing information 1212 In particular, since the “hide free” button 1106 is selected or toggled, each of the application objects 1240 requires payment. Selecting a particular application object in the ranked list of application objects 1240 transitions the user interface to an interface providing information regarding the application associated with the selected application object.
  • the application information is provided in a similar manner to the application information interface 403 described above with respect to FIG. 4 .
  • FIG. 13 is a block diagram 1300 of an example user interface of the mobile device 100 illustrating an application store following selection of a search tab.
  • the user can access the app store display object 132 using the touch sensitive display 102 (e.g., by pressing the app store display object 132 ), resulting in a transition to an app store interface.
  • touching the app store display object 132 in FIG. 1 causes an animated transition to the app store interface.
  • the user interface for the app store includes a display portion 1302 and the menu portion 226 .
  • the menu portion 226 can include several tabs.
  • the menu portion 226 includes the featured tab 216 , the categories tab 218 , the top 25 tab 220 , the search tab 222 , and the updates tab 224 .
  • Each of the tabs in the menu portion 226 can be used to access different features of the application store.
  • the display portion 1302 displays a search interface 1303 associated with the search tab 222 , which is shown as highlighted in the display portion 236 .
  • the search interface 1303 includes a title bar 1201 identifying the user interface as an application search interface.
  • the search interface 1303 includes a search field 1304 and a search button 1306 .
  • the search field 1304 allows a user to input one or more search terms. For example, the user can input keywords identifying a particular application, developer, category, or other keywords.
  • the search button 1306 executes an application search based on the user input to the search field 1304 . For example, the user can execute the search by touching the search button 1306 .
  • the user can input search terms into the search field 1304 using keyboard 516 .
  • the keyboard 516 provides a full QWERTY layout of keys for typing.
  • the user inputs text with the touch sensitive display 102 by touching individual keys according to the desired text.
  • Executing a search transitions the user interface to an interface providing information regarding one or more applications associated with the input search terms.
  • the application information is provided in a similar manner to the application information interface 403 (e.g., as a list of application objects) as described above with respect to FIG. 4 .
  • FIG. 14 is a block diagram 1400 of an example user interface of the mobile device 100 after invoking an application store display object and illustrating available updates.
  • the user can access the app store display object 132 using the touch sensitive display 102 (e.g., by pressing the app store display object 132 ), resulting in a transition to an application store interface.
  • touching the application store display object 132 in FIG. 1 causes an animated transition to the app store interface.
  • the user interface for the application store includes the display portion 236 and the menu portion 240 .
  • the menu portion 226 includes several tabs.
  • the menu portion 226 includes the featured tab 216 , the categories tab 218 , the top 25 tab 220 , the search tab 222 , and the updates tab 224 .
  • Each of the tabs in the menu portion 226 can be used to access different features of the application store.
  • the display portion 236 displays a featured interface 203 associated with the featured tab 216 , which is shown as highlighted in the display portion 236 .
  • the featured interface 203 including application objects is described above with respect to FIG. 2 .
  • the updates tab 224 includes an updates badge 1402 .
  • the updates badge 1402 identifies whether or not there are updates available to the applications installed on the mobile device 100 . The user can identify whether there are available updates without selecting the updates tab 224 .
  • the updates badge 1402 can be a symbol or graphic associated with the updates tab 224 . As shown in FIG. 14 , the updates badge 1402 is a circle with a number inside that is superimposed over a portion of the graphic identifying the updates tab 224 . Additionally, the updates badge 1402 can be visible only when an update is available. In some implementations, the updates badge indicates the number of available updates (e.g., by including a number in the badge). For example, updates badge 1402 shows that there are two updates available.
  • FIG. 15 is a block diagram of an example user interface 1500 of the mobile device 100 illustrating an application store following selection of an updates tab (e.g., updates tab 224 ).
  • the user can access the app store display object 132 using the touch sensitive display 102 (e.g., by pressing the app store display object 132 ), resulting in a transition to an app store interface.
  • touching the app store display object 132 in FIG. 1 causes an animated transition to the app store interface.
  • the user interface for the app store includes a display portion 1102 and the menu portion 226 .
  • the menu portion 226 can include several tabs.
  • the menu portion 226 includes the featured tab 216 , the categories tab 218 , the top 25 tab 220 , the search tab 222 , and the updates tab 224 .
  • Each of the tabs in the menu portion 226 can be used to access different features of the application store.
  • the display portion 1502 displays an updates interface 1503 associated with the updates tab 224 , which is shown as highlighted in the display portion 236 .
  • the updates interface 1503 includes a title bar 1501 identifying the user interface as an updates interface.
  • the title bar 1501 also includes an optional back button 1504 .
  • the back button 1504 allows the user to exit the updates interface 1503 or the application store and to return to an earlier user interface. Alternatively, the user can exit the application store and return to the “home” interface shown in FIG. 1 by pressing button 120 .
  • the updates interface 1503 includes update objects 1540 .
  • two update objects 1506 and 1508 are shown in the updates interface 1503 , which corresponds to the number of updates identified by the updates badge 1402 in FIG. 14 .
  • the user can scroll to view additional update objects.
  • the update objects 1540 identify particular updates available for applications already installed on the mobile device 100 .
  • the update object 1506 identifies an update to “Application A” while the update object 1508 identifies an update to “Application B”.
  • the user can select the particular update object (e.g., by touching the update object or an associated update button 1514 ). Selecting the update object can indicate the update download.
  • selecting the update object can transition the updates interface 1503 to an information interface that provides additional information about the update, after which the user can decide whether or not to get the update.
  • a select all button is provided in the updates interface 1503 allowing the user to get all application updates associated with the displayed update objects 1540 .
  • the updates interface 1503 can end, restoring a previous interface or returning the user to the home screen.
  • a particular update object e.g., update object 1506
  • that object disappears from the update interface 1503 (e.g., only the update object 1508 would remain).
  • FIG. 16 is a block diagram 1600 of an example user interface of the mobile device 100 illustrating an application download.
  • the user can select a particular application in the app store, for example, as described above.
  • the user interface can transition to the home screen including display objects 104 and 106 as described above with respect to FIG. 1 .
  • a download object 1602 is presented as one of the display objects 106 .
  • the download object presents a dimmed or shaded object placeholder for the application being downloaded.
  • the download object 1602 is positioned in the next available location relative to the other display objects 106 .
  • the download object includes a “loading . . . ” indicator instead of the application title as well as a loading bar.
  • the loading bar can animate to show the progress of the download.
  • FIG. 17 is a flowchart illustrating an example process 1700 for navigating an application store using a mobile device.
  • An input is provided to a mobile device requesting an application management interface (step 1702 ).
  • the user can select (e.g., using a touch-sensitive display) an application store object as shown, e.g., in FIG. 1 .
  • An application management interface is presented (step 1704 ).
  • one or more user interfaces can be presented in association with an application store.
  • the application management interface can include buttons, toggles, or other user activated elements that allow the user to navigate between different user interfaces, identify and select application objects, and review and report applications as shown, for example, in FIGS. 2-15 .
  • An input is received selecting a particular application for installation (step 1706 ).
  • the input can be received, for example, from a user touching a touch-sensitive display (e.g., touch-sensitive display 102 of FIG. 1 ).
  • a touch-sensitive display e.g., touch-sensitive display 102 of FIG. 1
  • the user can search for or identify an application in the presented application management interface using different criteria or listings provided by the application management interface.
  • the user can select the particular application using a touch-sensitive display by touching a displayed application object corresponding to the particular application.
  • an input can be received reviewing an application, reporting a problem with an application, notifying others about an application, or updating a previously installed application.
  • the payment is collected (step 1712 ).
  • the payment can be received, for example, by charging a user account, redeeming a coupon or other credit, or by receiving an electronic payment (e.g., by credit card) from the user.
  • authentication is performed to verify the user.
  • the application is presented in a home screen of the mobile device (step 1714 ).
  • the application can be presented as an object on the home screen.
  • a placeholder object is positioned on the home screen (e.g., in a next available location on the home screen).
  • the placeholder object can be dimmed and include other indications that the application is not yet available (e.g., providing loading text).
  • the placeholder object can indicate the progress of the installation (e.g., using a loading bar animation).
  • the application store can include one or more applications that are location specific. For example, corporations or other entities can develop and provide applications within the network, which are not accessible to those outside the local network. In some other implementations, parental controls can be activated (e.g., using settings for the mobile device) to limit access to applications or particular types of applications in the application store.
  • FIG. 18 is a block diagram 1800 of an example user interface of the mobile device 100 illustrating an application available for deletion.
  • the user can identify applications available for deletion, for example, by selecting a display object 106 (e.g., using a touch-sensitive display). For example, the user can touch and hold a display object 106 corresponding to a particular application (e.g., application 1802 ) for a specified period of time to enter an editing mode.
  • a display object 106 e.g., using a touch-sensitive display.
  • the user can touch and hold a display object 106 corresponding to a particular application (e.g., application 1802 ) for a specified period of time to enter an editing mode.
  • the held application along with one or more other display objects 106 can become editable (e.g., movable to other locations on the touch-sensitive display 102 ).
  • Some display objects 106 can be deleted.
  • the system can present an indicator in the editing mode identifying those display objects, for example, a badge with an “X” presented for those display objects that can be deleted.
  • “Application 1” 1802 has a badge indicating that this application can be deleted. The user can select the badge (e.g., by touching the “X” on the touch-sensitive display 102 ) in order to initiate a deletion process for the application.
  • FIG. 19 is a block diagram 1900 of an example user interface of the mobile device 100 illustrating a rating prompt 1902 .
  • an application for deletion e.g., application 1802 of FIG. 18
  • the rating prompt 1902 can be displayed, for example, on the user-interface provided by the touch-sensitive display 102 .
  • the portion of the user interface outside of the rating prompt 1902 can be dimmed relative to the rating prompt 1902 .
  • the rating prompt 1902 can include a request to review the application, a rating scale (e.g., a set of stars), and one or more buttons (e.g., to submit a rating or to decline rating the application).
  • the user can provide an input (e.g., using the touch-sensitive display 102 ) that indicates a particular rating (e.g., by selecting a particular number of stars).
  • a particular rating e.g., by selecting a particular number of stars.
  • the user can submit the rating using, e.g., a “rate” button.
  • the user can decline to rate the application, for example, by selecting a “no thanks” button.
  • FIG. 20 is a flowchart illustrating an example process 2000 for deleting an installed application using a mobile device.
  • An input is received to delete an installed application (step 2002 ).
  • the input can be received, for example, from a user touching a touch-sensitive display (e.g., touch-sensitive display 102 of FIG. 18 ).
  • the user can select a particular application and provide an input indicating that the selected application should be deleted.
  • the user can enter an editing mode that allows the user to identify applications that can be deleted as well as select a particular application for deletion.
  • a confirmation prompt can be presented to the user.
  • the confirmation prompt can indicate that continuing will delete the application including any saved data associated with the application.
  • the conformation prompt can further provide an opportunity for the user to cancel the deletion process.
  • a rating prompt is presented (step 2004 ).
  • the ratings prompt can be presented prior to completing the deletion of the selected application.
  • the ratings prompt allows the user to provide feedback for the application being deleted. For example, the user can input a rating for the application (e.g., by selecting a specified number of stars).
  • the determination can be made according to one or more user inputs. For example, based on whether the user entered a rating or selected a button indicating that a rating has been provided.
  • the user input can indicate that no rating is being provided.
  • the user can select a button indicating that no rating is being provided.
  • the rating information is sent to a remote location (step 2008 ).
  • the rating information can be sent to an application store located at a remote location (e.g., the application store described above).
  • the application is removed and the user interface can return to a home screen or other default interface (step 2010 ).
  • the application is removed and the user interface can return to a home screen or other default interface (step 2010 ).
  • 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, for example, communicate over one or more wired and/or wireless networks 2110 in data communication.
  • a wireless network 2112 e.g., a cellular network
  • WAN wide area network
  • an access point 2118 such as an 802.11g wireless access point, can provide communication access to the wide area network 2114 .
  • both voice and data communications can be established over the wireless network 2112 and the access point 2118 .
  • the mobile device 100 a can place and receive phone calls (e.g., using VoIP protocols), send and receive e-mail messages (e.g., using POP3 protocol), and retrieve electronic documents and/or streams, such as web pages, photographs, and videos, over the wireless network 2112 , gateway 2116 , and wide area network 2114 (e.g., using TCP/IP or UDP protocols).
  • the mobile device 100 b can place and receive phone calls, send and receive e-mail messages, and retrieve electronic documents over the access point 2118 and the wide area network 2114 .
  • 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 this configuration, the mobile device 100 can be referred to as a “tethered” device.
  • the mobile devices 100 a and 100 b can also establish communications by other means.
  • the wireless device 100 a can communicate with other wireless devices, e.g., other wireless devices 100 , cell phones, etc., over the wireless network 2112 .
  • the mobile devices 100 a and 100 b can establish peer-to-peer communications 2120 , e.g., a personal area network, by use of one or more communication subsystems, such as the BluetoothTM communication device 188 shown in FIG. 1 .
  • Other communication protocols and topologies can also be implemented.
  • the mobile device 100 can, for example, communicate with one or more services 2130 , 2140 , 2150 , and 2160 and/or one or more content publishers 2170 over the one or more wired and/or wireless networks 2110 .
  • a navigation service 2130 can provide navigation information, e.g., map information, location information, route information, and other information, to the mobile device 100 .
  • a user of the mobile device 100 b has invoked a map functionality, e.g., by pressing the maps object 144 on the top-level graphical user interface shown in FIG. 1 , and has requested and received a map for the location “1 Infinite Loop, Cupertino, Calif.”
  • a messaging service 2140 can, for example, provide e-mail and/or other messaging services.
  • a media service 2150 can, for example, 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 over the one or more wired and/or wireless networks 2110 .
  • an application store 2170 can be accessed by the mobile device 100 to provide applications. Such access can be provided by invocation of a web browsing function or application (e.g., a browser) in response to a user touching a web object on the home screen of the mobile device 100 .
  • a web browsing function or application e.g., a browser
  • FIG. 22 is a block diagram 2200 of an example implementation of the mobile device 100 of FIG. 1 .
  • the mobile device 100 can include a memory interface 2202 , one or more data processors, image processors and/or central processing units 2204 , and a peripherals interface 2206 .
  • the memory interface 2202 , the one or more processors 2204 and/or the peripherals interface 2206 can be separate components or can be integrated in one or more integrated circuits.
  • the various components in the mobile device 100 can be coupled by one or more communication buses or signal lines.
  • Sensors, devices and subsystems can be coupled to the peripherals interface 2206 to facilitate multiple functionalities.
  • a motion sensor 2210 a light sensor 2212 , and a proximity sensor 2214 can be coupled to the peripherals interface 2206 to facilitate the orientation, lighting and proximity functions described with respect to FIG. 1 .
  • Other sensors 2216 can also be connected to the peripherals interface 2206 , such as a positioning system (e.g., GPS receiver), a temperature sensor, a biometric sensor, or other sensing device, to facilitate related functionalities.
  • a camera subsystem 2220 and an optical sensor 2222 can be utilized to facilitate camera functions, such as recording photographs and video clips.
  • an optical sensor 2222 e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, can be utilized to facilitate camera functions, such as recording photographs and video clips.
  • CCD charged coupled device
  • CMOS complementary metal-oxide semiconductor
  • Communication functions can be facilitated through one or more wireless communication subsystems 2224 , which can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters.
  • the specific design and implementation of the communication subsystem 2224 can depend on the communication network(s) over which the mobile device 100 is intended to operate.
  • a mobile device 100 may include communication subsystems 2224 designed to operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, and a BluetoothTM network.
  • the wireless communication subsystems 2224 may include hosting protocols such that the device 100 may be configured as a base station for other wireless devices.
  • An audio subsystem 2226 can be coupled to a speaker 2228 and a microphone 2230 to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions.
  • the I/O subsystem 2240 can include a touch screen controller 2242 and/or other input controller(s) 2244 .
  • the touch-screen controller 2242 can be coupled to a touch screen 2246 .
  • the touch screen 2246 and touch screen controller 2242 can, for example, detect contact and movement or break thereof using any of multiple touch sensitivity 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 .
  • the other input controller(s) 2244 can be coupled to other input/control devices 2248 , such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus.
  • the one or more buttons can include an up/down button for volume control of the speaker 2228 and/or the microphone 2230 .
  • a pressing of the button for a first duration may disengage a lock of the touch screen 2246 ; and a pressing of 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 able to customize a functionality of one or more of the buttons.
  • the touch screen 2246 can, for example, also be used to implement virtual or soft buttons and/or a keyboard.
  • the mobile device 100 can present recorded audio and/or video files, such as MP3, AAC, and MPEG files.
  • the mobile device 100 can include the functionality of an MP3 player, such as an iPodTM.
  • the mobile device 100 may, therefore, include a 32-pin connector that is compatible with the iPodTM.
  • Other input/output and control devices can also be used.
  • the memory interface 2202 can be coupled to memory 2250 .
  • the memory 2250 can 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 can store an operating system 2252 , such as Darwin, RTXC, LINUX, UNIX, OS X, 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 dependent tasks.
  • the operating system 2252 can be a kernel (e.g., UNIX kernel).
  • the memory 2250 may also store communication instructions 2254 to facilitate communicating with one or more additional devices, one or more computers and/or one or more servers.
  • the memory 2250 may include graphical user interface instructions 2256 to facilitate graphic user interface processing including presentation, navigation, and selection within an application store as shown in FIGS.
  • sensor processing instructions 2258 to facilitate sensor-related processing and functions
  • phone instructions 2260 to facilitate phone-related processes and functions
  • electronic messaging instructions 2262 to facilitate electronic-messaging related processes and functions
  • web browsing instructions 2264 to facilitate web 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 processes and instructions
  • camera instructions 2270 to facilitate camera-related processes and functions
  • other software instructions 2272 to facilitate other processes and functions.
  • Each of the above identified instructions and applications can correspond to a set of instructions for performing one or more functions described above. These instructions need not be implemented as separate software programs, procedures or modules.
  • the memory 2250 can include additional instructions or fewer instructions.
  • various functions of the mobile device 100 may be implemented in hardware and/or in software, including in 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 them.
  • data processing apparatus encompasses 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, 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.
  • 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 performing instructions and one or more memory devices for storing instructions and data.
  • 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., magnetic, magneto-optical disks, or optical disks.
  • mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
  • a computer need not have such devices.
  • a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, to name just 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, e.g., 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.
  • 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.
  • a display device e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
  • keyboard and a pointing device e.g., a mouse or a trackball
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can 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 can 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”), e.g., the Internet.
  • LAN local area network
  • WAN wide area network
  • the computing system can 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Software Systems (AREA)
  • Human Computer Interaction (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • User Interface Of Digital Computer (AREA)
  • Stored Programmes (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

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 the application management interface including an input to install a particular application; installing the selected application; and presenting the installed application.

Description

CROSS-REFERENCES TO RELATED APPLICATIONS
This application is a continuation of U.S. patent application Ser. No. 13/350,563 filed Jan. 13, 2012, which is a continuation of U.S. patent application Ser. No. 12/354,616, filed Jan. 15, 2009, and which claims the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Application Ser. No. 61/059,730, filed Jun. 6, 2008. The disclosures of the foregoing applications are hereby incorporated by reference in their entirety for all purposes.
BACKGROUND
The present disclosure relates to user interfaces for mobile devices.
Conventional mobile devices are often dedicated to performing specific functions. For example, a mobile phone provides telephony services, a personal digital assistant (PDA) provides a way to organize addresses, contacts and notes, a media player plays content, email devices provide email communication, a browser to surf the Internet, etc. Modern mobile devices can include two or more of these functions.
In particular, a mobile device can include a number of different applications, which a user can access independent of other applications. For example, the mobile device can include one or more games, web applications, or productivity applications.
BRIEF SUMMARY
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 the 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 can 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 multiple tabs, each tab providing access to particular features of the application management interface. Receiving one or more user inputs includes receiving a selection of a particular application object. The method further includes, in response to the selection, transitioning the display portion to present additional information about the selected application. Presenting additional information includes presenting one or more reviews 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 includes presenting a placeholder object on a display of the mobile device, the placeholder object including an indicator of installation progress. The method further includes receiving payment information from a 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 including one or more application objects corresponding to respective applications, each application object presenting information about the respective application, and a menu portion including multiple tabs, each tab providing access to particular features of the 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. A user can easily navigate an application store to identify and download applications for a mobile device. Users can be notified of updates to previously downloaded applications without navigating to an update interface. Users can quickly provide feedback on applications including rating the applications and reporting identified problems. Additionally, users can quickly and easily share information on particular applications of interest with other users. Once an application is selected, the user can access other features and applications of the mobile device while waiting for the application to download.
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 apparent from the description, the drawings, and the claims.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of an example mobile device.
FIG. 2 is a block diagram of an example user interface of the mobile device after invoking an application store display object.
FIG. 3 is a block diagram of an example user interface of the mobile device after selecting a staff favorites button.
FIG. 4 is a block diagram of an example user interface of the mobile device for providing information associated with a particular application.
FIG. 5 is a block diagram of an example user interface of the mobile device for notifying another user of an application.
FIG. 6 is a block diagram of an example user interface of the 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 the mobile device for reviewing a selected application.
FIG. 8 is a block diagram of an example user interface of the mobile device for reporting on a selected application.
FIG. 9 is a block diagram of an example user interface of the mobile device illustrating an application store following selection of a categories tab.
FIG. 10 is a block diagram 1000 of an example user interface of the mobile device 100 illustrating application objects of a particular selected category.
FIG. 11 is a block diagram of an example user interface of the mobile device illustrating an application store following selection of a “top 25” tab.
FIG. 12 is a block diagram of an example user interface of the mobile device illustrating an application store “top 25” with free applications hidden.
FIG. 13 is a block diagram of an example user interface of the mobile device illustrating an application store following selection of a search tab.
FIG. 14 is a block diagram of an example user interface of the mobile device after invoking an application store display object and illustrating available updates.
FIG. 15 is a block diagram of an example user interface of the mobile device illustrating an application store following selection of an updates tab.
FIG. 16 is a block diagram of an example user interface of the mobile device illustrating an application download.
FIG. 17 is a flowchart illustrating an example process for navigating an application store using a mobile device.
FIG. 18 is a block diagram of an example user interface of the mobile device illustrating an application available for deletion.
FIG. 19 is a block diagram of an example user interface of the mobile device illustrating a rating prompt.
FIG. 20 is a flowchart 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.
FIG. 22 is a block diagram of an example implementation of the mobile device of FIG. 1.
Like reference numbers and designations 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 can be, for example, a handheld computer, a personal digital assistant, a cellular telephone, a network appliance, a camera, a smart phone, an enhanced general packet radio service (EGPRS) mobile phone, a network base station, a media player, a navigation device, an email device, a game console, or a combination of any two or more of these data processing devices or other data processing devices.
Mobile Device Overview
In some implementations, the mobile device 100 includes a touch-sensitive display 102. The touch-sensitive display 102 can implement liquid crystal display (LCD) technology, light emitting polymer display (LPD) technology, or some other display technology. The touch-sensitive display 102 can be sensitive to haptic and/or tactile contact with a user.
In some implementations, the touch-sensitive display 102 can comprise a multi-touch-sensitive display 102. A multi-touch-sensitive display 102 can, for example, process multiple simultaneous touch points, including processing data related to the pressure, degree and/or position of each touch point. Such processing facilitates gestures and interactions with multiple fingers, chording, and other interactions. Other touch-sensitive display technologies can also be used, e.g., a display in which contact is made 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/0015024A1, each of which is incorporated by reference herein in its entirety.
In some implementations, the mobile device 100 can display one or more graphical user interfaces on the touch-sensitive display 102 for providing the user access to various system objects and for conveying information to the user. In some implementations, the graphical user interface can include one or more display objects 104, 106. In the example shown, the display objects 104, 106, are graphic representations of system objects. Some examples of system objects include device functions, applications, windows, files, alerts, events, or other identifiable system objects.
Exemplary Mobile Device Functionality
In some implementations, the mobile device 100 can implement multiple device functionalities, such as a telephony device, as indicated by a phone object 110; an e-mail device, as indicated by the e-mail object 112; a network data communication device, as indicated by the Web object 114; a Wi-Fi base station device (not shown); and a media processing device, as indicated by the media player object 116. In some implementations, particular display objects 104, e.g., the phone object 110, the e-mail object 112, the Web object 114, and the media player object 116, can be displayed in a menu bar 118. In some implementations, device functionalities can be accessed from a top-level graphical user interface, such as the graphical user interface illustrated in FIG. 1. Touching one of the objects 110, 112, 114 or 116 can, for example, invoke corresponding functionality.
In some implementations, the mobile device 100 can implement network distribution functionality. For example, the functionality can enable the user to take the mobile device 100 and its associated network while traveling. In particular, the mobile device 100 can extend Internet access (e.g., Wi-Fi) to other wireless devices in the vicinity. For example, mobile device 100 can be configured as a base station for one or more devices. As such, mobile device 100 can grant or deny network access to other wireless devices.
In some implementations, upon invocation of device functionality, the graphical user interface of the mobile device 100 changes, or is augmented or replaced with another user interface or user interface elements, to facilitate user access to particular functions associated with the corresponding device functionality. 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; likewise, touching of the email object 112 may cause the graphical user interface to present display objects related to various e-mail functions; touching the Web object 114 may cause the graphical user interface to present display objects related to various Web-surfing functions; and touching the 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 functionality may have corresponding “home” display objects displayed on the touch-sensitive display 102, and the graphical user interface environment of FIG. 1 can be restored by pressing the “home” display object.
In some implementations, the top-level graphical user interface can include additional display objects 106, such as a short messaging service (SMS) object, a calendar object, a photos object, a camera object, a calculator object, a stocks object, a weather object, a maps object, a notes object, a clock object, an address book object, a settings object, and an app store object 132. Touching the SMS display object can, for example, invoke an SMS messaging environment and supporting functionality; likewise, each selection of a display object can invoke a corresponding object environment and functionality.
Additional and/or different display objects can also be displayed in the graphical user interface of FIG. 1. For example, if the device 100 is functioning as a base station for other devices, one or more “connection” objects may appear in the graphical user interface to indicate the connection. In some implementations, the display objects 106 can be configured by a user, e.g., a user may specify which display objects 106 are displayed, and/or may download additional applications or other software that provides other functionalities 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 can be included to facilitate voice-enabled functionalities, such as phone and voice mail functions. In some implementations, an up/down button 184 for volume control of the speaker 160 and the microphone 162 can be included. The mobile device 100 can also include an on/off button 182 for a ring indicator of incoming phone calls. In some implementations, a loud speaker 164 can be included to facilitate hands-free voice functionalities, such as speaker phone functions. An audio jack 166 can also be included for use of headphones and/or a microphone.
In some implementations, a proximity sensor 168 can be included to facilitate the detection of the user positioning the mobile device 100 proximate to the user's ear and, in response, to disengage the touch-sensitive display 102 to prevent accidental function invocations. In some implementations, the touch-sensitive display 102 can be turned off to conserve additional power when the mobile device 100 is proximate to the user's ear.
Other sensors can also be used. For example, in some implementations, an ambient light sensor 170 can be utilized to facilitate adjusting the brightness of the touch-sensitive display 102. In some implementations, an accelerometer 172 can be utilized to detect movement of the mobile device 100, as indicated by the directional arrows. Accordingly, display objects and/or media can be presented according to a detected orientation, e.g., portrait or landscape. In some implementations, the mobile device 100 may include circuitry and sensors for supporting a location determining capability, such as that provided by the global positioning system (GPS) or other positioning systems (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 into the mobile device 100 or provided as a separate device that can be coupled to the mobile device 100 through an interface (e.g., port device 190) to provide access to location-based services.
The mobile device 100 can also include a camera lens and sensor 180. In some implementations, the camera lens and sensor 180 can be located on the back surface of the mobile device 100. The camera can capture still images and/or video.
The mobile device 100 can also include one or more wireless communication subsystems, such as an 802.11 b/g communication device 186, and/or a Bluetooth™ communication device 188. Other communication protocols can 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), etc.
In some implementations, the port device 190, e.g., a Universal Serial Bus (USB) port, or a docking port, or some other wired port connection, is included. The port device 190 can, for example, be utilized to establish a wired connection to other computing devices, such as other communication devices 100, network access devices, a personal computer, a printer, 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, the TCP/IP, HTTP, UDP and any other known protocol. In some implementations, a TCP/IP over USB protocol can be used, as described in U.S. Provisional Patent Application No. 60/945,904, filed Jun. 22, 2007, for “Multiplexed Data Stream Protocol,”, which is incorporated by reference here in its entirety.
FIG. 2 is a block diagram 200 of an example user interface of the mobile device 100 after invoking an application store display object (e.g., app store display object 132 of FIG. 1). For example, the user can access the app store display object 132 using the touch-sensitive display 102 (e.g., by pressing the app store display object 132), resulting in a transition to an application store interface. In some implementations, touching the app store display object 132 in FIG. 1 causes 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 several tabs. In particular, the menu portion 226 includes a featured tab 216, a categories tab 218, a top 25 tab 220, a search tab 222, and an updates tab 224. Each of the tabs in the menu portion 226 can be used to access different features of the application store, each of which will be described in greater detail below. In some implementations, other tabs can be provided and/or the tab order can vary, for example, as determined by the application store, the mobile device, or based on input received from another remote location.
The display portion 236 displays a featured interface 203 associated with the featured tab 216, which is shown as highlighted in the menu portion 226. The featured interface 203 includes a title bar 201. The title bar 201 includes a recently added button 202 and a staff favorites button 204. The recently added button 202 and staff favorites button 204 are shown as separate buttons. However, the 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 featured interface 203 also includes one or more application objects 240. The recently added button 202 is shown as currently selected (e.g., based on a user input to the touch-sensitive display 102). When the recently added button 202 is selected, the application objects 240 displayed correspond to applications that have been recently added to the application store.
In some implementations, the recently added applications are specified by a time period from inclusion of the particular application to the application store. For example, the recently added applications can include applications made available in the application store within the past thirty days. In some other implementations, however, the recently added applications can be a specified number (e.g., 25) of most recently added applications to the application store regardless of the actual elapsed time.
The application objects 240 can be ordered within the display portion 236 according to one or more criteria. For example, the application objects can be ordered by date added to the application store, alphabetically, or according to user ratings.
In particular, the application objects 240 shown in the display portion 236 include application objects 210, 212, and 214. Additionally, when the display portion 236 cannot display all of the application objects 240 at one time, the user can scroll 238 up or down to view additional application objects 240. While a scroll 238 is represented by a dotted arrow at a particular portion of the display portion 236, the user can scroll 238 from other points. In particular, the user can scroll by gesturing in a particular direction (e.g., up or down) across the touch-sensitive display 102.
Each application object 240 includes information associated with the particular application. For example, application object 210 includes application information 228. The application information 228 can include an image representing the application, the application name (e.g., “Application 1” for application object 210), a developer's name, and rating information. In some implementations, the rating information is represented by a specified number of stars. Stars are filled to indicate the average rating (e.g., three out of five 5) for the application. In some implementations, stars are partially filled to represent a finer degree of granularity of the average rating.
In some other implementation, different symbols are used to represent the rating information. For example, in some implementations, the small dots are used to represent unselected stars, which are replaced by stars up to the rating level, such that there are only stars equal to the average rating. In some implementations, the rating information also includes a number of reviews used (e.g., from individual users) to determine the average rating.
The application objects 240 also include a purchasing information 230. The purchasing information indicates whether the application is free or must be purchased (e.g., identified by “free” or “buy” labels). In some implementations, the purchasing information indicates the cost of the application (e.g., $5.00). In some other implementations, the application object 240 can indicate whether or not the user has already installed the particular application. For example, if the user has already installed the application identified by application object 210, the purchase information 230 can read “installed” instead of “free”. Alternatively, the purchase information 230 can read “uninstall” indicating that the user can uninstall the already installed application.
The application objects 240 can also include an “>” indicator (e.g., indicator 232 of application object 210). The indicator 232 indicates that selecting a particular application object (e.g., by touching application object 210) will transition the user interface to provide additional information about the selected application. The transition can be animated.
The display portion 236 can also include one or more advertisements. In the display portion 236, a first advertisement 206 and a second advertisement 208 are shown near the title bar 201. In other implementations, only a single advertisement is presented. Alternatively, additional advertisements can be presented. Additionally, while the advertisements are shown near the title bar 201, one or more advertisements can 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 selecting a staff favorites button (e.g., staff favorites button 204 in FIG. 2). As shown in FIG. 2, the title bar 201 including both the recently added button 202 and the staff favorites button 204. When the staff favorites button 204 is selected, the display portion 236 presents application objects 340 as part of the featured interface 303. The application objects 340 can include one or more of the recently added application objects 240 or can be distinct from the application objects 240.
In some implementations, the application objects 340 represent application objects selected by one or more individuals associated with the application store. For example, the staff favorites can be selected by a group of individuals within a specified time period. Thus, the staff favorites can change regularly, e.g., every 30 days. In some other implementations, the staff favorites are identified according to the applications receiving a highest ratings from a specified group of individuals. In some implementations, the number of application objects 340 identified as staff favorites is limited to a specified number (e.g., top 25 applications).
The application objects 340 can be ordered within the featured interface 303 according to one or more criteria. For example, the application objects can be ordered by date added to the application store, alphabetically, or by staff rating.
In particular, the application objects 340 shown in the display portion 236 include application objects 302, 304, and 306. Additionally, when the display portion 236 cannot display all of the application objects 340 at one time, the user can scroll 238 up or down to view additional application objects 340 as described above with respect to FIG. 2.
Each application object 340 includes information associated with the respective application. Similar to the application information 228 described above with respect to FIG. 2, the application information can include an image representing the application, the application name (e.g., “Application 4” for application object 302), a developer's name, and rating information. In some implementations, the rating information is represented by a specified number of stars identifying an average rating for the corresponding application.
The application objects 340 also include purchasing information. The purchasing information indicates whether the “staff favorite” applications are free or must be purchased. In some implementations, the purchasing information indicates the cost of the particular application (e.g., $5.00). In some other implementations, the application object 340 indicates whether or not the user has already installed the particular application. For example, if the user has already installed the application identified by application object 302, the purchase information can read “installed” instead of “free”. Alternatively, the purchase information can read “uninstall” indicating that the user can uninstall the already installed application.
The application objects 340 can also include an “>” indicator (e.g., indicator 232 of FIG. 2). The indicator indicates that selecting a particular application object (e.g., by touching application object 302) will transition the user interface to provide additional information about the selected application. The transition can be animated.
The featured interface 303 can also include one or more advertisements. In particular, the display portion 236, presents a first advertisement 206 and a second advertisement 208 near the title bar 201. In other implementations, only a single advertisement is presented. Alternatively, additional advertisements can be presented. Additionally, while the advertisements are shown near the title bar 201, one or more advertisements can be presented at different locations on the display portion 236.
In either FIG. 2 or FIG. 3, a user selection of an application object (e.g., one of application objects 240 or 340, respectively), the user interface can transition to provide additional information regarding 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, an application information interface 403 corresponds to the user selection of application object 210 of FIG. 2.
The application information interface 403 includes an information display portion 410 and the menu portion 226. The menu portion 226 includes the featured tab 216, the categories tab 218, the top 25 tab 220, the search tab 222, and the updates tab 224. In some implementations, 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. Additionally, 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 (e.g., the user interface for the app 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 causes the user interface to transition into an interface for notifying another person about the particular application. The interface for notifying another person about the selected application is described in greater detail below with respect to FIG. 5.
The display portion 410 also includes application information 406, purchase information 408, an application screenshot 412, and reviews 414. The application information 406 includes, for example, the application name and the developer. The application information 406 can also include an image representing the particular application as well as other information, for example, the date the application was added to the application store. The application information 406 can also include a brief description of the application.
The purchase information 408 identifies whether the selected application is free or available for purchase. Alternatively, the purchase information 408 can indicate the price of the application (e.g., $5.00). In some implementations, the user can redeem credit to purchase the application. For example, the user can have a gift card, a coupon, or other credit that can be used toward purchasing applications on the application store. In some implementations, the user is presented with a “redeem” button in the application information interface. Touching the redeem button generates an interface where the user can input account information corresponding to the credit to be applied.
Additionally, in some implementations, touching the purchase information 408 initiates a process for downloading the application. For example, if the application is free, the download process can begin without further user input. Alternatively, if purchase is required, a user account can be accessed to purchase the application. In some implementations, the user can redeem a coupon or similar credit to purchase the application, In some other implementations, the user is required to provide account or other authentication information before purchasing the application.
In some alternative implementations, the purchase information 408 indicates whether the user has already installed the application (e.g., by including text “installed” or “uninstall” in the purchase information 408).
The screenshot 412 can provide a screen capture image of the application interface. In some implementations, a more detailed description of the application is provided in place of, or in addition to, the screenshot 412. For example, the detailed description can include features of the application and other information. In some implementations, more than one screenshot 412 is provided. Alternatively, in some other implementations, additional screenshots can be provided as thumbnails that can be displayed when selected by the user.
The reviews 414 includes rating information as well as individual reviews of the application. The rating information can include a graphic illustration of an average rating (e.g., using a star rating). Additionally, the number of individual reviews used to determine the average rating can also be provided. The average rating can be followed by one or more individual reviews of the application. In some implementation all reviews are listed. In some other implementations, only a specified number of reviews are listed. In some implementations, the user can scroll 238 to view additional reviews that are not presented within the visible portion of the application information interface 403.
The reviews 414 portion of the application information interface 403 can also include a review button 418 that allows a user to provide a review or other report associated with the application. Providing a review of the application is described below with respect to FIGS. 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 can be presented in response to the user selecting the “tell a friend” button 404 in FIG. 4.
The notification interface 502 includes a title bar 501. The title bar 501 identifies the notification interface 502 (e.g., as “tell a friend”). Additionally, the title bar 501 includes a back button 504 and a send button 506. The back button 504 can cancel the notification interface 502 and allow the user to return to a preceding user interface (e.g., the application information interface 403). The send button 506 allows the user to send application information to another person.
The notification interface 502 can provide a pre-configured e-mail message that includes a link to the application information in the application store. The 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 can input, for example, an e-mail address or a name corresponding to a contact or address book entry. The “from” field 510 allows the user to identify for the recipient the sender of the notification. In some implementations, the “from” field 510 is automatically populated based on user profile or account information. In some other implementations, the “from” field 510 is not presented to the user, but instead is automatically added to the notification. The “subject” field 512 allow the user to specify a subject for the recipient, for example, “check out this application”. In some implementations, the subject field 512 is automatically populated by the application store, for example, with the name of the application or other text.
The text box 514 provides additional space for the user to provide additional text to the user (e.g., a message body). In some implementations, the text box 514 has a maximum number of allowed characters for user input.
Input to each field and the text box 514 can be provided using keyboard 516. The keyboard 516 provides a full QWERTY layout of keys for typing. The user inputs text with the touch-sensitive display 102 by touching individual keys according to the desired text. After inputting information into one or more fields, the user can send the notification by touching the send button 506 as described above. In some implementations, sending the notification causes the user interface to transition to the 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 including a menu 602 for providing information associated with a selected application. In particular, a portion of the application information interface 403 can be overlaid with the menu 602. The menu 602 can be partially transparent such that the overlaid portion of the application information interface 403 is partially visible. In some implementations, the menu 602 is presented in response to the user selecting the review button 418 in the application information interface 403. In some alternative implementations, the menu 602 replaces the application information 403 entirely instead of being provided as a partial overlay.
The menu 602 includes a write a review button 604, a report a problem button 606, and a cancel button 608. The write a review button 604 allows the user to write a review for the application of the application information interface 403. In particular, when the user touches the write a review button 604, the user interface transitions into a review interface (e.g., using an animated transition). The review interface is described in greater detail below with respect to FIG. 7.
The report a problem button 606 allows the user to report a problem with the application identified in the application information interface 403. In particular, when the user touches the report a problem button 604, the user interface transitions into a report interface (e.g., using an animated transition). The report interface is described in greater detail below with respect to FIG. 8.
The 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 review interface 702 presented, for example, in response to the user selecting the write a review button 604 (FIG. 6).
The review interface 702 includes a title bar 701 identifying the interface as a review interface. The title bar 701 further includes a back button 704 and a send button 706. The back button 702 can cancel the review interface 702 and allow the user to return to a preceding user interface (e.g., the application information interface 403). The send button 706 allows the user to submit the review.
The review interface 702 includes a rating 708. The rating 708 allows the user to assign a rating value to the application. For example, the user can assign a specified number of stars to the application out of a maximum possible (e.g., from zero to five stars). In particular, the user can assign stars using a gesture motion on the touch-sensitive interface 102. For example, the user can slide a finger in a first direction to incrementally increase the number of stars (to a maximum number, e.g., 5) or in a second direction to incrementally reduce the number of stars (to a minimum number, e.g., zero).
The review interface 702 also includes a “from” field 710, a “title” field 712, and a review text box 714. The “from” field 710 allows the user to identify who is providing the review. In some implementations, the “from” field 710 is automatically populated based on user profile or account information. In some other implementations, the “from” field 710 is not presented to the user, but instead is automatically added to the review. The “title” field 712 allows the user to identify an occupation or capacity in which they are providing the review. In some implementations, the “title” field 712 is not provided.
The text box 714 provides additional space for the user to provide review text beyond the rating value. In some implementations, the text box 714 has a maximum number of allowed characters for user input.
Input to each field and the text box 714 can be provided using keyboard 516. The keyboard 516 provides a full QWERTY layout of keys for typing. The user inputs text with the touch-sensitive display 102 by touching individual keys according to the desired text. After inputting information into one or more fields, the user can submit the review by touching the send button 706 as described above. In some implementations, submitting the review 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 on a selected application. In particular, FIG. 8 shows a reporting interface 802 presented, for example, in response to the user selecting the report a problem button 606 (FIG. 6).
The reporting interface 802 includes a title bar 801 identifying the interface as a reporting interface. The title bar 801 further includes a back button 804 and a send button 806. The back button 802, for example, can cancel the reporting interface 802 and allow the user to return to a preceding user interface (e.g., the application information interface 403). The send button 806 allows the user to submit the report.
The review interface 802 includes menu buttons with suggested problems to report. In particular, the review interface 802 includes a report a bug button 808, a report as offensive button 810, and a concern not listed button 812. The user can select one of the menu buttons by touching a particular menu button in the review interface 802. In some implementations, when a user selects a particular menu button, the selected menu button is highlighted. In some other implementations, when the user selects a menu button an icon is displayed to indicate selection, for example, a checkmark.
Additionally, a text box 814 is presented. The text box 814 allows the user to optionally describe the reported problem. In some implementations, the text box 814 has a maximum number of allowed characters for user input.
Input to the text box 814 can be provided using keyboard 516. The keyboard 516 provides a full QWERTY layout of keys for typing. The user inputs text with the touch-sensitive display 102 by touching individual keys according to the desired text. After inputting information into the text box 814, the user can submit the report by touching the 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 an application store following selection of a categories tab (e.g., categories tab 218 of FIG. 2). For example, the user can access the app store display object 132 using the touch sensitive display 102 (e.g., by pressing the app store display object 132), resulting in a transition to an app store interface. In some implementations, touching the app store display object 132 in FIG. 1 causes an animated transition to the app store interface.
The user interface for the app store includes a display portion 902 and a menu portion 226. The menu portion 226 can include several tabs. In particular, the menu portion 226 includes the featured tab 216, the categories tab 218, the top 25 tab 220, the search tab 222, and the updates tab 224. Each of the tabs in the menu portion 226 can be used to access different features of the application store.
The display portion 236 displays a categories interface 903 associated with the categories tab 218, which is shown as highlighted in the display portion 236. The categories interface 903 includes a title bar 901 identifying the user interface as a categories interface. In some implementations, the title bar 903 includes one or more buttons, for example, a back button allowing the user to access a 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.
The categories interface 903 includes one or more category buttons. In particular, the categories interface 903 includes a games button 904, entertainment button 906, news button 908, productivity button 910, sports button 912, and travel button 914. The displayed categories can be arranged in any order (e.g., alphabetical, by popularity, etc.). Additionally, other categories can be displayed in place of or in addition to the categories shown. In some implementations, the user can view additional categories by scrolling 238 the category buttons.
Each category button allows the user to transition to an interface providing application objects associated with the particular category. For example, a selection of the games button 904 can cause the categories interface to transition to a game objects interface that includes one or more application objects corresponding to games or otherwise associated with the games category.
FIG. 10 is a block diagram 1000 of an example user interface of the mobile device 100 illustrating application objects of a particular selected category. In particular, FIG. 10 shows a games objects interface 1003 presented in response to a user category selection (e.g., a user selection of the games button 904 in FIG. 9).
The user interface includes a display portion 1002 and a menu portion 226. The menu portion 226 includes several tabs. In particular, the menu portion 226 includes a featured tab 216, a categories tab 218, a top 25 tab 220, a search tab 222, and an updates tab 224. In particular, the categories tab 218 is shown as highlighted.
The display portion 1002 displays a games objects interface 1003 associated with the selection of a games category. The games objects interface 1003 includes a title bar 1001 including recently added button 1004 and staff favorites button 1006. The recently added button 1004 and staff favorites button 1006 are shown as separate buttons, however, they can take other forms including, for example, a single toggle button that can be switched from one to the other.
The games objects interface 1003 also includes one or more games objects 1040. The recently added button 1004 is shown as currently selected (e.g., based on a user input to the touch-sensitive display 102). When the recently added button 1004 is selected, the games objects 1040 displayed correspond to game applications that have been recently added to the application store in similar manner as described above in FIG. 2, but with respect to games objects. Similarly, when the staff favorites button 1006 is selected or toggled, the games objects 1040 displayed correspond to game applications that have been selected by one or more individuals associated with the app store in a similar manner as 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 one time, the user can scroll 238 up or down to view additional game objects 1040.
Each game object 1040 includes information associated with the particular game application. For example, game object 1012 includes game application information 1018. The game application information 1018 can include an image representing the game application, the game application name (“Game 1”), a developer's name, and rating information. In some implementations, the rating information is represented by a specified number of stars. Stars are filled to indicate the average rating (e.g., three out of five) of the game. In some implementations, stars can be partially filled to represent a finer degree of granularity of the average rating.
The game objects 1040 also include a purchasing information 1022. The purchasing information 1022 indicates whether the application is free or must be purchased. In some implementations, the purchasing information indicates the cost of the game (e.g., $5.00). In some other implementations, each game object (e.g., game objects 1012, 1014, and 1016) can indicate whether or not the user has already installed the particular game. For example, if the user has already installed the game identified by game object 1012, the purchase information 1022 can read “installed” instead of “free”. Alternatively, the purchase information 122 can read “uninstall” indicating that the user can uninstall the already installed game application.
The game objects 1040 can also include an “>” indicator 1020. The indicator 1020 indicates that selecting a particular game object (e.g., by touching game object 1012) transitions the user interface to provide additional information about the selected game application. The transition can be animated.
The display portion 1002 can also include one or more advertisements. In the display portion 1002, a first advertisement 1008 and a second advertisement 1010 arc shown near the title bar 1001. In other implementations, only a single advertisement is presented. Alternatively, additional advertisements can be presented. Additionally, while the advertisements are shown near the title bar 1001, one or more advertisements can be presented at different locations on the display portion 1002.
The user can select a particular game object 1040 in order to transition to provide information regarding the game associated with the selected game object. The game information is provided in a similar manner to the application information interface 403 described above with respect to FIG. 4.
FIG. 11 is a block diagram 1100 of an example user interface of the mobile device 100 illustrating an application store following selection of a “top 25” tab (e.g., “top 25” tab 220). For example, the user can access the app store display object 132 using the touch sensitive display 102 (e.g., by pressing the app store display object 132), resulting in a transition to an app store interface. In some implementations, touching the app store display object 132 in FIG. 1 causes an animated transition to the app store interface.
The user interface for the app store includes a display portion 1102 and the menu portion 226. The menu portion 226 can include several tabs. In particular, the menu portion 226 includes the featured tab 216, the categories tab 218, the top 25 tab 220, the search tab 222, and the updates tab 224. Each of the tabs in the menu portion 226 can be used to access different features of the application store.
The display portion 1102 displays a “top 25” interface 1103 associated with the “top 25” tab 220, which is shown as highlighted in the display portion 236. The top 25 interface 1103 includes a title bar 1101 identifying the user interface as a 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 (as is shown by the highlighting in FIG. 11), the “top 25” interface 1103 displays application objects 1140 including those associated with applications available for free. When the “hide free” button 1106 is selected, the “top 25” interface 1103 only displays application objects that require payment.
The “top 25” interface 1103 includes application objects 1140. In particular, 25 application objects 1140 are listed. However, when all 25 application objects 1140 cannot be displayed in the display portion 1102, the user can 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 can be provided to allow the user to view another group of application objects (e.g., a “next 25” application objects).
The application objects 1140 shown include application objects 1112, 1114, and 1116. The application objects 1140 are presented in ranked order. Thus, application object 1112 is ranked 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 the application object 1112 as being ranked number one in the list of application objects 1140.
Each application object 1140 includes information associated with the particular application. For example, application object 1112 includes application information 1122. The application information 1122 can include an image representing the application, the application name (“Application 5”), a developer's name, and rating information. In some implementations, the rating information is represented by a specified number of stars. Stars are filled to indicate the average rating (e.g., 3/5) of the game. In some implementations, stars can be partially filled to represent a finer degree of granularity of the average rating.
The application objects 1140 also include a purchasing information 1124. The purchasing information 1124 indicates whether the application is free or must be purchased. In some implementations, the purchasing information indicates the cost of the application (e.g., $5.00). In some other implementations, each application object (e.g., application objects 1112, 1114, and 1116) can indicate whether or not the user has already installed the particular application. For example, if the user has already installed the application identified by application object 1112, the purchase information 1124 can read “installed” instead of “free”. Alternatively, the purchase information 1124 can read “uninstall” indicating that the user can uninstall the already installed application.
The application objects 1140 can also each include an “>” indicator 1124. The indicator 1124 indicates that selecting a particular application object (e.g., by touching application object 1112) will transition the user interface to provide additional information about the selected application. The transition can be animated.
The display portion 1102 can also include one or more advertisements. In the display portion 1102, a first advertisement 1108 and a second advertisement 1110 are shown near the title bar 1101. In other implementations, only a single advertisement is presented. Alternatively, additional advertisements can be presented. Additionally, while the advertisements are shown near the title bar 1101, one or more advertisements can be presented at different locations on the display portion 1102.
Selecting a particular application object in the ranked list of application objects 1140 transitions the user interface to an interface providing information regarding the application associated with the selected application object. The application information is provided in a similar manner to the application information interface 403 described above with respect to FIG. 4.
FIG. 12 is a block diagram 1200 of an example user interface of the mobile device 100 illustrating an application store “top 25” with free applications hidden. The user interface for the app store includes a display portion 1202 and the menu portion 226. The menu portion 226 can include several tabs. In particular, the menu portion 226 includes the featured tab 216, the categories tab 218, the top 25 tab 220, the search tab 222, and the updates tab 224. Each of the tabs in the menu portion 226 can be used to access different features of the application store.
The display portion 1202 displays a “top 25” interface 1203 associated with the “top 25” tab 220, which is shown as highlighted in the display portion 236. The top 25 interface 1103 includes a title bar 1201 identifying the user interface as a “top 25” interface. The title bar 1201 also includes the “show free” button 1104 and the “hide free” button 1106. In particular, the “hide free” button 1106 is selected, as shown by the highlighting in FIG. 12. When the “hide free” button 1106 is selected, the “top 25” interface 1203 only displays application objects which require payment.
The “top 25” interface 1203 includes application objects 1240. In particular, up to 25 application objects 1240 are listed. However, when there are more application objects 1240 than can be displayed in the display portion 1202, the user can 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 can be provided to allow the user to view another group of application objects (e.g., a “next 25” application objects).
The application objects 1240 shown include application objects 1204, 1206, and 1208. The application objects 1240 are presented in a ranked order. Thus, 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 1210 that identifies the application object 1204 as being ranked number one in the list of application objects 1240. The ranking can be based, for example, on the average star rating of each application or some other criteria.
Each application object 1240 includes information associated with the particular application. For example, the application objects 1240 can include an image representing the application, the application name (e.g., “Application 2”), a developer's name, and rating information.
The application objects 1240 also include a purchasing information 1212. In particular, since the “hide free” button 1106 is selected or toggled, each of the application objects 1240 requires payment. Selecting a particular application object in the ranked list of application objects 1240 transitions the user interface to an interface providing information regarding the application associated with the selected application object. The application information is provided in a similar manner to the application information interface 403 described above with respect to FIG. 4.
FIG. 13 is a block diagram 1300 of an example user interface of the mobile device 100 illustrating an application store following selection of a search tab. For example, the user can access the app store display object 132 using the touch sensitive display 102 (e.g., by pressing the app store display object 132), resulting in a transition to an app store interface. In some implementations, touching the app store display object 132 in FIG. 1 causes an animated transition to the app store interface.
The user interface for the app store includes a display portion 1302 and the menu portion 226. The menu portion 226 can include several tabs. In particular, the menu portion 226 includes the featured tab 216, the categories tab 218, the top 25 tab 220, the search tab 222, and the updates tab 224. Each of the tabs in the menu portion 226 can be used to access different features of the application store.
In particular, the display portion 1302 displays a search interface 1303 associated with the search tab 222, which is shown as highlighted in the display portion 236. The search interface 1303 includes a title bar 1201 identifying the user interface as an application search interface.
The search interface 1303 includes a search field 1304 and a search button 1306. The search field 1304 allows a user to input one or more search terms. For example, the user can input keywords identifying a particular application, developer, category, or other keywords. The search button 1306 executes an application search based on the user input to the search field 1304. For example, the user can execute the search by touching the search button 1306.
The user can input search terms into the search field 1304 using keyboard 516. The keyboard 516 provides a full QWERTY layout of keys for typing. The user inputs text with the touch sensitive display 102 by touching individual keys according to the desired text.
Executing a search (e.g., by touching the search button 1306) transitions the user interface to an interface providing information regarding one or more applications associated with the input search terms. The application information is provided in a similar manner to the application information interface 403 (e.g., as a list of application objects) as described above with respect to FIG. 4.
FIG. 14 is a block diagram 1400 of an example user interface of the mobile device 100 after invoking an application store display object and illustrating available updates. For example, the user can access the app store display object 132 using the touch sensitive display 102 (e.g., by pressing the app store display object 132), resulting in a transition to an application store interface. In some implementations, touching the application store display object 132 in FIG. 1 causes an animated transition to the app store interface.
The user interface for the application store includes the display portion 236 and the menu portion 240. The menu portion 226 includes several tabs. In particular, the menu portion 226 includes the featured tab 216, the categories tab 218, the top 25 tab 220, the search tab 222, and the updates tab 224. Each of the tabs in the menu portion 226 can be used to access different features of the application store.
The display portion 236 displays a featured interface 203 associated with the featured tab 216, which is shown as highlighted in the display portion 236. The featured interface 203 including application objects is described above with respect to FIG. 2.
The updates tab 224 includes an updates badge 1402. The updates badge 1402 identifies whether or not there are updates available to the applications installed on the mobile device 100. The user can identify whether there are available updates without selecting the updates tab 224. For example, the updates badge 1402 can be a symbol or graphic associated with the updates tab 224. As shown in FIG. 14, the updates badge 1402 is a circle with a number inside that is superimposed over a portion of the graphic identifying the updates tab 224. Additionally, the updates badge 1402 can be visible only when an update is available. In some implementations, the updates badge indicates the number of available updates (e.g., by including a number in the badge). For example, updates badge 1402 shows that there are two updates available.
FIG. 15 is a block diagram of an example user interface 1500 of the mobile device 100 illustrating an application store following selection of an updates tab (e.g., updates tab 224). For example, the user can access the app store display object 132 using the touch sensitive display 102 (e.g., by pressing the app store display object 132), resulting in a transition to an app store interface. In some implementations, touching the app store display object 132 in FIG. 1 causes an animated transition to the app store interface.
The user interface for the app store includes a display portion 1102 and the menu portion 226. The menu portion 226 can include several tabs. In particular, the menu portion 226 includes the featured tab 216, the categories tab 218, the top 25 tab 220, the search tab 222, and the updates tab 224. Each of the tabs in the menu portion 226 can be used to access different features of the application store.
The display portion 1502 displays an updates interface 1503 associated with the updates tab 224, which is shown as highlighted in the display portion 236. The updates interface 1503 includes a title bar 1501 identifying the user interface as an updates interface. The title bar 1501 also includes an optional back button 1504. The back button 1504 allows the user to exit the updates interface 1503 or the application store and to return to an earlier user interface. Alternatively, the user can exit the application store and return to the “home” interface shown in FIG. 1 by pressing button 120.
The updates interface 1503 includes update objects 1540. In particular, two update objects 1506 and 1508 are shown in the updates interface 1503, which corresponds to the number of updates identified by the updates badge 1402 in FIG. 14. In some other implementations, there are more update objects 1540 than are displayable in the display portion 1502. When there are additional update objects 1540 than can be displayed, the user can scroll to view additional update objects. Additionally, in some implementations, when the user can be presented with a button to allow the user to view another group of update objects (e.g., a next 25 update objects) either after scrolling or without any scrolling.
In some implementations, the update objects 1540 identify particular updates available for applications already installed on the mobile device 100. For example, the update object 1506 identifies an update to “Application A” while the update object 1508 identifies an update to “Application B”. The user can select the particular update object (e.g., by touching the update object or an associated update button 1514). Selecting the update object can indicate the update download. Alternatively, selecting the update object can transition the updates interface 1503 to an information interface that provides additional information about the update, after which the user can decide whether or not to get the update. In some implantations, a select all button is provided in the updates interface 1503 allowing the user to get all application updates associated with the displayed update objects 1540.
Upon selecting one or more of the update objects 1503 for download, the updates interface 1503 can end, restoring a previous interface or returning the user to the home screen. Alternatively, when a user selects a particular update object (e.g., update object 1506), that object disappears from the update interface 1503 (e.g., only the update object 1508 would remain).
FIG. 16 is a block diagram 1600 of an example user interface of the mobile device 100 illustrating an application download. For example, the user can select a particular application in the app store, for example, as described above. When the user selects an application object to download, the user interface can transition to the home screen including display objects 104 and 106 as described above with respect to FIG. 1.
Additionally, a download object 1602 is presented as one of the display objects 106. The download object presents a dimmed or shaded object placeholder for the application being downloaded. The download object 1602 is positioned in the next available location relative to the other display objects 106. In particular, the download object includes a “loading . . . ” indicator instead of the application title as well as a loading bar. The loading bar can animate to show the progress of the download. Once the download of the application is complete, the “loading . . . ” changes to the application title and the image presented in the download object 1602 is modified to correspond to the downloaded application.
FIG. 17 is a flowchart illustrating an example process 1700 for navigating an application store using a mobile device. An input is provided to a mobile device requesting an application management interface (step 1702). For example, the user can select (e.g., using a touch-sensitive display) an application store object as shown, e.g., in FIG. 1.
An application management interface is presented (step 1704). For example, one or more user interfaces can be presented in association with an application store. The application management interface can include buttons, toggles, or other user activated elements that allow the user to navigate between different user interfaces, identify and select application objects, and review and report applications as shown, for example, in FIGS. 2-15.
An input is received selecting a particular application for installation (step 1706). The input can be received, for example, from a user touching a touch-sensitive display (e.g., touch-sensitive display 102 of FIG. 1). For example, the user can search for or identify an application in the presented application management interface using different criteria or listings provided by the application management interface. The user can select the particular application using a touch-sensitive display by touching a displayed application object corresponding to the particular application.
In some other implementations, other user inputs can be received. For example, an input can be received reviewing an application, reporting a problem with an application, notifying others about an application, or updating a previously installed application.
A determination is made as to whether a payment is required for the selected application (step 1708). Some applications can be free to any user while other applications require payment. If payment is not required, the application is installed on the mobile device (step 1710).
If payment is required, the payment is collected (step 1712). The payment can be received, for example, by charging a user account, redeeming a coupon or other credit, or by receiving an electronic payment (e.g., by credit card) from the user. In some implementations, authentication is performed to verify the user.
The application is presented in a home screen of the mobile device (step 1714). The application can be presented as an object on the home screen. In some implementations, while the application is being installed, a placeholder object is positioned on the home screen (e.g., in a next available location on the home screen). The placeholder object can be dimmed and include other indications that the application is not yet available (e.g., providing loading text). The placeholder object can indicate the progress of the installation (e.g., using a loading bar animation).
In some implementations, the application store can include one or more applications that are location specific. For example, corporations or other entities can develop and provide applications within the network, which are not accessible to those outside the local network. In some other implementations, parental controls can be activated (e.g., using settings for the mobile device) to limit access to applications or particular types of applications in the application store.
FIG. 18 is a block diagram 1800 of an example user interface of the mobile device 100 illustrating an application available for deletion. The user can identify applications available for deletion, for example, by selecting a display object 106 (e.g., using a touch-sensitive display). For example, the user can touch and hold a display object 106 corresponding to a particular application (e.g., application 1802) for a specified period of time to enter an editing mode.
In response to holding the application, the held application along with one or more other display objects 106 can become editable (e.g., movable to other locations on the touch-sensitive display 102). Some display objects 106 can be deleted. The system can present an indicator in the editing mode identifying those display objects, for example, a badge with an “X” presented for those display objects 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 the badge (e.g., by touching the “X” on the touch-sensitive display 102) in order to initiate a deletion process for the application.
FIG. 19 is a block diagram 1900 of an example user interface of the mobile device 100 illustrating a rating prompt 1902. When a user selects an application for deletion (e.g., application 1802 of FIG. 18), the rating prompt 1902 can be displayed, for example, on the user-interface provided by the touch-sensitive display 102. In sonic implementations, the portion of the user interface outside of the rating prompt 1902 can be dimmed relative to the rating prompt 1902.
The rating prompt 1902 can include a request to review the application, a rating scale (e.g., a set of stars), and one or more buttons (e.g., to submit a rating or to decline rating the application). The user can provide an input (e.g., using the touch-sensitive display 102) that indicates a particular rating (e.g., by selecting a particular number of stars). Once the user has selected a particular number of stars, the user can submit the rating using, e.g., a “rate” button. Alternatively, the user can decline to rate the application, for example, by selecting a “no thanks” button.
FIG. 20 is a flowchart illustrating an example process 2000 for deleting an installed application using a mobile device. An input is received to delete an installed application (step 2002). The input can be received, for example, from a user touching a touch-sensitive display (e.g., touch-sensitive display 102 of FIG. 18). For example, the user can select a particular application and provide an input indicating that the selected application should be deleted. In some implementations, the user can enter an editing mode that allows the user to identify applications that can be deleted as well as select a particular application for deletion.
In some implementations, when a user selects an application for deletion, a confirmation prompt can be presented to the user. The confirmation prompt can indicate that continuing will delete the application including any saved data associated with the application. The conformation prompt can further provide an opportunity for the user to cancel the deletion process.
A rating prompt is presented (step 2004). The ratings prompt can be presented prior to completing the deletion of the selected application. The ratings prompt allows the user to provide feedback for the application being deleted. For example, the user can input a rating for the application (e.g., by selecting a specified number of stars).
A determination is made as to whether the user rated the application (step 2006). The determination can be made according to one or more user inputs. For example, based on whether the user entered a rating or selected a button indicating that a rating has been provided. Alternatively, the user input can indicate that no rating is being provided. For example, the user can select a button indicating that no rating is being provided.
If the determination is made that a rating has been provided, the rating information is sent to a remote location (step 2008). For example, the rating information can be sent to an application store located at a remote location (e.g., the application store described above). After sending the rating information, the application is removed and the user interface can return to a home screen or other default interface (step 2010).
If the determination is made that a rating has not been provided, the application is removed and the user interface can return to a home 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, for example, communicate over one or more wired and/or wireless networks 2110 in data communication. For example, a wireless network 2112, e.g., a cellular network, can communicate with a wide area network (WAN) 2114, such as the Internet, by use of a gateway 2116. Likewise, an access point 2118, such as an 802.11g wireless access point, can 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 100 a can place and receive phone calls (e.g., using VoIP protocols), send and receive e-mail messages (e.g., using POP3 protocol), and retrieve electronic documents and/or streams, such as web pages, photographs, and videos, over the wireless network 2112, gateway 2116, and wide area network 2114 (e.g., using TCP/IP or UDP protocols). Likewise, the mobile device 100 b can place and receive phone calls, send and receive e-mail 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 this configuration, the mobile device 100 can be referred to as a “tethered” device.
The mobile devices 100 a and 100 b can also establish communications by other means. For example, the wireless device 100 a can communicate with other wireless devices, e.g., other wireless devices 100, cell phones, etc., over the wireless network 2112. Likewise, the mobile devices 100 a and 100 b can establish peer-to-peer communications 2120, e.g., a personal area network, by use of one or more communication subsystems, such as the Bluetooth™ communication device 188 shown in FIG. 1. Other communication protocols and topologies can also be implemented.
The mobile device 100 can, for example, communicate with one or more services 2130, 2140, 2150, and 2160 and/or one or more content publishers 2170 over the one or more wired and/or wireless networks 2110. For example, a navigation service 2130 can provide navigation information, e.g., map information, location information, route information, and other information, to the mobile device 100. In the example shown, a user of the mobile device 100 b has invoked a map functionality, e.g., by pressing the maps object 144 on the top-level graphical user interface shown in FIG. 1, and has requested and received a map for the location “1 Infinite Loop, Cupertino, Calif.”
A messaging service 2140 can, for example, provide e-mail and/or other messaging services. A media service 2150 can, for example, 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 over the one or more wired and/or wireless networks 2110. For example, an application store 2170, can be accessed by the mobile device 100 to provide applications. Such access can be provided by invocation of a web browsing function or application (e.g., a browser) in response to a user touching a web object on the home screen of the mobile device 100.
Exemplary 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 can include a memory interface 2202, one or more data processors, image processors and/or central processing units 2204, and a peripherals interface 2206. The memory interface 2202, the one or more processors 2204 and/or the peripherals interface 2206 can be separate components or can be integrated in one or more integrated circuits. The various components in the mobile device 100 can be coupled by one or more communication buses or signal lines.
Sensors, devices and subsystems can be coupled to the peripherals interface 2206 to facilitate multiple functionalities. For example, a motion sensor 2210, a light sensor 2212, and a proximity sensor 2214 can be coupled to the peripherals interface 2206 to facilitate the orientation, lighting and proximity functions described with respect to FIG. 1. Other sensors 2216 can also be connected to the peripherals interface 2206, such as a positioning system (e.g., GPS receiver), a temperature sensor, a biometric sensor, or other sensing device, to facilitate related functionalities.
A camera subsystem 2220 and an optical sensor 2222, e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, can be utilized to facilitate camera functions, such as recording photographs and video clips.
Communication functions can be facilitated through one or more wireless communication subsystems 2224, which can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the communication subsystem 2224 can depend on the communication network(s) over which the mobile device 100 is intended to operate. For example, a mobile device 100 may include communication subsystems 2224 designed to operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, and a Bluetooth™ network. In particular, the wireless communication subsystems 2224 may include hosting protocols such that the device 100 may be configured as a base station for other wireless devices.
An audio subsystem 2226 can be coupled to a speaker 2228 and a microphone 2230 to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions.
The I/O subsystem 2240 can include a touch screen controller 2242 and/or other input controller(s) 2244. The touch-screen controller 2242 can be coupled to a touch screen 2246. The touch screen 2246 and touch screen controller 2242 can, for example, detect contact and movement or break thereof using any of multiple touch sensitivity 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.
The other input controller(s) 2244 can be coupled to other input/control devices 2248, such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) can include an up/down button for volume control of the speaker 2228 and/or the microphone 2230.
In one implementation, a pressing of the button for a first duration may disengage a lock of the touch screen 2246; and a pressing of 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 able to customize a functionality of one or more of the buttons. The touch screen 2246 can, for example, also be used 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 can include the functionality of an MP3 player, such as an iPod™. The mobile device 100 may, therefore, include a 32-pin connector that is compatible with the iPod™. Other input/output and control devices can also be used.
The memory interface 2202 can be coupled to memory 2250. The memory 2250 can 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 can store an operating system 2252, such as Darwin, RTXC, LINUX, UNIX, OS X, 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 dependent tasks. In some implementations, the operating system 2252 can be a kernel (e.g., UNIX kernel).
The memory 2250 may also store communication instructions 2254 to facilitate communicating with one or more additional devices, one or more computers and/or one or more servers. The memory 2250 may include graphical user interface instructions 2256 to facilitate graphic user interface processing including presentation, navigation, and selection within an application store as shown in FIGS. 2-16; sensor processing instructions 2258 to facilitate sensor-related processing and functions; phone instructions 2260 to facilitate phone-related processes and functions; electronic messaging instructions 2262 to facilitate electronic-messaging related processes and functions; web browsing instructions 2264 to facilitate web 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 processes and instructions; camera instructions 2270 to facilitate camera-related processes and functions; and/or other software instructions 2272 to facilitate other processes and functions.
Each of the above identified instructions and applications can correspond to a set of instructions for performing one or more functions described above. These instructions need not be implemented as separate software programs, procedures or modules. The memory 2250 can include additional instructions or fewer instructions. Furthermore, various functions of the mobile device 100 may be implemented in hardware and/or in software, including in 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 them. The term “data processing apparatus” encompasses 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, 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 performing instructions and one or more memory devices 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., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, to name just 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, e.g., 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 kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can 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 can 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”), e.g., the Internet.
The computing system can 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. Moreover, 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 subcombination or variation of a subcombination.
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 certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation 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 actions recited in the claims can be performed in a different order and still achieve desirable results.

Claims (39)

What is claimed is:
1. A computer-implemented method, comprising:
displaying, on a display of a mobile device, an application management interface that includes:
a set of application objects corresponding to respective applications from an application store server that are available for installation on the mobile device;
a first user activated element associated with only displaying application objects that require payment, and
a second user activated element associated with displaying application objects that do not require payment;
detecting selection of the first user activated element associated with only displaying application objects that require payment;
in response to detecting selection of the first user activated element, ceasing to display application objects that do not require payment and displaying at least some of the application objects that require payment;
detecting a selection of an application object from the displayed application objects;
receiving, from the application store server, an application that corresponds to the selected application object; and
installing, on the mobile device, the application that corresponds to the selected application object.
2. The method of claim 1, further comprising:
displaying a set of application icons on a home screen; and
receiving a request to display the application management interface, wherein the application management interface is displayed in response to receiving the request.
3. The method of claim 2, wherein receiving the request to display the application management interface includes receiving an input directed to a selection of an app store icon, and wherein the app store icon is included in the displayed set of application icons.
4. The method of claim 2, further comprising:
displaying the set of application icons on the home screen prior to installing the application on the mobile device, wherein the set of application icons does not include the application icon corresponding to the installed application.
5. The method of claim 1, further comprising:
determining and presenting purchasing information associated with the application that corresponds to the selected application object, the purchasing information indicating a cost associated with the application that corresponds to the selected application object; and
prior to installing the application that corresponds to the selected application object on the mobile device:
accessing a user account to purchase the application that corresponds to the selected application object; and
receiving an indication that the application that corresponds to the selected application object has been purchased, wherein the indication that the application that corresponds to the selected application object has been-purchased is received when the user account has been charged the cost associated with the application that corresponds to the selected application object via an electronic payment.
6. The method of claim 5, wherein accessing the user account includes requesting and receiving authentication information associated with the user account.
7. The method of claim 1, including:
detecting a selection of the second user activated element associated with displaying application objects that do not require payment; and
in response to detecting selection of the second user activated element, ceasing to display the application objects that require payment and displaying at least some of the application objects that require payment.
8. The method of claim 7, wherein at least one application object of the displayed application objects displays purchase information.
9. The method of claim 8, wherein the purchase information for the at least one application object includes at least one of:
an indication that an application that corresponds to the at least one application object does not require payment; or
an indication that the application that corresponds to the at least one application object has already been installed.
10. The method of claim 1, including detecting an input to view additional application objects from the application objects that require payment; and, in response to detecting the input to view the additional application objects that require payment, scrolling the set of application objects that require payment to present additional application objects that require payment.
11. The method of claim 1, wherein at least one application object of the displayed application objects includes a rank and the displayed application objects are presented in ranked order.
12. The method of claim 1, including, before installing the application that corresponds to the selected application object, transitioning from displaying the application management interface to displaying a home screen including a placeholder object corresponding to the selected application.
13. The method claim 12, wherein the placeholder object includes an indicator of installation progress of the application that corresponds to the selected application object.
14. A mobile device, comprising:
a display;
one or more processors;
memory; and
one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for:
displaying, on a display of the mobile device, an application management interface that includes:
a set of application objects corresponding to respective applications from an application store server that are available for installation on the electronic device;
a first user activated element associated with only displaying application objects that require payment, and
a second user activated element associated with displaying application objects that do not require payment;
detecting selection of the first user activated element associated with only displaying application objects that require payment;
in response to detecting selection of the first user activated element, ceasing to display application objects that do not require payment and displaying at least some of the application objects that require payment;
detecting a selection of an application object from the displayed application objects;
receiving, from the application store server, an application that corresponds to the selected application object; and
installing, on the mobile device, the application that corresponds to the selected application object.
15. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions which, when executed by a mobile device with a display, cause the mobile device to:
display, on a display of the mobile device, an application management interface that includes:
a set of application objects corresponding to respective applications from an application store server that are available for installation on the electronic device;
a first user activated element associated with only displaying application objects that require payment, and
a second user activated element associated with displaying application objects that do not require payment;
detect selection of the first user activated element associated with only displaying application objects that require payment;
in response to detecting selection of the first user activated element, cease to display application objects that do not require payment and displaying at least some of the application objects that require payment;
detect a selection of an application object from the displayed application objects;
receive from the application store server an application that corresponds to the selected application object; and
install, on the mobile device, the application that corresponds to the selected application object.
16. The mobile device of claim 14, further comprising instructions for:
displaying a set of application icons on a home screen; and
receiving a request to display the application management interface, wherein the application management interface is displayed in response to receiving the request.
17. The mobile device of claim 16, wherein receiving the request to display the application management interface includes receiving an input directed to a selection of an app store icon, and wherein the app store icon is included in the displayed set of application icons.
18. The mobile device of claim 16, further comprising instructions for:
displaying the set of application icons on the home screen prior to installing the application on the mobile device, wherein the set of application icons does not include the application icon corresponding to the installed application.
19. The mobile device of claim 14, further comprising instructions for:
determining and presenting purchasing information associated with the application that corresponds to the selected application object, the purchasing information indicating a cost associated with the application that corresponds to the selected application object; and
prior to installing the application that corresponds to the selected application object on the mobile device:
accessing a user account to purchase the application that corresponds to the selected application object; and
receiving an indication that the application that corresponds to the selected application object has been purchased, wherein the indication that the application that corresponds to the selected application object has been-purchased is received when the user account has been charged the cost associated with the application that corresponds to the selected application object via an electronic payment.
20. The mobile device of claim 19, wherein accessing the user account includes requesting and receiving authentication information associated with the user account.
21. The mobile device of claim 14, further comprising instructions for:
detecting a selection of the second user activated element associated with displaying application objects that do not require payment; and
in response to detecting selection of the second user activated element, ceasing to display the application objects that require payment and displaying at least some of the application objects that require payment.
22. The mobile device of claim 21, wherein at least one application object of the displayed application objects displays purchase information.
23. The mobile device of claim 22, wherein the purchase information for the at least one application object includes at least one of:
an indication that an application that corresponds to the at least one application object does not require payment; or
an indication that the application that corresponds to the at least one application object has already been installed.
24. The mobile device of claim 14, further comprising instructions for:
detecting an input to view additional application objects from the application objects that require payment; and,
in response to detecting the input to view the additional application objects that require payment, scrolling the set of application objects that require payment to present additional application objects that require payment.
25. The mobile device of claim 14, wherein at least one application object of the displayed application objects includes a rank and the displayed application objects are presented in ranked order.
26. The mobile device of claim 14, further comprising instructions for, before installing the application that corresponds to the selected application object, transitioning from displaying the application management interface to displaying a home screen including a placeholder object corresponding to the selected application.
27. The mobile device of claim 26, wherein the placeholder object includes an indicator of installation progress of the application that corresponds to the selected application object.
28. The non-transitory computer readable storage medium of claim 15, further comprising instructions which, when executed by the mobile device, cause the mobile device to:
display a set of application icons on a home screen; and
receive a request to display the application management interface, wherein the application management interface is displayed in response to receiving the request.
29. The non-transitory computer readable storage medium of claim 28, wherein receiving the request to display the application management interface includes receiving an input directed to a selection of an app store icon, and wherein the app store icon is included in the displayed set of application icons.
30. The non-transitory computer readable storage medium of claim 28, further comprising instructions which, when executed by the mobile device, cause the mobile device to:
display the set of application icons on the home screen prior to installing the application on the mobile device, wherein the set of application icons does not include the application icon corresponding to the installed application.
31. The non-transitory computer readable storage medium of claim 15, further comprising instructions which, when executed by the mobile device, cause the mobile device to:
determine and present purchasing information associated with the application that corresponds to the selected application object, the purchasing information indicating a cost associated with the application that corresponds to the selected application object; and
prior to installing the application that corresponds to the selected application object on the mobile device:
access a user account to purchase the application that corresponds to the selected application object; and
receive an indication that the application that corresponds to the selected application object has been purchased, wherein the indication that the application that corresponds to the selected application object has been-purchased is received when the user account has been charged the cost associated with the application that corresponds to the selected application object via an electronic payment.
32. The non-transitory computer readable storage medium of claim 31, wherein accessing the user account includes requesting and receiving authentication information associated with the user account.
33. The non-transitory computer readable storage medium of claim 15, further comprising instructions which, when executed by the mobile device, cause the mobile device to:
detect a selection of the second user activated element associated with displaying application objects that do not require payment; and
in response to detecting selection of the second user activated element, cease to display the application objects that require payment and displaying at least some of the application objects that require payment.
34. The non-transitory computer readable storage medium of claim 33, wherein at least one application object of the displayed application objects displays purchase information.
35. The non-transitory computer readable storage medium of claim 34, wherein the purchase information for the at least one application object includes at least one of:
an indication that an application that corresponds to the at least one application object does not require payment; or
an indication that the application that corresponds to the at least one application object has already been installed.
36. The non-transitory computer readable storage medium of claim 15, further comprising instructions which, when executed by the mobile device, cause the mobile device to:
detect an input to view additional application objects from the application objects that require payment; and,
in response to detecting the input to view the additional application objects that require payment, scroll the set of application objects that require payment to present additional application objects that require payment.
37. The non-transitory computer readable storage medium of claim 15, wherein at least one application object of the displayed application objects includes a rank and the displayed application objects are presented in ranked order.
38. The non-transitory computer readable storage medium of claim 15, further comprising instructions which, when executed by the mobile device, cause the mobile device to, before installing the application that corresponds to the selected application object, transition from displaying the application management interface to displaying a home screen including a placeholder object corresponding to the selected application.
39. The non-transitory computer readable storage medium of claim 38, wherein the placeholder object includes an indicator of installation progress of the application that corresponds to the selected application object.
US14/279,168 2008-06-06 2014-05-15 User interface for application management for a mobile device Active US9965146B2 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US14/279,168 US9965146B2 (en) 2008-06-06 2014-05-15 User interface for application management for a mobile device
US15/974,510 US10318119B2 (en) 2008-06-06 2018-05-08 User interface for application management for a mobile device
US16/409,717 US11320961B2 (en) 2008-06-06 2019-05-10 Systems and methods for providing and interacting with application-update objects on a mobile device
US17/705,179 US11947776B2 (en) 2008-06-06 2022-03-25 Systems and methods for providing and interacting with application-update objects on a mobile device
US18/587,833 US20240201828A1 (en) 2008-06-06 2024-02-26 Systems and Methods for Providing and Interacting with Application-Update Objects on a Mobile Device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US5973008P 2008-06-06 2008-06-06
US12/354,616 US8099332B2 (en) 2008-06-06 2009-01-15 User interface for application management for a mobile device
US13/350,563 US8751321B2 (en) 2008-06-06 2012-01-13 User interface for application management for a mobile device
US14/279,168 US9965146B2 (en) 2008-06-06 2014-05-15 User interface for application management for a mobile device

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US13/350,563 Continuation US8751321B2 (en) 2008-06-06 2012-01-13 User interface for application management for a mobile device

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/974,510 Continuation US10318119B2 (en) 2008-06-06 2018-05-08 User interface for application management for a mobile device

Publications (2)

Publication Number Publication Date
US20140250015A1 US20140250015A1 (en) 2014-09-04
US9965146B2 true US9965146B2 (en) 2018-05-08

Family

ID=40886083

Family Applications (7)

Application Number Title Priority Date Filing Date
US12/354,616 Active 2029-05-29 US8099332B2 (en) 2008-06-06 2009-01-15 User interface for application management for a mobile device
US13/350,563 Active US8751321B2 (en) 2008-06-06 2012-01-13 User interface for application management for a mobile device
US14/279,168 Active US9965146B2 (en) 2008-06-06 2014-05-15 User interface for application management for a mobile device
US15/974,510 Active US10318119B2 (en) 2008-06-06 2018-05-08 User interface for application management for a mobile device
US16/409,717 Active US11320961B2 (en) 2008-06-06 2019-05-10 Systems and methods for providing and interacting with application-update objects on a mobile device
US17/705,179 Active US11947776B2 (en) 2008-06-06 2022-03-25 Systems and methods for providing and interacting with application-update objects on a mobile device
US18/587,833 Pending US20240201828A1 (en) 2008-06-06 2024-02-26 Systems and Methods for Providing and Interacting with Application-Update Objects on a Mobile Device

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US12/354,616 Active 2029-05-29 US8099332B2 (en) 2008-06-06 2009-01-15 User interface for application management for a mobile device
US13/350,563 Active US8751321B2 (en) 2008-06-06 2012-01-13 User interface for application management for a mobile device

Family Applications After (4)

Application Number Title Priority Date Filing Date
US15/974,510 Active US10318119B2 (en) 2008-06-06 2018-05-08 User interface for application management for a mobile device
US16/409,717 Active US11320961B2 (en) 2008-06-06 2019-05-10 Systems and methods for providing and interacting with application-update objects on a mobile device
US17/705,179 Active US11947776B2 (en) 2008-06-06 2022-03-25 Systems and methods for providing and interacting with application-update objects on a mobile device
US18/587,833 Pending US20240201828A1 (en) 2008-06-06 2024-02-26 Systems and Methods for Providing and Interacting with Application-Update Objects on a Mobile Device

Country Status (11)

Country Link
US (7) US8099332B2 (en)
EP (1) EP2300916A1 (en)
JP (5) JP5486593B2 (en)
KR (3) KR101787184B1 (en)
CN (2) CN102089744B (en)
AU (2) AU2009255409B2 (en)
BR (1) BRPI0915601B1 (en)
CA (1) CA2726117C (en)
MX (1) MX2010013377A (en)
RU (2) RU2477879C2 (en)
WO (1) WO2009148781A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10152205B2 (en) 2015-01-05 2018-12-11 Samsung Electronics Co., Ltd. Display apparatus and display method

Families Citing this family (510)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7680324B2 (en) 2000-11-06 2010-03-16 Evryx Technologies, Inc. Use of image-derived information as search criteria for internet and other search engines
US7565008B2 (en) 2000-11-06 2009-07-21 Evryx Technologies, Inc. Data capture and identification system and process
US7899243B2 (en) 2000-11-06 2011-03-01 Evryx Technologies, Inc. Image capture and identification system and process
US9310892B2 (en) 2000-11-06 2016-04-12 Nant Holdings Ip, Llc Object information derived from object images
US8218873B2 (en) * 2000-11-06 2012-07-10 Nant Holdings Ip, Llc Object information derived from object images
US8224078B2 (en) 2000-11-06 2012-07-17 Nant Holdings Ip, Llc Image capture and identification system and process
EP1920393A2 (en) * 2005-07-22 2008-05-14 Yogesh Chunilal Rathod Universal knowledge management and desktop search system
US8225231B2 (en) 2005-08-30 2012-07-17 Microsoft Corporation Aggregation of PC settings
US11126321B2 (en) * 2007-09-04 2021-09-21 Apple Inc. Application menu user interface
US10997531B2 (en) 2007-09-11 2021-05-04 Ciambella Ltd. System, method and graphical user interface for workflow generation, deployment and/or execution
US8099332B2 (en) 2008-06-06 2012-01-17 Apple Inc. User interface for application management for a mobile device
US8520000B2 (en) * 2008-07-02 2013-08-27 Icharts, Inc. Creation, sharing and embedding of interactive charts
US7925797B2 (en) 2008-07-03 2011-04-12 Steelseries Hq System and method for distributing user interface device configurations
US8281046B2 (en) 2008-07-03 2012-10-02 Steelseries Aps System and method for distributing user interface device configurations
US20100107100A1 (en) 2008-10-23 2010-04-29 Schneekloth Jason S Mobile Device Style Abstraction
US8411046B2 (en) 2008-10-23 2013-04-02 Microsoft Corporation Column organization of content
KR101588666B1 (en) * 2008-12-08 2016-01-27 삼성전자주식회사 Display apparatus and method for displaying thereof
US8199507B2 (en) * 2008-12-19 2012-06-12 Openpeak Inc. Telephony and digital media services device
US8745153B2 (en) * 2009-02-09 2014-06-03 Apple Inc. Intelligent download of application programs
US8457688B2 (en) * 2009-02-26 2013-06-04 Research In Motion Limited Mobile wireless communications device with voice alteration and related methods
US8589374B2 (en) 2009-03-16 2013-11-19 Apple Inc. Multifunction device with integrated search and application selection
US8238876B2 (en) 2009-03-30 2012-08-07 Microsoft Corporation Notifications
US8175653B2 (en) 2009-03-30 2012-05-08 Microsoft Corporation Chromeless user interface
US8836648B2 (en) 2009-05-27 2014-09-16 Microsoft Corporation Touch pull-in gesture
JP4871373B2 (en) 2009-06-19 2012-02-08 任天堂株式会社 Information processing system and information processing apparatus
US20100332996A1 (en) * 2009-06-25 2010-12-30 Nokia Corporation Method and apparatus of acquiring information regarding applications for display on a user interface
US8535152B2 (en) * 2009-06-26 2013-09-17 Curtis Instruments, Inc. Integrated game function in a personal mobility vehicle, such as a wheelchair
CN101656789B (en) * 2009-07-01 2012-09-05 中兴通讯股份有限公司 Method for managing application information of mobile phone and application program manager
US10387140B2 (en) 2009-07-23 2019-08-20 S3G Technology Llc Modification of terminal and service provider machines using an update server machine
EP2288113B1 (en) * 2009-08-21 2014-09-24 Samsung Electronics Co., Ltd. Apparatuses for downloading applications via application lists
JP5674296B2 (en) 2009-09-09 2015-02-25 任天堂株式会社 Information processing system and information processing apparatus
US20110072421A1 (en) * 2009-09-18 2011-03-24 Research In Motion Limited Method, apparatus and system for updating a software bundle installed on a mobile electronic device
KR20110038863A (en) * 2009-10-09 2011-04-15 삼성전자주식회사 Searching method of a function and portable device using the same
US8559931B2 (en) * 2009-11-04 2013-10-15 Cellco Partnership Application suggestions for mobile communication device based on location-based directory information
US20110113365A1 (en) * 2009-11-09 2011-05-12 Microsoft Corporation Scrolling large data sets
KR20110063297A (en) * 2009-12-02 2011-06-10 삼성전자주식회사 Mobile device and control method thereof
US8271031B2 (en) * 2009-12-30 2012-09-18 Sap Ag Communication between integrated device and mobile application client on mobile personal communication device
US8698845B2 (en) 2010-01-06 2014-04-15 Apple Inc. Device, method, and graphical user interface with interactive popup views
EP2524492A4 (en) * 2010-01-11 2014-11-19 Mobile Messenger Global Inc Method and apparatus for billing purchases from a mobile phone application
US20110191330A1 (en) * 2010-02-04 2011-08-04 Veveo, Inc. Method of and System for Enhanced Content Discovery Based on Network and Device Access Behavior
US9721279B2 (en) * 2010-03-23 2017-08-01 Microsoft Technology Licensing, Llc Determining mobile operators for mobile devices
US9823831B2 (en) 2010-04-07 2017-11-21 Apple Inc. Device, method, and graphical user interface for managing concurrently open software applications
US9513801B2 (en) 2010-04-07 2016-12-06 Apple Inc. Accessing electronic notifications and settings icons with gestures
US20110250969A1 (en) * 2010-04-07 2011-10-13 Marcel Van Os Systems and methods for providing a game center having player specific achievement data
US8291344B2 (en) 2010-04-07 2012-10-16 Apple Inc. Device, method, and graphical user interface for managing concurrently open software applications
KR101642725B1 (en) * 2010-04-14 2016-08-11 삼성전자 주식회사 Method and apparatus for managing lock function in mobile terminal
US8166106B2 (en) * 2010-04-15 2012-04-24 Microsoft Corporation Targeting applications based on mobile operator
KR101829406B1 (en) * 2010-05-19 2018-02-19 구글 엘엘씨 Bug clearing house
US20110288941A1 (en) * 2010-05-20 2011-11-24 Google Inc. Contextual content items for mobile applications
JP2011250874A (en) 2010-05-31 2011-12-15 Nintendo Co Ltd Information processing program, information processing apparatus, information processing system, and information processing method
CN101859425B (en) * 2010-06-02 2014-11-05 中兴通讯股份有限公司 Method and device for providing application list
US20110307323A1 (en) * 2010-06-10 2011-12-15 Google Inc. Content items for mobile applications
JP5593566B2 (en) 2010-06-10 2014-09-24 任天堂株式会社 Information processing system, information processing apparatus, information processing apparatus control method, and information processing apparatus control program
JP2012018657A (en) 2010-06-11 2012-01-26 Nintendo Co Ltd Information processing terminal, information processing system, and information processing program
JP5677811B2 (en) * 2010-06-11 2015-02-25 任天堂株式会社 Portable information terminal, portable information system, portable information terminal control program
KR101735606B1 (en) * 2010-07-21 2017-05-15 엘지전자 주식회사 Mobile terminal and operation control method thereof
USD666626S1 (en) * 2010-07-22 2012-09-04 Research In Motion Limited Display screen with graphical user interface
KR101742986B1 (en) * 2010-07-26 2017-06-15 엘지전자 주식회사 Image display apparatus and method for operating the same
KR101752355B1 (en) * 2010-07-26 2017-06-29 엘지전자 주식회사 Method for operating an apparatus for displaying image
US9936333B2 (en) * 2010-08-10 2018-04-03 Microsoft Technology Licensing, Llc Location and contextual-based mobile application promotion and delivery
US9600630B2 (en) * 2010-08-17 2017-03-21 Welch Allyn, Inc. User installed applications in a physiological parameter display device
KR101750337B1 (en) * 2010-08-17 2017-06-23 삼성전자주식회사 Method for providing information and apparatus therefor
KR101690595B1 (en) * 2010-09-01 2016-12-28 엘지전자 주식회사 Mobile Terminal And Method Of Managing Icon Using The Same
FR2964779A1 (en) * 2010-09-09 2012-03-16 Sagem Wireless MOBILE TERMINAL, AND METHOD, COMPUTER PROGRAM, AND CORRESPONDING STORAGE MEANS
JP4999213B2 (en) 2010-09-17 2012-08-15 任天堂株式会社 Information processing program, portable terminal device, system, information processing method, and communication system
US10013492B1 (en) * 2010-09-24 2018-07-03 Amazon Technologies, Inc. Categorization based on user questionnaire
US20110029881A1 (en) * 2010-10-11 2011-02-03 Nevolution Digital, Llc Devices and methods for providing software programs compatible with a computer system for download by a user
US8484100B2 (en) 2010-10-19 2013-07-09 Apple Inc. Method, medium, and system for an integrated application store for a user device
US10169017B2 (en) * 2010-10-21 2019-01-01 International Business Machines Corporation Crowdsourcing location based applications and structured data for location based applications
US20120102164A1 (en) * 2010-10-21 2012-04-26 International Business Machines Corporation Deployment of location based applications with crowdsourced structured points of input for data entry
US9805022B2 (en) 2010-12-09 2017-10-31 Apple Inc. Generation of topic-based language models for an app search engine
US9244606B2 (en) 2010-12-20 2016-01-26 Apple Inc. Device, method, and graphical user interface for navigation of concurrently open software applications
US20120159383A1 (en) 2010-12-20 2012-06-21 Microsoft Corporation Customization of an immersive environment
US20120159395A1 (en) 2010-12-20 2012-06-21 Microsoft Corporation Application-launching interface for multiple modes
KR101789622B1 (en) * 2010-12-22 2017-10-25 엘지전자 주식회사 Mobile terminal and Method for displaying information thereof
US8689123B2 (en) 2010-12-23 2014-04-01 Microsoft Corporation Application reporting in an application-selectable user interface
US8612874B2 (en) 2010-12-23 2013-12-17 Microsoft Corporation Presenting an application change through a tile
JP4882022B1 (en) 2010-12-28 2012-02-22 任天堂株式会社 Communication system, information processing program, information processing method, information processing apparatus, information processing system
US9423951B2 (en) 2010-12-31 2016-08-23 Microsoft Technology Licensing, Llc Content-based snap point
JP5675373B2 (en) * 2011-01-06 2015-02-25 任天堂株式会社 Communication system, information processing apparatus, communication program, and communication method
JP5688297B2 (en) 2011-01-06 2015-03-25 任天堂株式会社 Communication system, information processing apparatus, communication program, and communication method
WO2012098555A1 (en) * 2011-01-20 2012-07-26 Google Inc. Direct carrier billing
CN102129639B (en) * 2011-01-28 2014-07-16 Tcl集团股份有限公司 Method and system for sharing application procedure
US10394539B2 (en) * 2011-03-17 2019-08-27 Iheartmedia Management Services, Inc. Dynamically configured graphical user interface for a software application
KR101069205B1 (en) * 2011-03-28 2011-09-30 주식회사 모리아타운 System and method for providing social advertisement service using word input device
US9383917B2 (en) 2011-03-28 2016-07-05 Microsoft Technology Licensing, Llc Predictive tiling
US20120254768A1 (en) * 2011-03-31 2012-10-04 Google Inc. Customizing mobile applications
US20120249461A1 (en) 2011-04-01 2012-10-04 Analog Devices, Inc. Dedicated user interface controller for feedback responses
US8275672B1 (en) * 2011-04-04 2012-09-25 Google Inc. Coordinating multiple devices in a product purchasing system
EP2523107B1 (en) * 2011-04-19 2018-11-07 LG Electronics Inc. Mobile terminal and system for managing applications using the same
US20120268388A1 (en) * 2011-04-21 2012-10-25 Mahmoud Razzaghi Touch screen text selection
US10187494B2 (en) 2011-04-26 2019-01-22 Acumera, Inc. Gateway device application development system
US8491384B2 (en) * 2011-04-30 2013-07-23 Samsung Electronics Co., Ltd. Multi-user discovery
US8943514B2 (en) 2011-04-30 2015-01-27 Samsung Electronics Co., Ltd. Middle partners
US20120284599A1 (en) * 2011-05-03 2012-11-08 Htc Corporation Handheld Electronic Device and Method for Recording Multimedia Clip
US9158445B2 (en) 2011-05-27 2015-10-13 Microsoft Technology Licensing, Llc Managing an immersive interface in a multi-application immersive environment
US20120302206A1 (en) * 2011-05-27 2012-11-29 Vock Curtis A Surface software and associated methods
US8893033B2 (en) 2011-05-27 2014-11-18 Microsoft Corporation Application notifications
US9104307B2 (en) 2011-05-27 2015-08-11 Microsoft Technology Licensing, Llc Multi-application environment
US9104440B2 (en) * 2011-05-27 2015-08-11 Microsoft Technology Licensing, Llc Multi-application environment
US9658766B2 (en) 2011-05-27 2017-05-23 Microsoft Technology Licensing, Llc Edge gesture
US20120304132A1 (en) 2011-05-27 2012-11-29 Chaitanya Dev Sareen Switching back to a previously-interacted-with application
US9339727B2 (en) 2011-06-15 2016-05-17 Microsoft Technology Licensing, Llc Position-based decision to provide service
KR101801577B1 (en) 2011-06-28 2017-11-27 엘지전자 주식회사 Mobile terminal and Method for controlling display thereof
US20130012286A1 (en) * 2011-07-08 2013-01-10 Schuff Ryan S System to purchase state lottery ticket
US8700709B2 (en) 2011-07-29 2014-04-15 Microsoft Corporation Conditional location-based reminders
US8687023B2 (en) 2011-08-02 2014-04-01 Microsoft Corporation Cross-slide gesture to select and rearrange
US8930940B2 (en) * 2011-08-19 2015-01-06 Yongyong Xu Online software execution platform
US8806369B2 (en) 2011-08-26 2014-08-12 Apple Inc. Device, method, and graphical user interface for managing and interacting with concurrently open software applications
US20130057587A1 (en) 2011-09-01 2013-03-07 Microsoft Corporation Arranging tiles
WO2013035901A1 (en) * 2011-09-08 2013-03-14 Kim A Lim Marketing method using smart phone
US9557909B2 (en) 2011-09-09 2017-01-31 Microsoft Technology Licensing, Llc Semantic zoom linguistic helpers
US10353566B2 (en) 2011-09-09 2019-07-16 Microsoft Technology Licensing, Llc Semantic zoom animations
US8922575B2 (en) 2011-09-09 2014-12-30 Microsoft Corporation Tile cache
US9329851B2 (en) * 2011-09-09 2016-05-03 Microsoft Technology Licensing, Llc Browser-based discovery and application switching
US8933952B2 (en) 2011-09-10 2015-01-13 Microsoft Corporation Pre-rendering new content for an application-selectable user interface
US9244802B2 (en) 2011-09-10 2016-01-26 Microsoft Technology Licensing, Llc Resource user interface
US9146670B2 (en) 2011-09-10 2015-09-29 Microsoft Technology Licensing, Llc Progressively indicating new content in an application-selectable user interface
CN102331945A (en) * 2011-09-16 2012-01-25 北京思创银联科技股份有限公司 Application management method based on electronic store
US9161225B2 (en) 2011-09-23 2015-10-13 Blackberry Limited Authentication procedures for managing mobile device applications
US8554175B2 (en) 2011-09-23 2013-10-08 Blackberry Limited Managing mobile device applications on a mobile device
US9497688B2 (en) 2011-09-23 2016-11-15 Certicom Corp. Managing mobile device applications in a wireless network
US8554179B2 (en) 2011-09-23 2013-10-08 Blackberry Limited Managing mobile device applications
US20130080968A1 (en) * 2011-09-27 2013-03-28 Amazon Technologies Inc. User interface with media content prediction
KR101840852B1 (en) 2011-10-10 2018-03-22 삼성전자주식회사 Surface temperature management method of mobile device and memory thermal management method of multichip package
US8971842B2 (en) * 2011-10-12 2015-03-03 Verizon Patent And Licensing Inc. Enterprise mobile application store
WO2013067000A1 (en) * 2011-11-01 2013-05-10 Google Inc. Launching applications from webpages
US8880022B2 (en) * 2011-11-10 2014-11-04 Microsoft Corporation Providing per-application resource usage information
US8713646B2 (en) 2011-12-09 2014-04-29 Erich Stuntebeck Controlling access to resources on a network
KR101515998B1 (en) * 2011-12-19 2015-05-07 주식회사 케이티 Method for providing space market widget, market server and user deivce thereof
KR20130071908A (en) * 2011-12-21 2013-07-01 삼성전자주식회사 Device and method for editing screen in wireless terminal
US9223472B2 (en) 2011-12-22 2015-12-29 Microsoft Technology Licensing, Llc Closing applications
KR101234342B1 (en) * 2011-12-23 2013-03-15 유신출 Advertisement method and system using mobile application
CN102541603B (en) * 2011-12-28 2015-12-02 华为终端有限公司 A kind of application program launching method, system and terminal device
KR101895536B1 (en) * 2011-12-29 2018-10-25 삼성전자주식회사 Server and terminal for recommending application according to use of application, and recommending application method
US10129720B1 (en) * 2011-12-30 2018-11-13 Genesys Telecommunications Laboratories, Inc. Conversation assistant
KR101373550B1 (en) * 2012-01-11 2014-03-13 (주)마상소프트 System for platform system based on network
JP2013145484A (en) * 2012-01-16 2013-07-25 Nec Casio Mobile Communications Ltd Processing system, processor, terminal device, processing method and program
US9128513B2 (en) * 2012-02-08 2015-09-08 Qualcomm Incorporated Display of an online catalog for concurrent downloading of files
US9128605B2 (en) 2012-02-16 2015-09-08 Microsoft Technology Licensing, Llc Thumbnail-image selection of applications
KR101956082B1 (en) 2012-05-09 2019-03-11 애플 인크. Device, method, and graphical user interface for selecting user interface objects
EP2847659B1 (en) 2012-05-09 2019-09-04 Apple Inc. Device, method, and graphical user interface for transitioning between display states in response to a gesture
WO2013169875A2 (en) 2012-05-09 2013-11-14 Yknots Industries Llc Device, method, and graphical user interface for displaying content associated with a corresponding affordance
CN104487929B (en) 2012-05-09 2018-08-17 苹果公司 For contacting the equipment for carrying out display additional information, method and graphic user interface in response to user
WO2013169845A1 (en) 2012-05-09 2013-11-14 Yknots Industries Llc Device, method, and graphical user interface for scrolling nested regions
WO2013169865A2 (en) 2012-05-09 2013-11-14 Yknots Industries Llc Device, method, and graphical user interface for moving a user interface object based on an intensity of a press input
WO2013169843A1 (en) 2012-05-09 2013-11-14 Yknots Industries Llc Device, method, and graphical user interface for manipulating framed graphical objects
CN109298789B (en) 2012-05-09 2021-12-31 苹果公司 Device, method and graphical user interface for providing feedback on activation status
WO2013169849A2 (en) 2012-05-09 2013-11-14 Industries Llc Yknots Device, method, and graphical user interface for displaying user interface objects corresponding to an application
CN104487930A (en) 2012-05-09 2015-04-01 苹果公司 Device, method, and graphical user interface for moving and dropping a user interface object
WO2013169842A2 (en) 2012-05-09 2013-11-14 Yknots Industries Llc Device, method, and graphical user interface for selecting object within a group of objects
EP2847658B1 (en) 2012-05-09 2017-06-21 Apple Inc. Device, method, and graphical user interface for providing tactile feedback for operations performed in a user interface
WO2013169851A2 (en) 2012-05-09 2013-11-14 Yknots Industries Llc Device, method, and graphical user interface for facilitating user interaction with controls in a user interface
US9704171B2 (en) * 2012-06-05 2017-07-11 Applause App Quality, Inc. Methods and systems for quantifying and tracking software application quality
WO2013184018A1 (en) * 2012-06-07 2013-12-12 Google Inc. User curated collections for an online application environment
KR20130142301A (en) * 2012-06-19 2013-12-30 삼성전자주식회사 Device and method for setting menu environment in terminal
US8832847B2 (en) 2012-07-10 2014-09-09 International Business Machines Corporation Coordinating data sharing among applications in mobile devices
US8984480B2 (en) 2012-07-10 2015-03-17 International Business Machines Corporation Automating and/or recommending data sharing coordination among applications in mobile devices
US20140020096A1 (en) * 2012-07-11 2014-01-16 Clutch Mobile, Inc. System to profile application software
US20140026062A1 (en) * 2012-07-20 2014-01-23 Research In Motion Limited Method, system and apparatus for collecting data associated with applications
US20150220245A1 (en) * 2012-08-27 2015-08-06 Clear View Productions, Inc. Branded computer devices and apparatus to connect user and enterprise
US8584019B1 (en) * 2012-08-29 2013-11-12 Mitesh Gala Location-based and other criteria-based establishment management systems and methods
US20140075365A1 (en) * 2012-09-10 2014-03-13 Lookout, Inc. Method and system for visually monitoring the progress of a security operation of an electronic device
US9216835B2 (en) * 2012-09-17 2015-12-22 Intel Corporation Translating application labels
CN102930444A (en) * 2012-09-25 2013-02-13 中兴通讯股份有限公司 Mobile terminal as well as application classified management method and system thereof
JP6242045B2 (en) * 2012-09-26 2017-12-06 京セラ株式会社 Apparatus, method, and program
US9294554B2 (en) 2012-09-28 2016-03-22 Sears Brands, L.L.C. Integrated experience for applications within a mobile application
US8984008B2 (en) * 2012-10-19 2015-03-17 Google Inc. Re-use of binaries for multiple user accounts
KR20140057998A (en) * 2012-11-05 2014-05-14 삼성전자주식회사 Method and apparatus for notifying application update information in an electronic device
US9591339B1 (en) 2012-11-27 2017-03-07 Apple Inc. Agnostic media delivery system
US8832785B2 (en) 2012-12-06 2014-09-09 Airwatch, Llc Systems and methods for controlling email access
US8862868B2 (en) 2012-12-06 2014-10-14 Airwatch, Llc Systems and methods for controlling email access
US8978110B2 (en) 2012-12-06 2015-03-10 Airwatch Llc Systems and methods for controlling email access
KR20140073258A (en) * 2012-12-06 2014-06-16 삼성전자주식회사 Method for providing application information and mobile terminal
US8826432B2 (en) 2012-12-06 2014-09-02 Airwatch, Llc Systems and methods for controlling email access
US9021037B2 (en) 2012-12-06 2015-04-28 Airwatch Llc Systems and methods for controlling email access
US9774917B1 (en) 2012-12-10 2017-09-26 Apple Inc. Channel bar user interface
US10200761B1 (en) 2012-12-13 2019-02-05 Apple Inc. TV side bar user interface
US9532111B1 (en) 2012-12-18 2016-12-27 Apple Inc. Devices and method for providing remote control hints on a display
US20140172510A1 (en) * 2012-12-18 2014-06-19 Hyland Software, Inc. Enterprise Content Management (ECM) Solutions Tool and Method
USD923645S1 (en) * 2012-12-21 2021-06-29 Iconic Data Inc. Display screen or portion thereof with a graphical user interface
CN104885050B (en) 2012-12-29 2017-12-08 苹果公司 For determining the equipment, method and the graphic user interface that are rolling or selection content
EP2912542B1 (en) 2012-12-29 2022-07-13 Apple Inc. Device and method for forgoing generation of tactile output for a multi-contact gesture
JP6158947B2 (en) 2012-12-29 2017-07-05 アップル インコーポレイテッド Device, method and graphical user interface for transitioning between relationships from touch input to display output
EP3467634B1 (en) 2012-12-29 2020-09-23 Apple Inc. Device, method, and graphical user interface for navigating user interface hierarchies
EP2939095B1 (en) 2012-12-29 2018-10-03 Apple Inc. Device, method, and graphical user interface for moving a cursor according to a change in an appearance of a control icon with simulated three-dimensional characteristics
US10521188B1 (en) 2012-12-31 2019-12-31 Apple Inc. Multi-user TV user interface
CN103065250A (en) * 2013-01-15 2013-04-24 周万荣 Electronic business system based on application
JP6036852B2 (en) * 2013-01-24 2016-11-30 富士通株式会社 Portable information terminal, control method, control program
US20140215450A1 (en) * 2013-01-31 2014-07-31 Trane International Inc. System and method for updating software
KR102101876B1 (en) * 2013-01-31 2020-04-21 삼성전자주식회사 Method for managing application and device for performing management of application
US10545628B2 (en) 2013-01-31 2020-01-28 Samsung Electronics Co., Ltd. Method of and device for managing applications
US11016637B2 (en) 2013-01-31 2021-05-25 Samsung Electronics Co., Ltd. Method of and device for managing applications
WO2014119867A1 (en) 2013-01-31 2014-08-07 Samsung Electronics Co., Ltd. Method of and device for managing applications
US9959360B2 (en) 2013-03-01 2018-05-01 Samsung Electronics Co., Ltd. Generating search results containing state links to applications
US8997187B2 (en) 2013-03-15 2015-03-31 Airwatch Llc Delegating authorization to applications on a client device in a networked environment
US9727326B2 (en) * 2013-03-15 2017-08-08 Apple Inc. Providing customized notifications for security software updates
US9658740B2 (en) 2013-03-15 2017-05-23 Apple Inc. Device, method, and graphical user interface for managing concurrently open software applications
USD778929S1 (en) * 2013-03-15 2017-02-14 Dexcom, Inc. Display screen or portion thereof with graphical user interface
US9477404B2 (en) 2013-03-15 2016-10-25 Apple Inc. Device, method, and graphical user interface for managing concurrently open software applications
USD767605S1 (en) 2013-03-15 2016-09-27 Dexcom, Inc. Display screen or portion thereof with a graphical user interface with icons
US9450952B2 (en) 2013-05-29 2016-09-20 Microsoft Technology Licensing, Llc Live tiles without application-code execution
CN103246595B (en) * 2013-04-08 2016-06-08 小米科技有限责任公司 Application management method, device, server and terminating unit
US9369528B2 (en) * 2013-04-08 2016-06-14 Xerox Corporation Multi-function device application catalog with integrated discovery, management, and application designer
US9787686B2 (en) 2013-04-12 2017-10-10 Airwatch Llc On-demand security policy activation
USD739864S1 (en) * 2013-04-24 2015-09-29 Samsung Electronics Co., Ltd. Display screen or portion thereof with graphical user interface
US9288353B2 (en) 2013-04-26 2016-03-15 Canon Information And Imaging Solutions, Inc. System and method for resetting a counter associated with a component of an image processing device
US9123031B2 (en) 2013-04-26 2015-09-01 Airwatch Llc Attendance tracking via device presence
JP6448062B2 (en) * 2013-05-07 2019-01-09 ノーム ザタロブスキ、ヨーニ A system for browsing with personalized and customizable smart browsers
KR102280474B1 (en) * 2013-05-28 2021-07-22 삼성전자 주식회사 Method and apparatus for operating of electronic device
US9900261B2 (en) 2013-06-02 2018-02-20 Airwatch Llc Shared resource watermarking and management
US9584437B2 (en) 2013-06-02 2017-02-28 Airwatch Llc Resource watermarking and management
USD771084S1 (en) * 2013-06-05 2016-11-08 Samsung Electronics Co., Ltd. Display screen or portion thereof with graphic user interface
USD734774S1 (en) 2013-06-09 2015-07-21 Apple Inc. Display screen or portion thereof with graphical user interface
USD726219S1 (en) 2013-06-09 2015-04-07 Apple Inc. Display screen or portion thereof with animated graphical user interface
USD741350S1 (en) 2013-06-10 2015-10-20 Apple Inc. Display screen or portion thereof with animated graphical user interface
US9436439B2 (en) 2013-06-18 2016-09-06 Ciambella Ltd. Method and apparatus for code virtualization and remote process call generation
BR302013006652S1 (en) * 2013-06-21 2015-03-10 Samsung Electronics Co Ltd ORNAMENTAL STANDARD APPLIED TO THE GRAPHIC USER INTERFACE FOR A DISPLAY OR PART OF THE SAME
US20140379533A1 (en) * 2013-06-21 2014-12-25 One Kings Lane, Inc. Story based selling of products
US8756426B2 (en) 2013-07-03 2014-06-17 Sky Socket, Llc Functionality watermarking and management
US8806217B2 (en) 2013-07-03 2014-08-12 Sky Socket, Llc Functionality watermarking and management
US8775815B2 (en) 2013-07-03 2014-07-08 Sky Socket, Llc Enterprise-specific functionality watermarking and management
US9367806B1 (en) 2013-08-08 2016-06-14 Jasmin Cosic Systems and methods of using an artificially intelligent database management system and interfaces for mobile, embedded, and other computing devices
US9665723B2 (en) 2013-08-15 2017-05-30 Airwatch, Llc Watermarking detection and management
USD850475S1 (en) * 2013-08-28 2019-06-04 Chicisimo S.L. Display screen with graphical user interface
USD754671S1 (en) 2013-08-28 2016-04-26 Chicisimo S.L. Display screen with graphical user interface
USD778294S1 (en) 2013-08-28 2017-02-07 Chicisimo S.L. Display screen with graphical user interface
KR102153366B1 (en) 2013-08-30 2020-10-15 삼성전자 주식회사 Method and apparatus for switching screen in electronic device
JP5728544B2 (en) * 2013-09-11 2015-06-03 株式会社ソニー・コンピュータエンタテインメント Information processing apparatus, information processing method, program, and information storage medium
CN104462097B (en) * 2013-09-13 2018-02-27 联想(北京)有限公司 Display methods and electronic equipment
US11785061B2 (en) * 2013-09-16 2023-10-10 Insyde Software Corp. System and method to share an application with another device
USD766253S1 (en) * 2013-09-25 2016-09-13 Google Inc. Display panel or portion thereof with a graphical user interface component
CN103473004A (en) * 2013-09-29 2013-12-25 小米科技有限责任公司 Method, device and terminal equipment for displaying message
USD744498S1 (en) 2013-10-04 2015-12-01 Hidex Oy Display screen with graphical user interface
CN103530796B (en) 2013-10-10 2016-06-01 北京智谷睿拓技术服务有限公司 The active period detection method of application program and active period detection system
CN103761228B (en) * 2013-10-10 2017-10-13 北京智谷睿拓技术服务有限公司 The rank threshold of application program determines that method and rank threshold determine system
US20150127505A1 (en) * 2013-10-11 2015-05-07 Capital One Financial Corporation System and method for generating and transforming data presentation
US9258301B2 (en) 2013-10-29 2016-02-09 Airwatch Llc Advanced authentication techniques
US9544306B2 (en) 2013-10-29 2017-01-10 Airwatch Llc Attempted security breach remediation
USD755193S1 (en) * 2013-12-02 2016-05-03 Tencent Technology (Shenzhen) Company Limited Display screen with graphical user interface
US20160019360A1 (en) 2013-12-04 2016-01-21 Apple Inc. Wellness aggregator
US12080421B2 (en) 2013-12-04 2024-09-03 Apple Inc. Wellness aggregator
US9720672B2 (en) * 2014-01-06 2017-08-01 Quixey, Inc. Searching and accessing application functionality
EP3872659A1 (en) * 2014-01-23 2021-09-01 Apple Inc. Biometric authentication for online purchasing
US9600258B2 (en) * 2014-02-14 2017-03-21 Google Inc. Suggestions to install and/or open a native application
US20150242420A1 (en) 2014-02-21 2015-08-27 Quixey, Inc. Location-Based Searching
US10181028B2 (en) 2014-02-21 2019-01-15 Samsung Electronics Co., Ltd. Method and apparatus to sandbox run-time android applications with lightweight container
WO2015126133A1 (en) * 2014-02-21 2015-08-27 Samsung Electronics Co., Ltd. Method and apparatus to sandbox run-time android applications with lightweight container
WO2015149347A1 (en) 2014-04-04 2015-10-08 Microsoft Technology Licensing, Llc Expandable application representation
CN105378582B (en) 2014-04-10 2019-07-23 微软技术许可有限责任公司 Calculate the foldable cap of equipment
WO2015154276A1 (en) 2014-04-10 2015-10-15 Microsoft Technology Licensing, Llc Slider cover for computing device
US9811239B2 (en) * 2014-05-05 2017-11-07 Cellco Partnership Systems and methods for efficiently searching applications
KR102242348B1 (en) 2014-06-24 2021-04-20 애플 인크. Input device and user interface interactions
AU2015280256A1 (en) 2014-06-24 2016-10-13 Apple Inc. Column interface for navigating in a user interface
CN104077054B (en) * 2014-07-04 2019-02-26 北京奇虎科技有限公司 User's scoring implementation method, user's scoring client and electronic equipment
US10592080B2 (en) 2014-07-31 2020-03-17 Microsoft Technology Licensing, Llc Assisted presentation of application windows
US10254942B2 (en) 2014-07-31 2019-04-09 Microsoft Technology Licensing, Llc Adaptive sizing and positioning of application windows
US10678412B2 (en) 2014-07-31 2020-06-09 Microsoft Technology Licensing, Llc Dynamic joint dividers for application windows
US9613270B2 (en) 2014-08-12 2017-04-04 Xiaomi Inc. Weather displaying method and device
CN104183004A (en) * 2014-08-12 2014-12-03 小米科技有限责任公司 Weather display method and weather display device
US20160055133A1 (en) * 2014-08-19 2016-02-25 Adlast, Inc. Systems and methods for directing access to products and services
US10642365B2 (en) 2014-09-09 2020-05-05 Microsoft Technology Licensing, Llc Parametric inertia and APIs
USD771114S1 (en) * 2014-09-11 2016-11-08 Samsung Electronics Co., Ltd. Display screen or portion thereof with graphical user interface
CN104615452A (en) * 2014-09-19 2015-05-13 安一恒通(北京)科技有限公司 Information providing method and device
CN104199593B (en) * 2014-09-22 2017-12-29 联想(北京)有限公司 A kind of information processing method and device
USD771646S1 (en) 2014-09-30 2016-11-15 Apple Inc. Display screen or portion thereof with graphical user interface
US9501271B2 (en) * 2014-10-09 2016-11-22 Facebook, Inc. Device, method, and graphical user interface for presenting and installing applications
US9626443B2 (en) 2014-10-23 2017-04-18 Quixey, Inc. Searching and accessing application functionality
US9674335B2 (en) 2014-10-30 2017-06-06 Microsoft Technology Licensing, Llc Multi-configuration input device
USD784400S1 (en) * 2014-11-04 2017-04-18 Workplace Dynamics, LLC Display screen or portion thereof with rating scale graphical user interface
USD784401S1 (en) * 2014-11-04 2017-04-18 Workplace Dynamics, LLC Display screen or portion thereof with rating scale graphical user interface
US9928233B2 (en) 2014-11-12 2018-03-27 Applause App Quality, Inc. Computer-implemented methods and systems for clustering user reviews and ranking clusters
CN104391724B (en) * 2014-12-05 2019-02-15 广州三星通信技术研究有限公司 The method and apparatus for reconfiguring picture mark position
USD772261S1 (en) * 2014-12-12 2016-11-22 Wayblazer, Inc. Display screen with graphical user interface
US9569196B2 (en) * 2014-12-19 2017-02-14 Paypal, Inc. App store update notification and warning system
US9883007B2 (en) * 2015-01-20 2018-01-30 Microsoft Technology Licensing, Llc Downloading an application to an apparatus
US10255302B1 (en) 2015-02-27 2019-04-09 Jasmin Cosic Systems, methods, apparatuses, and/or interfaces for associative management of data and inference of electronic resources
US9645732B2 (en) 2015-03-08 2017-05-09 Apple Inc. Devices, methods, and graphical user interfaces for displaying and using menus
US10095396B2 (en) 2015-03-08 2018-10-09 Apple Inc. Devices, methods, and graphical user interfaces for interacting with a control object while dragging another object
US10048757B2 (en) 2015-03-08 2018-08-14 Apple Inc. Devices and methods for controlling media presentation
EP3070900A1 (en) * 2015-03-16 2016-09-21 Thomson Licensing Method and system of access of a mobile terminal to information in an area
US9785305B2 (en) 2015-03-19 2017-10-10 Apple Inc. Touch input cursor manipulation
CN104793844B (en) * 2015-03-31 2017-05-17 北京奇虎科技有限公司 Plug-in achieving method and device based on host program on mobile terminal
US20170045981A1 (en) 2015-08-10 2017-02-16 Apple Inc. Devices and Methods for Processing Touch Inputs Based on Their Intensities
USD766294S1 (en) 2015-04-02 2016-09-13 Kenneth Smith Display screen with graphical user interface
USD766954S1 (en) 2015-04-02 2016-09-20 Kenneth Smith Display screen with graphical user interface
USD769921S1 (en) 2015-04-02 2016-10-25 Kenneth Smith Display screen with graphical user interface
USD768678S1 (en) * 2015-04-02 2016-10-11 Kenneth Smith Display screen with graphical user interface
USD766295S1 (en) * 2015-04-02 2016-09-13 Kenneth Smith Display screen with graphical user interface
USD769283S1 (en) 2015-04-02 2016-10-18 Kenneth Smith Display screen with graphical user interface
USD780191S1 (en) * 2015-04-29 2017-02-28 Elijah Kelley Display screen with graphical user interface
US9665654B2 (en) 2015-04-30 2017-05-30 Icharts, Inc. Secure connections in an interactive analytic visualization infrastructure
US9813570B2 (en) * 2015-05-11 2017-11-07 Ricoh Company, Ltd. Information processing apparatus, information processing method, and computer program product
US10922094B2 (en) * 2015-06-05 2021-02-16 Apple Inc. Systems and methods for proactively providing recommendations to a user of a computing device
US9674426B2 (en) 2015-06-07 2017-06-06 Apple Inc. Devices and methods for capturing and interacting with enhanced digital images
US9860451B2 (en) 2015-06-07 2018-01-02 Apple Inc. Devices and methods for capturing and interacting with enhanced digital images
US9361011B1 (en) * 2015-06-14 2016-06-07 Google Inc. Methods and systems for presenting multiple live video feeds in a user interface
CN107967116B (en) 2015-06-16 2019-07-19 深圳市腾讯计算机系统有限公司 The method and apparatus, computer equipment of lock onto target in scene of game
CN105094608A (en) * 2015-07-17 2015-11-25 小米科技有限责任公司 Task display method and device
US9888145B2 (en) 2015-08-03 2018-02-06 Canon Information And Imaging Solutions, Inc. System and method enabling resetting of a counter associated with a component of an image processing device
USD863332S1 (en) 2015-08-12 2019-10-15 Samsung Electronics Co., Ltd. Display screen or portion thereof with graphical user interface
USD820289S1 (en) * 2015-08-12 2018-06-12 Samsung Electronics Co., Ltd. Display screen or portion thereof with graphical user interface
KR102360178B1 (en) * 2015-08-25 2022-02-08 삼성전자주식회사 System and method for providing application list
US10332090B2 (en) 2015-08-27 2019-06-25 Acumera, Inc. Providing secure remote access to a device at a merchant location
CN105260201B (en) * 2015-09-14 2019-08-06 小米科技有限责任公司 Using installation method, device and smart machine
USD768657S1 (en) * 2015-10-21 2016-10-11 Microsoft Corporation Display screen with graphical user interface
USD768658S1 (en) * 2015-10-21 2016-10-11 Microsoft Corporation Display screen with animated graphical user interface
CN105159564A (en) * 2015-10-23 2015-12-16 上海斐讯数据通信技术有限公司 Electronic device provided with touch display screen and application program deletion management method thereof
WO2017082764A1 (en) * 2015-11-09 2017-05-18 Валентина Митрофановна АРТЕМЕНКО Touch-sensitive cell phone
US10949184B2 (en) 2015-11-19 2021-03-16 Tokn Pty Ltd Method and system of application deployment on a mobile communication device
CN105487753B (en) * 2015-11-26 2018-06-22 网易(杭州)网络有限公司 The association method for down loading of game of mobile terminal
RU2015152232A (en) * 2015-12-07 2017-06-13 Максим Викторович Есин Portable Digital Device Communication System
JP6925365B2 (en) 2015-12-21 2021-08-25 チャンベッラ・リミテッド Methods and equipment for creating and managing controller-based remote solutions
CN106921377B (en) * 2015-12-24 2020-06-02 小米科技有限责任公司 Touch key module, key icon display method and device
EP4354268A3 (en) * 2015-12-24 2024-04-24 Huawei Technologies Co., Ltd. Method for displaying multiple application windows by mobile terminal, and mobile terminal
KR20170076489A (en) * 2015-12-24 2017-07-04 삼성전자주식회사 electronic device and method for managing application program thereof
CN105892816A (en) * 2016-03-31 2016-08-24 北京奇虎科技有限公司 Method and device for calculating equipment desktop resetting
CN105912198A (en) * 2016-04-01 2016-08-31 厦门美柚信息科技有限公司 Information recording method and device
CN107347053B (en) * 2016-05-06 2020-12-01 苏州清云网络科技有限公司 Management execution platform constructed based on network video streaming computing method
CN106020592A (en) * 2016-05-09 2016-10-12 北京小米移动软件有限公司 Split screen display method and device
US11087249B2 (en) 2016-05-24 2021-08-10 Ciambella Ltd. Method and apparatus for triggering execution of a workflow over a network
AU2017100667A4 (en) 2016-06-11 2017-07-06 Apple Inc. Activity and workout updates
DK201670581A1 (en) 2016-06-12 2018-01-08 Apple Inc Device-level authorization for viewing content
DK201670582A1 (en) 2016-06-12 2018-01-02 Apple Inc Identifying applications on which content is available
USD848459S1 (en) 2016-07-11 2019-05-14 Xiaofeng Li Display screen with graphical user interface for controlling an electronic candle
USD824936S1 (en) 2016-07-22 2018-08-07 Xiaofeng Li Display screen with graphical user interface for operating an electronic candle
US10798780B2 (en) 2016-08-22 2020-10-06 Ciambella Ltd. Method and apparatus for creating and managing controller based remote solutions
USD810770S1 (en) * 2016-09-21 2018-02-20 Uipco, Llc Display panel or portion thereof with graphical user interface
USD811426S1 (en) * 2016-09-21 2018-02-27 Uipco, Llc Display panel or portion thereof with graphical user interface
US11966560B2 (en) 2016-10-26 2024-04-23 Apple Inc. User interfaces for browsing content from multiple content applications on an electronic device
USD943624S1 (en) 2016-10-27 2022-02-15 Apple Inc. Electronic device with pair of display screens or portions thereof each with animated graphical user interface
USD927529S1 (en) 2019-01-11 2021-08-10 Apple Inc. Electronic device with pair of display screens or portions thereof each with graphical user interface
USD842892S1 (en) * 2016-10-27 2019-03-12 Apple Inc. Electronic device with pair of display screens or portions thereof each with graphical user interface
USD862489S1 (en) * 2016-12-29 2019-10-08 Samsung Electronics Co., Ltd. Display screen or portion thereof with graphical user interface
US10231103B2 (en) * 2017-01-26 2019-03-12 Vmware, Inc. Automated provisioning of applications
USD813251S1 (en) * 2017-02-27 2018-03-20 Tata Consultancy Services Limited Display screen with animated graphical user interface
USD865795S1 (en) * 2017-03-24 2019-11-05 Samsung Electronics Co., Ltd. Display screen or portion thereof with graphical user interface
CN106970868A (en) * 2017-04-10 2017-07-21 广东欧珀移动通信有限公司 Method for information display, device and terminal
CN107203398B (en) * 2017-05-26 2020-11-13 北京小米移动软件有限公司 Application distribution method and device
US10955994B2 (en) * 2017-06-02 2021-03-23 Apple Inc. User interfaces for downloading applications on an electronic device
USD936663S1 (en) 2017-06-04 2021-11-23 Apple Inc. Display screen or portion thereof with graphical user interface
USD831039S1 (en) 2017-06-05 2018-10-16 Apple Inc. Display screen or portion thereof with graphical user interface
KR101920389B1 (en) * 2017-06-27 2018-11-20 스마트샵주식회사 System and method for controlling selective operation of a service module installed in parallel with an application
USD889491S1 (en) * 2017-07-19 2020-07-07 Lenovo (Beijing) Co., Ltd. Display screen or a portion thereof with graphical user interface
CN107704751A (en) * 2017-08-23 2018-02-16 深圳天珑无线科技有限公司 A kind of cipher-code input method, mobile terminal and the device with store function
CN107566875A (en) * 2017-08-31 2018-01-09 江苏省公用信息有限公司 A kind of UI flexible configurations on Intelligent set top box, the method for dynamic renewal
USD887443S1 (en) * 2017-09-11 2020-06-16 Apple Inc. Display screen or portion thereof with graphical user interface
US10417232B2 (en) * 2017-12-22 2019-09-17 Microsoft Technology Licensing, Llc Associating hardware to store applications
US20190228847A1 (en) * 2018-01-22 2019-07-25 Apple Inc. Systems and methods for displaying aggregated health records
USD858556S1 (en) * 2018-05-07 2019-09-03 Google Llc Display screen or portion thereof with an animated graphical interface
USD859450S1 (en) * 2018-05-07 2019-09-10 Google Llc Display screen or portion thereof with an animated graphical interface
DK201870354A1 (en) 2018-06-03 2019-12-20 Apple Inc. Setup procedures for an electronic device
AU2019100574B4 (en) * 2018-06-03 2020-02-20 Apple Inc. Setup procedures for an electronic device
US10546444B2 (en) 2018-06-21 2020-01-28 Capital One Services, Llc Systems and methods for secure read-only authentication
USD884021S1 (en) * 2018-09-24 2020-05-12 Salesforce.Com, Inc. Display screen or portion thereof with animated graphical user interface
USD884022S1 (en) * 2018-09-24 2020-05-12 Salesforce.Com, Inc. Display screen or portion thereof with animated graphical user interface
JP2022502901A (en) 2018-10-02 2022-01-11 キャピタル・ワン・サービシーズ・リミテッド・ライアビリティ・カンパニーCapital One Services, LLC Systems and methods for cryptographic authentication of non-contact cards
US10630653B1 (en) 2018-10-02 2020-04-21 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
CA3108917A1 (en) 2018-10-02 2020-04-09 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10511443B1 (en) 2018-10-02 2019-12-17 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10771253B2 (en) 2018-10-02 2020-09-08 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
JP2022511281A (en) 2018-10-02 2022-01-31 キャピタル・ワン・サービシーズ・リミテッド・ライアビリティ・カンパニー Systems and methods for cryptographic authentication of non-contact cards
US10949520B2 (en) 2018-10-02 2021-03-16 Capital One Services, Llc Systems and methods for cross coupling risk analytics and one-time-passcodes
AU2019355878A1 (en) 2018-10-02 2021-02-25 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10909527B2 (en) 2018-10-02 2021-02-02 Capital One Services, Llc Systems and methods for performing a reissue of a contactless card
US10579998B1 (en) 2018-10-02 2020-03-03 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10771254B2 (en) 2018-10-02 2020-09-08 Capital One Services, Llc Systems and methods for email-based card activation
WO2020072537A1 (en) 2018-10-02 2020-04-09 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10733645B2 (en) 2018-10-02 2020-08-04 Capital One Services, Llc Systems and methods for establishing identity for order pick up
MX2021003217A (en) 2018-10-02 2021-05-12 Capital One Services Llc Systems and methods for cryptographic authentication of contactless cards.
US10542036B1 (en) 2018-10-02 2020-01-21 Capital One Services, Llc Systems and methods for signaling an attack on contactless cards
JP2022508026A (en) 2018-10-02 2022-01-19 キャピタル・ワン・サービシーズ・リミテッド・ライアビリティ・カンパニー Systems and methods for cryptographic authentication of non-contact cards
US10581611B1 (en) 2018-10-02 2020-03-03 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10686603B2 (en) 2018-10-02 2020-06-16 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10582386B1 (en) 2018-10-02 2020-03-03 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
CA3115107A1 (en) 2018-10-02 2020-04-09 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10489781B1 (en) 2018-10-02 2019-11-26 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10554411B1 (en) 2018-10-02 2020-02-04 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
CA3115064A1 (en) 2018-10-02 2020-04-09 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10607214B1 (en) 2018-10-02 2020-03-31 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10783519B2 (en) 2018-10-02 2020-09-22 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10565587B1 (en) 2018-10-02 2020-02-18 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US11210664B2 (en) 2018-10-02 2021-12-28 Capital One Services, Llc Systems and methods for amplifying the strength of cryptographic algorithms
WO2020072440A1 (en) 2018-10-02 2020-04-09 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10505738B1 (en) 2018-10-02 2019-12-10 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10592710B1 (en) 2018-10-02 2020-03-17 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
CN112823492B (en) 2018-10-08 2024-08-13 西安姆贝拉有限公司 System, apparatus and method for providing an end-to-end solution for a network
DE102018126231A1 (en) * 2018-10-22 2020-04-23 Endress+Hauser SE+Co. KG Control module for a field device of automation technology and the same field device
US11063946B2 (en) 2018-10-24 2021-07-13 Servicenow, Inc. Feedback framework
US10664830B1 (en) 2018-12-18 2020-05-26 Capital One Services, Llc Devices and methods for selective contactless communication
US11361302B2 (en) 2019-01-11 2022-06-14 Capital One Services, Llc Systems and methods for touch screen interface interaction using a card overlay
US11037136B2 (en) 2019-01-24 2021-06-15 Capital One Services, Llc Tap to autofill card data
US10467622B1 (en) 2019-02-01 2019-11-05 Capital One Services, Llc Using on-demand applications to generate virtual numbers for a contactless card to securely autofill forms
US10510074B1 (en) 2019-02-01 2019-12-17 Capital One Services, Llc One-tap payment using a contactless card
US11120453B2 (en) 2019-02-01 2021-09-14 Capital One Services, Llc Tap card to securely generate card data to copy to clipboard
US10425129B1 (en) 2019-02-27 2019-09-24 Capital One Services, Llc Techniques to reduce power consumption in near field communication systems
US11375043B2 (en) * 2019-03-06 2022-06-28 Citizen Watch Co., Ltd. Program management system, external device and terminal device for controlling a program developer's ability to access, publish and manage marketing of a program
US10904375B2 (en) * 2019-03-18 2021-01-26 Apple Inc. User interfaces for subscription applications
AU2020100285B4 (en) * 2019-03-18 2020-09-10 Apple Inc. User interfaces for subscription applications
US10523708B1 (en) 2019-03-18 2019-12-31 Capital One Services, Llc System and method for second factor authentication of customer support calls
US10984416B2 (en) 2019-03-20 2021-04-20 Capital One Services, Llc NFC mobile currency transfer
US10643420B1 (en) 2019-03-20 2020-05-05 Capital One Services, Llc Contextual tapping engine
US10438437B1 (en) 2019-03-20 2019-10-08 Capital One Services, Llc Tap to copy data to clipboard via NFC
US10535062B1 (en) 2019-03-20 2020-01-14 Capital One Services, Llc Using a contactless card to securely share personal data stored in a blockchain
US10970712B2 (en) 2019-03-21 2021-04-06 Capital One Services, Llc Delegated administration of permissions using a contactless card
CN113711169A (en) 2019-03-24 2021-11-26 苹果公司 User interface including selectable representations of content items
CN113940088A (en) 2019-03-24 2022-01-14 苹果公司 User interface for viewing and accessing content on an electronic device
US11962836B2 (en) 2019-03-24 2024-04-16 Apple Inc. User interfaces for a media browsing application
US11683565B2 (en) 2019-03-24 2023-06-20 Apple Inc. User interfaces for interacting with channels that provide content that plays in a media browsing application
US10467445B1 (en) 2019-03-28 2019-11-05 Capital One Services, Llc Devices and methods for contactless card alignment with a foldable mobile device
DK201970532A1 (en) 2019-05-06 2021-05-03 Apple Inc Activity trends and workouts
CN110187889A (en) * 2019-05-23 2019-08-30 腾讯科技(深圳)有限公司 A kind of application starting method, apparatus and storage medium
US11521262B2 (en) 2019-05-28 2022-12-06 Capital One Services, Llc NFC enhanced augmented reality information overlays
USD937858S1 (en) 2019-05-31 2021-12-07 Apple Inc. Display screen or portion thereof with graphical user interface
CN113906380A (en) 2019-05-31 2022-01-07 苹果公司 User interface for podcast browsing and playback applications
US11863837B2 (en) 2019-05-31 2024-01-02 Apple Inc. Notification of augmented reality content on an electronic device
US11209957B2 (en) 2019-06-01 2021-12-28 Apple Inc. User interfaces for cycle tracking
US11152100B2 (en) 2019-06-01 2021-10-19 Apple Inc. Health application user interfaces
US11481205B2 (en) * 2019-06-01 2022-10-25 Apple Inc. User interfaces for managing subscriptions
US10516447B1 (en) 2019-06-17 2019-12-24 Capital One Services, Llc Dynamic power levels in NFC card communications
US10871958B1 (en) 2019-07-03 2020-12-22 Capital One Services, Llc Techniques to perform applet programming
US11392933B2 (en) 2019-07-03 2022-07-19 Capital One Services, Llc Systems and methods for providing online and hybridcard interactions
US11694187B2 (en) 2019-07-03 2023-07-04 Capital One Services, Llc Constraining transactional capabilities for contactless cards
US12086852B2 (en) 2019-07-08 2024-09-10 Capital One Services, Llc Authenticating voice transactions with payment card
US10713649B1 (en) 2019-07-09 2020-07-14 Capital One Services, Llc System and method enabling mobile near-field communication to update display on a payment card
US10498401B1 (en) 2019-07-15 2019-12-03 Capital One Services, Llc System and method for guiding card positioning using phone sensors
US10885514B1 (en) 2019-07-15 2021-01-05 Capital One Services, Llc System and method for using image data to trigger contactless card transactions
US10733601B1 (en) 2019-07-17 2020-08-04 Capital One Services, Llc Body area network facilitated authentication or payment authorization
US11182771B2 (en) 2019-07-17 2021-11-23 Capital One Services, Llc System for value loading onto in-vehicle device
US10832271B1 (en) 2019-07-17 2020-11-10 Capital One Services, Llc Verified reviews using a contactless card
US12002588B2 (en) 2019-07-17 2024-06-04 Apple Inc. Health event logging and coaching user interfaces
US11521213B2 (en) 2019-07-18 2022-12-06 Capital One Services, Llc Continuous authentication for digital services based on contactless card positioning
US10506426B1 (en) 2019-07-19 2019-12-10 Capital One Services, Llc Techniques for call authentication
US10541995B1 (en) 2019-07-23 2020-01-21 Capital One Services, Llc First factor contactless card authentication system and method
EP4004702A1 (en) 2019-09-09 2022-06-01 Apple Inc. Research study user interfaces
US11750585B2 (en) 2019-09-30 2023-09-05 Acumera, Inc. Secure ephemeral access to insecure devices
CA3153291A1 (en) 2019-10-02 2021-04-08 Evan Lerner Client device authentication using contactless legacy magnetic stripe data
US10657754B1 (en) 2019-12-23 2020-05-19 Capital One Services, Llc Contactless card and personal identification system
US10862540B1 (en) 2019-12-23 2020-12-08 Capital One Services, Llc Method for mapping NFC field strength and location on mobile devices
US10733283B1 (en) 2019-12-23 2020-08-04 Capital One Services, Llc Secure password generation and management using NFC and contactless smart cards
US11615395B2 (en) 2019-12-23 2023-03-28 Capital One Services, Llc Authentication for third party digital wallet provisioning
US11113685B2 (en) 2019-12-23 2021-09-07 Capital One Services, Llc Card issuing with restricted virtual numbers
US10885410B1 (en) 2019-12-23 2021-01-05 Capital One Services, Llc Generating barcodes utilizing cryptographic techniques
US11651361B2 (en) 2019-12-23 2023-05-16 Capital One Services, Llc Secure authentication based on passport data stored in a contactless card
US11200563B2 (en) 2019-12-24 2021-12-14 Capital One Services, Llc Account registration using a contactless card
US10853795B1 (en) 2019-12-24 2020-12-01 Capital One Services, Llc Secure authentication based on identity data stored in a contactless card
US10664941B1 (en) 2019-12-24 2020-05-26 Capital One Services, Llc Steganographic image encoding of biometric template information on a card
US10909544B1 (en) 2019-12-26 2021-02-02 Capital One Services, Llc Accessing and utilizing multiple loyalty point accounts
US10757574B1 (en) 2019-12-26 2020-08-25 Capital One Services, Llc Multi-factor authentication providing a credential via a contactless card for secure messaging
US11038688B1 (en) 2019-12-30 2021-06-15 Capital One Services, Llc Techniques to control applets for contactless cards
US10860914B1 (en) 2019-12-31 2020-12-08 Capital One Services, Llc Contactless card and method of assembly
US11455620B2 (en) 2019-12-31 2022-09-27 Capital One Services, Llc Tapping a contactless card to a computing device to provision a virtual number
USD937295S1 (en) 2020-02-03 2021-11-30 Apple Inc. Display screen or portion thereof with graphical user interface
USD958167S1 (en) * 2020-03-23 2022-07-19 Companion Medical, Inc. Display screen with graphical user interface
US11843838B2 (en) 2020-03-24 2023-12-12 Apple Inc. User interfaces for accessing episodes of a content series
US11210656B2 (en) 2020-04-13 2021-12-28 Capital One Services, Llc Determining specific terms for contactless card activation
US10915888B1 (en) 2020-04-30 2021-02-09 Capital One Services, Llc Contactless card with multiple rotating security keys
US10861006B1 (en) 2020-04-30 2020-12-08 Capital One Services, Llc Systems and methods for data access control using a short-range transceiver
US11030339B1 (en) 2020-04-30 2021-06-08 Capital One Services, Llc Systems and methods for data access control of personal user data using a short-range transceiver
US11222342B2 (en) 2020-04-30 2022-01-11 Capital One Services, Llc Accurate images in graphical user interfaces to enable data transfer
US11823175B2 (en) 2020-04-30 2023-11-21 Capital One Services, Llc Intelligent card unlock
US10963865B1 (en) 2020-05-12 2021-03-30 Capital One Services, Llc Augmented reality card activation experience
US11063979B1 (en) 2020-05-18 2021-07-13 Capital One Services, Llc Enabling communications between applications in a mobile operating system
US11100511B1 (en) 2020-05-18 2021-08-24 Capital One Services, Llc Application-based point of sale system in mobile operating systems
DK181037B1 (en) 2020-06-02 2022-10-10 Apple Inc User interfaces for health applications
USD951288S1 (en) 2020-06-20 2022-05-10 Apple Inc. Display screen or portion thereof with graphical user interface
USD965616S1 (en) 2020-06-20 2022-10-04 Apple Inc. Display screen or portion thereof with animated graphical user interface
US11899895B2 (en) 2020-06-21 2024-02-13 Apple Inc. User interfaces for setting up an electronic device
USD948535S1 (en) * 2020-06-22 2022-04-12 Apple Inc. Display screen or portion thereof with graphical user interface
USD1043735S1 (en) * 2020-08-03 2024-09-24 Google Llc Display screen or portion thereof with graphical user interface
US11062098B1 (en) 2020-08-11 2021-07-13 Capital One Services, Llc Augmented reality information display and interaction via NFC based authentication
US11698710B2 (en) 2020-08-31 2023-07-11 Apple Inc. User interfaces for logging user activities
USD962970S1 (en) * 2020-10-29 2022-09-06 Smiths Medical Asd, Inc. Display screen or portion thereof with graphical user interface
US11482312B2 (en) 2020-10-30 2022-10-25 Capital One Services, Llc Secure verification of medical status using a contactless card
US11165586B1 (en) 2020-10-30 2021-11-02 Capital One Services, Llc Call center web-based authentication using a contactless card
US11373169B2 (en) 2020-11-03 2022-06-28 Capital One Services, Llc Web-based activation of contactless cards
US11720229B2 (en) 2020-12-07 2023-08-08 Apple Inc. User interfaces for browsing and presenting content
US11216799B1 (en) 2021-01-04 2022-01-04 Capital One Services, Llc Secure generation of one-time passcodes using a contactless card
US11682012B2 (en) 2021-01-27 2023-06-20 Capital One Services, Llc Contactless delivery systems and methods
US11687930B2 (en) 2021-01-28 2023-06-27 Capital One Services, Llc Systems and methods for authentication of access tokens
US11792001B2 (en) 2021-01-28 2023-10-17 Capital One Services, Llc Systems and methods for secure reprovisioning
US11562358B2 (en) 2021-01-28 2023-01-24 Capital One Services, Llc Systems and methods for near field contactless card communication and cryptographic authentication
USD1004598S1 (en) * 2021-01-29 2023-11-14 Abbott Diabetes Care Inc. Display screen or portion thereof with graphical user interface
US11934640B2 (en) 2021-01-29 2024-03-19 Apple Inc. User interfaces for record labels
US11438329B2 (en) 2021-01-29 2022-09-06 Capital One Services, Llc Systems and methods for authenticated peer-to-peer data transfer using resource locators
US11777933B2 (en) 2021-02-03 2023-10-03 Capital One Services, Llc URL-based authentication for payment cards
US11637826B2 (en) 2021-02-24 2023-04-25 Capital One Services, Llc Establishing authentication persistence
US11245438B1 (en) 2021-03-26 2022-02-08 Capital One Services, Llc Network-enabled smart apparatus and systems and methods for activating and provisioning same
USD988339S1 (en) * 2021-03-31 2023-06-06 Netflix, Inc. Display panel of a programmed computer system with a graphical user interface
US11935035B2 (en) 2021-04-20 2024-03-19 Capital One Services, Llc Techniques to utilize resource locators by a contactless card to perform a sequence of operations
US11961089B2 (en) 2021-04-20 2024-04-16 Capital One Services, Llc On-demand applications to extend web services
US11902442B2 (en) 2021-04-22 2024-02-13 Capital One Services, Llc Secure management of accounts on display devices using a contactless card
US11354555B1 (en) 2021-05-04 2022-06-07 Capital One Services, Llc Methods, mediums, and systems for applying a display to a transaction card
US11449188B1 (en) 2021-05-15 2022-09-20 Apple Inc. Shared-content session user interfaces
US11907605B2 (en) 2021-05-15 2024-02-20 Apple Inc. Shared-content session user interfaces
US12041172B2 (en) 2021-06-25 2024-07-16 Capital One Services, Llc Cryptographic authentication to control access to storage devices
US12061682B2 (en) 2021-07-19 2024-08-13 Capital One Services, Llc System and method to perform digital authentication using multiple channels of communication
US12062258B2 (en) 2021-09-16 2024-08-13 Capital One Services, Llc Use of a payment card to unlock a lock
USD978187S1 (en) 2021-09-17 2023-02-14 Slack Technologies, Llc Display screen or portion thereof with animated graphical user interface
USD985616S1 (en) 2021-09-17 2023-05-09 Slack Technologies, Llc Display screen or portion thereof with animated graphical user interface
US11812135B2 (en) 2021-09-24 2023-11-07 Apple Inc. Wide angle video conference
USD1026029S1 (en) * 2021-09-28 2024-05-07 Beijing Zitiao Network Technology Co., Ltd. Display screen or portion thereof with a graphical user interface
USD1025118S1 (en) * 2021-09-28 2024-04-30 Beijing Zitiao Network Technology Co., Ltd. Display screen or portion thereof with a graphical user interface
USD1024102S1 (en) 2021-09-28 2024-04-23 Beijing Zitiao Network Technology Co., Ltd. Display screen or portion thereof with a graphical user interface
USD1024101S1 (en) 2021-09-28 2024-04-23 Beijing Zitiao Network Technology Co., Ltd. Display screen or portion thereof with a graphical user interface
KR20230065574A (en) * 2021-11-05 2023-05-12 석정웅 Method and apparatus for providing application generation service
US12069173B2 (en) 2021-12-15 2024-08-20 Capital One Services, Llc Key recovery based on contactless card authentication
WO2023235143A1 (en) * 2022-05-31 2023-12-07 Apple Inc. Two-layer bandit optimization for recommendations
USD1035680S1 (en) 2022-06-06 2024-07-16 Apple Inc. Display screen or portion thereof with graphical user interface
US12124903B2 (en) 2023-03-16 2024-10-22 Capital One Services, Llc Card with a time-sensitive element and systems and methods for implementing the same

Citations (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH03233750A (en) 1990-02-09 1991-10-17 Fujitsu Ltd Process state display/conversion system
US5406307A (en) 1989-12-05 1995-04-11 Sony Corporation Data processing apparatus having simplified icon display
US5634128A (en) 1993-09-24 1997-05-27 International Business Machines Corporation Method and system for controlling access to objects in a data processing system
WO1999022325A1 (en) 1997-10-24 1999-05-06 Microsoft Corporation System and method for managing application installation for a mobile device
JP2000148348A (en) 1998-11-13 2000-05-26 Internatl Business Mach Corp <Ibm> Method and system capable of easily discriminating application being activated program and completing the same
KR20010000586A (en) 2000-10-07 2001-01-05 구자혁 Download Method for utilizing computer communication
US6570557B1 (en) 2001-02-10 2003-05-27 Finger Works, Inc. Multi-touch system and method for emulating modifier keys via fingertip chords
WO2003058410A1 (en) 2001-12-28 2003-07-17 Access Co., Ltd. Usage period management system for applications
JP2003256062A (en) 2001-12-28 2003-09-10 Access:Kk Expiration date management system for application
US20030236867A1 (en) * 2001-05-14 2003-12-25 Takeshi Natsuno System for managing program stored in storage block of mobile terminal
JP2004118365A (en) 2002-09-24 2004-04-15 Yoshitaka Yamamoto Distribution system for online software
US20040109013A1 (en) 2002-12-10 2004-06-10 Magnus Goertz User interface
US20040130576A1 (en) 2003-01-08 2004-07-08 Pioneer Corporation Touchscreen display device
EP1462999A2 (en) 2003-03-27 2004-09-29 Microsoft Corporation Application-centric user interface techniques
JP2004348599A (en) 2003-05-23 2004-12-09 Sony Corp Information processor and method, and control program thereof
US20050154798A1 (en) 2004-01-09 2005-07-14 Nokia Corporation Adaptive user interface input device
JP2005196617A (en) 2004-01-09 2005-07-21 Sony Corp Information processor, information processing method, recording medium and program
JP2005251167A (en) 2004-01-09 2005-09-15 Microsoft Corp On-device application catalog updated by management server
US20060212548A1 (en) 2005-03-15 2006-09-21 Microsoft Corporation Method and system for installing applications via a display page
RU2005125837A (en) 2004-08-16 2007-02-20 Майкрософт Корпорейшн (Us) COMMAND USER INTERFACE FOR DISPLAYING ON THE SCREEN OF SELECTABLE FUNCTIONAL CONTROLS OF THE SOFTWARE
WO2007052285A2 (en) 2005-07-22 2007-05-10 Yogesh Chunilal Rathod Universal knowledge management and desktop search system
US20080052945A1 (en) * 2006-09-06 2008-03-06 Michael Matas Portable Electronic Device for Photo Management
US20080208452A1 (en) 2005-11-08 2008-08-28 Bayerische Motoren Werke Aktiengesellschaft Method and System for Updating Card Data of a Navigation System
WO2009148781A1 (en) 2008-06-06 2009-12-10 Apple Inc. User interface for application management for a mobile device

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US1462999A (en) * 1923-07-24 Locking device fob
CA1317678C (en) 1989-03-20 1993-05-11 William Jaaskelainen Dynamic progress marking icon
JP3873362B2 (en) * 1997-04-04 2007-01-24 カシオ計算機株式会社 Network system and recording medium
US6104397A (en) 1997-06-30 2000-08-15 Sun Microsystems, Inc. Method and system for generating improved progress indicators
US6414697B1 (en) 1999-01-28 2002-07-02 International Business Machines Corporation Method and system for providing an iconic progress indicator
JP2003521754A (en) * 1999-02-26 2003-07-15 アクセンチュール エルエルピー System, method and product for e-commerce interface with government agencies
JP4033619B2 (en) * 2000-05-26 2008-01-16 シャープ株式会社 Server device
WO2002003199A1 (en) * 2000-07-03 2002-01-10 Access Co., Ltd. Mobile information terminal device, storage server, and method for providing storage region
AU2002226995A1 (en) 2000-11-28 2002-06-11 4Thpass Inc. Method and system for maintaining and distributing wireless applications
US7729925B2 (en) * 2000-12-08 2010-06-01 Sony Corporation System and method for facilitating real time transactions between a user and multiple entities
US20030023513A1 (en) * 2001-04-06 2003-01-30 Phil Festa E-business systems and methods for diversfied businesses
JP3941620B2 (en) * 2001-08-31 2007-07-04 株式会社デンソーウェーブ Electronic device with built-in ID tag
JP2003268160A (en) * 2002-03-14 2003-09-25 Asahi Kasei Corp Latex composition and composition for paper coating
US9715500B2 (en) * 2004-04-27 2017-07-25 Apple Inc. Method and system for sharing playlists
JP3928852B2 (en) 2002-04-08 2007-06-13 ソニー・エリクソン・モバイルコミュニケーションズ株式会社 Mobile communication terminal
JP2005289816A (en) 2002-05-14 2005-10-20 Banyu Pharmaceut Co Ltd Benzimidazole derivative
US7360174B2 (en) * 2002-12-19 2008-04-15 Microsoft Corporation Contact user interface
CA2438368A1 (en) * 2003-08-26 2005-02-26 Winnie W.N. Lai A method and system for creating navigational information for an electronic store from virtual and master catalog links
US7113981B2 (en) * 2003-12-29 2006-09-26 Mixxer, Inc. Cellular telephone download locker
US20060265409A1 (en) 2005-05-21 2006-11-23 Apple Computer, Inc. Acquisition, management and synchronization of podcasts
US7711835B2 (en) * 2004-09-30 2010-05-04 Citrix Systems, Inc. Method and apparatus for reducing disclosure of proprietary data in a networked environment
US8099482B2 (en) * 2004-10-01 2012-01-17 E-Cast Inc. Prioritized content download for an entertainment device
EP1768359A3 (en) * 2004-11-09 2007-07-25 Research In Motion Limited Dynamic bar oriented user interface for a device having a status bar displaying status information concerning the device
WO2007006126A1 (en) 2005-04-18 2007-01-18 Research In Motion Limited Method and system for hosting and executing a component application
US8225312B2 (en) * 2005-08-12 2012-07-17 Sony Corporation Method and apparatus for downloading software updates
US8117554B1 (en) * 2006-04-25 2012-02-14 Parallels Holdings, Ltd. Seamless integration of non-native widgets and windows with dynamically scalable resolution into native operating system
US8924269B2 (en) * 2006-05-13 2014-12-30 Sap Ag Consistent set of interfaces derived from a business object model
US20080147671A1 (en) * 2006-12-18 2008-06-19 Lampdesk Corporation System for Running Web Applications Offline and Providing Access to Native Services
US20080271066A1 (en) * 2007-04-27 2008-10-30 Spielman Howard L Local message performance on an entertainment system

Patent Citations (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5406307A (en) 1989-12-05 1995-04-11 Sony Corporation Data processing apparatus having simplified icon display
JPH03233750A (en) 1990-02-09 1991-10-17 Fujitsu Ltd Process state display/conversion system
US5634128A (en) 1993-09-24 1997-05-27 International Business Machines Corporation Method and system for controlling access to objects in a data processing system
WO1999022325A1 (en) 1997-10-24 1999-05-06 Microsoft Corporation System and method for managing application installation for a mobile device
JP2001521254A (en) 1997-10-24 2001-11-06 マイクロソフト コーポレイション Mobile device application installation management system and method
JP2000148348A (en) 1998-11-13 2000-05-26 Internatl Business Mach Corp <Ibm> Method and system capable of easily discriminating application being activated program and completing the same
KR20010000586A (en) 2000-10-07 2001-01-05 구자혁 Download Method for utilizing computer communication
US6570557B1 (en) 2001-02-10 2003-05-27 Finger Works, Inc. Multi-touch system and method for emulating modifier keys via fingertip chords
US20030236867A1 (en) * 2001-05-14 2003-12-25 Takeshi Natsuno System for managing program stored in storage block of mobile terminal
WO2003058410A1 (en) 2001-12-28 2003-07-17 Access Co., Ltd. Usage period management system for applications
JP2003256062A (en) 2001-12-28 2003-09-10 Access:Kk Expiration date management system for application
AU2002359001A1 (en) 2001-12-28 2003-07-24 Access Co., Ltd. Usage period management system for applications
US20050044191A1 (en) 2001-12-28 2005-02-24 Access Co., Ltd Usage period management system for applications
JP2004118365A (en) 2002-09-24 2004-04-15 Yoshitaka Yamamoto Distribution system for online software
US20040109013A1 (en) 2002-12-10 2004-06-10 Magnus Goertz User interface
US20040130576A1 (en) 2003-01-08 2004-07-08 Pioneer Corporation Touchscreen display device
KR20040086535A (en) 2003-03-27 2004-10-11 마이크로소프트 코포레이션 Application-centric user interface techniques
KR101086125B1 (en) 2003-03-27 2011-11-25 마이크로소프트 코포레이션 Application-centric user interface techniques
US20040192440A1 (en) 2003-03-27 2004-09-30 Microsoft Corporation Application-centric user interface techniques
JP2004326736A (en) 2003-03-27 2004-11-18 Microsoft Corp Application-centered user interface method
EP1462999A2 (en) 2003-03-27 2004-09-29 Microsoft Corporation Application-centric user interface techniques
CN1534471A (en) 2003-03-27 2004-10-06 Application program centrol user interface technology
JP2004348599A (en) 2003-05-23 2004-12-09 Sony Corp Information processor and method, and control program thereof
US20050154798A1 (en) 2004-01-09 2005-07-14 Nokia Corporation Adaptive user interface input device
JP2005196617A (en) 2004-01-09 2005-07-21 Sony Corp Information processor, information processing method, recording medium and program
JP2005251167A (en) 2004-01-09 2005-09-15 Microsoft Corp On-device application catalog updated by management server
CN1906565A (en) 2004-01-09 2007-01-31 诺基亚公司 Adaptive user interface input device
RU2005125837A (en) 2004-08-16 2007-02-20 Майкрософт Корпорейшн (Us) COMMAND USER INTERFACE FOR DISPLAYING ON THE SCREEN OF SELECTABLE FUNCTIONAL CONTROLS OF THE SOFTWARE
US20060212548A1 (en) 2005-03-15 2006-09-21 Microsoft Corporation Method and system for installing applications via a display page
WO2007052285A2 (en) 2005-07-22 2007-05-10 Yogesh Chunilal Rathod Universal knowledge management and desktop search system
US20080208452A1 (en) 2005-11-08 2008-08-28 Bayerische Motoren Werke Aktiengesellschaft Method and System for Updating Card Data of a Navigation System
US20080052945A1 (en) * 2006-09-06 2008-03-06 Michael Matas Portable Electronic Device for Photo Management
WO2009148781A1 (en) 2008-06-06 2009-12-10 Apple Inc. User interface for application management for a mobile device
US8099332B2 (en) 2008-06-06 2012-01-17 Apple Inc. User interface for application management for a mobile device
US20120117504A1 (en) 2008-06-06 2012-05-10 Apple Inc. User Interface for Application Management for a Mobile Device
US8751321B2 (en) * 2008-06-06 2014-06-10 Apple Inc. User interface for application management for a mobile device

Non-Patent Citations (59)

* Cited by examiner, † Cited by third party
Title
Ascii.jp, "Listen and Purchase & Play Immediately!! A Wonderful World of Wi-Fi Stores", Ascii.jp [online] Japan, Kabushiki Kaisha Kadokawa, https://ascii.jp/elem/000/000/069/69364, Sep. 23, 2007, 5 pages.
Certificate of Patent, dated Aug. 13, 2015, received in Korean Patent Application No. 10-2013-7002719, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Decision to Grant, dated Sep. 28, 2012, received in Russian Patent Application No. 2010153571, which corresponds with U.S. Appl. No. 12/354,616, 6 pages.
Final Office Action mailed on Apr. 27, 2011 for U.S. Appl. No. 12/354,616, 10 pages.
Hirokawa, Getting Started with Super Easy iPod Touch Hack, MAC Power 2008 Winter, Japan, Kabushiki Kaisha Ascii, first edition, ISBN 978-4-7561-5081-3, Dec. 21, 2007, 4 pages.
Ikeda, iPhone 2.0 Beta & Software Development Kit (SDK) Released, MacFan, Japan, Kabushiki Kaisha Mainichi Communications, vol. 16, No. 5, (vol. 301), May 1, 2008, 10 pages.
International Preliminary Report on Patentability mailed Dec. 6, 2010 for PCT Patent Application No. PCT/US2009/043840, 8 pages.
International Search Report and Written Opinion mailed Aug. 12, 2009 for PCT Patent Application No. PCT/US2009/043840, 15 pages.
Non-Final Office Action mailed on Aug. 24, 2010 for U.S. Appl. No. 12/354,616, 9 pages.
Non-Final Office Action mailed on Jul. 31, 2013 for U.S. Appl. No. 13/350,563, 20 pages.
Notice of Acceptance, dated Jul. 14, 2016, received in Australian Patent Application No. 2014215929, which corresponds with U.S. Appl. No. 13/354,616, 2 pages.
Notice of Acceptance, dated Jul. 5, 2012, received in Australian Patent Application No. 2009255409, which corresponds with U.S. Appl. No. 12/354,616, 3 pages.
Notice of Acceptance, dated Jun. 30, 2014, received in Australian Patent Application No. 2012203197, which corresponds with U.S. Appl. No. 13/354,616, 1 page.
Notice of Allowance mailed on Jan. 31, 2014 for U.S. Appl. No. 13/350,563, 12 pages.
Notice of Allowance mailed on Nov. 16, 2011 for U.S. Appl. No. 12/354,616, 5 pages.
Notice of Allowance, dated Apr. 22, 2016, received in Japanese Patent Application No. 2014-031795, which corresponds with U.S. Appl. No. 12/354,616, 5 pages.
Notice of Allowance, dated Jun. 30, 2015, received in Korean Patent Application No. 10-2013-7002719, which corresponds with U.S. Appl. No. 12/354,616, 1 page.
Notice of Allowance, dated Mar. 16, 2017, received in Canadian Patent Application No. 2726117, which corresponds with U.S. Appl. No. 12/354,616, 1 page.
Notice of Allowance, dated May 6, 2014, received in U.S. Appl. No. 13/350,563, 5 pages.
Notice of Allowance, dated Sep. 22, 2015, received in Canadian Patent Application No. 2,726,117, which corresponds with U.S. Appl. No. 12/354,616, 1 page.
Notice of Grant, dated Apr. 22, 2016, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 5 pages.
Notice of Reinstatement, dated Apr. 27, 2016, received in Canadian Patent Application No. 2,726,117, which corresponds with U.S. Appl. No. 12/354,616, 4 pages.
Notification of Grant, dated Nov. 26, 2014, received in Singapore Patent Application No. 201088250, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, date Jul. 15, 2015, received in Australian Patent Applicaton No. 2012203197, which corresponds with U.S. Appl. No. 13/354,616, 3 pages.
Office Action, dated Apr. 10, 2013, received in Mexican Patent Application No. MX/a/2010/013377, which corresponds with U.S. Appl. No. 12/354,616, 6 pages.
Office Action, dated Apr. 10, 2014, received in European Patent Application No. 09 758 944.4, which corresponds with U.S. Appl. No. 12/354,616, 6 pages.
Office Action, dated Apr. 3, 2017, received in Japanese Patent Application No. 2016-100793, which corresponds with U.S. Appl. No. 12/354,616, 8 pages.
Office Action, dated Aug. 1, 2013, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Aug. 4, 2014, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Aug. 8, 2014, received in Korean Patent Application No. 10-2013-7002719, which corresponds with U.S. Appl. No. 12/354,616, 4 pages.
Office Action, dated Dec. 16, 2013, received in Mexican Patent Application No. MX/a/2010/013377, which corresponds with U.S. Appl. No. 12/354,616, 6 pages.
Office Action, dated Dec. 19, 2016, received in Indian Patent Application No. 7906/CHENP/2010, which corresponds with U.S. Appl. No. 12/354,616, 7 pages.
Office Action, dated Dec. 6, 2011, received in Australian Patent Application No. 2009255409, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Feb. 2, 2016, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 3 pages.
Office Action, dated Feb. 21, 2013, received in Canadian Patent Application No. 2,726,117, which corresponds with U.S. Appl. No. 12/354,616, 3 pages.
Office Action, dated Feb. 29, 2012, received in Russian Patent Application No. 2010153571, which corresponds with U.S. Appl. No. 12/354,616, 4 pages.
Office Action, dated Jan. 17, 2014, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Jan. 18, 2012, received in European Patent Application No. 09 758 944.4, which corresponds with U.S. Appl. No. 12/354,616, 5 pages.
Office Action, dated Jan. 4, 2015, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Jul. 1, 2013, received in Australian Patent Application No. 2012203197, which corresponds with U.S. Appl. No. 12/354,616, 3 pages.
Office Action, dated Jul. 2, 2015, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Jun. 28, 2013, received in Korean Patent Application No. 10-2011-7000351, which corresponds with U.S. Appl. No. 12/354,616, 4 page.
Office Action, dated Jun. 29, 2015, received in Japanese Patent Application No. 2011-512509, which corresponds with U.S. Appl. No. 12/354,616, 3 pages.
Office Action, dated Jun. 30, 2012, received in Korean Patent Application No. 10-2011-7000351, which corresponds with U.S. Appl. No. 12/354,616, 1 page.
Office Action, dated Mar. 15, 2016, received in Korean Patent Application No. 10-2014-7014295, which corresponds with U.S. Appl. No. 12/354,616, 5 pages.
Office Action, dated May 7, 2013, received in Japanese Patent Application No. 2011-512509, which corresponds with U.S. Appl. No. 12/354,616, 5 pages.
Office Action, dated Nov. 23, 2012, received in Chinese Patent Application No. 200980127249.6, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Nov. 25, 2013, received in Canadian Patent Application No. 2,726,117, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Oct. 2, 2014, received in Canadian Patent Application No. 2,726,117, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Office Action, dated Sep. 7, 2012, received in Japanese Patent Application No. 2011-512509, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Patent, dated Apr. 11, 2017, received in Canadian Patent Application No. 2726117, which corresponds with U.S. Appl. No. 12/354,616, 3 pages.
Patent, dated May 27, 2016, received in Japanese Patent Application No. 2014-031795, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Patent, dated Sep. 1, 2017, received in Honk Kong Application No. 11113270.1, which corresponds with U.S. Appl. No. 12/354,616, 2 pages.
Softbank Corporation, "Task Bar Type Launcher," Oh! PC, Japan, Nov. 1, 1997, vol. 16, No. 11, p. 187.
Submission of Prior Art Under 37 CFR1.501, dated Apr. 26, 2012, received in U.S. Appl. No. 12/235,616, 38 pages.
Submission of Prior Art Under 37 CFR1.501, dated Jul. 19, 2012, received in U.S. Appl. No. 12/235,616, 86 pages.
Submission of Prior Art Under 37 CFR1.501, dated Jun. 11, 2012, received in U.S. Appl. No. 12/235,616, 53 pages.
Toru, "For iPod & iTunes Beginners," Nikkei Personal Computing No. 533, Nikkei Business Publications, Inc., Jul. 9, 2007, No. 533, 8 pages.
Written Opinion, dated Feb. 15, 2012, received in Singapore Patent Application No. 201008825-0, 5 pages.

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10152205B2 (en) 2015-01-05 2018-12-11 Samsung Electronics Co., Ltd. Display apparatus and display method
US11169662B2 (en) 2015-01-05 2021-11-09 Samsung Electronics Co., Ltd. Display apparatus and display method

Also Published As

Publication number Publication date
JP5941079B2 (en) 2016-06-29
US20180335904A1 (en) 2018-11-22
US20190265850A1 (en) 2019-08-29
JP5486593B2 (en) 2014-05-07
JP2020061160A (en) 2020-04-16
BRPI0915601B1 (en) 2021-02-02
AU2009255409A1 (en) 2009-12-10
JP2014139800A (en) 2014-07-31
US20090307105A1 (en) 2009-12-10
AU2009255409B2 (en) 2012-07-05
CN106157116B (en) 2020-03-03
JP6514144B2 (en) 2019-05-15
US10318119B2 (en) 2019-06-11
RU2477879C2 (en) 2013-03-20
RU2635231C2 (en) 2017-11-09
US20120117504A1 (en) 2012-05-10
JP2016177831A (en) 2016-10-06
AU2012203197A1 (en) 2012-06-21
US20140250015A1 (en) 2014-09-04
US20220214782A1 (en) 2022-07-07
CA2726117C (en) 2017-04-11
MX2010013377A (en) 2011-06-16
US8099332B2 (en) 2012-01-17
KR20110016990A (en) 2011-02-18
CN102089744A (en) 2011-06-08
KR20140081896A (en) 2014-07-01
CN102089744B (en) 2016-05-25
CA2726117A1 (en) 2009-12-10
AU2012203197B2 (en) 2014-07-24
WO2009148781A1 (en) 2009-12-10
US20240201828A1 (en) 2024-06-20
KR101382932B1 (en) 2014-04-08
US8751321B2 (en) 2014-06-10
KR101787184B1 (en) 2017-10-18
KR101546166B1 (en) 2015-08-20
US11947776B2 (en) 2024-04-02
US11320961B2 (en) 2022-05-03
JP6622863B2 (en) 2019-12-18
CN106157116A (en) 2016-11-23
RU2010153571A (en) 2012-07-20
KR20130028140A (en) 2013-03-18
JP7090059B2 (en) 2022-06-23
RU2013104079A (en) 2014-08-10
JP2011525275A (en) 2011-09-15
JP2018185846A (en) 2018-11-22
EP2300916A1 (en) 2011-03-30

Similar Documents

Publication Publication Date Title
US11947776B2 (en) Systems and methods for providing and interacting with application-update objects on a mobile device
US11656737B2 (en) Adding a contact to a home screen
US11416122B2 (en) Location text
AU2019203723B2 (en) User interface for application management for a mobile device
AU2014215929B2 (en) User interface for application management for a mobile device

Legal Events

Date Code Title Description
STCF Information on status: patent grant

Free format text: PATENTED CASE

CC Certificate of correction
MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4