WO2018057268A1 - Données d'image pour interactions utilisateur améliorées - Google Patents

Données d'image pour interactions utilisateur améliorées Download PDF

Info

Publication number
WO2018057268A1
WO2018057268A1 PCT/US2017/049760 US2017049760W WO2018057268A1 WO 2018057268 A1 WO2018057268 A1 WO 2018057268A1 US 2017049760 W US2017049760 W US 2017049760W WO 2018057268 A1 WO2018057268 A1 WO 2018057268A1
Authority
WO
WIPO (PCT)
Prior art keywords
content
user
avatar
image data
message
Prior art date
Application number
PCT/US2017/049760
Other languages
English (en)
Other versions
WO2018057268A4 (fr
Inventor
Marek Bereza
Lukas Robert Tom GIRLING
Joseph A. MALIA
Jeffrey Traer Bernstein
William D. LINDMEIER
Mark HAUENSTEIN
Adi Berenson
Amir Hoffnung
Julian Missig
Original Assignee
Apple Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from DKPA201770418A external-priority patent/DK179978B1/en
Priority to EP17853654.6A priority Critical patent/EP3485392B1/fr
Priority to KR1020217015473A priority patent/KR102403090B1/ko
Priority to EP21166287.9A priority patent/EP3920052A1/fr
Priority to JP2019511975A priority patent/JP6824552B2/ja
Priority to AU2017330208A priority patent/AU2017330208B2/en
Application filed by Apple Inc. filed Critical Apple Inc.
Priority to CN201780053143.0A priority patent/CN109691074A/zh
Priority to KR1020197005136A priority patent/KR102257353B1/ko
Publication of WO2018057268A1 publication Critical patent/WO2018057268A1/fr
Publication of WO2018057268A4 publication Critical patent/WO2018057268A4/fr
Priority to AU2020201721A priority patent/AU2020201721B2/en
Priority to AU2021250944A priority patent/AU2021250944B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72427—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality for supporting games or graphical animations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H04M1/72436—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for text messaging, e.g. short messaging services [SMS] or e-mails
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures

Definitions

  • the present disclosure relates generally to computer user interfaces, and more specifically to techniques for using avatars and/or image data for enhanced user interactions.
  • Avatars are used to represent the users of electronic devices.
  • the avatars can represent the appearance of a user or can represent an idealized or completely fictional representation of the user.
  • Avatars can be then be associated with a user so that the appearance of the avatar to others indicates triggers an association or link with the user.
  • the present technique provides electronic devices with faster, more efficient methods and interfaces for using avatars and/or image data to enhance user interactions.
  • Such methods and interfaces optionally complement or replace other methods for using avatars and/or image data to enhance user interactions.
  • Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human- machine interface.
  • For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
  • an electronic device with a display and associated with a first user receives a first message from a second user, wherein the first message includes first content; receives first status data for the second user, wherein the first status data is associated with the first message and separate from the first content;
  • the display displays concurrently, on the display, the first message, including the first content, and a first avatar, wherein the first avatar is based on the first status data and the displayed first avatar is adjacent to the displayed first message; after displaying the first message and the first avatar, receives a second message from the second user, wherein the second message includes second content; receives second status data for the second user, wherein the second status is associated with the second message and separate from the second content; and while maintaining the display of the first message and the first avatar, displays, on the display, the second message, including the second content, and a second avatar, wherein the displayed second avatar is adjacent to the displayed second message, the second avatar is based on the second status data, and the first avatar and the second avatar are different.
  • An embodiment of a transitory computer readable storage medium stores one or more programs, the one or more programs comprise instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the device to: display, on the display, content in an application, wherein the content is displayed while the application is in a first configuration; while displaying the content, capture image data ( from the one or more image sensors of the electronic device; after capturing the image data, receive a request to navigate away from the content; and in response to receiving a request to navigate away from the content: in accordance with a determination that a first set of content-lock criteria have been met, prevent navigation away from the content while maintaining display of the content, wherein the first set of content- lock criteria includes a first criterion that is met when the captured image data indicates that an unauthorized user is using the device; and in accordance with a determination that the first set of content-lock criteria have not been met, navigate away from the content in accordance with the request.
  • an electronic device with one or more image sensors, memory, and a display captures first image data from one or more image sensors of the electronic device, wherein the first image data includes first optical image data of an object from a first perspective; captures second image data from the one or more image sensors of the electronic device, wherein the second image data includes second optical image light data of the object from a second perspective that is different from the first perspective; selects an algorithm based on the change in perspective from the first perspective to the second perspective; based on the algorithm, determines additional image data that is needed to continue the 3D modeling of the object; and displays, on the display, visual feedback that provides instructions for capturing the additional image data
  • An embodiment of a transitory computer readable storage medium stores one or more programs, the one or more programs comprise instructions, which when executed by one or more processors of an electronic device with a display and one or more image sensors, cause the device to: capture first image data from one or more image sensors of the electronic device, wherein the first image data includes first optical image data of an object from a first perspective; capture second image data from the one or more image sensors of the electronic device, wherein the second image data includes second optical image light data of the object from a second perspective that is different from the first perspective; select an algorithm based on the change in perspective from the first perspective to the second perspective; based on the algorithm, determine additional image data that is needed to continue the 3D modeling of the object; and display, on the display, visual feedback that provides instructions for capturing the additional image data determined based on the selected algorithm.
  • an electronic device with a display and one or more image sensors displays, on the display, content in an application, wherein the content is displayed while the application is in a first configuration; while displaying the content, captures image data ( from the one or more image sensors of the electronic device; after capturing the image data, receives a request to navigate away from the content; and in response to receiving a request to navigate away from the content: in accordance with a determination that a first set of content-lock criteria have been met, prevents navigation away from the content while maintaining display of the content, wherein the first set of content-lock criteria includes a first criterion that is met when the captured image data indicates that an unauthorized user is using the device; and in accordance with a
  • An embodiment of a transitory computer readable storage medium stores one or more programs, the one or more programs comprise instructions, which when executed by one or more processors of an electronic device with a display and one or more image sensors, cause the device to: display, on the display, content in an application, wherein the content is displayed while the application is in a first configuration; while displaying the content, capture image data from the one or more image sensors of the electronic device; after capturing the image data, receive a request to navigate away from the content; and in response to receiving a request to navigate away from the content: in accordance with a determination that a first set of content-lock criteria have been met, prevent navigation away from the content while maintaining display of the content, wherein the first set of content- lock criteria includes a first criterion that is met when the captured image data indicates that an unauthorized user is using the device; and in accordance with a determination that the first set of content-lock criteria have not been met, navigate away from the content in accordance with the request.
  • 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. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
  • devices are provided with faster, more efficient methods and interfaces for using image data to enhance user interactions, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices.
  • Such methods and interfaces may complement or replace other methods for using image data to enhance user interactions.
  • FIG. 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.
  • FIG. IB 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. 5A illustrates a personal electronic device in accordance with some embodiments.
  • FIG. 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.
  • FIGs. 6A-6J illustrate exemplary user interfaces for communicating user status information for a message.
  • FIGs. 7A-7B is a flow diagram illustrating a method for communicating user status information for a message.
  • FIG. 8 shows an exemplary functional block diagram of an electronic device.
  • FIGs. 9A-9L illustrate exemplary user interfaces for capturing data for building
  • FIGs. 10A-10B is a flow diagram illustrating a method for capturing data for building 3D models.
  • FIG. 11 shows an exemplary functional block diagram of an electronic device.
  • FIGs. 12A-12J illustrate exemplary user interfaces for restricting access to data and applications based on the user.
  • FIGs. 13A-13B is a flow diagram illustrating a method for restricting access to data and applications based on the user.
  • FIG. 14 shows an exemplary functional block diagram of an electronic device. DESCRIPTION OF EMBODIMENTS
  • avatars and/or image data can be used to enhance user interactions with electronic devices and other users. Such techniques can reduce the cognitive burden on a user who is using avatars and/or image data to communicate with other users and interact with their electronic devices, thereby enhancing productivity.
  • FIGs. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of exemplary devices for performing the techniques for using image data to enhance user interaction, as described below.
  • FIGs. 6A-6J illustrate exemplary user interfaces for communicating user status information for a message with an avatar.
  • FIGs. 7A-7B is a flow diagram illustrating methods of communicating user status information for a message with an avatar in accordance with some embodiments.
  • the user interfaces in FIGs. 6A-6G are used to illustrate the processes described below, including the processes in FIGs. 7A-7B.
  • FIGs. 9A-9L illustrate exemplary user interfaces for capturing data for building
  • FIGs. 10A-10B is a flow diagram illustrating methods of capturing data for building 3D models in accordance with some embodiments.
  • the user interfaces in FIGs. 9A-9L are used to illustrate the processes described below, including the processes in FIGs. 10A-10B.
  • FIGs. 12A-12J illustrate exemplary user interfaces for restricting access to data and applications based on the user.
  • FIGs. 13A-13B is a flow diagram illustrating methods of restricting access to data and applications based on the user in accordance with some embodiments.
  • the user interfaces in FIGs. 12A-12J are used to illustrate the processes described below, including the processes in FIGs. 13A-13B.
  • first means "first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another.
  • a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments.
  • the first touch and the second touch are both touches, but they are not the same touch.
  • 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.
  • portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.
  • Other portable electronic devices such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used.
  • 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 touchpad).
  • 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.
  • 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.
  • FIG. 1A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments.
  • Touch- sensitive display 112 is sometimes called a "touch screen” for convenience and is sometimes known as or called a "touch-sensitive display system.”
  • Device 100 includes memory 102 (which optionally includes one or more computer-readable storage mediums), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external port 124.
  • Device 100 optionally includes one or more optical sensors 164.
  • Device 100 optionally includes one or more contact intensity sensors 165 for detecting intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100).
  • Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.
  • tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300).
  • These components optionally communicate over one or more communication buses or signal lines 103.
  • 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.
  • 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.
  • force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact.
  • a pressure- sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface.
  • 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.
  • 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).
  • the intensity threshold is described in units corresponding to the substitute measurements.
  • 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).
  • the intensity threshold is a pressure threshold measured in units of pressure.
  • 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.
  • a component e.g., a touch- sensitive surface
  • another component e.g., housing
  • 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.
  • a touch-sensitive surface e.g., a touch-sensitive display or trackpad
  • movement of a touch-sensitive surface is, optionally, interpreted by the user as a "down click" or "up click" of a physical actuator button.
  • 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.
  • 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.
  • a tactile output is described as
  • 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.
  • device 100 is only one example of a portable multifunction device, and that device 100 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 in FIG. 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application- specific integrated circuits.
  • Memory 102 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.
  • Memory controller 122 optionally controls access to memory 102 by other components of device 100.
  • Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102.
  • the one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
  • peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally,
  • RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from
  • RF circuitry 108 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 circuitry 108 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 RF circuitry 108 optionally includes well-known circuitry for detecting near field
  • 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, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.
  • VoIP voice over Internet Protocol
  • 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.
  • IMAP Internet message access protocol
  • POP post office protocol
  • 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)
  • SMS Short Message Service
  • Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100.
  • Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111.
  • Speaker 111 converts the electrical signal to human-audible sound waves.
  • Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves.
  • Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118.
  • audio circuitry 110 also includes a headset jack (e.g., 212, FIG. 2).
  • the headset jack provides an interface between audio circuitry 110 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
  • I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118.
  • I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices.
  • the one or more input controllers 160 receive/send electrical signals from/to other input control devices 116.
  • the other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth.
  • input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse.
  • the one or more buttons optionally include an up/down button for volume control of speaker 111 and/or microphone 113.
  • the one or more buttons optionally include a push button (e.g., 206, FIG. 2).
  • a quick press of the push button optionally disengages a lock of touch screen
  • a longer press of the push button (e.g., 206) optionally turns power to device 100 on or off.
  • the functionality of one or more of the buttons are, optionally, user-customizable.
  • Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
  • Touch-sensitive display 112 provides an input interface and an output interface between the device and a user.
  • Display controller 156 receives and/or sends electrical signals from/to touch screen 112.
  • Touch screen 112 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 optionally corresponds to user-interface objects.
  • Touch screen 112 has a touch- sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact.
  • Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112.
  • user-interface objects e.g., one or more soft keys, icons, web pages, or images
  • a point of contact between touch screen 112 and the user corresponds to a finger of the user.
  • Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD
  • Touch screen 112 and display controller 156 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 with touch screen 112.
  • 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 with touch screen 112.
  • projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
  • a touch- sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety.
  • touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
  • a touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. Patent Application No. 11/381,313, "Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. Patent Application No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. Patent Application No. 10/903,964, "Gestures For Touch Sensitive Input Devices,” filed July 30, 2004; (4) U.S. Patent Application No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. Patent Application No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. Patent Application No. 10/903,964, "Gestures For Touch Sensitive Input Devices," filed July 30, 2004; (4) U.S. Patent
  • Touch screen 112 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 with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth.
  • 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.
  • the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
  • device 100 in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions.
  • 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 from touch screen 112 or an extension of the touch- sensitive surface formed by the touch screen.
  • Device 100 also includes power system 162 for powering the various components
  • Power system 162 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.
  • 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.
  • power sources e.g., battery, alternating current (AC)
  • AC alternating current
  • a recharging system e.g., a recharging system
  • a power failure detection circuit e.g., a
  • Device 100 optionally also includes one or more optical sensors 164.
  • FIG. 1A shows an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106.
  • Optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors.
  • CCD charge-coupled device
  • CMOS complementary metal-oxide semiconductor
  • Optical sensor 164 receives light from the environment, projected through one or more lenses, and converts the light to data representing an image.
  • imaging module 143 also called a camera module
  • optical sensor 164 optionally captures still images or video.
  • imaging module 143 also called a camera module
  • an optical sensor is located on the back of device 100, opposite touch screen display 112 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.
  • an optical sensor is located on the front of the device so that the user's image is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display.
  • the position of optical sensor 164 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 164 is used along with the touch screen display for both video conferencing and still and/or video image acquisition.
  • Device 100 optionally also includes one or more contact intensity sensors 165.
  • FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I/O subsystem 106.
  • Contact intensity sensor 165 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 sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment.
  • at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112).
  • at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.
  • Device 100 optionally also includes one or more proximity sensors 166.
  • FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.
  • proximity sensor 166 is, optionally, coupled to input controller 160 in I/O subsystem 106.
  • Proximity sensor 166 optionally performs as described in U.S. Patent Application Nos.
  • the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).
  • Device 100 optionally also includes one or more tactile output generators 167.
  • FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I/O subsystem 106.
  • Tactile output generator 167 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 sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that are capable of being sensed by a user of device 100.
  • At least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device 100) or laterally (e.g., back and forth in the same plane as a surface of device 100).
  • at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.
  • Device 100 optionally also includes one or more accelerometers 168.
  • FIG. 1A shows accelerometer 168 coupled to peripherals interface 118.
  • accelerometer 168 is, optionally, coupled to an input controller 160 in I/O subsystem 106.
  • Accelerometer 168 optionally performs as described in U.S. Patent Publication No. 20050190059,
  • Device 100 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) of device 100.
  • the software components stored in memory 102 include operating system 126, 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.
  • memory 102 FIG. 1A
  • 370 FIG. 3
  • Device/global internal state 157 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 of touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and location information concerning the device's location and/or attitude.
  • Operating system 126 e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,
  • WINDOWS or an embedded operating system such as Vx Works
  • Vx Works 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 module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124.
  • External port 124 e.g.,
  • USB Universal Serial Bus
  • FIREWIRE FireWire
  • 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.
  • Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel).
  • Contact/motion module 130 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 module 130 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'Vmultiple finger contacts).
  • contact/motion module 130 and display controller 156 detect contact on a touchpad.
  • contact/motion module 130 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).
  • 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 device 100). For example, a mouse "click" threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware.
  • 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 module 130 optionally detects a gesture input by a user.
  • a gesture is, optionally, detected by detecting a particular contact pattern.
  • detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon).
  • 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 (liftoff) event.
  • Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 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.
  • 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.
  • graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 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 display controller 156.
  • Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
  • Text input module 134 which is, optionally, a component of graphics module
  • 132 provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
  • applications e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
  • GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location- based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
  • applications e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location- based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
  • Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
  • Contacts module 137 (sometimes called an address book or contact list);
  • Video conference module 139 • E-mail client module 140;
  • Camera module 143 for still and/or video images
  • Calendar module 148 • Calendar module 148;
  • Widget modules 149 which optionally include one or more of: weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;
  • Widget creator module 150 for making user-created widgets 149-6;
  • Video and music player module 152 which merges video player module and music player module
  • Map module 154 • Map module 154;
  • Examples of other applications 136 that are, optionally, stored in memory 102 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.
  • contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including:
  • telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, 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.
  • the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
  • video conference module 139 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.
  • e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
  • the instant messaging module 141 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
  • SMS Short Message Service
  • Multimedia Message Service MMS
  • XMPP extensible Markup Language
  • SIMPLE extensible Markup Language
  • IMPS Internet-based instant messages
  • transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS).
  • EMS Enhanced Messaging Service
  • 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).
  • workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
  • create workouts e.g., with time, distance, and/or calorie burning goals
  • communicate with workout sensors sports devices
  • receive workout sensor data calibrate sensors used to monitor a workout
  • select and play music for a workout and display, store, and transmit workout data.
  • camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
  • image management module 144 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.
  • modify e.g., edit
  • present e.g., in a digital slide show or album
  • browser module 147 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.
  • calendar module 148 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.
  • widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user- created widget 149-6).
  • a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file.
  • a widget includes an XML (Extensible Markup Language) file and a
  • the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user- specified portion of a web page into a widget).
  • search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user- specified search terms) in accordance with user instructions.
  • search criteria e.g., one or more user- specified search terms
  • video and music player module 152 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., on touch screen 112 or on an external, connected display via external port 124).
  • device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
  • notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
  • map module 154 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.
  • maps e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data
  • online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264.
  • instant messaging module 141 rather than e-mail client module 140, is used to send a link to a particular online video.
  • modules and applications corresponds 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).
  • modules e.g., sets of
  • memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.
  • device 100 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.
  • a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 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.
  • the touchpad when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100.
  • a "menu button" is implemented using a touchpad.
  • the menu button is a physical push button or other physical input control device instead of a touchpad.
  • FIG. IB is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.
  • memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).
  • event sorter 170 e.g., in operating system 126
  • application 136-1 e.g., any of the aforementioned applications 137-151, 155, 380-390.
  • Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information.
  • Event sorter 170 includes event monitor 171 and event dispatcher module 174.
  • application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing.
  • device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
  • application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
  • Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch- sensitive display 112, as part of a multi-touch gesture).
  • Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110).
  • Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
  • event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 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).
  • event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
  • Hit view determination module 172 provides software procedures for
  • FIG. 110 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.
  • Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 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 (e.g., 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 172, 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 event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location 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 module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
  • an event recognizer e.g., event recognizer 180.
  • event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173.
  • event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
  • operating system 126 includes event sorter 170.
  • application 136-1 includes event sorter 170.
  • event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
  • application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface.
  • Each application view 191 of the application 136-1 includes one or more event recognizers 180.
  • a respective application view 191 includes a plurality of event recognizers 180.
  • one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136- 1 inherits methods and other properties.
  • a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170.
  • Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192.
  • one or more of the application views 191 include one or more respective event handlers 190.
  • one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
  • a respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information.
  • Event recognizer 180 includes event receiver 182 and event comparator 184. In some
  • event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
  • Event receiver 182 receives event information from event sorter 170.
  • the event information includes information about a sub-event, for example, a touch or a touch movement.
  • the event information also includes additional information, such as location of the sub-event.
  • the event information optionally also includes speed and direction of the sub-event.
  • 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 comparator 184 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.
  • event comparator 184 includes event definitions 186.
  • Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others.
  • sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching.
  • 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 liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase.
  • 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 display 112, and liftoff of the touch (touch end).
  • the event also includes information for one or more associated event handlers 190.
  • event definition 187 includes a definition of an event for a respective user-interface object.
  • event comparator 184 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 display 112, when a touch is detected on touch- sensitive display 112, event comparator 184 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 a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
  • the definition for a respective event (187) 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.
  • a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 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.
  • a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers.
  • metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another.
  • metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
  • a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized.
  • a respective event recognizer 180 delivers event information associated with the event to event handler 190.
  • Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view.
  • event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
  • event delivery instructions 188 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.
  • data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module.
  • object updater 177 creates and updates objects used in application 136-1.
  • object updater 177 creates a new user-interface object or updates the position of a user-interface object.
  • GUI updater 178 updates the GUI.
  • GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch- sensitive display.
  • event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178.
  • data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
  • event handling of user touches on touch- sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens.
  • 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 touchpads; 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 a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments.
  • the touch screen optionally displays one or more graphics within user interface (UI) 200.
  • UI user interface
  • 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 fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure).
  • selection of one or more graphics occurs when the user breaks contact with the one or more graphics.
  • 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 with device 100.
  • inadvertent contact with a graphic does not select the graphic.
  • 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.
  • Device 100 optionally also include one or more physical buttons, such as "home" or menu button 204.
  • menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100.
  • the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
  • device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124.
  • Push button 206 is, optionally, used to turn 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.
  • device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113.
  • Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
  • FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.
  • Device 300 need not be portable.
  • device 300 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).
  • Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components.
  • Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components.
  • Device 300 includes input/output (I/O) interface 330 comprising display 340, which is typically a touch screen display.
  • I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A), sensors 359 (e.g., optical, acceleration, proximity, touch- sensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A).
  • I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A), sensors 359 (e.g., optical, acceleration, proximity, touch- sensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165
  • Memory 370 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. Memory 370 optionally includes one or more storage devices remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100.
  • memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.
  • Each of the above-identified elements in FIG. 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 (e.g., 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 rearranged in various embodiments.
  • memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.
  • FIG. 4A illustrates an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device 300.
  • user interface 400 includes the following elements, or a subset or superset thereof:
  • Tray 408 with icons for frequently used applications such as: o Icon 416 for telephone module 138, labeled “Phone,” which optionally includes an indicator 414 of the number of missed calls or voicemail messages; o Icon 418 for e-mail client module 140, labeled “Mail,” which optionally includes an indicator 410 of the number of unread e-mails; o Icon 420 for browser module 147, labeled “Browser;” and o Icon 422 for video and music player module 152, also referred to as iPod
  • Icons for other applications such as: o Icon 424 for IM module 141, labeled “Messages;” o Icon 426 for calendar module 148, labeled “Calendar;” o Icon 428 for image management module 144, labeled “Photos;” o Icon 430 for camera module 143, labeled “Camera;” o Icon 432 for online video module 155, labeled “Online Video;” o Icon 434 for stocks widget 149-2, labeled “Stocks;” o Icon 436 for map module 154, labeled “Maps;” o Icon 438 for weather widget 149-1, labeled “Weather;” o Icon 440 for alarm clock widget 149-4, labeled “Clock;” o Icon 442 for workout support module 142, labeled “Workout Support;” o Icon 444 for notes module 153, labeled “Notes;” and o Icon 446 for notes module
  • icon labels illustrated in FIG. 4A are merely exemplary.
  • icon 422 for video and music player module 152 is labeled "Music" or "Music Player.”
  • Other labels are, optionally, used for various application icons.
  • a label for a respective application icon includes a name of an application corresponding to the respective application icon.
  • 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., device 300, FIG. 3) with a touch- sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3) that is separate from the display 450 (e.g., touch screen display 112).
  • Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch- sensitive surface 451 and/or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.
  • one or more contact intensity sensors e.g., one or more of sensors 359
  • tactile output generators 357 for generating tactile outputs for a user of device 300.
  • the device detects inputs on a touch- sensitive surface that is separate from the display, as shown in FIG. 4B.
  • the touch- sensitive surface e.g., 451 in FIG. 4B
  • the touch- sensitive surface has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450).
  • the device detects contacts (e.g., 460 and 462 in FIG.
  • finger inputs e.g., finger contacts, finger tap gestures, finger swipe gestures
  • one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input).
  • 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).
  • 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).
  • 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. 5A illustrates exemplary personal electronic device 500.
  • Device 500 includes body 502.
  • device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGs. 1A-4B).
  • device 500 has touch-sensitive display screen 504, hereafter touch screen 504.
  • touch screen 504 optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied.
  • the one or more intensity sensors of touch screen 504 (or the touch- sensitive surface) can provide output data that represents the intensity of touches.
  • the user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device 500.
  • PCT/US2013/040061 titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for
  • device 500 has one or more input mechanisms 506 and 508.
  • Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms.
  • device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
  • FIG. 5B depicts exemplary personal electronic device 500.
  • device 500 can include some or all of the components described with respect to FIGs. 1A, IB, and 3.
  • Device 500 has bus 512 that operatively couples I/O section 514 with one or more computer processors 516 and memory 518.
  • I/O section 514 can be connected to display 504, which can have touch- sensitive component 522 and, optionally, intensity sensor 524 (e.g., contact intensity sensor).
  • I/O section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques.
  • Device 500 can include input mechanisms 506 and/or 508.
  • Input mechanism 506 is, optionally, a rotatable input device or a depressible and rotatable input device, for example.
  • Input mechanism 508 is, optionally, a button, in some examples.
  • Input mechanism 508 is, optionally, a microphone, in some examples.
  • Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
  • sensors such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
  • Memory 518 of personal electronic device 500 can include one or more non- transitory computer-readable storage mediums, for storing computer-executable
  • Personal electronic device 500 is not limited to the components and configuration of FIG. 5B, but can include other or additional components in multiple configurations.
  • the term "affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (FIGs. 1, 3, and 5).
  • an image e.g., icon
  • a button e.g., button
  • text e.g., hyperlink
  • the term "focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting.
  • the cursor acts as a "focus selector” so that when an input (e.g., a press input) is detected on a touch- sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input.
  • a touch- sensitive surface e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B
  • a particular user interface element e.g., a button, window, slider, or other user interface element
  • a detected contact on the touch screen acts as a "focus selector" so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input.
  • a particular user interface element e.g., a button, window, slider, or other user interface element
  • focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface.
  • the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user's intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact).
  • a focus selector e.g., a cursor, a contact, or a selection box
  • a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).
  • the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact).
  • a predefined time period e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds
  • a characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like.
  • the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time).
  • the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user.
  • the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold.
  • a contact with a characteristic intensity that does not exceed the first threshold results in a first operation
  • a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation
  • a contact with a characteristic intensity that exceeds the second threshold results in a third operation.
  • a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.
  • a portion of a gesture is identified for purposes of determining a characteristic intensity.
  • a touch- sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases.
  • the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location).
  • a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact.
  • the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm.
  • these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
  • the intensity of a contact on the touch- sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds.
  • the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad.
  • the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad.
  • the device when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold.
  • a characteristic intensity below the light press intensity threshold e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected
  • these intensity thresholds are consistent between different sets of user interface figures.
  • An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press” input.
  • An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press” input.
  • An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface.
  • a decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface.
  • the contact- detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
  • one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold.
  • the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a "down stroke" of the respective press input).
  • the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press- input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an "up stroke" of the respective press input).
  • the device employs intensity hysteresis to avoid accidental inputs sometimes termed "jitter," where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold).
  • the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold.
  • the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an "up stroke" of the respective press input).
  • the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
  • the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold.
  • the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press- input intensity threshold.
  • UI user interfaces
  • portable multifunction device 100 such as portable multifunction device 100, device 300, or device 500.
  • FIGs. 6A-6J illustrate exemplary user interfaces for communicating user status information for a message, in accordance with some embodiments.
  • the user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGs. 7A-7B.
  • FIG. 6A depicts device 600, which in some examples is a specific form factor for device 100, device 300, or device 500 described above.
  • Device 600 includes display 601, which in some embodiments is a touch- sensitive display, and image sensor 602.
  • additional sensors e.g., depth sensors, IR sensors, etc.
  • other components e.g., flash or IR emitter
  • display 601 is displaying messaging interface 603 for another user named "Joe.”
  • Messaging interface 603 includes back button 604, username 605, user picture 606, and contact information button 607.
  • back button 604 In response to the user selecting back button 604, by, for example, touching back button 604 on display 601, messaging interface 603 returns to a main messaging screen where recent messages are displayed and/or other contacts are selected for communicating with.
  • User name 605 and user picture 606 indicate the other user that messaging interface 603 is configured to communicate with.
  • User picture 606 is, for example, an avatar (e.g., emoji or other graphical representation such as a non- photorealistic graphical representation) for the other user, a picture of the other user, or some other image associated with the other contact.
  • avatar e.g., emoji or other graphical representation such as a non- photorealistic graphical representation
  • the contact information button 607 causes device 600 to open a user interface page that allows the user to initiate communicate with the other user using other channels of communication, allows the user to send certain types of information (e.g., a current location) to the other user, allows the user to change communications settings for the other user, and/or allows the user to review information related to previous communications with the other user.
  • certain types of information e.g., a current location
  • Messaging interface 603 includes message area 608, which is empty in FIG. 6A, and message entry area 609.
  • Message entry area includes photo button 610, drawing button 611, sticker/emoji button 612, text entry field 613, and voice recognition button 614.
  • Photo button 610 allows the user to either select an existing picture/video or capture a new picture/video to include in a message to the other user.
  • Drawing button 611 allows the user to create a sketch to include in a message to the other user.
  • Sticker/emoji button 612 allows a user to select stickers and/or emojis to include in a message to the other user.
  • Text entry field 613 allows a user to enter text that will be included in a message to the other user. In FIG. 6A, text entry field 613 includes the word "iMessage,” which indicates the type of textual message that will be sent to the other user.
  • Voice recognition button 614 allows a user to enter text for text entry field 613 by speaking into device 600 instead of manually entering the
  • keyboard 616 is displayed on display 601. Additionally, text entry field 613 is moved up the display and expanded by hiding photo button 610, drawing button 611, and sticker/emoji button 612 of FIG. 6A. These buttons are redisplayed if the user selects expand button 617. Additionally, in some examples, a cursor (not shown) is displayed inside of text entry field 613.
  • text entry field 613 is updated to include the selected letters.
  • voice recognition button 614 (FIG. 6B) is replaced with send button 620, which sends the currently entered message, including entered text and other data such as image data, to the other user.
  • FIG. 6D depicts messaging interface 603 after additional text entry via additional touches on keyboard 616.
  • Text entry field 613 includes the additional entered text.
  • the user indicates that the message is ready to be sent by, for example, selecting send button 620 via touch 621 on display 601.
  • device 600 prepares the message that includes, in the example of FIG. 6D, the text in text entry field 613.
  • device 600 sends the message to the other user (the other user named "Joe" in the case of the example of FIGs. 6A-6F).
  • device 600 also sends status data of the user of device 600 to the other user (e.g., status data associated with a user account currently associated with device 600).
  • the status data of the user represents a physical state (e.g., tired, sick, hot, cold, bored) or an emotional state (e.g., happy, sad, concerned, angry).
  • the status data can be obtained from any number of sources.
  • the status data is obtained by presenting the user with a list of statuses and allowing the user to select one of the statuses that represents the user or the content of the message that the user is sending.
  • device 600 prompts the user with a list of statuses that the user can chose to associate and send with the message having content that includes the text of text entry field 613.
  • to obtain status data device 600 is configured to determine automatically a status data for the user.
  • Device 600 determines status data, in some examples, based on the content of the message, based on image data of the user using one or more image sensors (e.g., image sensor 602 of FIG. 6A), and/or based on other contextual information (e.g., calendar entries, weather, time of day/year, location, etc.) that is available to device 600.
  • Device 600 can use the data from image sensor 602 or other sensors, such as biometric sensors, to perform facial recognition to identify a facial expression or obtain physiological data (e.g., heart rate or temperature) for determining a user status.
  • the user status is personal to the user and not associated with objects (e.g., electronic devices) related to the user.
  • the user status data is associated with the message and sent to the other user either with the message (e.g., as part of the message) or separately from the message (e.g., before, after, or concurrently with sending the message).
  • the message content is displayed in message area 608 in displayed in text box 622.
  • Text box 622 optionally, also includes other, non-textual content of the message (e.g., images, animations, video, etc.).
  • avatar 623 is also displayed adjacent to text box 622 (e.g., the message is coming from the avatar's mouth).
  • avatar 623 is generated based on a previously defined (e.g., baseline) avatar or avatar model (e.g., a wire, mesh, or structural model) that represents the user of device 600.
  • avatar 623 is based on the user status data that is associated with the message in text box 622.
  • the user status data for the message in text box 622 was sympathetic.
  • the messaging application determined that a smiling avatar is most appropriate for this status data. Accordingly, avatar 623 was generated to show a smile and a warm expression.
  • the generated avatar can include accessories (e.g., an umbrella in rain, sunglasses when on the beach, a costume on Halloween, or gift when wishing someone a happy birthday).
  • the generated avatar is an animated avatar.
  • FIG. 6F depicts messaging interface 603 after a message and associated status data was received from the other user named "Joe” (e.g., received from an electronic device associated with the other user "Joe”).
  • the content of the message is displayed in text box 624 in message area 608.
  • an associated avatar 625 is displayed adjacent text box 624.
  • avatar 625 is based on a previously defined avatar or avatar model, except the predefined (e.g., baseline) avatar or avatar model is for "Joe,” instead of the user of device 600.
  • the previously defined avatar or avatar model is, optionally, set by the user of device 600 or is provided by the other user or by a remote server.
  • Device 600 optionally, stores the previously defined avatar or avatar model locally or it retrieves the previously defined avatar or avatar model as needed.
  • the message application on device 600 loads the previously defined avatar or avatar model and modifies it or uses it to generate an avatar based on the user status data associated with the received message.
  • the user status data for a message received from another user can be received as part of the message or separately from the message (e.g., before, after, or concurrently with the message).
  • the user status data for the other user is determined in a similar manner as described above with respect to the user except that the other user's device (e.g., "Joe's" device) does the determination.
  • the other user's device e.g., "Joe's" device
  • the other user's device determines that the user status was agreeable and ashamed.
  • avatar 625 is based on the user status data.
  • the messaging application generated avatar 625 based on the agreeable and ashamed user status data to include a smile and a thumbs-up.
  • avatar 625 is an animated avatar (the arrow represents animated shaking of the avatar thumb).
  • avatar 625 is optionally saved on device 600 and associated with the other user.
  • user picture 606 is replaced with avatar 625 or subsequently generated avatars for the contact.
  • the other user's information is displayed (e.g., in other applications or in a contact list)
  • the avatar that represents the most recently received user status data for the other user is displayed.
  • FIG. 6G depicts messaging interface 603 after the user of device 600 has entered and sent another message to the other user named "Joe.”
  • the content of the message is displayed in text box 626 in message area 608.
  • avatar 627 is displayed adjacent to text box 626 and is generated based on user status data for the user when the message associated with text box 626 was sent.
  • device 600 e.g., as programed by the messaging application
  • avatar 627 was generated to have a sad expression as compared to avatar 623 (e.g., the eyes, eyebrows, and mouth were all changed to reflect a sad expression).
  • avatar 627 reflects new user status data as compared to avatar 623, avatar 623 remains unchanged. In other words, avatar 623 stays the same despite device 600 receiving updated user status data.
  • the unchanged status of avatar 623 may function as a historical record of the user's status, even as status data is subsequently updated.
  • avatars 623 and 627 can be updated based on a new baseline avatar or avatar model. For example, if the user of device 600 shaves his beard and updates his baseline avatar or avatar model accordingly, avatars 623 and 627 are updated to remove the beard, but the expressions and other features based on the user status data remain (although they can be modified based on the new baseline avatar or avatar model). In some embodiments, previously generate avatars, such as avatars 623 and 627, are not updated even when the baseline avatar or avatar model is updated.
  • FIG. 6G depicts messaging interface 603 after the user of device 600 has received another message from the other user named "Joe.”
  • the content of the message is displayed in text box 628 in message area 608.
  • avatar 629 is displayed adjacent to text box 628 and is generated based on user status data for the other user that was received and associated with the message represented in text box 628. Based on user status data indicating that the other user was apologetic, avatar 629 was generated to have a concerned expression.
  • avatar 629 reflects new user status data for the other user as compared to avatar 625, avatar 625 remains unchanged. As shown in FIG. 6G, avatar 625 stays the same despite device 600 receiving updated user status data. In this manner, it is easy to determine the state of a user when they set a particular message. This results in a more efficient interface that allows a user to search for and comprehend messages faster.
  • avatars 625 and 629 can be updated based on a new baseline avatar or avatar model. For example, if the other user starts wearing glasses and updates his baseline avatar or avatar model accordingly and the other user sends out a new baseline avatar or avatar models and avatars 625 and 629 are updated to add glasses, but the expressions and other features based on the user status data remain (although they can be modified based on the new baseline avatar or avatar model). In some embodiments, previously generate avatars, such as avatars 625 and 629, are not updated even when the baseline avatar or avatar model for the other user is updated.
  • FIG. 61 depicts message application interface 630 that includes edit button 631, title 632, compose button 633, and affordances 634-636.
  • Interface 630 is optionally displayed in response to selection of back button 604 in FIG. 6H.
  • Selection of edit button 631of interface 630 allows a user to select particular contact affordances and perform an operation (e.g., deletion) on contact information associated with the selected affordances.
  • Title 632 provides the name of the message application.
  • Selection of compose button 633 allows a user to create a new message and select recipients for the message.
  • Affordances 634-636 display contact information for different remote users.
  • each affordance includes contact information, such as a user name, a summary of the most recent communication with the other user, a graphical element associated with the other user, and the time of the most recent communication.
  • the graphical element is the most recently generated avatar for the other user.
  • affordance 634 for "Joe Smith” includes avatar 629, which was the most recently generated avatar for "Joe Smith” based on the user status received with the message associated with text box 629 of FIG. 6H.
  • This avatar is optionally updated with subsequently generated avatars that are based on subsequently received user status data so that the contact list in interface 630 always includes an avatar reflecting the most up-to-date status of the other user.
  • Selection of one of the affordance returns the display of messaging interface 603.
  • selection of contact affordance 634 will return the display of messaging interface 603 as depicted in FIG. 6H.
  • Affordance 635 does not have an associated avatar. Instead monogram 637 is displayed in place of displaying an avatar.
  • FIG. 6J depicts messaging interface 603 for the other user "Joe” after a new baseline avatar or avatar model is received for "Joe.”
  • Joe has grown a mustache and updated his avatar accordingly.
  • device 600 In response to receiving the new baseline avatar or avatar model, device 600, for example via the messaging program, has updated avatars 625 and 629 with avatars 638 and 639 to reflect Joe's new mustache.
  • Avatars 628 and 629 continue to be based on the user status data received with the corresponding messages. In the example shown in FIG. 6J, this means that the facial expressions remain the same.
  • FIGs. 7A-7B are a flow diagram illustrating a method for an enhanced messaging interface using an electronic device in accordance with some embodiments.
  • Method 700 is performed at a device (e.g., 100, 300, 500) with a display.
  • Some operations in method 700 are, optionally, combined, the order of some operations are, optionally, changed, and some operations are, optionally, omitted.
  • method 700 provides an intuitive way for communicating user status information for a message.
  • the method reduces the cognitive burden on a user for communicating status information, thereby creating a more efficient human-machine interface.
  • An electronic device e.g., device 600 of FIGs. 6A-6J with a display (e.g., display 601 of device 600), is associated a first user (e.g., the owner or user of device 600).
  • the electronic device receives (702) a first message (e.g., message associated with text box 624 of FIGs. 6F-6J) (e.g., a SMS message, a MMS message, an iMessage, or other type of message) from a second user (e.g., the other user having user name 605 and user picture 606 of FIG. 6A).
  • the first message includes first content (e.g., content in text box 624 of FIGs. 6F-6H).
  • the second user is associated with a source electronic device that sends the first message and the second message.
  • the electronic device receives (704) first status data (e.g., an emotional or physical state or other state associated with or personal to the other user) for the second user.
  • the first status data is associated with the first message and separate from the first content (e.g., the first status data is transmitted as a part of the message that is separate from the content or is sent separately from the message but in a manner that allows identification of the status data as being for a message).
  • the status data can be obtained from any number of sources.
  • the status data is obtained by presenting the user with a list of statuses and allowing the user to select one of the statuses that represents the user or the content of the message that the user is sending.
  • the electronic device is configured to determine automatically a status data for the user based on, for example, image data of the user using one or more image sensors (e.g., image sensor 602 of FIG. 6A), and/or based on other contextual information (e.g., calendar entries, weather, time of day/year, location, etc.) that is available to the electronic device.
  • image data e.g., image sensor 602 of FIG. 6A
  • other contextual information e.g., calendar entries, weather, time of day/year, location, etc.
  • data from image sensor 602 or other sensors, such as biometric are used to perform facial recognition to identify a facial expression or obtain physiological data (e.g., heart rate or temperature) for determining a user status.
  • physiological data e.g., heart rate or temperature
  • the user status is personal to the user and not associated with objects (e.g., electronic devices) related to the user.
  • the user status data is associated with the message and sent to the other user either with the message (e.g., as part of the message) or separately from the message (e.g., before, after, or concurrently with sending the message).
  • the display of the electronic device displays (706) the first message, including the first content (e.g., content in text box 624), and a first avatar (e.g., avatar 624 of FIGs. 6F-6H) (e.g., emoji or other graphical representations).
  • the first avatar is based on the first status data and the displayed first avatar is adjacent to the displayed first message (e.g., the message is coming from the avatar's mouth).
  • the electronic device After displaying the first message and the first avatar, the electronic device receives (708) a second message (e.g., another SMS message, MMS message, iMessage, or other type of message) from the second user, wherein the second message includes second content (e.g., context in text box 629 of FIG. 6H).
  • a second message e.g., another SMS message, MMS message, iMessage, or other type of message
  • second message includes second content (e.g., context in text box 629 of FIG. 6H).
  • the electronic device receives (710) second status data (e.g., emotional or physical state) for the sender, wherein the second status is associated with the second message and separate from the second content.
  • second status data e.g., emotional or physical state
  • the second status data is generated and sent in a similar manner as the first status data.
  • the display of the electronic device displays (712) the second message, including the second content (e.g., text box 629 of FIG. 6H), and a second avatar (e.g., avatar 629 of FIG. 6H) (e.g., emoji or other graphical representations), wherein the displayed second avatar is adjacent to the displayed second message (e.g., the message is coming from the avatar's mouth), the second avatar is based on the second status data, and the first avatar and the second avatar are different.
  • the operability of the electronic device is enhanced by increasing the amount of information presented on the display.
  • users can quickly scan messages and determine some context associated with the messages based on the avatars without having to read the text content of the message.
  • This improved operability of the electronic device makes it more efficient, reduces power usage, and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
  • the different avatars for different messages can help when a user is trying to find a particular message that the user knows to be associated with a particular status (e.g., a sad message, in some instances, will have a sad avatar).
  • a message-specific avatar may help the reader accurately interpret the meaning of the message.
  • the electronic device displays (720) contact information (e.g., FIG. 61) (e.g., phone number, email address, user names, recent communications, etc.) for a set of users that includes contact information for the second user (e.g., information in affordance 633 of FIG. 6J), wherein the second avatar (e.g., avatar 629) is displayed with the contact information for the second user.
  • the second avatar e.g., avatar 629
  • the second avatar upon detection of a change in status of the second user, the second avatar is replaced with a third avatar for the second user.
  • the user of the electronic device also has access to the avatar that represents the most recent status of the second user.
  • This provides for a more efficient interface by eliminating the need for the user of the electronic device to review old messages to determine the second user's status during the last communication.
  • the user is required to make fewer interactions with the electronic device to retrieved desired information, which makes the electronic device more efficient, reduces power usage, and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
  • the electronic device stores a first association of the first avatar or first status data with contact information for the second user (e.g., linking the first avatar or first status data with contact information in a database or as part of the contact information) and stores a second association of the second avatar or second status data with contact information for the second user (e.g., linking the first avatar or first status data with contact information in a database or as part of the contact information).
  • the electronic device receives a first avatar model (e.g., a wire mesh, parameterized model) for the second user, generates the first avatar (e.g., 625) based on the first avatar model and first status data (e.g., an avatar that looks like the second user with a first expression such as a smile), and generates the second avatar (e.g., 629) based on the first avatar model and the second status data, (e.g., an avatar that looks like the second user with a second expression such as a frown).
  • a first avatar model e.g., a wire mesh, parameterized model
  • first status data e.g., an avatar that looks like the second user with a first expression such as a smile
  • second avatar e.g., 629
  • the electronic device maps the first status data on to a predefined avatar model (e.g., a preexisting avatar on the electronic device) to create the first avatar (e.g., 625).
  • a predefined avatar model e.g., a preexisting avatar on the electronic device
  • the electronic device can more efficiently generate the second user avatars based on the received status data because a baseline avatar need not be received or generated each time a new avatar is generated.
  • the electronic device is more efficient, uses less power, and has longer battery life by limiting the processing power necessary to generate the avatars.
  • the electronic device receives (722) a second avatar model (e.g., a wire mesh, parameterized model) for the second user and generates (724) an updated first avatar (e.g., 637) based on the second avatar model and first status data.
  • the electronic device generates (726) an updated second avatar (e.g., 638) based on the second avatar model and the second status data.
  • the electronic device also displays (728) the updated first avatar instead of the first avatar with the first message including the first content (e.g., FIG. 6J) (e.g., updating the displayed avatars while leaving the message content and the contextual information related to the avatar unchanged).
  • the first avatar (e.g., 625) and second avatar (629) represent the physical appearance of the second user (e.g., the avatars are reflective of the second user's appearance).
  • the messaging interface ensures that the avatars always reflect the second user's current avatar. This provides for a more efficient interface by eliminating the need for the user of the electronic device to recognize multiple different baseline avatars being associated with the second user.
  • the user can more quickly and efficiently interact with the electronic device, which makes the electronic device more efficient, reduces power usage, and improves battery life of the device.
  • the first status data is based on (716) a first biometric characteristic (e.g., depth information, facial recognition, heart rate, etc.) of the second user.
  • the first status data is based on an optical image or a depth image of the sender.
  • the first status data is based on (714) a detected expression (e.g., based on a facial map (e.g., description of various facial features)) of the second user at the time the second user composed and/or sent the first message.
  • the second status data is based on (718) a detected expression (e.g., based on a facial map (e.g., description of various facial features)) of the second user at the time the second user composed and/or sent the second message.
  • a detected expression e.g., based on a facial map (e.g., description of various facial features)
  • biometric characteristics or image data of the second user to generate the first status data
  • the messaging interface is enhanced by minimizing the burden on the second user to determine and/or enter status data.
  • the electronic device provides for an improved man-machine interface, which makes the electronic device more efficient, reduces power usage, and improves battery life.
  • the electronic device selects (e.g., choosing a predefined avatar or generating a new avatar) one or more characteristics (e.g., eyes, mouth, and eyebrows for a sad expression of avatars 629 or 638) (e.g., an expression or accessory) for the first avatar based on the first status data.
  • the electronic device selects (e.g., chooses an existing avatar or generating a new avatar) one or more characteristics for the second avatar based on the second status data, wherein the second status data is based on a second biometric characteristic (e.g., depth information, facial recognition, heart rate, etc.).
  • a second biometric characteristic e.g., depth information, facial recognition, heart rate, etc.
  • the first status data represents an emotion (e.g., happy, sad, smiling, etc.) of the second user.
  • an emotion e.g., happy, sad, smiling, etc.
  • the electronic device By selecting characteristics for an avatar instead of selecting an entire avatar, the electronic device more efficiently generates new avatars based on the status by only modifying the subset of characteristics that are relevant to a particular status. Thus, the electronic device is more efficient, uses less power, and has longer battery life by limiting the processing power necessary to generate the avatars.
  • the first avatar is an animated avatar (e.g., 629 or 638) (e.g., a Quicktime-based avatar, a GIF Avatar, etc. based on a series of recorded expressions).
  • animated avatar e.g., 629 or 638
  • the range and granularity of statuses that of the first avatar can represent is increased, thereby making for a more efficient first avatar and messaging interface.
  • the electronic device receives, from the first user and on the electronic device, third content (e.g., content in text box 626 of FIGs. 6G and 6H) for a third message (e.g., a message 626 replying the second user's first message 624).
  • the electronic device generates third status data for the first user and associates the third status data with the third message (e.g., sending them together or cross- referencing the message and the status data).
  • the electronic device sends the third message to the second user sending the third status data to the second user.
  • the electronic device concurrently displays on the display the third message including the third content (e.g., content in text box 626 of FIGs.
  • the operability of the electronic device is enhanced by increasing the amount of information presented on the display. For example, users can quickly scan messages and determine some context associated with the messages based on the avatars without having to read the text content of the message. This improved operability of the electronic device makes it more efficient, reduces power usage, and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
  • the different avatars for different messages can help when a user is trying to find a particular message that the user knows to be associated with a particular status (e.g., a sad message, in some instances, will have a sad avatar).
  • a message-specific avatar may help the reader accurate interpret the meaning of the message.
  • displaying the first message and the first avatar includes displaying the first message as a text bubble (e.g., 624) coming from a mouth of the first avatar. Displaying the first message coming from a mouth of the first avatar enables the association between the first avatar and the first message to be clear, even with minimal review of the messaging interface.
  • FIG. 8 shows an exemplary functional block diagram of an electronic device 800 configured in accordance with the principles of the various described embodiments.
  • the functional blocks of electronic device 800 are configured to perform the techniques described above.
  • the functional blocks of the device 800 are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 8 are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.
  • an electronic device 800 includes a display unit 802 and a processing unit 804 coupled to the display unit 802.
  • the processing unit 804 includes a receiving unit 806, a display enabling unit 808, generating unit 810, selecting unit 812, mapping unit 814, associating unit 816, and sending unit 818.
  • the processing unit 804 is configured to: receive (e.g., using receiving unit 806) a first message from a second user, wherein the first message includes first content; receive (e.g., using receiving unit 806) first status data for the second user, wherein the first status data is associated with the first message and separate from the first content; enable display (e.g., using display enabling unit 808) concurrently, on the display, the first message, including the first content, and a first avatar, wherein the first avatar is based on the first status data and the displayed first avatar is adjacent to the displayed first message; after displaying the first message and the first avatar, receive (e.g., using receiving unit 806) a second message from the second user, wherein the second message includes second content; receive (e.g., using receiving unit 806) second status data for the second user, wherein the second status is associated with the second message and separate from the second content; and while maintaining the display of the first message and the first avatar, display (e.g., using display enabling unit 808), on the first message
  • the processing unit 804 is further configured to display (e.g., using display enabling unit 808) contact information for a set of users that includes contact information for the second user, wherein the second avatar is displayed with the contact information for the second user.
  • the processing unit 804 is further configured to: receive (e.g., using receiving unit 806) a first avatar model for the second user; and generate (e.g., using generating unit 810) the first avatar based on the first avatar model and first status data; and generating the second avatar based on the first avatar model and the second status data.
  • the processing unit 804 is further configured to: receive (e.g., using receiving unit 806) a second avatar model for the second user; generate (e.g., using generating unit 810)an updated first avatar based on the second avatar model and first status data; generate (e.g., using generating unit 810) an updated second avatar based on the second avatar model and the second status data; and display (e.g., using display enabling unit 808) the updated first avatar instead of the first avatar with the first message including the first content.
  • the first status data is based on a first biometric characteristic of the second user.
  • the processing unit 804 is further configured to select (e.g., using selectin unit 812) one or more characteristics for the first avatar based on the first status data.
  • the processing unit 804 is further configured to select (e.g., using selecting unit 812) one or more characteristics for the second avatar based on the second status data, wherein the second status data is based on a second biometric
  • the first avatar is an animated avatar.
  • the first status data is based on an optical image or a depth image of the second user.
  • the processing unit 804 is further configured to map (e.g., using mapping unit 814) the first status data on to a predefined avatar model to create the first avatar.
  • the first status data represents an emotion of the second user.
  • the first status data is based on a detected expression of the second user at the time the second user composed and/or sent the first message.
  • the second status data is based on a detected expression of the second user at the time the second user composed and/or sent the second message.
  • the processing unit 804 is further configured to: receive (e.g., using receiving unit 806), from the first user and on the electronic device, third content for a third message; generate (e.g., using generating unit 810) third status data for the first user; associate (e.g., using associating unit 816) the third status data with the third message; send (e.g., using sending unit 818) the third message to the second user; and send (e.g., using sending unit 818) the third status data to the second user.
  • the processing unit 804 is further configured to concurrently display (e.g., using display enabling unit 808) the third message including the third content and a third avatar, wherein the third avatar is based on the third status data, and the third message and third avatar are displayed concurrently with the second message and second avatar.
  • the first avatar and second avatar represent the physical appearance of the second user.
  • display of the first message and the first avatar includes displaying the first message as a text bubble coming from a mouth of the first avatar.
  • the second user is associated with a source electronic device that sends the first message and the second message.
  • FIGs. 9A-9K illustrate exemplary user interfaces for capturing data for building 3D models, in accordance with some embodiments.
  • the user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGs. 10A-10B.
  • FIG. 9A depicts device 900, which in some examples is a specific form factor for device 100, device 300, or device 500 described above.
  • Device 900 includes display 901, which in some examples is a touch-sensitive display, and image sensor 902. Additionally, in some embodiments of device 900, additional sensors (e.g., depth sensors, IR sensors, etc.) and/or other components (e.g., flash or IR emitter) are present along with image sensor 902.
  • additional sensors e.g., depth sensors, IR sensors, etc.
  • other components e.g., flash or IR emitter
  • display 901 is displaying a scanning interface 903 of a scanning program, which includes instructions for how to proceed, and an image data area 904 that depicts the data that has been captured so far for the 3D model.
  • Image data area 904 includes add data button 905.
  • FIG. 9B depicts device 900 from the opposite side as depicted in FIG. 9A. On this side of device 900, image sensor 906, light sensor 907, and flash 908 are present.
  • Image sensor 906, in some examples, is a high quality visible light sensor. Optionally, it also captures other types of light, such as IR. Image sensor 906, optionally, also is configured to capture depth information using time of flight or other techniques.
  • Light sensor 907 in some examples, is used to determine lighting characteristics, which can be used to properly configure and operate image sensor 906. Flash 908 provides a visible light flash for image sensor 906. Flash 908, in some examples, is also configured based on data measured from light sensor 907.
  • other components e.g., an additional image sensor, an IR detector, an IR emitter, etc. are also present in some embodiments.
  • FIG. 9C depicts scanning interface 903 after add data button 905 (FIG. 9A) has been selected via, for example, touch 909 on display 901.
  • scanning interface 903 includes instructions 910 for selecting one of four affordances (affordances 911-914) for determining how data is to be added.
  • Affordance 911 allows a user to select image data that is already stored on device 900.
  • Affordance 912 allows a user to select image data that is already present on a remote device (e.g., doing an Internet search, accessing a particular remote server, or selecting from a particular remote device).
  • Affordance 913 allows a user to capture new data using, for example, image sensor 902 or image sensor 906 (FIG. 9C).
  • Affordance 914 returns the user to the state of the interface depicted in FIG. 9A.
  • FIG. 9D depicts scanning interface 903 after affordance 913 (FIG. 9C) has been selected, for example, via touch 915 on display 901.
  • scanning interface 903 provides four affordances (916-919) for selecting the type of image data to capture.
  • Affordance 916 selects a still image.
  • Affordance 917 selects video image data.
  • Affordance 918 selects panorama image data.
  • Affordance 919 returns the scanning interface to the state depicted in FIG. 9C.
  • FIG. 9E depicts scanning interface 903 after affordance 916 (FIG. 9D) has been selected, for example, via touch 920 on display 901.
  • a capture interface is displayed on display 901 to capture a portion of scene 920 using image sensor 906 (FIG. 9B).
  • View finder 921 represents the current field of view of image sensor 906 (FIG. 9B).
  • Home button 922 of device 900 in this example, is used to capture the image data in view finder 921.
  • the image data represented by the data displayed in view finder 921 is captured and saved to device 900.
  • FIG. 9F depicts scanning interface 903 after the image data depicted in FIG. 9E was captured. Representation 924 of the image data captured as described with respect to FIG. 9E is now present in image data area 904. In FIG. 9F, scanning interface 903 has already been returned to the photo capture state via the process described with respect to FIGs. 9A and 9C-9D.
  • Device 900 has moved with respect to the target as compared to FIG. 9E.
  • Display 901 shows view finder 921 is pointed at a portion of scene 925, which is of the same target but a different angle as compared to scene 920 (FIG. 9E).
  • Home button 922 is used to capture image data represented in view finder 921.
  • FIG. 9G depicts scanning interface 903 after image data represented by representation 926 has been captured. Based on the image data represented by
  • the scanning program takes various factors into account when determining an appropriate algorithm.
  • the type of image data e.g., still image versus video versus panorama
  • the orientation and/or location that device 900 was in when the image data was captured is a factor.
  • Other factors, such as whether the image data includes depth information and the amount of image data are also considered in various embodiments.
  • FIG. 9G also includes 3D model preview area 927 that includes model preview 928, which may be manipulated to be viewed from different angles and perspectives. For example, in response to touch and drag 929 on display 901, model preview 928 is rotated as depicted in FIG.9H, which shows that model preview 928 is not complete due to incomplete image data capture. In some embodiments, to complete the model, the user selects add data button 905 to add additional image data.
  • FIG. 91 depicts scanning interface 903 after selection of add data button 905 in FIG. 9H.
  • device 900 has determined that based on the still image data captured so far, a still image algorithm is best suited to build the model.
  • scanning interface 903 is displaying instructions 929 to the user to obtain additional image data of the type that will be most useful in building the model.
  • scanning interface 903 provides instructions and/or suggestion to obtain video data or panorama data image data instead.
  • Scanning interface 903, optionally, also provides instructions for how to position device 900 to obtain the most useful image data. The same capture options as described with respect to FIG. 9C are also displayed.
  • Remote selection interface 931 includes representations 932-934 that depict image data that is available from a remote location.
  • the representations 932-934 are determined to represent image data that is potentially relevant to the model that is currently being built.
  • device 900 optionally transmits its location to a remote server that uses the location to determine other image data captured in the same approximate location.
  • device 900 optionally transmits some or all of the image data that has already been captured.
  • a remote server then performs image recognition to determine other image data that is potentially relevant.
  • a standard Internet search is performed using search criteria provided by the user.
  • remote selection interface 931 is implemented as a web browser interface displaying the results of an Internet search.
  • selection interface 931 a swipe gesture on the interface will allow a user to scroll through additional image data that is available.
  • device 900 retrieves the respective image data and adds it to the available image data for building the model, as indicated by representation 935 in FIG. 9K.
  • model preview 936 has been updated with a new model, model preview 936 that is based on the available image data.
  • FIG. 9L depicts model preview 936 after the user has rotated the model, for example, via a touch on display 901 as described above with respect to FIGs. 9G and 9H.
  • model preview 936 is built using a different algorithm than device 900, via the scanning program, selected earlier with respect to FIG. 9G.
  • FIGs. 10A-10B is a flow diagram illustrating a method for building a 3D model of an object using an electronic device in accordance with some embodiments.
  • Method 1000 is performed at a device (e.g., 100, 300, 500) with a display and one or more image sensors. Some operations in method 1000 are, optionally, combined, the order of some operations are, optionally, changed, and some operations are, optionally, omitted.
  • method 1000 provides an intuitive way for building a 3D model of an object.
  • the method reduces the cognitive burden on a user for building a 3D model of an object, thereby creating a more efficient human-machine interface.
  • An electronic device e.g., 900 with one or more image sensors (e.g., 902, 906), memory, and a display (e.g, 901) captures (1002) first image data (e.g., 921, 904) (e.g., still or video with optical data, depth data, etc. and, optionally, position data) from one or more image sensors (e.g., 902, 906) (e.g., depth sensor, light sensor, IR sensor) of the electronic device.
  • the first image data includes first optical image data of an object (e.g., 920) from a first perspective (e.g., FIG. 9E).
  • the electronic device also captures (1004) second image data (e.g., 921, 926) from the one or more image sensors (e.g., 921, 904) (e.g., depth sensor, light sensor) of the electronic device, wherein the second image data includes second optical image light data of the object from a second perspective (e.g., FIG. 9F) that is different from the first perspective.
  • second image data e.g., 921, 926
  • the one or more image sensors e.g., 921, 904
  • the second image data includes second optical image light data of the object from a second perspective (e.g., FIG. 9F) that is different from the first perspective.
  • the electronic device selects (1006) an algorithm (e.g., algorithm that stiches different captures, algorithm that uses panning data) based on the change in perspective from the first perspective to the second perspective and based on the algorithm, determines additional image data (e.g., FIG. 91) that is needed to continue the 3D modeling of the object.
  • an algorithm e.g., algorithm that stiches different captures, algorithm that uses panning data
  • the electronic device displays (1010), on the display, visual feedback (929) that provides instructions for capturing the additional image data determined based on the selected algorithm.
  • visual feedback 929) that provides instructions for capturing the additional image data determined based on the selected algorithm.
  • the electronic device is enhanced to reduce the cognitive burden on the user to determine what further image data (e.g., types of image data and locations of image data) is needed. This increases the likelihood that a user will be successful in creating an accurate model.
  • the electronic device receives (1018) third data (e.g., 935) (e.g., from the image sensors or a remote server).
  • the third data includes third optical image data of the object from a third perspective.
  • the electronic device selects (1020) an updated algorithm (e.g., algorithm that stiches different captures, algorithm that uses panning data) based on the third perspective.
  • the updated algorithm is different than the algorithm.
  • the electronic device determines (1022) updated additional image data that is needed to continue the 3D modeling of the object, wherein the updated additional image data is different than the additional image data.
  • the electronic device displays (1024), on the display, visual feedback that provides updated instructions for capturing the updated additional image data, wherein the update instructions are different than the instructions displayed prior to selecting the update algorithm.
  • the electronic device's ability to build a model is enhanced by adjusting how the model will be built based on the image data that is available.
  • the electronic device's building of the model based on an algorithm based on the captured image data is more efficient, uses less power, and improves battery life.
  • the electronic device builds a 3D model (e.g., 936) of the object based on the first image data (e.g., 924), the second image data (e.g., 926), and the third image (e.g., 935) data using the selected updated algorithm.
  • a 3D model e.g., 936 of the object based on the first image data (e.g., 924), the second image data (e.g., 926), and the third image (e.g., 935) data using the selected updated algorithm.
  • the electronic device sends at least a portion of the first image data (e.g., 924) (e.g., position data) to a remote server and receives an indication from the remote server that the third data (e.g., 932) is available for the object (e.g., FIG. 9J).
  • the third data is from the data available from other users.
  • displaying, on the display, visual feedback that provides updated instructions for capturing the updated additional image data includes: the electronic device, in accordance with a determination that a first algorithm has been selected, displays (1014) a first set of instructions (e.g., 929) and in accordance with a determination that a second algorithm, different from the first algorithm, has been selected, the visual feedback includes (1016) a second set of instructions different than the first set of instructions (e.g., prompting the user to slide the camera horizontally rather than rotating the camera around a fixed point or taking still images of an object).
  • a first set of instructions e.g., 929
  • the visual feedback includes (1016) a second set of instructions different than the first set of instructions (e.g., prompting the user to slide the camera horizontally rather than rotating the camera around a fixed point or taking still images of an object).
  • the first image data includes (1012) first depth image data of the object from a first perspective.
  • the electronic device obtains (e.g., from a sensor or the image data) first position data (e.g., GPS, tilt, orientation data) for the first perspective (e.g., perspective of FIG. 9E) (e.g., orientation or relative position).
  • first position data e.g., GPS, tilt, orientation data
  • first perspective e.g., perspective of FIG. 9E
  • orientation or relative position e.g., orientation or relative position
  • selecting the algorithm is also based on the first position data.
  • the electronic device captures second position data (e.g., GPS, tilt, orientation data) for the second perspective (e.g., perspective of FIG. 9F) (e.g., orientation or relative position), wherein the second image data includes second depth image data of the object from the second perspective and selecting the algorithm is also based on the second position data.
  • second position data e.g., GPS, tilt, orientation data
  • the second perspective e.g., perspective of FIG. 9F
  • the second image data includes second depth image data of the object from the second perspective and selecting the algorithm is also based on the second position data.
  • the electronic device builds a 3D model (e.g., 936) of the object based on the first image data (e.g., 924), the second image data (e.g., 926), and the additional image data (e.g., 935) using the selected algorithm and stores, in the memory, the 3D model.
  • a 3D model e.g., 936 of the object based on the first image data (e.g., 924), the second image data (e.g., 926), and the additional image data (e.g., 935) using the selected algorithm and stores, in the memory, the 3D model.
  • a graphical representation of the 3D model (e.g., 936) is displayed to the user (e.g., a partially generated 3D model is displayed to the user while the user is scanning the object to help the user complete scanning the object and/or a completed 3D model is displayed to the user after the user has finished scanning the object optionally in response to a detected request to display the model such as activation of a displayed affordance to display the 3D model).
  • selecting the algorithm includes selecting a scan-based algorithm based on the change from the first perspective to the second perspective indicating that the first image data and the second image data are from a scan of the object.
  • selecting the algorithm includes selecting a discrete-image-based algorithm based on the change from the first perspective to the second perspective indicating that the first perspective and the second perspective are for discrete images (e.g., the perspectives shown in FIGs. 9E and 9F).
  • the electronic device identifies a support (e.g., a hand or a table) in the first image data that is touching the object and builds a 3D model of the object based on the first image data and the second image data using the selected algorithm.
  • the 3D model does not include the support touching the first object (e.g., the 3D model is generated at least in part by excluding detected points that are determined to be a part of the support rather than part of the first object).
  • the electronic device is enhanced to be capable of producing a model that is more useful to a user by not including extraneous detail that is not relevant to the user.
  • the user is not required to manually remove the support later, which makes the electronic device more efficient, use less power, and have longer battery life.
  • the electronic device displays on a display of the electronic device a first window that includes a live image of the object (e.g., 921) and displays on the display a second window that includes an image of a model (e.g., 927) (e.g., either full or partial) of the object, wherein the model is based on the first image data and the second image data.
  • the image of the model of the object is updated as additional images are captured and the model of the object is improved. This feedback enables the user to more accurately scan the object by providing real-time feedback to the user as to the progress of the scan and the type of movement of the device that is likely, at least in some cases, to improve the quality of the scan, which results in a more accurate model.
  • FIG. 11 shows an exemplary functional block diagram of an electronic device 1100 configured in accordance with the principles of the various described embodiments.
  • the functional blocks of electronic device 1100 are configured to perform the techniques described above.
  • the functional blocks of the device 1100 are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 11 are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.
  • an electronic device 1100 includes a display unit 1102 and a processing unit 1104 coupled to the display unit 1102.
  • the processing unit 1104 includes a capturing unit 1106, selecting enabling unit 1108, determining unit 1110, display enabling unit 1112, receiving unit 1114, building unit 1116, sending unit 1118, obtaining unit 1022, storing unit 1124, and identifying unit 1126.
  • the processing unit 1104 is configured to: capture (e.g., using capturing unit 1006) first image data from one or more image sensors of the electronic device, wherein the first image data includes first optical image data of an object from a first perspective;
  • capture e.g., using capturing unit 1106
  • second image data includes second optical image light data of the object from a second perspective that is different from the first perspective
  • select e.g., using selecting unit 1108
  • an algorithm based on the change in perspective from the first perspective to the second perspective
  • determine e.g., using determining unit 1110
  • additional image data that is needed to continue the 3D modeling of the object
  • display e.g., using display enabling unit 1112
  • the processing unit 1104 is further configured to: receive (e.g., using receiving unit 1114) third data, wherein the third data includes third optical image data of the object from a third perspective; select (e.g., using selecting unit 1108) an updated algorithm based on the third perspective, wherein the updated algorithm is different than the algorithm; based on the updated algorithm, determine (e.g., using determining unit 1110) updated additional image data that is needed to continue the 3D modeling of the object, wherein the updated additional image data is different than the additional image data; and display (e.g., using display enabling unit 1112), on the display, visual feedback that provides updated instructions for capturing the updated additional image data, wherein the update instructions are different than the instructions displayed prior to selecting the update algorithm.
  • the processing unit 1104 is further configured to build (e.g., using building unit 1116) a 3D model of the object based on the first image data, the second image data, the third image data, and the updated additional image data using the selected updated algorithm.
  • the processing unit 1104 is further configured to send (e.g., using sending unit 1118) at least a portion of the first image data to a remote server; and receive (e.g., using receiving unit 1114) an indication from the remote server that the third data is available for the object.
  • display, on the display, of visual feedback that provides updated instructions for capturing the updated additional image data includes: in accordance with a determination that a first algorithm has been selected, display of a first set of instructions; and in accordance with a determination that a second algorithm, different from the first algorithm, has been selected, the visual feedback includes a second set of instructions different than the first set of instructions.
  • the first image data includes first depth image data of the object from the first perspective.
  • the processing unit 1104 is further configured to obtain (e.g., using obtaining unit 1122) first position data for the first perspective.
  • selecting the algorithm is also based on the first position data.
  • the processing unit 1104 is further configured to capture (e.g., using capturing unit 1106) second position data for the second perspective, wherein the second image data includes second depth image data of the object from the second perspective and selecting the algorithm is also based on the second position data.
  • the processing unit 1104 is further configured to build (e.g., using building unit 1116) a 3D model of the object based on the first image data, the second image data, and the additional image data using the selected algorithm; and store (e.g., using storing unit 1124), in the memory, the 3D model.
  • selecting the algorithm includes selecting a scan-based algorithm based on the change from the first perspective to the second perspective indicating that the first image data and the second image data are from a scan of the object.
  • selecting the algorithm includes selecting a discrete- image -based algorithm based on the change from the first perspective to the second perspective indicating that the first perspective and the second perspective are for discrete images.
  • the processing unit 1104 is further configured to identify (e.g., using identifying unit 1126) a support in the first image data that is touching the object; and build (e.g., using building unit 1116) a 3D model of the object based on the first image data and the second image data using the selected algorithm, wherein the 3D model does not include the support touching the first object.
  • the processing unit 1104 is further configured to display (e.g., using display enabling unit 1112) on a display of the electronic device a first window that includes a live image of the object; and display (e.g., using display enabling unit 1112) on the display a second window that includes an image of a model of the object, wherein the model is based on the first image data and the second image data.
  • FIGs. 12A-12J illustrate exemplary user interfaces for restricting access to data and applications based on the user, in accordance with some embodiments.
  • the user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGs. 13A-13B.
  • FIG. 12A depicts device 1200 having display 1201, image sensor 1202, and home button 1204.
  • display 1201 is a touch-sensitive display.
  • home button 1204 is a mechanical button separate from display 1201 and includes a fingerprint sensor for identifying a user that places a finger on home button 1204.
  • home button 1204 is integrated with display 1201 and still includes a fingerprint sensor.
  • device 1200 is displaying, on display 1201, lock screen interface 1203. Lock screen interface 1203 is displayed when device 1200 is in a locked stated with restricted functionality. For example, access to most applications on device 1200 and other functionality is not permitted when in the locked state.
  • some applications e.g., a camera application
  • functionality e.g., calling an emergency number
  • device 1200 is unlocked via the authentication of fingerprint data measured by the fingerprint sensor present in home button 1204.
  • device 1200 is unlocked via authentication of a pin code that is entered via a pin code interface (not shown).
  • image sensor 1202 is configured to capture image data of the user using device 1200. The image data is then processed in device 1200 and compared against image data or other data for authorized users. Device 1200 can also be unlocked if the image data allows for the user to be authenticated.
  • FIG. 12B depicts device 1200 displaying home screen interface 1205 after device 1200 has been unlocked, for example, using one of the techniques described with respect to FIG. 12A.
  • Home screen interface 1205 includes a plurality of icons for applications installed on device 1200, including a photo application associated with icon 1206.
  • the photo application is launched or, if the photo application has already been launched, the photo application is displayed.
  • FIG. 12C depicts device 1200 displaying the photo application, and more specifically, photo album interface 1208, which includes add button 1209, title 1210, search button 1211, and edit button 1212.
  • Selection of add button 1209 causes an add album interface to be displayed that enables creation of an additional photo album.
  • Title 1210 identifies the interface as the album interface.
  • Selection of search button 1210 causes a search interface to be displayed that enables searching of photos in the photo application.
  • Selection of edit button 1212 enables an album edit interface that enables deleting of albums or other functions.
  • Photo album interface 1208 also includes thumbnails 1213-1216 that each represents a respective photo album in the photo application.
  • each thumbnail is a smaller version of a photo that is present in that album.
  • Thumbnails 1213- 1216 are also selectable, for example, via a touch on display 1201.
  • FIG. 12D depicts the photo application after selection of thumbnail 1213 (FIG. 12C).
  • Photo selection interface 1217 is displayed, which includes back button 1218, title 1219, and select button 1220. Selection of back button 1218 returns the photo application to album interface 1208 (FIG. 12C).
  • Title 1219 identifies the current album that is displayed in photo selection interface 1217. Selection of select button 1220 allows the user to select multiple of the photos in the current album and perform an operation (e.g., deleting) on the selected photos.
  • Photo album interface 1217 also includes thumbnails 1221-1232 that each represents a respective photo in the album. In some examples, each thumbnail is a smaller version of the photo that is present in that album. Thumbnails 1221-1232 are also selectable, for example, via a touch on display 1201.
  • FIG. 12E depicts the photo application after selection of thumbnail 1227 (FIG. 12D).
  • Photo interface 1234 is displayed, which includes back button 1235, photo information 1236, and details button 1237. Selection of back button 1235 returns the photo application to photo selection interface 1217 (FIG. 12D).
  • Photo information 1235 provides information, such as location and time, related to the currently displayed photo (1238).
  • Selection of details button 1237 displays a details interface that provides additional information about the currently displayed photo (1238), such as related photos or people identified in the photo
  • Photo interface 1234 also includes display of the currently selected photo, photo 1238.
  • the interface also includes a preview area that includes thumbnail 1239 of photo 1238 and other reduced sized thumbnails 1240 representing some of the other photos in the album. If there is not sufficient room for all photos in the album to have a displayed thumbnail in the preview area, in some embodiments, a user can scroll through the thumbnails, for example, via a swipe gesture on display 1201 over the preview area.
  • the user of device 1200 can request the interface to navigate away from photo 1238 to the next photo in the album (e.g., photo represented by thumbnail 1228 of FIG. 12D).
  • the request to navigate away from the current photo in some examples, is a gesture on display 1201 received on the currently selected photo (e.g., photo 1238 in the case of FIG. 12E).
  • swipe gesture 1241 is received.
  • device 1200 captures image data using image sensor 1202. In other examples, the image data is captured prior to receiving a request to navigate away from the current photo.
  • device 1200 determines whether a set of content-lock criteria is met.
  • the set of content-lock criteria includes a criterion that is met if an unauthorized user is detected as using device 1200 based on analysis of the captured image.
  • other criteria are also used, such as detecting the absence of an authorized user (e.g., by analyzing the captured image data), the orientation or movement of the device (e.g., detection of a handoff of the device or that the device is laying flat), a time delay since an authorized user was last detected, and/or information associated with the content that is being displayed (e.g., sensitive or private content could have a stricter set of criteria).
  • photo interface 1234 transitions from photo 1238 to the next photo in the album, photo 1242. Additionally, thumbnail 1239 associated with photo 1238 shrinks as thumbnail 1243 associated with photo 1242 grows.
  • FIG. 12G depicts the completed navigation away from the previously selected content (photo 1238 in FIG. 12E) to the newly selected content (photo 1242).
  • the photo information for photo interface 1234 has been updated with photo information 1244 associated with photo 1242.
  • device 1200 has determined that the set of content-lock criteria has been met.
  • device 1200 In response to a request to navigate away from the currently selected content (photo 1238) via, for example, swipe gesture 1241 of FIG. 12E, device 1200 does not show the next photo in the album as was described with respect to FIGs. 12F and 12G. Additionally, the photo preview area with thumbnail 1239 is not updated in response to the request. In some embodiments the photo preview area is completely hidden.
  • photo 1238 returns to the center of display 1201, as depicted in FIG. 12E. The ability to navigate away from photo 1238 is permitted again once the set of content-lock criteria is no longer met.
  • a set of lock criteria is associated with a function of the device, such as the ability to exit an application, switch to another open application, or launch a new application. If this set of lock criteria is met, the associated function of the device is disabled.
  • a set of lock criteria is associated with a configuration of an application on the device, such as read-only configuration. If this set of lock criteria is met, the configuration of the application is switched (e.g., the application's functionality is restricted or the application is switched from a read/write configuration to a read-only configuration).
  • a set of lock criteria is associated with locking all other functionality of the device other than the current function (e.g., if the device is displaying a photo, that is the only function permitted on the device other than, perhaps, locking the device).
  • FIGs. 121 and 12J depict another example of an application of a set of lock criteria.
  • a communication has been received in the form of an iMessage message.
  • Device 1200 has determined that a set of lock criteria is not met.
  • Device 1200 thus displays notification 1245 to indicate that the communication was received and to preview the message content and sender.
  • device 1200 has determined that the same set of lock criteria is met.
  • This set of lock criteria is associated with whether to display notifications about communications or, alternatively, what kind of notification to display.
  • notification 1246 only indicates that a message or communication has been received without showing content of the message or who sent the message.
  • the display of a notification is suppressed entirely in response to lock criteria being met.
  • Restricted functionality and features of device 1200 and its applications are optionally restored when an associated set of lock criteria is no longer met.
  • the restricted functionality and features are also restored when the device is unlocked, for example, using a pin code or fingerprint identification.
  • FIGs. 13A-13B are a flow diagram illustrating a method for restricting access to data and applications based on the user using an electronic device in accordance with some embodiments.
  • Method 1300 is performed at a device (e.g., 100, 300, 500) with a display and an image sensor. Some operations in method 1300 are, optionally, combined, the order of some operations are, optionally, changed, and some operations are, optionally, omitted.
  • method 1300 provides an intuitive way for restricting access to data and applications based on the user using the device.
  • the method reduces the cognitive burden on a user for restricting access to data and applications based on the user using the device, thereby creating a more efficient human-machine interface.
  • enabling a user to restrict access to data and applications based on the user using the device faster and more efficiently conserves power and increases the time between battery charges.
  • An electronic device e.g., 1200 with a display (e.g., 1201) and one or more image sensors (e.g., 1202) displays, on the display, content (e.g., 1238) (e.g., a photo) in an application (e.g., Photos, photo sharing application, messaging application).
  • the electronic device displays (1302) the content while the application is in a first configuration (e.g., a normal configuration). While displaying the content, the electronic device captures (1304) image data (e.g., image and/or depth information) from the one or more image sensors (e.g., 1202) of the electronic device.
  • image data e.g., image and/or depth information
  • the electronic device After capturing the image data, the electronic device receives (1306) a request e.g., (e.g., 1241) to navigate away from the content.
  • a request to navigate away from the content e.g., swiping to a different photo or going to a different webpage
  • the electronic device in accordance with a determination that a first set of content-lock criteria have been met, prevents (1310) navigation away (e.g., FIG.
  • the first set of content-lock criteria includes a first criterion that is met when the captured image data indicates that an unauthorized user is using the device; and in accordance with a
  • the security of the electronic device is enhanced by preventing access to other content while still enabling view of content that an authorized user intends to allow access to (e.g., preventing access to other photos when an authorized user is not using the device).
  • the electronic device navigating away from the content includes translating currently displayed content (e.g., scrolling a map or a list in response to a scroll input such as a drag gesture on a touch- sensitive surface).
  • the electronic device navigating away from the content includes switching between content items (e.g., 1238 and 1242) in an application (e.g., FIG. 12F) (e.g., switching through pages in a book or pdf, pictures in a camera roll, webpages in a browser based on a next content item input such as a swipe gesture on a touch-sensitive surface).
  • the electronic device in accordance with a determination that the first set of content-lock criteria is no longer met, allows (1314) navigation away (e.g., FIGs. 12F-12G) (e.g., swiping to a different photo or going to a different webpage) from the content.
  • navigation away e.g., FIGs. 12F-12G
  • FIGs. 12F-12G e.g., swiping to a different photo or going to a different webpage
  • the first set of lock-criteria includes a second criterion that is met when the captured image data indicates that an authorized user of the electronic device is not using the device (e.g., a face of an authorized user is not detected in the field of view of the camera for more than a predetermined amount of time such as 1 second, 15 seconds, or 1 minute).
  • the first set of lock-criteria includes a third criterion that is met when the captured image data indicates that the unauthorized user is present and an authorized user is not present (e.g., a face of a user that is not recognized as an authorized user is detected in the field of view of the camera without a face of an authorized user being detected in the field of view of the camera).
  • the first set of lock-criteria is met when any of the included criterions are met. In some embodiments, the first set of lock-criteria is only met when all the include criterions are met.
  • the first set of lock-criteria is met when the captured image data indicates that the unauthorized user is present without regard to whether or not an authorized user is present (e.g., the first set of lock-criteria is met if the first criterion is met).
  • the electronic device determines whether the captured image data indicates the presence of an unauthorized user of the electronic device.
  • the electronic device in accordance with a determination that a second set of content- lock criteria has been met, disabling (1316) at least one function of the electronic device (FIGs. 121 and 12J) (e.g., suppressing the display of notifications).
  • the electronic device in accordance with the determination that a fourth set of (e.g., same or different as other sets) content-lock criteria have been met, locking (1320) other functionality (e.g., all other functionality except the sleep/wake button functionality) of the electronic device while continuing to display the content in the application.
  • preventing navigation between applications on the electronic device and in accordance with the fifth criterion being met preventing navigation within the application (e.g., transition from the photo view in FIG. 12E back to the album view in FIG. 12D).
  • the fourth criterion is met (and accordingly, the fifth set of lock-criteria) are met, a user press of the home button will not return the device to the home screen. Instead, either the application display remains or the device is locked and the lock interface (e.g., 1203) is displayed.
  • the fourth set of content-lock criteria is met when the image data indicate no authorized user is using the electronic device.
  • switching between applications and/or viewing notifications is disabled.
  • the security of the electronic device is enhanced by restricting access to certain functionality when the user is allowing others to view content on the electronic device. For example, if the user provides the electronic device to another person to view a displayed image and the electronic device receives a phone call, the electronic device can determine that the user (e.g., an authorized user) is not using the electronic device and prevent the phone call from being answered.
  • the first set of lock-criteria and the second set of lock-criteria are different (e.g., the first set of lock-criteria is met is the image data indicates an unauthorized user is using the electronic device regardless of whether an authorized user is present and the second set of lock-criteria is met if the image data indicates an authorized user is not using the electronic device, regardless of whether an unauthorized user is present).
  • the electronic device in accordance with a determination that a third set of content-lock criteria has been met, switching (1318) the application to a second configuration (e.g., FIG. 12G) that limits operation of the application as compared to the first configuration (e.g., FIG. 12F) (e.g., navigation is locked if an unauthorized user and authorized user present and the entire device is locked an
  • the electronic device in accordance with the determination that a fifth set (e.g., same or different as other sets) of content- lock criteria have been met, preventing (1322) the display of a notification related to a communication received at the electronic device (e.g., detecting a notification triggering condition, and in accordance with a determination that the content-lock criteria have been met, suppressing presentation of the notification / in accordance with a determination that the content-lock criteria have not been met, presenting the notification (e.g., via audible, tactile, or visual output)).
  • a notification related to a communication received at the electronic device e.g., detecting a notification triggering condition, and in accordance with a determination that the content-lock criteria have been met, suppressing presentation of the notification / in accordance with a determination that the content-lock criteria have not been met, presenting the notification (e.g., via audible, tactile, or visual output)).
  • the fifth set of lock-criteria includes a fourth criterion that is met when the captured image data indicates that an unauthorized user is using the electronic device and the fifth set of lock-criteria is met if the fourth criterion is met and the first set of lock-criteria includes a fifth criteria that is met when the captured image data indicates the absence of an authorized user.
  • the fourth criterion of the fifth set of lock-criteria is met when image data captured from the electronic device indicates that a user other than an authorized user is present in the captured image data (e.g., the image data indicates that an unauthorized user (with or without an authorized user) is within the field of view of a camera on the front of the electronic device).
  • the fifth set of lock-criteria is met as long as the fourth criterion is met regardless of whether other criterions in the fifth set of lock criteria are met (e.g., as long as an unauthorized user is present in the captured image data, no other criterion need to be met in order for the fifth set of lock-criteria to be met).
  • the image data includes optical data and depth data, and wherein determining whether the first set of content-lock criteria have been met is based on the optical data and the depth data.
  • the optical data is provided by a first camera with a first resolution and the depth data is provided by a second camera with a second resolution that is lower than the first resolution.
  • the depth data is generated by a combination of images from two cameras that are located a known distance apart. In some embodiments the depth data and the optical data are generated by the same camera.
  • the electronic device navigating away from the content includes switching applications or closing the application (e.g., the photo application of FIGs. 12C-12J) to display the home screen (e.g., 1205) (e.g., switching through applications in a multitasking mode triggered by repeated activation of a button such as a home button or exiting to an application launch user interface triggered by activation of a button such as a home button).
  • switching applications or closing the application e.g., the photo application of FIGs. 12C-12J
  • the home screen e.g., 1205
  • switching through applications in a multitasking mode triggered by repeated activation of a button such as a home button or exiting to an application launch user interface triggered by activation of a button such as a home button e.g., switching through applications in a multitasking mode triggered by repeated activation of a button such as a home button or exiting to an application launch user interface triggered by activation of a button such as a home button.
  • the electronic device receives unlock information (e.g., a pin code, a password, or biometric information, such as fingerprint information or iris information) associated with an authorized user of the electronic device; determines whether the unlock information is authentic; and in accordance with a determination that the unlock information is authentic, enables navigation away (e.g., FIG. 12F) (e.g., swiping to a different photo or going to a different webpage) from the content (e.g., 1238) (e.g., returning the electronic device to normal operation).
  • unlock information e.g., a pin code, a password, or biometric information, such as fingerprint information or iris information
  • FIG. 14 shows an exemplary functional block diagram of an electronic device 1400 configured in accordance with the principles of the various described embodiments.
  • the functional blocks of electronic device 1400 are configured to perform the techniques described above.
  • the functional blocks of the device 1400 are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 14 are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.
  • an electronic device 1400 includes a display unit 1402 and a processing unit 1404 coupled to the display unit 1402.
  • the processing unit 1404 includes a display enabling unit 1406, capturing unit 1408, receiving unit 1410, preventing unit 1412, navigating unit 1414, allowing unit 1416, disabling unit 1418, locking unit 1420, preventing unit 1422, determining unit 1424, switching unit 1126, and enabling unit 1128.
  • the processing unit configured to 1404 is configured to display (e.g., using display enabling unit 1406), on the display, content in an application, wherein the content is displayed while the application is in a first configuration; while displaying the content, capture (e.g., using capturing unit 1408) image data (from the one or more image sensors of the electronic device; after capturing the image data, receive (e.g., using receiving unit 1410) a request to navigate away from the content; and in response to receiving a request to navigate away from the content: in accordance with a determination that a first set of content-lock criteria have been met, prevent (e.g., using preventing unit 1412) navigation away from the content while maintaining display of the content, wherein the first set of content-lock criteria includes a first criterion that is met when the captured image data indicates that an unauthorized user is using the device; and in accordance with a
  • the processing unit 1404 is further configured to, in accordance with a determination that the first set of content-lock criteria is no longer met, allow (e.g., using allowing unit 1416) navigation away from the content.
  • the first set of lock-criteria includes a second criterion that is met when the captured image data indicates that an authorized user of the electronic device is not using the device.
  • the first set of lock-criteria includes a third criterion that is met when the captured image data indicates that the unauthorized user is present and an authorized user is not present.
  • the first set of lock-criteria is met when the captured image data indicates that the unauthorized user is present without regard to whether or not an authorized user is present.
  • the processing unit 1404 is further configured to in accordance with a determination that a second set of content-lock criteria has been met, disable (e.g., using disabling unit 1418) at least one function of the electronic device.
  • the first set of lock-criteria and the second set of lock- criteria are different.
  • processing unit 1404 is further configured to in accordance with a determination that a third set of content-lock criteria has been met, switch
  • the processing unit 1404 is further configured to in accordance with the determination that a fourth set of content-lock criteria have been met, lock (e.g., using locking unit 1420) other functionality of the electronic device while continuing to display the content in the application.
  • the processing unit 1404 is further configured to in accordance with the determination that a fifth set of content-lock criteria have been met, prevent (e.g., using preventing unit 1412) the display of a notification related to a communication received at the electronic device.
  • the fifth set of lock-criteria includes a fourth criterion that is met when the captured image data indicates that an unauthorized user is using the electronic device and the fifth set of lock-criteria is met if the fourth criterion is met; and the first set of lock-criteria includes a fifth criteria that is met when the captured image data indicates the absence of an authorized user.
  • the processing unit 1404 is further configured to in accordance with the fourth criterion being met, prevent (e.g., using preventing unit 1412) navigation between applications on the electronic device; and in accordance with the fifth criterion being met, prevent (e.g., using preventing unit 1412) navigation within the application.
  • the processing unit 1404 is further configured to determine (e.g., using determining unit 1124) whether the captured image data indicates the presence of an unauthorized user of the electronic device.
  • the image data includes optical data and depth data, and wherein determining whether the first set of content-lock criteria have been met is based on the optical data and the depth data.
  • navigating away from the content includes translating currently displayed content.
  • navigating away from the content includes switching between content items in an application.
  • navigating away from the content includes switching applications or closing the application to display the home screen.
  • the processing unit 1404 is further configured to receive (e.g., using receiving unit 1410) unlock information associated with an authorized user of the electronic device; determine (e.g., using determining unit 1124) whether the unlock information is authentic; and in accordance with a determination that the unlock information is authentic, enable (e.g., using enabling unit 1128) navigation away from the content.
  • receive e.g., using receiving unit 1410
  • determine e.g., using determining unit 1124
  • enable e.g., using enabling unit 1128
  • a method comprising:
  • the first message including the first content, and a first avatar, wherein the first avatar is based on the first status data and the displayed first avatar is adjacent to the displayed first message;
  • the display while maintaining the display of the first message and the first avatar, displaying, on the display, the second message, including the second content, and a second avatar, wherein the displayed second avatar is adjacent to the displayed second message, the second avatar is based on the second status data, and the first avatar and the second avatar are different.
  • the method of item 13 further comprising:
  • displaying the first message and the first avatar includes displaying the first message as a text bubble coming from a mouth of the first avatar.
  • the second user is associated with a source electronic device that sends the first message and the second message.
  • An electronic device comprising:
  • processors one or more processors
  • one or more programs wherein the one or more programs are stored in memory and configured to be executed by the one or more processors, the one or more programs including instructions for:
  • the first message including the first content, and a first avatar, wherein the first avatar is based on the first status data and the displayed first avatar is adjacent to the displayed first message;
  • the display while maintaining the display of the first message and the first avatar, displaying, on the display, the second message, including the second content, and a second avatar, wherein the displayed second avatar is adjacent to the displayed second message, the second avatar is based on the second status data, and the first avatar and the second avatar are different.
  • a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the device to: receive a first message from a second user, wherein the first message includes first content;
  • the display concurrently, on the display, the first message, including the first content, and a first avatar, wherein the first avatar is based on the first status data and the displayed first avatar is adjacent to the displayed first message;
  • the second message while maintaining the display of the first message and the first avatar, display, on the display, the second message, including the second content, and a second avatar, wherein the displayed second avatar is adjacent to the displayed second message, the second avatar is based on the second status data, and the first avatar and the second avatar are different.
  • An electronic device comprising:
  • An electronic device comprising:
  • processors one or more processors
  • one or more programs wherein the one or more programs are stored in memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods of items 1-18.
  • a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the device to perform any of the methods of items 1-18.
  • An electronic device comprising:
  • a method comprising:
  • first image data includes first optical image data of an object from a first perspective
  • second image data from the one or more image sensors of the electronic device, wherein the second image data includes second optical image light data of the object from a second perspective that is different from the first perspective
  • the method of item 25 further comprising:
  • the third data includes third optical image data of the object from a third perspective
  • the method of item 26 further comprising:
  • the visual feedback includes a second set of instructions different than the first set of instructions.
  • the second image data includes second depth image data of the object from the second perspective and selecting the algorithm is also based on the second position data.
  • selecting the algorithm includes selecting a scan- based algorithm based on the change from the first perspective to the second perspective indicating that the first image data and the second image data are from a scan of the object.
  • selecting the algorithm includes selecting a discrete- image -based algorithm based on the change from the first perspective to the second perspective indicating that the first perspective and the second perspective are for discrete images.
  • An electronic device comprising:
  • processors one or more processors
  • one or more programs wherein the one or more programs are stored in memory and configured to be executed by the one or more processors, the one or more programs including instructions for:
  • first image data includes first optical image data of an object from a first perspective
  • the second image data includes second optical image light data of the object from a second perspective that is different from the first perspective
  • a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the device to:
  • first image data includes first optical image data of an object from a first perspective
  • the second image data includes second optical image light data of the object from a second perspective that is different from the first perspective
  • An electronic device comprising:
  • first image data includes first optical image data of an object from a first perspective
  • An electronic device comprising:
  • processors one or more processors
  • one or more programs wherein the one or more programs are stored in memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods of items 25-38.
  • a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the device to perform any of the methods of items 25-38.
  • An electronic device comprising:
  • a method comprising:
  • the first set of content-lock criteria includes a first criterion that is met when the captured image data indicates that an unauthorized user is using the device;
  • the method of item 45 further comprising:
  • the first set of lock-criteria includes a second criterion that is met when the captured image data indicates that an authorized user of the electronic device is not using the device.
  • the first set of lock-criteria includes a third criterion that is met when the captured image data indicates that the unauthorized user is present and an authorized user is not present.
  • any of items 45-53 further comprising: in accordance with the determination that a fifth set of content-lock criteria have been met, preventing the display of a notification related to a communication received at the electronic device.
  • the fifth set of lock-criteria includes a fourth criterion that is met when the captured image data indicates that an unauthorized user is using the electronic device and the fifth set of lock-criteria is met if the fourth criterion is met;
  • the first set of lock-criteria includes a fifth criteria that is met when the captured image data indicates the absence of an authorized user.
  • the method of item 55 further comprising:
  • navigating away from the content includes translating currently displayed content.
  • navigating away from the content includes switching between content items in an application.
  • navigating away from the content includes switching applications or closing the application to display the home screen.
  • the method of any of items 45-61 further comprising:
  • An electronic device comprising:
  • processors one or more processors
  • one or more programs wherein the one or more programs are stored in memory and configured to be executed by the one or more processors, the one or more programs including instructions for:
  • the first set of content-lock criteria includes a first criterion that is met when the captured image data indicates that an unauthorized user is using the device;
  • a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the device to:
  • the first set of content-lock criteria includes a first criterion that is met when the captured image data indicates that an unauthorized user is using the device;
  • An electronic device comprising:
  • An electronic device comprising:
  • processors one or more processors
  • one or more programs wherein the one or more programs are stored in memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods of items 45-62.
  • a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the device to perform any of the methods of items 45-62.
  • An electronic device comprising:
  • this gathered data may include personal information data that uniquely identifies or can be used to communicate with or locate a specific person.
  • personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information.
  • the present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users.
  • the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.
  • the present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices.
  • such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure.
  • personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures.
  • the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data.
  • the present technology can be configured to allow users to select to "opt in” or "opt out" of participation in the collection of personal information data during registration for services.
  • users can select not to provide location information for targeted content delivery services.
  • users can select to not provide precise location information, but permit the transfer of location zone information.
  • the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data.
  • content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publically available information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

La présente invention concerne d'une manière générale l'utilisation d'avatars et de données d'image pour des interactions utilisateur améliorées. Dans certains exemples, des avatars dépendants de l'état de l'utilisateur sont générés et affichés avec un message associé à l'état de l'utilisateur. Dans certains exemples, un dispositif capture des informations d'image pour balayer un objet afin de créer un modèle 3D de l'objet. Le dispositif détermine un algorithme pour le modèle 3D sur la base des informations d'image de capture et fournit une rétroaction visuelle sur des données d'image supplémentaires qui sont nécessaires à l'algorithme pour construire le modèle 3D. Dans certains exemples, un fonctionnement d'application sur un dispositif est limité sur la base du fait qu'un utilisateur autorisé est identifié à l'aide du dispositif sur la base de données d'image capturées.
PCT/US2017/049760 2016-09-23 2017-08-31 Données d'image pour interactions utilisateur améliorées WO2018057268A1 (fr)

Priority Applications (9)

Application Number Priority Date Filing Date Title
KR1020197005136A KR102257353B1 (ko) 2016-09-23 2017-08-31 향상된 사용자 상호작용들에 대한 이미지 데이터
KR1020217015473A KR102403090B1 (ko) 2016-09-23 2017-08-31 향상된 사용자 상호작용들에 대한 이미지 데이터
EP21166287.9A EP3920052A1 (fr) 2016-09-23 2017-08-31 Données d'image pour interactions utilisateur améliorées
JP2019511975A JP6824552B2 (ja) 2016-09-23 2017-08-31 拡張されたユーザ対話のための画像データ
AU2017330208A AU2017330208B2 (en) 2016-09-23 2017-08-31 Image data for enhanced user interactions
EP17853654.6A EP3485392B1 (fr) 2016-09-23 2017-08-31 Données d'image pour interactions utilisateur améliorées
CN201780053143.0A CN109691074A (zh) 2016-09-23 2017-08-31 用于增强的用户交互的图像数据
AU2020201721A AU2020201721B2 (en) 2016-09-23 2020-03-09 Image data for enhanced user interactions
AU2021250944A AU2021250944B2 (en) 2016-09-23 2021-10-15 Image data for enhanced user interactions

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201662399226P 2016-09-23 2016-09-23
US62/399,226 2016-09-23
DKPA201770418 2017-05-31
DKPA201770418A DK179978B1 (en) 2016-09-23 2017-05-31 IMAGE DATA FOR ENHANCED USER INTERACTIONS

Publications (2)

Publication Number Publication Date
WO2018057268A1 true WO2018057268A1 (fr) 2018-03-29
WO2018057268A4 WO2018057268A4 (fr) 2018-05-31

Family

ID=61689723

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/049760 WO2018057268A1 (fr) 2016-09-23 2017-08-31 Données d'image pour interactions utilisateur améliorées

Country Status (1)

Country Link
WO (1) WO2018057268A1 (fr)

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020113843A (ja) * 2019-01-09 2020-07-27 凸版印刷株式会社 画像撮像支援装置及び画像撮像支援方法
US11039074B1 (en) 2020-06-01 2021-06-15 Apple Inc. User interfaces for managing media
US11102414B2 (en) 2015-04-23 2021-08-24 Apple Inc. Digital viewfinder user interface for multiple cameras
US11112964B2 (en) 2018-02-09 2021-09-07 Apple Inc. Media capture lock affordance for graphical user interface
US11128792B2 (en) 2018-09-28 2021-09-21 Apple Inc. Capturing and displaying images with multiple focal planes
US11165949B2 (en) 2016-06-12 2021-11-02 Apple Inc. User interface for capturing photos with different camera magnifications
US11178335B2 (en) 2018-05-07 2021-11-16 Apple Inc. Creative camera
US11204692B2 (en) 2017-06-04 2021-12-21 Apple Inc. User interface camera effects
US11212449B1 (en) 2020-09-25 2021-12-28 Apple Inc. User interfaces for media capture and management
US11223771B2 (en) 2019-05-06 2022-01-11 Apple Inc. User interfaces for capturing and managing visual media
US11321857B2 (en) 2018-09-28 2022-05-03 Apple Inc. Displaying and editing images with depth information
US11350026B1 (en) 2021-04-30 2022-05-31 Apple Inc. User interfaces for altering visual media
US11468625B2 (en) 2018-09-11 2022-10-11 Apple Inc. User interfaces for simulated depth effects
US11706521B2 (en) 2019-05-06 2023-07-18 Apple Inc. User interfaces for capturing and managing visual media
US11722764B2 (en) 2018-05-07 2023-08-08 Apple Inc. Creative camera
US11770601B2 (en) 2019-05-06 2023-09-26 Apple Inc. User interfaces for capturing and managing visual media
US11778339B2 (en) 2021-04-30 2023-10-03 Apple Inc. User interfaces for altering visual media
US12112024B2 (en) 2021-06-01 2024-10-08 Apple Inc. User interfaces for managing media styles

Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3859005A (en) 1973-08-13 1975-01-07 Albert L Huebner Erosion reduction in wet turbines
US4826405A (en) 1985-10-15 1989-05-02 Aeroquip Corporation Fan blade fabrication system
US6323846B1 (en) 1998-01-26 2001-11-27 University Of Delaware Method and apparatus for integrating manual input
US6570557B1 (en) 2001-02-10 2003-05-27 Finger Works, Inc. Multi-touch system and method for emulating modifier keys via fingertip chords
US6677932B1 (en) 2001-01-28 2004-01-13 Finger Works, Inc. System and method for recognizing touch typing under limited tactile feedback conditions
US20050190059A1 (en) 2004-03-01 2005-09-01 Apple Computer, Inc. Acceleration-based theft detection system for portable electronic devices
US20060017692A1 (en) 2000-10-02 2006-01-26 Wehrenberg Paul J Methods and apparatuses for operating a portable device based on an accelerometer
US20090175509A1 (en) 2008-01-03 2009-07-09 Apple Inc. Personal computing device control using face detection and recognition
US7657849B2 (en) 2005-12-23 2010-02-02 Apple Inc. Unlocking a device by performing gestures on an unlock image
WO2013169849A2 (fr) 2012-05-09 2013-11-14 Industries Llc Yknots Dispositif, procédé et interface utilisateur graphique permettant d'afficher des objets d'interface utilisateur correspondant à une application
US20140013422A1 (en) 2012-07-03 2014-01-09 Scott Janus Continuous Multi-factor Authentication
EP2713298A1 (fr) 2012-09-27 2014-04-02 LG Electronics, Inc. Appareil d'affichage et son procédé de fonctionnement
US20140143693A1 (en) * 2010-06-01 2014-05-22 Apple Inc. Avatars Reflecting User States
US20140157153A1 (en) * 2012-12-05 2014-06-05 Jenny Yuen Select User Avatar on Detected Emotion
WO2014105276A1 (fr) 2012-12-29 2014-07-03 Yknots Industries Llc Dispositif, procédé et interface utilisateur graphique pour effectuer une transition entre des relations d'entrée tactile et de sortie d'affichage
WO2015196448A1 (fr) 2014-06-27 2015-12-30 Microsoft Technology Licensing, Llc Protection de données reposant sur une reconnaissance d'utilisateur et de geste

Patent Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3859005A (en) 1973-08-13 1975-01-07 Albert L Huebner Erosion reduction in wet turbines
US4826405A (en) 1985-10-15 1989-05-02 Aeroquip Corporation Fan blade fabrication system
US6323846B1 (en) 1998-01-26 2001-11-27 University Of Delaware Method and apparatus for integrating manual input
US20020015024A1 (en) 1998-01-26 2002-02-07 University Of Delaware Method and apparatus for integrating manual input
US20060017692A1 (en) 2000-10-02 2006-01-26 Wehrenberg Paul J Methods and apparatuses for operating a portable device based on an accelerometer
US6677932B1 (en) 2001-01-28 2004-01-13 Finger Works, Inc. System and method for recognizing touch typing under limited tactile feedback conditions
US6570557B1 (en) 2001-02-10 2003-05-27 Finger Works, Inc. Multi-touch system and method for emulating modifier keys via fingertip chords
US20050190059A1 (en) 2004-03-01 2005-09-01 Apple Computer, Inc. Acceleration-based theft detection system for portable electronic devices
US7657849B2 (en) 2005-12-23 2010-02-02 Apple Inc. Unlocking a device by performing gestures on an unlock image
US20090175509A1 (en) 2008-01-03 2009-07-09 Apple Inc. Personal computing device control using face detection and recognition
US20140143693A1 (en) * 2010-06-01 2014-05-22 Apple Inc. Avatars Reflecting User States
WO2013169849A2 (fr) 2012-05-09 2013-11-14 Industries Llc Yknots Dispositif, procédé et interface utilisateur graphique permettant d'afficher des objets d'interface utilisateur correspondant à une application
US20140013422A1 (en) 2012-07-03 2014-01-09 Scott Janus Continuous Multi-factor Authentication
EP2713298A1 (fr) 2012-09-27 2014-04-02 LG Electronics, Inc. Appareil d'affichage et son procédé de fonctionnement
US20140157153A1 (en) * 2012-12-05 2014-06-05 Jenny Yuen Select User Avatar on Detected Emotion
WO2014105276A1 (fr) 2012-12-29 2014-07-03 Yknots Industries Llc Dispositif, procédé et interface utilisateur graphique pour effectuer une transition entre des relations d'entrée tactile et de sortie d'affichage
WO2015196448A1 (fr) 2014-06-27 2015-12-30 Microsoft Technology Licensing, Llc Protection de données reposant sur une reconnaissance d'utilisateur et de geste

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3485392A4

Cited By (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11102414B2 (en) 2015-04-23 2021-08-24 Apple Inc. Digital viewfinder user interface for multiple cameras
US11711614B2 (en) 2015-04-23 2023-07-25 Apple Inc. Digital viewfinder user interface for multiple cameras
US11490017B2 (en) 2015-04-23 2022-11-01 Apple Inc. Digital viewfinder user interface for multiple cameras
US11245837B2 (en) 2016-06-12 2022-02-08 Apple Inc. User interface for camera effects
US11962889B2 (en) 2016-06-12 2024-04-16 Apple Inc. User interface for camera effects
US11165949B2 (en) 2016-06-12 2021-11-02 Apple Inc. User interface for capturing photos with different camera magnifications
US11641517B2 (en) 2016-06-12 2023-05-02 Apple Inc. User interface for camera effects
US11687224B2 (en) 2017-06-04 2023-06-27 Apple Inc. User interface camera effects
US11204692B2 (en) 2017-06-04 2021-12-21 Apple Inc. User interface camera effects
US11977731B2 (en) 2018-02-09 2024-05-07 Apple Inc. Media capture lock affordance for graphical user interface
US11112964B2 (en) 2018-02-09 2021-09-07 Apple Inc. Media capture lock affordance for graphical user interface
US11722764B2 (en) 2018-05-07 2023-08-08 Apple Inc. Creative camera
US11178335B2 (en) 2018-05-07 2021-11-16 Apple Inc. Creative camera
US11468625B2 (en) 2018-09-11 2022-10-11 Apple Inc. User interfaces for simulated depth effects
US11895391B2 (en) 2018-09-28 2024-02-06 Apple Inc. Capturing and displaying images with multiple focal planes
US11321857B2 (en) 2018-09-28 2022-05-03 Apple Inc. Displaying and editing images with depth information
US11669985B2 (en) 2018-09-28 2023-06-06 Apple Inc. Displaying and editing images with depth information
US11128792B2 (en) 2018-09-28 2021-09-21 Apple Inc. Capturing and displaying images with multiple focal planes
JP7286968B2 (ja) 2019-01-09 2023-06-06 凸版印刷株式会社 画像撮像支援装置及び画像撮像支援方法
JP2020113843A (ja) * 2019-01-09 2020-07-27 凸版印刷株式会社 画像撮像支援装置及び画像撮像支援方法
US11706521B2 (en) 2019-05-06 2023-07-18 Apple Inc. User interfaces for capturing and managing visual media
US11223771B2 (en) 2019-05-06 2022-01-11 Apple Inc. User interfaces for capturing and managing visual media
US11770601B2 (en) 2019-05-06 2023-09-26 Apple Inc. User interfaces for capturing and managing visual media
US11617022B2 (en) 2020-06-01 2023-03-28 Apple Inc. User interfaces for managing media
US11054973B1 (en) 2020-06-01 2021-07-06 Apple Inc. User interfaces for managing media
US11039074B1 (en) 2020-06-01 2021-06-15 Apple Inc. User interfaces for managing media
US12081862B2 (en) 2020-06-01 2024-09-03 Apple Inc. User interfaces for managing media
US11330184B2 (en) 2020-06-01 2022-05-10 Apple Inc. User interfaces for managing media
US11212449B1 (en) 2020-09-25 2021-12-28 Apple Inc. User interfaces for media capture and management
US11416134B1 (en) 2021-04-30 2022-08-16 Apple Inc. User interfaces for altering visual media
US11418699B1 (en) 2021-04-30 2022-08-16 Apple Inc. User interfaces for altering visual media
US11539876B2 (en) 2021-04-30 2022-12-27 Apple Inc. User interfaces for altering visual media
US11778339B2 (en) 2021-04-30 2023-10-03 Apple Inc. User interfaces for altering visual media
US11350026B1 (en) 2021-04-30 2022-05-31 Apple Inc. User interfaces for altering visual media
US12101567B2 (en) 2021-04-30 2024-09-24 Apple Inc. User interfaces for altering visual media
US12112024B2 (en) 2021-06-01 2024-10-08 Apple Inc. User interfaces for managing media styles

Also Published As

Publication number Publication date
WO2018057268A4 (fr) 2018-05-31

Similar Documents

Publication Publication Date Title
AU2021250944B2 (en) Image data for enhanced user interactions
US12079458B2 (en) Image data for enhanced user interactions
AU2023200797B2 (en) Image data for enhanced user interactions
WO2018057268A1 (fr) Données d'image pour interactions utilisateur améliorées
US11921998B2 (en) Editing features of an avatar
US11875021B2 (en) Underwater user interface
US20180074693A1 (en) Special lock mode user interface

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17853654

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20197005136

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017853654

Country of ref document: EP

Effective date: 20190215

ENP Entry into the national phase

Ref document number: 2019511975

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017330208

Country of ref document: AU

Date of ref document: 20170831

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE