DK201770393A1

DK201770393A1 - Emoji recording and sending

Info

Publication number: DK201770393A1
Application number: DKPA201770393A
Authority: DK
Inventors: C. Dye Alan; Guzman Aurelio; J. Bauer Sebastian; V. King Nicholas; Allen Anzures Freddy; Scapel Nicolas; Wilson Christopher; Pham Hoan; Yerkes Giancarlo
Original assignee: Apple Inc.
Priority date: 2017-05-16
Filing date: 2017-05-29
Publication date: 2019-01-24

Abstract

An electronic device having a camera and a display displays a virtual avatar generation interface. The electronic device display a preview of a virtual avatar in the virtual avatar generation interface, wherein the preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera. In response to detecting an input in the virtual avatar generation interface and in accordance with a determination that the input starts on the preview of the virtual avatar, the electronic device generates a static virtual avatar that represents an expression of the face in the field of view of the camera at a respective time, wherein the respective time is determined based on a timing of the input; and in accordance with a determination that the input includes activation of a record affordance in the virtual avatar generation interface, the electronic device generates an animated virtual avatar that represents a sequences of changes in the expression of the face in the field of view of the camera over a period of time, wherein the period of time is determined based on a timing of the input.

Description

EMOJI RECORDING AND SENDING

CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This application claims priority to U.S. provisional patent application 62/507,177, entitled “Emoji Recording and Sending,” filed May 16, 2017, the content of which is hereby incorporated by reference in its entirety.

FIELD [0002] The present disclosure relates generally to computer user interfaces, and more specifically to techniques for recording and sending emojis.

BACKGROUND [0003] Multimedia content, such as emojis, are sometimes sent as part of messaging communications. The emojis represents a variety of predefined people, objects, actions, and/or other things. Some messaging applications allow users to select from a predefined library of emojis which are sent as part of a message that can contain other content (e.g., other multimedia and/or textual content). Stickers are another type of multimedia content that are sometimes sent with messaging applications. In some ways, stickers are similar to emojis in that they can represent people, objects, actions, and/or other things. Some stickers and/or messaging applications allow for stickers to be associated with previously sent or received messages.

BRIEF SUMMARY [0004] Some techniques for sending and receiving emojis using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.

[0005] Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for sending and receiving emojis. Such methods and interfaces

DK 2017 70393 A1 optionally complement or replace other methods for sending and receiving emojis. 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.

[0006] In accordance with some embodiments, a method performed at an electronic device with a display and a camera is described. The method comprises: displaying a virtual avatar generation interface; displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein the preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera; while displaying the preview of the virtual avatar, detecting an input in the virtual avatar generation interface; in response to detecting the input in the virtual avatar generation interface: in accordance with a determination that the input starts on the preview of the virtual avatar, generating a static virtual avatar that represents an expression of the face in the field of view of the camera at a respective time, wherein the respective time is determined based on a timing of the input; and in accordance with a determination that the input includes activation of a record affordance in the virtual avatar generation interface, generating an animated virtual avatar that represents a sequences of changes in the expression of the face in the field of view of the camera over a period of time, wherein the period of time is determined based on a timing of the input.

[0007] In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display and a camera, the one or more programs including instructions for: displaying a virtual avatar generation interface; displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein the preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera; while displaying the preview of the virtual avatar, detecting an input in the virtual avatar generation interface; in response to detecting the input in the virtual avatar generation interface: in accordance with a determination that the input starts on the preview of the virtual avatar, generating a static virtual avatar that represents an expression of the face in the field of view of the camera at a respective time, wherein the

DK 2017 70393 A1 respective time is determined based on a timing of the input; and in accordance with a determination that the input includes activation of a record affordance in the virtual avatar generation interface, generating an animated virtual avatar that represents a sequences of changes in the expression of the face in the field of view of the camera over a period of time, wherein the period of time is determined based on a timing of the input.

[0008] In accordance with some embodiments, a transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display and a camera, the one or more programs including instructions for: displaying a virtual avatar generation interface; displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein the preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera; while displaying the preview of the virtual avatar, detecting an input in the virtual avatar generation interface; in response to detecting the input in the virtual avatar generation interface: in accordance with a determination that the input starts on the preview of the virtual avatar, generating a static virtual avatar that represents an expression of the face in the field of view of the camera at a respective time, wherein the respective time is determined based on a timing of the input; and in accordance with a determination that the input includes activation of a record affordance in the virtual avatar generation interface, generating an animated virtual avatar that represents a sequences of changes in the expression of the face in the field of view of the camera over a period of time, wherein the period of time is determined based on a timing of the input.

[0009] In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; a camera; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a virtual avatar generation interface; displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein the preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera; while displaying the preview of the virtual avatar, detecting an input in the virtual avatar generation interface; in response to detecting the input in the virtual avatar generation interface:

DK 2017 70393 A1 in accordance with a determination that the input starts on the preview of the virtual avatar, generating a static virtual avatar that represents an expression of the face in the field of view of the camera at a respective time, wherein the respective time is determined based on a timing of the input; and in accordance with a determination that the input includes activation of a record affordance in the virtual avatar generation interface, generating an animated virtual avatar that represents a sequences of changes in the expression of the face in the field of view of the camera over a period of time, wherein the period of time is determined based on a timing of the input.

[0010] In accordance with some embodiments, an electronic device is described. The electronic device comprises: a camera; a display for displaying a virtual avatar generation interface and displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein the preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera; means for, while displaying the preview of the virtual avatar, detecting an input in the virtual avatar generation interface; and means for, in response to detecting the input in the virtual avatar generation interface: in accordance with a determination that the input starts on the preview of the virtual avatar, generating a static virtual avatar that represents an expression of the face in the field of view of the camera at a respective time, wherein the respective time is determined based on a timing of the input; and in accordance with a determination that the input includes activation of a record affordance in the virtual avatar generation interface, generating an animated virtual avatar that represents a sequences of changes in the expression of the face in the field of view of the camera over a period of time, wherein the period of time is determined based on a timing of the input.

[0011] In accordance with some embodiments, a method performed at an electronic device with a display and a camera is described. The method comprises: displaying a virtual avatar generation interface; displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera; receiving a request to generate an animated virtual avatar based on changing facial expressions of the face that is in the field of view of the camera; in response to receiving the request to generate the animated virtual avatar, recording a sequence of facial expressions of the face in the field of view of the camera; after recording the facial

DK 2017 70393 A1 expressions of the face that is in the view of the camera, displaying a looping version of an animated virtual avatar that includes an animation sequence based on the sequence of facial expressions recorded in response to the request to generate the animate virtual avatar, wherein displaying the looping version of the animated virtual avatar includes displaying the animation sequence two or more times.

[0012] In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display and a camera, the one or more programs including instructions for: displaying a virtual avatar generation interface; displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera; receiving a request to generate an animated virtual avatar based on changing facial expressions of the face that is in the field of view of the camera; in response to receiving the request to generate the animated virtual avatar, recording a sequence of facial expressions of the face in the field of view of the camera; after recording the facial expressions of the face that is in the view of the camera, displaying a looping version of an animated virtual avatar that includes an animation sequence based on the sequence of facial expressions recorded in response to the request to generate the animate virtual avatar, wherein displaying the looping version of the animated virtual avatar includes displaying the animation sequence two or more times.

[0013] In accordance with some embodiments, a transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display and a camera, the one or more programs including instructions for: displaying a virtual avatar generation interface; displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera; receiving a request to generate an animated virtual avatar based on changing facial expressions of the face that is in the field of view of the camera; in response to receiving the request to generate the animated virtual avatar, recording a sequence

DK 2017 70393 A1 of facial expressions of the face in the field of view of the camera; after recording the facial expressions of the face that is in the view of the camera, displaying a looping version of an animated virtual avatar that includes an animation sequence based on the sequence of facial expressions recorded in response to the request to generate the animate virtual avatar, wherein displaying the looping version of the animated virtual avatar includes displaying the animation sequence two or more times.

[0014] In accordance with some embodiments, an electronic device is described. The electronic device comprises: displaying a virtual avatar generation interface; displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera; receiving a request to generate an animated virtual avatar based on changing facial expressions of the face that is in the field of view of the camera; in response to receiving the request to generate the animated virtual avatar, recording a sequence of facial expressions of the face in the field of view of the camera; after recording the facial expressions of the face that is in the view of the camera, displaying a looping version of an animated virtual avatar that includes an animation sequence based on the sequence of facial expressions recorded in response to the request to generate the animate virtual avatar, wherein displaying the looping version of the animated virtual avatar includes displaying the animation sequence two or more times.

[0015] In accordance with some embodiments, an electronic device is described. The electronic device comprises: a camera; a display for displaying a virtual avatar generation interface and displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera; means for receiving a request to generate an animated virtual avatar based on changing facial expressions of the face that is in the field of view of the camera; means for, in response to receiving the request to generate the animated virtual avatar, recording a sequence of facial expressions of the face in the field of view of the camera; means for after recording the facial expressions of the face that is in the view of the camera, causing display of a looping version of an animated virtual avatar that includes an animation sequence based on the sequence of facial expressions recorded in response to the request to generate the animate virtual

DK 2017 70393 A1 avatar, wherein displaying the looping version of the animated virtual avatar includes displaying the animation sequence two or more times.

[0016] 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.

[0017] Thus, devices are provided with faster, more efficient methods and interfaces for sending and receiving emojis, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for sending and receiving emojis.

DESCRIPTION OF THE FIGURES [0018] For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.

[0019] FIG. 1A is a block diagram illustrating a portable multifunction device with a touchsensitive display in accordance with some embodiments.

[0020] FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.

[0021] FIG. 2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.

[0022] FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

[0023] FIG. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

DK 2017 70393 A1 [0024] 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.

[0025] FIG. 5A illustrates a personal electronic device in accordance with some embodiments.

[0026] FIG. 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.

[0027] FIGs. 6A-6MM illustrate exemplary user interfaces for generating and sending emojis, stickers, virtual avatars, and/or other multimedia content.

[0028] FIGs. 7A-7J illustrate exemplary user interfaces for receiving emojis, stickers, virtual avatars, and/or other multimedia content.

[0029] FIGs. 8A-8B are a flow diagram illustrating a method for generating and sending emojis, stickers, virtual avatars, and/or other multimedia content.

[0030] FIGs. 9A-9B are a flow diagram illustrating a method for generating and sending emojis, stickers, virtual avatars, and/or other multimedia content.

DESCRIPTION OF EMBODIMENTS [0031] The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.

[0032] Sending messages with multimedia content with or in place of text content has the potential to better communicate a sender’s message. For example, multimedia content such as virtual avatars (e.g., animated or static emojis or stickers) can provide context and/or tone (e.g., what might be called “non-verbal communication”) that would be cumbersome or impossible to communicate with text alone. In some cases, predefined virtual avatars can be used to provide some of this context and/or tone. Predefined content, however, cannot cover every situation or provide finely tuned context or tone. Accordingly, there is a need for electronic devices that

DK 2017 70393 A1 provide efficient methods and interfaces for generating, sending, and receiving virtual avatars as part of messages. Such techniques can reduce the cognitive burden on a user who is sending and receiving messages, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.

[0033] Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of exemplary devices for performing the techniques for generating, sending, and receiving virtual avatars. FIGS. 6A-6MM illustrate exemplary user interfaces for generating and sending virtual avatars. FIGs. 7A-7J illustrate exemplary user interfaces for receiving virtual avatars. FIGs. 8A-8B and 9A-9B are flow diagrams illustrating methods of generating and sending virtual avatars in accordance with some embodiments. The user interfaces in FIGs. 6A-6MM and FIGs. 7A-7J are used to illustrate the processes described below, including the processes in FIGs. 8A-8B and 9A9B.

[0034] Although the following description uses terms “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. For example, 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.

[0035] The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

DK 2017 70393 A1 [0036] The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.

[0037] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, 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. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).

[0038] In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.

[0039] 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.

[0040] The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more

DK 2017 70393 A1 functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.

[0041] Attention is now directed toward embodiments of portable devices with touchsensitive displays. 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.

[0042] As used in the specification and claims, the term “intensity” of a contact on a touchsensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure

DK 2017 70393 A1 force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touchsensitive surface, or a physical/mechanical control such as a knob or a button).

[0043] As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user’s sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user’s hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator

DK 2017 70393 A1 button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user’s movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.

[0044] It should be appreciated that 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.

[0045] 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.

[0046] 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. In some embodiments, 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, implemented on separate chips.

DK 2017 70393 A1 [0047] RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. 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 communication (NFC) fields, such as by a short-range communication radio. 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 (EVDO), 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.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

[0048] 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 14

DK 2017 70393 A1 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. In some embodiments, 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 microphone).

[0049] 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. In some alternate embodiments, 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 (e.g., 208, FIG. 2) 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).

[0050] A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. Patent Application 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed December 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. 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.

DK 2017 70393 A1 [0051] 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.

[0052] 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. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.

[0053] Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch 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. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

[0054] 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. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.

DK 2017 70393 A1 [0055] 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/048,264, “Gestures For Touch Sensitive Input Devices,” filed January 31, 2005; (5) U.S. Patent Application No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed January 18, 2005; (6) U.S. Patent Application No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed September 16, 2005; (7) U.S. Patent Application No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed September 16, 2005; (8) U.S. Patent Application No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed September 16, 2005; and (9) U.S. Patent Application No. 11/367,749, “Multi-Functional Hand-Held Device,” filed March 3, 2006. All of these applications are incorporated by reference herein in their entirety.

[0056] 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. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.

[0057] In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

DK 2017 70393 A1 [0058] 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.

[0059] 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. Optical sensor 164 receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, 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. In some embodiments, 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. In some embodiments, 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.

[0060] 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. In some embodiments, at least one contact

DK 2017 70393 A1 intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touchsensitive display system 112). In some embodiments, 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.

[0061] Device 100 optionally also includes one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternately, 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. 11/241,839, “Proximity Detector In Handheld Device”; 11/240,788, “Proximity Detector In Handheld Device”;

11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, 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).

[0062] 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. In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touchsensitive 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). In some

DK 2017 70393 A1 embodiments, 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.

[0063] Device 100 optionally also includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternately, 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, “Accelerationbased Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. 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.

[0064] In some embodiments, 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. Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device/global internal state 157, as shown in FIGS. 1A and 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.

[0065] Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory

DK 2017 70393 A1 management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

[0066] 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., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

[0067] 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 touchsensitive 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”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.

[0068] In some embodiments, 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). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds 21

DK 2017 70393 A1 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. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).

[0069] Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.

[0070] 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. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.

[0071] In some embodiments, 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.

DK 2017 70393 A1 [0072] 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.

[0073] 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).

[0074] 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).

[0075] 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);

• Telephone module 138;

• Video conference module 139;

• E-mail client module 140;

• Instant messaging (IM) module 141;

• Workout support module 142;

• Camera module 143 for still and/or video images;

• Image management module 144;

• Video player module;

• Music player module;

DK 2017 70393 A1 • Browser module 147;

• 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;

• Search module 151;

• Video and music player module 152, which merges video player module and music player module;

• Notes module 153;

• Map module 154; and/or • Online video module 155.

[0076] 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.

[0077] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, 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: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate

DK 2017 70393 A1 and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or

IM 141; and so forth.

[0078] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, 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. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.

[0079] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, 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.

[0080] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, 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.

[0081] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, 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 Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP,

DK 2017 70393 A1

SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0082] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, 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.

[0083] In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, 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.

[0084] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, 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.

[0085] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, 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.

DK 2017 70393 A1 [0086] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module

140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, todo lists, etc.) in accordance with user instructions.

[0087] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, 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 1496). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).

[0088] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, 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).

[0089] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, 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.

[0090] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, 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

DK 2017 70393 A1 play back videos (e.g., on touch screen 112 or on an external, connected display via external port

124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

[0091] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.

[0092] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, 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.

[0093] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, 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. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed June 20, 2007, and U.S. Patent Application No.

11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed December 31, 2007, the contents of which are hereby incorporated by reference in their entirety.

DK 2017 70393 A1 [0094] Each of the above-identified 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). These modules (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. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152, FIG. 1A). In some embodiments, 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.

[0095] In some embodiments, 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. By using 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.

[0096] The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

[0097] FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In 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).

[0098] 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. In some embodiments,

DK 2017 70393 A1 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. In some embodiments, 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.

[0099] In some embodiments, 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.

[0100] 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.

[0101] In some embodiments, 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).

[0102] In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.

[0103] Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112

DK 2017 70393 A1 displays more than one view. Views are made up of controls and other elements that a user can see on the display.

[0104] 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.

[0105] 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.

[0106] 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.

DK 2017 70393 A1 [0107] 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.

[0108] In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.

[0109] In some embodiments, 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. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, 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. In some embodiments, 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. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

[0110] 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 embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).

DK 2017 70393 A1 [0111] 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. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.

[0112] Event comparator 184 compares the event information to predefined event or subevent definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event 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. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first 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. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0113] In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, 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

DK 2017 70393 A1 hit test to determine which of the three user-interface objects is associated with the touch (subevent). 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 subevent and the object triggering the hit test.

[0114] In some embodiments, 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.

[0115] When 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 subevents 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.

[0116] In some embodiments, 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. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether subevents are delivered to varying levels in the view or programmatic hierarchy.

[0117] In some embodiments, 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. In some embodiments, 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. In some embodiments, event recognizer

DK 2017 70393 A1

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.

[0118] In some embodiments, 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.

[0119] In some embodiments, 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. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.

[0120] In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, 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.

[0121] It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on 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.

DK 2017 70393 A1 [0122] 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. In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

[0123] Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.

[0124] In some embodiments, 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. In an alternative embodiment, 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.

DK 2017 70393 A1 [0125] 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. In some embodiments, 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, touchsensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A). 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. For example, 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.

[0126] 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 37

DK 2017 70393 A1 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. In some 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.

[0127] Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.

[0128] 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. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

• Signal strength indicator(s) 402 for wireless communication(s), such as cellular and WiFi signals;

• Time 404;

• Bluetooth indicator 405;

• Battery status indicator 406;

• 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 (trademark of Apple Inc.) module 152, labeled “iPod;” and

DK 2017 70393 A1 • 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 a settings application or module, labeled “Settings,” which provides access to settings for device 100 and its various applications 136.

[0129] It should be noted that the icon labels illustrated in FIG. 4A are merely exemplary. For example, icon 422 for video and music player module 152 is labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.

[0130] 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 357for generating tactile outputs for a user of device 300.

DK 2017 70393 A1 [0131] Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) 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). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (e.g., contacts 460 and 462, and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) are used by the device to manipulate the user interface on the display (e.g., 450 in FIG. 4B) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein.

[0132] Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.

[0133] FIG. 5A illustrates exemplary personal electronic device 500. Device 500 includes body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitive display screen 504, hereafter touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100

DK 2017 70393 A1 and 300, in some embodiments, touch screen 504 (or the touch-sensitive surface) 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.

[0134] Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No.

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 Transitioning Between Touch Input to Display Output Relationships,” filed November 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.

[0135] In some embodiments, 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. In some embodiments, 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.

[0136] FIG. 5B depicts exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, 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). In addition, I/O section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field

DK 2017 70393 A1 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.

[0137] 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.

[0138] Memory 518 of personal electronic device 500 can include one or more nontransitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 800 and 900 (FIGs. 8A-8B and 9A-9B). A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a nontransitory computer-readable storage medium. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. 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.

[0139] As used here, 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. 1A, 3, and 5A-5B). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) each optionally constitute an affordance.

[0140] As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that

DK 2017 70393 A1 include a cursor or other location marker, 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. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, 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. In some implementations, 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. Without regard to the specific form taken by the focus selector, 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). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while 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).

[0141] As used in the specification and claims, 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

DK 2017 70393 A1 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 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. In some embodiments, 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). In some embodiments, 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. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, 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, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, 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.

[0142] In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, 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. In this example, 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). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average

DK 2017 70393 A1 smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.

[0143] 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. In some embodiments, 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. In some embodiments, 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. In some embodiments, 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. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.

[0144] 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 contactdetection 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 touchsurface. A decrease of characteristic intensity of the contact from an intensity above the contactdetection intensity threshold to an intensity below the contact-detection intensity threshold is

DK 2017 70393 A1 sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.

[0145] In some embodiments described herein, 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. In some embodiments, 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). In some embodiments, 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).

[0146] In some embodiments, 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). Thus, in some embodiments, 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). Similarly, in some embodiments, 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

DK 2017 70393 A1 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).

[0147] For ease of explanation, 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. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below 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.

[0148] Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

[0149] FIGs. 6A-6MM illustrate exemplary user interfaces for generating and sending virtual avatars, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGs. 8A-8B and 9A-9B. FIGs. 7A-7J illustrate exemplary user interfaces for receiving and playing virtual avatars, in accordance with some embodiments. FIGs. 6A-6MM and FIGs. 7A-7J use virtual avatars as a specific example of a virtual avatar.

[0150] FIG. 6A depicts device 600 having display 601, which in some cases is a touchsensitive display, and camera 602, which, at a minimum, includes an image sensor that is capable of capturing data representing a portion of the light spectrum (e.g., visible light, infrared light, or

DK 2017 70393 A1 ultraviolet light). In some embodiments, camera 602 includes multiple image sensors and/or other types of sensors. In addition to capturing data representing sensed light, in some embodiments, camera 602 is capable of capturing other types of data, such as depth data. For example, in some embodiments, camera 602 also captures depth data using techniques based on speckle, time-of-flight, parallax, or focus. Image data that device 600 captures using camera 602 includes data corresponding to a portion of the light spectrum for a scene within the field of view of the camera. Additionally, in some embodiments, the captured image data also includes depth data for the light data. In some other embodiments, the captured image data contains data sufficient to determine or generate depth data for the data for the portion of the light spectrum. In some embodiments, device 600 includes one or more features of devices 100, 300, or 500.

[0151] In FIG. 6A, device 600 is displaying a home screen interface with multiple icons for various applications, including icon 603 for a messaging application. In response to a gesture (e.g., tap gesture 604) on icon 603, device 600 displays the user interface in FIG. 6B corresponding to a messaging application associated with icon 603.

[0152] In FIG. 6B, device 600 is displaying messaging interface 608. Elements 605-1 to 605-6 correspond to previous messaging communications. Each element 605-1 to 605-6 represents one communication with one or more remote users that are each associated with their own electronic device. In response to a gesture (e.g., tap gesture 606) on a particular element, device 600 updates messaging interface 608 to display a part of a previous messaging communication with the remote user or users that are part of the communication, as depicted in FIG. 6C.

[0153] In FIG. 6C, device 600 is displaying messaging interface 608 for messaging communications with the remote user called “John” (and having initials or a monogram of “JA”). Messaging interface 608 includes message area 609 that includes four previously exchanged messages 610-1 to 610-3 (message 610-3 was sent from the user of device 600 to “John” while the other two messages were received by device 600 from “John”). Messaging interface 608 also includes message composition area 612 and message option icons, including icon 614 (e.g., that accesses an interface for selecting stickers and/or other multimedia elements for a message), to the left of message composition area 612. In some embodiments, the message option icons allow 48

DK 2017 70393 A1 for sending different types of messages, including photos, emojis, stickers, and other forms of non-textual messages, such as those described below.

[0154] In response to device 600 detecting selection of message composition area 612 (e.g., via tap gesture 616 of FIG. 6C), messaging interface 608 is updated as depicted in FIG. 6D. For example, in FIG. 6D, the message option icons are hidden (but can be shown again by selection of button 618), suggested message responses 620 are displayed, and virtual keyboard 622 is displayed. In some cases, virtual keyboard 622 is used to enter a new message to send to the remote user.

[0155] In FIG. 6E, message composition area 612 includes the text “running late,” which is entered, for example, via virtual keyboard 622 or other methods, such as voice input. In response to selection of send button 621, device 600 sends the text as part of a message to one or more participants associated with the communication in message 609. In the case of FIG. 6E, device 600 sends the message to the user called “John.” In FIG. 6F, device 600 has updated message area 609 to reflect the sending of the message by updating message area 612 to include message 610-4.

[0156] In some cases, the message options icons are accessed to add to or compose a new message (e.g., by adding non-textual content to the message). For example, in response to device 600 detecting selection of affordance 618 (e.g., via tap gesture 624 in FIG. 6F), message option icons, including icon 614, are displayed again, as depicted in FIG. 6G. In response to selection of icon 614 (e.g., via a gesture, such as tap gesture 626), device 600 updates messaging interface 608, as depicted in FIG. 6I, by replacing virtual keyboard 622 with multimedia item interface 628, which is currently display a recent item menu 629 (sometimes known as “tray” for recent items), which includes previously sent multimedia items (e.g., stickers 630-1 to 630-4 in FIG. 6I, but other types of multimedia items, such as sound, animations, or videos, could also be included). Using this interface, a user can select a previously sent multimedia item to send again. For example, a user can select one of the stickers in recent item menu 629 of FIG. 6I via a tap gesture on the selected sticker. In response to such selection, device 600 either places the sticker in message composition area 612 or sends the selected sticker to the one or more remote users that are involved in the communication represented in message area 609. In some

DK 2017 70393 A1 embodiments, a tap and drag gesture is used to place the selected sticker (or other multimedia item) in either message composition area 612 or message area 609 (and in some cases on a specific message). For example, a particular sticker is selected via a tap gesture. Without breaking contact with touch-sensitive display 601, the sticker is dragged to either message composition area 612 or message area 609 via a drag gesture. Once the desired location of the sticker is reached, contact with touch-sensitive display 601 is ceased and the sticker is placed at the last location of the contact. If the last location of the contact is in message area 609, then the sticker is sent to the one or more remote users associated with the communication represented in message area 609. Optionally, the sticker is sent to the remote users with data associating the sticker with a particular message (e.g., the sticker is sent with data indication a particular location of a particular message to which the sticker is “stuck”). These techniques are not specific to selecting and sending stickers. It can also apply to other types of multimedia items selectable from recent item menu 629 or other locations.

[0157] In FIG. 6I, multimedia item interface 628 also includes menu selection button 632 (which allows for menus or interfaces other than recent item menu 629 to be selected via a display of buttons or other selectable items corresponding to available menus) and full screen button 634 (which allows for multimedia item interface 628 to expand to more of the display (or the entire display). Full screen button 634 is further described below.

[0158] In addition to using menu selection button 632 to switch between menus or interfaces, gestures are also optionally used to switch between menus. For example, in response to a swipe gesture (e.g., a swipe represented by contact 636’s movement across multimedia item interface 628 as depicted in FIGs. 6J and 6K), device updates multimedia item interface 628 to replace display of recent item menu 629 with virtual avatar menu 638. While recent item menu 629 is being replaced with virtual avatar menu 638, scroll indicator 639 provides feedback about how many other menus are available in multimedia item interface 628.

[0159] In FIG. 6L, virtual avatar menu 638 has completely replaced display of recent item menu 629. In response to device 600 detecting selection of continue affordance 640 (e.g., via a gesture such as tap gesture 642 of FIG. 6M), virtual avatar interface 643 is displayed as depicted in FIG. 6N. This interface allows users to generate new virtual avatars that reflect a user’s facial 50

DK 2017 70393 A1 movements and expressions, as further described below. In some embodiments, virtual avatar menu 638 is not displayed at all. Instead, virtual avatar interface 643 is displayed without first displaying virtual avatar menu 638.

[0160] Virtual avatar interface 643 of FIG. 6N includes avatar template representations 6441 to 644-7 that correspond to different avatar frameworks (e.g., avatar characters that have different appearances and behavior). Each avatar template represents an avatar framework to which detected facial movements and expressions can be mapped. Indicator 645 corresponds to a currently selected avatar template. Virtual avatar preview 646 is a “live” preview of the virtual avatar in that it is updated to reflect the user’s current facial movements and expressions. For example, in some embodiments, using camera 602, device 600 continuously captures image data from camera 602. The captured image data includes visible light data and depth data. Device 600 analyzes the captured image data to identify facial movements (e.g., muscle movements, head orientations, gaze direction, etc.) and/or facial expressions (e.g., a smile, a frown, an angry expression, a sad expression, a confused expression, etc.). Device 600 then updates avatar preview 646 to reflect the detected characteristics of the user, in accordance with the parameters of the avatar framework currently associated with virtual avatar preview 646. In some embodiments, device 600 starts continuously updating virtual avatar preview 646 automatically in response to virtual avatar interface 643 first executing or being displayed. Detecting selection of a representation of a different avatar template will cause device 600 to update virtual avatar preview 646 based on the newly selected avatar template.

[0161] FIG. 6O depicts several example of a user’s face in captured image data 650-1 to 650-5 and corresponding updates 651-1 to 651-5 to the virtual avatar preview. These are examples of device 600 updating emoji preview 646 to reflect the user’s facial movements, expressions, and poses. In captured image data 650-1, device 600 detects (for example, based on facial features, muscles, movements, and/or expressions) that the user is looking straight ahead, smiling and/or happy. In response, device 600 updates the virtual avatar preview to reflect the user’s smile and/or happy expression in addition to updating the virtual avatar preview’s eyes to look straight ahead,, as depicted in update 651-1. While the detected physical feature of the user in the captured image data is sometimes the same physical feature in the virtual avatar that is

DK 2017 70393 A1 updated so that the virtual avatar reflects the user, in other cases, a detected change in a user’s physical feature results in an update of a different type of physical feature of the virtual avatar. For example, in FIG. 6O, changes in the user’s eye brows are mapped to the monkey’s ears (or other feature) because the monkey does not have eyebrows, as shown by 650-2 and 651-2. In this example, the user’s mouth and eyes are mapped to the monkey’s mouth and eyes. In the example of image data 650-3 and update 651-3, the user’s unhappy expression and/or frown are reflected in the virtual avatar preview’s corresponding features. In some embodiments, if the user holds a facial expression or facial pose, as depicted by image 650-3 and 650-4, the virtual avatar preview is updated with additional features, such as tears in the case of update 651-4. This type of predefined update can also occur in response to a lack of detected movement. In some embodiments, updates are also based on detected user movement in image data. For example, device 600 detecting rotation of the user’s head results in an update that similar rotates the virtual avatar preview. In some embodiments, updates are also based on a physic models for features of the virtual avatar. For example, in image data 650-5, device 600 detects the user’s head is shaking. In response, device 600 generates update 651-5 to reflect the head shaking. Additionally, in update 651-5, the puppy’s ears also stick out as a result of a physics model applied to the puppy’s ears.

[0162] In FIG. 6P, device 600 detects selection of record button 652 via a gesture (e.g., tap gesture represented by contact 653). In response, virtual avatar interface 643 is updated to show that an animated virtual avatar is being generated, as depicted in FIG. 6Q. For example, record button 652 is replaced with stop button 654, avatar template representations 644-1 to 644-7 are no longer displayed, and record progress indicator 656 is displayed that indicates how long the animated emoji has been recorded and a relative amount of time that the virtual avatar can still be recorded. The recording can stop by any number of methods, such as by the expiration of a predetermined amount of time (e.g., 15 seconds) or by selection of stop button 654. In some embodiments, while recording, device 600 is detecting and/or storing a series of data points that are used to create an animated virtual avatar. For example, in some embodiments, device 600 records a time series of facial movements and/or facial expressions (e.g., as values of a range of possible values, with each value of the range of possible values corresponding to a predetermined movement or expression), which are then mapped onto an avatar template to

DK 2017 70393 A1 create an animated virtual avatar. Alternatively, device 600 records the animated virtual avatar by creating a video recording of the virtual avatar preview as device 600 updates the virtual avatar preview to reflect the user’s facial movements and/or expressions. In some embodiments, device 600 also records sound captured with a microphone of device 600 so that the recorded animated virtual avatar includes sounds that can be played back along with the recorded animations of the virtual avatar.

[0163] FIG. 6R depicts a later point in time during the recording of an animated virtual avatar. Virtual avatar preview 646 has been updated to reflect a newly detected facial movement and/or expression from the user. Indicator 656 has also been updated to reflect the further progress in recording the animated virtual avatar.

[0164] FIG. 6S depicts a yet later point in time during the recording of an animated virtual avatar. Virtual avatar preview 646 has been updated further to reflect a newly detected facial movement and/or expression from the user. Indicator 656 has also been updated to reflect the further progress in recording the animated virtual avatar.

[0165] In FIG. 6S, a gesture (e.g., a tap gesture represented by contact 658) requesting recording of the animated virtual avatar to stop is received. In response, device 600 stops recording the animated virtual avatar and updates the virtual avatar interface as depicted in FIG. 6T. In other cases, device 600 stops recording the animated virtual avatar and updates the virtual avatar interface as depicted in FIG. 6T in response to expiration of a predetermined time period (e.g., 15 seconds).

[0166] In FIG. 6T, virtual avatar interface 643 now plays recorded animated virtual avatar 659 in place of displaying the virtual avatar preview, as depicted by the three snapshots of the play back of animated virtual avatar 659. In some embodiments, the recorded animate emoji is played in loop (e.g., it is played at least twice without user input as indicated by the arrows in FIG. 6T). Virtual avatar interface 643 also includes discard button 560, mute button 662, and confirm button 664 (which is displayed in place of record button 652). Discard button 560 discards the display recorded animated virtual avatar without saving it and without sending it to a remote user. Mute button 662 allows a user to mute the play back of sound from the recorded

DK 2017 70393 A1 animated emoji. Confirm button 664 allows the recorded animated virtual avatar to get sent to a remote user (e.g., sending directing to one or more users associated with the communication displayed in message area 609 in response to activation of confirm button 664 or moved to message composition area 612 before a user sends the message). After device 600 detects selection of confirm button 664, virtual avatar interface 643 is updated to return to the state described with respect to FIG. 6N. In some embodiments, confirm button 664 includes a glyph or icon that is similar to or the same as a send glyph or icon (e.g., 670 in Figure 6 V) that is displayed in a send button for sending messages that are in a message composition region to indicate that the recorded animated virtual avatar can be sent to the remote user by selecting the confirm button 664.

[0167] While animated virtual avatar 659 is playing, in response to tap gesture 665 on a representation of a different avatar template than the currently selected template, the animated virtual avatar is updated to reflect the new avatar template without having to rerecord the animated virtual avatar. This is depicted in FIG. 6U, which depicts animated virtual avatar 659 having been replaced by animated virtual avatar 666. The recorded facial muscles, movements, features, and expressions used to generate animated virtual avatar 659 in FIG. 6T are reapplied to the newly selected avatar template in FIG. 6U.

[0168] Referring back to FIG. 6T, in response to a gesture (e.g., a tap gesture represented by contact 667), device 600 adds the recorded animated virtual avatar 668 to message composition area 612 (see FIG. 6V) and returns virtual avatar interface 643 to the state described in FIG. 6N (see FIG. 6V). The user can then add more message content (e.g., text or other multimedia items) to the message (see FIG. 6 V) before device 600 sends the message (e.g., in response to a tap gesture represented by contact 672 on send affordance 670, as depicted in FIG. 6W). Alternatively, upon device 600 detecting selection of confirm button 664, device 600 sends the recorded animated virtual avatar to one or more remote users associated with the communication displayed in message area 609, which is then updated to reflect that animated virtual avatar 668 has been sent to one or more user associated with the communication included in message area 609, as depicted in FIG. 6X.

DK 2017 70393 A1 [0169] FIGs. 6Y-6BB depict the response of virtual avatar interface 643 to user input scrolling through the list of avatar templates. For example, in response to swipe gestures (e.g., representation by the movement of contact 676 vertically across the avatar templates, as depicted in FIGs. 6Y-6AA), device 600 scrolls the avatar templates and changes which avatar template is currently selected. The avatar template present within avatar template indicator 645 is updated based on the swipe gesture. In response to detecting new avatar templates being selected, device 600 updates the virtual avatar preview. For example, in FIG. 6Z, when device 600 detects selection of avatar template representation 644-5, virtual avatar preview 678 (which is based on an avatar template corresponding to representation 644-5) is displayed and in FIG. 6AA, when avatar template representation 644-8 is selected, virtual avatar preview 680 (which is based on an avatar template corresponding to representation 644-8) is displayed.

[0170] In addition to generating a recording of animated puppet emoji, emoji interface 643 also allows for generating static virtual avatars (e.g., stickers with an expression/appearance that is determine based on the state of an virtual avatar). For example, in FIG. 6CC, in response to user input (e.g., a tap and hold gesture represented by contact 682) on virtual avatar preview 680, device 600 generates a sticker corresponding to the state of virtual avatar preview 680 at a time associated with the user input (e.g., when the input was received, when it ended, or some other time associated with the user input). In embodiments, device 600 displays sticker 683 (FIGs. 6DD and 6EE) being peeled off of virtual avatar preview 680 to indicate that a sticker has been generated and/or that the user can place the sticker.

[0171] After device 600 generates a sticker, the user optionally chooses from several operations for the sticker. For example, the user can cause device 600 to place the sticker in the recent menu or other similar interface that allows for later use. The user can also cause device 600 to place the sticker in message composition area 612 before device 600 sends a message that includes the sticker, the user can place the sticker in message area 609 (and optionally) on a specific message to cause device 600 to send the sticker to one or more users participating in the communication in message area 609.

[0172] For example, in FIG. 6FF, device 600 has detected lift off of contact 682 while contact was still over virtual avatar preview 680. In response, device 600 has saved the

DK 2017 70393 A1 generated sticker to device 600, such as in a database or library in device 600’s memory that is accessible by recent item menu 629 (FIG. 6I) so that the sticker is optionally selectable through recent item menu 629 or via other interfaces on device 600. Device 600 optionally shows that the sticker is being save locally via an animation with different graphical versions 684 and 686, as depicted in FIGs. 6FF-6GG, moving towards menu selection button 632.

[0173] As another example, FIGs. 6HH-6KK show an example of device 600 sending a generated sticker to one or more users participating in the communication represented in message area 609. In Fig. 6II, device 600 detects user input on virtual avatar preview 680 (e.g., a tap and drag gesture represented by contact 688 in FIGs. 6HH-6JJ that starts on virtual avatar preview 680). Sticker representation 690 follows contact 688 as device 600 detects the user dragging the sticker representation into message area 609. Once device 600 detects lift off of contact 688 in message area 609, device 600 sends sticker 691 to one or more remote users that are participants of the communication represented in message area 609, as depicted in FIG. 6KK.

[0174] in FIG. 6LL, device 600 updates virtual avatar interface 643 to display more of the screen (or in a full-screen mode) in response to selection of full-screen button 634 (e.g., via a tap gesture represented by contact 692 in FIG. 6LL). FIG. 6MM depicts virtual avatar interface 643 after it is enlarged to use more of display 601. Button 692, when selected, causes device 600 to return virtual avatar interface 643 to its previous configuration.

[0175] FIGs. 7A-7J depict messaging interface 608 after receiving an animated emoji from a remote user. While FIGs. 7A-7J use device 600 of FIGs. 6A-6MM as an example, the user interfaces and functionality depicted in FIGs. 7A-7J also apply to other devices (e.g., devices 100, 300, or 500), including those that have not previously sent a sticker or animated virtual avatar.

[0176] FIG. 7A depicts message interface 608 after having received animated virtual avatar 700 from the remote user named “John” (and has initials or a monogram “JA”), just prior to playing the animated virtual avatar. After receiving it, device 600 plays animated virtual avatar 700 automatically in some embodiments. Mute button 702, when selected, causes device 600 to mute any sound that is associated with animated virtual avatar 700. In some embodiments, any

DK 2017 70393 A1 sound is also muted if the animated virtual avatar is scrolled off of the display. In some embodiments, virtual avatar interface 643 is displayed as described with respect to FIGs. 6A6MM (e.g., virtual avatar interface 643 includes a preview virtual avatar based on detected facial movements/expressions and a selected avatar template).

[0177] In FIG. 7B, in response to animated virtual avatar 700 being played once (e.g., played from start to finish, once), still frame 703 of animated virtual avatar 700 is displayed in place of the animated virtual avatar 700. Replay button 704 is also displayed in message area 609 and allows for animated virtual avatar 700 to be played again by, for example, a tap feature represented by contact 706 of FIG. 7C. FIG. 7D depicts device 600 playing animated virtual avatar 700 again (playing the animated emoji is described with respect to FIG. 7A).

[0178] In some embodiments, while animated virtual avatar 700 is playing, if device 600 receives user input on mute button 702 (e.g., a tap gesture represented by contact 708 of FIG. 7E), device 600 stops playing any sounds associated with animated virtual avatar 700 while continuing to play animate virtual avatar 700 (e.g., animated virtual avatar 700 still moves without sound). In some embodiments, in response to selection of mute button 702 (or if sound is turned off on device 600 or device 600 has accessibility features enabled) transcript button 714 is displayed, as depicted in FIG. 7H. In response to selection of transcript button 714 (e.g., via a tap gesture represented by contact 716 of FIG. 7G) transcript 718 of the sound for animated virtual avatar 700 is displayed, as depicted in FIG. 7H. The content of transcript 718 is generated local to device 600 or remotely (e.g., using remote server computing resources).

[0179] In response to user input on animated virtual avatar 700 (e.g., a tap and hold gesture represented by contact 720 in FIG. 7I), device 600 displays a menu of options related to animated virtual avatar 700, as depicted in FIG. 7J. For example, menu 722 includes several response buttons 723-1 to 723-6 that device 600 can send to one or more remote users participating in the communication represented in message area 609. Additionally, menu 724 is also displayed having copy button 726, save button 728, and more button 730. Copy button 726 copies animated virtual avatar 700 to a clipboard of device 600. Save button 728 saves animated virtual avatar 700 to device 600 (e.g., to a database or library that can be later access by

DK 2017 70393 A1 applications installed on device 600). More button 730 displays additional operations that can be performed with respect to animated virtual avatar 700.

[0180] FIGs. 8A-8B are a flow diagram illustrating a method for 800 using an electronic device in accordance with some embodiments. Method 800 is performed at a device (e.g., 100, 300, 500, 600) with a display and a camera. Some operations in method 800 are, optionally, combined, the order of some operations are, optionally, changed, and some operations are, optionally, omitted.

[0181] As described below, method 800 provides an intuitive way for generating and sending emojis, such as virtual avatars. The method reduces the cognitive burden on a user for generating and sending emojis, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to generate and send emojis faster and more efficiently conserves power and increases the time between battery charges.

[0182] An electronic device (e.g., 600) having a camera (e.g., 602) (e.g., configured with one or more sensors for capturing data representing visible light, IR light, depth data, etc.) and a display (e.g., 601), displays (802) a virtual avatar generation interface (e.g. 643 of FIG. 6N) (e.g., for selecting emojis (animated or static), generating static stickers, and/or recording animated virtual avatars). The electronic device displays (804) a preview of a virtual avatar (e.g., 646 of FIG. 6N) (e.g., a 2D or 3D computer generated graphical object, in some cases intended to convey a non-verbal message, such as an emotion or reaction) in the virtual avatar generation interface (e.g., an animated virtual avatar selected from multiple different available virtual avatar templates). The preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera (e.g., FIG. 6O) (e.g., the animated virtual vatar will reflect the user’s head movements, facial expressions, and orientation as detected in image data from one or more image sensors in the camera). While displaying the preview of the virtual avatar, the electronic device detects (806) an input (e.g., contact 652, 682, or 690) in the virtual avatar generation interface. In response (808) to detecting the input in the virtual avatar generation interface and in accordance with a determination that the input starts on the preview of the virtual avatar (e.g., 682 or 690) (e.g., a touch and hold input on the animated virtual avatar or a trackpad input controlling a cursor), the electronic device generates (810) a static virtual avatar a sticker

DK 2017 70393 A1 (e.g., 683 or 691) (e.g., a still image of the animated emoji that is “stickable” on a particular location in a message area) that represents an expression of the face in the field of view of the camera at a respective time. In some embodiments, the respective time is determined based on a timing of the input (e.g., at the time the input was first received, at the time the input ended, at the time a gesture corresponding to the input started a moving across a touch-sensitive surface, or any other time related to the input). In accordance with a determination that the input includes activation of a record affordance (e.g., 648) in the virtual avatar generation interface (e.g., a tap on a record affordance), the electronic device generates (812) an animated virtual avatar (e.g., 668) that represents a sequences of changes in the expression of the face in the field of view of the camera over a period of time (e.g., as shown in FIG 6Q-6S). In some embodiments, the period of time is determined based on a timing of the input (e.g., the period of time starts when the start of the input is detected, when the end of the input is detected, when some sort of movement of the input, such as when the input is a gesture on a touch-sensitive surface, is detected, or some other period of time based on the input). In some embodiments, the virtual avatar is three-dimensional. In some embodiments, the preview of the virtual avatar (e.g., 646) or the animated virtual avatar (e.g., 659) is displayed in 3D. Disambiguating a user input between two possible styles of communication (e.g., animated virtual avatars and static virtual avatars) avoids the need for separate interfaces to generate each type of message content. Reducing the number of inputs needed to communicate a desired message enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended communication by allowing for multiple types of multimedia communication from a single interface) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0183] In some embodiments, the electronic device displays (814) a messaging interface (e.g., interface 608) (e.g., a messaging application such as Apple’s Messages) including a message area (e.g., 609). The message area includes messages (e.g., 610-1 to 610-4) from two or more participants (e.g., in FIG. 6C, remote user “John” and the user of device 600) (e.g., a message sent from the user of the electronic device and a message received from a remote user of a different electronic device) of a communication (e.g., the communication in message area 609 of FIG. 6N) (e.g., a messaging thread). The virtual avatar generation interface is displayed 59

DK 2017 70393 A1 concurrently with the messaging interface (e.g., FIG. 6N) (e.g., the virtual avatar generation interface is display in the bottom half of the messaging interface). In some embodiments, the preview of the virtual avatar (e.g., 646) is displayed automatically as part of the initial display of the virtual avatar generation interface.

[0184] In some embodiments, the messaging interface includes a message composition area (e.g., 612) (e.g., a message entry area for entering text, emojis, and other content before sending the message to a recipient) and the input is a tap on the preview of the virtual avatar (e.g., 646). The electronic device, in response to detecting the input in the virtual avatar generation interface, displays the static virtual avatar (e.g., 683 or 691) in the message composition area. In some embodiments, displaying the virtual avatar generation interface includes replacing display of a virtual keyboard (e.g., 622) of the messaging interface with display of the virtual avatar generation interface (e.g., a transition from FIG. 6H to FIG. 6N, without intervening figures). Displaying multimedia content of a message prior to sending the message reduces the likelihood of an erroneous message and allows a user to add more content (e.g., via text or other content) prior to sending the message. Reducing the number of messages needed to communicate a desired message enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended communication while reducing the number of messages needed for the communication), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0185] In some embodiments, the avatar generation interface includes a static virtual avatar area (e.g., 629) (e.g., a tray of previously generated stickers displayed at the bottom of the avatar generation interface) that includes a collection of one or more previously generated virtual avatars (e.g., 630-1 to 630-4). In response to a user input (e.g., 682 of FIG. 6CC), the electronic device adds (612) the generated virtual avatar to the collection of one or more previously generated virtual avatars (e.g., sending an avatar, marking a virtual avatar as a favorite or otherwise marking the virtual avatar for inclusion in the collection of virtual avatars). In some embodiments, the collection of virtual avatars (e.g., stickers) is displayed in response to a user input (e.g. 626) (e.g., selection of a virtual avatar collection affordance in the avatar generation

DK 2017 70393 A1 user interface or in the messaging user interface) (e.g., including a miniature version of the newly generated sticker in the tray). In some embodiments, the tray of previously generated stickers is hidden until an input (e.g., input 626) is received from the user requesting display of the tray or until some other event detected on the electronic device indicates that the tray is possibly relevant to a current state of the message interface or avatar generation interface. In some embodiments, after adding the virtual avatar to the collection of virtual avatars, the electronic device receives, from the user a request to share the collection of virtual avatars with a second user and in response, and the electronic device sends the collection of virtual avatars to the second user. Maintaining previously sent message multimedia content allows a user to add and reuse previous content when applicable to new messages. Eliminating the need to recreate content enhances the operability of the device and makes the user-device interface more efficient (e.g., by eliminating repetitive generation of content) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0186] In some embodiments, the input starts (816) on the preview of the virtual avatar (e.g., 680) and ends at a location within the message area (e.g., see FIGs. 6HH-6KK) (e.g., a gesture that starts with a finger contacting the preview of the virtual avatar (e.g., 680), continues with the finger dragging to the message area, and ends with the lift off of the finger in the message area (in some cases, the gesture may end on a particular message in the message area and the sticker is associated with that particular message and, optionally, moves as that message moves in the conversation)). The electronic device sends (818) the static virtual avatar (e.g., 691) to a participant (e.g., one or more remote users) associated with the communication (e.g., FIG. 6KK). In some embodiments, an animation is displayed in response to the gesture that shows the static virtual avatar being peeled off of the preview of the virtual avatar (FIGs. 6CC-6FF).

[0187] In some embodiments, the static virtual avatar (e.g., 691) has an appearance that is determined based on an expression of the face in the field of view of the camera at the time that input (e.g., 688) was detected on the preview of the virtual avatar (e.g., 680). In some embodiments, the electronic device, in response to detecting the start of the input on the preview of the virtual avatar, causes the preview of the virtual avatar to cease (820) to react to changes in

DK 2017 70393 A1 an appearance of a face that is in a field of view of the camera. This indicates to the user that the sticker has been generated and previews to the user the appearance of the sticker that will be sent if the sticker is dragged to the communication displayed in message are 609 by sending it to a user. This enhances the operability of the device by showing a preview of the sticker that will be generated without the user having to perform additional interactions or completing the full sticker generation gesture before seeing the resulting sticker, which makes for an improved and more efficient man-machine interface. This reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0188] In some embodiments, the preview of the virtual avatar (e.g., 680) resumes reacting to changes after the input moves away from the virtual avatar (e.g., the animation resumes when the static avatar is dragged toward the message conversation). In some embodiments, the preview of the virtual avatar (e.g., 680) ceases to react to changes in the appearance of the face until the input that is dragging the static avatar ends. Resuming the updates to the virtual avatar preview enables the user to compare the appearance of the sticker that was generated to other possible appearances of the virtual avatar that may potentially be the basis for a different/additional sticker. This enhances the operability of the device and makes the userdevice interface more efficient (e.g., by helping the user to achieve an intended result by providing feedback about other content that can be generated before the user sends the generated content) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0189] In some embodiments, the electronic device, in response to expiration of the period of time (e.g., the expiration of a timer for 5, 10, or 15 seconds or a user input that stops the period of time) for generating the animated virtual avatar, displays a send or confirmation affordance (e.g., 664) in place of the record affordance (e.g., a virtual record button is no longer displayed and instead a virtual send button is displayed in place of the virtual record button). The electronic device, in response to receiving input selecting the send or confirmation affordance (e.g., a tap gesture on the send affordance on a touch-sensitive display), sends (824) the generated animated virtual avatar to a remote user (e.g., see FIGs. 6U and 6X without first sending the animated virtual avatar to the message composition area 612 as shown in FIGs. 6 V

DK 2017 70393 A1 and 6W) (e.g., the animated virtual avatar is sent to a remote user associated with a messaging thread or session without the animated virtual avatar being placed first into another area of the messaging interface, such as a message composition area). Displaying a send or confirmation button in place of a record button after the recording of the animated virtual avatar is completed enables more information to be displayed in the interface by reusing areas occupied for buttons that are not applicable to the current state of the interface and by providing the user with more contextually relevant functionality. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by displaying more information/options on a display without cluttering the display with unused elements) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0190] In some embodiments, the electronic device, in response to expiration of the period of time for generating the animated virtual avatar, displays (822) a confirm affordance (e.g., 664) in place of the record affordance. In response to receiving input selecting the send affordance (e.g., via contact 667) (e.g., a tap gesture on the send affordance on a touch-sensitive display), the electronic device displays a representation of the animated virtual avatar (e.g., a static graphical element or the animated virtual avatar) in a message composition area (e.g., 612) of the messaging interface (e.g., FIG. 6V) (e.g., a region of the messaging interface that would display text typed on the keyboard). In some embodiments, the period of time is based on a predetermined amount of time (e.g., represented by progress indicator 656). The electronic device, after generating the animated virtual avatar, ceases to display the preview of the virtual avatar and displaying a looping version of the animated virtual avatar (e.g., FIG. 6T). The displaying of the looping version of the animated virtual avatar includes displaying the animation sequence two or more times (e.g., as described below with respect to method 900). Displaying a send or confirmation button in place of a record button after the recording of the animated virtual avatar is completed enables more information to be displayed in the interface by reuse areas occupied for buttons that are not applicable (or less applicable) to the current state of the interface. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by displaying more information/options on a display without cluttering the display

DK 2017 70393 A1 with unused elements) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0191] In some embodiments, the looping version of the animated virtual avatar is displayed using a first virtual avatar template (e.g., represented by element 644-4, or another element indicated by indicator 645 of FIG. 6N). The electronic device displays representations of a plurality of other virtual avatar templates (e.g., elements 644-1 to 644-7) (e.g., miniature generic versions of different virtual avatar templates, such a smiley faces, animals, robots, or other objects) including a representation of a second virtual avatar template (e.g., element 644-8 of FIG. 6Z), wherein the second virtual avatar template is different from the first virtual avatar template. In some embodiments, one or more of the virtual avatar templates in the plurality of virtual avatar templates are based on emojis that are available to be sent via the messaging application. The electronic device, after starting to display the looping version of the animated virtual avatar (e.g., FIG. 6T) and in response to receiving user input (e.g., 665) selecting the first virtual avatar template representation, updates the display of the looping version of the animated virtual avatar to reflect the second virtual avatar template (e.g., FIG. 6U) (e.g., while the animated virtual avatar is still based on the sequences of changes in the expression of the face, the animated virtual avatar’s appearance is change to reflect the new virtual avatar template. For example, the animated virtual avatar may change from a monkey to a robot but it will still reflect the same sequence of changes in the expression of the face in the field of view of the camera over time (e.g., see transition from FIG. 6T to FIG. 6U). Updating animated virtual avatars based on newly selected avatar templates allows a user to fine tune the multimedia content for an intended message by allowing for the selection of the style of animated virtual avatar after recording the movements and actions of the animated virtual avatar. Eliminating the need to rerecord animated virtual avatars to try new avatar templates enhances the operability of the device and makes the user-device interface more efficient (e.g., by eliminating repetitive generation of content) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0192] In some embodiments, the preview of the virtual avatar (e.g., 646) is automatically displayed in response to launching the virtual avatar generation interface. In some embodiments,

DK 2017 70393 A1 the preview of the virtual avatar is displayed, without user input, as soon as the virtual avatar generation interface is displayed.

[0193] In some embodiments, the electronic device, in response to detecting a characteristic (e.g., position, orientation, movement) of a first physical feature (e.g., a mouth smiling, a tongue sticking out, ear wiggling, eye brows raise, or any other movement of any other physical feature) of the face in the field of view of the camera, updates a first physical feature of the displayed preview of the virtual avatar based on the detected characteristic, wherein a type (e.g., eyes, eye brows, mouth, tongue, ears) of the first physical feature of the face is the same as a type of the first physical feature of the displayed preview. In some embodiments, if a user’s mouth opens, the virtual avatar’s mouth will open in response (e.g., FIG. 6O at 650-1 and 651-1). Similar results can be based on facial expressions. For example, if one or more movements of physical features or characteristics of the face are detected, the electronic device may determine that a predefined emotion is being displayed. In response, the displayed preview of the virtual avatar may be updated to reflect the predefined motion by updating the corresponding physical features or characteristics to reflect the detected facial expression. Mapping physical features of the user to like physical features of the virtual avatar enables a user to provide movements, expressions, and poses that provide inputs to the system that intuitively map onto the virtual avatar, without the need for cumbersome or time consuming touch or key inputs. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended result by mapping features of the user to the virtual avatar in a predictable manner and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0194] In some embodiments, the electronic device, in response to detecting a characteristic of a second physical feature of the face in the field of view of the camera, updates a second physical feature of the displayed preview of the virtual avatar based on the detected the characteristic, wherein a type of the second physical feature of the face is different than a type of the second physical feature of the displayed preview (e.g., FIG. 6O movement of eyebrows of 650-2 and ears of 651-2). In some embodiments, if a user is smiling indicating that the user is

DK 2017 70393 A1 happy, a different feature of the virtual avatar, such as a unicorn horn or a light on a robot, may change to reflect the smiling. Similar results can be based on facial expressions. For example, if one or more movements of physical features or characteristics of the face are detected, the electronic device may determine that a predefined emotion is being displayed. In response, the displayed preview of the virtual avatar is, optionally, updated to reflect the predefined motion by updating a different set of physical features or characteristics to reflect the detected facial expression. Mapping physical features of the user to different physical features of the virtual avatar enables a user to provide movements, expressions, and poses that provide inputs to the system that map to features of the avatar that the user cannot otherwise easily control. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended result by mapping features of the user to the virtual avatar so that additional features of the virtual avatar are controlled and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0195] In some embodiments, the electronic device, the electronic device, in response to detecting movement of the face in the field of view of the camera, updates a third physical feature of the displayed preview of the virtual avatar based on a physics model for the virtual avatar and the detected movement (e.g., FIG. 6O at 650-5 and 651-5). In some embodiments, for example, if the virtual avatar is based on a virtual avatar template for a puppy, then when the user’s face is detected as shaking, the virtual avatar’s face will shake and the virtual avatar’s ears might stick out to reflect the physics of the shaking motion even though the user’s ears did not stick out in response to the shaking. In some embodiments, the same physical feature of the displayed preview of the virtual avatar is updated based on movement of the corresponding feature of the face in the field of view of the camera and the physics model (e.g., an ear moves based on the movement of the user’s ear but also based on a physics model for a floppy puppy ear). Updating the virtual avatar based on a physics model for the virtual avatar enables the user to create a realistic and interactive virtual avatar that can communicate a wider range of nonverbal information. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to communicate an intended message using

DK 2017 70393 A1 more realistic movements of the virtual avatar) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0196] In some embodiments, the preview of the virtual avatar is based on a pre-defined virtual avatar template (e.g., avatar template associated with representation 644-4 of FIG. 6N). The electronic device updates the preview of the virtual avatar based on one or more predefined behaviors associated with the pre-defined virtual avatar template. In some embodiments, if no movement or change in facial expression is detected (e.g., 650-3 and 650-4) from the face in the field of view of the camera, the preview of the virtual avatar shows a predefined response (e.g., 651-4), such as blinking eyes, rotating a head, making a facial expression, or other action.

[0197] In some embodiments, the electronic device, in response to a determination that the face is no longer detected in the field of view of the camera (e.g., tracking of the face has failed because the face has moved out of the field of view of the camera, the face has been obscured from view of the camera, or the face has been repositioned so that the device can no longer accurately track the movement of features on the face), gradually fades the display of the preview of the virtual avatar (e.g., virtual avatar preview 646 would fade). In some embodiments, the device makes other modifications to the virtual avatar preview to indicate that it can no longer track a user’s face, such as degrading the virtual avatar preview from last information that the device detected, including changing the size, rotation, motion, etc. of the virtual avatar preview. In some embodiments, the electronic device, in response to a determination that the face is no longer detected in the field of view of the camera (e.g., tracking of the face has failed because the face has moved out of the field of view of the camera, the face has been obscured from view of the camera, or the face has been repositioned so that the device can no longer accurately track the movement of features on the face), displays a message indicating that the face is no longer being properly detected by the camera (e.g., a display prompt is displayed over virtual avatar 643 of FIG. 6N or in place of virtual avatar preview 646 of FIG. 6N). In some embodiments, the electronic device, in response to a determination that the face is no longer detected in the field of view of the camera (e.g., tracking of the face has failed because the face has moved out of the field of view of the camera, the face has been obscured from view

DK 2017 70393 A1 of the camera, or the face has been repositioned so that the device can no longer accurately track the movement of features on the face), updates the display of the preview of the virtual avatar based on a change in appearance of the face that was occurring during a time period before (e.g., immediately before or shortly before) the face was no longer detected in the field of view (e.g., device 600 repeatedly displays a transition from a smile to a frown or a movement of eyes). In some embodiments, updating the display of the preview of the virtual avatar based on a change in appearance of the face that was occurring during a time period before the face was no longer detected in the field of view of the camera includes gradually slowing the updating of the preview of the virtual avatar over time so that the updating of the virtual avatar gradually stops (e.g., an avatar that is turning slowly stops turning, eyes that are opening or closing slowly stop opening or closing, a mouth that was opening or closing slowly stops opening or closing). Displaying feedback about whether the virtual avatar preview is tracking the user’s face enables the user to determine whether the device is being held properly and whether the conditions for detection of the user’s face are proper. Providing improved feedback to the user of a state of the device, enhances the operability of the device, and makes the user-device interface more efficient by providing better continuity of the user interface through indications that the device is still trying to track the user’s face. This provides for a better and more intuitive man-machine interface and will result in the user continuing to interact with the device even when the device cannot track the user’s face.

[0198] Note that details of the processes described above with respect to method 800 (e.g., FIGs. 8A-8B) are also applicable in an analogous manner to the methods described below. For example, method 900 optionally includes one or more of the characteristics of the various methods described above with reference to method 800. For example, the generation of stickers described above with respect to method 800 is optionally incorporated with the user interface described below with respect to method 900. As another example, the muting of sound prior to sending an animated virtual avatar (e.g., an animated virtual avatar) as described above with respect to method 800 is optionally incorporated with the user interface described below with respect to method 900. For brevity, these details are not repeated below.

DK 2017 70393 A1 [0199] The operations in the information processing methods described above are, optionally, implemented by running one or more functional modules in an information processing apparatus such as general purpose processors (e.g., as described with respect to FIGs. 1A, 3, 5A) or application specific chips. Further, the operations described above with reference to FIGs. 8A and 8B are, optionally, implemented by components depicted in FIGs. 1A-1B. For example, detecting an input in the virtual avatar generation interface (806) is, optionally, implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive surface 604, and event dispatcher module 174 delivers the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as selection of an object on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGs. 1A-1B.

[0200] FIGs. 9A-9B are a flow diagram illustrating a method for 900 using an electronic device in accordance with some embodiments. Method 900 is performed at a device (e.g., 100, 300, 500, 600) with a display and a camera. Some operations in method 900 are, optionally, combined, the order of some operations are, optionally, changed, and some operations are, optionally, omitted.

[0201] As described below, method 900 provides an intuitive way for generating and sending emojis, such as virtual avatars. The method reduces the cognitive burden on a user for generating and sending emojis, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to generate and send emojis faster and more efficiently conserves power and increases the time between battery charges.

DK 2017 70393 A1 [0202] An electronic device (e.g., 600), having a camera (e.g., configured with one or more sensors for capturing data representing visible light, IR light, depth data, etc.) and a display (e.g., 601), displays (902) a virtual avatar generation interface (e.g., 643 of FIG. 6N) (e.g., selecting emojis, generating static emojis, and recording animated emojis). The electronic device displays (904) a preview of a virtual avatar (e.g., 646 of FIG. 6N) (e.g., a 2D or 3D computer generated graphical object, in some cases intended to convey a non-verbal message, such as an emotion or reaction) in the virtual avatar generation interface (e.g., a moving emoji selected from multiple different available emoji styles or templates). The preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera (e.g., FIG. 6O) (e.g., the animated emoji will reflect the user’s head movements, facial expressions, and orientation as detected in image data from the one or more image sensors). The electronic device receives (906) a request (e.g., contact 652) to generate an animated virtual avatar based on changing facial expressions of the face that is in the field of view of the camera. In response to receiving the request to generate the animated virtual avatar, the electronic device records (908) (e.g., FIGs. 6Q-6S) a sequence of facial expressions of the face in the field of view of the camera (e.g., the sequence includes a series of data points that for provide a mapping of points that can be applied a virtual avatar template to generate the animated virtual avatar). The electronic device, after recording the facial expressions of the face that is in the view of the camera, displays (910) a looping version (e.g., FIGs. 6T and 6U) of an animated virtual avatar (e.g., 659) that includes an animation sequence based on the sequence of facial expressions recorded in response to the request to generate the animate virtual avatar (e.g., the animated virtual avatar is displaying by sequentially mapping the series of data points representing the recorded facial expressions to a predefined animated virtual avatar template). The electronic device displays the looping version of the animated virtual avatar two or more times. In some embodiments, recording the sequence of facial expressions includes recording a time sequence of values for discrete mapping points of a predefined virtual avatar template. Displaying a looping version of an animated virtual avatar enables the user to subsequently review the animated virtual avatar content to understand whether the appropriate message is being communicated. Providing improved visual feedback to the user enhances the operability of the device, reduces the instances of errors, and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended result by

DK 2017 70393 A1 providing feedback indicative of an input that will cause the device to generate the intended result and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0203] In some embodiments, the electronic device stops the recording of the sequence of facial expressions in response to the expiration of a timer (e.g., as represented by progress indicator 656) (e.g., a 5, 10, or 15 second timer). In some embodiments, the electronic device stops the recording of the sequence of facial expressions in response to receiving user input (e.g., contact 658) (e.g., a user tap on a virtual button displayed on the display). Limiting the time of an animated virtual avatar recording enables a user to create animated virtual avatar recordings while limiting the impact on the computing resources (e.g., storage) of the device. This enhances the operability of the device by preserving the device’s computing resources.

[0204] In some embodiments, the electronic device replaces (912) display of the preview with the display of the looping version of the animated virtual avatar (e.g., see transition from FIG. 6S to FIG. 6T) (e.g., in response to the recording of the sequence of facial expressions being completed, the generated animated virtual avatar is played back to the user in a loop). Playing a looping version of the recorded animated emoji automatically enables the user to review the animated emoji prior to deciding whether to send, delete, or save the animated emoji. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended result by providing feedback indicative result before the user commits to the result and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0205] In some embodiments, the request to generate the animated virtual avatar includes the selection of a record affordance (e.g., 648) displayed in the virtual avatar generation interface. The electronic device, after recording the facial expressions of the face that is in the view of the camera, replaces display of the record affordance with a send or a confirm affordance (e.g., 664). In some embodiments, the send affordance operates as explained above with respect to method 800. Recording an animated virtual avatar in response to selection of a record affordance

DK 2017 70393 A1 enables a user to use the virtual avatar preview to verify that the device is tracking the user and the currently selected virtual avatar template is consistent with the message that the user wishes to convey. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended result by providing a preview of the intended result prior to the user generating the intended result and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0206] In some embodiments, the looping version of the animated virtual avatar is displayed (918) using a first virtual avatar template (e.g., avatar template corresponding to element 644-4). The electronic device displays representations of a plurality of other virtual avatar templates (e.g., elements 644-1 to 644-7) (e.g., miniature generic versions of different virtual avatar templates, such a smiley faces, animals, robots, or other objects) including a representation of a second virtual avatar template (e.g., element 644-8 of FIG. 6Z). The second virtual avatar template is different from the first virtual avatar template. In some embodiments, one or more of the virtual avatar templates in the plurality of virtual avatar templates are based on emoji that are available to be sent via the messaging application. After starting to display the looping version of the animated virtual avatar and in response to receiving user input selecting the first virtual avatar template representation, the electronic device updates (922) the display of the looping version of the animated virtual avatar to reflect the second virtual avatar template (e.g., while the animated virtual avatar is still based on the sequences of changes in the expression of the face, the animated virtual avatar’s appearance is change to reflect the new virtual avatar template). For example, the animated virtual avatar may change from a monkey to a robot but it will still reflect the same sequence of changes in the expression of the face in the field of view of the camera over time (e.g., see transition from FIG. 6T to 6U). In some embodiments, the electronic device displays (914) a plurality of representations of virtual avatar templates (e.g., miniature generic versions of different virtual avatar templates, such a smiley faces, animals, robots, or other objects) including a representation of a first virtual avatar template. In response to receiving user input corresponding to a selection of the representation of the first virtual avatar template, the electronic device updates (916) the display of the looping version of the animated virtual avatar to correspond to the first virtual avatar template (e.g., changing the animation to be 72

DK 2017 70393 A1 of a robot based on a robot virtual avatar template instead of a puppy based on a puppy virtual avatar template without the user having to rerecord any facial expressions). Updating animated virtual avatars based on newly selected avatar templates allows a user to fine tune the multimedia content for an intended message by allowing for the selection of the style of animated virtual avatar after recording the movements and actions of the animated virtual avatar. Eliminating the need to rerecord animated virtual avatars to preview new avatar templates enhances the operability of the device and makes the user-device interface more efficient (e.g., by eliminating repetitive generation of content) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0207] In some embodiments, the preview virtual avatar is based on a second avatar template. In response to detecting a first characteristic of a first physical feature (e.g., movement of a user’s eyebrows) of the face in the field of view of the camera (e.g., 650-2 of FIG. 6O), the electronic device updates (920) a first physical feature of the displayed preview of the virtual avatar based on the detected first characteristic (e.g., causing the preview of the virtual avatar to move its eyebrows). The first physical feature of the displayed preview has a first feature type (e.g., an eyebrow). After receiving user input corresponding to the selection of the first graphical element (e.g., switching the avatar template from a puppy to a monkey) and in response to detecting a second characteristic of the first physical feature (e.g., movement of a user’s eyebrows) of the face in the field of view of the camera, the electronic device updates (922) a second physical feature (e.g., 651-2 of FIG. 6O) of the displayed preview of the virtual avatar based on the detected second characteristic (e.g., moving the monkey’s ears), wherein the second physical feature of the displayed preview has a second feature type (e.g., ears) different than the first feature type (e.g., eyebrows). Mapping the same physical feature of a user to different physical features of different avatar templates enables the user to have a wider range of options for communicating a message by having the same inputs produce a variety of virtual avatars. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended message by providing more choices to convey the message) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

DK 2017 70393 A1 [0208] In some embodiments, the electronic device, in response to receiving user input corresponding to a request to scroll (e.g., via contact 676 of FIGs. 6Y-6AA) the plurality of representations of virtual avatar templates, scrolls the display of the plurality of representations of virtual avatar templates to display a second graphical element not part of the plurality of representations of virtual avatar templates. In some embodiments, the scrolling is based on a velocity of the user input corresponding to the request. Scrolling through virtual avatar template enables a user to quickly see the different options for the virtual avatar. Additionally, scrolling the display of the plurality of representations of virtual avatar templates enables the user to see the previous and next virtual avatar template. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended result by providing feedback indicative of an input that will cause the device to generate the intended result and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0209] In some embodiments, the speed of scrolling gradually decreases over time after detecting an end of the user input (e.g., the scrolling gradually stops as though the plurality of representations of virtual avatars had an inertia that was being gradually slowed by friction). Gradually decreasing the speed of scroll over time enables the user to continue to see different virtual avatar template options without having to provide additional input. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended result by providing feedback of possible results without requiring additional interaction and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0210] In some embodiments, the electronic device, in response to receiving the user input corresponding to the request, generates audible output and/or tactile output that corresponds to the currently selected virtual avatar template changing from one virtual avatar template to a different virtual avatar template. For example, audible and/or tactile outputs are generated as each of a plurality of the representations of the virtual avatar templates scroll past a location that

DK 2017 70393 A1 indicates a currently selected virtual avatar template. Generating audible or tactile feedback enables the user to determine when a new selection has occurred. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended result by providing feedback indicative of when a new selection is made and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0211] In some embodiments, the electronic device, in response to receiving user input on the animated virtual avatar, the input corresponding to a request to save the animated virtual avatar, stores data for the animated virtual avatar to a database on the electronic device (e.g., FIGs. 6CC-6GG). For example, the electronic device stores data representing the animated virtual avatar to a directory or library in non-volatile storage in the electronic device.

[0212] In some embodiments, the electronic device receives a request (e.g., contact 688) to send the animated virtual avatar to a remote user of a remote device (e.g., FIGs. 6HH-6KK). In accordance with a determination that the remote device meets a first set of criteria (e.g., the remote device has a required version of a required application to play the first version of the animate virtual avatar), the electronic device sends a first version of the animated virtual avatar to a user of the remote device (e.g., sending non-graphical data representing the recorded sequence of facial expressions and an indication of an virtual avatar template so that the remote device can reproduce the animated virtual avatar). In accordance with a determination that the remote device does not meet the first set of criteria (e.g., the remote device does not have an appropriate messaging application or version of a messaging application to play the first version of the animated virtual avatar), the electronic device sends a second version (e.g., sending a video file representing the animated virtual avatar) of the animated virtual avatar different than the first version to the user of the remote device. Determining which version of an animated virtual avatar to send to a remote user saves the device’s resource by sending only the minimal amount of compatible information to the remote user. Further, doing so reduces the need for the user to re-send information in a more compatible format (e.g., in response to a remote user indicating that the initial format was not viewable). Efficient and effective data transfer

DK 2017 70393 A1 enhances the operability of the device, which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0213] In some embodiments, the electronic device, while displaying the looping version of the animated virtual avatar, plays (924) audio data based on sound recorded while recording the sequence of facial expressions and based on an audio filter associated with a predefined avatar template. In some embodiments, the electronic device, while displaying the looping version of the animated virtual avatar, plays audio data based on sound recorded while recording the sequence of facial expressions. In response to receiving user input corresponding to a selection of a mute affordance (e.g., 662 of FIG. 6T and 6U), the electronic device ceases to play the audio data. Playing filtered audio for an animated virtual avatar based on a filter specific to the avatar template for the virtual avatar enables a user to more effectively communicate a message by providing for more options in how the message is communicated and a more engaging animated virtual avatar. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended message by providing the user with more options on how the message is conveyed) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0214] In some embodiments, the electronic device, in response (926) to receiving a request to send the animated virtual avatar to a remote user and in accordance with a determination that the request (e.g., contact 667) to send the animated virtual avatar to the remote user was received while audio data associated with the display of the looping version of the animated virtual avatar was muted, sends (928) data representing the animated virtual avatar to the remote user without sending the sound data for the animated virtual avatar. In accordance with a determination that the request to send the animated virtual avatar to the remote user was received while audio data associated with the display of the looping version of the animated virtual avatar was not muted, the electronic device sends (930) data representing the animated virtual avatar to the remote user along with sound data for the animated virtual avatar. Sending an animated virtual avatar without sound when the user has muted the sound in the playback of the animated virtual avatar enables the user to efficiently choose whether sound is included in the message that is sent to a

DK 2017 70393 A1 remote user. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended result with minimal interactions) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0215] In some embodiments, the electronic device, in response to receiving the request (e.g., contact 652) to generate the animated virtual avatar, records a first face movement of the face that is in the view of the camera, wherein displaying the looping version of an animated virtual avatar includes animating the virtual avatar based on a physics model for the animated virtual avatar and the first face movement (e.g., see image data 650-5 and update 651-5 of FIG. 6O). Updating the animated virtual avatar based on a physics model for the virtual avatar enables the user to create a realistic and interactive virtual avatar that can communicate a wider range of non-verbal communication. This enhances the operability of the device and makes the userdevice interface more efficient (e.g., by helping the user to communicate an intended message using more realistic movements of the virtual avatar) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0216] In some embodiments, the electronic device, in response to detecting that a particular feature of the face that is in the view of the camera while recording the sequence of facial expressions is maintained in a particular pose for more than a threshold amount of time (e.g., see 650-4 and 650-5 of FIG. 6O), adds, to the animated virtual avatar, a predefined animated expression (e.g., see 651-5 of FIG. 6O) that corresponds to the particular pose of the face. For example, if the face has a neutral expression for a predetermined period of time, a predefined movement, such as a head turn or a wink, is added to the animated virtual avatar. As another example, if the face has an angry expression for a predetermined period of time, one or more additional features, such as color or steam coming out of ears, that connote anger are added to the animated virtual avatar. Updating the animated virtual avatar based on the device detecting that a feature of the user’s face is maintained in a particular pose for a threshold amount of time enables a user to add more actions to the animated virtual avatar than is possible with only facial expressions, features, and movements. This enhances the operability of the device and makes

DK 2017 70393 A1 the user-device interface more efficient (e.g., by helping the user to achieve an intended result by providing additional mechanism to communicate actions that do not otherwise correspond to an easily achievable facial expression, movement, or feature) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0217] In some embodiments, the electronic device, while recording the sequence of facial expression, in response receiving user input via an input mechanism separate from the camera (e.g., a touch on a touch-sensitive surface, a movement of the electronic device detected by motion sensors, activation of a button, or other input), adds a first facial expression to the sequence of facial expressions (e.g., record a happy facial expression, facial expression with a tongue sticking out, or any other facial expression that was not actually recorded as a facial expression that was made by the face in the field of view of the camera while recording facial expressions for inclusion in the animated virtual avatar). The first facial expression is based on the user input received via the input mechanism. In some embodiments, while the animated virtual avatar is looping, the user can use touch screen controls to add additional expressions to the animated virtual avatar, so that as the animated virtual avatar is looping, the user can gradually add expressions to the an animated virtual avatar, so that the animated virtual avatar includes the changes in expression selected by the user, even if those changes in expression differ from the changes in expression recorded based on the facial expressions of the face in the field of view of the camera (e.g., the user’s face) when initially creating the animated virtual avatar. Updating the animated virtual avatar based on user input other than captured with a camera enables a user to add more actions to the animated virtual avatar than is possible with only facial expressions, features, and movements. This enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended result by providing additional mechanism to communicate actions that do not otherwise correspond to an easily achievable facial expression, movement, or feature) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

DK 2017 70393 A1 [0218] Note that details of the processes described above with respect to method 900 (e.g., FIGs. 9A-9B) are also applicable in an analogous manner to the methods described above. For example, method 900 optionally includes one or more of the characteristics of the various methods described above with reference to method 800. For example, displaying an animated virtual avatar preview based on a sequence of record facial features, movements, and/or expressions and based on a framework associated with an avatar template as described with respect to method 900 can be applied to the sticker and animated virtual avatar interface described with respect to method 800, above.

[0219] The operations in the information processing methods described above are, optionally, implemented by running one or more functional modules in an information processing apparatus such as general purpose processors (e.g., as described with respect to FIGs.

IA, 3, and 5A) or application specific chips. Further, the operations described above with reference to FIGS. 9A and 9B are, optionally, implemented by components depicted in Figs. 1AIB. For example, receiving a request to generate an animated virtual avatar (906) is, optionally, implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive surface 604, and event dispatcher module 174 delivers the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as selection of an object on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in Figs. 1A-1B.

Exemplary methods, devices, electronic devices, and non-transitory computer-readable storage media are set out in the following items:

DK 2017 70393 A1

1. A method comprising:

at an electronic device having a camera and a display:

displaying a virtual avatar generation interface;

displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein the preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera;

while displaying the preview of the virtual avatar, detecting an input in the virtual avatar generation interface;

in response to detecting the input in the virtual avatar generation interface:

in accordance with a determination that the input starts on the preview of the virtual avatar, generating a static virtual avatar that represents an expression of the face in the field of view of the camera at a respective time, wherein the respective time is determined based on a timing of the input; and in accordance with a determination that the input includes activation of a record affordance in the virtual avatar generation interface, generating an animated virtual avatar that represents a sequences of changes in the expression of the face in the field of view of the camera over a period of time, wherein the period of time is determined based on a timing of the input.

2. The method of item 1 further comprising:

displaying a messaging interface including a message area, wherein the message area includes messages from two or more participants of a communication, the virtual avatar generation interface is displayed concurrently with the messaging interface.

3. The method of item 2, wherein displaying the virtual avatar generation interface includes replacing display of a virtual keyboard of the messaging interface with display of the virtual avatar generation interface.

4. The method of any one of items 2-3, wherein the messaging interface includes a message composition area and the input is a tap on the preview of the virtual avatar, the method further comprising:

DK 2017 70393 A1 in response to detecting the input in the virtual avatar generation interface, displaying the static virtual avatar in the message composition area.

5. The method of any one of items 1-4, wherein the avatar generation interface includes a static virtual avatar area that includes a collection of one or more previously generated virtual avatars, the method further comprising:

in response to a user input, adding the generated virtual avatar to the collection of one or more previously generated virtual avatars.

6. The method of item 5, after adding the virtual avatar to the collection of virtual avatars, receiving, from the user a request to share the collection of virtual avatars with a second user and in response, sending the collection of virtual avatars to the second user.

7. The method of any one of items 2-6, wherein the input starts on the preview of the virtual avatar and ends at a location within the message area the method further comprising:

sending the static virtual avatar to a participant associated with the communication.

8. The method of item 7, wherein the static virtual avatar has an appearance that is determined based on an expression of the face in the field of view of the camera at the time that input was detected on the preview of the virtual avatar.

9. The method of item 7 further comprising:

in response to detecting the start of the input on the preview of the virtual avatar, the preview of the virtual avatar ceases to react to changes in an appearance of a face that is in a field of view of the camera.

10. The method of any one of items 1 -6 further comprising:

in response to expiration of the period of time for generating the animated virtual avatar, displaying a send affordance in place of the record affordance;

in response to receiving input selecting the send affordance, sending the generated animated virtual avatar to a remote user.

11. The method of any one of items 2-6 further comprising:

DK 2017 70393 A1 in response to expiration of the period of time for generating the animated virtual avatar, displaying a confirm affordance in place of the record affordance;

in response to receiving input selecting the send affordance, displaying a representation of the animated virtual avatar in a message composition area of the messaging interface.

12. The method of any one of items 1-11, wherein the period of time is based on a predetermined amount of time, the method further comprising:

after generating the animated virtual avatar, ceasing to display the preview of the virtual avatar and displaying a looping version of the animated virtual avatar, wherein displaying the looping version of the animated virtual avatar includes displaying the animation sequence two or more times.

13. The method of item 12, wherein the looping version of the animated virtual avatar is displayed using a first virtual avatar template and the method further comprises:

displaying representations of a plurality of other virtual avatar templates including a representation of a second virtual avatar template, wherein the second virtual avatar template is different from the first virtual avatar template;

after starting to display the looping version of the animated virtual avatar and in response to receiving user input selecting the first virtual avatar template representation, updating the display of the looping version of the animated virtual avatar to reflect the second virtual avatar template.

14. The method of any one of items 1-13, wherein the preview of the virtual avatar is automatically displayed in response to launching the virtual avatar generation interface.

15. The method of any one of items 1-14 further comprising:

in response to detecting a characteristic of a first physical feature of the face in the field of view of the camera, updating a first physical feature of the displayed preview of the virtual avatar based on the detected characteristic, wherein a type of the first physical feature of the face is the same as a type of the first physical feature of the displayed preview.

16. The method of any one of items 1-15, further comprising:

DK 2017 70393 A1 in response to detecting a characteristic of a second physical feature of the face in the field of view of the camera, updating a second physical feature of the displayed preview of the virtual avatar based on the detected the characteristic, wherein a type of the second physical feature of the face is different than a type of the second physical feature of the displayed preview.

17. The method of any one of items 1-16, further comprising:

in response to detecting movement of the face in the field of view of the camera, updating a third physical feature of the displayed preview of the virtual avatar based on a physics model for the virtual avatar and the detected movement.

18. The method of any one of items 1-17, wherein the preview of the virtual avatar is based on a pre-defined virtual avatar template, the method further comprising:

updating the preview of the virtual avatar based on one or more predefined behaviors associated with the pre-defined virtual avatar template.

19. The method of any one of items 1-18 further comprising:

in response to a determination that the face is no longer detected in the field of view of the camera, gradually fade the display of the preview of the virtual avatar.

20. The method of any one of items 1-19 further comprising:

in response to a determination that the face is no longer detected in the field of view of the camera, displaying a message indicating that the face is no longer being properly detected by the camera.

21. The method of any one of items 1 -20 further comprising:

in response to a determination that the face is no longer detected in the field of view of the camera, updating the display of the preview of the virtual avatar based on a change in appearance of the face that was occurring during a time period before the face was no longer detected in the field of view.

22. The method of item 21, wherein updating the display of the preview of the virtual avatar based on a change in appearance of the face that was occurring during a time period before the

DK 2017 70393 A1 face was no longer detected in the field of view of the camera includes gradually slowing the updating of the preview of the virtual avatar over time so that the updating of the virtual avatar gradually stops

23. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display and a camera, the one or more programs including instructions for performing the method of any of items 1 -22.

24. An electronic device, comprising:

a display;

a camera;

one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any of items 1 -22.

25. An electronic device, comprising:

a display;

a camera; and means for performing the method of any of items 1 - 22.

26. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display and a touch-sensitive surface, the one or more programs including instructions for:

displaying a virtual avatar generation interface;

displaying a preview of a virtual avatar ( in the virtual avatar generation interface, wherein the preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera;

in response to detecting the input in the virtual avatar generation interface:

27. An electronic device, comprising:

a display;

a camera;

one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for:

displaying a virtual avatar generation interface;

in response to detecting the input in the virtual avatar generation interface:

DK 2017 70393 A1

28. An electronic device, comprising:

a display for displaying a virtual avatar generation interface and displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein the preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera;

a camera;

means for, while displaying the preview of the virtual avatar, detecting an input in the virtual avatar generation interface; and means for, in response to detecting the input in the virtual avatar generation interface: in accordance with a determination that the input starts on the preview of the virtual avatar, generating a static virtual avatar that represents an expression of the face in the field of view of the camera at a respective time, wherein the respective time is determined based on a timing of the input; and in accordance with a determination that the input includes activation of a record affordance in the virtual avatar generation interface, generating an animated virtual avatar that represents a sequences of changes in the expression of the face in the field of view of the camera over a period of time, wherein the period of time is determined based on a timing of the input.

29. A method comprising:

at an electronic device having a camera and a display:

displaying a virtual avatar generation interface;

displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera;

receiving a request to generate an animated virtual avatar based on changing facial expressions of the face that is in the field of view of the camera;

in response to receiving the request to generate the animated virtual avatar, recording a sequence of facial expressions of the face in the field of view of the camera;

after recording the facial expressions of the face that is in the view of the camera, displaying a looping version of an animated virtual avatar that includes an animation sequence based on the sequence of facial expressions recorded in response to the request to generate the

DK 2017 70393 A1 animate virtual avatar, wherein displaying the looping version of the animated virtual avatar includes displaying the animation sequence two or more times.

30. The method of item 29 further comprising:

stopping the recording of the sequence of facial expressions in response to the expiration of a timer.

31. The method of item 29 further comprising:

stopping the recording of the sequence of facial expressions in response to receiving user input.

32. The method of any one of items 29-31 further comprising:

replacing display of the preview with the display of the looping version of the animated virtual avatar.

33. The method of any one of items 29-32, wherein the request to generate the animated virtual avatar includes the selection of a record affordance displayed in the virtual avatar generation interface, the method further comprising:

after recording the facial expressions of the face that is in the view of the camera, replacing display of the record affordance with a send affordance.

34. The method of any one of items 29-33, wherein the looping version of the animated virtual avatar is displayed using a first virtual avatar template and the method further comprises:

35. The method of any one of item 34, wherein the preview virtual avatar is based on a second avatar template, the method further comprising:

DK 2017 70393 A1 in response to detecting a first characteristic of a first physical feature of the face in the field of view of the camera, updating a first physical feature of the displayed preview of the virtual avatar based on the detected first characteristic, wherein the first physical feature of the displayed preview has a first feature type; and after receiving user input corresponding to the selection of the first graphical element and in response to detecting a second characteristic of the first physical feature of the face in the field of view of the camera, updating a second physical feature of the displayed preview of the virtual avatar based on the detected second characteristic, wherein the second physical feature of the displayed preview has a second feature type different than the first feature type.

36. The method of any one of items 29-35 further comprising:

displaying a plurality of representations of virtual avatar templates including a representation of a first virtual avatar template;

in response to receiving user input corresponding to a selection of the representation of the first virtual avatar template, updating the display of the looping version of the animated virtual avatar to correspond to the first virtual avatar template.

37. The method of item 35 or 36 further comprising:

in response to receiving user input corresponding to a request to scroll the plurality of representations of virtual avatar templates, scrolling the display of the plurality of representations of virtual avatar templates to display a second graphical element not part of the plurality of representations of virtual avatar templates, wherein the scrolling is based on a velocity of the user input corresponding to the request.

38. The method of item 37 further comprising:

in response to receiving the user input corresponding to the request, generating audible output and/or tactile output that corresponds to the currently selected virtual avatar template changing from one virtual avatar template to a different virtual avatar template.

39. The method of any one of items 29-38 further comprising:

DK 2017 70393 A1 in response to receiving user input on the animated virtual avatar, the input corresponding to a request to save the animated virtual avatar, storing data for the animated virtual avatar to a database on the electronic device.

40. The method of any one of items 29-39, wherein recording the sequence of facial expressions includes recording a time sequence of values for discrete mapping points of a predefined virtual avatar template.

41. The method of any one of items 29-40 further comprising:

receiving a request to send the animated virtual avatar to a remote user of a remote device;

in accordance with a determination that the remote device meets a first set of criteria, sending a first version of the animated virtual avatar to a user of the remote device; and in accordance with a determination that the remote device does not meet the first set of criteria, sending a second version of the animated virtual avatar different than the first version to the user of the remote device.

42. The method of any one of items 29-41 further comprising:

while displaying the looping version of the animated virtual avatar, playing audio data based on sound recorded while recording the sequence of facial expressions and based on an audio filter associated with a predefined avatar template.

43. The method of any one of items 29-41 further comprising:

while displaying the looping version of the animated virtual avatar, playing audio data based on sound recorded while recording the sequence of facial expressions; and in response to receiving user input corresponding to a selection of a mute affordance, ceasing to play the audio data.

44. The method of any one of items 29-43 further comprising:

in response to receiving a request to send the animated virtual avatar to a remote user: in accordance with a determination that the request to send the animated virtual avatar to the remote user was received while audio data associated with the display of the

DK 2017 70393 A1 looping version of the animated virtual avatar was muted, sending data representing the animated virtual avatar to the remote user without sending the sound data for the animated virtual avatar;

and in accordance with a determination that the request to send the animated virtual avatar to the remote user was received while audio data associated with the display of the looping version of the animated virtual avatar was not muted, sending data representing the animated virtual avatar to the remote user along with sound data for the animated virtual avatar.

45. The method of any one of items 29-44 further comprising:

in response to receiving the request to generate the animated virtual avatar, recording a first face movement of the face that is in the view of the camera, wherein displaying the looping version of an animated virtual avatar includes animating the virtual avatar based on a physics model for the animated virtual avatar and the first face movement.

46. The method of any one of items 29-45 further comprising:

in response to detecting that a particular feature of the face that is in the view of the camera while recording the sequence of facial expressions is maintained in a particular pose for more than a threshold amount of time, adding, to the animated virtual avatar, a predefined animated expression that corresponds to the particular pose of the face.

47. The method of any one of items 29-46 further comprising:

while recording the sequence of facial expression, in response receiving user input via an input mechanism separate from the camera, adding a first facial expression to the sequence of facial expressions, wherein the first facial expression is based on the user input received via the input mechanism.

48. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display and a camera, the one or more programs including instructions for performing the method of any of items 29 - 47.

49. An electronic device, comprising:

DK 2017 70393 A1 a display;

a camera;

one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any of items 29 - 47.

50. An electronic device, comprising:

a display;

a camera; and means for performing the method of any of items 29 - 47.

51. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display and a touch-sensitive surface, the one or more programs including instructions for:

displaying a virtual avatar generation interface;

after recording the facial expressions of the face that is in the view of the camera, displaying a looping version of an animated virtual avatar that includes an animation sequence based on the sequence of facial expressions recorded in response to the request to generate the animate virtual avatar, wherein displaying the looping version of the animated virtual avatar includes displaying the animation sequence two or more times.

52. An electronic device, comprising:

a display;

a camera;

DK 2017 70393 A1 one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for:

displaying a virtual avatar generation interface;

53. An electronic device, comprising:

a display for displaying a virtual avatar generation interface and displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera;

a camera;

means for receiving a request to generate an animated virtual avatar based on changing facial expressions of the face that is in the field of view of the camera;

means for, in response to receiving the request to generate the animated virtual avatar, recording a sequence of facial expressions of the face in the field of view of the camera;

means for after recording the facial expressions of the face that is in the view of the camera, causing display of a looping version of an animated virtual avatar that includes an animation sequence based on the sequence of facial expressions recorded in response to the request to generate the animate virtual avatar, wherein displaying the looping version of the animated virtual avatar includes displaying the animation sequence two or more times.

DK 2017 70393 A1 [0220] The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.

[0221] Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.

Claims

What is claimed is:

1. A method comprising:

at an electronic device having a camera and a display:

displaying a virtual avatar generation interface;

displaying a preview of a virtual avatar in the virtual avatar generation interface, wherein the preview of the virtual avatar reacts to changes in an appearance of a face that is in a field of view of the camera;

while displaying the preview of the virtual avatar, detecting an input in the virtual avatar generation interface;

in response to detecting the input in the virtual avatar generation interface:

in accordance with a determination that the input starts on the preview of the virtual avatar, generating a static virtual avatar that represents an expression of the face in the field of view of the camera at a respective time, wherein the respective time is determined based on a timing of the input; and in accordance with a determination that the input includes activation of a record affordance in the virtual avatar generation interface, generating an animated virtual avatar that represents a sequences of changes in the expression of the face in the field of view of the camera over a period of time, wherein the period of time is determined based on a timing of the input.
2. The method of claim 1 further comprising:

displaying a messaging interface including a message area, wherein the message area includes messages from two or more participants of a communication, the virtual avatar generation interface is displayed concurrently with the messaging interface.
3. The method of claim 2, wherein displaying the virtual avatar generation interface includes replacing display of a virtual keyboard of the messaging interface with display of the virtual avatar generation interface.

DK 2017 70393 A1
4. The method of any one of claims 2-3, wherein the messaging interface includes a message composition area and the input is a tap on the preview of the virtual avatar, the method further comprising:

in response to detecting the input in the virtual avatar generation interface, displaying the static virtual avatar in the message composition area.
5. The method of any one of claims 1-4, wherein the avatar generation interface includes a static virtual avatar area that includes a collection of one or more previously generated virtual avatars, the method further comprising:

in response to a user input, adding the generated virtual avatar to the collection of one or more previously generated virtual avatars.
6. The method of claim 5, after adding the virtual avatar to the collection of virtual avatars, receiving, from the user a request to share the collection of virtual avatars with a second user and in response, sending the collection of virtual avatars to the second user.
7. The method of any one of claims 2-6, wherein the input starts on the preview of the virtual avatar and ends at a location within the message area the method further comprising:

sending the static virtual avatar to a participant associated with the communication.
8. The method of claim 7, wherein the static virtual avatar has an appearance that is determined based on an expression of the face in the field of view of the camera at the time that input was detected on the preview of the virtual avatar.
9. The method of claim 7 further comprising:

in response to detecting the start of the input on the preview of the virtual avatar, the preview of the virtual avatar ceases to react to changes in an appearance of a face that is in a field of view of the camera.
10. The method of any one of claims 1-6 further comprising:

in response to expiration of the period of time for generating the animated virtual avatar, displaying a send affordance in place of the record affordance;

DK 2017 70393 A1 in response to receiving input selecting the send affordance, sending the generated animated virtual avatar to a remote user.
11. The method of any one of claims 2-6 further comprising:

in response to expiration of the period of time for generating the animated virtual avatar, displaying a confirm affordance in place of the record affordance;

in response to receiving input selecting the send affordance, displaying a representation of the animated virtual avatar in a message composition area of the messaging interface.
12. The method of any one of claims 1-11, wherein the period of time is based on a predetermined amount of time, the method further comprising:

after generating the animated virtual avatar, ceasing to display the preview of the virtual avatar and displaying a looping version of the animated virtual avatar, wherein displaying the looping version of the animated virtual avatar includes displaying the animation sequence two or more times.
13. The method of claim 12, wherein the looping version of the animated virtual avatar is displayed using a first virtual avatar template and the method further comprises:

displaying representations of a plurality of other virtual avatar templates including a representation of a second virtual avatar template, wherein the second virtual avatar template is different from the first virtual avatar template;

after starting to display the looping version of the animated virtual avatar and in response to receiving user input selecting the first virtual avatar template representation, updating the display of the looping version of the animated virtual avatar to reflect the second virtual avatar template.
14. The method of any one of claims 1-13, wherein the preview of the virtual avatar is automatically displayed in response to launching the virtual avatar generation interface.
15. The method of any one of claims 1-14 further comprising:

in response to detecting a characteristic of a first physical feature of the face in the field of view of the camera, updating a first physical feature of the displayed preview of the virtual

DK 2017 70393 A1 avatar based on the detected characteristic, wherein a type of the first physical feature of the face is the same as a type of the first physical feature of the displayed preview.
16. The method of any one of claims 1-15, further comprising:

in response to detecting a characteristic of a second physical feature of the face in the field of view of the camera, updating a second physical feature of the displayed preview of the virtual avatar based on the detected the characteristic, wherein a type of the second physical feature of the face is different than a type of the second physical feature of the displayed preview.
17. The method of any one of claims 1-16, further comprising:

in response to detecting movement of the face in the field of view of the camera, updating a third physical feature of the displayed preview of the virtual avatar based on a physics model for the virtual avatar and the detected movement.
18. The method of any one of claims 1-17, wherein the preview of the virtual avatar is based on a pre-defined virtual avatar template, the method further comprising:

updating the preview of the virtual avatar based on one or more predefined behaviors associated with the pre-defined virtual avatar template.
19. The method of any one of claims 1-18 further comprising:

in response to a determination that the face is no longer detected in the field of view of the camera, gradually fade the display of the preview of the virtual avatar.
20. The method of any one of claims 1-19 further comprising:

in response to a determination that the face is no longer detected in the field of view of the camera, displaying a message indicating that the face is no longer being properly detected by the camera.
21. The method of any one of claims 1 -20 further comprising:

in response to a determination that the face is no longer detected in the field of view of the camera, updating the display of the preview of the virtual avatar based on a change in

DK 2017 70393 A1 appearance of the face that was occurring during a time period before the face was no longer detected in the field of view.
22. The method of claim 21, wherein updating the display of the preview of the virtual avatar based on a change in appearance of the face that was occurring during a time period before the face was no longer detected in the field of view of the camera includes gradually slowing the updating of the preview of the virtual avatar over time so that the updating of the virtual avatar gradually stops
23. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display and a camera, the one or more programs including instructions for performing the method of any of claims 1 - 22.
24. An electronic device, comprising:

a display;

a camera;

one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any of claims 1 - 22.