US20140365895A1 - Device and method for generating user interfaces from a template - Google Patents

Abstract

An electronic device is configured to receive a first request to display a user interface of a first third-party application on a respective display that is in communication with the device. The device is further configured to, in response to receiving the request, obtain a first user-interface template configured to be used by a plurality of third-party applications, and request, from the first application, one or more values for populating the first template. The device is also configured to receive, from the first application, while the first application is running on the device, a first set of values for populating the first template; populate the first template with the first set of values; generate a first user interface for the first application using the first template populated with the first set of values; and send information to the respective display that enables the first user interface to be displayed.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
• This application claims priority to U.S. Provisional Patent Application No. 61/832,841, filed Jun. 8, 2013, and is related to the following applications: U.S. Provisional Application Ser. No. 61/793,924, filed Mar. 15, 2013, entitled “Voice and Touch User Interface”; U.S. application Ser. No. 13/032,614, filed Feb. 22, 2011, entitled “Pushing a Graphical User Interface to a Remote Device with Display Rules Provided by the Remote Device”; U.S. application Ser. No. 12/683,218, filed Jan. 6, 2010, entitled “Pushing a User Interface to a Remote Device”; U.S. application Ser. No. 12/119,960, filed May 13, 2008, entitled “Pushing a User Interface to a Remote Device”; U.S. application Ser. No. 13/175,581, filed Jul. 1, 2011, entitled “Pushing a User Interface to a Remote Device”; U.S. application Ser. No. 13/161,339, filed Jun. 15, 2011, entitled “Pushing a Graphical User Interface to a Remote Device with Display Rules Provided by the Remote Device”; U.S. application Ser. No. 13/250,947, filed Sep. 30, 2011, entitled “Automatically Adapting User Interfaces for Hands-Free Interaction”; U.S. application Ser. No. 12/987,982, filed Jan. 10, 2011, entitled “Intelligent Automated Assistant”; U.S. Provisional Application Ser. No. 61/295,774, filed Jan. 18, 2010, entitled “Intelligent Automated Assistant”; U.S. Provisional Application Ser. No. 61/493,201, filed Jun. 3, 2011, entitled “Generating and Processing Data Items that Represent Tasks to Perform”; U.S. Provisional Application Ser. No. 61/657,744, filed Jun. 9, 2012, entitled “Automatically Adapting User Interface for Hands-Free Interaction”; U.S. application Ser. No. 12/207,316, filed Sep. 9, 2008, entitled “Radio with Personal DJ”; U.S. Provisional Application Ser. No. 61/727,554, filed Nov. 16, 2012, entitled “System and Method for Negotiating Control of a Shared Audio or Visual Resource”; U.S. Application Ser. No. 61/832,818, filed Jun. 8, 2013, entitled “Mapping Application with Several User Interfaces,”; U.S. application Ser. No. 13/913,428, filed Jun. 8, 2013, entitled “Application Gateway for Providing Different User Interfaces for Limited Distraction and Non-Limited Distraction Contexts,”; U.S. Provisional Application Ser. No. 61/832,842, filed Jun. 8, 2013, entitled “Device, Method, and Graphical User Interface for Synchronizing Two of More Displays,” which applications are incorporated herein by reference in their entirety.
TECHNICAL FIELD
• This relates generally to electronic devices for generating user interfaces, including, but not limited to, providing user interfaces for third-party applications.
BACKGROUND
• The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensitive surfaces include touch pads and touch screen displays. Such surfaces are widely used to manipulate user interface objects on a first display associated with a first electronic device.
• Exemplary manipulations include adjusting the position and/or size of one or more user interface objects, activating buttons or opening files/applications represented by user interface objects, or otherwise manipulating user interfaces. Exemplary user interface objects include digital images, video, text, icons, control elements such as buttons and other graphics.
• Devices sometimes have first-party (or native) device software (e.g., an operating system for the device and applications developed by or at the direction of the same entity that developed the operating system) and third-party software that includes applications developed separately from the first-party (or native) device software. Third party applications are sometimes loaded on a device to provide additional functionality to the device.
SUMMARY
• But the user interfaces of third-party applications are often custom and/or application-specific. Additionally, application-specific user interfaces sometimes include words or controls that are too small to be safely used while driving a vehicle. Moreover, different custom and/or application-specific user interfaces for different applications sometimes put controls with similar functions in different locations, so that users will have to take additional time and attention to locate and determine the function of these different controls. Thus, having different custom and/or application-specific user interfaces for different applications is cumbersome and inefficient. In addition, in some circumstances, these user interfaces take longer than necessary for a user manipulate, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.
• Accordingly, there is a need for electronic devices with faster, more efficient methods for providing access to third-party applications and eliminating driver distraction when using third-party applications. Generating user interfaces from a template for use with third-party applications that increase the legibility and ease of use of user interfaces for interacting with third-party applications eliminates driver distraction and improves user efficiency. Such methods optionally complement or replace conventional methods for generating user interfaces and providing access to third-party applications. Such methods reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated devices, such methods conserve power and increase the time between battery charges.
• The above deficiencies and other problems associated with user interfaces for electronic devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch screen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, website creating, disk authoring, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, and/or digital video playing. Executable instructions for performing these functions are, optionally, included in a non-transitory computer readable storage medium or other computer program product configured for execution by one or more processors.
• In accordance with some embodiments, a method is performed at an electronic device with one or more processors and memory. The method includes receiving a first display request to display a user interface of a first third-party application on a respective display that is in communication with the electronic device. In response to receiving the first display request, the method includes: obtaining a first user-interface template that is configured to be used by a plurality of third-party applications; and requesting, from the first third-party application, one or more values for populating the first user-interface template. The method further includes receiving, from the first third-party application, while the first third-party application is running on the electronic device, a first set of values for populating the first user-interface template; populating the first user-interface template with the first set of values received from the first third-party application; generating a first user interface for the first third-party application using the first user-interface template populated with the first set of values; and sending information to the respective display that enables the first user interface for the first third-party application to be displayed on the respective display.
• In accordance with some embodiments, an electronic device includes memory and a processing unit coupled to the memory. The processing unit is configured to receive a first display request to display a user interface of a first third-party application on a respective display unit that is in communication with the electronic device. The processing unit is further configured to, in response to receiving the first display request: obtain a first user-interface template that is configured to be used by a plurality of third-party applications; and request, from the first third-party application, one or more values for populating the first user-interface template. The processing unit is also configured to receive, from the first third-party application, while the first third-party application is running on the electronic device, a first set of values for populating the first user-interface template; populate the first user-interface template with the first set of values received from the first third-party application; generate a first user interface for the first third-party application using the first user-interface template populated with the first set of values; and send information to the respective display unit that enables the first user interface for the first third-party application to be displayed on the respective display unit.
• In accordance with some embodiments, an electronic device includes one or more processors, memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors and the one or more programs include instructions for performing the operations of any of the methods described herein. In accordance with some embodiments, a non-transitory computer readable storage medium has stored therein instructions which when executed by an electronic device, cause the device to perform the operations of any of the methods described herein. In accordance with some embodiments, an electronic device includes a means for performing the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in a first electronic device, includes means for performing the operations of any of the methods described herein.
• Thus, electronic devices with displays are provided with faster, more efficient methods for providing user interfaces for third-party applications, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for generating user interfaces.
BRIEF DESCRIPTION OF THE DRAWINGS
• For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
• FIG. 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.
• FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.
• FIG. 2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.
• FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.
• FIG. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.
• FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.
• FIG. 5 is a block diagram illustrating an operating environment in which a portable multifunction device communicates with an external information presentation system and/or a server in accordance with some embodiments.
• FIGS. 6A-6C illustrate exemplary user interfaces generated from a template in accordance with some embodiments.
• FIGS. 7A-7I are flow diagrams illustrating a method of generating user interfaces from a template in accordance with some embodiments.
• FIG. 8 is a functional block diagram of an electronic device in accordance with some embodiments.
DESCRIPTION OF EMBODIMENTS
• Many electronic devices use graphical user interfaces. Many of the graphical user interfaces are custom designed, or are specific to an individual application. The methods and devices described below improve on these methods by generating user interfaces from a user-interface template for use with third-party applications. In some embodiments, the user-interface template is a generic or application-agnostic user-interface template that is used by a plurality of different applications. These user interfaces are displayed on a respective display. Using the same generic user interface template for a number of different third-party applications helps to standardize the user interfaces of the third-party applications. This standardization makes the third-party applications more intuitive, and easier and more convenient to interact with, while still providing the user with access to the functionality of the third-party applications.
• These templates are particularly helpful in situations where a device is providing access to the third-party application on an information presentation system that is external to the device, such as a smart phone providing access to a third-party application on the smartphone via a touch screen display in a car. The information presentation system optionally has a display with one of a plurality of different sets of operational properties (e.g., display dimensions, control types, etc.). In some embodiments, the respective display is a display in a vehicle information display system that is visible from a driver seat of a vehicle, so as to improve the ease of use of the third-party application by the driver and/or passengers in the vehicle.
• Below,FIGS. 1A-1B,2, and3 provide a description of exemplary devices.FIGS. 4A-4B and6A-6C illustrate exemplary user interfaces generated from a template.FIGS. 7A-7I are flow diagrams illustrating a method of providing user interfaces for third-party applications.FIG. 8 is a functional block diagram of an electronic device. The user interfaces inFIGS. 6A-6C are used to illustrate the processes inFIGS. 7A-7I.
Exemplary Devices
• Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
• It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact.
• The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
• As used herein, the term “if′ is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or ‘upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
• Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touch pad).
• In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.
• The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
• The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
• Attention is now directed toward embodiments of portable devices with touch-sensitive displays.FIG. 1A is a block diagram illustrating portablemultifunction device100 with touch-sensitive displays112 in accordance with some embodiments. Touch-sensitive display112 is sometimes called a “touch screen” for convenience, and is sometimes known as or called a touch-sensitive display system.Device100 includes memory102 (which optionally includes one or more computer readable storage mediums),memory controller122, one or more processing units (CPU's)120, peripherals interface118,RF circuitry108,audio circuitry110,speaker111,microphone113, input/output (I/O) subsystem106, other input orcontrol devices116, andexternal port124.Device100 optionally includes one or moreoptical sensors164.Device100 optionally includes one ormore intensity sensors165 for detecting intensity of contacts on device100 (e.g., a touch-sensitive surface such as touch-sensitive display system112 of device100).Device100 optionally includes one or moretactile output generators167 for generating tactile outputs on device100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system112 ofdevice100 ortouchpad355 of device300). These components optionally communicate over one or more communication buses orsignal lines103.
• As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure).
• As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
• It should be appreciated thatdevice100 is only one example of a portable multifunction device, and thatdevice100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown inFIG. 1A are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.
• Memory102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access tomemory102 by other components ofdevice100, such asCPU120 and theperipherals interface118, is, optionally, controlled bymemory controller122.
• Peripherals interface118 can be used to couple input and output peripherals of the device toCPU120 andmemory102. The one ormore processors120 run or execute various software programs and/or sets of instructions stored inmemory102 to perform various functions fordevice100 and to process data.
• In some embodiments, peripherals interface118,CPU120, andmemory controller122 are, optionally, implemented on a single chip, such aschip104. In some other embodiments, they are, optionally, implemented on separate chips.
• RF (radio frequency)circuitry108 receives and sends RF signals, also called electromagnetic signals.RF circuitry108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals.RF circuitry108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth.RF circuitry108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication optionally uses any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoiP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
• Audio circuitry110,speaker111, andmicrophone113 provide an audio interface between a user anddevice100.Audio circuitry110 receives audio data fromperipherals interface118, converts the audio data to an electrical signal, and transmits the electrical signal tospeaker111.Speaker111 converts the electrical signal to human-audible sound waves.Audio circuitry110 also receives electrical signals converted bymicrophone113 from sound waves.Audio circuitry110 converts the electrical signal to audio data and transmits the audio data to peripherals interface118 for processing. Audio data is, optionally, retrieved from and/or transmitted tomemory102 and/orRF circuitry108 byperipherals interface118. In some embodiments,audio circuitry110 also includes a headset jack (e.g.,212,FIG. 2). The headset jack provides an interface betweenaudio circuitry110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone).
• I/O subsystem106 couples input/output peripherals ondevice100, such astouch screen112 and otherinput control devices116, toperipherals interface118. I/O subsystem106 optionally includesdisplay controller156,optical sensor controller158,intensity sensor controller159,haptic feedback controller161 and one ormore input controllers160 for other input or control devices. The one ormore input controllers160 receive/send electrical signals from/to other input orcontrol devices116. The otherinput control devices116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s)160 are, optionally, coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g.,208,FIG. 2) optionally include an up/down button for volume control ofspeaker111 and/ormicrophone113. The one or more buttons optionally include a push button (e.g.,206,FIG. 2).
• Touch-sensitive display112 provides an input interface and an output interface between the device and a user.Display controller156 receives and/or sends electrical signals from/totouch screen112.Touch screen112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user-interface objects.
• Touch screen112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact.Touch screen112 and display controller156 (along with any associated modules and/or sets of instructions in memory102) detect contact (and any movement or breaking of the contact) ontouch screen112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed ontouch screen112. In an exemplary embodiment, a point of contact betweentouch screen112 and the user corresponds to a finger of the user.
• Touch screen112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments.Touch screen112 anddisplay controller156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, 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 withtouch screen112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.
• Touch screen112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact withtouch screen112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
• In some embodiments, in addition to the touch screen,device100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate fromtouch screen112 or an extension of the touch-sensitive surface formed by the touch screen.
• Device100 also includespower system162 for powering the various components.Power system162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
• Device100 optionally also includes one or moreoptical sensors164.FIG. 1A shows an optical sensor coupled tooptical sensor controller158 in I/O subsystem106.Optical sensor164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors.Optical sensor164 receives light from the environment, projected through one or more lens, and converts the light to data representing an image. In conjunction with imaging module143 (also called a camera module),optical sensor164 optionally captures still images or video. In some embodiments, an optical sensor is located on the back ofdevice100, oppositetouch screen display112 on the front of the device, so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, another optical sensor is located on the front of the device so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conference participants on the touch screen display.
• Device100 optionally also includes one or morecontact intensity sensors165.FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller159 in I/O subsystem106.Contact intensity sensor165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface).Contact intensity sensor165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system112). In some embodiments, at least one contact intensity sensor is located on the back ofdevice100, oppositetouch screen display112 which is located on the front ofdevice100.
• Device100 optionally also includes one ormore proximity sensors166.FIG. 1A showsproximity sensor166 coupled toperipherals interface118. Alternately,proximity sensor166 is coupled to inputcontroller160 in I/O subsystem106. In some embodiments, the proximity sensor turns off and disablestouch screen112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).
• Device100 optionally also includes one or moretactile output generators167.FIG. 1A shows a tactile output generator coupled tohaptic feedback controller161 in I/O subsystem106.Tactile output generator167 optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device).Contact intensity sensor165 receives tactile feedback generation instructions fromhaptic feedback module133 and generates tactile outputs ondevice100 that are capable of being sensed by a user ofdevice100. In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system112) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device100) or laterally (e.g., back and forth in the same plane as a surface of device100). In some embodiments, at least one tactile output generator sensor is located on the back ofdevice100, oppositetouch screen display112 which is located on the front ofdevice100.
• Device100 optionally also includes one ormore accelerometers168.FIG. 1A showsaccelerometer168 coupled toperipherals interface118. Alternately,accelerometer168 is, optionally, coupled to aninput controller160 in I/O subsystem106. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers.Device100 optionally includes, in addition to accelerometer(s)168, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information concerning the location and orientation (e.g., portrait or landscape) ofdevice100.
• In some embodiments, the software components stored inmemory102 includeoperating system126, communication module (or set of instructions)128, contact/motion module (or set of instructions)130, graphics module (or set of instructions)132, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions)136. Furthermore, in someembodiments memory102 stores device/globalinternal state157, as shown inFIGS. 1A and 3. Device/globalinternal state157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions oftouch screen display112; sensor state, including information obtained from the device's various sensors andinput control devices116; and location information concerning the device's location and/or attitude.
• Operating system126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
• Communication module128 facilitates communication with other devices over one or moreexternal ports124 and also includes various software components for handling data received byRF circuitry108 and/orexternal port124. External port124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used on iPod (trademark of Apple Inc.) devices. In some embodiments, the external port is a multi-pin (e.g., 8-pin) connector that is the same as, or similar to and/or compatible with the 8-pin connector (e.g., Lightning connector) used on iPhone and iPod (trademark of Apple Inc.) devices.
• Contact/motion module130 optionally detects contact with touch screen112 (in conjunction with display controller156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module130 anddisplay controller156 detect contact on a touchpad.
• In some embodiments, contact/motion module130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined thresholds values without changing the trackpad or touch screen display hardware. Additionally, in some implementations a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
• Contact/motion module130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event.
• Graphics module132 includes various known software components for rendering and displaying graphics ontouch screen112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
• In some embodiments,graphics module132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code.Graphics module132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to displaycontroller156.
• Haptic feedback module133 includes various software components for generating instructions used by tactile output generator(s)167 to produce tactile outputs at one or more locations ondevice100 in response to user interactions withdevice100.
• Text input module134, which is, optionally, a component ofgraphics module132, provides soft keyboards for entering text in various applications (e.g.,contacts137, e-mail140,IM141,browser147, and any other application that needs text input).
• GPS module135 determines the location of the device and provides this information for use in various applications (e.g., to telephone138 for use in location-based dialing, tocamera143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
• Applications136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
• • contacts module137 (sometimes called an address book or contact list);
  • telephone module138;
  • video conferencing module139;
  • e-mail client module140;
  • instant messaging (IM)module141;
  • Internet radio module142;
  • camera module143 for still and/or video images;
  • image management module144;
  • browser module147;
  • calendar module148;
  • widget modules149, which optionally include one or more of: weather widget149-1, stocks widget149-2, calculator widget149-3, alarm clock widget149-4, dictionary widget149-5, and other widgets obtained by the user, as well as user-created widgets149-6;
  • digitalpersonal assistant module150;
  • vehicle integration module151;
  • video andmusic player module152, which is, optionally, made up of a video player module and a music player module;
  • notes module153;
  • map module154; and/or
  • music library module155.
• Examples ofother applications136 that are, optionally, stored inmemory102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
• In conjunction withtouch screen112,display controller156,contact module130,graphics module132, andtext input module134,contacts module137 are, optionally, used to manage an address book or contact list (e.g., stored in applicationinternal state192 ofcontacts module137 inmemory102 or memory370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications bytelephone138,video conference139,e-mail140, orIM141; and so forth.
• In conjunction withRF circuitry108,audio circuitry110,speaker111,microphone113,touch screen112,display controller156,contact module130,graphics module132, andtext input module134,telephone module138 are, optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers inaddress book137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies.
• In conjunction withRF circuitry108,audio circuitry110,speaker111,microphone113,touch screen112,display controller156,optical sensor164,optical sensor controller158,contact module130,graphics module132,text input module134,contact list137, andtelephone module138,videoconferencing module139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
• In conjunction withRF circuitry108,touch screen112,display controller156,contact module130,graphics module132, andtext input module134,e-mail client module140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction withimage management module144,e-mail client module140 makes it very easy to create and send e-mails with still or video images taken withcamera module143.
• In conjunction withRF circuitry108,touch screen112,display controller156,contact module130,graphics module132, andtext input module134, theinstant messaging module141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
• In conjunction withtouch screen112,display system controller156,contact module130,graphics module132,audio circuitry110,speaker111, andRF circuitry108,Internet radio module142 is a prophetic third-party application that includes executable instructions to select and play Internet radio stations.
• In conjunction withtouch screen112,display controller156, optical sensor(s)164,optical sensor controller158,contact module130,graphics module132, andimage management module144,camera module143 includes executable instructions to capture still images or video (including a video stream) and store them intomemory102, modify characteristics of a still image or video, or delete a still image or video frommemory102.
• In conjunction withtouch screen112,display controller156,contact module130,graphics module132,text input module134, andcamera module143,image management module144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
• In conjunction withRF circuitry108,touch screen112,display system controller156,contact module130,graphics module132, andtext input module134,browser module147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
• In conjunction withRF circuitry108,touch screen112,display system controller156,contact module130,graphics module132,text input module134,e-mail client module140, andbrowser module147,calendar module148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
• In conjunction withRF circuitry108,touch screen112,display system controller156,contact module130,graphics module132,text input module134, andbrowser module147,widget modules149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget149-1, stocks widget149-2, calculator widget149-3, alarm clock widget149-4, and dictionary widget149-5) or created by the user (e.g., user-created widget149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
• In conjunction withRF circuitry108,audio circuitry110,speaker111,microphone113,touch screen112,display controller156,contact module130,graphics module132, andtext input module134, digitalpersonal assistant module150 records voice commands and sends information representative of the recorded voice commands to a server such asserver510 inFIG. 5 for analysis, and responds to the voice commands based on a response from the server.
• Vehicle integration module151 includes executable instructions for one or more intermediation processes that control a vehicle information display system in a vehicle (e.g., a car, a truck, a van, etc.) that provides a user interface on a respective display of the vehicle information display system (e.g., display547 of externalinformation presentation system540 inFIG. 5), such as for a mapping application or a music application. The vehicle integration application converts information from third-party applications into content for display by the vehicle integration application on the respective display of the vehicle information display system.
• In conjunction withtouch screen112,display system controller156,contact module130,graphics module132,audio circuitry110,speaker111,RF circuitry108, andbrowser module147, video andmusic player module152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., ontouch screen112 or on an external, connected display via external port124). In some embodiments,device100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
• In conjunction withtouch screen112,display controller156,contact module130,graphics module132, andtext input module134, notesmodule153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
• In conjunction withRF circuitry108,touch screen112,display system controller156,contact module130,graphics module132,text input module134,GPS module135, andbrowser module147,map module154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
• In conjunction withtouch screen112,display system controller156,contact module130,graphics module132,audio circuitry110, speaker Ill, andRF circuitry108,music library module155 is a prophetic third-party application that includes executable instructions to select and play songs from a music library.
• Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments,memory102 optionally stores a subset of the modules and data structures identified above. Furthermore,memory102 optionally stores additional modules and data structures not described above.
• In some embodiments,device100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation ofdevice100, the number of physical input control devices (such as push buttons, dials, and the like) ondevice100 is, optionally, reduced.
• The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigatesdevice100 to a main, home, or root menu from any user interface that is displayed ondevice100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
• FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory102 (inFIG. 1A) or370 (FIG. 3) includes event sorter170 (e.g., in operating system126) and a respective application136-1 (e.g., any of the aforementioned applications137-13,155,380-390).
• Event sorter170 receives event information and determines the application136-1 andapplication view191 of application136-1 to which to deliver the event information.Event sorter170 includes event monitor171 andevent dispatcher module174. In some embodiments, application136-1 includes applicationinternal state192, which indicates the current application view(s) displayed on touchsensitive display112 when the application is active or executing. In some embodiments, device/globalinternal state157 is used byevent sorter170 to determine which application(s) is (are) currently active, and applicationinternal state192 is used byevent sorter170 to determineapplication views191 to which to deliver event information.
• In some embodiments, applicationinternal state192 includes additional information, such as one or more of: resume information to be used when application136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application136-1, a state queue for enabling the user to go back to a prior state or view of application136-1, and a redo/undo queue of previous actions taken by the user.
• Event monitor171 receives event information fromperipherals interface118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display112, as part of a multi-touch gesture). Peripherals interface118 transmits information it receives from I/O subsystem106 or a sensor, such asproximity sensor166, accelerometer(s)168, and/or microphone113 (through audio circuitry110). Information that peripherals interface118 receives from I/O subsystem106 includes information from touch-sensitive display112 or a touch-sensitive surface.
• In some embodiments, event monitor171 sends requests to the peripherals interface118 at predetermined intervals. In response, peripherals interface118 transmits event information. In other embodiments,peripheral interface118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
• In some embodiments,event sorter170 also includes a hitview determination module172 and/or an active eventrecognizer determination module173.
• Hitview determination module172 provides software procedures for determining where a sub-event has taken place within one or more views, when touchsensitive display112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
• Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
• Hitview determination module172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hitview determination module172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
• Active eventrecognizer determination module173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active eventrecognizer determination module173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active eventrecognizer determination module173 determines that all views that include the physic allocation of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
• Event dispatcher module174 dispatches the event information to an event recognizer (e.g., event recognizer180). In embodiments including active eventrecognizer determination module173,event dispatcher module174 delivers the event information to an event recognizer determined by active eventrecognizer determination module173. In some embodiments,event dispatcher module174 stores in an event queue the event information, which is retrieved by a respectiveevent receiver module182.
• In some embodiments,operating system126 includesevent sorter170. Alternatively, application136-1 includesevent sorter170. In yet other embodiments,event sorter170 is a stand-alone module, or a part of another module stored inmemory102, such as contact/motion module130.
• In some embodiments, application136-1 includes a plurality ofevent handlers190 and one or more application views191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Eachapplication view191 of the application136-1 includes one ormore event recognizers180. Typically, arespective application view191 includes a plurality ofevent recognizers180. In other embodiments, one or more ofevent recognizers180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application136-1 inherits methods and other properties. In some embodiments, arespective event handler190 includes one or more of:data updater176,object updater177,GUI updater178, and/orevent data179 received fromevent sorter170.Event handler190 optionally utilizes or callsdata updater176,object updater177 orGUI updater178 to update the applicationinternal state192. Alternatively, one or more of the application views191 includes one or morerespective event handlers190. Also, in some embodiments, one or more ofdata updater176,object updater177, andGUI updater178 are included in arespective application view191.
• Arespective event recognizer180 receives event information (e.g., event data179) fromevent sorter170, and identifies an event from the event information.Event recognizer180 includesevent receiver182 andevent comparator184. In some embodiments,event recognizer180 also includes at least a subset of:metadata183, and event delivery instructions188 (which optionally include sub-event delivery instructions).
• Event receiver182 receives event information fromevent sorter170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
• Event comparator184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments,event comparator184 includesevent definitions186.Event definitions186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associatedevent handlers190.
• In some embodiments, event definition187 includes a definition of an event for a respective user-interface object. In some embodiments,event comparator184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display112, when a touch is detected on touch-sensitive display112,event comparator184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with arespective event handler190, the event comparator uses the result of the hit test to determine whichevent handler190 should be activated. For example,event comparator184 selects an event handler associated with the sub-event and the object triggering the hit test.
• In some embodiments, the definition for a respective event187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
• When arespective event recognizer180 determines that the series of sub-events do not match any of the events inevent definitions186, therespective event recognizer180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
• In some embodiments, arespective event recognizer180 includesmetadata183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments,metadata183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments,metadata183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
• In some embodiments, arespective event recognizer180 activatesevent handler190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, arespective event recognizer180 delivers event information associated with the event toevent handler190. Activating anevent handler190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments,event recognizer180 throws a flag associated with the recognized event, andevent handler190 associated with the flag catches the flag and performs a predefined process.
• In some embodiments,event delivery instructions188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
• In some embodiments,data updater176 creates and updates data used in application136-1. For example,data updater176 updates the telephone number used incontacts module137, or stores a video file used in video player module145. In some embodiments, objectupdater177 creates and updates objects used in application136-1. For example, objectupdater176 creates a new user-interface object or updates the position of a user-interface object.GUI updater178 updates the GUI. For example,GUI updater178 prepares display information and sends it tographics module132 for display on a touch-sensitive display.
• In some embodiments, event handler(s)190 includes or has access todata updater176,object updater177, andGUI updater178. In some embodiments,data updater176,object updater177, andGUI updater178 are included in a single module of a respective application136-1 orapplication view191. In other embodiments, they are included in two or more software modules.
• It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operatemultifunction devices100 with input-devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
• FIG. 2 illustrates aportable multifunction device100 having atouch screen112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI)200. In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers202 (not drawn to scale in the figure) or one or more styluses203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward) and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact withdevice100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.
• Device100 optionally also includes one or more physical buttons, such as “home” ormenu button204. As described previously,menu button204 is, optionally, used to navigate to anyapplication136 in a set of applications that are, optionally executed ondevice100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed ontouch screen112.
• In one embodiment,device100 includestouch screen112,menu button204,push button206 for powering the device on/off and locking the device, volume adjustment button(s)208, Subscriber Identity Module (SIM)card slot210, head setjack212, and docking/chargingexternal port124.Push button206 is, optionally, used to tum the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment,device100 also accepts verbal input for activation or deactivation of some functions throughmicrophone113.Device100 also, optionally, includes one or morecontact intensity sensors165 for detecting intensity of contacts ontouch screen112 and/or one or moretactile output generators167 for generating tactile outputs for a user ofdevice100.
• FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.Device300 need not be portable. In some embodiments,device300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or industrial controller).Device300 typically includes one or more processing units (CPU's)310, one or more network orother communications interfaces360,memory370, and one ormore communication buses320 for interconnecting these components.Communication buses320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components.Device300 includes input/output (I/O)interface330 comprisingdisplay340, which is typically a touch screen display (e.g., touch screen display112). I/O interface330 also optionally includes a keyboard and/or mouse (or other pointing device)350 andtouchpad355,tactile output generator357 for generating tactile outputs on device300 (e.g., similar to tactile output generator(s)167 described above with reference toFIG. 1A), sensors359 (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s)165 described above with reference toFIG. 1A).Memory370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices.Memory370 optionally includes one or more storage devices remotely located from CPU(s)310. In some embodiments,memory370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored inmemory102 of portable multifunction device100 (FIG. 1A), or a subset thereof. Furthermore,memory370 optionally stores additional programs, modules, and data structures not present inmemory102 of portablemultifunction device100. For example,memory370 ofdevice300 optionallystores drawing module380,presentation module382,word processing module384,website creation module386,disk authoring module388, and/orspreadsheet module390, whilememory102 of portable multifunction device100 (FIG. 1A) optionally does not store these modules.
• Each of the above identified elements inFIG. 3 is, optionally, stored in one or more of the previously mentioned memory devices. Each of the above identified modules corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments,memory370 optionally stores a subset of the modules and data structures identified above. Furthermore,memory370 optionally stores additional modules and data structures not described above.
• Attention is now directed towards embodiments of user interfaces (“UI”) that is, optionally, implemented onportable multifunction device100.
• FIG. 4A illustrates an exemplary user interface for a menu of applications onportable multifunction device100 in accordance with some embodiments. Similar user interfaces are, optionally, implemented ondevice300. In some embodiments,user interface400 includes the following elements, or a subset or superset thereof:
• • Signal strength indicator(s)402 for wireless communication(s), such as cellular and Wi-Fi signals;
  • Time404;
  • Bluetooth indicator405;
  • Battery status indicator406;
  • Tray408 with icons for frequently used applications, such as:
    • Icon416 fortelephone module138, labeled “Phone,” which optionally includes anindicator414 of the number of missed calls or voicemail messages;
    • Icon418 fore-mail client module140, labeled “Mail,” which optionally includes anindicator410 of the number of unread e-mails;
    • Icon420 forbrowser module147, labeled “Browser;” and
    • Icon422 for video andmusic player module152, also referred to as iPod (trademark of Apple Inc.)module152, labeled “iPod;” and
  • Icons for other applications, such as:
    • Icon424 forIM module141, labeled “Text;”
    • Icon426 forcalendar module148, labeled “Calendar;”
    • Icon428 forimage management module144, labeled “Photos;”
    • Icon430 forcamera module143, labeled “Camera;”
    • Icon432 formusic library module155, labeled “Music Library”
    • Icon434 for stocks widget149-2, labeled “Stocks;”
    • Icon436 formap module154, labeled “Map;”
    • Icon438 for weather widget149-1, labeled “Weather;”
    • Icon440 for alarm clock widget149-4, labeled “Clock;”
    • Icon442 forInternet radio module142, labeled “Internet Radio;”
    • Icon444 fornotes module153, labeled “Notes;” and
    • Icon446 for a settings application or module, which provides access to settings fordevice100 and itsvarious applications136.
• It should be noted that the icon labels illustrated inFIG. 4A are merely exemplary. For example,icon422 for video andmusic player module152 are labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.
• FIG. 4B illustrates an exemplary user interface on a device (e.g.,device300,FIG. 3) with a touch-sensitive surface451 (e.g., a tablet ortouchpad355,FIG. 3) that is separate from the display450 (e.g., touch screen display112).Device300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors357) for detecting intensity of contacts on touch-sensitive surface451 and/or one or moretactile output generators359 for generating tactile outputs for a user ofdevice300.
• Although some of the examples which follow will be given with reference to inputs on touch screen display112 (where the touch sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown inFIG. 4B. In some embodiments the touch sensitive surface (e.g.,451 inFIG. 4B) has a primary axis (e.g.,452 inFIG. 4B) that corresponds to a primary axis (e.g.,453 inFIG. 4B) on the display (e.g.,450). In accordance with these embodiments, the device detects contacts (e.g.,460 and462 inFIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display (e.g., inFIG. 4B,460 corresponds to468 and462 corresponds to470). In this way, user inputs (e.g.,contacts460 and462, and movements thereof) detected by the device on the touch-sensitive surface (e.g.,451 inFIG. 4B) are used by the device to manipulate the user interface on the display (e.g.,450 inFIG. 4B) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein.
• Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
• FIG. 5 illustrates a block diagram of an operatingenvironment500 in accordance with some embodiments.Operating environment500 includesserver510, one ormore communications networks505,portable multifunction device100, and externalinformation presentation system540. In some embodiments, externalinformation presentation system540 is implemented in a vehicle.
• Server510 typically includes one or more processing units (CPUs)512 for executing modules, programs and/or instructions stored inmemory524 and thereby performing processing operations, one or more network orother communications interfaces520,memory524, and one ormore communication buses522 for interconnecting these components.Communication buses522 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components.Memory524 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices.Memory524 optionally includes one or more storage devices remotely located from the CPU(s)512.Memory524, or alternately the non-volatile memory device(s) withinmemory524, comprises a non-transitory computer readable storage medium. In some embodiments,memory524, or the computer readable storage medium ofmemory524 stores the following programs, modules, and data structures, or a subset thereof:
• • anoperating system526 that includes procedures for handling various basic system services and for performing hardware dependent tasks; and
  • anetwork communication module528 that is used for connecting (wired or wireless)server510 to other computing devices via the one or more communication network interfaces520 and one ormore communication networks505, such as the Internet, other wide area networks, local area networks, metropolitan area networks, and so on.
• Portablemultifunction device100 typically includes the components described with reference toFIGS. 1A-1B and/or3.
• Externalinformation presentation system540 typically includes one or more processing units (CPUs)542 for executing modules, programs and/or instructions stored inmemory554 and thereby performing processing operations, one or more network orother communications interfaces550,memory554, and one ormore communication buses552 for interconnecting these components. Externalinformation presentation system540 optionally includes auser interface546 comprising adisplay device547 and controls548 (e.g., mechanical affordances, buttons or knobs, a touch-sensitive surface such as a touchscreen display, or other input sources). In some embodiments,display547 is a touch screen display that is capable of receiving user touch inputs.Communication buses552 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components.Memory554 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices.Memory554 optionally includes one or more storage devices remotely located from the CPU(s)542.Memory552, or alternately the non-volatile memory device(s) withinmemory552, comprises a non-transitory computer readable storage medium. In some embodiments,memory552, or the computer readable storage medium ofmemory552 stores the following programs, modules, and data structures, or a subset thereof:
• • anoperating system556 that includes procedures for handling various basic system services and for performing hardware dependent tasks; and
  • a network communication module558 that is used for connecting (wired or wireless)server540 to other computing devices via the one or more communication network interfaces550 and one ormore communication networks505, such as the Internet, other wide area networks, local area networks, metropolitan area networks, and so on.
• In some embodiments,device100 drives display547 ofsystem540. For example,device100 sends a video signal tosystem540, andCPU542 ofsystem540 renders the video signal ondisplay547. In some embodiments,device100 sends a video signal directly to display547 andCPU542 is not used to render the video signal (e.g.,device100 usesdisplay547 as an auxiliary display). In some embodiments, the user interface displayed ontouch screen112 ofdevice100 is synchronized with the user interface displayed ondisplay547 ofsystem540, and, in some other embodiments, the user interface displayed ontouch screen112 ofdevice100 is not synchronized with the user interface displayed ondisplay547 ofsystem540. In some embodiments,system540 sends information corresponding to a user input (e.g., a user touch input ondisplay547 or a user input via controls548) todevice100, anddevice100 updates the user interface displayed ontouch screen112 ofdevice100 in accordance with the received information.
User Interfaces and Associated Processes
• Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device with a display and a touch-sensitive surface, such asdevice300 or portablemultifunction device100.
• FIGS. 6A-6C illustrate exemplary user interfaces generated from a template for use with third-party applications, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes inFIGS. 7A-7I.
• FIG. 6A illustrates user-interface template601 displayed on adisplay547 of externalinformation presentation system540. In some embodiments,system540 is included in a vehicle (e.g., in the dashboard or steering wheel of the vehicle). In some embodiments,display547 is a touch screen display configured to receive user touch input.FIG. 6A further illustrates a plurality of user interface objects (sometimes herein called “affordances” or “selectable user interface objects”) includingapplication title bar602, defaultmain menu604,custom menu608, content selections view606,active item bar610, andexit button612. In some embodiments, the user-interface template contains fewer affordances than shown intemplate601, to further simplify the user interface and prevent driver distraction.
• FIG. 6B illustrates an example of a user interface generated from user-interface template601 (e.g., for use with an internet radio application).FIG. 6B illustratesapplication title bar602 displaying the title of the current application (e.g., Internet Radio App),main menu604 with default controls (e.g., up, down, search, sort, etc.), custom menu608 (e.g., Favorites menu) with application-specific controls (e.g., filter favorites, add current to favorites that correspond to application-specific functions), andexit button612.FIG. 6B further illustrates content selections view606 (e.g., station selections) displaying selection options for the current application (e.g.,smooth jazz station103,Korean pop station105, etc.) andactive item bar610 displaying information regarding the currently active item (e.g., hard rock station101).
• FIG. 6C illustrates an example of a user interface generated from user-interface template601 (e.g., for use with a music library application) that is different from the user interface generated fromtemplate601 that is shown inFIG. 6B.FIG. 6C illustratesapplication title bar602 displaying the title of the current application (e.g., Music Library App),main menu604 with default controls (e.g., up, down, search, sort, etc.), custom menu608 (e.g., User Playlists menu) with application-specific controls (e.g.,playlist 1,playlist 2, etc.), andexit button612.FIG. 6C further illustrates content selections view606 (e.g., song library) displaying selection options for the current application (e.g., storedsong103, storedsong105, etc.) andactive item bar610 displaying information regarding the currently active item (e.g., stored song101).
• As shown inFIGS. 6B-6C, a common template (e.g., thetemplate601 shown inFIG. 6A) is, optionally, used to generate different user interfaces for different third-party applications (e.g., the user interface for the internet radio application shown inFIG. 6B is different from the user interface for the music library application shown inFIG. 6C) by inserting information retrieved from the different third-party applications into user-interface template601. The different user interfaces shown inFIGS. 6B and 6C, however, share similarities that make them easier to use (e.g., affordances for selecting playable content are displayed in content selections view606 in both of the user interfaces inFIGS. 6B and 6C and information about the currently playing media is displayed in theactive item bar610 in both of the user interfaces inFIGS. 6B and 6C). Additionally, the template optionally enforces a minimum text size to ensure that text displayed in the user interfaces inFIGS. 6B and 6C is easy to read.
• FIGS. 7A-7I are flow diagrams illustrating amethod700 of providing user interfaces for third-party applications in accordance with some embodiments. Themethod700 is performed at an electronic device (e.g.,device300,FIG. 3, or portablemultifunction device100,FIG. 1A). In some embodiments, the electronic device includes a display and a touch-sensitive surface. In some embodiments, the display is a touch screen display and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations inmethod700 are, optionally, combined and/or the order of some operations is, optionally, changed.
• As described below, themethod700 provides user interfaces for third-party applications that reduce the cognitive burden on a user when interacting with third party applications, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to interact with the user interfaces faster and more efficiently conserves power and increases the time between battery charges.
• The device receives (702) a first display request to display a user interface of a first third-party application on a respective display that is in communication (e.g., via a wired or wireless connection) with the electronic device. For example, the device receives an input that corresponds to activation of an application launch icon for the first third-party application from a control associated with the respective display or a control associated with the electronic device (e.g., a tap gesture on Internet radio icon442 (FIG. 4A) for Internet radio application142 (FIG. 1A or3), or a tap gesture on Music Library icon432 (FIG. 4A) for Music Library application155 (FIG. 1A or3). In some embodiments, the respective display is a display of the device (e.g.,touchscreen112 of portable multifunction device100). In some embodiments, the respective display is a display that is separate from the device (e.g., display547 of externalinformation presentation system540 inFIG. 5).
• In response to receiving the first display request (704), the device obtains (706) a first user-interface template that is configured (or designed) to be used by a plurality of third-party applications; and the device requests (710), from the first third-party application, one or more values for populating the first user-interface template. In some embodiments, the first user-interface template is a generic or application-agnostic (or independent) user-interface template that is used by a plurality of different applications. For example, in some embodiments, the device obtains user-interface template601 shown inFIG. 6A.
• In some embodiments, the respective display is (708) a display in a vehicle information display system that is visible from a driver seat of a vehicle; and the first user-interface template is one of a plurality of predetermined user-interface templates that are configured to be used to generate user interfaces for the third-party application on the respective display that prevents distraction of the driver (e.g., the plurality of predetermined templates have large font and a few easily selectable options that can be operated by a driver without distracting the driver from driving safely). Thus, in some embodiments, using these predetermined user-interface templates enables the device to provide the user with access to the functionality of one or more third party applications while maintaining some control over the appearance of the user interface that is displayed on the respective display, so as to ensure that the user interface on the respective display is simple and intuitive to use.
• In some embodiments, values at the first third-party application are arranged (711) in a tree structure that includes a plurality of nodes that have predetermined properties and a tree relationship (e.g., a parent relationship or a child relationship) with one or more other nodes in the tree structure. In some embodiments, the request for one or more values for populating the first user-interface template includes one or more of: a request to return values that correspond to a list of child nodes of a respective node of the plurality of nodes (e.g., for a node that corresponds to an artist, the child nodes correspond to songs by the artist or albums by the artist); a request to return values that correspond to a list of properties of a respective node of the plurality of nodes; a request to provide content that is represented by the respective node (e.g., a request to provide audio content that corresponds to an audio file, an audio stream, a video file, a video stream and/or a playlist or radio station that corresponds to a plurality of distinct units of content); a request to provide a list of nodes that match a search query (e.g., a request to provide a list of artists, albums, songs, radio stations, audio books, podcasts or the like that match a set of one or more search terms and, optionally, logical operators connecting the search terms); and a request to provide a list of actions specific to the first third-party application that can be taken while providing access to content associated with the first third-party application (e.g., “like” “skip” “add to favorites” “flag” or other application-specific operations). In some embodiments, the properties of a respective node include one or more of: artwork for the respective node, an identifier for the respective node, a duration of media content associated with the respective node, a title of the respective node (a title of a currently playing track or radio station), a subtitle of the respective node (e.g., an artist of a currently playing song or a track of a currently playing radio station), a playable flag indicating whether or not the respective node is playable, a played flag indicating whether or not the respective node has already been played, and/or a container flag indicating whether or not the respective node is a container that has child nodes.
• The device receives (712), from the first third-party application, while the first third-party application is running on the electronic device, a first set of values for populating the first user-interface template (e.g., receiving a list of names of internet streaming radio stations). For example,FIG. 6B shows user-interface template601 populated with data from an application titled “Internet Radio App.”
• In some embodiments, one or more of the values in the first set of values are retrieved (713) from a remote source (e.g., a server in communication with the first third-party application such as sever510 inFIG. 5) by the first third-party application in response to the request for one or more values for populating the first user-interface template. For example, when a streaming internet radio station has been selected for playing, the first third-party application initiates sending to a remote server a request to start streaming the streaming internet radio station and requests a name of a song and artist and corresponding album artwork for a song to be played on the streaming internet radio station. The first third-party application receives these values and transmits these values to an intermediary process for incorporation into a “now playing” user interface template that the intermediary process will transmit to the respective display.
• In some embodiments, the device includes (714) a digital personal assistant process with voice recognition capabilities (e.g., a digitalpersonal assistant150 that records voice commands and sends information representative of the recorded voice commands to a server such asserver510 inFIG. 5 for analysis, and responds to the voice commands based on a response from the server). In some embodiments, the device determines (715) the capabilities of the first third-party application based on responses from the first third-party application to a plurality of requests to the third-party application for values associated with populating user-interface templates for user interfaces for the respective display (e.g., the digital personal assistant process traverses a tree structure of metadata for the first third-party application and maps out the various options and metadata that are accessible via the first third-party application). In some embodiments, the device generates (716) an index of the capabilities of the first third-party application (e.g., based on the map of the various options and metadata that are accessible via the first third-party application). In some embodiments, the device provides (718) voice access to the capabilities of the first third-party application via the digital personal assistant process (e.g., enabling a user to use voice commands to request display of a list of the songs by a particular artist, display of a list of internet streaming radio stations that are available for playing, playback of a particular song by a particular artist, or searching through a media presentation application for media that matches a verbally stated search query). For example, for a streaming internet radio application, the personal assistant would traverse and index the tree structure of the metadata for available streaming internet radio stations and other operations that can be performed by the streaming internet radio application. Then, the user is enabled to provide verbal commands to the digital personal assistant to start playing a radio station, stop playing a radio station, create a new radio station based on a current song, skip a song or other operation using voice commands directed to the digital personal assistant (e.g., “Assistant, please play Artist X radio station,” “Assistant, please skip this song,” “Assistant please list all radio stations created in the last week,” or “Assistant, please mark this song as a favorite.”)
• In some embodiments, the device detects (720) that a predetermined condition has been met. In response to detecting that the predetermined condition has been met, the device re-determines (721) the capabilities of the first third-party application and re-generates the index of the capabilities of the first third-party application (e.g., the various options that are accessible via the first third-party application are re-indexed: when the device is placed in communication with the respective display (such asdisplay547 of external information presentation system540 (FIG.5)), when the device is connected to a vehicle information display system that includes the respective display, and/or when the first third-party application is launched). For example, for a streaming internet radio application, the availability of streaming internet radio stations is, optionally, determined based on the availability of an internet connection for receiving the streaming internet radio station; similarly, if the user creates/subscribes to a new radio station or deletes/unsubscribes to an old radio station, the metadata associated with the streaming internet radio application changes (e.g., which radio stations are nodes in the tree structure and/or which radio stations are playable). In order to address the changing metadata at the streaming internet radio application, the device periodically re-indexes the metadata at the streaming internet radio application (e.g., when the streaming internet radio application is launched or when the device is connected to a vehicle information display system). In some embodiments, the third-party application proactively informs the digital personal assistant that some portion of the metadata has been changed or updated and prompts the digital personal assistant to re-index that portion (or all) of the metadata of the third-party application. The digital personal assistant re-indexes that portion (or all) of the metadata of the third-party application in response to receiving the information that the portion of the metadata has been changed or the next time that the third-party application is launched.
• The device populates (722) the first user-interface template with the first set of values received from the first third-party application. For example, in accordance with these embodiments,FIG. 6B shows user-interface template601 populated with data from a third-party application titled “Internet Radio App” (e.g., station selections, favorites, current station, etc.) to generate the user interface for the third-party application that is displayed onDisplay547 inFIG. 6C.
• In some embodiments, the first user-interface template is used by a plurality of different third-party applications including (724) the first third-party application and a second third-party application. In some embodiments, populating the first user-interface template with values received from a respective third-party application includes inserting values identified by the respective third-party application as belonging to a first class of values in a predefined region at a predefined font size in a user interface that is provided to the respective display. For the first user-interface template, the first third-party application identifies a first type of information as the first class of values, and the second third-party application identifies a second type of information, different from the first type of information, as the first class of values. For example,FIG. 6B shows user-interface template601 populated with values related to internet radio stations andFIG. 6C shows user-interface template601 populated with values related to stored songs. In accordance with these embodiments,FIGS. 6B and 6C show user-interface templates with the same font sizes.
• In some embodiments, for the first user-interface template: the first third-party application identifies (726) the names of remotely-generated content stations (e.g., streaming internet radio stations) as the first class of values; and the second third-party application identifies the names of predetermined playlists as the first class of values. In some embodiments, a predetermined playlist is different from a streaming internet radio station because a predetermined playlist has a set length and the contents of the playlist are set at the time that the user selects the playlist for playing, whereas a streaming internet radio station is a continuous stream of music of indeterminate length that continues for as long as the user is listening and includes content selected remotely (e.g., automatically by a computer in accordance with music-selection algorithms or manually by a disc jockey, radio host or other person independent of actions by a user of the device). For example inFIGS. 6B-6C, the device identifies the names of streaming internet radio stations as the first class of values (e.g., descriptions of playable media content items) for the Internet radio application (e.g.,142,FIG. 1A) inFIG. 6B and the device identifies the names of songs as the first class of values for the music library application (e.g.,155,FIG. 1A) inFIG. 6C.
• In some embodiments, for the first user-interface template: the first third-party application identifies (728) the names of content that can be streamed to the device (e.g., on-demand streaming of music or other media content over a distributed data network such as the Internet) as the first class of values; and the second third-party application identifies the names of content stored on the device (e.g., language learning programs, audio books, music, podcasts or the like) as the first class of values.
• The device generates (730) a first user interface for the first third-party application using the first user-interface template populated with the first set of values. For example,FIG. 6B illustrates a user interface generated from user-interface template601 and values received from an internet radio application. In accordance with this example,FIG. 6B shows defaultmain menu604 including an info button (e.g., to return values that correspond to a list of properties of a respective node), an activate button (e.g., to provide content that is represented by the respective node), a search button (e.g., to provide a list of nodes that match a search query), andcustom menu608 with custom buttons (e.g., to provide a list of actions specific to the first third-party application that can be taken while providing access to content associated with the first third-party application).
• In some embodiments, the device includes (732) a plurality of processes including a first third-party application process for running the first third-party application and a set of one or more intermediation processes (e.g., an application for integrating third-party applications with a vehicle information display system such as a navigation or entertainment system or other external information display system, like externalinformation presentation system540 inFIG. 5) for relaying information between the respective display and the first-third party application process. In some embodiments, the request of the one or more values for populating the first user-interface template is generated by an intermediation process from the set of one or more intermediation processes; and the first user interface is generated by an intermediation process from the set of one or more intermediation processes. For example, a smart phone (e.g.,portable multifunction device100 inFIG. 5) has a vehicle integration application151 (e.g., an application including one or more intermediation processes) that controls a vehicle information display system in the vehicle (e.g., a car, a truck, a van, etc.) that provides a user interface on a respective display of the vehicle information display system (e.g., display547 of externalinformation presentation system540 inFIG. 5), such as for a mapping application or a music application. The smart phone also has one or more third-party applications such as a separate podcasting application or a streaming internet radio application and the vehicle integration application converts information from the third-party applications into content for display by the vehicle integration application on the respective display of the vehicle information display system.
• In some embodiments, the first third-party application is (734) a media presentation application (e.g.,Internet radio142,FIG. 1A). In some embodiments, the device includes a first-party application that is a media presentation application (e.g., video &music player module152,FIG. 1A); the first party application includes a first-party user interface that has a plurality of selectable affordances for requesting performance of media presentation operations and one or more content presentation regions (e.g., a region for displaying a list of available media) at respective locations in the first-party user interface; and generating the first user interface for the first third-party application includes generating a user interface that includes selectable affordances and one or more content presentation regions that correspond in function and location to the selectable affordances and content presentation regions of the first-party user interface. Thus, in some embodiments, the first user-interface template is a template that conforms information from third-party applications into a standardized user interface that has similar controls, content regions, and appearance to a first-party media presentation application so as to provide a consistent user interface that is familiar to the user and thus prevents driver distraction when displayed on a vehicle information display system that is visible from a driver seat of a vehicle.
• The device sends (736), or otherwise provides, information to the respective display that enables the first user interface for the first third-party application to be displayed on the respective display (e.g.,portable multifunction device100 provides the information to display547 of externalinformation presentation system540 inFIG. 5).
• In some embodiments, while the first user-interface for the first third-party application is displayed on the respective display, the device receives (738), from an input device for the respective display (e.g., a touch-sensitive surface that is co-incident with the respective display or a button or knob that is used for controlling the respective display) a respective input that corresponds to selection of an option in the first user interface (e.g., the selected option is an option to play, pause, seek, display a new menu or perform a third-party application specific operation such as “liking,” “skipping” or “add to favorites”). In response to receiving the respective input, the device provides (740) information to the first third-party application running on the electronic device that enables the first third-party application to respond to selection of the option in the first user interface. In some embodiments, the device receives (742), from the first third-party application, the response to selection of the option from the first third-party application; and sends (744), or otherwise provides, information to the respective display that enables the response to selection of the option to be provided (e.g., displayed) to the user. For example, the user is presented with a list of names of streaming internet radio stations on the respective display, the user taps on a name of a respective streaming internet radio station (e.g., on a touchscreen display of externalinformation presentation system540 inFIG. 5), an intermediation process at the device (e.g.,portable multifunction device100 inFIG. 5) provides the first third-party application with information indicating that the respective streaming internet radio station has been selected, the first third-party application requests that a server (e.g.,server510 inFIG. 5) provide artwork, a title, subtitle and audio stream for the respective streaming internet radio station and then provides this information to the intermediation process (e.g., at portablemultifunction device100 inFIG. 5) which generates a user interface based on the information and a user interface template and transmits the generated user interface to the respective display for display (e.g., ondisplay547 of externalinformation presentation system540 inFIG. 5).
• In some embodiments, a first-party intermediation process at the device intermediates communication between the respective display and a first third-party application by converting data from the first third-party application into a standardized, simplified, user interface that prevents distracted driving and by relaying inputs that correspond to user interaction with the user interface displayed on the respective display so that the first third-party application can respond to the inputs, even when the first third-party application is not provided with information indicative of a size, resolution and other characteristics of the respective display and does not have direct access to user interactions with the user interface displayed on the respective display. For example, the third-party application is not provided with times and locations of touch inputs but rather gets information about what information was requested by the user as filtered through the first-party intermediation process.
• In some embodiments, while the first user interface for the first third-party application is displayed on the respective display (746), the device receives (748) information indicative of a selection of a respective option in the first user interface (e.g., selection of a container or a node with child nodes, such as an “artist” folder that includes songs by the selected artist or selection of a particular internet streaming radio station of a plurality of internet streaming radio stations). In some embodiments, in response to receiving the information indicative of the selection of the respective option in the first user interface (750): the device obtains (752) a second user-interface template, different from the first user-interface template (e.g., a template for displaying the contents of a container, such as a playlist template or a “now playing” user interface template); and requests (754), from the first third-party application, one or more values for populating the second user-interface template. In some embodiments, the device receives (756), from the first third-party application, while the first third-party application is running on the electronic device, a second set of values for populating the second user-interface template (e.g., names and playtime information for the songs by the selected artist for a playlist template or a name of a currently playing radio station, a name of a currently playing song, artwork for the currently playing song for a “now playing” template); populates (758) the second user-interface template with the second set of values received from the first third-party application; generates (760) a second user interface for the first third-party application by using the second user-interface template populated with the second set of values (e.g., inserting the names and playtime information for the songs by the selected artist into the playlist template or inserting a name of a currently playing radio station, a name of a currently playing song, and artwork for the currently playing song into a “now playing” template that includes controls for controlling pausing/starting/stopping/fast forwarding/rewinding the currently playing song); and sends (762), or otherwise provides, information to the respective display that enables the second user interface for the first third-party application to be displayed on the respective display.
• In some embodiments, after sending the information to the respective display that enables the first user interface for the first third-party application to be displayed on the respective display (764), the device receives (766) a second display request to display a user interface for a second third-party application, different from the first third-party application, on the respective display (e.g., receiving activation of an application launch icon for the second third-party application using a control associated with the respective display or a control associated with the electronic device). For example, while the user was initially playing audio from an Internet streaming radio application142 (e.g., using the user interface for the streaming internet radio application shown inFIG. 6B), the user switches to playing audio from a separate podcast application or an audio book application. In some embodiments, in response to receiving the second display request, the device requests (768), from the second third-party application, one or more values for populating the first user-interface template; receives (770), from the second third-party application, while the second third-party application is running on the electronic device, a third set of values for populating the first user-interface template; populates (772) the first user-interface template with the third set of values received from the second third-party application; generates (774) a second user interface for the second third-party application using the first user-interface template populated with the third set of values; and sends (776) (or otherwise provides) information to the respective display that enables the second user interface for the second third-party application to be displayed on the respective display (e.g., the user interface for themusic library application155 shown inFIG. 6C). Thus, in some embodiments, the device repeats the process of requesting values from a third party application to fill out the first user-interface template when a different third party application is requested that uses the same first user-interface template. This process is repeated in this situation because the first user-interface template is designed or configured to be used by a plurality of different third-party applications.
• In some embodiments, after sending the information to the respective display that enables the first user interface for the first third-party application to be displayed on the respective display (764): the device receives (778), from the first third-party application, an updated first set of values for populating the first user-interface template. In some embodiments, in response to receiving the updated first set of values for populating the first user-interface template (780), the device populates (782) the first user-interface template with the updated first set of values received from the first third-party application; generates (784) an updated first user interface for the first third-party application using the first user-interface template populated with the updated first set of values; and provides (786) information to the respective display that enables the updated first user interface for the first third-party application to be displayed on the respective display. In some embodiments, the updated first set of values is generated based on events that occur at the first third-party application (e.g., the update to the user interface for the first third-party application is initiated by the first third-party application rather than being initiated by an intermediation process). For example, the third-party application is a streaming media application and the data connection of the device ceases to function. In response to detecting that the data connection has ceased to function, the third-party application transmits information to an intermediation process at the device indicating that streaming content that was previously marked as “playable” (e.g., when there was a working data connection) has changed in status so that it is “not playable” (e.g., because the data connection is no longer available). In some embodiments, when content changes from being “playable” to “not playable,” the first user interface for the first third-party application is updated to indicate that the content is “not playable” (e.g., by removing the content from a list of playable content or changing an appearance of a representation of the content to indicate that the content is not currently playable by reducing a contrast of the representation or displaying a “not playable” icon or symbol next to the representation of the content). For example, inFIG. 6B, if the device were to cease to have access to the streaming internet radio stations shown in content selections view606, the device would regenerate the user interface shown inFIG. 6B to reflect the unavailability of the streaming internet radio stations (e.g., by displaying a not-playable icon adjacent to the names of the unavailable stations, by reducing the contrast of (“graying out”) the unavailable stations or by removing the stations from the content selections view606).
• It should be understood that the particular order in which the operations inFIGS. 7A-7I have been described is merely an example and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein.
• In accordance with some embodiments,FIG. 8 shows a functional block diagram of a firstelectronic device800 configured in accordance with the principles of the various described embodiments. The functional blocks of the device are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described embodiments. It is understood by persons of skill in the art that the functional blocks described inFIG. 8 are, optionally, combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.
• As shown inFIG. 8,electronic device800 includes memory coupled toprocessing unit802. In some embodiments,electronic device800 also includescommunications interface unit804 coupled toprocessing unit802 and configured to communicate withrespective display unit806. In some embodiments, processingunit802 includes receivingunit807, obtainingunit808, requestingunit810, populatingunit812,interface generating unit814, sendingunit816, information providing unit818, determiningunit820,index generating unit822,voice providing unit824, detectingunit826, and digitalassistant unit828.Processing unit802 is configured to receive (e.g., with receivingunit807 via communications interface unit804) a first display request to display a user interface of a first third-party application on a respective display unit (e.g., with respective display unit806) that is in communication withelectronic device800.Processing unit802 is further configured to, in response to receiving the first display request: obtain (e.g., with obtaining unit808) a first user-interface template that is configured to be used by a plurality of third-party applications; and request (e.g., with requesting unit810), from the first third-party application, one or more values for populating the first user-interface template.Processing unit802 is further configured to receive (e.g., with receivingunit807 or communications interface unit804), from the first third-party application, while the first third-party application is running on the electronic device, a first set of values for populating the first user-interface template; populate (e.g., with populating unit812) the first user-interface template with the first set of values received from the first third-party application; generate (e.g., with interface generating unit814) a first user interface for the first third-party application using the first user-interface template populated with the first set of values; and send (e.g., with sending unit816) information to the respective display unit that enables the first user interface for the first third-party application to be displayed on the respective display unit (e.g., respective display unit806).
• In some embodiments, processingunit802 is further configured to: while the first user-interface for the first third-party application is displayed on the respective display unit (e.g., respective display unit806), receive (e.g., with receivingunit807 via communications interface unit804), from an input device for the respective display unit a respective input that corresponds to selection of an option in the first user interface; and, in response to receiving the respective input, provide (e.g., with information providing unit818) information to the first third-party application running on the electronic device that enables the first third-party application to respond to selection of the option in the first user interface. In some embodiments, processingunit802 is further configured to receive (e.g., with receivingunit807 via communications interface unit804), from the first third-party application, the response to selection of the option from the first third-party application; and send (e.g., with sending unit816) information to the respective display unit that enables the response to selection of the option to be provided to the user.
• In some embodiments, processingunit802 is further configured to, while the first user interface for the first third-party application is displayed on the respective display unit (e.g., respective display unit806): receive (e.g., with receivingunit807 via communications interface unit804) information indicative of a selection of a respective option in the first user interface; and, in response to receiving the information indicative of the selection of the respective option in the first user interface: obtain (e.g., with obtaining unit808) a second user-interface template, different from the first user-interface template; and request (e.g., with requesting unit810), from the first third-party application, one or more values for populating the second user-interface template. In some embodiments, processingunit802 is further configured to receive (e.g., with receivingunit807 via communications interface unit804), from the first third-party application, while the first third-party application is running on the electronic device, a second set of values for populating the second user-interface template; populate (e.g., with populating unit812) the second user-interface template with the second set of values received from the first third-party application; generate (e.g., with interface generating unit814) a second user interface for the first third-party application by using the second user-interface template populated with the second set of values; and send (e.g., with sending unit816) information to the respective display unit that enables the second user interface for the first third-party application to be displayed on the respective display unit (e.g., respective display unit806).
• In some embodiments, processingunit802 is further configured to, after sending (e.g., with sending unit816) the information to the respective display unit that enables the first user interface for the first third-party application to be displayed on the respective display unit (e.g., respective display unit806) receive (e.g., with receivingunit807 or communications interface unit804) a second display request to display a user interface for a second third-party application, different from the first third-party application, on the respective display unit (e.g., respective display unit806). In some embodiments, processingunit802 is further configured to, in response to receiving the second display request, request (e.g., with requesting unit810), from the second third-party application, one or more values for populating the first user-interface template; receive (e.g., with receivingunit807 via communications interface unit804), from the second third-party application, while the second third-party application is running on the electronic device, a third set of values for populating the first user-interface template; populate (e.g., with populating unit812) the first user-interface template with the third set of values received from the second third-party application; generate (e.g., with interface generating unit814) a second user interface for the second third-party application using the first user-interface template populated with the third set of values; and send (e.g., with sending unit816) information to the respective display unit that enables the second user interface for the second third-party application to be displayed on the respective display unit (e.g., respective display unit806).
• In some embodiments, the device includes a plurality of processes including a first third-party application process for running the first third-party application and a set of one or more intermediation processes for relaying information between the respective display unit and the first-third party application process; the request of the one or more values for populating the first user-interface template is generated by an intermediation process from the set of one or more intermediation processes; and the first user interface is generated by an intermediation process from the set of one or more intermediation processes.
• In some embodiments, one or more of the values in the first set of values are retrieved from a remote source by the first third-party application in response to the request for one or more values for populating the first user-interface template.
• In some embodiments, the respective display unit (e.g., respective display unit806) is a display unit in a vehicle information display system that is visible from a driver seat of a vehicle; and the first user-interface template is one of a plurality of predetermined user-interface templates that are configured to be used to generate user interfaces for the third-party application on the respective display unit that prevents distraction of the driver.
• In some embodiments, the first user-interface template is used by a plurality of different third-party applications including the first third-party application and a second third-party application; populating (e.g., with populating unit812) the first user-interface template with values received from a respective third-party application includes inserting values identified by the respective third-party application as belonging to a first class of values in a predefined region at a predefined font size in a user interface that is provided to the respective display unit; and, for the first user-interface template: the first third-party application identifies a first type of information as the first class of values; and the second third-party application identifies a second type of information, different from the first type of information, as the first class of values.
• In some embodiments, for the first user-interface template: the first third-party application identifies the names of remotely-generated content stations as the first class of values; and the second third-party application identifies the names of predetermined playlists as the first class of values.
• In some embodiments, for the first user-interface template: the first third-party application identifies the names of content that can be streamed to the device as the first class of values; and the second third-party application identifies the names of content stored on the device as the first class of values.
• In some embodiments, values at the first third-party application are arranged in a tree structure that includes a plurality of nodes that have predetermined properties and a tree relationship with one or more other nodes in the tree structure; and the request (e.g., with requesting unit810) for one or more values for populating the first user-interface template includes one or more of: a request to return values that correspond to a list of child nodes of a respective node of the plurality of nodes; a request to return values that correspond to a list of properties of a respective node of the plurality of nodes; a request to provide content that is represented by the respective node; a request to provide a list of nodes that match a search query; and a request to provide a list of actions specific to the first third-party application that can be taken while providing access to content associated with the first third-party application.
• In some embodiments, the first third-party application is a media presentation application. In some embodiments,device800 includes a first-party application that is a media presentation application; the first party application includes a first-party user interface that has a plurality of selectable affordances for requesting performance of media presentation operations and one or more content presentation regions at respective locations in the first-party user interface; and generating (e.g., with interface generating unit814) the first user interface for the first third-party application includes generating a user interface that includes selectable affordances and one or more content presentation regions that correspond in function and location to the selectable affordances and content presentation regions of the first-party user interface.
• In some embodiments, processingunit802 is further configured to, after sending the information to the respective display unit that enables the first user interface for the first third-party application to be displayed on the respective display unit (e.g., respective display unit806): receive (e.g., with receivingunit807 via communications interface unit804), from the first third-party application, an updated first set of values for populating the first user-interface template; and, in response to receiving the updated first set of values for populating the first user-interface template: populate (e.g., with populating unit812) the first user-interface template with the updated first set of values received from the first third-party application; generate (e.g., with interface generating unit814) an updated first user interface for the first third-party application using the first user-interface template populated with the updated first set of values; and provide (e.g., with information providing unit818) information to the respective display unit that enables the updated first user interface for the first third-party application to be displayed on the respective display unit.
• In some embodiments,device800 includes a digital personal assistant process (e.g., digital assistant unit828) with voice recognition capabilities. In some embodiments, processingunit802 is further configured to: determine (e.g., with determining unit820) the capabilities of the first third-party application based on responses from the first third-party application to a plurality of requests to the third-party application for values associated with populating user-interface templates for user interfaces for the respective display unit; generate (e.g., with index generating unit822) an index of the capabilities of the first third-party application; and provide (e.g., with voice providing unit824) voice access to the capabilities of the first third-party application via the digital personal assistant process (e.g., with digital assistant unit828).
• In some embodiments, processingunit802 is further configured to: detect (e.g., with detecting unit826) that a predetermined condition has been met; and, in response to detecting that the predetermined condition has been met: re-determine (e.g., with determining unit820) the capabilities of the first third-party application; and re-generate (e.g., with index generating unit822) the index of the capabilities of the first third-party application.
• The operations in the information processing methods described above are, optionally, implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect toFIGS. 1A and 3) or application specific chips.
• The operations described above with reference toFIGS. 7A-7I are, optionally, implemented by components depicted inFIGS. 1A-1B orFIG. 8. For example, receivingoperations702 and712, requestingoperation710, populatingoperation722, generatingoperation730, and sendingoperation736 are, optionally, implemented byevent sorter170,event recognizer180, andevent handler190. Event monitor171 inevent sorter170 detects a contact on touch-sensitive display112, andevent dispatcher module174 delivers the event information to application136-1. Arespective event recognizer180 of application136-1 compares the event information torespective event definitions186, and determines whether a first contact at a first location on the touch-sensitive surface (or whether orientation of the device) corresponds to a predefined event or sub-event, such as selection of an object on a user interface, or rotation of the device from one orientation to another. When a respective predefined event or sub-event is detected,event recognizer180 activates anevent handler190 associated with the detection of the event or sub-event.Event handler190 optionally uses or calls data updater176 or objectupdater177 to update the applicationinternal state192. In some embodiments,event handler190 accesses arespective GUI updater178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted inFIGS. 1A-1B.
• The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated.

Claims (20)

What is claimed is:

1. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device with one or more processors and memory, cause the device to perform:

receiving a first display request to display a user interface of a first third-party application on a respective display that is in communication with the electronic device;

in response to receiving the first display request:

obtaining a first user-interface template that is configured to be used by a plurality of third-party applications; and

requesting, from the first third-party application, one or more values for populating the first user-interface template;

receiving, from the first third-party application, while the first third-party application is running on the electronic device, a first set of values for populating the first user-interface template;

populating the first user-interface template with the first set of values received from the first third-party application;

generating a first user interface for the first third-party application using the first user-interface template populated with the first set of values; and

sending information to the respective display that enables the first user interface for the first third-party application to be displayed on the respective display.

2. The medium ofclaim 1, wherein the one or more programs further comprise instructions, which when executed by an electronic device with one or more processors and memory, cause the device to perform:

while the first user-interface for the first third-party application is displayed on the respective display, receiving, from an input device for the respective display a respective input that corresponds to selection of an option in the first user interface; and

in response to receiving the respective input, providing information to the first third-party application running on the electronic device that enables the first third-party application to respond to selection of the option in the first user interface;

receiving, from the first third-party application, the response to selection of the option from the first third-party application; and

sending information to the respective display that enables the response to selection of the option to be provided to the user.

3. The medium ofclaim 1, wherein the one or more programs further comprise instructions, which when executed by an electronic device with one or more processors and memory, cause the device to perform:

while the first user interface for the first third-party application is displayed on the respective display:

receiving information indicative of a selection of a respective option in the first user interface; and

in response to receiving the information indicative of the selection of the respective option in the first user interface:

obtaining a second user-interface template, different from the first user-interface template; and

requesting, from the first third-party application, one or more values for populating the second user-interface template;

receiving, from the first third-party application, while the first third-party application is running on the electronic device, a second set of values for populating the second user-interface template;

populating the second user-interface template with the second set of values received from the first third-party application;

generating a second user interface for the first third-party application by using the second user-interface template populated with the second set of values; and

sending information to the respective display that enables the second user interface for the first third-party application to be displayed on the respective display.

4. The medium ofclaim 1, wherein the one or more programs further comprise instructions, which when executed by an electronic device with one or more processors and memory, cause the device to perform:

after sending the information to the respective display that enables the first user interface for the first third-party application to be displayed on the respective display:

receiving a second display request to display a user interface for a second third-party application, different from the first third-party application, on the respective display;

in response to receiving the second display request, requesting, from the second third-party application, one or more values for populating the first user-interface template;

receiving, from the second third-party application, while the second third-party application is running on the electronic device, a third set of values for populating the first user-interface template;

populating the first user-interface template with the third set of values received from the second third-party application;

generating a second user interface for the second third-party application using the first user-interface template populated with the third set of values; and

sending information to the respective display that enables the second user interface for the second third-party application to be displayed on the respective display.

5. The medium ofclaim 1, wherein:

the device includes a plurality of processes including a first third-party application process for running the first third-party application and a set of one or more intermediation processes for relaying information between the respective display and the first-third party application process;

the request for the one or more values for populating the first user-interface template is generated by an intermediation process from the set of one or more intermediation processes; and

the first user interface is generated by an intermediation process from the set of one or more intermediation processes.

6. The medium ofclaim 1, wherein one or more of the values in the first set of values are retrieved from a remote source by the first third-party application in response to the request for one or more values for populating the first user-interface template.

7. The medium ofclaim 1, wherein:

the respective display is a display in a vehicle information display system that is visible from a driver seat of a vehicle; and

the first user-interface template is one of a plurality of predetermined user-interface templates that are configured to be used to generate user interfaces for the first third-party application on the respective display that prevents distraction of the driver.

8. The medium ofclaim 1, wherein:

the first user-interface template is used by a plurality of different third-party applications including the first third-party application and a second third-party application;

populating the first user-interface template with values received from a respective third-party application includes inserting values identified by the respective third-party application as belonging to a first class of values in a predefined region at a predefined font size in a user interface that is provided to the respective display; and

for the first user-interface template:

the first third-party application identifies a first type of information as the first class of values; and

the second third-party application identifies a second type of information, different from the first type of information, as the first class of values.

9. The medium ofclaim 8, wherein, for the first user-interface template:

the first third-party application identifies the names of remotely-generated content stations as the first class of values; and

the second third-party application identifies the names of predetermined playlists as the first class of values.

10. The medium ofclaim 8, wherein, for the first user-interface template:

the first third-party application identifies the names of content that can be streamed to the device as the first class of values; and

the second third-party application identifies the names of content stored on the device as the first class of values.

11. The medium ofclaim 1, wherein:

values at the first third-party application are arranged in a tree structure that includes a plurality of nodes that have predetermined properties and a tree relationship with one or more other nodes in the tree structure; and

the request for one or more values for populating the first user-interface template includes one or more of:

a request to return values that correspond to a list of child nodes of a respective node of the plurality of nodes;

a request to return values that correspond to a list of properties of a respective node of the plurality of nodes;

a request to provide content that is represented by the respective node;

a request to provide a list of nodes that match a search query; and

a request to provide a list of actions specific to the first third-party application that can be taken while providing access to content associated with the first third-party application.

12. The medium ofclaim 1, wherein:

the first third-party application is a media presentation application;

the device includes a first-party application that is a media presentation application; the first party application includes a first-party user interface that has a plurality of selectable affordances for requesting performance of media presentation operations and one or more content presentation regions at respective locations in the first-party user interface; and

generating the first user interface for the first third-party application includes generating a user interface that includes selectable affordances and one or more content presentation regions that correspond in function and location to the selectable affordances and content presentation regions of the first-party user interface.

13. The medium ofclaim 1, after sending the information to the respective display that enables the first user interface for the first third-party application to be displayed on the respective display:

receiving, from the first third-party application, an updated first set of values for populating the first user-interface template; and

in response to receiving the updated first set of values for populating the first user-interface template:

populating the first user-interface template with the updated first set of values received from the first third-party application;

generating an updated first user interface for the first third-party application using the first user-interface template populated with the updated first set of values; and

providing information to the respective display that enables the updated first user interface for the first third-party application to be displayed on the respective display.

14. The medium ofclaim 1, wherein:

the device includes a digital personal assistant process with voice recognition capabilities; and

wherein the one or more programs further comprise instructions, which when executed by an electronic device with one or more processors and memory, cause the device to perform:

determining the capabilities of the first third-party application based on responses from the first third-party application to a plurality of requests to the first third-party application for values associated with populating user-interface templates for user interfaces for the respective display;

generating an index of the capabilities of the first third-party application; and

providing voice access to the capabilities of the first third-party application via the digital personal assistant process.

15. The medium ofclaim 14, wherein the one or more programs further comprise instructions, which when executed by an electronic device with one or more processors and memory, cause the device to perform:

detecting that a predetermined condition has been met; and

in response to detecting that the predetermined condition has been met:

re-determining the capabilities of the first third-party application; and

re-generating the index of the capabilities of the first third-party application.

16. A method, comprising:

at an electronic device with one or more processors and memory:

receiving a first display request to display a user interface of a first third-party application on a respective display that is in communication with the electronic device;

in response to receiving the first display request:

obtaining a first user-interface template that is configured to be used by a plurality of third-party applications; and

requesting, from the first third-party application, one or more values for populating the first user-interface template;

receiving, from the first third-party application, while the first third-party application is running on the electronic device, a first set of values for populating the first user-interface template;

populating the first user-interface template with the first set of values received from the first third-party application;

generating a first user interface for the first third-party application using the first user-interface template populated with the first set of values; and

sending information to the respective display that enables the first user interface for the first third-party application to be displayed on the respective display.

17. An electronic device, comprising:

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:

receiving a first display request to display a user interface of a first third-party application on a respective display that is in communication with the electronic device;

in response to receiving the first display request:

obtaining a first user-interface template that is configured to be used by a plurality of third-party applications; and

requesting, from the first third-party application, one or more values for populating the first user-interface template;

receiving, from the first third-party application, while the first third-party application is running on the electronic device, a first set of values for populating the first user-interface template;

populating the first user-interface template with the first set of values received from the first third-party application;

generating a first user interface for the first third-party application using the first user-interface template populated with the first set of values; and

sending information to the respective display that enables the first user interface for the first third-party application to be displayed on the respective display.

18. The device ofclaim 17, wherein the one or more programs further include instructions for:

while the first user-interface for the first third-party application is displayed on the respective display, receiving, from an input device for the respective display a respective input that corresponds to selection of an option in the first user interface; and

in response to receiving the respective input, providing information to the first third-party application running on the electronic device that enables the first third-party application to respond to selection of the option in the first user interface;

receiving, from the first third-party application, the response to selection of the option from the first third-party application; and

sending information to the respective display that enables the response to selection of the option to be provided to the user.

19. The device ofclaim 17, wherein the one or more programs further include instructions for:

while the first user interface for the first third-party application is displayed on the respective display:

receiving information indicative of a selection of a respective option in the first user interface; and

in response to receiving the information indicative of the selection of the respective option in the first user interface:

obtaining a second user-interface template, different from the first user-interface template; and

requesting, from the first third-party application, one or more values for populating the second user-interface template;

receiving, from the first third-party application, while the first third-party application is running on the electronic device, a second set of values for populating the second user-interface template;

populating the second user-interface template with the second set of values received from the first third-party application;

generating a second user interface for the first third-party application by using the second user-interface template populated with the second set of values; and

sending information to the respective display that enables the second user interface for the first third-party application to be displayed on the respective display.

20. The device ofclaim 17, wherein the one or more programs further include instructions for:

after sending the information to the respective display that enables the first user interface for the first third-party application to be displayed on the respective display:

receiving a second display request to display a user interface for a second third-party application, different from the first third-party application, on the respective display;

in response to receiving the second display request, requesting, from the second third-party application, one or more values for populating the first user-interface template;

receiving, from the second third-party application, while the second third-party application is running on the electronic device, a third set of values for populating the first user-interface template;

populating the first user-interface template with the third set of values received from the second third-party application;

generating a second user interface for the second third-party application using the first user-interface template populated with the third set of values; and

sending information to the respective display that enables the second user interface for the second third-party application to be displayed on the respective display.

Images