Multi-mode activity tracking user interface

Abstract

The invention relates to a multi-mode activity tracking user interface. The present disclosure relates generally to user interfaces and techniques for monitoring fitness activities. In accordance with some embodiments, user interfaces and techniques are described for transitioning between a user interface mode for measuring activity metrics and a user interface mode for measuring different activities based on detecting that user characteristics have changed. In accordance with some embodiments, user interfaces and techniques are described for measuring activity data and providing activity reviews in response to activity-based events, where different activity reviews are provided based on user characteristics.

Description

[0001] This application is a Divisional Application of the Invention Patent Application with the Application Number 202080039364.4, the Invention Name of “MULTI-MODAL ACTIVITY TRACKING USER INTERFACE”, and the Filing Date of May 29, 2020. Cross Reference to Related Applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 856,048, filed June 1, 2019, entitled “MULTI-MODAL ACTIVITY TRACKING USER INTERFACE,” the contents of which are incorporated by reference in their entirety for all purposes. TECHNICAL FIELD

[0003] The present disclosure relates generally to computer user interfaces, and more particularly to user interfaces and techniques for monitoring fitness activities. BACKGROUND

[0004] Users rely on portable multifunction devices for a variety of operations, including timing and running various software applications that enhance device functionality. Users can also want to access different types of information, such as various forms of body-activity related data measured by the device, in order to further their health and fitness related goals. Moreover, users have different physical characteristics. SUMMARY

[0005] However, some techniques for monitoring fitness activities using electronic devices are often cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that can include multiple button presses or keystrokes. As another example, some existing techniques do not accommodate differences in user characteristics, such as age. It is therefore desirable to allow users to access body-activity related data while keeping the interface simple and intuitive to use. Other existing techniques rely on the user’s ability to interpret complex or confusing information, which can make it particularly difficult for some users (e.g., children) to meaningfully monitor their body-activity levels. Existing techniques can be error prone or require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0006] Accordingly, the present techniques provide faster and more efficient methods and interfaces for electronic devices to monitor fitness activities. Such methods and interfaces optionally supplement or replace other methods for monitoring fitness activities. Such methods and interfaces reduce the cognitive burden placed on the user and produce a more efficient human-machine interface. For battery-powered computing devices, such methods and interfaces conserve power and increase the interval between battery charges.

[0007] According to some embodiments, a method performed at an electronic device including a display device and a first set of sensors is described. The method includes: while the electronic device is operating in a first device mode, detecting a change in a first user physical characteristic from a first physical characteristic value to a second physical characteristic value; in response to detecting the change in the first user physical characteristic: in accordance with a determination that the second physical characteristic value satisfies a set of mode change criteria; and in accordance with a determination that the second physical characteristic value does not satisfy a set of mode change criteria, remaining in the first device mode; while the electronic device is operating in the first device mode: receiving first user activity data from the first set of sensors; after receiving the first user activity data, displaying a first activity user interface, the first activity user interface including a first activity metric based on the user activity data received from the first set of sensors; and while the electronic device is operating in the second device mode: receiving second user activity data from the first set of sensors; and after receiving the second user activity data, displaying a second activity user interface, the second activity user interface including a second activity metric different from the first activity metric based on the user activity data received from the first set of sensors.

[0008] According to some embodiments, 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 device and a first set of sensors is described. The one or more programs include instructions for: while the electronic device is operating in a first device mode, detecting a change in a first user physical characteristic from a first physical characteristic value to a second physical characteristic value; in response to detecting the change in the first user physical characteristic: in accordance with a determination that the second physical characteristic value satisfies a set of mode change criteria; and in accordance with a determination that the second physical characteristic value does not satisfy a set of mode change criteria, remaining in the first device mode; while the electronic device is operating in the first device mode: receiving first user activity data from the first set of sensors; after receiving the first user activity data, displaying a first activity user interface, the first activity user interface including a first activity metric based on the user activity data received from the first set of sensors; and while the electronic device is operating in the second device mode: receiving second user activity data from the first set of sensors; and after receiving the second user activity data, displaying a second activity user interface, the second activity user interface including a second activity metric different from the first activity metric based on the user activity data received from the first set of sensors.

[0009] According to some embodiments, a 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 device and a first set of sensors is described. The one or more programs include instructions for: while the electronic device is operating in a first device mode, detecting a change in a first user physical characteristic from a first physical characteristic value to a second physical characteristic value; in response to detecting the change in the first user physical characteristic: in accordance with a determination that the second physical characteristic value satisfies a set of mode change criteria; and in accordance with a determination that the second physical characteristic value does not satisfy a set of mode change criteria, remaining in the first device mode; while the electronic device is operating in the first device mode: receiving first user activity data from the first set of sensors; after receiving the first user activity data, displaying a first activity user interface that includes a first activity metric based on the user activity data received from the first set of sensors; and while the electronic device is operating in the second device mode: receiving second user activity data from the first set of sensors; and after receiving the second user activity data, displaying a second activity user interface that includes a second activity metric different from the first activity metric based on the user activity data received from the first set of sensors.

[0010] According to some embodiments, an electronic device is described. The electronic device includes: a display device; a first set of sensors, one or more processors; 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: while the electronic device is operating in a first device mode, detecting a change in a first user physical characteristic from a first physical characteristic value to a second physical characteristic value; in response to detecting the change in the first user physical characteristic: in accordance with a determination that the second physical characteristic value satisfies a set of mode change criteria; and in accordance with a determination that the second physical characteristic value does not satisfy a set of mode change criteria, remaining in the first device mode; while the electronic device is operating in the first device mode: receiving first user activity data from the first set of sensors; after receiving the first user activity data, displaying a first activity user interface that includes a first activity metric based on the user activity data received from the first set of sensors; and while the electronic device is operating in the second device mode: receiving second user activity data from the first set of sensors; and after receiving the second user activity data, displaying a second activity user interface that includes a second activity metric different from the first activity metric based on the user activity data received from the first set of sensors.

[0011] According to some embodiments, an electronic device is described. The electronic device includes: a display device; a first set of sensors; means for detecting, while the electronic device is operating in a first device mode, a change in a first user physical property from a first physical property value to a second physical property value; means for: in response to detecting the change in the first user physical property: in accordance with a determination that the second physical property value satisfies a set of mode change criteria, initiating a process to transition from the first device mode to a second device mode; and in accordance with a determination that the second physical property value does not satisfy a set of mode change criteria, remaining in the first device mode; means for: while the electronic device is operating in the first device mode: receiving first user activity data from the first set of sensors; means for displaying, after receiving the first user activity data, a first activity user interface, the first activity user interface including a first activity metric based on the user activity data received from the first set of sensors; and means for: while the electronic device is operating in the second device mode: receiving second user activity data from the first set of sensors; and after receiving the second user activity data, displaying a second activity user interface, the second activity user interface including a second activity metric different from the first activity metric based on the user activity data received from the first set of sensors.

[0012] According to some embodiments, a method performed at a first electronic device including a display device is described. The method includes: receiving user activity data; and after receiving the user activity data and in accordance with a determination that the user activity data satisfies a first set of activity commentary display criteria, displaying, via the display device, a first user interface, wherein: in accordance with a determination that a value of a user property satisfies a set of first commentary criteria, the first user interface includes a first activity commentary based on the user activity data; and in accordance with a determination that the value of the user property satisfies a set of second commentary criteria, the first user interface includes a second activity commentary based on the user activity data, the second activity commentary being different from the first commentary.

[0013] According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device that includes a display device is described. The one or more programs include instructions for: receiving user activity data; and displaying, via the display device, a first user interface after receiving the user activity data and in accordance with a determination that the user activity data satisfies a first set of activity-comment-display criteria, wherein: in accordance with a determination that a value of a user characteristic satisfies a first set of comment criteria, the first user interface includes a first activity comment that is based on the user activity data; and in accordance with a determination that the value of the user characteristic satisfies a second set of comment criteria, the first user interface includes a second activity comment that is based on the user activity data, the second activity comment being different from the first comment.

[0014] According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device that includes a display device is described. The one or more programs include instructions for: receiving user activity data; and displaying, via the display device, a first user interface after receiving the user activity data and in accordance with a determination that the user activity data satisfies a first set of activity-comment-display criteria, wherein: in accordance with a determination that a value of a user characteristic satisfies a first set of comment criteria, the first user interface includes a first activity comment that is based on the user activity data; and in accordance with a determination that the value of the user characteristic satisfies a second set of comment criteria, the first user interface includes a second activity comment that is based on the user activity data, the second activity comment being different from the first comment.

[0015] According to some embodiments, a first electronic device is described. The first electronic device includes: a display device; 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: receiving user activity data; and displaying, via the display device, a first user interface after receiving the user activity data and in accordance with a determination that the user activity data satisfies a first set of activity-comment-display criteria, wherein: in accordance with a determination that a value of a user characteristic satisfies a first set of comment criteria, the first user interface includes a first activity comment that is based on the user activity data; and in accordance with a determination that the value of the user characteristic satisfies a second set of comment criteria, the first user interface includes a second activity comment that is based on the user activity data, the second activity comment being different from the first comment.

[0016] According to some embodiments, a first electronic device is described. The first electronic device includes a display device, means for receiving user activity data, and means for displaying, via the display device, a first user interface after receiving the user activity data and in accordance with a determination that the user activity data satisfies a first set of activity commentary display criteria, wherein: in accordance with a determination that a value of a user characteristic satisfies a first set of commentary criteria, the first user interface includes a first activity commentary based on the user activity data; and in accordance with a determination that the value of the user characteristic satisfies a second set of commentary criteria, the first user interface includes a second activity commentary based on the user activity data, the second activity commentary being different from the first commentary.

[0017] Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product that is 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 that is configured for execution by one or more processors.

[0018] Thus, devices are provided with faster, more efficient methods and interfaces for monitoring fitness activities, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces can complement or replace other methods for monitoring fitness activities. BRIEF DESCRIPTION OF DRAWINGS

[0019] For a better understanding of the various described implementations, reference should be made to the Detailed Description below, in connection with the following drawings, in which like references numerals refer to corresponding parts throughout the figures.

[0020] Figure 1A FIG. 1 is a block diagram illustrating a portable multifunction device in accordance with some embodiments.

[0021] Figure 1B FIG. 2 is a block diagram illustrating exemplary components for event processing in accordance with some embodiments.

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

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

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

[0025] Figure 4BExample user interfaces for a multifunction device having a display that is separate from a touch-sensitive surface are shown in accordance with some embodiments.

[0026] Figure 5A A personal electronic device is shown in accordance with some embodiments.

[0027] Figure 5B A block diagram showing a personal electronic device in accordance with some embodiments is shown.

[0028] Figures 5C to 5D Example components of a personal electronic device having a touch-sensitive display and intensity sensor are shown in accordance with some embodiments.

[0029] Figures 5E to 5H Example components and user interfaces of a personal electronic device are shown in accordance with some embodiments.

[0030] Figures 6A to 6W Example user interfaces for monitoring fitness activities are shown.

[0031] Figures 7A to 7D A flow diagram depicting a method for providing a user interface in accordance with some embodiments is shown.

[0032] Figures 8A to 8H Example user interfaces for monitoring fitness activities are shown.

[0033] Figures 9A to 9B A flow diagram depicting a method for providing a user interface in accordance with some embodiments is shown. DETAILED DESCRIPTION

[0034] 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 included merely for illustrative purposes.

[0035] There is a need for electronic devices that provide efficient methods and interfaces for monitoring fitness activities. For example, users who are trying to increase their physical activity levels to obtain associated health benefits (e.g., prevention and improvement of management of health conditions such as hypertension, type 2 diabetes, depression and anxiety, arthritis, etc.) typically rely on tracking their progress toward their goals mentally, manually (via pen and paper), or using devices that provide inaccurate data, and, worse, require navigation of cumbersome interfaces to access such data. More efficient techniques can reduce the cognitive burden on users accessing fitness activity data, thereby increasing productivity and the likelihood of achieving their fitness and health goals. Moreover, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user inputs.

[0036] Below, Figures 1A to 1B , Figure 2 、 Figure 3 、 Figures 4A to 4B and Figures 5A to 5H A description of an exemplary device for performing techniques for monitoring fitness activities is provided. Figures 6A to 6W An exemplary user interface for monitoring fitness activities is shown. Figures 7A to 7D is a flow diagram illustrating a method of monitoring fitness activities, in accordance with some embodiments. Figures 6A to 6W The user interface in Figures 7A to 7D includes processes described below, including Figures 8A to 8H An exemplary user interface for providing dynamic activity commentary is shown. Figures 9A to 9B is a flow diagram illustrating a method of providing dynamic activity commentary, in accordance with some embodiments. Figures 8A to 8H The user interface in Figures 9A to 9B includes processes described below, including Although the following description uses the 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.

[0037] 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 "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.

[0038] The term "if' is optionally interpreted as meaning "when," "while," or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [stated condition or event] is detected" is optionally interpreted as meaning "upon determining" or "in response to determining" or "upon detecting [stated condition or event]" or "in response to detecting [stated condition or event]," depending on the context.

[0039] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. 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 exemplary embodiments of portable multifunction devices include, without limitation, the Nexus 4, Nexus 5, and Nexus 6 devices from Google of Mountain View, California. ® iPod Touch® devices, and iPad® devices. Other portable electronic devices, such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and / or touchpads), are, optionally, used. ® iPod Touch® devices, and iPad® devices. Other portable electronic devices, such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and / or touchpads), are, optionally, used. ® iPod Touch® devices, and iPad® devices. Other portable electronic devices, such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and / or touchpads), are, optionally, used. In some embodiments, an electronic device is a computer system (e.g., via wireless communication, via wired communication) in communication with a display generation component. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, "displaying" content includes displaying content by transmitting data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually produce the content (e.g., video data rendered or decoded by display controller 156).

[0040] In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. However, it should be understood 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.

[0041] 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 game 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.

[0042] Various applications 1246 executing on the device optionally use at least one common physical user interface 1245, such as a touchscreen 1245. One or more functions of the touchscreen 1245, as well as corresponding information displayed on the device, are optionally adjusted and / or changed in relation to the different applications 1246, and / or in relation to a current orientation of the device. Thus, the shared physical architecture of the device, such as the touchscreen 1245, is utilized by various applications 1246 to implement a native user interface 1245 for each of the applications 1246.

[0043] Attention is now directed towards embodiments of portable devices with touch-sensitive displays. Figure 1A FIG. 1 shows a block diagram of a portable multifunction device 100 with a touch-sensitive display system 112 in accordance with some embodiments. The touch- sensitive display 112 is sometimes called a "touch screen" for convenience, and is sometimes known as or called a "touch-sensitive display system." The device 100 includes a memory 102 (which optionally includes one or more computer-readable storage mediums), a memory controller 122, one or more processing units (CPUs) 120, a peripherals interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact intensity sensors 165 for detecting intensity of contacts on the device 100 (e.g., a touch-sensitive surface such as the touch- sensitive display system 112 of the device 100). The device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on the device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as the touch-sensitive display system 112 of the device 100 or the touchpad 355 of the device 300). These components optionally communicate over one or more communication buses or signal lines 103.

[0044] As used in the specification and claims, the term "intensity" of a contact on a touch- sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch- sensitive surface, or a proxy for the force or pressure of the 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 optionally are used to measure force at various points on the touch- sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force. 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 (or an change in the size of the contact area) detected on the touch- sensitive surface, the capacitance of the touch- sensitive surface proximate to the contact (or a change in the capacitance of the touch- sensitive surface), and / or the resistance of the touch- sensitive surface proximate to the contact (or a change in the resistance of the touch- sensitive surface) 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 functions with additional device features.

[0045] 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 (for example, a touch-sensitive surface) of a device relative to another component (for example, a 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 (for example, a surface of a finger, palm, or other portion of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as an "egress click," "ingress click," or "drag," in areas where the user is touching the device. In situations where the device or component of the device is not in contact with the user's skin, the tactile output generated by the physical displacement will be perceived by the user as a tactile sensation that is euphemistically referred to as "haptic feedback," where the user's object is moved relative to user's body or head.

[0046] It should be appreciated that device 100 is only one example of a portable multifunctional 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 illustrated in FIG. 1 can be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and / or application specific integrated circuits. Figure 1A The various components illustrated in FIG. 1 can be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0047] Memory 102 optionally includes high-speed random access memory and also optionally includes nonvolatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.

[0048] The peripheral interface 118 can be used to couple the device's input and output peripherals to the CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and / or instruction sets stored in the memory 102 to perform various functions of the device 100 and process data. In some embodiments, the peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as the chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0049] The RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. The RF circuitry 108 converts between electrical signals and electromagnetic signals, and communicates with communications networks and other communications devices through electromagnetic signals. The RF circuitry 108 optionally includes well-known circuitry for detecting and for resolving signals received through the antenna system, including, for example, low-noise amplifiers, switches, and filters. The RF circuitry 108 optionally includes a transmit / receive switch, power amplifiers, and low-noise amplifiers. The RF circuitry 108 optionally interfaces with the transceiver interface 112. The RF circuitry 108 optionally includes a Bluetooth® radio and a Global Positioning System (GPS) receiver, which can be used for location determination. The RF circuitry 108 optionally includes a short wave near-field communication (SWNFC) 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), code division multiple access (CDMA), time division multiple access (TDMA), Wideband-CDMA (W-CDMA), Long Term Evolution (LTE), Near Field Communication (NFC), 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), Short Message Service (SMS), or General Packet Radio Service (GPRS), using time-division multiple access (TDMA), code-division multiple access (CDMA), wideband code-division multiple access (WCDMA), long term evolution (LTE) designs (e.g., LTE Frey, LTE-A, LTE-A Pro, LTE-A Pro Plus, and / or LTE-A Pro Ultra), 5G, 6G, or any other suitable communication protocol, including one not yet developed at the time of the filing of this document.

[0050] Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and / or transmitted to memory 102 and / or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212 in 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., stereo Figure 2

[0051] I / O subsystem 106 couples input / output peripherals on device 100, such as touch screen 112 and other input control devices 116, with peripherals interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, 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., 208 in FIG. 2), dials, slider switches, joysticks, click wheels, and so on. In some alternate embodiments, input controller(s) 160 are, optionally, coupled with any Figure 2 Figure 2 ​​In some embodiments, the electronic device is a computer system in communication with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a touchpad, as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as to track a user's gestures (e.g., hand gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system.

[0052] A quick press of the down button optionally disengages a lock of the touch screen 112 or optionally begins a process that uses a gesture 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 (i.e., U.S. Patent No. 7,657,849), which is hereby incorporated by reference in its entirety. A longer press of the down button (e.g., 206) optionally turns the device 100 on or off. The functionality of one or more of the buttons is optionally made user-customizable by mapping of one or more buttons to key commands. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0053] The touch screen 112 provides an input interface and an output interface between the device and a user. The display controller 156 receives and / or sends electrical signals from / to the touch screen 112. The 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.

[0054] The 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. The touch screen 112 and the 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 the touch screen 112 and convert the detected contact into data

[0055] The 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. The touch screen 112 and the display controller 156 optionally use 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 the touch screen 112 and any ® and iPod Touch ® devices from Apple Inc. of Cupertino, California.

[0056] The touch-sensitive display in some embodiments of the touch screen 112 is optionally similar to the multi-touch touchpad 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 et al), and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, the touch screen 112 displays visual output from the device 100, whereas a touch- sensitive pad does not provide visual output.

[0057] In some embodiments, the touch-sensitive display of touch screen 112 is as 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 hereby incorporated by reference in their entirety.

[0058] Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, 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 precise commands by a variety of techniques. In some embodiments, the device translates the rough finger-based input into precise commands by a variety of techniques.

[0059] In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad. In some embodiments, the touchpad is a touch-sensitive area, located on the device, that is separate from the touch screen 112 and that does not display visual output. The touchpad optionally is a touch-sensitive surface that is separate from the touch screen 112, or that is an extension of the touch-sensitive surface formed by the touch screen.

[0060] Device 100 also includes power system 162 for powering the various components of device 100. 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 for device 100.

[0061] Device 100 optionally also includes one or more optical sensors 164. Figure 1AAn optical sensor coupled to optical sensor controller 158 in I / O subsystem 106 is shown. The optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) photoreceptor(s). The optical sensor 164 receives light from the environment, projected through one or more lens, and converts the light to data representing an image. In conjunction with imaging module 143 (also called a camera module), the optical sensor 164 optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite the 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 image 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 the 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 together with the touch screen display for both video conferencing and still and / or video image acquisition.

[0062] Device 100 optionally also includes one or more depth camera sensors 175. Figure 1A A depth camera sensor coupled to depth camera controller 169 in I / O subsystem 106 is shown. The depth camera sensor 175 receives data from the environment to create a 3-D model representing a physical, real-world environment in 3-D space from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also called a camera module), the depth camera sensor 175 optionally captures still images or video for use by the user. In some embodiments, the depth camera sensor is located on the front of device 100 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, and to capture selfies with depth data. In some embodiments, the depth camera sensor 175 is located on the back of device 100, or on the back and the front of the device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that the depth camera sensor 175 is used together with the touch screen display for both video conferencing and still and / or video image acquisition.

[0063] In some embodiments, a depth map (e.g., a depth map image) contains information (e.g., values) related to the distance of objects in a scene from a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor). In one embodiment of a depth map, each depth pixel defines the location in the Z-axis of the viewpoint of its corresponding two-dimensional pixel. In some embodiments, a depth map is composed of pixels, where each pixel is defined by a value (e.g., 0 to 255). For example, a "0" value represents a pixel located the farthest in the "three-dimensional" scene from the viewpoint (e.g., a camera, an optical sensor, a depth camera sensor), and a "255" value represents a pixel located the closest in the "three-dimensional" scene from the viewpoint. In other embodiments, a depth map represents the distance between objects in a scene and the plane of the viewpoint. In some embodiments, a depth map includes information about the relative depth of various features of an object of interest in the field of view of the depth camera (e.g., the relative depth of the eyes, nose, mouth, ears of a user's face). In some embodiments, a depth map includes information that enables a device to determine the contours of an object of interest in the z-direction.

[0064] Device 100 optionally also includes one or more contact intensity sensors 165. Figure 1A Contact intensity sensor(s) 165 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 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 intensity sensor is collocated with, or coiresident in, a touch-sensitive surface (e.g., touch- sensitive 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.

[0065] Device 100 optionally also includes one or more proximity sensors 166. Figure 1AA proximity sensor 166 coupled to the peripherals interface 118 is shown. The proximity sensor 166 is optionally coupled to the input controller 160 in the I / O subsystem 106. The proximity sensor 166 optionally performs as described in the following applications: No. 11 / 241,839, "Proximity Detector In Handheld Device"; No. 11 / 240,788, "Proximity Detector In Handheld Device"; No. 11 / 620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586,862, "Automated Response To And Sensing Of User Activity In Portable Devices"; and No. 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 the touchscreen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0066] The device 100 optionally also includes one or more tactile output generators 167. Figure 1AA tactile output generator coupled to tactile feedback controller 161 in I / O subsystem 106 is shown. Tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components and / or electromechanical devices such as a motor, a solenoid, an electroactive polymer, a piezoelectric actuator, an electrostatic actuator or other tactile output generating component (e.g., a component for converting 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 a user is able to feel. In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display screen 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 the touch-sensitive surface of device 100). In some 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.

[0067] Device 100 optionally also includes one or more accelerometers 168. Figure 1A Accelerometer 168 coupled to peripherals interface 118 is shown. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I / O subsystem 106. Accelerometer 168 optionally performs as described in U.S. Patent Publication No. 20050190059, "Acceleration-based 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 by one or more accelerometers. Device 100 optionally includes a magnetometer (not shown) and 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.

[0068] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application program (or instruction set) 136. Furthermore, in some embodiments, memory 102 ( Figure 1A ) or 370 ( Figure 3 Storage device / global internal state 157, such as Figure 1A and Figure 3 As shown in the figure. Device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and position information about the device's position and / or orientation.

[0069] The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or embedded operating systems such as VxWorks) includes various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

[0070] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is for use with an iPod. ® (Trademark of Apple Inc.) The same or similar and / or compatible multi-pin (e.g., 30-pin) connectors used in Apple Inc. devices.

[0071] 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 movement has occurred (e.g., detecting a finger-drag event), and determining if an object making contact has been removed (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 contact point, optionally, includes determining speed (magnitude), velocity (magnitude and direction), and / or acceleration (a change of magnitude and / or direction) of the movement of the contact point, which are indicative of a finger gesture. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., "multitouch'Vmultiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contact on a touchpad.

[0072] In some embodiments, contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed (e.g., whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by activation thresholds of particular physical actuators, and can be adjusted without changing the physical hardware of device 100). For example, without changing the touchpad or touch screen display hardware, the mouse "click" threshold of the touchpad or touch screen can be set to any of a large range of predefined thresholds. Additionally, in some implementations, software settings are provided to users of the device to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once with a system-wide click on an "intensity" parameter).

[0073] Contact / motion module 130 optionally detects intensities of contacts on touch- sensitive surface 112 using contact intensity sensor(s) 165. Contact intensity sensor(s) 165 optionally include one or more piezoelectric or piezoresistive sensors to measure force of contacts either on or near touch- sensitive surface 112. In one or more embodiments, intensity of forces is

[0074] Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing 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.

[0075] 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, and then generates screen image data for a

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

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

[0078] 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, yellow page, and map / navigation services).

[0079] The applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof: • a contacts module 137 (sometimes referred to as an address book or contact list); • a telephone module 138; • a video conferencing module 139; • an e-mail client module 140; • an instant messaging (IM) module 141; • a workout support module 142; • a camera module 143 for still and / or video images; • an image management module 144; • a video player module; • a music player module; • a browser module 147; • a calendar module 148; • a desk clock module 149, which optionally includes one or more of the following: a weather desk clock 149-1, a stock market desk clock 149-2, a calculator desk clock 149-3, an alarm clock desk clock 149-4, a dictionary desk clock 149-5, and other desk clocks acquired by user, and user-created desk clocks 149-6; • a desk clock creator module 150 for forming user-created desk clocks 149-6; • a search module 151; • a video and music player module 152, which merges video player module and music player module; • a notepad module 153; • a map module 154; and / or • an online video module 155.

[0080] Examples of other applications 136 that can optionally be stored on the storage 102 include other word processing applications, other image editing applications, a drawing application, a presentation application, JAVA-enabled applications, an encryption, a digital rights management, a voice recognition and a voice replication.

[0081] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the 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 one or more new names; deleting one or more existing names; associating one or more telephone numbers with a name; associating one or more e-mail addresses with a name; associating one or more physical addresses with a name; associating one or more user IDs with a name; pushing / flowing contacts from the computer system 600 to another system that is linked to the computer system 600 via the contacts module 137 (e.g., the system 600, another mobile terminal 800, a server or homeowner security system); pulling / flowing contacts from another system (e.g., the system 600, another mobile terminal 800, a server or homeowner security system) to the computer system 600 via the contacts module 137; transferring a contact (e.g., a name) from the computer system 600 to another system, as well as transferring a contact from another system to the computer system 600 using the contacts module 137; associating a contact image with a name; categorizing and sorting contacts; providing telephony numbers or e-mail addresses of one or more contacts; initiating and facilitating communications (e.g., telephone calls, video calls, electronic mail, or IM messages) with one or more contacts; and the like.

[0082] 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 the contacts module 137, modify a telephone number from the contacts module 137, calibrate an output from the microphone 113, dial one or more telephone numbers, calibrate an output of the

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

[0084] 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, the e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with the camera module 143.

[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, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, modify previously entered characters, transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for a

[0086] 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, the 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.

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

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

[0089] 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 browser module 147 includes executable instructions to browse, using user gestures, the Internet, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0090] 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, the calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.

[0091] 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 desktop app module 149 is an optional micro-app (e.g., weather desktop app 149-1, stocks desktop app 149-2, calculator desktop app 149-3, alarm clock desktop app 149-4, and dictionary desktop app 149-5) that is downloaded and used by a user or a micro-app (e.g., user-created desktop app 149-6) that is created by the user. In some embodiments, a desktop app includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheet) files, and JavaScript files. In some embodiments, a desktop app includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! Desktop App).

[0092] 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 desktop app creator module 150 is used by a user to create desktop apps (e.g., to convert user-specified portions of web pages into desktop apps).

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

[0094] 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 to play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

[0095] 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 using a format similar to "sticky" notes. In some embodiments, notes module 153 includes executable instructions to send reminder messages in accordance with a scheduled or actual schedule (e.g., reminders via e-mail, traps, SMS message, or software-generated prompts).

[0096] 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 a map format).

[0097] 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 for enabling 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 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,” and U.S. Patent Application No. 11 / 968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” both of which were filed on June 20, 2007, the contents of which are hereby incorporated by reference in their entirety.

[0098] Each of the above-identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods described herein and other information processing methods). 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 re-arranged in various embodiments. For example, video and music player module 152 optionally corresponds to a set of executable instructions for implementing both video and music player capabilities in one integrated module or to a set of executable instructions for implementing a music player capability in one module and a video player capability in a different module. 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. Figure 1A

[0099] ​In some embodiments, device 100 is a device for which a predefined set of functions on the device are operated exclusively through the touch screen and / or touchpad. By using the touch screen and / or touchpad as the primary input control devices for operating device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on device 100 is optionally reduced.

[0100] The predefined set of functions that are operated exclusively through the touch screen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 from any user interface displayed on device 100 to a main menu, home menu, or root menu. In such embodiments, the touchpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

[0101] Figure 1B FIG. 1 is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory 102 (e.g., memory 102 of device 100) Figure 1A ) or memory 370 (e.g., memory 370 of device 100) Figure 3 ) includes event classifier 170 (e.g., in operating system 126) and corresponding application programs 136-1 (e.g., any of the aforementioned application programs 137-151, 155, 380-390).

[0102] Event classifier 170 receives event information and determines an application program 136-1 and an application program view 191 of the application program 136-1 to which to deliver the event information. Event classifier 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application programs 136-1 include application program internal state 192 that indicates one or more current application program views that are displayed on touch-sensitive display 112 when the application program is active or executing. In some embodiments, device / global internal state 157 is used by event classifier 170 to determine which application program(s) are currently active, and application program internal state 192 is used by event classifier 170 to determine an application program view 191 to which to deliver event information.

[0103] In some embodiments, application program internal state 192 includes additional information, such as one or more of: resume information to be used when the application program 136-1 resumes execution, user interface state information indicating that information is being displayed or is ready for display by the application program 136-1, a state queue for enabling the user to return to a previous state or view of the application program 136-1, and a repeat / undo queue of previous actions taken by the user.

[0104] Event monitor 171 receives event information from peripherals interface 118. Event information includes information about sub-events (e.g., user touches on touch- sensitive display 112, motion sensor events, or audio sensor events, as examples). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors, such as proximity sensor 166, one or more accelerometers 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 touch-sensitive surface.

[0105] In some embodiments, event monitor 171 sends a request to 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., when an input is received that is above a predetermined noise threshold and / or that lasts longer than a predetermined duration).

[0106] In some embodiments, event categorizer 170 also includes hit view determination module 172 and / or active event recognizer determination module 173.

[0107] When touch-sensitive display 112 displays more than one view, hit view determination module 172 provides a software procedure for determining where a sub-event has occurred within one or more views. A view is made up of controls and other elements that a user is able to see on the display.

[0108] Another aspect of a user interface associated with an application is a set of views, also sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which a touch is detected optionally corresponds to a programmed level within the application's programmatic or view hierarchy. For example, the lowest level view in which a touch is detected is optionally referred to as the hit view, and the set of events that are correctly inputted is optionally determined based at least in part on the hit view of an initial touch that begins a touch-based gesture.

[0109] The hit view determination module 172 receives information related to touch-based gesture sub-events. When an application has multiple views organized in a hierarchy, the hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle the sub-event. In most cases, the hit view is the lowest level view in which the sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) originated. 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.

[0110] The active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognizer determination module 173 determines that all views that include the physical location of the sub-events are actively engaged views, and thus determines that all actively engaged views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is entirely confined to an area associated with one particular view, higher views in the hierarchy will remain actively engaged views.

[0111] The event dispatcher module 174 dispatches event information to event recognizers (e.g., event recognizers 180). In embodiments that include the active event recognizer determination module 173, the event dispatcher module 174 delivers event information to the event recognizers determined by the active event recognizer determination module 173. In some embodiments, the event dispatcher module 174 stores event information in an event queue that is retrieved by the respective event recognizers 182.

[0112] In some embodiments, the operating system 126 includes the event classifier 170. Alternatively, the application 136-1 includes the event classifier 170. In yet another embodiment, the event classifier 170 is a standalone module, or part of another module stored in the memory 102, such as the contact / motion module 130.

[0113] 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 user interface of the application. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a standalone module that is a higher level object from which application 136-1 inherits methods and other attributes, such as a user interface toolkit or application framework. In some embodiments, a respective event handler 190 includes one or more of a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls for related data 180 from event sorter 170, device controller 952, and / or event router 956, as well as

[0114] A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and, based on the event information, recognizes events occurring within the application. Event recognizer 180 includes an event receiver 182 and an 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).

[0115] Event receiver 182 receives event information from event sorter 170. The event information includes information about the sub-event, e.g., a touch or touch movement. Additionally, the event information also includes information about other aspects of the event such as location of the sub-event. Where a sub-event involves a touch by a finger, event information additionally includes information about which finger touched the touch screen, the force and / or velocity of the touch, and / or the like. In some embodiments, the event information additionally includes information about a current

[0116] Event comparator 184 compares event information to predefined event or sub-event definitions and determines an event or sub-event, or a status of an event or sub-event, based on the comparison. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), such as 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 move, touch cancel, and multi-touch. In one example, the definition of event 1 (187-1) is a double tap on a displayed object. For example, a double tap includes a first touch (touch begin) on a displayed object for a predetermined duration, a first liftoff (touch end) for a predetermined duration, a second touch (touch begin) on a displayed object for a predetermined duration, and a second liftoff (touch end) for a predetermined duration. In another example, the definition of event 2 (187-2) is a drag on a displayed object. For example, a drag includes a touch (or contact) on a displayed object for a predetermined duration, movement of the touch on the touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, an event also includes information for one or more associated event handlers 190.

[0117] In some embodiments, event definitions 187 include definitions of events for respective user interface objects. 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 that displays three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, event comparator uses the results of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects the event handler associated with the sub-event and the object that triggered the hit test.

[0118] In some embodiments, the definition of a respective event (187) also includes a deferred action that delays delivery of event information until it has been determined that a sequence of sub-events does or does not correspond to an event type of the event recognizer.

[0119] When a respective event recognizer 180 determines that a sub-event sequence does not match any event in the event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

[0120] In some embodiments, the respective event recognizers 180 include metadata 183 having configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to the event recognizer of the active participant. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists that indicate how the event recognizers interact or are able to interact with each other. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0121] In some embodiments, when one or more particular sub-events of an event are recognized, the respective event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the respective event recognizer 180 delivers event information associated with the event to the event handler 190. Activating an event handler 190 is distinct from sending (and deferring sending) sub-events to a respective hit view. In some embodiments, the event recognizer 180 throws a token associated with the recognized event, and an event handler 190 associated with the token picks up the token and performs a pre-defined procedure.

[0122] In some embodiments, the 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 the event information to an event handler associated with the sub-event sequence or to the active participant view. The event handler associated with the sub-event sequence or with the active participant view receives the event information and performs a pre-determined procedure.

[0123] 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 a 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 the touch screen.

[0124] In some embodiments, event handler 190 includes data updater 176, object updater 177, and GUI updater 178, or has access to them and utilizes them as needed. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0125] It should be understood that the above discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to the multi-function device 100 not all of which are touch-based. For example, mouse movements and mouse button presses, optionally coordinated with single or multi-key presses or holds, are also user inputs that are optionally used to implement event handling. Touch-sensitive display 112 optionally uses LCD (liquid crystal display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch-sensitive display 112 and touch screen 112 optionally display visual output onto a display region. See FIG. 6. In some embodiments, a display region is a portion of the touch-sensitive display 112. In some embodiments, the display region is the entire touch-sensitive display 112. In some embodiments, the display region is larger than the touch-sensitive display 112. In some embodiments, the display region is the same size as the touch-sensitive display 112. In some embodiments, the display region is smaller than the touch-sensitive display 112. In some embodiments, the display region is the entire touch-sensitive display 112, and the touch-sensitive display 112 optionally displays visual output onto the display region.

[0126] Figure 2The portable multifunction device 100 with touch screen 112 is, according to some embodiments, shown. The touch screen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as in other embodiments discussed below, the 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 drag (using contact), one or more pinches (expand outward from point to increase the size or shrink inward from size to decrease the size) and / or a squeeze (using contact) on the graphics. In some implementations or situations, an inadvertent or unsolicited touch of graphics does not select the graphics. For example, some graphics can be editable even when touched by the user. A gesture that selects a graphics is, optionally, a gesture that changes the state of the graphics, for example, without causing the device 100 to function in a particular manner. Such a selection gesture is often referred to as an "edit gesture" or "edit gesture" in this discussion. A gesture that causes the device 100 to function in a particular manner is, optionally, a gesture that selects the graphics, and is often referred to as a "select gesture" or "select gesture" in this discussion. 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 drag (using contact), one or more pinches (expand outward from point to increase the size or shrink inward from size to decrease the size) and / or a squeeze (using contact) on the graphics. In some implementations or situations, an inadvertent or unsolicited touch of a graphic does not select the graphic. For example, when the gesture corresponding to selection is a tap, a swipe gesture that sweeps across an application icon optionally does not select the corresponding application.

[0127] Device 100 optionally also includes one or more physical buttons, such as "home" or menu button 204. As described previously, the menu button 204 is, optionally, used to navigate to any application 136 included in a set of applications 136 that is, optionally, executed by device 100. Alternatively, the menu button is, optionally, implemented as a soft key in a GUI displayed by

[0128] In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on / off and placing device 100 in a sleep state, one or more volume adjustment buttons 208, user identity module (SIM) card slot 210, headset jack 212, and docking / charging external port 124. Push button 206 is, optionally, used to power the device on / off by depressing the button and holding the button 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 to a user of device 100.

[0129] Figure 3is 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 education device (such as a child's learning toy), a gaming device, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPU's) 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 keyboard and / or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 (e.g., tactile feedback provided to the device user via display 340 and / or external devices such as a motor in a motorized laptop computer or control surface) for generating tactile outputs (e.g., similar to the tactile output generator 167 described above with reference to Figure 1A the contact intensity sensor 165 described above with reference to Figure 1A the contact intensity sensor 165 described above with reference to Figure 1A the contact intensity sensor 165 described above with reference to Figure 1A the contact intensity sensor 165 described above with reference to

[0130] Figure 3Each of the above identified elements can optionally be stored on one or more of the aforementioned memory devices 370. Each of the above identified modules corresponds to a set of instructions for performing a certain task. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules can optionally be combined or otherwise re-arranged 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.

[0131] Attention is now directed towards embodiments of user interfaces ("UI") that are optionally implemented on portable multifunction devices 100.

[0132] Figure 4A An exemplary user interface that includes an application menu on a portable multifunction device 100 is shown. 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 402 for wireless communication, such as cellular signal and Wi-Fi signal; • Time 404; • Bluetooth indicator 405; • Battery status indicator 406; • Tray 408 with icons for commonly used applications, such as: • Icon 416 for telephone module 138 labeled "Phone," which optionally includes an indicator 414 of the number of missed calls or voice mails; • Icon 418 for e-mail client module 140 labeled "Mail," which optionally includes an indicator 410 of the number of unread e-mails; • Icon 420 for browser module 147 labeled "Safari®"; and • Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled "iPod"; and • Icons for other applications, such as: • Icon 424 for IM module 141 labeled "Messages"; • Icon 426 for calendar module 148 labeled "Calendar"; • Icon 428 for image-managing module 144 labeled "Photos"; • Icon 430 for camera module 143 labeled "Camera"; • an icon 432 labeled "Online Videos" for the online video module 155; • an icon 434 labeled "Stocks" for the stock market widget 149-2; • an icon 436 labeled "Maps" for the maps module 154; • an icon 438 labeled "Weather" for the weather widget 149-1; • an icon 440 labeled "Clock" for the alarm clock widget 149-4; • an icon 442 labeled "Fitness" for the fitness support module 142; • an icon 444 labeled "Notes" for the notes module 153; and • an icon 446 labeled "Settings" for the settings application or module, which provides access to settings for the device 100 and its various applications 136.

[0133] It should be noted that Figure 4A The icon labels shown in FIG. 6 are merely examples. For instance, the icon 422 for the video and music player module 152 is labeled "Music" or "Music Player." Other labels for various application icons are optional. In some embodiments, the label for a particular application icon includes the name of the application to which that particular application icon corresponds. In some embodiments, the label for a particular application icon is different than the name of the application to which the particular application icon corresponds.

[0134] Figure 4B An example user interface on a device (e.g., device 300) with a touch- sensitive surface 451 (e.g., touchpad or trackpad 355) that is separate from the display 450 (e.g., touch screen display 112) is shown. Figure 3 An example user interface on a device (e.g., device 300) with a touch- sensitive surface 451 (e.g., touchpad or trackpad 355) that is separate from the display 450 (e.g., touch screen display 112) is shown. Figure 3 The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more sensors 359 in the contact intensity sensor array 357) to detect intensity of contacts on the touch-sensitive surface 451 and / or one or more tactile output generators 357 to generate tactile outputs for the user of the device 300.

[0135] Although some of the examples that follow will be given with reference to inputs on the touch screen display 112, in which 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 in the device 300 of FIG. 3. Figure 4B Figure 4B Although some of the examples that follow will be given with reference to inputs on the touch screen display 112, in which 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 in the device 300 of FIG. 3. Figure 4B Although some of the examples that follow will be given with reference to inputs on the touch screen display 112, in which 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 in the device 300 of FIG. 3.​ Figure 4B (452 in the example). According to these embodiments, the device detects the position corresponding to the corresponding position on the display (e.g., in the example). Figure 4B In the diagram, 460 corresponds to 468 and 462 corresponds to 470) is in contact with the touch-sensitive surface 451 (e.g., Figure 4B (460 and 462 in the text). Thus, when the touch-sensitive surface (e.g., ...) Figure 4B 451 in the middle) and the display of a multi-functional device (e.g., Figure 4B When 450 is separated from the touch-sensitive surface, user input detected by the device on that touch-sensitive surface (e.g., touches 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods may optionally be used for other user interfaces described herein.

[0136] Additionally, while the examples below are primarily given with reference to finger input (e.g., finger touch, single-finger tap, finger swipe), it should be understood that in some implementations, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by a mouse click (e.g., instead of a touch), followed by movement of the cursor along the swipe path (e.g., instead of movement of the touch). Similarly, a tap gesture may optionally be replaced by a mouse click while the cursor is over the location of the tap gesture (e.g., instead of detection of touch, followed by cessation of touch detection). Likewise, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0137] Figure 5A An exemplary personal electronic device 500 is illustrated. Device 500 includes a body 502. In some embodiments, device 500 may include components relative to devices 100 and 300 (e.g., Figures 1A to 4B Some or all of the features described herein. In some embodiments, device 500 has a touch-sensitive display 504, referred to below as touchscreen 504. As an alternative to or complement to touchscreen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touchscreen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). The one or more intensity sensors of touchscreen 504 (or touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of device 500 can respond to touches based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface operations on device 500.

[0138] Exemplary techniques for detecting and processing touch intensity are found in, for example, International Patent Application Serial No. PCT / US2013 / 040061 entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," filed May 8, 2013, published as WIPO Patent Publication No. WO / 2013 / 169849; and International Patent Application Serial No. PCT / US2013 / 069483 entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships," filed November 11, 2013, published as WIPO Patent Publication No. WO / 2014 / 105276, each of which is hereby incorporated by reference in its entirety.

[0139] 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 a depressible button and a rotatable mechanism. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can allow device 500 to be attached with, for example, a hat, glasses, earrings, a necklace, a shirt, a jacket, a bracelet, a watchband, a necklace, pants, a belt, shoes, a purse, a backpack, and the like. These attachment mechanisms allow a user to wear device 500.

[0140] Figure 5B An exemplary personal electronic device 500 is shown. In some embodiments, device 500 can include the features described with reference to Figure 1A , Figure 1B and Figure 3Some or all of the described components can be used in the device 500, which is in communication with one or more computer processors 516 and memory 518 that are operatively coupled with a bus 512 that connects I / O section 514 with the one or more computer processors 516 and memory 518. The I / O section 514 can connect to a display 504, which can have a touch-sensitive component 522 and optionally a intensity sensor 524 (e.g., contact intensity sensor). Additionally, the I / O section 514 can connect with a communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and / or other wireless communication techniques. The device 500 can include input mechanisms 506 and / or 508. For example, the input mechanism 506 is optionally a rotatable input device or a pressable input device, and a rotatable input device. In some examples, the input mechanism 508 is optionally a button.

[0141] In some examples, the input mechanism 508 is optionally a microphone. The personal electronic device 500 optionally includes various sensors, such as a GPS sensor 532, an accelerometer 534, an orientation sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or a combination thereof, all of which can be operatively connected to the I / O section 514.

[0142] The memory 518 of the personal electronic device 500 can include one or more non-transitory computer-readable storage media that stores computer-executable instructions for execution by the one or more computer processors 516, which, when executed, for example, can cause the computer processors to perform the techniques described below, including the processes 700 and 900 Figures 7A to 7D and Figures 9A to 9B . The computer-readable storage media can be any media capable of Figure 5B having tangibly embodied computer-executable instructions for use by or in connection with an instruction execution system, apparatus, and device. In some examples, the storage media is a transitory computer-readable storage medium. In some examples, the storage media is a non-transitory 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 disks based on CD, DVD, or Blu-ray technologies, and persistent solid-state memory such as flash, solid-state drives, and the like. The personal electronic device 500 is not limited to

[0143] As used herein, the term “affordance” refers to a visual, auditory, or tactile display item that is capable of being perceived by a user and that is operable to enable user interaction with the device 100, 300, and / or 500 Figure 1A , Figure 3 and Figures 5A to 5BA user-interactive graphical user interface object displayed on a screen. For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) optionally each constitute a functional representation.

[0144] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some specific implementations that include a cursor or other positional marker, the cursor acts as a "focus selector," such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the cursor is positioned on a touch-sensitive surface (e.g., a...). Figure 3 The touchpad 355 or Figure 4B When an input (e.g., a press input) is detected on the touch-sensitive surface 451 of the display, the specific user interface element is adjusted according to the detected input. This applies to touchscreen displays (e.g., those capable of direct interaction with user interface elements on a touchscreen display) that enable direct interaction with user interface elements on the touchscreen display. Figure 1A The touch-sensitive display system 112 or Figure 4A In some embodiments of the touchscreen 112, a touch detected on the touchscreen acts as a "focus selector," such that when input (e.g., a press input by touch) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, that particular user interface element is adjusted according to the detected input. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled user interface element (or a touch on the touchscreen display) that delivers the user-expected interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate to the user that they expect to activate the corresponding button (rather than other user interface elements shown on the device's display).

[0145] As used in the specification and claims, the term "feature strength" of a contact refers to a characteristic of the contact based on one or more strengths of the contact. In some embodiments, the feature strength is based on a predefined number of strength samples or a set of strength samples taken during a predetermined period of time (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) with respect to a predefined event (e.g., after detecting the contact, before detecting the contact lift-off, before or after detecting the contact starting to move, before detecting the contact ending, before detecting the contact increasing in intensity, and / or before detecting the contact decreasing in intensity). The feature strength of a contact is optionally based on one or more of: a maximum value of the strength of the contact, a mean value of the strength of the contact, a median value of the strength of the contact, a value at the 10% of the strength of the contact, a half maximum value of the strength of the contact, a 90% maximum value of the strength of the contact, etc. In some embodiments, the duration of the contact is used in determining the feature strength (e.g., when the feature strength is the average of the strength of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact with a feature strength that does not exceed the first threshold results in a first operation, a contact with a feature strength that exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact with a feature strength that exceeds the second threshold results in a third operation. In some embodiments, the comparison between the feature strength and the one or more thresholds is used to determine whether one or more operations are to be performed (e.g., whether to perform a respective operation or to forego performing a respective operation) rather than to determine whether to perform a first operation or a second operation.

[0146] Figure 5C Multiple contacts 552A-552E on the touch-sensitive display 504 are shown being detected with multiple intensity sensors 524A-524D. Figure 5C An intensity plot is also included, showing the current intensity measurements of the intensity sensors 524A-524D relative to intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are both 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are both 7 intensity units. In some implementations, the cumulative intensity is the sum of the intensity measurements of the multiple intensity sensors 524A-524D, which is 32 intensity units in this example. In some embodiments, each contact is assigned a respective intensity, which is a fraction of the cumulative intensity. Figure 5DAssigning cumulative intensities to contacts 552A-552E based on their distance from the center of force 554 is shown. In this example, each of contacts 552A, 552B, and 552E is assigned a contact intensity of 8 intensity units of cumulative intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of cumulative intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij according to a predefined mathematical function Ij = A-(Dj / ∑Di), which is a fraction of cumulative intensity A, where Dj is the distance of respective contact j from the center of force, and ∑Di is the sum of the distances of all respective contacts (e.g., i = 1 to last) from the center of force. The operations described with reference to FIGS. 5A-5D can be performed with an electronic device similar to or the same as device 100, 300, or 500. In some embodiments, the feature intensity of a contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine a single feature intensity (e.g., a single feature intensity of a single contact). It is noted that the intensity map is not part of the displayed user interface, but is included in Figures 5C to 5D the description to assist the reader. Figures 5C to 5D

[0147] In some embodiments, a portion of a gesture is identified for use in determining a feature intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting location and reaches an ending location at which the contact intensity increases. In this example, the feature intensity of the contact at the ending location is optionally based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the ending location). In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the feature intensity of the contact. For example, the smoothing algorithm optionally includes one or more of the following: an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact for the purpose of determining the feature intensity.

[0148] ​Optionally, intensity of contact on the touch-sensitive surface is 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, a light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, a deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from that typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact of feature intensity below the light press intensity threshold (e.g., and above the nominal contact detection intensity threshold, below which contacts are no longer detected) is 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.

[0149] An increase in intensity of a contact feature 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 in intensity of a contact feature 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 in intensity of a contact feature from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on a touch surface. A decrease in intensity of a contact feature from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting liftoff of a contact from a touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

[0150] 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 a respective press input performed with a respective contact (or multiple contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, a respective operation is performed in response to detecting an increase in intensity of the respective contact above the press input intensity threshold (e.g., a "downstroke" of the respective press input). In some embodiments, a press input includes an increase in intensity of a respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below the press input intensity threshold, and a 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 "upstroke" of the respective press input).

[0151] Figures 5E to 5HThe detection of gestures is shown, including gestures involving contact 562 with an intensity ranging from less than... Figure 5E The light press intensity threshold (e.g., "IT") L The intensity of ) increases to higher than Figure 5H The deep press intensity threshold (e.g., "IT") D The intensity of the press input corresponds to the strength of the press. On the user interface 570, which includes application icons 572A-572D displayed in the predefined area 574, when a cursor 576 is displayed above the application icon 572B corresponding to application 2, a gesture performed using contact 562 is detected on the touch-sensitive surface 560. In some embodiments, the gesture is detected on the touch-sensitive display 504. The intensity sensor detects the intensity of the contact on the touch-sensitive surface 560. The device determines the intensity of the contact 562 within a deep press intensity threshold (e.g., "IT"). D The intensity reaches its peak at 562. Contact 562 is maintained on the touch-sensitive surface 560. In response to a detected gesture, and based on the intensity increasing to a deep press intensity threshold during the gesture (e.g., "IT"), the intensity is increased to a peak value. D The above contact 562 displays the scale representation 578A-578C (e.g., thumbnails) of the document recently opened for application 2, such as... Figures 5F to 5H As shown. In some embodiments, the intensity is a characteristic intensity of the contact compared to one or more intensity thresholds. It should be noted that the intensity map for contact 562 is not part of the displayed user interface, but is included in... Figures 5E to 5H This is intended to assist readers.

[0152] In some implementations, the display of icons 578A-578C includes animation. For example, icon 578A might initially appear near application icon 572B, such as... Figure 5F As shown, as the animation progresses, icon 578A moves upwards, and icon 578B appears near application icon 572B, as shown. Figure 5G As shown in the diagram. Then, representation 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed near application icon 572B, as shown. Figure 5H As shown in the diagram. This indicates that 578A-578C form an array above icon 572B. In some implementations, the animation progresses according to the intensity of contact 562, such as... Figures 5F to 5G As shown, where 578A-578C appear and increase with the intensity of contact 562 towards the deeper pressing strength threshold (e.g., "IT"). D The animation progresses upwards as it increases in intensity. In some implementations, the intensity upon which the animation progresses is based is the characteristic intensity of the contact. Reference can be performed using electronic devices similar to or equivalent to devices 100, 300, or 500. Figures 5E to 5H The aforementioned operations.

[0153] In some embodiments, a device employs intensity hysteresis to avoid an accidental input sometimes referred to as "bouncing," in which the device defines or selects a hysteresis intensity threshold that has a predefined relationship to a 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 percentage of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in intensity of a respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and a 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 "upstroke" of the respective press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold, and optionally a subsequent decrease in contact intensity to an intensity at or below the hysteresis intensity, and a respective operation is performed in response to detecting the press input (e.g., an increase in contact intensity or a decrease in contact intensity depending on the circumstances).

[0154] For ease of explanation, optionally, descriptions of operations performed in response to a press input associated with a press input intensity threshold or in response to a gesture that includes a press input are triggered in response to detecting any of a variety of conditions: an increase in contact intensity above a press input intensity threshold, an increase in contact intensity from an intensity below a hysteresis intensity threshold to an intensity above a press input intensity threshold, a decrease in contact intensity below a press input intensity threshold, and / or a decrease in contact intensity below a hysteresis intensity threshold corresponding to a press input intensity threshold. Additionally, in examples in which an operation is described as being performed in response to detecting a decrease in intensity of a contact below a press input intensity threshold, optionally the operation is performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

[0155] As used herein, an "installed application" refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and / or 500) and is ready to be launched (e.g., become open) on the device. In some embodiments, a downloaded application becomes an installed application with an installer that extracts program portions from a downloaded package and integrates the extracted portions with an operating system of the computer system.

[0156] As used herein, the term "open application" or "application in execution" refers to a software application that has state information retained (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or application in execution is optionally any of the following types of applications: • an active application currently displayed on a display screen of a device using the application; • a background application (or background process) that is not currently displayed but one or more processes of the application are being processed by one or more processors; and • a suspended or hibernating application that is not running but has state information stored in memory (respectively, volatile and non-volatile) and available to resume execution of the application.

[0157] As used herein, the term "closed application" refers to a software application that does not have state information maintained (e.g., state information of the closed application is not stored in memory of the device). Thus, closing an application includes stopping and / or removing application processes of the application and removing state information of the application from memory of the device. Generally, opening a second application while in a first application does not close the first application. The first application becomes a background application when the second application is displayed and the first application ceases to be displayed.

[0158] Attention is now directed to embodiments of user interfaces ("UIs") and associated processes implemented on an electronic device, such as portable multifunctional device 100, device 300, or device 500.

[0159] Figures 6A to 6W Example user interfaces for monitoring fitness activities are shown in accordance with some embodiments. In particular, Figures 6A to 6I , Figure 6M , Figure 6P and Figure 6U user interfaces for monitoring fitness activities when the device is in a youth- dedicated device mode (e.g., a mode optimized for users under the age of 13), while Figures 6J to 6L , Figure 6N and Figure 6Q corresponding user interfaces for monitoring fitness activities when the device is in a second device mode (e.g., a mode optimized for adults and users over the age of 13). Figures 6R to 6W Additional user interfaces related to transitioning between device modes are shown. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 7A to 7C .

[0160] Figure 6A Device 600 is shown with display 602, rotatable and depressible input mechanism 604 (e.g., rotatable and depressible relative to a housing or frame of the device), and button 606. In some embodiments, device 600 is a wearable electronic device, such as a smart watch. In some embodiments, device 600 includes one or more features of devices 100, 300, or 500.

[0161] As Figure 6AAs shown, while operating in the young device mode, device 600 displays a clock user interface 608A on display 602. Clock user interface 608A includes a numeric indication of time 610 (e.g., a presentation of a digital clock that displays current hour, minute, and second values) and a plurality of affordances (e.g., dial complication), each of which is associated with an application on device 600. A date affordance 612 indicates the current date and, when selected, launches a calendar application. A workout affordance 614, when selected, launches a workout application (e.g., an application that tracks exercises performed by a user of device 600).

[0162] As Figure 6A depicted, clock user interface 608A also includes a plurality of affordances that indicate user activity data obtained from an activity tracking application (e.g., activity metrics that quantify recorded physical activity of a user of device 600 during the day). Clock user interface 608A includes a numeric activity affordance 616, a graphical activity affordance 618, and a textual activity affordance 620. Data indicated by each activity affordance is updated in response to receiving data from the associated activity application (e.g., as described below).

[0163] Numeric activity affordance 616 includes a movement value 616A that represents a movement metric (e.g., minutes of general physical movement by a user of device 600), a workout value 616B that represents a workout metric (e.g., minutes of vigorous physical activity by a user of device 600, such as time spent participating in sports), and a standing value 616C that represents a standing hour metric (e.g., number of hours in which a user of device 600 stood for a minimum amount of time, such as 2 minutes). In some embodiments, the movement metric represented by movement value 616A is a time-based activity metric (e.g., minutes of activity that meet an activity threshold). In some embodiments, the movement metric is derived from another metric based on received user activity data (e.g., a metric based on energy or calories).

[0164] The graphical activity performance indicator 618 includes three concentric rings (e.g., a movement ring 618A; an exercise ring 618B; and a standing ring 618C), corresponding to movement values ​​616A, exercise values ​​616B, and standing values ​​616C, respectively. The angular length of each ring (e.g., the angular distance relative to 360 degrees covered by the arc associated with each ring) indicates current progress toward the corresponding activity goal associated with the ring (e.g., ring 618C shows 60% of the complete ring, indicating 6 standing hours out of a daily goal of 10 standing hours). The textual activity performance indicator 620 includes a textual representation of activity data values ​​(e.g., textual movement value 620A, textual exercise value 620B, and textual standing value 620C), corresponding to the data described above with respect to the digital activity performance indicator 616 and the graphical activity performance indicator 618 (e.g., textual movement value 620A indicates movement minutes and corresponds to movement value 616A and ring 618A).

[0165] exist Figure 6A In this process, device 600 receives user input 622 corresponding to a selection of the graphical activity display 618. In response to user input 622, device 600 initiates an activity tracking application associated with the display (e.g., display of a user interface for an activity application, such as user interface 624A, etc.). Figure 6B (As depicted).

[0166] like Figure 6B As shown, the user interface 624A includes an active panel 626 (e.g., a moving panel 626A, an exercise panel 626B, and a standing panel 626C) that outlines user activity data displayed by a digital activity indicator 616, a graphical activity indicator 618, and a text activity indicator 620 (e.g., the moving panel 626A includes a presentation of data shown by movement values ​​616A, movement rings 618A, and text movement values ​​620A).

[0167] exist Figure 6B At this point, device 600 receives user input 628. In response to user input 628 (e.g., a tap with a feature strength exceeding a threshold strength, or an input lasting longer than a threshold time period), device 600 displays user interface 630, such as... Figure 6C The user interface 630, as depicted, includes a change target indication 632 for changing user activity targets (e.g., movement targets, movement minute targets) associated with user activity metrics. Figure 6C A device 600 is depicted that receives user input 634 corresponding to a selection of a change target indication 632. In response to user input 634, device 600 displays a user interface 636, such as... Figure 6D What is depicted.

[0168] like Figure 6D As shown, the user interface 636 allows the user to adjust the active target value 638 by selecting to add an energy indicator 640 or subtract an energy indicator 642. Figure 6D A device 600 is depicted that receives user input 644 corresponding to a selection of an added power display 640, which causes the device 600 to display a user interface 646, such as Figure 6E The user interface 646 depicts an activity target value 638 that has been updated to a new value in response to user input 644 (e.g., now reflecting 110 mobile minutes instead of as previously shown). Figure 6D (The 100 moving minutes shown).

[0169] exist Figure 6E In this process, device 600 receives user input 648 at the updated display indicator 650. In response to user input 648, device 600 saves the updated active target 638 and redisplays the user interface 624A (e.g., as shown in the image). Figure 6F (As depicted). Figure 6F As shown, the mobile dial 626A displays user activity data based on the updated movement target of 110. For example, the mobile dial 626A indicates that only 41% of the current movement target is active (e.g., compared to...). Figure 6B The previous 45% (as shown) has been completed (e.g., 45 / 110).

[0170] exist Figure 6F At this location, device 600 receives user input 652, a press of the rotatable and pressable input mechanism 604. In response to user input 652, device 600 displays a clock user interface 608A (e.g., a watch face) with an updated graphical active display 618, such as... Figure 6G What is depicted. Figure 6G The current time depicted is 2:09:55 on the 22nd day of the month (e.g., May 2019) as shown in date display 612 (e.g., "22") (as shown in device 600). Figure 6A The clock user interface 608A depicts a clock user interface that has been active for 16 seconds.

[0171] Figure 6H A clock user interface 608A depicts the day following the 22nd of the month (e.g., the 23rd day of May 2019). The digital activity indicator 616, the graphical activity indicator 618, and the text activity indicator 620 have been reset to reflect that the application has not recorded activity data for the current day (e.g., the 23rd day of May 2019). For example, the text movement value 620A indicates that "0M-minutes" (e.g., moving minutes) has been recorded.

[0172] In response to determining that the user of device 600 has changed from 12 years old to 13 years old (e.g., the user's 13th birthday is the 23rd day of the month (e.g., May 2019), device 600 displays user interface 654, as follows: Figure 6I As depicted. In some embodiments, device 600 determines age changes by comparing birth data associated with the user of device 600 with the current date. User interface 654 includes prompts describing the availability of a new device mode (e.g., an adult device mode associated with displaying active calorie measurements), an upgrade indication 656 for selecting to enter the new adult device mode, and a deactivation indication 658 for maintaining operation of device 600 in a youth device mode (e.g., a device mode associated with displaying mobile minute measurements). In some embodiments, device 600 displays user interface 654 for a predetermined period of time (e.g., one day) before the user's age exceeds a threshold age (e.g., 13 years old).

[0173] exist Figure 6I In this process, device 600 receives user input 660 corresponding to the selection of upgrade capability display 656. In response to user input 660, device 600 switches from a youth mode (e.g., a mode displaying mobile minutes measurement, such as...) to a youth mode. Figure 6A and Figure 6B The operation is switched to adult mode (e.g., displaying different measurements, moving calories, etc.). Figure 6K and Figure 6L (As shown) Operation. In response to user input 660, device 600 displays adult mode welcome user interface 662B, as shown. Figure 6J The description further emphasizes that device 600 is currently operating in adult device mode. In some implementations, the user selects to upgrade the power display midday (e.g., noon on Monday, May 23), and the transition to adult mode does not occur until the following day (e.g., 12:00 noon on Tuesday, May 24). In some implementations, after selecting to upgrade the power display, the device may no longer operate in youth mode (e.g., the transition to adult mode is irreversible after the user's age exceeds a predetermined age).

[0174] like Figure 6JThe depicted adult mode welcome interface 662B includes an activity goal summary 664, a personal information summary 668, and a power indicator removal 672. The activity goal summary 664 includes a change goal power indicator 666 for editing the activity goal. In some embodiments, the initial activity goal is set to a default value associated with the device 600 operating in adult mode (e.g., 300 mobile calories, 30 minutes of exercise, and 12 hours of standing). In some embodiments, the initial activity goal is based in part on user data (e.g., historical activity, age, gender, weight, etc.). In some embodiments, selecting the change goal power indicator 666 causes the device 600 to display something similar to... Figure 6D and Figure 6E The depicted interfaces are a series of interfaces that allow updating various activity measurement goals. Personal Information Summary 668 includes a summary of personal data (e.g., height and weight) used by device 600 to derive activity measurement data (e.g., data showing progress toward goals for calories burned, minutes of exercise, and hours of standing shown in Activity Goal Summary 664) and a change information display 670 for editing personal data. In some embodiments, selecting the change information display 670 causes device 600 to display a series of interfaces allowing updating of the user's height and weight information. In some embodiments, goals and personal information are changed via a settings menu instead of the adult mode welcome interface 662B.

[0175] In some implementations, in response to determining that the user of device 600 has changed from 17 to 18 years old while the device is in youth mode (e.g., the user's 18th birthday is the 23rd day of the month (e.g., May 2019)), device 600 refrains from displaying such... Figure 6I The depicted user interface 654, instead of directly switching (e.g., not accepting user input corresponding to consent or permission) to operate in adult mode (e.g., the device mode associated with displaying mobile calorie measurements), then displays a welcome user interface 662B (e.g., the device 600 switching from youth mode to adult mode is not optional). In some embodiments, the switch to adult mode does not occur until one day after the user's age exceeds a predetermined threshold (e.g., the user becomes 18 on Monday, May 23, and the device 600 switches to adult mode on Tuesday, May 24).

[0176] exist Figure 6J Device 600 receives user input 674 at the power indicator 672. In response to user input 674, device 600 displays user interface 608B (e.g., a watch face in adult mode), such as... Figure 6K The description. Figure 6KA clock user interface 608B (e.g., an adult version corresponding to clock user interface 608A) is depicted, which includes an updated time and date display (e.g., indicating the new current time and date) and updated activity complexity blocks (e.g., activity complexity blocks 616, 618, and 620 display data indicating current progress toward the corresponding activity goal). For example, as... Figure 6K The description in the text activity complex block 620 includes a description of CAL values ​​(e.g., mobile calorie metrics) rather than M-minute values ​​(e.g., mobile minute metrics). In some embodiments, the mobile calorie metric is based at least in part on user-defined data (e.g., weight, height, gender, or age). In some embodiments, the mobile calorie metric is based at least in part on data measured by the device (e.g., heart rate, historical exercise data, etc.).

[0177] exist Figure 6K In this process, device 600 receives user input 622B, corresponding to input selecting the graphical activity display 618. In response to user input 622B, device 600 launches the activity tracking application, causing device 600 to display user interface 624B (e.g., corresponding to...). Figure 6B The youth mode user interface 624A depicted (adult mode user interface), such as Figure 6L The user interface 624B includes an activity panel 626 that outlines user activity data displayed by a digital activity indicator 616, a graphical activity indicator 618, and a text activity indicator 620 when the device is operated in adult mode (e.g., a device mode associated with displaying mobile calorie measurements).

[0178] Figure 6M and Figure 6N The description depicts the display of corresponding fitness application interfaces when device 600 operates in youth mode (e.g., a device mode associated with displaying mobile minute metrics) and adult mode (e.g., a device mode associated with displaying mobile calorie metrics). In response to, for example, detecting... Figure 6AThe device 600 displays a user interface 676A upon selection of a fitness performance indicator 614. The user interface 676A includes a fitness group 678A (e.g., including performance indicators for outdoor running, outdoor walking, and outdoor cycling activities, which, when selected, cause the device 600 to initiate an activity monitoring process corresponding to the selected fitness activity). In some embodiments, the activity monitoring process includes receiving motion data based on user movement (e.g., movement of a device worn by the user), determining fitness metrics (e.g., active calorie burn, total calorie burn, heart rate, distance traveled, etc.) based on the received motion data, and displaying the fitness metrics on one or more display devices. In some embodiments, the activity monitoring process determines fitness metrics based on algorithms optimized for younger users (e.g., specifically tuned to provide accurate metrics for children rather than adults).

[0179] In response to, for example, detecting an object Figure 6K The device 600 displays a user interface 676B upon selection of a fitness indicator 614. The user interface 676B includes a fitness group 678B, which, in addition to other fitness indicators (e.g., indoor running, indoor walking, indoor cycling, pool swimming, etc.), includes indicators corresponding to each fitness displayed in the fitness group 678A. In some embodiments, the fitness group 678B includes a larger subset of available fitnesss accessible by selecting an indicator such as "More Fitness".

[0180] In some implementations, when device 600 operates in youth mode (e.g., a device mode associated with displaying mobile minute metrics), additional fitness activities (e.g., additional fitness activities from fitness group 676B or other fitness activities not included in fitness group 678B) can be added to fitness group 678A by selecting a “More Fitness” indicator 680A, etc. In some implementations, in response to selecting a “More Fitness” indicator 680A, device 600 displays a prompt indicating that the additional fitness activities may not be optimized for younger users (e.g., “Adding additional fitness activities may result in accurate activity tracking”). In some implementations, fitness activities added in youth mode appear in adult mode after transitioning (e.g., if archery is added to fitness group 678A in youth mode, then fitness group 678B additionally includes archery when transitioning to adult mode).

[0181] Figure 6O A settings menu (e.g., watch settings) for device 600 is depicted, including a fitness settings display 684 for accessing a fitness application on device 600 (e.g., a fitness application associated with fitness complexity block 614) and an activity settings display 688 for accessing settings associated with an activity application (e.g., an activity application associated with activity complexity block 618). Figure 6OIn this process, device 600 receives user input 686 corresponding to the selection of fitness settings indicator 684. In response to receiving user input 686, when device 600 is operating in youth mode (e.g., a device mode associated with displaying mobile calorie measurements), user interface 690A is displayed (e.g., as shown in the image). Figure 6P (As depicted). The user interface 690A includes a fitness settings group 692A (e.g., including an indicator for adjusting settings associated with the fitness application).

[0182] In response to receiving user input 686 while the device 600 is operating in adult mode (e.g., a device mode associated with displaying mobile calorie measurements), the device 600 displays a user interface 690B (e.g., as shown in the image). Figure 6Q (As depicted). Compared to user interface 690A (e.g., the corresponding youth mode interface), user interface 690B includes additional fitness settings indications. For example, fitness settings group 692B includes indications for enabling or disabling fitness features that are not available in youth mode (e.g., start fitness reminder, end fitness reminder, and detect fitness equipment). In some embodiments, when device 600 switches from operating in youth mode to operating in adult mode, additional features included in fitness settings group 692B are disabled by default (e.g., features not included in fitness settings group 692A or features that are otherwise available when device 600 operates in youth mode).

[0183] Figure 6R and 6S A second device (e.g., device 500) is shown wirelessly linked to device 600. In some embodiments, device 600 receives configuration data from device 500 indicating a selection of a device mode (e.g., in response to receiving input 582 at youth mode enablement indicator 580, device 500 transmits data indicating a request from device 600 to enable youth mode). In some embodiments, in response to receiving data indicating a selection of a device mode, device 600 displays a user interface 694, such as... Figure 6T As depicted. In some implementations, data indicating the selection of a youth mode from a second device indicates parental consent (e.g., device 600 collects information from users of device 600 who are under 13 years old).

[0184] exist Figure 6T In this embodiment, device 600 displays a warning prompt (e.g., interface 694) instructing the user to select a device mode (e.g., adult mode) from device 500. In some implementations, in response to detecting an input corresponding to a selection on the confirmation display 696, device 600 will switch from operating in a first mode (e.g., adult mode) to operating in a second mode (e.g., youth mode).

[0185] exist Figure 6T In the process, device 600 receives input 696 corresponding to the selection of mode change confirmation indication 695, and in response to receiving input 696, device 600 displays... Figure 6U The welcome screen for the youth mode is 622A. (Example) Figure 6U The youth mode welcome screen 662A depicted includes elements corresponding to those in the adult mode welcome screen 662B (e.g., as referenced above). Figure 6J (as described above). In some embodiments, the initial activity goal is set to a default value associated with the device 600 operating in youth mode (e.g., 100 minutes of movement, 60 minutes of exercise, and 10 hours of standing). In some embodiments, the initial activity goal is based in part on user data (e.g., historical activity, age, gender, weight, etc.). In some embodiments, changing the selection of the target energy display causes the device 600 to display something similar to... Figure 6D and Figure 6E The interfaces shown are a series of interfaces that allow for updating activity metric goals. In some implementations, goals and personal information are changed via a settings menu rather than from a welcome prompt.

[0186] Figure 6V The active application settings user interface 697 of device 600 is depicted. In some embodiments, in response to receiving input corresponding to a selection of the active settings enablement display 688 (e.g., ... Figure 6O As depicted), device 600 displays the active application settings user interface 697. (For example...) Figure 6VAs depicted, the Activity Application Settings User Interface 697 includes an Activity Power Indicator for enabling or disabling features associated with an Activity Application on device 600 (e.g., an Activity Application associated with Activity Power Indicator 616). In some embodiments, the Activity Application Settings User Interface 697 includes a Mode Power Indicator 698 that, when selected, causes device 600 to initiate a transition from operating in a first device mode (e.g., Youth Mode) to operating in a second device mode (e.g., Adult Mode). In some embodiments, the Mode Power Indicator 698 is not displayed or disabled, such that user input detected at the power indicator does not initiate a transition between device modes. In some embodiments, once device 600 transitions to Adult Mode (e.g., a mode associated with displaying mobile calorie measurements), the Mode Power Indicator 698 is not displayed as part of the Activity Application Settings User Interface 698, thereby preventing the user of device 600 from manually changing the device mode. In some implementations, in response to receiving configuration data from a second device (e.g., device 500), mode indication 698 is displayed in a disabled state (e.g., grayed out and not responding to user input), the configuration data including instructions for disabling mode changes on device 600 (e.g., in response to device 500 receiving input at the "Allow Change" indication, e.g., as...). Figure 6S (As depicted), device 600 receives data from device 500.

[0187] exist Figure 6W In this embodiment, device 600 displays a warning prompt interface 699 in response to receiving a request to change between adult mode and youth mode (e.g., selecting a mode indication 698 for enabling and disabling youth mode). In some embodiments, in response to detecting input corresponding to a confirmation indication selection, device 600 will only switch from operating in the first mode (e.g., youth mode) to operating in the second mode (e.g., adult mode) and vice versa (e.g., the device will not switch operating modes without first confirming that the user intends to initiate a mode change).

[0188] Figures 7A to 7D This is a flowchart illustrating a method for monitoring fitness activity using electronic devices according to some embodiments. Method 700 is performed by electronic devices (e.g., 100, 300, 600, 800) having a display device and one or more sensors (e.g., accelerometer, GPS sensor; heart rate sensor). In some embodiments, the electronic device is a wearable device with attachment mechanisms such as a strap. Some operations in method 700 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0189] In some embodiments, the electronic device (e.g., 600) includes a computer system. The computer system optionally communicates with a display generating component and one or more input devices (e.g., wired communication, wireless communication). The display generating component is configured to provide visual output, such as a display via a CRT monitor, a display via an LED monitor, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. One or more input devices are configured to receive input, such as a touch-sensitive surface that receives user input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separate from the computer system. Therefore, the computer system can transmit data (e.g., image data or video data) via wired or wireless connections to an integrated or external display generating component to visually generate content (e.g., using a display device), and can receive input from one or more input devices via wired or wireless connections.

[0190] As described below, Method 700 provides an intuitive way to monitor fitness activity. This method reduces the cognitive burden on users monitoring fitness activity, thereby creating a more efficient human-computer interface. For battery-powered computing devices, it enables users to monitor fitness activity faster and more effectively and increases the time interval between battery charges.

[0191] When the electronic device (e.g., device 600) is in a first device mode (e.g., youth mode) (e.g., Figures 6A to 6H When device 600 is operating, the electronic device detects (e.g., based on received updated information; based on the context of the device, such as the current date) (e.g., using birth date information, where the current date indicates the user is a different age) (702) a change in a first user physical characteristic (e.g., age; weight; body mass index) from a first physical characteristic value (e.g., the user is 17 years old) to a second physical characteristic value (e.g., the user is 18 years old) (e.g., ... Figure 6G and Figure 6H Device 600 detects changes in the user's age based on time and / or date.

[0192] In some implementations, the first user physical characteristic is the age of the user associated with the electronic device (e.g., in years), the first physical characteristic value is a first age value (e.g., a value less than 13 years old; a value less than 17 years old), and the second physical characteristic is a second age value greater than the first age value (e.g., 13 years old; 17 years old).

[0193] In response to the detection of a change in a first user's physical characteristics (704), the electronic device initiates (706) a process (in some embodiments, this process is completed) to transition from a first device mode (e.g., youth mode) to a second device mode (e.g., adult mode) based on the determination that a second physical characteristic value meets a set of mode change criteria (e.g., the second physical characteristic value exceeds a predetermined threshold; the second physical characteristic value matches one or more values ​​in a predetermined set of values) (e.g., device 600 displays user interface 654). Initiating (e.g., automatically, without further user input) the transition from the first device mode (e.g., youth mode) to the second device mode (e.g., adult mode) based on the determination that a second physical characteristic value meets a set of mode change criteria allows the user to quickly and easily access the second device mode. Performing the operation when a set of conditions has been met without further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and effectively.

[0194] In some embodiments, the process of initiating a transition from a first device mode to a second device mode includes displaying (708) a first confirmation user interface including a first confirmation power indication (e.g., "upgrade") (e.g., 656), receiving (710) input corresponding to the first confirmation power indication (e.g., 660), and in response to receiving input corresponding to the first confirmation power indication, transitioning (712) from the first device mode (e.g., immediately, after a predetermined time, or at a selected time (e.g., 12:00 AM)) to the second device mode (e.g., 622B). In some embodiments, the confirmation user interface includes a cancel / reject power indication (e.g., 658) that, when selected, keeps the device in the first mode.

[0195] In some implementations, detecting a change in a first user's physical characteristic from a first physical characteristic value to a second physical characteristic value occurs immediately. In some implementations, initiating a transition from a first device mode to a second device mode includes transitioning from the first device mode to the second device mode at a second time later than the first time (e.g., the first time). Figure 6K The next (e.g., upcoming) occurrence at a specific time of day after (e.g., the next 12:00 AM). In some implementations, the process of initiating the transition from child mode to adult mode occurs in the middle of the day (e.g., Monday), and the transition to adult mode begins on the following day (e.g., Tuesday).

[0196] In some implementations, the process of initiating a transition from a first device mode to a second device mode includes transitioning from the first device mode to the second device mode. In some implementations, after transitioning from the first device mode to the second device mode, the electronic device waives (714) the option (e.g., any option) to transition from the second device mode back to the first device mode. Waiving the option to transition from the second device mode back to the first device mode after transitioning from the first device mode allows the device to be protected (e.g., locked) in the second device mode without (e.g., unintentionally) reverting to the first device mode, which in turn enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently. In some implementations, the transition from the first device mode to the second device mode is irreversible under normal use (e.g., without resetting the electronic device). In some implementations, the second electronic device does not include (or provides) discrete settings or options for transitioning from the second device mode to the first device mode.

[0197] In response to the detection of a change in the physical characteristics of the first user (704), and based on the determination that a second physical characteristic value does not meet a set of mode change criteria, the electronic device remains (716) in a first device mode (e.g., youth mode). Figure 6G (608A in the middle).

[0198] When the electronic device is operating in a first device mode (e.g., youth mode), the electronic device receives (718) first user activity data (e.g., data detected by one or more sensors of the device) from a first set of sensors.

[0199] After receiving the first user activity data, the electronic device displays (720) user activity data received from the first set of sensors (e.g., calculated from the following; derived from the following). Figure 6A and Figure 6G The first activity metric (e.g., visual indication of the metric) of 616, 618, and 620) Figure 6B The first active user interface (626) is used. In some embodiments, the first active user interface does not include a second active metric (e.g., 608A, 624A). In some embodiments, the first active user interface includes a first unit of measurement, such as mobile minutes (e.g., ...). Figure 6A 620A and Figure 6B(626A) Activity metrics based on received activity data. When the electronic device operates in a first device mode, a first activity user interface displaying (e.g., automatically displayed, without further user input) including the first activity metric provides the user with quick and easy access to activity metrics that are likely or more likely to be relevant or useful to the user. Reducing the amount of input required to perform operations enhances device operability and makes the user device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), thereby further reducing power consumption and extending device battery life by enabling users to use the device more quickly and efficiently.

[0200] When the electronic device is operating in a second device mode (e.g., adult mode) (722), the electronic device receives (724) second user activity data (e.g., data detected using one or more sensors of the device) from the first set of sensors (e.g., receiving activity data displayed on the user interface 608B).

[0201] When the electronic device operates in a second device mode (e.g., adult mode) (722), after receiving second user activity data, the electronic device displays (726) a second activity user interface (e.g., 608B) that includes a second activity metric different from the first activity metric, based on (e.g., calculated from; derived from) the user activity data received from the first set of sensors. In some embodiments, the second activity user interface does not include the first activity metric (e.g., 608B, 624B). In some embodiments, the second activity user interface includes an activity metric based on the received activity data using a second unit of measurement, such as calories burned (e.g., 608B, 624B). Displaying (e.g., automatically, without further user input) the second activity user interface that includes the second activity metric when the electronic device operates in the second device mode provides the user with quick and easy access to an activity metric that may or is more likely to be relevant or useful to the user. Reducing the amount of input required to perform an operation enhances device operability and makes the user device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), thereby further reducing power consumption and extending device battery life by enabling users to use the device more quickly and efficiently.

[0202] In some implementations, when the device is in a first corresponding device mode selected from the group consisting of a first device mode and a second device mode, the electronic device receives data from an external device (e.g., a smartphone paired with or connected to the electronic device) (e.g., Figures 6R to 6SThe device 500 receives (728) a request to change device mode (e.g., a request to change to a different mode; a request to change to a specific mode (e.g., specifically, a first device mode or a second device mode) (e.g., 694). In some embodiments, in response to receiving a request to change device mode, the electronic device changes (730) to a second corresponding device mode selected from the group consisting of the first device mode and the second device mode, wherein the second corresponding device mode is different from the first corresponding device mode (e.g., if the first corresponding device mode is the first device mode, then the second corresponding device mode is the second device mode, and vice versa).

[0203] In some embodiments, when the device is in a third corresponding device mode selected from the group consisting of a first device mode and a second device mode, the electronic device receives (732) a second request to change the device mode from a second external device (e.g., a smartphone paired with or connected to the electronic device). This request may be for changing to a different mode or a specific mode (e.g., specifically the first or second device mode). In some embodiments, in response to receiving the second request to change the device mode, the electronic device displays (734) a second confirmation user interface (e.g., 694), which includes a second confirmation enable indication (e.g., 695) and a first rejection enable indication (e.g., an interface for accepting or rejecting the change request).

[0204] In some embodiments, when displaying the second confirmation power indication, the electronic device receives (736) a first input (e.g., 696). In some embodiments, in response to receiving the first input (738), based on determining that the first input corresponds to the second confirmation power indication, the electronic device switches (740) to a second corresponding device mode selected from the group consisting of a first device mode and a second device mode, wherein a third corresponding device mode is different from a fourth corresponding device mode (e.g., if the third corresponding device mode is the first device mode, then the fourth corresponding device mode is the second device mode, and vice versa) (e.g., Figure 6U (622A). In some embodiments, in response to receiving a first input (738), the electronic device maintains (742) a third corresponding device mode (e.g., abandons the mode change) based on determining that the first input corresponds to a second confirmation indication.

[0205] In some embodiments, the electronic device includes an input device (e.g., an integrated input device, such as a touch-sensitive surface). In some embodiments, when the device is in a fifth corresponding device mode selected from the group consisting of a first device mode and a second device mode, the electronic device receives (744) a third request to change the device mode (e.g., selection of a mode change indication) via the input device. In some embodiments, in response to receiving the third request to change the device mode, the electronic device changes (746) to a sixth corresponding device mode selected from the group consisting of the first device mode and the second device mode, wherein the sixth corresponding device mode is different from the fifth corresponding device mode (e.g., if the fifth corresponding device mode is the first device mode, then the sixth corresponding device mode is the second device mode, and vice versa).

[0206] In some implementations, when the electronic device operates in a first device mode, the electronic device displays (748) a first body activity tracking user interface (e.g., a fitness user interface) (e.g., 676A), which includes a first set of one or more activity tracking power indicators (e.g., 678A), which includes a first activity tracking power indicator (e.g., an outdoor running power indicator, an outdoor walking power indicator), which initiates a first activity tracking function (e.g., an outdoor running tracking function, an outdoor walking tracking function) when selected. In some implementations, when the electronic device operates in a second device mode, the electronic device displays (750) a second body activity tracking user interface (e.g., a fitness user interface) (e.g., 676B), which includes a second set of one or more activity tracking indications (e.g., 678B), which includes a first activity tracking indication and a second activity tracking indication (e.g., a pool swimming indication), which initiates a second activity tracking function (e.g., a swimming tracking function) when selected, wherein the second activity tracking indication is not included in the first body activity tracking user interface (e.g., not included in the first set of one or more activity tracking indications; not included in the default instance of the first body activity tracking user interface). By displaying a first or second body activity tracking user interface based on whether the electronic device operates in a first device mode or a second device mode, the user is given quick and easy access to a more relevant and / or useful activity tracking user interface. This, in turn, enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0207] In some implementations, the top-level fitness in the youth mode (e.g., the initial or first fitness activity displayed when the fitness app is launched) (e.g., 678A) includes a subset of the fitness in the adult mode (e.g., the youth mode includes outdoor running, outdoor walking, and outdoor cycling, while the adult mode includes fitness in addition to outdoor running, outdoor walking, and outdoor cycling). In some implementations, the adult mode includes a set of fitness corresponding to the fitness in the youth mode (e.g., the adult mode includes outdoor running fitness, but it is optimized to be different from the outdoor running fitness in the youth mode) (e.g., 678B).

[0208] In some implementations, when the electronic device operates in a first device mode, the electronic device displays (752) a first settings user interface (e.g., a settings user interface for an activity-related application of the electronic device) (e.g., 690A), the first settings user interface including a first set of one or more settings indications (e.g., 692A), the first set of one or more settings indications including a first settings indication (e.g., an auto-pause indication), the first settings indication changing a first setting (e.g., an auto-pause setting) when selected. In some implementations, when the electronic device operates in a second device mode, the electronic device displays (754) a second settings user interface (e.g., 690B), which includes a second set of one or more settings indications (e.g., 692B), including a first settings indication and a second settings indication (e.g., a start fitness reminder indication), which, when selected, changes a second setting (e.g., a setting that controls whether to send a start fitness reminder), wherein the second settings indication is not included in the first settings user interface (e.g., not included in the first set of one or more settings indications; not included in the default instance of the first settings user interface). In some implementations, features associated with the second settings indication are disabled by default when switching from a first device mode (e.g., youth mode) to a second device mode (e.g., adult mode). By displaying a first settings user interface or a second settings user interface respectively based on whether the electronic device operates in a first device mode or a second device mode, the user is given quick and easy access to settings user interfaces that are more relevant and / or more useful to the user. This, in turn, enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0209] In some implementations, the first activity metric is a time-based activity metric (e.g., activity minutes that meet an activity threshold). Figure 6A (referring to 616A). In some embodiments, the first activity metric is derived from another metric (e.g., an energy- or calorie-based metric) based on the received activity data. In some embodiments, the second activity metric is an energy-based activity metric (e.g., calories). Figure 6K and Figure 6L (622B, "card"). In some implementations, the second activity measure is based at least in part on user-defined data (e.g., weight, height, gender, or age, etc.) (e.g., 668). In some implementations, the second activity measure is based at least in part on data measured by the device (e.g., heart rate, historical exercise data, etc.).

[0210] In some implementations, the user interface for displaying the first activity includes displaying a first activity target (e.g., a target of 30 minutes of activity exceeding an activity threshold) that is a first activity metric. The first activity target has a first value (e.g., 30 minutes). Figure 6A The 608A, Figure 6B (e.g., 624A), and when displaying a first activity target for a first activity metric, the electronic device receives a first set of one or more inputs (e.g., 622, 628, 634, 644), and in response to receiving the first set of one or more inputs (e.g., one or more inputs in the user interface for adjusting the activity target value), the electronic device displays a second instance of the first activity user interface, the second instance including a second activity target for the first activity metric, the second activity target having a second value different from the first value of the first activity target (e.g., 60 minutes) (e.g., 624A), and when displaying a first activity target for a first activity metric, the electronic device receives a first set of one or more inputs (e.g., 622, 628, 634, 644), and in response to receiving the first set of one or more inputs (e.g., one or more inputs in the user interface Figure 6F 624A and Figure 6G (608A).

[0211] In some implementations, the activity goal changes to a new default value upon mode transition (e.g., from 10 standing hours for youth to 12 standing hours for adults, etc.) (e.g., 622A, 622B). In some implementations, in response to the addition of a top-level (e.g., default) fitness activity displayed in children's mode (e.g., via a "More Fitness" indicator), the electronic device displays a warning about optimization (e.g., "Adding additional fitness may result in inaccurate activity tracking"). Displaying the warning about optimization allows the user to quickly and easily recognize that adding additional fitness may (e.g., negatively) affect the accuracy of activity tracking for existing fitness activities. Providing the user with improved visual feedback enhances device operability and makes the user device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling the user to use the device more quickly and efficiently. In some implementations, fitness activities added in youth mode appear in adult mode after the transition (e.g., if archery is added in youth mode, the default fitness list includes all regular activities plus archery upon transition).

[0212] In some implementations, the electronic device displays a welcome or settings prompt (e.g., a prompt displaying the current target and personal information and providing an editable capability representation) after switching modes (e.g., 622A, 622B). In some implementations, the target and personal information are changed via a settings menu rather than from a welcome / settings prompt. In some implementations, the electronic device displays a warning prompt in response to switching modes at the device and requires confirmation before switching modes (e.g., 654, 694, 699).

[0213] It should be noted that the above reference method 700 (for example, Figures 7A to 7D The details of the process described above also apply in a similar manner to the methods described below. For example, method 700 optionally includes one or more features of the various methods described above with reference to method 900. For example, device 600 may display comments (as described below relative to...) when operating in a first device mode (e.g., youth mode). Figures 8A to 8H As described in devices 802 and 804), and displays different comments when operating in a second device mode (e.g., adult mode) (as described below relative to...). Figures 8A to 8H (As described in device 800). For the sake of brevity, these details will not be repeated below.

[0214] Figures 8A to 8H An exemplary user interface for providing dynamic activity comments is shown according to some implementation schemes. Specifically, Figures 8A to 8HA user interface is shown that dynamically provides activity comments in response to activity-based events (e.g., congratulatory comments, encouraging statements, or new activity challenges) based on the characteristics of the device-based user (e.g., age) and the activity-based goals being met or nearing completion. Figures 8A to 8H A comparison was made of the corresponding user interfaces (e.g., user interfaces including text and graphical content) provided by devices (e.g., devices 800, 802, 804) in various scenarios related to monitoring or tracking physical activity (e.g., conditions that trigger the device to display comments), while the devices are operated by users with different characteristics (e.g., users whose ages are determined to be within a predetermined age range, such as those under 9 years old, those between 9 and 12 years old, and those over 12 years old). In some implementations, simplified standing reminders, daily guidance, goal completion notifications, activity summaries, and special challenge notifications are provided to the first type of user instead of the second type of user.

[0215] In some implementations, user characteristics include input of the user's indicated cognitive abilities (e.g., user's age, highest level of education, standardized test scores). In some implementations, user input is related to characteristics (e.g., cognitive abilities). For example, during the initial setup of device 800, device 802, and / or device 804, the user may input information related to: user's age, user's highest level of education (e.g., elementary school class, expected high school or college graduation date, college degree, master's degree, doctoral degree, professional degree), standardized test results achieved by the user (e.g., National Assessment of Educational Progress (NAEP), Metropolitan Achievement Test (MAT8), one or more state-managed standardized tests, such as California Standardized Tests and Reports (STAR), Texas Assessment of Knowledge and Skills (TAK), and New York State Testing Program (NYSTP)), and / or options selected by the user related to the user's preferences for activity comments (e.g., options for the user to understand sample activity comments of multiple best sample activity comments and / or to use emojis in activity comments). In some implementations, the output of the activity comments is based on the information input by the user.

[0216] exist Figures 8A to 8H In this design, devices 800, 802, and 804 (and each corresponding device is depicted as a user interface to be displayed) are each associated with (e.g., operated by) users of different ages. Device 800 is associated with users in a first age range (e.g., 13 years or older). Device 802 is associated with users in a second age range (e.g., 9 to 12 years old). Device 804 is associated with users in a third age range (e.g., less than 9 years old).

[0217] In some embodiments, devices 800, 802, and 804 (collectively referred to below as the "device group") determine a user's age by interpreting age data received at the respective device (e.g., configuration or profile information entered at the respective device or otherwise transmitted to and / or received by the respective device). In some embodiments, devices 800, 802, and 804 determine a user's age by comparing age data received at the device with data representing the current date. The user interface in these figures is used to illustrate the processes described below, including... Figures 9A to 9B The process in.

[0218] Figure 8A Devices 800, 802, and 804 are described (e.g., as described above relative to...). Figure 6A Each of the devices described in device 600). Figure 8A The device 800 depicts a clock user interface 608B (e.g., as described above relative to...). Figure 6J (as described above), and devices 802 and 804 display a clock user interface 608A (e.g., as described above relative to...). Figure 6A The clock user interface 608B (left illustration) and clock user interface 600A (center illustration and right illustration) each indicate the current time of the night, 10:09:00 (e.g., as depicted by time indicator 610) and indicate that the motion measurement target is nearing completion (e.g., the activity ring 618-A has almost completed a 360-degree rotation).

[0219] Figure 8B A group of devices is depicted displaying an evening update user interface 802 after a first set of review triggering conditions has been met. For example, in some embodiments, the devices display an evening update user interface 807 after determining that a predetermined portion of the day (e.g., 75%) has passed and the activity metric is within a predetermined completion threshold (e.g., 5%). In some embodiments, the group of devices determines that a predetermined portion of the day has passed based on the current time. In some embodiments, the group of devices determines that the activity metric is within the predetermined completion threshold based on received activity data. In some embodiments, the group of devices determines that a set of review criteria has been met based on one or more of the following: current time, day, received activity data, device status, etc.

[0220] like Figure 8BAs depicted, the group of devices displays a nighttime update user interface 807; however, the nighttime update user interface 807 includes different comments (e.g., nighttime prompt 805, nighttime prompt 806, nighttime prompt 808) depending on the age of the user associated with each corresponding device (e.g., as described above, device 800 is associated with users in a first age range, device 802 with users in a second age range, and device 804 with users in a third age range). Figure 8B As depicted, nighttime prompt 804 is longer than nighttime prompt 806. Similarly, nighttime prompt 806 is longer than nighttime prompt 808. In some embodiments, based on the user's age, the total number of characters included in the displayed comment is below a corresponding threshold number of characters (e.g., the maximum prompt length is higher for older or more mature device users). In some embodiments, based on the user's age, each word in the displayed comment is below a corresponding threshold number of characters (e.g., the maximum word length is higher for older or more mature device users).

[0221] like Figure 8B As depicted, nighttime prompts 806 and 808 include graphic content (e.g., emojis), while nighttime prompt 804 does not include graphic content. In some embodiments, the amount of graphic content included in the displayed comment is partly based on the characteristics of the device user (e.g., emojis are shown to younger device users (e.g., ages 6-9) and not to older device users (e.g., ages 9 and above). In some embodiments, the ratio of graphic content (e.g., emojis) to text content (e.g., characters) included in the displayed comment is partly based on the characteristics of the device user (e.g., the ratio is higher for younger users on the device and lower for older users on the device).

[0222] In some implementations, feedback is simplified for younger users (e.g., feedback is limited to activity loop goals for the youngest users, while feedback for older users may include activity loop goals other than other types of goals (e.g., total calories burned, total distance, etc.). In some implementations, feedback gradually incorporates more advanced concepts (e.g., long-term goals) as the user ages. In some implementations, monthly challenges for younger users are limited to activity loop metrics (e.g., minutes of movement, hours of standing, and minutes of exercise). In some implementations, monthly challenges for younger users do not include specific fitness or total distance goals.

[0223] like Figure 8BAs depicted, evening update prompt 805 includes activity-based instructions to achieve an activity goal (e.g., "...brisk walk, 20 minutes walk"), while evening prompts 806 and 808 do not include activity-based instructions. In some implementations, the amount of activity-based instructions shown in the comments, or the amount of activity-based instructions included, is partly based on the characteristics of the device user (e.g., more activity-based instructions are shown to older or more mature device users than to younger device users).

[0224] Figure 8C This describes a group of devices (e.g., devices 800, 802, and 804) that were just before the second set of comment trigger conditions were met. Figure 8C In this configuration, device 800 displays a clock user interface 608B, device 802 displays a clock user interface 602A, and device 804 displays a clock user interface 608A. For example... Figure 8C The depicted set of devices indicates the current time as 10:15 a.m. on the first day of the month (e.g., as shown by time indicator 610 and date indicator 612).

[0225] Figure 8D This describes the group of devices at a second point in time after the second set of comment triggering conditions are met. For example, Figure 8D The description depicts the appearance of the devices (e.g., the content displayed by each device) after a predetermined time period (e.g., 10 minutes) has elapsed since each device detected the condition on the wrist (e.g., the device detected that the user put on the watch at approximately 10:05 AM). Figure 8D As depicted, the group of devices displays or does not display the activity challenge user interface 814 (e.g., a notification with associated comments) based on the age of the user associated with each respective device. For example, device 800 (e.g., the device associated with a user older than 12 years old) displays the activity challenge user interface 812 (e.g., a notification) including prompts 814 (e.g., comments). In contrast, devices 802 and 804 (e.g., each device associated with a younger user) do not display the challenge user interface 814 at a second time (e.g., their displays remain off).

[0226] Figure 8E A set of devices is depicted at a third time following the second time (e.g., 4:30 PM as indicated by time indicator 810). Figure 8EAs depicted, the group of devices displays or continues to omit displaying the Activity Challenge User Interface 814 (e.g., a notification) based on the age of the user associated with each respective device. For example, device 802 (e.g., a device associated with a 9-12 year old user) displays the Activity Challenge User Interface 814 (e.g., a notification) including prompt 816. In contrast, device 804 continues to omit displaying the Activity Challenge User Interface 814. In some embodiments, the display of comments such as the Activity Challenge User Interface 814 is indefinitely omitted based on the age of the user associated with each device. In some embodiments, comments are suppressed (e.g., no comments are posted) during typical school hours for school-aged users (e.g., 6-12 years, 4-12 years, 4-18 years, or 6-18 years). In some embodiments, comments are suppressed (e.g., no comments are posted) during scheduled sleep periods (e.g., after bedtime). In some embodiments, comments are suppressed (e.g., no comments are posted) during one or more time periods associated with a scheduled timetable based on the user's age.

[0227] Figure 8F The description depicts the group of devices after the third set of comment triggering conditions are met. For example, the group of devices displays the morning user interface 820 after determining that the current time has reached a predetermined time (e.g., 7:00 AM) and after determining that one or more activity metric targets have exceeded predetermined amounts (e.g., exceeding 200%, 300%, 400%) during the previous day.

[0228] like Figure 8F As depicted, each of the devices displays a morning user interface 820; however, the morning user interface 820 includes different comments (e.g., morning prompts 822, 824, and 826) depending on the age of the user associated with each respective device (e.g., as described above, device 800 is associated with users in a first age range, device 802 with users in a second age range, and device 804 with users in a third age range).

[0229] like Figure 8F As depicted, morning prompts 822 and 824 include textual references to mathematical concepts (e.g., "double"), while morning prompt 826 does not. In some embodiments, the inclusion of mathematical concepts (e.g., references to average, double, triple, quadruple, etc.) in the displayed comment is based on the characteristics of the device user (e.g., age) (e.g., prompts only include mathematical concepts for older or more mature device users). In some embodiments, the quantity (e.g., number) of the mathematical concept in the displayed comment is based on the characteristics of the device user (e.g., age).

[0230] like Figure 8FAs depicted, morning prompt 822 includes interrogative statements (e.g., questions), while morning prompts 824 and 826 do not. In some embodiments, interrogative statements are included in the displayed comments regarding the user's characteristics (e.g., age) of the device (e.g., the number of interrogative statements included in the comments is proportional to the more mature device user or multiple more mature device users). In some embodiments, the number (e.g., quantity) of interrogative statements in the displayed comments is based on the user's characteristics (e.g., age).

[0231] Figure 8G A set of devices is described that displays a recent activity user interface 828 (e.g., an interface including notifications) after receiving activity data from an external device. In some embodiments, the received activity data indicates that a friend or parent is ahead of the user in a fitness-based competition, or indicates that a friend or parent recently completed a workout. Figure 8G The depicted recently active user interface 828 includes an activity description 830 and a response capability display 832. Figure 8G A set of devices is depicted that receives and responds to user input 832 (e.g., a tap) corresponding to a selection made by an indication display 832. In response to user input 832, the set of devices displays a user interface 836, such as... Figure 8H What is depicted.

[0232] like Figure 8H The depicted user interface 836 includes different sets of responsive display representations (e.g., 838, 840, and 842) depending on the characteristics of the user of the device (e.g., age). Each set of responsive display representations is associated with a set of predetermined statements (e.g., content displayed on each individual display representation), which are transmitted to an external device (e.g., a device associated with the received activity data). In some embodiments, data representing the corresponding predetermined statements is sent via text messages or messages associated with the activity or fitness application. However, the content of the predetermined statements associated with (and displayed by) each set of responsive display representations (e.g., 838, 840, and 842) is based on the age of the user associated with the respective device (e.g., as described above, device 800 is associated with users in a first age range, device 802 with users in a second age range, and device 804 with users in a third age range).

[0233] like Figure 8HThe depicted set of response capability representations 838 includes predetermined statements (e.g., comments), which include disdainful (e.g., sarcastic) comments (e.g., 838C) and aggressive (e.g., inflammatory) language (e.g., 838A, 838B). In contrast, a set of response capability representations 840 and 842 does not include predetermined statements (e.g., comments) with disdainful comments or aggressive language (e.g., 840A, 840B, 840C, 842A, 842B, and 842C, each corresponding to a comment with a positive emotion or otherwise non-inflammatory). In some implementations, the sentiment of the content included in the displayed comments is partly based on the characteristics of the device's users (e.g., comments with negative sentiment are displayed to older device users (e.g., those 12 years and older), but not to younger device users (e.g., those under 12 years old). In some implementations, the response associated on the device with a user having a first characteristic (e.g., under 9 years old) indicates that the associated set of available comments is a subset of the larger set of available comments associated on the device with a second characteristic (e.g., 9-12 years old or over 12 years old).

[0234] Figures 9A to 9B This is a flowchart illustrating a method for dynamically providing activity comments using an electronic device according to some embodiments. Method 900 is performed at a first electronic device (e.g., 100, 300, 500, 600, 800) including a display device. In some embodiments, the first electronic device is a wearable device having an attachment mechanism such as a strap. Some operations in method 900 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0235] In some embodiments, the electronic device (e.g., 800) includes a computer system. The computer system optionally communicates with a display generating component and one or more input devices (e.g., wired communication, wireless communication). The display generating component is configured to provide visual output, such as a display via a CRT monitor, a display via an LED monitor, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. One or more input devices are configured to receive input, such as a touch-sensitive surface that receives user input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separate from the computer system. Therefore, the computer system can transmit data (e.g., image data or video data) via wired or wireless connections to an integrated or external display generating component to visually generate content (e.g., using a display device), and can receive input from one or more input devices via wired or wireless connections.

[0236] As described below, Method 900 provides an intuitive way to dynamically deliver activity feedback. This method provides users with interpretable feedback that quickly draws their attention to relevant information (e.g., guidance, encouraging statements, fitness data, etc.) and / or reduces the cognitive burden on users to identify device status (e.g., current activity metrics measured by the device), thereby creating a more effective human-machine interface. Providing users with improved visual feedback enhances device operability and makes the user-device interface more efficient (e.g., by helping users quickly interpret displayed information, users don't need to spend as much time interacting with the device), which in turn further reduces power consumption and extends device battery life by enabling users to use the device more efficiently.

[0237] The first electronic device receives (902) user activity data (e.g., data indicating the movement of the user of the recorded device) (e.g., Figure 8A (Activity data depicted in 616, 618, and 620).

[0238] Upon receiving user activity data and determining that the user activity data meets a first set of activity comment display criteria (e.g., the data indicates that an activity goal / threshold is met or nearly met (e.g., 618A), fitness completed, activity achievement achieved, change in the lead of an activity competition, activity below a threshold level), the first electronic device displays (904) a first user interface (e.g., 807) via a display device. Displaying (e.g., automatically, without further user input) the first user interface after receiving user activity data and determining that the user activity data meets the first set of activity comment display criteria provides quick access to the first user interface when the interface may (e.g., may) be needed or useful to the user. Performing an operation when a set of conditions has been met without further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and effectively.

[0239] Based on the determination that user characteristics (e.g., user age; user weight; user body mass index; user education level; standardized test results achieved by the user; options selected by the user) satisfy a set of first comment criteria (e.g., user age greater than 9 years old; user education level higher than third grade; standardized test results achieved by the user within a first threshold range) (e.g., user of device 802), the first user interface includes a first activity comment based on (e.g., 806) user activity data (e.g., a congratulatory comment, encouraging or guiding statement, activity reminder, or new activity challenge when the activity loop is closed or nearing closure) (906). In some embodiments, the comment criteria include the user age determined to be within a certain range, e.g., 6-9 years old and 9-13 years old. In some embodiments, the values ​​of user characteristics are received from another device (e.g., from a server storing profile data for the user). Including the first activity comment based on user activity data in the first user interface based on the determination that user characteristics (e.g., user age; user weight; user body mass index; user education level; standardized test results achieved by the user; options selected by the user) satisfy the set of first comment criteria provides the user with quick and easy access to relevant and / or useful information. Performing an operation when a set of conditions has been met and no further user input is required enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0240] Based on the determination that user characteristics (e.g., user age; user weight; user body mass index; user education level; standardized test results achieved by the user; options selected by the user) satisfy a set of second review criteria (e.g., user age 6-9 years old; user education level between first and third grade; standardized test results achieved by the user within a second threshold range (e.g., the second threshold range includes scores lower than the first threshold range)) (e.g., user of device 804), a first user interface includes a second activity review (e.g., 808) based on user activity data, which differs from the first review (e.g., a simplified version of the first activity review) (908). In some embodiments, simplified reviews, such as stand reminders, daily guidance statements, goal completion notifications, and activity challenge notifications, are provided to the first type of user instead of the second type of user. In some embodiments, the set of second review criteria is satisfied when the first set of review criteria is not satisfied. In some embodiments, the values ​​of user characteristics are received from another device (e.g., from a server that stores profile data for the user). Including a second active comment based on user activity data in the first user interface, based on a set of second comment criteria determined by user characteristics (e.g., user age; user weight; user body mass index; user education level; standardized test results performed by the user; options selected by the user), provides users with quick and easy access to relevant and / or useful information. Performing an action when a set of conditions has been met without requiring further user input enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0241] In some implementations, the user characteristic is the age (e.g., in years) of the user associated with the first electronic device (e.g., 800, 802, 804). In some implementations, the first set of first review criteria includes criteria that are met when the age of the user associated with the first electronic device is below a predetermined threshold (e.g., the user of device 802).

[0242] In some implementations, the first active comment (e.g., 806) has a first length (e.g., word count, letter count), and the second active comment (e.g., 808) has a second length greater than the first length. In some implementations, the comment is formatted (e.g., selected, resized) according to a first comment template, which includes a maximum length limit less than the maximum length limit of the second comment template formatted by the second active comment.

[0243] In some implementations, based on (e.g., determined) a value of a user characteristic within a first predetermined range, a first activity comment (e.g., 806, 808) includes graphical elements (e.g., emoticons, icons, images) based on user activity data (e.g., values ​​of user activity data) and not within the first predetermined range based on the value of the user characteristic. A first activity comment (e.g., 805) does not include graphical elements (e.g., emoticons, icons, images) based on user activity data (e.g., values ​​of user activity data). Including graphical elements based on user activity data within the first predetermined range based on (e.g., determined) a value of a user characteristic and excluding graphical elements based on user activity data not within the first predetermined range based on the value of the user characteristic allows the user to improve visual feedback by providing graphical elements and / or where graphical elements are more likely to be helpful. Providing improved visual feedback to the user enhances device operability and makes the user device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling the user to use the device more quickly and effectively.

[0244] In some implementations, after displaying the first activity comment, the first electronic device receives (910) second user activity data (e.g., Figure 8C The activity data described in 616, 618, and 620). In some embodiments, after receiving the second user activity data (912), a second set of activity display criteria is determined to be met (e.g., the data indicates that the activity target / threshold is met or nearly met; the first set of activity comment display criteria). Figure 8C The second set of activity display criteria includes criteria that are met when the current time is not within a predetermined time period (e.g., between 8 a.m. and 3 p.m.; a time period corresponding to an expected event (e.g., a school day; a sleep schedule)). The first electronic device displays the second user activity data (914) and then a third activity comment (e.g., 814, 816). In some embodiments, after receiving the second user activity data (912), the first electronic device abandons displaying (916) based on the second user activity data (e.g., the data indicates that the activity target / threshold is met or nearly met; the first set of activity comment display criteria) if it is determined that the second set of activity display criteria (e.g., the data indicates that the activity target / threshold is met or nearly met; the first set of activity comment display criteria) is not met. Figure 8D The third activity comment (802 and 804 in the example). In some implementations, the third activity comment (e.g., Figure 8E The 816 and 804 criteria were delayed until the second set of activity display criteria were met.

[0245] In some embodiments, the first electronic device receives (918) third user activity data (e.g., user activity data of a user other than the user associated with the user activity data) from an external device (e.g., 830). In some embodiments, the third activity data indicates that an activity goal / threshold is met or nearly met, a fitness activity is completed, an activity achievement is obtained, a change in the lead of an activity competition, or an activity level below a threshold. In some embodiments, in response to receiving the third user activity data, the first electronic device displays (922) a first response user interface (e.g., an interface for sending a response to an external device) (e.g., 828). Displaying the first response user interface in response to receiving the third user activity data provides the user with quick and easy access to information corresponding to the third activity data. Reducing the amount of input required to perform an operation enhances the operability of the device and makes the user device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), thereby further reducing power consumption and extending the device's battery life by enabling the user to use the device more quickly and efficiently. In some embodiments, based on determining that the values ​​of user characteristics satisfy a first set of first response criteria, the first response user interface includes a first set of one or more response comment capability representations (e.g., 840), the first set of one or more response comment capability representations including a first response comment capability representation that, when selected, causes the first response comment to be transmitted to an external device (922). In some embodiments, based on determining that the values ​​of user characteristics satisfy a second set of second response criteria, the first response user interface includes a second set of one or more response comment capability representations (e.g., 842), the second set of one or more response comment capability representations including a second response comment capability representation that, when selected, causes the second response comment to be transmitted to an external device, wherein the first set of one or more response comment capability representations differs from the second set of one or more response comment capability representations (e.g., the first set does not include a second response comment capability representation; the second set does not include a first response comment capability representation) (924).

[0246] In some implementations, upon receiving user activity data (e.g., Figure 8APrior to the activity data depicted in 616, 618, and 620, the first electronic device receives values ​​of user characteristics via user input (e.g., user characteristics are input by the user during setup of the first electronic device before the first electronic device collects activity data). Enabling the user to input user characteristics provides the user with additional control over the activity comments displayed by the device. This additional control over the activity comments provides the user with enhanced visual feedback containing relevant and / or useful information. Providing the user with improved visual feedback enhances the operability of the device and makes the user device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and effectively.

[0247] In some implementations, the values ​​of user characteristics are selected from the following groups: age (e.g., one or more age thresholds, one or more age range thresholds), the user's highest level of education (e.g., one or more grade level thresholds, one or more grade level range thresholds), standardized test results achieved by the user (e.g., one or more score thresholds, one or more score range thresholds), options selected by the user (e.g., a first electronic device receiving user input corresponding to selecting an option from a plurality of options related to the example activity commentary), and any combination thereof. In some implementations, standardized test results may include the National Assessment of Educational Progress (NAEP), the Metropolitan Achievement Test (MAT8), one or more state-managed standardized tests, such as the California Standardized Tests and Reports (STAR), the Texas Assessment of Knowledge and Skills (TAK), and the New York State Testing Program (NYSTP). In some implementations, the user selects the option for the activity commentary that the user best understands or comprehends.

[0248] It should be noted that the process described in the above-mentioned reference method 900 (e.g., Figures 9A to 9B The details of the above-described methods also apply in a similar manner. For example, method 900 optionally includes one or more characteristics of the various methods described above with reference to method 700. For example, the mode in which the device operates—a first device mode (e.g., youth mode) and a second device mode (adult mode)—can be used to at least partially determine the type of comment to be displayed on the device. For the sake of brevity, these details will not be repeated below.

[0249] For purposes of explanation, the foregoing description has been given by reference to specific embodiments. However, the illustrative discussion above is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible based on the teachings above. These embodiments were chosen and described in order to best explain the principles of these techniques and their practical applications. Others skilled in the art will thus be able to best utilize these techniques and the various embodiments with various modifications suitable for the particular intended use.

[0250] While this disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will become apparent to those skilled in the art. It should be understood that such changes and modifications are considered to be included within the scope of this disclosure and examples as defined by the claims.

[0251] As described above, one aspect of the present invention involves collecting and using data from various sources to improve the delivery of inspirational or other content that may be of interest to users. This disclosure contemplates that, in some instances, such collected data may include personal information that uniquely identifies or can be used to contact or locate specific individuals. Such personal information may include demographic data, location-based data, telephone numbers, email addresses, Twitter IDs, home addresses, data or records relating to a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

[0252] This disclosure recognizes that the use of such personal information data in the techniques of this invention can benefit users. For example, personal information data (e.g., health and fitness data) can be used to provide insights into a user's overall health status or as positive feedback to individuals using the technology to pursue health goals (e.g., fitness-related advice or guidance). Therefore, the use of such personal information data enables users to achieve better health outcomes by providing more helpful feedback on fitness-related activities. Furthermore, this disclosure also anticipates other uses of personal information data that benefit users.

[0253] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use change. Personal information from users should be collected for the entity's lawful and reasonable purposes and not shared or sold outside of these lawful uses. Furthermore, such collection / sharing should be conducted only after obtaining informed consent from users. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including specific considerations regarding jurisdiction. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while in other countries, health data may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

[0254] Regardless of the foregoing, this disclosure also contemplates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, in providing insights into a user's overall health status, the technology of this invention can be configured to allow users to opt-in or opt-out during or at any time after registering for the service. As another example, users can choose not to provide health and fitness-related data to provide positive feedback (e.g., fitness-related advice or guidance) to individuals using the technology to pursue health goals. Furthermore, users can choose to limit the length of time health and fitness data is retained, or completely prohibit the development of basic health or fitness conditions. In addition to providing "opt-in" and "opt-out" options, this disclosure envisions providing notifications related to access to or use of personal information. For example, users can be notified when downloading an application that their personal information data will be accessed, and then reminded again just before the application accesses the personal information data.

[0255] Furthermore, the purpose of this disclosure is to manage and process personal information data to minimize the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by limiting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods.

[0256] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not be rendered inoperable due to the absence of all or part of such personal information data. For example, health and fitness data sharing preferences can be inferred and content delivered to a user based on non-personal information data or a small amount of personal information, such as content requested by a device associated with the user, other non-personal information, or publicly available information.

Claims

1. A first electronic device, comprising: Display devices; One or more processors; as well as A memory storing one or more programs configured to be executed by one or more processors, the one or more programs including instructions for the following operations: Receive user activity data; as well as After receiving the user activity data and determining that the user activity data meets the first set of activity comment display criteria, a first user interface is displayed via the display device: Based on the determination that the values ​​of user characteristics satisfy a first set of first comment criteria, the first user interface includes a first activity comment based on the user activity data, wherein the first activity comment includes a first number of characters, and wherein the first activity comment does not include activity-based instructions; as well as Based on the determination that the value of the user characteristic satisfies a second set of second comment criteria, the first user interface includes a second active comment based on the user activity data, the second active comment being different from the first comment, wherein the second active comment includes a second number of characters greater than the first number of characters, and wherein the second active comment includes the activity-based instruction.

2. The first electronic device according to claim 1, wherein the user characteristic is the age of the user associated with the electronic device.

3. The first electronic device according to claim 1, wherein the one or more programs further include instructions for the following operations: After displaying the first activity comment, receive the second user activity data; and After receiving the second user activity data: Based on the determination that the second set of activity display criteria is met, a third activity comment is displayed based on the second user activity data. The second set of activity display criteria includes criteria that are met when the current time is not within a predetermined time period. Based on the determination that the display criteria for the second group of activities were not met, the display of the third activity comments based on the second user activity data was abandoned.

4. The first electronic device according to claim 1, wherein: Based on the values ​​of the user characteristics within a first predetermined range, the first activity comment includes graphical elements based on the user activity data; and Since the value of the user characteristic is not within the first predetermined range, the first activity comment does not include the graphical elements based on the user activity data.

5. The first electronic device of claim 1, wherein the one or more programs further include instructions for the following operations: Receive third-party user activity data from external devices; and In response to receiving the third user activity data, a first response user interface is displayed: Based on the determination that the value of the user characteristic satisfies a set of first response criteria, the first response user interface includes a first set of one or more response comment capability representations, the first set of one or more response comment capability representations including a first response comment capability representation, and when the first response comment capability representation is selected, causing a first response comment to be sent to the external device; and Based on the determination that the value of the user characteristic satisfies a second set of response criteria, the first response user interface includes a second set of one or more response comment capability representations, the second set of one or more response comment capability representations including a second response comment capability representation, when the second response comment capability representation is selected, causing a second response comment to be sent to the external device, wherein the first set of one or more response comment capability representations is different from the second set of one or more response comment capability representations.

6. The first electronic device of claim 1, wherein the one or more programs further include instructions for the following operations: Before receiving the user activity data, the values ​​of the user characteristics are received via user input.

7. The first electronic device according to claim 1, wherein the value of the user characteristic is selected from the group consisting of: age, the user's highest level of education, the standard test results obtained by the user, the option selected by the user, and any combination thereof.

8. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device including a display device, the one or more programs including instructions for: Receive user activity data; and After receiving the user activity data and determining that the user activity data meets the first set of activity comment display criteria, a first user interface is displayed via the display device: Based on the determination that user characteristics satisfy a first set of first comment criteria, the first user interface includes a first activity comment based on the user activity data, wherein the first activity comment includes a first number of characters, and wherein the first activity comment does not include activity-based instructions; and Based on the determination that the value of the user characteristic satisfies a second set of second comment criteria, the first user interface includes a second active comment based on the user activity data, the second active comment being different from the first comment, wherein the second active comment includes a second number of characters greater than the first number of characters, and wherein the second active comment includes the activity-based instruction.

9. The non-transitory computer-readable storage medium of claim 8, wherein the user characteristic is the age of the user associated with the electronic device.

10. The non-transitory computer-readable storage medium of claim 8, wherein the one or more programs further include instructions for: After displaying the first activity comment, receive the second user activity data; and After receiving the second user activity data: Based on the determination that the second set of activity display criteria is met, a third activity comment is displayed based on the second user activity data. The second set of activity display criteria includes criteria that are met when the current time is not within a predetermined time period. Based on the determination that the display criteria for the second group of activities were not met, the display of the third activity comments based on the second user activity data was abandoned.

11. The non-transitory computer-readable storage medium according to claim 8, wherein: Based on the values ​​of the user characteristics within a first predetermined range, the first activity comment includes graphical elements based on the user activity data; and Since the value of the user characteristic is not within the first predetermined range, the first activity comment does not include the graphical elements based on the user activity data.

12. The non-transitory computer-readable storage medium of claim 8, wherein the one or more programs further include instructions for: Receive third-party user activity data from external devices; and In response to receiving the third user activity data, a first response user interface is displayed: Based on the determination that the value of the user characteristic satisfies a set of first response criteria, the first response user interface includes a first set of one or more response comment capability representations, the first set of one or more response comment capability representations including a first response comment capability representation, and when the first response comment capability representation is selected, causing a first response comment to be sent to the external device; and Based on the determination that the value of the user characteristic satisfies a second set of response criteria, the first response user interface includes a second set of one or more response comment capability representations, the second set of one or more response comment capability representations including a second response comment capability representation, when the second response comment capability representation is selected, causing a second response comment to be sent to the external device, wherein the first set of one or more response comment capability representations is different from the second set of one or more response comment capability representations.

13. The non-transitory computer-readable storage medium of claim 8, wherein the one or more programs further include instructions for: Before receiving the user activity data, the values ​​of the user characteristics are received via user input.

14. The non-transitory computer-readable storage medium of claim 8, wherein the value of the user characteristic is selected from the group consisting of: age, the user's highest level of education, the standard test results obtained by the user, the options selected by the user, and any combination thereof.

15. A method comprising: At the first electronic device, which includes the display device: Receive user activity data; as well as After receiving the user activity data and determining that the user activity data meets the first set of activity comment display criteria, a first user interface is displayed via the display device: Based on the determination that the values ​​of user characteristics satisfy a first set of first comment criteria, the first user interface includes a first activity comment based on the user activity data, wherein the first activity comment includes a first number of characters, and wherein the first activity comment does not include activity-based instructions; as well as Based on the determination that the value of the user characteristic satisfies a second set of second comment criteria, the first user interface includes a second active comment based on the user activity data, the second active comment being different from the first comment, wherein the second active comment includes a second number of characters greater than the first number of characters, and wherein the second active comment includes the activity-based instruction.

16. The method of claim 15, wherein the user characteristic is the age of the user associated with the electronic device.

17. The method of claim 15, further comprising: After displaying the first activity comment, receive the second user activity data; as well as After receiving the second user activity data: If the second set of activity display criteria is determined to be met, a third activity comment based on the second user activity data is displayed. The second set of activity display criteria includes criteria that are met when the current time is not within a predetermined time period. and Based on the determination that the display criteria for the second group of activities were not met, the display of the third activity comments based on the second user activity data was abandoned.

18. The method of claim 15, wherein: Based on the values ​​of the user characteristics within a first predetermined range, the first activity comment includes graphical elements based on the user activity data; and Since the value of the user characteristic is not within the first predetermined range, the first activity comment does not include the graphical elements based on the user activity data.

19. The method of claim 15, further comprising: Receive third-party user activity data from external devices; as well as In response to receiving the third user activity data, a first response user interface is displayed: Based on the determination that the value of the user characteristic satisfies a set of first response criteria, the first response user interface includes a first set of one or more response comment capability representations, the first set of one or more response comment capability representations including a first response comment capability representation, and when the first response comment capability representation is selected, causing a first response comment to be sent to the external device; as well as Based on the determination that the value of the user characteristic satisfies a second set of response criteria, the first response user interface includes a second set of one or more response comment capability representations, the second set of one or more response comment capability representations including a second response comment capability representation, when the second response comment capability representation is selected, causing a second response comment to be sent to the external device, wherein the first set of one or more response comment capability representations is different from the second set of one or more response comment capability representations.

20. The method of claim 15, further comprising: Before receiving the user activity data, the values ​​of the user characteristics are received via user input.

21. The method of claim 15, wherein the value of the user characteristic is selected from the group consisting of: age, the user's highest level of education, the standard test results obtained by the user, the options selected by the user, and any combination thereof.

Images