Displaying a user interface associated with physical activity

Abstract

To provide a quicker and more efficient method for displaying a user interface associated with a physical activity, and an electronic device for executing the method.SOLUTION: An electronic device receives first user activity data and second user activity data, and displays a user interface including an expression of each user activity data. Each user activity data includes each user activity data of a first time subset and a second time subset. The user interface includes expressions of the first and second user activity data of first and second subset times, a cumulative expression of the first user activity data based on the first user activity data of the first and second subset times, and a cumulative expression of the second user activity data based on the second user activity data of the first and second subset times.SELECTED DRAWING: Figure 7A

Description

[Technical field]

[0001] (Priority) This application claims priority to U.S. Provisional Patent Application No. 62 / 668,159, filed May 7, 2018, entitled “Displaying a User Interface Associated with Physical Activity,” and U.S. Provisional Patent Application No. 62 / 679,906, filed June 3, 2018, entitled “Displaying a User Interface Associated with Physical Activity,” the contents of each of which are incorporated herein by reference in their entireties.

[0002] FIELD OF THE DISCLOSURE The present disclosure relates generally to user interfaces, and more particularly, to techniques for displaying user interfaces associated with physical activity. [Background technology]

[0003] Many modern electronic devices provide the ability to track a user's physical activity. Such electronic devices often display information associated with the physical activity to the user. Technology exists that provides the ability to compare a user's physical activity with the physical activity of other users. Some technology provides the ability to start and stop tracking of physical activity. Some technology provides the ability to set pace alerts for physical activity. However, such technology can be cumbersome and inefficient. Summary of the Invention

[0004] Techniques for displaying user interfaces associated with physical activity using electronic devices are generally cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that may involve multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device power. The latter problem is particularly acute in battery-operated devices.

[0005] Thus, the present technology provides electronic devices with faster and more efficient methods and interfaces for displaying user interfaces associated with physical activity, optionally complementing or replacing other methods for displaying user interfaces associated with physical activity, reducing the cognitive burden on the user and providing a more efficient human-machine interface, and in the case of battery-powered computing devices, conserving power and increasing the time between battery charges.

[0006] One or more computer systems may be configured to perform particular operations or actions by installing software, firmware, hardware, or a combination thereof into a running system and causing the system to perform the operations. One or more computer programs may be configured to perform particular operations or actions by comprising instructions that, when executed by a data processing device, cause the device to perform the operations.

[0007] One general aspect includes a method performed on an electronic device having a display, the method including receiving first user activity data during a time period including at least a first subset of first user activity data and a second subset of first user activity data, the method further including receiving second user activity data during the time period including at least a first subset of second user activity data and a second subset of second user activity data. The method further includes displaying, on the display, a user interface including: (1) a representation of the first user activity data for the first subset of time, (2) a representation of the first user activity data for the second subset of time, (3) a cumulative representation of the first user activity data for the time period based on at least the first user activity data for the first subset of time and the first user activity data for the second subset of time, (4) a representation of the second user activity data for the first subset of time, (5) a representation of the second user activity data for the second subset of time, and (6) a cumulative representation of the second user activity data for the time period based on at least the second user activity data for the first subset of time and the second user activity data for the second subset of time. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform operations of the method.

[0008] One general aspect includes a method performed on an electronic device having a display, the method including receiving first user activity data corresponding to a first time period and a second time period for a first user, the method further including receiving second user activity data for a second user, the second user activity data corresponding to a first time period, the first time period including a first elapsed sub-period and a first unexpired sub-period for an activity competition between the first user and the second user, the method further including receiving third user activity data for a third user, the third user activity data corresponding to a second time period, the second time period including a second elapsed sub-period and a second unexpired sub-period for an activity competition between the first user and the third user. The method further includes displaying, on the display, a user interface including: (1) a representation of first user activity data and second user activity data during a first elapsed subperiod related to the activity competition between the first user and the second user, (2) an indication of a time amount of a first unexpired subperiod related to the activity competition between the first user and the second user, (3) a representation of first activity data and third activity data during a second elapsed subperiod related to the activity competition between the first user and the third user, and (4) an indication of a time amount of a second unexpired subperiod related to the activity competition between the first user and the third user. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the operations of the method.

[0009] One general aspect includes a method implemented on an electronic device including a display and one or more sensors. The method includes detecting activity data by the one or more sensors. The method further includes, in response to detecting the activity data, displaying an activity boundary alert in accordance with a determination that the activity data meets the activity boundary alert criteria. The method further includes, in response to detecting the activity data, withholding display of the activity boundary alert in accordance with a determination that the activity data does not meet the activity boundary alert criteria. Other examples of this aspect include corresponding computer systems, apparatus, and computer programs stored on one or more computer storage devices, each configured to perform the operations of the method.

[0010] One general aspect includes a method executed on an electronic device. The method includes displaying a physical activity rate user interface including a first setting affordance and a second setting affordance. The method further includes receiving a first user input while displaying the physical activity rate user interface. The method further includes, in response to receiving the first user input, configuring the physical activity rate calculation to use a first portion of the dataset according to the first user input corresponding to a selection of the first setting affordance. The method further includes, in response to receiving the first user input, configuring the physical activity rate calculation to use a second portion of the dataset different from the first portion according to the first user input corresponding to a selection of the second setting affordance. Other examples of this aspect include corresponding computer systems, apparatuses, and computer programs recorded on one or more computer storage devices, each configured to perform the operations of the method.

[0011] One general aspect includes 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 having a display, the one or more programs including instructions for any of the methods described above.

[0012] One general aspect includes a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, the one or more programs including instructions for any of the methods described above.

[0013] One general aspect includes an electronic device with a display. The electronic device also includes one or more processors. The electronic device also includes a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods described above.

[0014] One general aspect includes an electronic device with a display. The electronic device also includes means for receiving first user activity data including at least a first subset of time first user activity data and a second subset of time first user activity data. The electronic device also includes means for receiving second user activity data including at least a first subset of time second user activity data and a second subset of time second user activity data. The electronic device also includes means for displaying on the display a user interface including: (1) a representation of the first user activity data for the first subset of time; (2) a representation of the first user activity data for the second subset of time; (3) a cumulative representation of the first user activity data for the period based on at least the first user activity data for the first subset of time and the first user activity data for the second subset of time; (4) a representation of the second user activity data for the first subset of time; (5) a representation of the second user activity data for the second subset of time; and (6) a cumulative representation of the second user activity data for the period based on at least the second user activity data for the first subset of time and the second user activity data for the second subset of time.

[0015] One general aspect includes an electronic device with a display. The electronic device also includes means for receiving first user activity data corresponding to a first time period and a second time period for a first user. The electronic device also includes receiving second user activity data for a second user, the second user activity data corresponding to a first time period, the first time period including a first elapsed sub-period and a first unexpired sub-period for an activity competition between the first user and the second user. The electronic device also includes means for receiving third user activity data for a third user, the third user activity data corresponding to a second time period, the second time period including a second elapsed sub-period and a second unexpired sub-period for an activity competition between the first user and the third user. The electronic device also includes means for displaying on the display a user interface including: (1) a representation of first user activity data and second user activity data during a first elapsed subperiod related to the activity competition between the first user and the second user; (2) a display of a time amount of a first unelapsed subperiod related to the activity competition between the first user and the second user; (3) a representation of first activity data and third activity data during a second elapsed subperiod related to the activity competition between the first user and the third user; and (4) a display of a time amount of a second unelapsed subperiod related to the activity competition between the first user and the third user.

[0016] One general aspect includes an electronic device with a display. The electronic device also includes means for detecting activity data by one or more sensors. The electronic device also includes means for displaying an activity boundary alert in response to detecting the activity data and in accordance with a determination that the activity data meets the activity boundary alert criteria. The electronic device also includes means for withholding display of the activity boundary alert in response to detecting the activity data and in accordance with a determination that the activity data does not meet the activity boundary alert criteria.

[0017] One general aspect includes an electronic device with a display. The electronic device also includes means for displaying a physical activity rate user interface including a first setting affordance and a second setting affordance. The electronic device also includes means for receiving a first user input while displaying the physical activity rate user interface. The electronic device also includes means for configuring a physical activity rate calculation to use a first portion of a dataset according to the first user input corresponding to a selection of the first setting affordance, in response to receiving the first user input. The electronic device also includes means for configuring a physical activity rate calculation to use a second portion of a dataset different from the first portion, in response to receiving the first user input, according to the first user input corresponding to a selection of the second setting affordance.

[0018] Executable instructions for performing these functions are optionally included on a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are optionally included on a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0019] Thus, devices are provided with faster and more efficient methods and interfaces for displaying user interfaces associated with physical activity, which may complement or replace other methods for displaying user interfaces associated with physical activity. [Brief description of the drawings]

[0020] For a better understanding of the various embodiments described, reference should be made to the following Detailed Description in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:

[0021] [Figure 1A] FIG. 1 is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.

[0022] [Figure 1B] FIG. 2 is a block diagram illustrating example components for event processing according to some embodiments.

[0023] [Diagram 2] 1 illustrates a portable multifunction device with a touch screen according to some embodiments.

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

[0025] [Figure 4A] 1 illustrates an example user interface for a menu of applications on a portable multifunction device according to some embodiments.

[0026] [Figure 4B] 1 illustrates an example user interface for a multifunction device with a touch-sensitive surface that is separate from the display.

[0027] [Figure 5A] 1 illustrates a personal electronic device according to some embodiments.

[0028] [Figure 5B] FIG. 1 is a block diagram illustrating a personal electronic device according to some embodiments.

[0029] [Figure 5C] 1 illustrates example components of a personal electronic device having a touch-sensitive display and an intensity sensor in accordance with some embodiments. [Figure 5D]1 illustrates example components of a personal electronic device having a touch-sensitive display and an intensity sensor in accordance with some embodiments.

[0030] [Figure 5E] 1 illustrates example components and a user interface of a personal electronic device according to some embodiments. [Figure 5F] 1 illustrates example components and a user interface of a personal electronic device according to some embodiments. [Figure 5G] 1 illustrates example components and a user interface of a personal electronic device according to some embodiments. [Figure 5H] 1 illustrates example components and a user interface of a personal electronic device according to some embodiments.

[0031] [Figure 6A] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6B] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6C] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6D] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6E] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6F] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6G] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6H] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6I]1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6J] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6K] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6L] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6M] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6N] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6O] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6P] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6Q] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6R] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6S] 1 illustrates an example user interface related to an activity competition, according to some embodiments. [Figure 6T] 1 illustrates an example user interface related to an activity competition, according to some embodiments.

[0032] [Figure 7A] FIG. 1 is a flow diagram illustrating a method for displaying a representation of an activity competition using an electronic device, according to some embodiments. [Figure 7B] FIG. 1 is a flow diagram illustrating a method for displaying a representation of an activity competition using an electronic device, according to some embodiments.

[0033] [Figure 8A] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8B] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8C] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8D] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8E] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8F] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8G] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8H] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8I] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8J] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8K] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8L] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8M] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8N]1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8O] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8P] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8Q] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8R] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8S] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8T] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8U] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8V] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8W] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8X] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments. [Figure 8Y] 1 illustrates an example user interface related to a friends list for activity sharing, according to some embodiments.

[0034] [Figure 9A] FIG. 1 is a flow diagram illustrating a method for displaying a friends list representation using an electronic device according to some embodiments. [Figure 9B]FIG. 1 is a flow diagram illustrating a method for displaying a friends list representation using an electronic device according to some embodiments.

[0035] [Figure 10A] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10B] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10C] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10D] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10E] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10F] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10G] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10H] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10I]1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10J] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10K] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10L] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10M] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10N] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10O] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10P] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. [Figure 10Q] 1 illustrates an example user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments.

[0036] [Figure 11]FIG. 1 is a flow diagram illustrating a method for displaying an alert in response to automatically determining physical activity boundaries using an electronic device, according to some embodiments.

[0037] [Figure 12A] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12B] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12C] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12D] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12E] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12F] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12G] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12H] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12I] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12J]1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12K] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12L] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12M] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12N] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12O] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12P] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12Q] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12R] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12S] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12T]1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12U] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12V] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12W] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Fig. 12X] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12Y] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12Z] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12AA] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12AB] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12AC] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12AD]1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12AE] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Fig. 12AF] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12A-G] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12AH] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12AI] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12AJ] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments. [Figure 12AK] 1 illustrates an example user interface associated with configuring a pace alert for a training application, according to some embodiments.

[0038] [Figure 13] FIG. 11 is a flow diagram illustrating a method for displaying a user interface for configuring a dataset used to calculate pace using an electronic device, according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0039] The following description sets forth example methods, parameters, etc., however, it should be recognized that such description is not intended to limit the scope of the present disclosure, but rather is provided as a description of example embodiments.

[0040] There is a need for electronic devices that provide efficient methods and interfaces for displaying user interfaces associated with physical activity. Such techniques can reduce the cognitive burden on a user accessing user interfaces associated with physical activity, thereby increasing productivity. Furthermore, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0041] 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description of an exemplary device for performing techniques for managing event notifications. FIGS. 6A-6T illustrate an exemplary user interface associated with an activity competition, according to some embodiments. FIGS. 7A-7B are flow diagrams illustrating a method for displaying a representation of an activity competition using an electronic device, according to some embodiments. The user interfaces of FIGS. 6A-6T are used to explain the processes described below, including the processes of FIGS. 7A-7B. FIGS. 8A-8Y illustrate an exemplary user interface associated with a friend list for activity sharing, according to some embodiments. FIGS. 9A-9B are flow diagrams illustrating a method for displaying a representation of a friend list using an electronic device, according to some embodiments. The user interfaces of FIGS. 8A-8Y are used to explain the processes described below, including the processes of FIGS. 9A-9B. FIGS. 10A-10Q illustrate an exemplary user interface associated with an alert presented to a user in response to automatically determining workout boundaries, according to some embodiments. FIG. 11 is a flow diagram illustrating a method for displaying an alert in response to automatically determining physical activity boundaries using an electronic device, according to some embodiments. The user interfaces of FIGS. 10A-10Q are used to explain the processes described below, including the process of FIG. 11. FIGS. 12A-12AK show example user interfaces associated with configuring a pace alert for a training application, according to some embodiments. FIG. 13 is a flow diagram illustrating a method for displaying a user interface for configuring a data set used to calculate pace using an electronic device, according to some embodiments. The user interfaces of FIGS. 12A-12AK are used to explain the processes described below, including the process of FIG. 13.

[0042] In the following description, terms such as "first" and "second" are used to describe various elements, but these elements should not be limited by the terms. These terms are only used to distinguish one element from another element. For example, a first touch can be called a second touch, and similarly, a second touch can be called a first touch without departing from the scope of various described embodiments. A first touch and a second touch are both touches, but are not the same touch.

[0043] The terms used in the description of the various embodiments described herein are for the purpose of describing particular embodiments only and are not intended to be limiting. When used in the description of the various embodiments described and in 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 includes any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0044] Optionally, the term "if" is interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (a stated condition or event) is detected" are optionally interpreted to mean "upon determining," "in response to determining," "upon detecting (the stated condition or event)," or "in response to detecting (the stated condition or event)," depending on the context.

[0045] Examples of electronic devices, user interfaces for such devices, and associated methods for using such devices are described. In some examples, the device is a portable communication device, such as a mobile telephone, that also includes other functions, such as PDA and / or music player functions. Exemplary examples of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads), are also optionally used. It should also be understood that in some examples, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (e.g., touchscreen displays and / or touchpads).

[0046] In the following description, an electronic device is described that includes a display and a touch-sensitive surface, but 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.

[0047] The device typically supports a variety of applications, such as one or more of drawing applications, presentation applications, word processing applications, website creation applications, disc authoring applications, spreadsheet applications, gaming applications, telephony applications, video conferencing applications, email applications, instant messaging applications, training support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0048] The various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within each application. In this way, the common physical architecture (such as the touch-sensitive surface) of the device optionally supports a variety of applications with user interfaces that are intuitive and transparent to the user.

[0049] Attention is now directed to examples of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. Touch-sensitive display 112 may be conveniently referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." Device 100 includes memory 102 (optionally including one or more computer-readable storage media), 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. Device 100 optionally includes one or more light sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating a tactile output on device 100 (e.g., generating a tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0050] As used herein and in the 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 surrogate (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values, including at least four different values, and more typically including hundreds of different values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using a variety of techniques and a variety of sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure the 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 estimate of the force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact, are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure of the force or pressure of the contact is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measure). In some implementations, the surrogate measure of the force or pressure of the contact is 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 contact as an attribute of user input allows a user access to additional device functionality that may not otherwise be accessible by the user on devices of reduced size that have a limited area for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0051] As used herein and in the claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that is to be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of the device is in contact with a touch-sensitive surface of a user (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement is interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a "down-click" or "up-click" of a physical actuator button. In some cases, a user feels a tactile sensation such as a "down-click" or "up-click" even when no movement of a physical actuator button associated with the touch-sensitive surface is physically pressed (e.g., displaced) by the user's action. As another example, movement of the touch-sensitive surface is optionally interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Such user interpretation of touch depends on the user's personal sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an "up click," a "down click," a "roughness"), unless otherwise noted, the generated tactile output corresponds to a physical displacement of the device or a component of the device that will produce the described sensory perception for a typical (or average) user.

[0052] It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of components. The various components shown in FIG. 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.

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

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

[0055] The radio frequency (RF) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. The RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuitry 108 optionally includes well-known circuitry for performing their functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and the like. The RF circuitry 108 optionally communicates by wireless communication with networks, such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. The RF circuitry 108 optionally includes well-known circuitry for detecting a field of near field communication (NFC), such as by near field communication radio. The wireless communication optionally uses any of a number of communication standards, protocols, and technologies, including Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (WDC), and other communication standards, protocols, and technologies.Wireless technology may include, but is not limited to, wireless LAN, wireless LANs, wireless LAN networks, wireless LAN devices, wireless LAN systems, wireless LAN networks, wireless LAN systems ... Examples of suitable communication protocols include, but are not limited to, Simple Intermediate System (SIMPLE), Instant Messaging and Presence Service (IMPS), and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

[0056] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and the device 100. The audio circuit 110 receives audio data from the peripherals interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into sound waves audible to humans. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into voice data and transmits the voice data to the peripherals interface 118 for processing. The voice data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripherals interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212 in FIG. 2). The headset jack provides an interface between audio circuitry 110 and a removable audio input / output peripheral, such as an output-only headphone or a headset that has both an output (e.g., one- or binaural headphones) and an input (e.g., a microphone).

[0057] The I / O subsystem 106 couples input / output peripherals of the device 100, such as the touch screen 112 and other input control devices 116, to a peripheral interface 118. The I / O subsystem 106 optionally includes one or more input controllers 160 for a display controller 156, a light sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and other input or control devices. The one or more input controllers 160 receive / send electrical signals to the other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller(s) 160 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2) optionally include up / down buttons for adjusting the volume of the speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in FIG. 2).

[0058] A quick press of a push button optionally unlocks the touchscreen 112 or optionally initiates a process of using gestures on the touchscreen to unlock the device, as described in U.S. Patent Application Serial No. 11 / 322,549, U.S. Patent No. 7,657,849, filed December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," which is incorporated herein by reference in its entirety. A longer press of a push button (e.g., 206) optionally powers the device 100 on and off. The functions of one or more of the buttons are optionally user customizable. The touchscreen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0059] Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or transmits electrical signals to touchscreen 112. Touchscreen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively referred to as "graphics"). In some embodiments, optionally, some or all of the visual output corresponds to user interface objects.

[0060] Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detects contacts (and any movement or cessation of contact) on touch screen 112 and translates the detected contacts into interactions with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touch screen 112. In an exemplary embodiment, the point of contact between touch screen 112 and the user corresponds to the user's finger.

[0061] Touch screen 112 optionally uses LCD (Liquid Crystal Display), LPD (Light Emitting Polymer Display) or LED (Light Emitting Diode) technology, although in other embodiments other display technologies are used. Touch screen 112 and display controller 156 optionally detect contact and any movement or interruption thereof using any of a number of now known or later developed touch sensing technologies, including, but not limited to, capacitive, resistive, infrared, and surface ultrasonic technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as found in the iPhone® and iPod Touch® by Apple Inc. (Cupertino, California).

[0062] The touch-sensitive display in some implementations of touchscreen 112 is optionally similar to the multi-touch-sensing touchpads described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman), and / or U.S. Patent Application Publication No. 2002 / 0015024 (A1), each of which is incorporated by reference in its entirety herein: However, whereas touchscreen 112 displays visual output from device 100, a touch-sensitive touchpad does not provide visual output.

[0063] Some embodiments of touch-sensitive displays for touch screen 112 are described in the following applications: (1) U.S. Patent Application No. 11 / 381,313, filed May 2, 2006, entitled "Multipoint Touch Surface Controller"; (2) U.S. Patent Application No. 10 / 840,862, filed May 6, 2004, entitled "Multipoint Touchscreen"; (3) U.S. Patent Application No. 10 / 903,964, filed July 30, 2004, entitled "Gestures For Touch Sensitive Input Devices"; (4) U.S. Patent Application No. 11 / 048,264, filed January 31, 2005, entitled "Gestures For Touch Sensitive Input Devices"; (5) U.S. Patent Application No. 11 / 038,590, filed January 18, 2005, entitled "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices"; (6) U.S. Patent Application No. 11 / 228,758, filed September 16, 2005, entitled "Virtual Input Device Placement On A Touch Screen User Interface"; No. 11 / 228,700, filed Sep. 16, 2005, entitled "Operation Of A Computer With A Touch Screen Interface," (7) No. 11 / 228,700, filed Sep. 16, 2005, entitled "Operation Of A Computer With A Touch Screen Interface," (8) No. 11 / 228,737, filed Sep. 16, 2005, entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard," and (9) No. 11 / 367,749, filed Mar. 3, 2006, entitled "Multi-Functional Hand-Held Device," all of which are incorporated herein by reference in their entireties.

[0064] Touchscreen 112 optionally has a video resolution of greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. A user optionally contacts touchscreen 112 using any suitable object or appendage, such as a stylus, a finger, or the like. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which may be less precise than stylus-based input due to the large contact area of ​​a finger on a touchscreen. In some embodiments, the device converts coarse finger-based input into precise pointer / cursor position or commands to perform the user's desired action.

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

[0066] Device 100 also includes a power system 162 for providing power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power within a portable device.

[0067] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor connected to light sensor controller 158 in I / O subsystem 106. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor 164 receives light from the environment, projected through one or more lenses, and converts the light into data representing an image. In conjunction with imaging module 143 (also referred to as a camera module), light sensor 164 optionally captures still images or video. In some embodiments, the light sensor is located on the back of device 100, opposite touchscreen display 112 on the front of the device, to enable the touchscreen display as a viewfinder for still image and / or video capture. In some embodiments, the light sensor is optionally located on the front of the device to obtain an image of the user for videoconference at the same time the user sees other videoconference participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by a user (e.g., by rotating the lens and sensor within the device housing), thereby using a single light sensor 164 in conjunction with a touch screen display for both video conferencing and still and / or video image capture.

[0068] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the surrounding environment. In some examples, at least one contact intensity sensor is located on or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some examples, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display 112 located on the front of device 100.

[0069] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled with peripherals interface 118. Alternatively, proximity sensor 166 is optionally connected to an input controller 160 in I / O subsystem 106. The proximity sensor 166 may optionally be implemented as described in U.S. patent application Ser. No. 11 / 241,839, "Proximity Detector In Handheld Device," Ser. No. 11 / 240,788, "Proximity Detector In Handheld Device," Ser. No. 11 / 620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output," Ser. No. 11 / 586,862, "Automated Response To And Sensing Of User Activity In Portable Devices," and Ser. No. 11 / 638,251, "Methods And Systems For Automatic Configuration Of Peripherals," which are incorporated herein by reference in their entireties. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0070] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I / O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear training, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some examples, at least one tactile output generator is disposed on or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or laterally (e.g., back and forth in the same plane as the surface of device 100). In some examples, at least one tactile output generator sensor is disposed on the back of device 100, opposite touchscreen display 112 disposed on the front of device 100.

[0071] Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I / O subsystem 106. Accelerometer 168 optionally functions as described in U.S. Patent Application Publication Nos. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated herein by reference in their entireties. In some embodiments, information is displayed on the touchscreen display in portrait or landscape orientation based on an analysis of data received from the one or more accelerometers. Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information regarding the position and orientation (e.g., vertical or horizontal) of device 100.

[0072] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch / 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 applications (or instruction sets) 136. Additionally, in some embodiments, as shown in FIGS. 1A and 3, memory 102 (FIG. 1A) or memory 370 (FIG. 3) stores device / global internal state 157. 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 which applications, views, or other information are occupying various regions of touchscreen display 112; sensor state, which includes information obtained from the device's various sensors and input control devices 116; and location information regarding the location and / or orientation of the device.

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

[0074] Communications module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by RF circuitry 108 and / or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) is adapted to couple to other devices directly or indirectly through a network (e.g., Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector identical to or similar to and / or compatible with the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

[0075] Contact / motion module 130, optionally in conjunction with display controller 156, detects contact with touch screen 112 and other touch-sensing devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to detecting contact, such as determining whether contact has occurred (e.g., detecting a finger down event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger up event or an interruption in the contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point represented by the set of contact data optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These actions are, optionally, applied to a single contact (e.g., one finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some examples, contact / motion module 130 and display controller 156 detect contacts on a touchpad.

[0076] In some examples, contact / motion module 130 uses a set of one or more intensity thresholds for determining whether an action has been performed by a user (e.g., for determining whether a user has “clicked” on an icon). In some examples, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of a particular physical actuator and can be adjusted without modifying the physical hardware of device 100). For example, the mouse “click” threshold of a trackpad or touchscreen display may be set to any of a wide range of predefined thresholds without modifying the hardware of the trackpad or touchscreen display. Additionally, in some implementations, a user of the device is provided with a software setting for adjusting 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-level click “intensity” parameter).

[0077] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or strength of detected contacts). Thus, gestures are optionally detected by detection of a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger down event (e.g., at an icon location), followed by detecting a finger lift off event at the same location (or substantially the same location) as the finger down event. As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger down event, followed by detecting one or more finger drag events, followed by detecting a finger lift off event.

[0078] Graphics module 132 includes various known software components for rendering and displaying graphics on touchscreen 112 or other display, including components for modifying the visual effects (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, but not limited to, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, and animations.

[0079] In some embodiments, graphics module 132 stores data representing the graphics to be used. Each graphic is optionally assigned a corresponding code. Graphics module 132 receives one or more codes specifying the graphics to be displayed, including coordinate data and other graphic characteristic data, as appropriate, from an application or the like, and then generates screen image data for output to display controller 156.

[0080] The tactile feedback module 133 includes various software components for generating instructions used by the tactile output generator(s) 167 to generate tactile outputs at one or more locations on the device 100 in response to user interaction with the device 100.

[0081] Text input module 134 is optionally a component of graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

[0082] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for use in location-based telephony, to the camera 143 as photo / video metadata, and to applications that provide location-based services, such as a weather widget, a local yellow pages widget, and a maps / navigation widget).

[0083] The application 136 optionally includes the following modules (or instruction sets), or a subset or superset thereof: ● a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ● Videoconferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141; ● Training support module 142, A camera module 143 for still and / or video images, ● Image management module 144, ●Video player module, ●Music player module, ● Browser module 147, ● Calendar module 148, A widget module 149, optionally including one or more of a weather widget 149-1, a stock price widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5 and other widgets obtained by the user, as well as user-created widgets 149-6; ● a widget creation module 150 for creating user-created widgets 149-6; ● Search module 151, A video and music player module 152 that integrates a video player module and a music player module; ● Memo module 153, Map module 154 and / or ●Online video module 155.

[0084] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA® enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

[0085] The contacts module 137, along with the touch screen 112, the display controller 156, the touch module 130, the graphics module 132, and the text input module 134, is optionally used to manage an address book or contact list (e.g., stored in the memory 102 or in the application internal state 192 of the contacts module 137 in the memory 370), including adding a name(s) to the address book, deleting a name(s) from the address book, associating a phone number(s), email address(es), address(es), or other information with a name, associating a picture with a name, categorizing and sorting names, providing phone numbers or email addresses to initiate and / or facilitate communication by telephone 138, videoconferencing module 139, email 140, or IM 141, and the like.

[0086] 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 is optionally used to enter a series of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify an entered telephone number, dial a corresponding telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As mentioned above, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0087] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, videoconferencing module 139 contains executable instructions for initiating, conducting, and terminating a videoconference between a user and one or more other participants in accordance with the user's instructions.

[0088] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 contains executable instructions for composing, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 144, email client module 140 makes it very easy to compose and send emails with still or video images captured by camera module 143.

[0089] In cooperation with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for entering characters corresponding to an instant message, modifying entered characters, sending the corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-based instant messaging, or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephone-based messaging (e.g., messages sent using SMS or MMS) and Internet-based messaging (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0090] In conjunction with the 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 training support module 142 contains executable instructions to create workouts (e.g., having time, distance and / or calorie burn goals), communicate with training sensors (sports devices), receive training sensor data, calibrate sensors used to monitor the workouts, select and play music for the workouts, and display, store and transmit the workout data.

[0091] In cooperation with touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, camera module 143 contains executable instructions to capture still images or video (including video streams) and store them in memory 102, change characteristics of the still images or video, or delete the still images or video from memory 102.

[0092] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 contains executable instructions for arranging, modifying (e.g., editing) or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing still and / or video images.

[0093] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, browser module 147 contains executable instructions for browsing the Internet at the direction of a user, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0094] In cooperation with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 contains executable instructions to create, display, modify, and store calendars and data associated with the calendars (e.g., calendar items, to-do lists, etc.) in accordance with a user's instructions.

[0095] In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is a mini-application (e.g., weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) that is optionally downloaded and used by a user, or a mini-application (e.g., user-created widget 149-6) that is created by a user. In some embodiments, a widget includes a Hypertext Markup Language (HTML) file, a Cascading Style Sheets (CSS) file, and a JavaScript file. In some embodiments, a widget includes an Extensible Markup Language (XML) file and a JavaScript file (e.g., Yahoo! Widget).

[0096] In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget creation module 150 is optionally used by a user to create a widget (e.g., turn a user-specified portion of a web page into a widget).

[0097] In cooperation with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the search module 151 contains executable instructions to search the memory 102 for text, music, sound, images, video, and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with a user's instructions.

[0098] In conjunction with touchscreen 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 contains executable instructions that enable a user to download and play pre-recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions to display, present, or otherwise play videos (on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (a registered trademark of Apple Inc.).

[0099] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like, in accordance with a user's instructions.

[0100] In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is used to receive, display, modify, and store maps and data associated with the maps (e.g., driving directions, data for stores and other points of interest at or near a particular location, and other location-based data), optionally in accordance with a user's instructions.

[0101] In conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 contains instructions that enable a user to access, view, receive (e.g., by streaming and / or downloading), play (e.g., on the touchscreen or on an external display connected via external port 124) online videos in one or more file formats, such as H.264, and send and otherwise manage emails containing links to particular online videos. In some embodiments, instant messaging module 141 is used to send links to particular online videos rather than email client module 140. Further description of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed June 20, 2007, and U.S. Patent Application No. 11 / 968,067, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed December 31, 2007, the entire contents of which are incorporated herein by reference.

[0102] Each of the above identified modules and applications corresponds to an executable instruction set that performs one or more of the functions described above, as well as the methods described in this application (e.g., computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules, and thus, in various embodiments, various subsets of these modules are optionally combined or otherwise rearranged. For example, a video player module is optionally combined with a music player module into a single module (e.g., video and music player module 152 of FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the above identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

[0103] In some embodiments, device 100 is a device on which operation of a predefined set of functions is performed exclusively through a touchscreen and / or touchpad. By using the touchscreen and / or touchpad as the primary input control device for operation of device 100, the number of physical input control devices (push buttons, dials, etc.) on device 100 is optionally reduced.

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

[0105] 1B is a block diagram illustrating example components for event processing, according to some embodiments. In some embodiments, memory 102 (FIG. 1A) or memory 370 (FIG. 3) includes event sorter 170 (e.g., in operating system 126) and corresponding application 136-1 (e.g., any of applications 137-151, 155, 380-390 described above).

[0106] Event sorter 170 receives the event information and determines application 136-1 and application view 191 of application 136-1 to which the event information is to be delivered. Event sorter 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192 that indicates the current application view(s) that are displayed on touch-sensitive display 112 when the application is active or running. In some embodiments, device / global internal state 157 is used by event sorter 170 to determine which application(s) is currently active, and application internal state 192 is used by event sorter 170 to determine application view 191 to which the event information is to be delivered.

[0107] In some embodiments, application internal state 192 includes additional information such as one or more of resume information used when application 136-1 resumes execution, user interface state information indicating information being displayed or prepared for display by application 136-1, a state queue to allow the user to return to a previous state or view of application 136-1, and a redo / undo queue of previous actions taken by the user.

[0108] Event monitor 171 receives event information from peripherals interface 118. The event information includes information of sub-events (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

[0109] In some embodiments, event monitor 171 sends a request to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits the event information. In other embodiments, peripherals interface 118 transmits the event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or for longer than a predetermined period of time).

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

[0111] Hit view determination module 172 provides software procedures for determining where in one or more views a sub-event occurred when touch-sensitive display 112 displays more than one view. A view consists of controls and other elements that a user can see on the display.

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

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

[0114] Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive the particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive the particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of the sub-event are actively participating views, and therefore all actively participating views should receive the particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with one particular view, views higher in the hierarchy remain actively participating views.

[0115] Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information obtained by a corresponding event receiver 182 in an event queue.

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

[0117] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, a corresponding event handler 190 includes one or more of data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or invokes data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more corresponding event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in the corresponding application view 191.

[0118] Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes 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 (optionally including sub-event delivery instructions).

[0119] Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, e.g., a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves a touch movement, the event information also optionally includes the speed and direction of the sub-event. In some implementations, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the device's current orientation (also called the device's attitude).

[0120] The event comparator 184 compares the event information to predefined event or sub-event definitions and determines the event or sub-event or determines or updates the state of the event or sub-event based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a predefined set of sub-events), such as event 1 (187-1), event 2 (187-2), etc. In some embodiments, the sub-events in the event 187 include, for example, touch start, touch end, touch movement, touch stop, and multiple touches. In one embodiment, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch (touch start) on the displayed object for a given stage, a first lift off (touch end) for the given stage, a second touch (touch start) on the displayed object for the given stage, and a second lift off (touch end) for the given stage. In another embodiment, the definition for event 2 (187-2) is a drag operation on the displayed object. The drag operation includes, for example, a touch (or contact) on a display object for a given step, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (end of the touch). In some embodiments, the event also includes information regarding one or more associated event handlers 190.

[0121] In some embodiments, event definition 187 includes a definition of the event for each user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view in which three user interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (the sub-event). If each displayed object is associated with a corresponding event handler 190, event comparator 184 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 object that triggers the hit test.

[0122] In some embodiments, the definition for each event (187) also includes a delay action that delays delivery of the event information until it is determined whether the sequence of sub-events corresponds to the event type of the event recognizer.

[0123] If each event recognizer 180 determines that the sequence of sub-events does not match any of the events in event definition 186, then each event recognizer 180 enters an event disabled, event failed, or event finished state and thereafter ignores the next sub-event of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

[0124] In some embodiments, each event recognizer 180 includes metadata 183 having configurable properties, flags, and / or lists that indicate how the event delivery system performs sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact or are enabled to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how sub-events are delivered to various levels in a view or programmatic hierarchy.

[0125] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more particular sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and deferring sending) the sub-events to each hit view. In some embodiments, the event recognizer 180 emits a flag associated with the recognized event, and the event handler 190 associated with the flag captures the flag and performs predefined processing.

[0126] 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 a set of sub-events or an actively participating view. The event handler associated with the set of sub-events or an actively participating view receives the event information and performs predetermined processing.

[0127] In some embodiments, data updater 176 creates and updates data used by application 136-1. For example, data updater 176 updates phone numbers used by contacts module 137 or stores video files used by a video player module. In some embodiments, object updater 177 creates and updates objects used by application 136-1. For example, object updater 177 creates new user interface objects or updates the positions of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on the touch-sensitive display.

[0128] In some embodiments, event handler(s) 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of each application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0129] It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 with an input device, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holds, touch movements such as tapping, dragging, scrolling on a touchpad, pen stylus input, device movements, verbal cues, detected eye training, biometric input, and / or any combination thereof, are optionally utilized as inputs corresponding to sub-events that define the event to be recognized.

[0130] FIG. 2 illustrates portable multifunction device 100 having touch screen 112, according to some embodiments. The touch screen optionally displays one or more graphics in user interface (UI) 200. In this embodiment, as well as embodiments described below, a user may 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) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics occurs when a user breaks contact with one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upward and / or downward), and / or a rotation of a finger in contact with device 100 (right to left, left to right, upward and / or downward). In some implementations or situations, accidental contact with a graphic does not result in selection of the graphic. For example, a swipe gesture sweeping over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

[0131] Device 100 also optionally includes one or more physical buttons, such as a “home” or menu button 204. As mentioned above, menu button 204 is optionally used for navigation to any application 136 in a set of applications optionally executing on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.

[0132] In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for turning power to the device on / off and locking the device, volume control button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external port 124 for docking / charging. Push button 206 is optionally used to turn power on / off on the device by pressing and holding the button down for a predefined time, to lock the device by pressing and releasing the button before the predefined time has elapsed, and / or to unlock the device or initiate an unlocking process. In an alternative embodiment, device 100 also receives verbal input through microphone 113 for activating or deactivating some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touch screen 112 and / or one or more tactile output generators 167 for generating a tactile output to a user of device 100.

[0133] FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or commercial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interfaces 330, including a display 340, which is typically a touchscreen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A) for generating tactile output on device 300, sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch-sensitive sensors, and / or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, ​​word processing module 384, website creation module 386, disk authoring module 388, and / or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

[0134] Each of the above-identified elements of FIG. 3 is optionally stored in one or more of the memory devices mentioned above. Each of the above-identified modules corresponds to an instruction set that performs the functions described above. The above-identified modules or programs (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules, and thus, in various embodiments, various subsets of these modules are optionally combined or otherwise rearranged. In some embodiments, memory 370 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.

[0135] Attention is now directed to examples of user interfaces that are optionally implemented on portable multifunction device 100, for example.

[0136] 4A shows an example user interface for a menu of applications on portable multifunction device 100, according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof: ● signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals; ●Time 404, ●Bluetooth indicator 405, ● Battery status indicator 406, A tray 408 containing icons for frequently used applications, such as: ○ An icon 416 for the phone module 138, labeled "Phone", optionally including an indicator 414 of the number of missed calls or voicemail messages; ○ An icon 418 for the email client module 140, labeled "Mail", optionally including an indicator 410 of the number of unread emails; ○ An icon 420 for the browser module 147, labeled "Browser"; and ○ An icon 422 for the video and music player module 152, also called the iPod (trademark of Apple Inc.) module 152, labeled "iPod"; and ●Icons for other applications, such as: ○ An icon 424 for the IM module 141 labeled "Messages", ○ An icon 426 for the calendar module 148, labeled "Calendar"; ○ An icon 428 for the image management module 144, labeled "Photos"; ○ An icon 430 for the camera module 143, labeled "camera"; ○ An icon 432 for the online video module 155, labeled "Online Video"; ○ Icon 434 for stock price widget 149-2, labeled "Stock Price" ○ Icon 436 for the map module 154, labeled "Map"; ○ Icon 438 for weather widget 149-1, labeled "Weather"; ○ Icon 440 for alarm clock widget 149-4, labeled "Clock"; ○ An icon 442 for the training support module 142, labeled "Training Support"; ○ An icon 444 for the notes module 153, labeled "Notes"; and ○ An icon 446 for a settings application or module, labeled “Settings,” that provides access to settings related to the device 100 and its various applications 136.

[0137] 4A are merely exemplary. For example, icon 422 for video and music player module 152 is labeled "Music" or "Music Player." Other labels are optionally used for the various application icons. In some embodiments, the label for each application icon includes the name of the application that corresponds to each application icon. In some embodiments, the label of a particular application icon is different from the name of the application that corresponds to the particular application icon.

[0138] 4B shows an exemplary user interface on a device (e.g., device 300 of FIG. 3) that includes a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3) that is separate from display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting the intensity of a contact on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating a tactile output to a user of device 300.

[0139] Although some of the following examples are described with reference to input on touch screen display 112 (where the touch-sensitive surface and display are combined), in some examples, the device detects input on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B. In some examples, this touch-sensitive surface (e.g., 451 in FIG. 4B) has a major axis (e.g., 452 in FIG. 4B) that corresponds to a major axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). According to these examples, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B) at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this manner, when the touch-sensitive surface is separate from the display, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device. It is to be understood that similar methods are optionally used for the other user interfaces described herein.

[0140] In addition, although the following examples are described primarily with reference to finger input (e.g., finger touch, finger tap gesture, finger swipe gesture), it should be understood that in some examples, one or more of those finger inputs are replaced with input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced with a mouse click (e.g., instead of a touch) followed by a cursor movement along the path of the swipe (e.g., instead of a touch movement). As another example, a tap gesture is optionally replaced with a mouse click while the cursor is positioned over the location of the tap gesture (e.g., instead of detecting a touch followed by ceasing to detect a touch). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are, optionally, being used simultaneously, or mice and finger touches are, optionally, being used simultaneously.

[0141] FIG. 5A illustrates an exemplary personal electronic device 500. Device 500 includes a body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504 (hereinafter, touchscreen 504). Instead of or in addition 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 a contact (e.g., a touch) being applied. The one or more intensity sensors of touchscreen 504 (or touch-sensitive surface) can provide output data representative of the intensity of the touch. A user interface of device 500 can respond to a touch based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface actions on device 500.

[0142] Exemplary techniques for detecting and processing touch intensity can be found, for example, in related applications, International Application 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 WO 2013 / 169849), and International Application 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 WO 2014 / 105276), each of which is incorporated by reference in its entirety.

[0143] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms can allow device 500 to be worn by a user.

[0144] FIG. 5B illustrates an exemplary personal electronic device 500. In some embodiments, the device 500 may include some or all of the components described with respect to FIGS. 1A, 1B, and 3. The device 500 has a bus 512 operably coupling an I / O unit 514 to one or more computer processors 516 and a memory 518. The I / O unit 514 may be connected to a display 504, which may have a touch-sensing component 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, the I / O unit 514 may connect to 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 technologies. The device 500 may include an input mechanism 506 and / or an input mechanism 508. The input mechanism 506 is optionally, for example, a rotatable input device, or a depressible and rotatable input device. Input mechanism 508 is optionally a button in some embodiments.

[0145] The input mechanism 508 is optionally a microphone in some embodiments. 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 combinations thereof, all of which may be operatively connected to the I / O section 514.

[0146] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may, for example, cause the computer processors to perform the techniques described below, including process 700 (FIGS. 7A and 7B), process 9000 (FIGS. 9A and 9B), process 1100 (FIG. 11), and process 1300 (FIG. 13). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions used by or in connection with an instruction execution system, apparatus, or device. In some embodiments, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD or Blu-ray technology, and persistent solid-state memory such as flash, solid-state drives, etc. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in multiple configurations.

[0147] As used herein, the term "affordance" refers to a user-interactive graphical user interface object that is optionally displayed on a display screen of device 100, 300 and / or 500 (FIGS. 1A, 3 and 5A-5B). For example, images (e.g., icons), buttons and text (e.g., hyperlinks) each, optionally, constitute an affordance.

[0148] As used herein, the term "focus selector" refers to an input element that indicates the current portion of a user interface with which a user is interacting. In some implementations involving a cursor or other position marker, when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B), the cursor acts as a "focus selector" when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element) and the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 in FIG. 1A or touchscreen 112 in FIG. 4A) that allows direct interaction with user interface elements on the touchscreen display, contact detected on the touchscreen acts as a "focus selector" such that when an input (e.g., a press input by contact) 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, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface (e.g., by using a tab key or arrow keys to move focus from one button to another) without a corresponding cursor movement or contact movement on the touchscreen display, and in these implementations, the focus selector moves to follow the movement of focus between different regions of the user interface. Regardless of the specific form taken by the focus selector, the focus selector is generally a user interface element (or contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device which element of the user interface the user intends 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, contact, or selection box) over a corresponding button indicates that the user intends to activate the corresponding button (and not other user interface elements shown on the device's display).

[0149] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some examples, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples or a set of intensity samples collected within a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) for a predetermined event (e.g., after detecting a contact, before detecting lift-off of the contact, before or after detecting the start of movement of the contact, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of: a maximum intensity of the contact, a mean value of the intensity of the contact, an average value of the intensity of the contact, the top 10% of the intensity of the contact, half the maximum intensity of the contact, 90% of the maximum intensity of the contact, etc. In some examples, the duration of the contact is used to determine the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some examples, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation is performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold results in a first action being performed, a contact having a characteristic intensity that exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second action being performed, and a contact having a characteristic intensity that exceeds the second threshold results in a third action being performed. In some examples, the comparison between the characteristic intensity and the one or more thresholds is used to determine whether to perform one or more actions (e.g., whether to perform each action or to omit performing each action), rather than to determine whether to perform the first action or the second action.

[0150] FIG. 5C illustrates detection of multiple contacts 552A-552E on touch-sensitive display screen 504 by multiple intensity sensors 524A-524D. FIG. 5C additionally includes an intensity diagram illustrating the current intensity measurements of intensity sensors 524A-524D in terms of intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are each 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are each 7 intensity units. In some implementations, the total intensity is the sum of the intensity measurements of multiple intensity sensors 524A-524D, which in this example is 32 intensity units. In some implementations, each contact is assigned a corresponding intensity that is a portion of the total intensity. FIG. 5D illustrates the assignment of the total intensity to contacts 552A-552E based on the distance of contacts 552A-552E from center of force 554. In this example, each of contacts 552A, 552B, and 552E is assigned a contact intensity of 8 intensity units of the total intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of the total intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij that is a portion of the total intensity A according to a predetermined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance of each contact point j to the center of force, and ΣDi is the sum of the distances of all each contact point to the center of force (e.g., from i=1 to the end). The operations described with reference to Figures 5C and 5D can be performed using electronic devices similar or identical to device 100, 300, or 500. In some examples, the characteristic intensity of the contact is based on one or more intensities of the contact. In some examples, an intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). Note that the intensity plots are not part of the displayed user interface, but are included in FIGS. 5C-5D for the reader's convenience.

[0151] In some examples, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a start position to an end position, where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end position is optionally based on only a portion of the swipe contact (e.g., only the portion of the swipe contact at the end position) rather than the entire continuous swipe contact. In some examples, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms may exclude small increases or decreases in the intensity of the swipe contact for purposes of determining the characteristic intensity.

[0152] The intensity of the contact on the touch-sensitive surface is optionally characterized against one or more intensity thresholds, such as a contact-detection intensity threshold, a light pressure intensity threshold, a deep pressure intensity threshold, and / or one or more other intensity thresholds. In some examples, the light pressure intensity threshold corresponds to an intensity at which the device performs an action typically associated with a physical mouse button or a click of a trackpad. In some examples, the deep pressure intensity threshold corresponds to an intensity at which the device performs an action different from an action typically associated with a physical mouse button or a click of a trackpad. In some examples, when a contact is detected with a characteristic intensity below the light pressure intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device moves a focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an action associated with the light pressure intensity threshold or the deep pressure intensity threshold. Generally, unless otherwise specified, these intensity thresholds are consistent among different sets of user interface appearances.

[0153] An increase in the characteristic intensity of the contact from an intensity below the light pressure intensity threshold to an intensity between the light pressure intensity threshold and the deep pressure intensity threshold may be referred to as a "light press" input. An increase in the characteristic intensity of the contact from an intensity below the deep pressure intensity threshold to an intensity above the deep pressure intensity threshold may be referred to as a "deep press" input. An increase in the characteristic intensity of the contact from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light pressure intensity threshold may be referred to as detecting a contact on the touch surface. A decrease in the characteristic intensity of the contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold may be referred to as detecting a lift-off of the contact from the touch surface. In some examples, the contact detection intensity threshold is zero. In some examples, the contact detection intensity threshold is greater than zero.

[0154] In some examples described herein, one or more operations are performed in response to detecting a gesture including the respective pressure inputs or in response to detecting the respective pressure inputs performed on the respective contact (or contacts), where the respective pressure inputs are detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a pressure input intensity threshold. In some examples, the respective actions are performed in response to detecting an increase in intensity of the respective contacts (e.g., a "downstroke" of the respective pressure input) above the pressure input intensity threshold. In some examples, the pressure inputs include an increase in intensity of the respective contacts above the pressure input intensity threshold and a subsequent decrease in intensity of the contacts below the pressure input intensity threshold, where the respective actions are performed in response to detecting a subsequent decrease in intensity of the respective contacts below the pressure input intensity threshold (e.g., an "upstroke" of the respective pressure input).

[0155] 5E to 5H show the results of the light pressure intensity threshold (e.g., “IT L " ) to the deep press intensity threshold in Figure 5H (e.g., "IT D5 illustrates detection of a gesture including a press input corresponding to an increase in the intensity of contact 562 to an intensity above a deep pressure intensity threshold (e.g., "IT 2"). The gesture made by contact 562 is detected on touch-sensitive surface 560. In doing so, cursor 576 is displayed over application icon 572B corresponding to app2 on displayed user interface 570 including application icons 572A-572D displayed in predetermined area 574. In some examples, the gesture is detected on touch-sensitive display 504. An intensity sensor detects the intensity of the contact on touch-sensitive surface 560. The device detects whether the intensity of contact 562 exceeds a deep pressure intensity threshold (e.g., "IT D Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture and during the gesture, a deep pressure intensity threshold (e.g., “IT D Based on contact 562 having an intensity greater than "," display reduced representations 578A-578C (e.g., thumbnails) of recently opened documents for app2, as shown in Figures 5F-5H. In some examples, the intensity is a characteristic intensity of the contact that is compared to one or more intensity thresholds. Note that the intensity plot of contact 562 is not part of the displayed user interface, but is included in Figures 5E-5H for the reader.

[0156] In some embodiments, the display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed near application icon 572B, as shown in FIG. 5F. As the animation progresses, representation 578A moves up and representation 578B is displayed near application icon 572B, as shown in FIG. 5G. Then, representation 578A moves up and representation 578B moves up toward representation 578A and representation 578C is displayed near application icon 572B, as shown in FIG. 5H. Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses based on the intensity of contact 562, as shown in FIGS. 5F-5G, where the intensity of contact 562 exceeds a deep pressure intensity threshold (e.g., "IT D Representations 578A-578C appear and move upward as the intensity increases toward "intensity." In some embodiments, the intensity on which the animation progression is based is a characteristic intensity of the contact. The operations described with reference to FIGS. 5E-5H may be performed using an electronic device similar or identical to device 100, 300 or 500.

[0157] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter," and the device defines or selects a hysteresis intensity threshold that has a predefined relationship to the pressure input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the pressure input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the pressure input intensity threshold). Thus, in some embodiments, the pressure input includes an increase in intensity of each contact above the pressure input intensity threshold and a subsequent decrease in intensity of each contact below the hysteresis intensity threshold corresponding to the pressure input intensity threshold, and each action is performed in response to detecting a decrease in intensity of each subsequent contact below that hysteresis intensity threshold (e.g., an "upstroke" of each pressure input). Similarly, in some examples, a pressure input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressure input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a respective action is performed in response to detection of that pressure input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

[0158] For ease of explanation, the description of an action performed in response to a pressure input associated with a pressure input intensity threshold or in response to a gesture including the pressure input is optionally triggered in response to detecting any of an increase in the intensity of the contact above the pressure input intensity threshold, an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the pressure input intensity threshold, a decrease in the intensity of the contact below the pressure input intensity threshold, and / or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the pressure input intensity threshold. Additionally, in examples described as an action being performed in response to detecting a decrease in the intensity of the contact below a pressure input intensity threshold, the action is optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to and lower than the pressure input intensity threshold.

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

[0160] As used herein, the terms "open application" or "running application" refer to a software application for which state information is maintained (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application is, optionally, any one of the following types of applications: ● The active application currently displayed on the display screen of the device on which the application is being used; Background applications (or background processes) that are not currently displayed, but for which one or more processes are being processed by one or more processors; and A suspended or hibernated application that is not running but has state information stored in memory (volatile and / or non-volatile, respectively) that can be used to resume execution of that application.

[0161] As used herein, the term "closed application" refers to a software application for which no state information is maintained (e.g., no state information for the closed application is stored in the device's memory). Thus, closing an application includes stopping and / or removing the application process for that application, as well as removing state information for that application from the device's memory. Generally, opening a second application during a first application does not close the first application. Once the second application is displayed and the first application is no longer displayed, the first application becomes a background application.

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

[0163] 6A-6T illustrate example user interfaces associated with an activity competition, according to some embodiments. Such an activity competition allows participants in the activity competition to compete for a set period of time using physical activity detected by each device. For example, an activity competition can be set to last for one week. During the week, the participants' devices can detect the physical activity they have engaged in. By the end of the week, the participant with the most detected physical activity can win the activity competition. In some embodiments, the activity competition can be between two participants. In other embodiments, the activity competition can be between three or more participants.

[0164] FIG. 6A illustrates two electronic devices (i.e., device 600A and device 600B). For purposes of illustration, assume that device 600A belongs to Molly and device 600B belongs to Aled, and the two devices are in electronic communication (e.g., wireless communication). Each of the two electronic devices can include a touch-sensitive display (e.g., touch-sensitive display 602A and touch-sensitive display 602B) for displaying a user interface that can be interacted with by touching the touch-sensitive display. It should be appreciated that other input mechanisms (other than touch) can be used to interact with the user interfaces displayed by the two electronic devices. For example, each electronic device includes a rotatable input mechanism (e.g., rotatable input mechanism 604A and rotatable input mechanism 604B, each of which can be rotated relative to the housing of each device) and a push button (e.g., push button 606A and push button 606B). In some embodiments, devices 600A and 600B can include one or more features of devices 100, 300, or 500, as described above. When multiple electronic devices are shown in a single diagram, it should be appreciated that the user interfaces shown in the diagrams may be synchronized in time (e.g., while device 600A displays a first user interface in the diagram, while device 600B displays a second user interface in the diagram).

[0165] 6A, a user interface 608 is displayed on a touch-sensitive display 602A. User interface 608 is a notification displayed in response to a determination that a participant (e.g., Molly) of an activity competition associated with device 600A has completed three different physical activity goals (called rings). A representation of the three different completed physical activity goals is shown in representation 610B.

[0166] 6A , in response to receiving data transmitted from device 600A, user interface 612 is displayed indicating that Molly has completed three different physical activity goals. For example, user interface 612 may inform Aled that Molly has completed three different physical activity goals (as shown in representation 610A). It should be appreciated that user interface 612 may be displayed in response to other physical activities performed by Molly, such as Molly completing a workout.

[0167] The user interface 612 may comprise a scrollable list of affordances 614, each of which is associated with a respective action. For example, the scrollable list of affordances 614 may include a first affordance 614A, a second affordance 614B, and a third affordance 614C. Selection of the first affordance 614A may initiate a sequence for initiating an activity competition between Aled and Molly. Selection of the second affordance 614B may cause a message interface to be displayed that allows Aled to send a message to Molly in response to Molly completing her three physical activity goals (as shown in FIG. 6J and described below). Selection of the third affordance 614 may cause the device 600B to stop displaying the user interface 612. In FIG. 6A, for ease of illustration, the complete contents of the user interface 612 are shown, including portions that do not initially fit on the display (e.g., portions accessed by scrolling). Throughout the disclosure, additional user interfaces are shown in this manner for ease of illustration.

[0168] FIG 6B illustrates again the user interface shown in FIG 6A. Although device 600A continues to display user interface 608 of FIG 6B, it should be appreciated that a different user interface may be displayed. As discussed above, user interface 612 on device 600B includes a first affordance 614A. Referring to FIG 6B, a user input (e.g., a tap input) 601 corresponding to a selection of first affordance 614A is received. Pursuant to a determination that user input 601 is detected at first affordance 614A, a user interface associated with initiating an activity competition is displayed (e.g., user interface 616 shown in FIG 6C).

[0169] With reference to FIG. 6C, in response to selection of first affordance 614A, user interface 616 is displayed on touch-sensitive display 602B. User interface 616 explains the rules of the activity competition. It should be appreciated that in some examples, user interface 616 may not be displayed in response to selection of first affordance 614A (as shown in FIG. 6B). For example, Aled may have already started a certain number of activity competitions, and therefore a user interface explaining the rules of the activity competition is not necessary. In some examples, user interface 616 may be displayed a certain number of times per participant in response to selection of first affordance 614A. For example, user interface 616 may be displayed to Aled two times before it is no longer displayed to Aled.

[0170] User interface 616 includes icon 618. Icon 618 may represent an activity competition between Molly and Aled such that all activity competitions between Molly and Aled (e.g., past activity competitions) are associated with icon 618. In some embodiments, an activity competition between a different participant (e.g., Molly and Steve) may be represented by a different icon having a different visual theme than icon 618. It should be appreciated that in some embodiments, an icon may be assigned to the activity competition prior to display of user interface 616. User interface 616 further includes affordances 620 for indicating acceptance of terms in user interface 616 and for sending an invitation to Molly (e.g., to device 600A) to start the activity competition.

[0171] FIG 6D illustrates the user interface depicted in FIG 6C again. Although device 600A continues to display user interface 608 of FIG 6D, it should be appreciated that device 600A may display a different user interface. As discussed above, user interface 616 includes affordance 620A. Referring to FIG 6D, user input (e.g., tap input) 603 corresponding to a selection of affordance 620 is received. Pursuant to a determination that user input 603 is detected at affordance 620, an invitation for an activity competition between Aled and Molly (as shown in FIG 6E) may be sent to device 600A.

[0172] With reference to Figure 6E, in response to Molly selecting affordance 620 in user interface 616 (as shown in Figure 6D), user interface 628 may be displayed on device 600B and user interface 622 may be displayed on device 600A. User interface 628 indicates that Aled must wait for Molly to accept the invitation sent by Aled before the activity competition can begin. User interface 628 includes icon 630 (which may have the same theme as icon 618 shown in Figure 6C) and affordance 632 that stops the display of user interface 628.

[0173] User interface 622 of device 600A, like user interface 616, describes the rules of the activity competition. User interface 622 includes icons 624 (which may have the same theme as icons 618 shown in FIG. 6C). User interface 622 further includes a scrollable list of affordances 626, with each affordance associated with a different action. For example, scrollable list of affordances 626 includes a first affordance 626A and a second affordance 626B.

[0174] Selecting the first affordance 626A may accept the activity competition invitation sent by Aled. Accepting the invitation may start the activity competition at a predetermined time after the selection (e.g., midnight that day), as described further below. Selecting the second affordance 626B may cause the device 600B to decline the invitation (e.g., not start the activity competition) and stop displaying the user interface 612.

[0175] FIG 6F illustrates again the user interface depicted in FIG 6E. Although device 600B continues to display user interface 628 of FIG 6F, it should be appreciated that it may display a different user interface. As discussed above, user interface 622 on device 600A includes first affordance 626A. Referring to FIG 6F, user input (e.g., tap input) 605 is received, which corresponds to a selection of first affordance 626A. Pursuant to a determination that user input 605 is detected at first affordance 626A, an activity competition between Molly and Aled may be set to commence at a predetermined time in the future.

[0176] 6G, in response to receiving a selection (e.g., by Molly) of affordance 605 in user interface 622 (as shown in FIG. 6F), user interface 634 may be displayed on device 600A, and user interface 640 may be displayed on device 600B. User interface 634 indicates that an activity race with Aled starts tomorrow. User interface 634 includes icon 636 (which may have the same theme as icon 618 shown in FIG. 6C) and affordance 638 to stop displaying user interface 638.

[0177] User interface 640 indicates that the invitation sent by Aled has been accepted and that an activity competition with Molly will begin tomorrow. User interface 640 includes icons 642 (which may have the same theme as icon 618 shown in FIG. 6C). User interface 622 may further include a scrollable list of affordances 644, each of which is associated with a respective action. For example, scrollable list of affordances 626 includes a first affordance 626A for displaying a message user interface (shown in FIG. 6I) and a second affordance 626B for stopping display of user interface 640.

[0178] FIG 6H illustrates again the user interface depicted in FIG 6G. Although device 600A continues to display user interface 634 of FIG 6H, it should be appreciated that device 600A may display a different user interface. As discussed above, user interface 640 on device 600B includes a first affordance 644A. Referring to FIG 6H, a user input (e.g., a tap input) 607 corresponding to a selection of first affordance 644A is received. Pursuant to a determination that user input 607 is detected at first affordance 644A, a message user interface is displayed (as shown in FIG 6I).

[0179] With reference to FIG. 6I, device 600B displays user interface 646 in response to selection of first affordance 644A in user interface 640 (as shown in FIG. 6H). User interface 646 includes a scrollable list of affordances 648, each affordance associated with a different predefined message. Selection of an affordance in the scrollable list of affordances 648 can cause a communication (also referred to as a message) having a corresponding predefined message to be generated and sent to Molly. For example, selection of second affordance 648B can cause a communication having the text "You can't beat me!" to be sent to Molly.

[0180] FIG 6J illustrates again the user interface depicted in FIG 6I. Although device 600A continues to display user interface 634 of FIG 6J, it should be appreciated that a different user interface may be displayed. As discussed above, user interface 646 on device 600B includes second affordance 648B. Referring to FIG 6J, user input (e.g., tap input) 609 corresponding to a selection of second affordance 648B is received. Pursuant to a determination that user input 609 is detected at second affordance 648B, a communication having text corresponding to second affordance 648B may be generated and sent to Molly.

[0181] 6K, in response to selection of second affordance 648B in user interface 646 (as shown in FIG. 6J), device 600B displays user interface 656. User interface 656 indicates that a message has been sent and includes affordance 658 that causes the display of user interface 656 to cease.

[0182] Also, in response to selecting a second affordance 648B in user interface 646 (as shown in FIG. 6J), device 600A displays user interface 650 on touch-sensitive display 602A, as shown in FIG. 6K. User interface 650 includes a representation of a predefined message sent by Aled, as described above. User interface 650 may also include a scrollable list of affordances 652, each of which is associated with a respective action. For example, scrollable list of affordances 626 includes a first affordance 626A for displaying a message user interface (as shown in FIG. 6I) and a second affordance 626B for stopping display of user interface 650.

[0183] While the activity competition is active, participants in the activity competition may receive notifications including the status of the activity competition. For example, in response to starting the activity competition, a notification may be displayed to each of the participants in the activity competition, as shown in FIG. 6L.

[0184] 6L, user interface 660 is displayed on touch-sensitive display 602B of device 600B. Although not shown, a similar user interface can be displayed on touch-sensitive display 602A of device 600A.

[0185] User interface 660 indicates that an activity competition with Molly has begun. User interface 600 can include a scrollable list of affordances 662, with each affordance associated with a respective action. For example, scrollable list of affordances 626 includes (1) a first affordance 662A for displaying information about the activity competition, (2) a second affordance 662B (shown in FIG. 6I ) for displaying a message user interface, and (3) a third affordance 662C for stopping display of user interface 660.

[0186] As shown in FIG. 6L, first affordance 662A includes a first portion 663A having information related to Aled regarding the activity competition and a second portion 663B having information related to Molly regarding the activity competition. The information related to Aled includes a number icon 663C indicating the number of times Aled has won an activity competition with Molly. The information related to Aled further includes Aled's score 663D on the activity competition to date. It should be appreciated that the information included within first affordance 662A may differ from that depicted, such as the information may include a graph 670, as shown in FIG. 6M and described below.

[0187] Selection of the first affordance 662A may cause a user interface to be displayed having additional information about the activity competition. For example, this additional information may include a graph 670, as shown in FIG. 6M and described below.

[0188] In addition to notifications being displayed at the start of an activity competition, notifications may be displayed at predetermined times during the activity competition, either at an absolute time during the activity competition (e.g., 10:00 a.m. each day) or as a result of an event occurring on the device on which the notification is being displayed (e.g., a participant achieving a goal, completing a workout, or accessing a particular application on the device). Such notifications may include information related to one or more active activity competitions.

[0189] 6M, in response to a trigger being activated at a predetermined time, user interface 664 is displayed on touch-sensitive display 602B. For example, the predetermined time may be 10:00 PM on Friday, which would cause user interface 644 to be displayed.

[0190] User interface 644 comprises a scrollable list of affordances 666, each of which is associated with a respective action. For example, the scrollable list of affordances 666 includes a first affordance 666A for a first activity competition, a second affordance 666B for a second activity competition, and a third affordance 666C for stopping the display of user interface 660. In some examples, the order of the affordances of an activity competition may be based on when the activity competition ends. For example, activity competitions that end earlier may be included in the scrollable list before activity competitions that end later.

[0191] The first affordance 666A includes information related to the first activity competition. As shown in FIG. 6M, the first affordance 666A includes similar information as the first affordance 662A (shown in FIG. 6L). For example, the first affordance 666A (shown in FIG. 6M) includes an icon 668A having a number indicating the number of times Molly has won the activity competition against Aled. The first affordance 666A further includes an identification of Molly (e.g., element 668B) and Molly's score (e.g., element 668C) for the first activity competition so far (sometimes referred to as a cumulative score).

[0192] As shown in FIG. 6M, the first affordance 666A further includes a graph 670 of the first activity competition, where the graph 670 includes information about the first activity competition of a plurality of subsets (e.g., days). The graph 670 may include more granular information than that included in the element 668. The x-axis of the graph 670 includes an identification of a plurality of subsets of the first activity competition. As shown in FIG. 6M, each subset is a day of the week (e.g., reference numeral 670A refers to "M" for Monday). Note that "M" is located first to indicate that the first activity competition started on Monday. Additionally, note that in FIG. 6M, "F" (e.g., reference numeral 670D) is visually highlighted (e.g., circled) to indicate that Friday is the current day.

[0193] The y-axis of graph 670 includes a representation of the detected physical activity for each participant in the first activity competition of each subset. For example, representation 670B shows the amount of detected physical activity (e.g., detected by device 600A and transmitted to device 600B) for Molly on Monday, and representation 670C shows the amount of detected physical activity for Aled on Monday. By adjacent representation 670B to representation 670C, the physical activity of each participant on Monday can be easily compared. Note that the representation of Molly is provided to the left of the representation of Aled on graph 670. This configuration is such that 600B corresponds to Aled's device. If a subset has not yet occurred (e.g., Saturday as shown in FIG. 6M), the representation corresponding to the subset (e.g., reference numeral 670E) may be displayed as zero.

[0194] In some embodiments, the representations of the subsets may be normalized across the time period such that the best representation of the subset for the time period is displayed at a particular size and other representations are normalized based on this best representation. For example, if Molly scored the most points during the time period on Friday, then Molly's representation on Friday would be the largest representation. In such an embodiment, a representation of Molly or Aled with half the score would be represented as half the size of Molly's representation on Friday.

[0195] Note that the representations associated with Molly are shown as visually distinct from the representations associated with Aled in Figure 6M. For example, Molly's icon 668A is visually distinct from Aled's icon. Further, the representations of the subsets of Molly are visually distinct from the representations of the subsets of Aled.

[0196] In some examples, representations associated with participants who are winning the activity competition may be highlighted relative to participants who are losing the activity competition. For example, because Molly's cumulative score is higher than Aled's cumulative score, the representations associated with Molly may appear visually highlighted relative to the representations associated with Aled. By visually highlighting the representations associated with the winning participants, participants may quickly assess how they are performing in the activity competition.

[0197] Graph 670 also includes the number of subsets remaining in the first activity competition (eg, reference numeral 670F). For example, as shown in FIG. 6M, there are two days remaining in the first activity competition.

[0198] Representation 670 also includes icon 670G, which can indicate that selecting affordance 666A or icon 670G (depending on the configuration of icon 670G) will cause a message interface to be displayed (as shown in FIG. 6J).

[0199] As shown in FIG. 6M, the second affordance 666B includes information about a second activity competition between John and Aled. The second affordance 666B indicates that John and Aled have competed 11 times, with John winning 4 times and Aled winning 7 times. Note that the second affordance 666B indicates that different activity competitions may start on different days. For example, the first activity competition started on Monday and the second activity competition started on Thursday. Also, note that the second affordance 666B indicates that the duration (e.g., 7 days) may be the same across different activity competitions.

[0200] In addition to notifications being displayed when an activity competition begins and at predetermined times, notifications may be displayed in response to activity by another participant. For example, notifications may be displayed to Aled in response to physical activity by Molly reaching a daily goal (e.g., closing three activity rings) or working out. Such notifications may include information related to the activity competition with other participants.

[0201] 6N, in response to Molly reaching her three ring goal for the day, a user interface 672 is displayed on the touch-sensitive display 602B. The user interface 672 comprises a scrollable list of affordances 674, each of which is associated with a respective action. For example, the scrollable list of affordances 674 includes a first affordance 674A for an activity competition between Molly and Aled, a second affordance 674B for displaying a message user interface (as shown in FIG. 6I), and a third affordance 674C for stopping the display of the user interface 672. The first affordance 674A is similar to the affordances described above for the first affordance 666A of FIG. 6M.

[0202] When the activity competition ends, a notification can be sent to the participants of the activity competition (e.g., displayed on their respective devices). Such notification can provide the results of the activity competition, including medal awards to winners, and includes an option to start a new activity competition, as shown in FIG. 6O.

[0203] 6O, user interface 676 is displayed on touch-sensitive display 602A in response to the completion of an activity competition between Molly and Aled. User interface 676 may include text provided to Molly and the results of the activity competition. For example, user interface 676 may state "ALED WON" and include information that Molly's best days during the activity competition were Friday and Monday.

[0204] User interface 676 comprises a scrollable list of affordances 678, each of which is associated with a respective action. For example, scrollable list of affordances 678 includes a first affordance 678A for an activity competition between Molly and Aled, a second affordance 678B for displaying a message user interface (as shown in FIG. 6I), a third affordance 678C for initiating a process to start a new activity competition (as described further below), and a fourth affordance 678D for stopping display of user interface 676.

[0205] Also, in response to the completion of the activity competition between Molly and Aled, user interface 680 is displayed on touch-sensitive display 602B. User interface 680 may include text provided to Aled and the results of the activity competition. For example, user interface 676 may state, "YOU WIN," and include information that Aled's best day during the activity competition was Saturday, with 794 points.

[0206] User interface 680 includes an icon 682 representing a victory for Aled in response to winning the activity competition. In response to winning icon 682, icon 682 may be placed in Aled's trophy case, as further described below with respect to FIG.

[0207] User interface 680 may also include a scrollable list of affordances 684, with each affordance associated with a respective action. For example, the scrollable list of affordances 684 may include a first affordance 684A for an activity competition between Molly and Aled, a second affordance 684B for displaying a message user interface (as shown in FIG. 6I), a third affordance 684C for initiating a process to start a new activity competition (as described further below), and a fourth affordance 684D for stopping display of user interface 680.

[0208] It should be appreciated that because user interface 676 and user interface 680 are side-by-side, the representations in the graphs (e.g., the graph included in first affordance 678A and the graph included in first affordance 684A) may be swapped depending on where the graphs are displayed. For example, when the graphs are displayed on Aled's device, the representation associated with Aled is generally to the right of the representation associated with Molly. Similarly, when the graphs are displayed on Molly's device, the representation associated with Molly is generally to the right of the representation associated with Alex. Also note that FIG. 6O illustrates that the highlight has changed (e.g., switched) from Molly to Aled (e.g., relative to FIG. 6M) because Aled is winning the activity competition shown in FIG. 6O. Such a switch may occur whenever the lead in the activity competition changes.

[0209] FIG. 6P illustrates the user interface depicted in FIG. 6O again. As described above, the user interface 676 on the device 600A includes a third affordance 678C. Referring to FIG. 6P, a user input (e.g., a tap input) 611 corresponding to a selection of the third affordance 678C is received. Pursuant to a determination that the user input 611 is detected at the third affordance 678C, a user interface associated with starting an activity competition is displayed (e.g., the user interface 686 shown in FIG. 6Q), an invitation for a new activity competition is sent to the alert, and a user interface associated with the invitation (e.g., the user interface 688 shown in FIG. 6Q) is displayed. It should be appreciated that although the device 600A is illustrated as receiving the user input 611, the device 600B can receive a similar user input on the third affordance 684C and similar functions are performed.

[0210] 6Q, in response to selecting third affordance 678C (as shown in FIG. 6P), user interface 686 is displayed on touch-sensitive display 602A. User interface 686 indicates that an invitation for a new activity competition has been sent to Aled. User interface 686 includes an affordance 687 for stopping the display of user interface 686.

[0211] 6Q, in response to selecting third affordance 678C (as shown in FIG. 6P), user interface 688 is displayed on touch-sensitive display 602B. User interface 688 indicates that Molly has invited Aled to a new activity competition. User interface 688 includes an icon 689 representing the activity competition between Molly and Aled. User interface 688 further comprises a scrollable list of affordances 690, each of which is associated with a respective action. For example, scrollable list of affordances 690 includes first affordance 690A and second affordance 690B.

[0212] 6E, selection of the first affordance 690A may cause a new activity competition between Molly and Aled to start at a predetermined time (e.g., midnight on the same day) after selection of the first affordance 690A. Selection of the second affordance 626B may cause the device 600B to decline the invitation (e.g., not start a new activity competition) and stop displaying the user interface 688.

[0213] FIG. 6R illustrates again the user interface depicted in FIG. 6Q. Although device 600A continues to display user interface 686 of FIG. 6R, it should be appreciated that device 600A may display a different user interface. As discussed above, user interface 688 on device 600B includes first affordance 690A. Referring to FIG. 6R, user input (e.g., tap input) 613 corresponding to a selection of first affordance 690A is received. Pursuant to a determination that user input 613 is detected at first affordance 690A, a new activity competition between Molly and Aled may be set to begin at a predetermined time in the future.

[0214] With reference to Figure 6S, in response to receiving a selection by Aled of affordance 690A in user interface 688 (as shown in Figure 6R), user interface 694 is displayed on device 600B and user interface 691 is displayed on device 600A. User interface 694 indicates that a new activity competition with Molly begins tomorrow. User interface 694 includes icon 695 (which may have the same theme as icon 618 shown in Figure 6C) and affordance 696 that stops the display of user interface 694.

[0215] User interface 691 indicates that the invitation sent by Molly has been accepted and that an activity race with Aled begins tomorrow. User interface 691 includes icons 692 (which may have the same theme as icon 618 shown in FIG. 6C). User interface 691 further includes a scrollable list of affordances 693, with each affordance associated with a respective action. For example, scrollable list of affordances 693 includes a first affordance 693A for displaying a message user interface (as shown in FIG. 6I) and a second affordance 693B for stopping display of user interface 691.

[0216] Although the above figures show an electronic device in the form of a smartwatch, it should be appreciated that any of the above-described user interfaces may be displayed on a different electronic device, such as a smartphone, etc. In some examples, the above-described user interfaces, when displayed on an electronic device having a larger display area, may include additional details (such as those shown in FIG. 6T) that are not shown on an electronic device having a smaller display.

[0217] 6T, a user interface 697 is displayed on a touch-sensitive display 802 of a device 800. In some embodiments, device 800 includes one or more features of devices 100, 300, 500, or 600. User interface 697 includes an affordance 698 that includes information related to an activity competition between Molly and Aled. Similar to that described above with respect to FIG. 6M, affordance 698 includes a number icon 698A indicating the number of times Molly has won the activity competition with Aled. Affordance 698 further includes an identity of Molly (e.g., element 698B), and Molly's score on the activity competition to date (e.g., element 698C) (sometimes referred to as a cumulative score).

[0218] Also, similar to that described above with respect to FIG. 6M, affordance 698 further includes a graph of the activity competition, but the graph includes information regarding the activity competition for multiple subsets (e.g., days). The x-axis of the graph includes an identification of the multiple subsets of the activity competition. As shown in FIG. 6T, each subset is a day of the week (e.g., reference numeral 698G refers to "Mon" on Monday). Note that "Mon" is placed first to indicate that the activity competition started on Monday. Additionally, note that "Fri" (e.g., reference numeral 698J) is visually highlighted (e.g., circled) in FIG. 6T to indicate that Friday is the current day.

[0219] The y-axis of the graph includes a representation of the detected physical activity for each participant in the activity competition for each subset. For example, representation 698H shows the amount of physical activity received for Molly (e.g., detected by device 600A and transmitted to device 800) on Monday, and representation 698I shows the amount of physical activity detected for Aled on Monday. By adjacent representation 698H to representation 698I, the physical activity of each participant on Monday can be easily compared. If a subset has not yet occurred (e.g., Saturday as shown in FIG. 6T), the representation corresponding to the subset (e.g., reference numeral 618K) may be displayed as zero.

[0220] In some examples, the representations of the subsets may be normalized across the time period such that the best representation of the subset for the time period is displayed at a particular size and other representations are normalized based on this best representation. For example, if Aled earned the most points during the time period on Monday, then Aled's representation on Monday would be the largest representation. In such an example, a representation of Molly or Aled with half the score would be displayed half the size of Aled's representation on Monday. As shown in FIG. 6T, the graph further includes a value 698L indicating the scale of the graph. This scale allows the participant to better understand the number of points for each representation in the graph.

[0221] Note that the representations associated with Molly are shown as visually distinct from the representations associated with Aled in Figure 6T. For example, Molly's icon 698A is visually distinct from Aled's icon 698D. Additionally, the representations of the subsets of Molly are visually distinct from the representations of the subsets of Aled.

[0222] In some examples, representations associated with participants who are winning the activity competition may be highlighted relative to participants who are losing the activity competition. For example, because Molly's cumulative score is higher than Aled's cumulative score, the representations associated with Molly may appear visually highlighted relative to the representations associated with Aled. By visually highlighting the representations associated with the winning participants, participants may quickly assess how they are performing in the activity competition.

[0223] Unlike graph 670 shown in FIG. 6M, the graph shown in FIG. 6T further includes additional information about the activity competition. For example, the graph includes the daily average number of points for each participant in the activity competition (e.g., reference numbers 698M and 698N). In particular, Molly has a daily average of 487 points and Aled has a daily average of 442 points. In the example shown in FIG. 6T, Molly's daily average is highlighted (e.g., in bold) because she is currently winning the activity competition. It should be appreciated that other additional information not included in graph 670 (shown in FIG. 6M) may be included in the graph shown in FIG. 6T.

[0224] In some embodiments, points awarded to participants in an activity competition are based on a percentage of a goal the participant achieves. For example, a goal may correspond to a daily walking volume. Such goals may be set by participants before the activity begins (in some embodiments) or at any time during the activity competition (in other embodiments). In some embodiments, different participants in an activity competition may have different goals. In some embodiments, points awarded to participants upon activity completion are based on a two-tiered scoring system where the scoring changes when a participant reaches a threshold (e.g., bonus points after a threshold).

[0225] 7A and 7B include a flow diagram illustrating a method for displaying an activity competition representation using an electronic device, according to some embodiments. Method 700 is performed on a device having a display (e.g., 100, 300, 500, 600A, 600B, 800). Some operations in method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0226] As described below, the method 700 provides an intuitive way of displaying a user interface on a device corresponding to a first user, the user interface including a graph of an activity competition (associated with a first user and a second user) with (1) a comparison of the scores for each day of the activity competition between the first user and the second user, and (2) a total throughout the activity competition. The user interface allows a user viewing the user interface to easily access physical activity data corresponding to the second user. This method reduces the cognitive burden on a user to access physical activity data corresponding to another user, thereby resulting in a more efficient human-machine interface. In a battery-powered computing device, power is conserved and the time between battery charges is increased by allowing a user to access physical activity data corresponding to another user more quickly and efficiently.

[0227] In block 702, a device (e.g., 600B in FIG. 6M and 800 in FIG. 6T) receives first user activity data (e.g., in FIG. 6M, data represented by the upper right portion of 666A and representations for Aled, and in FIG. 6T, 698D, 698E, 698F, 698I and other representations for Aled) for a period (e.g., a day, a week, a month) (e.g., in FIG. 6M, Monday through Sunday for the first activity competition, Thursday through Wednesday for the second activity competition, and in FIG. 6T, Monday through Sunday). The first user activity data includes first user activity data (e.g., in FIG. 6M, data represented by representation 670C, and in FIG. 6T, data represented by representation 698I) for at least a first subset of time (e.g., an hour, a day, a week) (e.g., in FIG. 6M, Monday for the first activity competition, Thursday for the second activity competition, and in FIG. 6T, Monday) and first user activity data (e.g., in FIG. 6M, data represented by Aled's representation for Tuesday, and in FIG. 6T, data represented by Aled's representation for Tuesday) for a second subset of time (e.g., in FIG. 6M, Tuesday for the first activity competition, Wednesday for the second activity competition, and in FIG. 6T, Tuesday).

[0228] In some examples, the first user activity data is received by the device (e.g., 600B of 6M, 800 of FIG. 6T) from a second device (e.g., 600A of FIG. 6A) (e.g., via one or more antennas of the device). For example, receiving the first user activity data may include detecting the first user activity data using one or more sensors of the device. In some examples, the one or more sensors include a heart rate monitor, a GPS positioning device, a gyroscope, etc.

[0229] In block 704, the device (e.g., 600B in FIG. 6M, 800 in FIG. 6T) receives second user activity data for the time period (e.g., in FIG. 6M, the data represented by the upper left portion of 666A and the representations for Molly, and in FIG. 6T, the data represented by 698A, 698B, 698C, 698H and other representations for Molly). The second user activity data includes at least the second user activity data for the first subset of time (e.g., in FIG. 6M, the data represented by representation 670B, and in FIG. 6T, the data represented by representation 698H) and the second user activity data for the second subset of time (e.g., in FIG. 6M, the data represented by Molly's representation for Tuesday, and in FIG. 6T, the data represented by Molly's representation for Tuesday).

[0230] In some embodiments, the second user activity data is received by the device (e.g., by one or more antennas of the device) from a second device (e.g., 600A in FIG. 6A). For example, receiving the second user activity data may include receiving the second user activity data from an external device (e.g., 600A in FIG. 6A) (e.g., by transmission from the external device).

[0231] In some embodiments, in response to receiving second user activity data from an external device (e.g., 600A of FIG. 6A ), the device (e.g., 600B of FIG. 6M , 800 of FIG. 6T ) may output an activity notification (visual, tactile, or audio alert) (612 of FIG. 6A ).

[0232] At 712, the device (e.g., 600B of FIG. 6M and 800 of FIG. 6T) displays a user interface (e.g., 664 of FIG. 6M and 697 of FIG. 6T) on a display (e.g., 602B of FIG. 6M and 802 of FIG. 6T). In some embodiments, the activity notification (e.g., 612 of FIG. 6M) described above is output prior to displaying the user interface.

[0233] In some examples, before displaying a user interface (e.g., 664 in FIG. 6M and 697 in FIG. 6T), the device (e.g., 600B in FIG. 6M and 800 in FIG. 6T) displays an activity summary notification (e.g., 664 in FIG. 6M when the user interface is 672 in FIG. 6N). The activity summary notification includes (1) a first notification element (e.g., information about an activity competition between a first user and a second user) (e.g., 666A in FIG. 6M) based on the first user activity data and / or the second user activity data, and (2) a second notification element (information about an activity competition between a third user and the first user) (e.g., 666B in FIG. 6M) based on at least third user activity data that is different from the first user activity data and different from the second user activity data.

[0234] At 714, a user interface (e.g., 664 in FIG. 6M, 697 in FIG. 6T) includes a representation (e.g., a graphical or textual display of values) of the first user activity data for the first time subset (e.g., 670C in FIG. 6M).

[0235] At 716, the user interface (e.g., 664 in FIG. 6M and 697 in FIG. 6T) further includes a representation (e.g., a graphical or textual display of values) of the first user activity data for the second time subset (e.g., the representation of Aled for Tuesday in FIG. 6M).

[0236] At 718, the user interface (e.g., 664 of FIG. 6M and 697 of FIG. 6T) further includes a cumulative representation of the first user activity data for the time period (e.g., a graphical or textual summary of the activity data for the entire time period) (e.g., the top right portion of FIG. 6M). The cumulative representation of the first user activity data for the time period is based on at least the first user activity data of the first subset of time and the first user activity data of the second subset of time. In some embodiments, the cumulative representation is presented in the same units (or different units) as the representation of the activity data of the time subsets.

[0237] At 720, the user interface (e.g., 664 in FIG. 6M and 697 in FIG. 6T) further includes a representation of the second user activity data of the first time subset (e.g., 670B in FIG. 6M). Displaying the scores of different users for a day provides feedback for the activity data received by the device on the same day. Providing improved feedback increases user participation in the activity competition, improves device usability, and provides a more efficient user-device interface (e.g., by helping the user provide proper inputs and reducing user errors when operating / interacting with the device), which further reduces power usage and improves device battery life by allowing the user to use the device more quickly and efficiently. The scores also provide an improved man-machine interface by reducing the number of interactions to display multiple users' activity data information.

[0238] In some examples, the representation of the second user activity data for the first time subset is displayed adjacent (e.g., next to or within a first region of the user interface) to the representation of the first user activity data for the first time subset (e.g., 670C of FIG. 6M). In some examples, the representation of the first user activity data for the first time subset is adjacent to the representation of the second user activity data for the first time subset (e.g., without intervening representations of activity data for other time subsets). Displaying the first user's score adjacent to the second user's score provides comparative feedback on the physical activity detected by the device. Providing improved feedback may increase user participation in the activity competition, improve usability of the device, and provide a more efficient user-device interface (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), thereby allowing the user to use the device more quickly and efficiently, further reducing power usage and improving the device's battery life.

[0239] At 722, the user interface (e.g., 664 in FIG. 6M and 697 in FIG. 6T) further includes a representation of second user activity data for the second time subset (e.g., in FIG. 6M, a representation of Molly for Tuesday). Displaying the scores for the different days provides feedback on the activity data received by the device for the different days. Providing improved feedback may increase user participation in the activity competition, improve usability of the device, and provide a more efficient user-device interface (e.g., by helping the user provide proper inputs and reducing user errors when operating / interacting with the device), thereby allowing the user to use the device more quickly and efficiently, further reducing power usage and improving the device's battery life. The scores also provide an improved man-machine interface by reducing the number of interactions to display activity data information for different time subsets.

[0240] In some embodiments, a representation of the second user activity data for the second subset of time (e.g., in FIG. 6M , the representation of Aled for Tuesday) is displayed adjacent to the first user activity data for the second subset of time (e.g., next to or within a second region of the user interface) and not adjacent to representations of the second user activity data for other subsets of time.

[0241] At 724, the user interface (e.g., 664 of FIG. 6M and 697 of FIG. 6T) further includes a cumulative representation of the second user activity data for the time period (e.g., 668A, 668B, and 669C of FIG. 6M). The cumulative representation of the second user activity data for the time period can be based on at least the second user activity data of the first time subset and the second user activity data of the second time subset. Displaying the user's total score provides feedback on the activity data received by the device of the first and second users. Providing improved feedback can increase user participation in the activity competition, improve device usability, and provide a more efficient user-device interface (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which can further reduce power usage and improve device battery life by allowing the user to use the device more quickly and efficiently. Displaying the user's total score provides feedback on the activity data received by the device of the first and second users. Providing improved feedback may increase user participation in activity competitions, improve usability of the device, and provide a more efficient user-device interface (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), thereby allowing the user to use the device more quickly and efficiently, further reducing power usage and improving the device's battery life.

[0242] In some embodiments, the first temporal subset of the first user activity data corresponds to the first temporal subset of the second user activity data.

[0243] In some embodiments, the user interface (e.g., 664 in FIG. 6M and 697 in FIG. 6T) may further include a representation (e.g., a textual representation, a graphical representation) of the number of remaining time subsets within the period (e.g., 670F in FIG. 6M).

[0244] In some examples, the user interface (e.g., 664 in FIG. 6M, 697 in FIG. 6T) includes an identification of the current time subset (e.g., the “F” in the first activity competition in FIG. 6M) that is visually highlighted (e.g., a circle around the “F” in FIG. 6M).

[0245] In some embodiments, the length of the first time subset is equal to the length of the second time subset (eg, Monday through Sunday in FIG. 6M).

[0246] In some embodiments, displaying a user interface (e.g., 664 of FIG. 6M and 697 of FIG. 6T) includes (1) visually enhancing (e.g., highlighting) the cumulative representation of the first user activity data for the period in accordance with a determination that a first value corresponding to the cumulative representation of the first user activity data (e.g., “2136” of FIG. 6M) exceeds a second value corresponding to the cumulative representation of the second user activity data (e.g., “2303” of FIG. 6M), and (2) visually enhancing (e.g., 668A of FIG. 6M) the cumulative representation of the second user activity data for the period in accordance with a determination that the second value exceeds the first value.

[0247] In some embodiments, the representation may be normalized.

[0248] In some examples, the representation may be based on a percentage of completion of one or more goals. Optionally, the one or more goals are user-defined.

[0249] In some examples, the first user activity data corresponds to the first user and the second user activity data corresponds to the second user. In such examples, the device displays a competition completion user interface (e.g., an interface showing details of a previously completed competition) (e.g., 680 in FIG. 6P) before displaying a user interface (e.g., 664 in FIG. 6M, 697 in FIG. 6T). The competition completion user interface can include a representation of the first user's activity data for a previous period (e.g., Monday through Sunday in FIG. 6P) (e.g., the graph portion of Aled in FIG. 6P), a representation of the second user's activity data for the previous period (e.g., the graph portion of Molly in FIG. 6P), and an affordance to start a new competition (e.g., 684C in FIG. 6P). The competition completion user interface can also include content (e.g., text at the top of 680 in FIG. 6P) based on whether the first user or the second user had more activity data for the previous period. In such an embodiment, the device receives a first user input (e.g., 611 on the other device in FIG. 6P) corresponding to a selection of a start affordance for a new competition, and in response to receiving the first user input, initiates processing of the activity competition between the first user and the second user (e.g., sends an invitation to the second user to accept / start a competition between the first user and the second user). In such an embodiment, a user interface is displayed after initiating processing of the activity competition between the first user and the second user (e.g., in response to the second user accepting the invitation to start the competition). Providing different entry points for the activity competition increases interaction with the device by allowing the activity competition to be started in an intuitive manner and at multiple locations. Providing entry points as described herein increases user participation in the activity competition, improves device usability, and provides a more efficient user-device interface (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which further reduces power usage and improves device battery life by allowing the user to use the device more quickly and efficiently.

[0250] In some examples, while displaying the user interface, the device receives a second user input corresponding to a request to display additional information corresponding to the first user activity data and / or the second user activity data. In such examples, in response to receiving the second user input, the device displays a second user interface including the additional information corresponding to the first user activity data and / or the second user activity data. In such examples, the additional information was not included in the user interface. In some examples, the additional information includes contact information, daily averages, actual point counts corresponding to the activity data for a particular day, etc. In some examples, the additional information feature occurs when the affordance is included in an alert rather than a notification, and the alert must be dismissed before using the device to view other content, but the notification is available to the user for viewing in the background.

[0251] In some examples, while displaying the user interface, the device receives a third user input corresponding to a request to display a message user interface (e.g., 646 of FIG. 6I) for sending a message to an external device (e.g., 600A of FIG. 6I). In such examples, in response to receiving the third user input, the device displays the message user interface. In some examples, the message interface function occurs when an affordance is included in a notification rather than an alert. In some examples, the message user interface includes one or more predefined responses (e.g., 648 of FIG. 6I).

[0252] In some examples, in response to user input at a location corresponding to the representation, the device displays a message user interface (e.g., 646 in FIG. 6I). In other examples, in response to user input at a location corresponding to the representation, the device displays additional information of the second user corresponding to the second user activity data.

[0253] In some embodiments, the first user activity data includes standing data, movement data, and workout data.

[0254] In some embodiments, the first user activity data corresponds to a first user and the second user activity data corresponds to a second user, in such embodiments, the user interface can further include a representation (e.g., 668A of FIG. 6M ) based on a comparison of the activity data of the first and second users for one or more previous time periods preceding the time period.

[0255] It should be noted that the process details described above with respect to method 700 (e.g., FIGS. 7A and 7B) are applicable in a similar manner to the methods described below. For example, method 700 optionally includes one or more features of the various methods described below with reference to method 900, method 1100, or method 1300. For example, the user interface of method 700 can be included in the affordance for the activity competition of method 900. In another example, the user interface of method 700 can be based on the activity data detected based on the alert of method 1100. In another example, the user interface of method 700 can include pace information detected based on the pace configured as described in method 1300. For the sake of brevity, these details will not be repeated below.

[0256] 8A-8Y show example user interfaces related to friends lists for activity sharing, according to some embodiments. Activity sharing can include representations regarding activity competitions (as described above in FIGS. 6A-6T and 7A-7B). Friends lists can also include affordances for initiating activity competitions in an intuitive manner, as described further below.

[0257] With reference to Figure 8A, a user interface 804 (called a home screen) is displayed on a touch-sensitive display 802 of a device 800. For purposes of illustration, the device 800 belongs to a first user, Aled. The user interface 804 includes a number of affordances 806 for various applications, including an affordance 806A for an activity application. In Figure 8B, the device 800 receives a selection of affordance 806A and, in response, causes a user interface corresponding to the activity application (e.g., user interface 808 as shown in Figure 8C) to be displayed.

[0258] With reference to Figure 8C, user interface 808 includes affordance 810D for displaying a user interface corresponding to the shared activity data. As shown in Figure 8C, affordance 810D includes an indication that three notifications are pending that are related to the user interface corresponding to the shared activity data. In Figure 8D, device 800 receives a selection of affordance 810D and, in response, causes a user interface corresponding to the shared activity data (e.g., user interface 812 as shown in Figure 8E).

[0259] 8E illustrates the device 800 displaying a user interface 812 (sometimes referred to as a friends list). The user interface 812 includes a first portion 814A relating to information related to the activity competition and a second portion 814B relating to information related to friends.

[0260] 8E, first portion 814A is above second portion 814B such that first portion 814A appears before second portion 814B (as the interface is scrolled). Displaying first portion 814A in front of second portion 814B may affect what is displayed if first portion 814A and second portion 814B contain too much content to be displayed on touch-sensitive display 802. For example, if first portion 814A is in front of second portion 814B of user interface 812, first portion 814A will be displayed in its entirety in front of either second portion 814B. In such an embodiment, content not included in touch-sensitive display 802 may be displayed in response to a scroll input.

[0261] First portion 812 includes a scrollable list of affordances 816, each affordance associated with a different activity competition. For example, the scrollable list of affordances 816 includes a first affordance 816A for a first activity competition (between Molly and Aled) and a second affordance 816B for a second activity competition (between John and Aled). In some examples, the order of affordances for an activity competition may be based on when the activity competition ends. For example, activity competitions that end earlier may be included in the scrollable list of affordances 816 before activity competitions that end later.

[0262] The first affordance 816A includes information related to the first activity competition, such as the cumulative scores of Molly (i.e., 2303) and Aled (i.e., 2136 labeled "ME"), the number of past activity competitions between Molly and Aled that Molly has won (i.e., 23 times), the number of past activity competitions between Molly and Aled that Aled has won (i.e., 7 times), and the amount of time left in the first activity competition (i.e., 2 days left). The second affordance 616B includes information related to the second activity competition, which may be similar to the information related to the first activity competition described above. Note that in some examples, the scrollable list of affordances 816 can include more or less information than is shown in FIG. 8E, with some affordances including more information than other affordances.

[0263] The second portion 814B includes a scrollable list of affordances 818, each of which is associated with a different friend of the user (e.g., Aled) logged into the device 800. For example, the scrollable list of affordances 818 includes a first affordance 818A for a first friend (i.e., Jane), a second affordance 818B for a second friend (i.e., Molly), and a third affordance 818C for a third friend (i.e., John). Note that in some embodiments, friends included in the second portion 814B can also be included in the activity competition of the first portion 814A. For example, Molly is a participant in the first activity competition (e.g., first affordance 816A) and is included in the scrollable list of affordances 818 (e.g., second affordance 818B). In other embodiments, friends included in the first portion 814A are not included in the second portion 814B.

[0264] Each affordance in the scrollable list of affordances 818 includes information related to the corresponding friend. For example, a first affordance 818A corresponds to Jane and includes an identification of Jane (e.g., "Jane"), the percentage Jane has completed of her goal (e.g., "95%"), the absolute amount Joan has completed relative to the goal amount (e.g., "400 / 450"), and an icon 818AA that visually indicates the amount of the multiple goals Joan has completed.

[0265] User interface 812 further includes a share affordance 820. Selecting the share affordance 820 causes device 800 to display a user interface with share details (e.g., user interface 834 shown in FIG. 8O), as described further below with respect to FIG. 8O. Share affordance 820 includes an indication that three notifications related to the shared data are pending.

[0266] FIG. 8F again illustrates user interface 812 (shown in FIG. 8E). As described above, user interface 810 includes first affordance 816A. Referring to FIG. 8F, a user input (e.g., a tap input) 805 is received by device 800, where the user input 805 corresponds to a selection of first affordance 816A of first portion 814A. Pursuant to a determination that user input 805 is detected at first affordance 816A in the scrollable list of affordances 816, a user interface (e.g., user interface 822 shown in FIG. 8G) having additional information (not included in first affordance 816A) related to the first activity competition is displayed.

[0267] Referring to FIG. 8G, device 800 displays a user interface 822 on touch-sensitive display 802 in response to selection of a first affordance 816A in first portion 814A (shown in FIG. 8F). User interface 822 includes multiple representations 824 of information related to the first activity competition. For example, representation 824A is a visual representation of Molly's most recent completion of the day's activity goal. This visual representation includes three circles, each circle corresponding to a different goal. Representation 824B includes information related to the first activity competition, as described above in FIG. 6T. Representation 824C includes a current state (e.g., 50 / 500) of Molly's progress in completing the first goal (e.g., a travel goal). Representation 824D includes a current state of Molly's progress in completing the second goal (e.g., a training goal). It should be appreciated that user interface 816 may include more or fewer representations of information related to the first activity competition than those shown in FIG. 8G.

[0268] User interface 822 also includes a back affordance 826 that causes a previous user interface (e.g., user interface 812 shown in FIG. 8E) to be displayed. With reference to FIG. 8H, a user input (e.g., a tap input) 807 corresponding to a selection of back affordance 826 is received. Pursuant to a determination that user input 807 is detected at back affordance 826, a user interface (e.g., user interface 812 shown in FIG. 8I) is displayed.

[0269] FIG 8I illustrates device 800 displaying user interface 812 in response to selection of back affordance 826 (shown in FIG 8H). As described above, user interface 812 includes first affordance 818A in second portion 814B. Referring to FIG 8J, user input (e.g., tap input) 809 corresponding to selection of first affordance 818A is received. Pursuant to a determination that user input 809 is detected at first affordance 818A, a user interface (e.g., user interface 812 shown in FIG 8I) having information related to the friend (e.g., Jane) corresponding to first affordance 818A is displayed.

[0270] Referring to FIG. 8K, device 800 displays user interface 828 on touch-sensitive display 802 in response to selection of first affordance 818A of second portion 814B (as shown in FIG. 8J). User interface 828 includes multiple representations 830 of information related to Jane. For example, representation 830A is a visual representation of Jane's most recent completion of today's activity goals. The visual representation includes three circles, each circle corresponding to a different goal. Representation 830B includes information related to past activity competitions between Jane and Aled. For example, icon 830BA indicates the number of past activity competitions that Jane won against Aled (e.g., "ME") (e.g., 7), and icon 830BB indicates the number of past activity competitions that Aled won against Jane (e.g., 2). Representation 830C includes a current state (e.g., 400 / 500) of Jane's completion of the first goal (e.g., a movement goal).

[0271] User interface 828 also includes an invitation affordance 831 that initiates a process to start an activity competition between Jane and Ard. For purposes of illustration, selection of invitation affordance 831 may cause user interface 616 (as shown in FIG. 6C) or user interface 686 (as shown in FIG. 6Q) to be displayed on touch-sensitive display 802.

[0272] With reference to Figure 8K, user interface 828 also includes a back affordance 832 that causes a previous user interface (e.g., user interface 812 shown in Figure 8J) to be displayed. With reference to Figure 8L, user input (e.g., a tap input) 811 corresponding to a selection of back affordance 832 is received. Pursuant to a determination that user input 811 is detected at back affordance 832, a user interface (e.g., user interface 812 shown in Figure 8M) is displayed.

[0273] Figure 8M illustrates device 800 displaying a user interface 812 in response to a selection of back affordance 832 (shown in Figure 8L). As described above, user interface 812 includes a shared affordance 820. With reference to Figure 8N, a user input (e.g., a tap input) 813 corresponding to a selection of shared affordance 820 is received. Pursuant to a determination that user input 813 has been detected at shared affordance 820, a user interface (e.g., user interface 834 shown in Figure 8O) is displayed.

[0274] 8O, in response to selection of shared affordance 820 (shown in FIG. 8N), device 800 displays a user interface 834 on touch-sensitive display 802. User interface 834 is divided into multiple portions (e.g., first portion 836 and second portion 838), each portion including a different type of information.

[0275] First portion 836 includes information related to an activity competition invitation received by device 800. For example, first portion 836 includes invitation 836A. Invitation 836A indicates that Tom has sent an invitation to start an activity competition to Aled (e.g., one or more devices (e.g., device 800) associated with Aled). Invitation 836A includes an acceptance affordance and a rejection affordance for responding to the invitation from Tom. Selecting the acceptance affordance initiates a process to start an activity competition between Tom and Aled. Selecting the rejection affordance removes invitation 836A from first portion 836.

[0276] Second portion 838 includes information related to activity competition invitations sent by device 800. For example, second portion 838 includes invitation 838A. Invitation 838A indicates that Aled has sent an invitation to Jane to start an activity competition. Invitation 838A includes a representation of the amount of time remaining for Jane to accept the invitation.

[0277] 8P shows device 600B (e.g., a second device associated with the same user, Aled) displaying user interface 840 on touch-sensitive display 602B. User interface 840, like user interface 812 (as shown in FIG. 8E), corresponds to a friends list. However, unlike user interface 812, user interface 840 is configured to be used on an electronic device having a smaller display area than device 800.

[0278] Similar to user interface 812, user interface 830 includes a first portion 842A and a second portion 842B. As shown in FIG. 8P, first portion 842A is above second portion 842B such that first portion 842A is displayed in front of second portion 842B. Displaying first portion 842A in front of second portion 842B may affect what is displayed if first portion 842A and second portion 842B contain too much content to be displayed on touch-sensitive display 602B. For example, if first portion 842A is in front of second portion 842B of user interface 812, first portion 842A will be displayed in its entirety in front of either second portion 842B. In such an embodiment, content not included in touch-sensitive display 802 may be displayed in response to a scroll input (e.g., rotation of rotatable input mechanism 604A).

[0279] 8P, a first portion 842A includes a scrollable list of affordances 844, where each affordance is associated with a different activity competition. For example, the scrollable list of affordances 844 includes a first affordance 844A for a first activity competition (between Molly and Aled) and a second affordance 816B for a second activity competition (between John and Aled). In some examples, the order of affordances for an activity competition may be based on when the activity competition ends. For example, activity competitions that end earlier may be included in the scrollable list of affordances 844 before activity competitions that end later.

[0280] The first affordance 844A includes information related to the first activity competition, such as the cumulative scores of Molly (i.e., 2303) and Aled (i.e., 2136), the number of past activity competitions between Molly and Aled that Molly has won (i.e., 23 times), the number of past activity competitions between Molly and Aled that Aled has won (i.e., 7 times), and the amount of time left in the first activity competition (i.e., 2 days remaining). The second affordance 616B includes information related to the second activity competition, which may be similar to the information related to the first activity competition described above. Note that in some examples, the scrollable list of affordances 816 can include more or less information than that shown in FIG. 8E, with some affordances including more information than other affordances.

[0281] Also, although user interface 840 is shown as having the same information as first portion 814A of user interface 812, the arrangement of the information in user interface 840 differs from the arrangement of the information in user interface 812. The difference in arrangement may be due to touch-sensitive display 602B having a smaller display area than touch-sensitive display 802.

[0282] The second portion 842B includes a scrollable list of affordances 846, each associated with a respective friend of the user (e.g., Aled) logged into the device 800. For example, the scrollable list of affordances 846 includes a first affordance 846A for a first friend (i.e., Jane), a second affordance 846B for a second friend (i.e., Molly), a third affordance 846C for a third friend (i.e., John), and a fourth affordance 846D for a fourth friend (i.e., Tom). Note that in some embodiments, the friends included in the second portion 842B can also be included in the activity competition of the first portion 842A. For example, Molly is a participant in the first activity competition (e.g., first affordance 842A) and is included in the scrollable list of affordances 846 (e.g., second affordance 846B). In other embodiments, the friends included in the first portion 842A are not included in the second portion 842B.

[0283] Each affordance in the scrollable list of affordances 846 includes information related to the corresponding friend. For example, a first affordance 846A corresponds to Jane and includes an identification of Jane (e.g., "Jane"), the percentage Jane has completed of her goal (e.g., "95%"), the absolute amount Joan has completed relative to the goal amount (e.g., "400 / 450"), and an icon that visually indicates the amount of the multiple goals Joan has completed.

[0284] FIG. 8P shows some information about the friends that is not shown in FIG. 8E. Such information may be included in FIG. 8E. For example, second affordance 846B in second portion 842B includes icon 846BA. Icon 846BA indicates that Aled won the activity competition between Aled and Molly. Icon 846BA may be a unique identification of the activity competition between Aled and Molly, such that other icons for other activity competitions between other participants have different themes (as shown for icon 846CA).

[0285] 8P also shows an invitation icon 842 included in a third affordance 846D within the second portion 842B. The invitation icon 842 indicates that a friend (e.g., Tom) corresponding to the third affordance 846D has sent an invitation to compete in an activity competition with Aled. The invitation icon 842 also includes a number indicating how many invitations from Tom have been received.

[0286] Figure 8Q again shows user interface 840 (illustrated in Figure 8P). As described above, user interface 810 includes a fourth affordance 846D having an invitation icon 842. With reference to Figure 8Q, a user input (e.g., a tap input) 815 is received, which corresponds to a selection of either the invitation icon 842 or the fourth affordance 846D (depending on how user interface 840 is configured). Pursuant to a determination that user input 815 has been detected at the invitation icon 842 (or the fourth affordance 846D), a user interface (e.g., user interface 848 shown in Figure 8R) is displayed.

[0287] Referring to FIG. 8R, device 800 displays user interface 848 in response to selection of invitation icon 842 (or fourth affordance 846D) (as shown in FIG. 8Q). User interface 848 indicates that Tom has invited Aled to a seven-day activity competition. User interface 848 includes Tom's activity data for the current day. User interface 848 further comprises a scrollable list of affordances 850, each of which is associated with a respective action. For example, scrollable list of affordances 850 includes first affordance 850A and second affordance 850B.

[0288] Selecting the first affordance 850A may accept the activity competition invitation sent by Tom. Accepting the invitation may start the activity competition at a predetermined time after the selection (e.g., midnight that day), as described further below. Selecting the second affordance 850B may cause the device 600B to decline the invitation (e.g., not start a new activity competition) and stop displaying the user interface 848. Selecting the second affordance 850B may also remove the invitation icon 842 from the fourth affordance 846D.

[0289] Figure 8S again illustrates user interface 848 (shown in Figure 8R). As described above, user interface 810 includes first affordance 850A. With reference to Figure 8S, a user input (e.g., a tap input) 817 corresponding to a selection of first affordance 850A is received. Pursuant to a determination that user input 817 is detected at first affordance 850A, a user interface (e.g., user interface 852 shown in Figure 8T) is displayed.

[0290] Referring to FIG. 8T, device 600B displays user interface 852 in response to selection of a first affordance 850A in user interface 848 (as shown in FIG. 8S). User interface 852 indicates that an activity competition between Tom and Aled starts tomorrow. User interface 852 includes an icon 854 that represents the activity competition between Tom and Aled. The user interface also includes affordance 856. Selection of affordance 856 causes device 600B to stop displaying user interface 852.

[0291] Figure 8U shows user interface 808 (shown in Figure 8C) again. User interface 810 includes a third affordance 810C. In response to selection of the third affordance 810C (as shown in Figure 8V), device 800 displays user interface 858 (as shown in Figure 8W).

[0292] 8W, user interface 858 (sometimes referred to as a trophy case) is related to the awards given to Aled. User interface 858 is divided into multiple sections 860, each section containing a different type of award. For example, section 860 includes Recent Activity 860A, Competitions 860B, Monthly Challenges 860C, Achievements 860D, and Training 860E.

[0293] Each portion may include one or more prizes associated with a corresponding type of prize. For example, recent activity 860 may include prizes awarded within a certain amount of time from the current time. In some implementations, the prizes in recent activity 860 may be greater than the prizes in other portions. Competition 860B may include prizes awarded in activity competitions. Monthly Challenge 860C may include prizes pre-determined for monthly challenges. Achievements 860D may include prizes pre-determined for achievements. Training 860E may include prizes awarded using a training application (described herein).

[0294] In some embodiments, some prizes in a section may not be visible, in which case these prizes may be navigated by side-scrolling through them.

[0295] The display of the prize in user interface 858 may differ based on the particular prize. For example, a representation of a prize received only once on a particular day may include an icon (e.g., icon 862A), an identification of the prize (e.g., identification 862B), and the date the prize was received (e.g., date 862C). In some embodiments, a representation of a prize received only once on a particular day may include an icon (e.g., icon 862A), an identification of the prize (e.g., identification 862B), and further information related to the achievement of the prize, such as the number of calories burned that met the minimum amount for the prize (e.g., calories 872C). In such embodiments, the date the prize was received may not be included in the representation, since the identification described above indicates a date.

[0296] In another embodiment, the representation of a prize that has been received multiple times may include an icon (e.g., icon 864A or 866A), an identification of the prize (e.g., identification 864B or 866B), and the number of times the prize has been received (e.g., number 864D or 866C). In some embodiments, the representation of a prize that has been received multiple times may also include the date the prize was last received (e.g., date 864C). In such embodiments, the representation may also include a date on which the prize was previously determined to be difficult to receive or a date on which the prize was received less than a certain number of times.

[0297] Note that each icon for each prize in competition 860B (e.g., icons 866A, 868A, and 870A) is different because each activity competition is assigned a different representation, as described herein.

[0298] Fig. 8X shows again the user interface 858 (illustrated in Fig. 8W). The user interface 810 includes an icon 866A of the representation 866. In response to the selection of the icon 866A (or the representation 866) (as shown in representation 8X), the device 800 displays a user interface 876 (as shown in Fig. 8X). With reference to Fig. 8X, the user interface 876 includes the icon 866A (as shown in Fig. 8W), the award identification 873B corresponding to the icon 878 (corresponding to the identification 866B), and further information not included in the representation 866 (as shown in Fig. 8W). This further information includes a description of the award (see reference numeral 878C) and the date of the last award (reference numeral 878D).

[0299] 9A and 9B include a flow diagram illustrating a method for displaying a friends list representation using an electronic device, according to some embodiments. Method 900 is performed on a device having a display (e.g., 100, 300, 500, 600A, 600B, 800). Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0300] As described below, the method 900 provides an intuitive way to display a user interface on a device corresponding to a first user, the user interface including affordances for multiple activity competitions, each activity competition being (1) between the first user and another user and (2) represented by a current score of the activity competition and the number of days remaining in the activity competition. The user interface allows a user viewing the user interface to easily access physical activity data corresponding to multiple users. This method reduces the cognitive burden on the user to access physical activity data corresponding to multiple users, thereby resulting in a more efficient human-machine interface. In a battery-powered computing device, power is conserved and the time between battery charges is increased by allowing a user to access physical activity data corresponding to multiple users more quickly and efficiently.

[0301] At 902, a device (e.g., 800 in FIG. 8A ) receives first user (e.g., Aled) activity data (e.g., data of FIG. 8C depicted in FIG. 8C ), where the first user activity data corresponds to a first time period (e.g., a day, a week, a month, a period of an activity competition between the first user and a second user) (e.g., Monday through Sunday for the activity competition with Molly in FIG. 8I ) and a second time period (e.g., a day, a week, a month, a period of an activity competition between the first user and a user that is different from the first time period) (e.g., Thursday through Wednesday for the activity competition with John in FIG. 8I ). In some examples, the first user activity data is received by one or more sensors of the device.

[0302] In some embodiments, the length of the first time period (e.g., 7 days for the activity competition with Molly in FIG. 8I) is the same as the length of the second time period (e.g., 7 days for the activity competition with John in FIG. 8I). In some embodiments, the length of the first time period is different from the length of the second time period. In some embodiments, the first time period and the second time period overlap (e.g., the activity competition with Molly and the activity competition with John in FIG. 8I).

[0303] At 904, a device (e.g., 800 of FIG. 8A) receives second user activity data (e.g., data represented by a representation for Molly in FIG. 8H) related to a second user (e.g., Molly in FIG. 8I), where the second user activity data corresponds to a first time period that includes a first (e.g., completed) elapsed subperiod (e.g., Monday through Friday in FIG. 8H) and a first (e.g., remaining) unexpired subperiod (e.g., Saturday through Sunday in FIG. 8H) related to an activity competition (e.g., FIG. 8H) between the first and second users. In some embodiments, the second user activity data is received by the device (e.g., by one or more antennas of the device) from a second device (e.g., a device associated with Molly).

[0304] At 906, a device (e.g., 800 in FIG. 8A) receives third user activity data (e.g., data represented by a representation for John in FIG. 8I) related to a third user (e.g., John in FIG. 8I), where the third user activity data corresponds to a second time period, the second time period including a second elapsed subperiod (e.g., from Thursday to Friday in FIG. 8I) and a second (e.g., remaining) unelapsed subperiod (e.g., from Saturday to Wednesday in FIG. 8I) related to an activity competition between the first user and the third user (e.g., an activity competition with John in FIG. 8I). In some examples, the third user activity data is received by the device (e.g., by one or more antennas of the device) from a third electronic device (e.g., a device associated with John).

[0305] In some embodiments, the activity competition between the first user and the second user begins at a first time (e.g., Monday in FIG. 8I), and the activity competition between the first user and the third user begins at a second time (Thursday in FIG. 8I) that is different from the first time.

[0306] At 908, the device (e.g., 800 of FIG. 8A) displays a user interface (e.g., 812 of FIG. 8E) on a display (e.g., 802 of FIG. 8A). In some implementations, the user interface relates to a friends list.

[0307] At 910, a user interface (e.g., 812 of FIG. 8E) includes a representation of first user activity data and second user activity data (e.g., 816A of FIG. 8E) during a first elapsed subperiod of an activity competition between a first user and a second user. In some embodiments, the representation of the first activity data and the second activity data is a score for each of the first user and the second user.

[0308] At 912, the user interface (e.g., 812 in FIG. 8E) includes an indication of an amount of time for a first unexpired subperiod (e.g., 816A in FIG. 8E having “2 days left”) for the activity competition between the first user and the second user. In some embodiments, the indication is an amount of time remaining in the activity competition.

[0309] At 914, the user interface (e.g., 812 of FIG. 8E) includes a representation of the first and third activity data (e.g., 816B of FIG. 8E) for a second elapsed subperiod for the activity competition between the first and third users. In some examples, the representation of the first and third activity data is a score for each of the first and third users. Displaying information about the multiple competitions provides feedback on the activity data being received by the device for the multiple different users. Providing improved feedback increases user participation in the activity competition, improves device usability, and provides a more efficient user-device interface (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), thereby allowing the user to use the device more quickly and efficiently, further reducing power usage and improving the device's battery life. The information about the multiple activity competitions also provides an improved man-machine interface by reducing the number of interactions to display the information for the different activity competitions.

[0310] At 916, the user interface (e.g., 812 in FIG. 8E) includes an indication of the amount of time for the second unexpired subperiod (e.g., 816B in FIG. 8E having “5 days remaining”) for the activity competition between the first user and the third user. Displaying the time remaining in the activity competition provides feedback for future received activity data. Providing improved feedback increases user participation in the activity competition, improves device usability, and provides a more efficient user-device interface (e.g., by helping the user provide proper inputs and reducing user errors when operating / interacting with the device), thereby allowing the user to use the device more quickly and efficiently, further reducing power usage and improving device battery life. The remaining time also provides an improved man-machine interface by increasing the amount of sustained interaction with the device based on the amount of remaining time.

[0311] In some examples, the user interface (e.g., 812 in FIG. 8E) further includes (1) a first portion (e.g., 814A in FIG. 8E) including a representation and display, and (2) a second portion (e.g., 814B in FIG. 8E) visually different from the first portion, the second portion further includes (1) a first affordance (e.g., 818A in FIG. 8E) having an identity of a second user (e.g., “Jane” in FIG. 8E), (2) a second affordance (e.g., 818B in FIG. 8E) having an identity of a third user (e.g., “Molly” in FIG. 8E), and (3) a third affordance (e.g., 818C in FIG. 8E) having an identity of a fourth user (e.g., “John” in FIG. 8E) who is not participating in an active activity competition with the first user. By displaying the competing friends different from the non-competing friends, feedback on the data received by the device (e.g., the location of the data) is provided. Providing improved feedback may increase user participation in activity competitions, improve usability of the device, and provide a more efficient user-device interface (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), thereby allowing the user to use the device more quickly and efficiently, further reducing power usage and improving battery life of the device. By displaying a first set of friends that is different from a second set of friends, emphasizing one set of friends over another, an improved man-machine interface is also obtained.

[0312] In some examples, the third affordance includes a notification (e.g., 842 in FIG. 8P) that the fourth user has requested to start an activity competition between the first user and the fourth user. In such examples, the device receives a first user input (e.g., 815 in FIG. 8Q) corresponding to a selection of the third affordance. In response to receiving the first user input, the device initiates a process to start an activity competition between the first user and the fourth user, where the activity competition between the first user and the fourth user receives first user activity data and fourth user activity data during a period of time (e.g., seven days from when the activity competition between Tom and Aled is started). Displaying additional entry points for the activity competition next to the friend's name in the friend list provides feedback for the pending request from the user in an intuitive place. Providing improved feedback may increase user participation in activity competitions, improve usability of the device, and provide a more efficient user-device interface (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), thereby allowing the user to use the device more quickly and efficiently, further reducing power usage and improving the device's battery life.

[0313] In some examples, the notification is removed from the third affordance after a certain amount of time (e.g., 48 hours) has elapsed since the fourth user sent a corresponding request to initiate an activity competition between the first user and the fourth user.

[0314] In some examples, while displaying a user interface (e.g., 812 of FIG. 8E), the device (e.g., 800 of FIG. 8A) receives a second user input (e.g., input corresponding to a representation of the first user activity data and the second user activity data) (e.g., 805 of FIG. 8F) corresponding to a request to display additional information related to the activity competition between the first user and the second user. In response to receiving the second user input, the device displays a second user interface (e.g., 822 of FIG. 8G) that includes the additional information. In some examples, this additional information includes (1) a representation of the first user activity data during a portion of the first elapsed subperiod related to the activity competition between the first user and the second user (e.g., “Me” of FIG. 8E), and (2) a representation of the second user activity data during a portion of the first elapsed subperiod related to the activity competition between the first user and the second user (e.g., 824B of FIG. 8G).

[0315] In some examples, the representation of the first user activity data and the second user activity data includes an identification of the first user (e.g., "Me" in FIG. 8E), an identification of the second user (e.g., "Molly" in FIG. 8E), and a representation based on a comparison of activity data of the first user and the second user for one or more prior time periods preceding the time period (a time period (e.g., "23" at 816A in FIG. 8E).

[0316] In some examples, the third affordance (e.g., 846C in FIG. 8P) includes a first icon (e.g., a graphic element) (e.g., 846CA in FIG. 8P) indicating a previous (e.g., assigned) activity competition between the first user and the fourth user.

[0317] In some examples, selecting the fourth affordance (e.g., 809 in FIG. 8J) causes a user interface (e.g., 828 in FIG. 8K) to be displayed having a representation (e.g., 830BA in FIG. 8K) indicating a previous activity competition between the first user and the fourth user.

[0318] In some examples, the second affordance includes a second icon indicating a previous active competition between the first user and a third user, where the first icon has a first visual theme (e.g., a shape, background color, or pattern), and the second icon with the second visual theme is different from the first visual theme. In some examples, the two graphical representations may differ in non-thematic visual elements (e.g., numbers or initials that are not part of the visual theme), but share a common visual theme. In some examples, a unique visual theme is assigned to each other user (e.g., second user, third user) who has competed or is currently competing with the user of the electronic device (e.g., first user).

[0319] In some embodiments, the icons for different activity competitions between the same two participants are the same.

[0320] In some examples, while displaying the user interface, a third user input (e.g., 819 of FIG. 8V) is received corresponding to a request to display an awards user interface (e.g., 858 of FIG. 8W). In response to receiving the third user input, the device displays on the display a third user interface (e.g., 858 of FIG. 8W) comprising a first portion (e.g., 858 of FIG. 8W) corresponding to a first type of icon, the first type of icon being associated with an activity competition, the first portion including a first icon (e.g., 866A of FIG. 8W) and a second icon (e.g., 868A of FIG. 8W), and a second portion (e.g., 860E of FIG. 8W) corresponding to a second type of icon, the second portion including a third icon (e.g., the star icon of FIG. 8W). In some examples, the third user interface is a trophy case. In some examples, the first portion includes an icon associated with the activity competition. In some examples, the second portion includes an icon associated with training. In some examples, the third user interface further includes a third portion corresponding to recently received icons, and the icons included in the third portion (e.g., 860A in FIG. 8W) are visually different (e.g., larger) than the icons in the other portions. In some examples, some of the icons are configured to be side-scrolled.

[0321] In some examples, the third user interface for an icon included in the third user interface (e.g., 864 in FIG. 8W) includes one or more of the following adjacent to the icon: an identity of the icon (e.g., 864B in FIG. 8W), and a number of times the icon has been acquired (e.g., 864D in FIG. 8W).

[0322] In some examples, the device receives a fourth user input (e.g., 815 in FIG. 8Q) corresponding to a selection of the third affordance. In response to receiving the fourth user input, the device displays a third user interface (e.g., 848 in FIG. 8R) including a start competition affordance (e.g., 850A in FIG. 8R). The device receives a fifth user input (e.g., 817 in FIG. 8S) corresponding to the start competition affordance. In response to receiving the fifth user input, the device starts an activity competition between the first user and the fourth user, and first user activity data and fourth user activity data during a third time period are received by the activity competition between the first user and the fourth user.

[0323] In some embodiments, the representation of the first user activity data and the second user activity data during a first elapsed subperiod for an activity competition between a first user and a second user is based on a two-tiered scoring system in which scores change (e.g., bonus points) when users reach a threshold.

[0324] In some examples, while displaying the user interface, the device receives a sixth user input using a rotatable input mechanism (e.g., an input mechanism that can rotate relative to a housing of the device) of the device (e.g., 604A of FIG. 8P). In response to receiving the sixth user input, the device updates the user interface to display a fourth affordance for the fifth user, where the fourth affordance was not visible prior to receiving the sixth user input.

[0325] It should be noted that the process details described above with respect to method 900 (e.g., FIGS. 9A and 9B) are also applicable in methods similar to those described below / above. For example, method 900 optionally includes one or more features of the various methods described below with reference to method 700, method 1100, or method 1300. For example, the user interface of method 900 can lead to the user interface of method 700 (e.g., by selecting an affordance of the first portion). In another example, the user interface of method 1100 can generate the activity data represented in the user interface of method 900. In another example, the user interface of method 1300 can generate the activity data represented in the user interface of method 900. For the sake of brevity, these details are not repeated below.

[0326] 10A-10Q show example user interfaces associated with alerts presented to a user in response to automatically determining workout boundaries, according to some embodiments. For example, FIG. 10A shows an alert presented in response to automatically determining the start of a workout, and FIG. 10D shows an alert presented in response to automatically determining the end of a workout. Such alerts reduce the need for a user to remember to start and / or end a workout. The user interfaces of these figures are used to explain the processes described below, including the process of FIG. 11.

[0327] 10A , a user interface 1004 of a training application is displayed on a touch-sensitive display 602A of the device 600A. In some examples, the user interface 1004 is displayed in response to a determination that the user-worn device 600A has begun an outdoor run. This determination may be based on data detected by one or more sensors associated with the device 600A. For example, the device 600A may include or be paired with a heart rate monitor and a GPS sensor. In response to heart rate information detected by the heart rate monitor and GPS information detected by the GPS sensor, the device 600A (or a device connected to the device 600A) may determine that the user is likely running outside.

[0328] The user interface 1004 includes a scrollable list of affordances 1006, each of which is associated with a respective action. For example, the scrollable list of affordances 1006 includes a start affordance 1006A, a change affordance 1006B, and a dismiss affordance 1006C. The start affordance 1006A activates a physical activity tracking feature configured for an outdoor run. The change affordance 1006B allows the user to select a different type of workout to activate a body tracking feature configured for the different type of workout. The dismiss affordance 1006C causes the user interface 1004 to stop displaying.

[0329] The user interface 1004 further includes a physical activity icon 1008 that corresponds to outdoor running. The physical activity icon 1008 is an icon of a runner. In various embodiments, the physical activity icon 1008 is displayed in an animated state, as further shown in FIG. 10I.

[0330] In some examples, the content included in user interface 1004 may not fit within touch-sensitive display 602A. In this case, the content that is not displayed may be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism 604A).

[0331] In some examples, the alert (e.g., user interface 1004) is reissued (e.g., redisplayed or a new alert corresponding to the alert is displayed) after a certain amount of time (e.g., a predetermined time) has passed without the user dismissing the alert (e.g., by selecting an affordance in the scrollable list of affordances 1006). For example, if the user does not select an affordance in the scrollable list of affordances 1006 within three minutes, a new user interface that is the same or similar to user interface 1004 is displayed on touch-sensitive display 602A of device 600A. In some examples, if the user selects an affordance (e.g., dismiss affordance 1006A) within three minutes of user interface 1004 being displayed, user interface 1004 is not reissued after three minutes. Although three minutes is used as an example, it should be appreciated that a different amount of time may be used.

[0332] In some examples, the alert is only reissued when the alert is interrupted (e.g., the user interface 1004 is no longer displayed because of another alert). In some examples, if the alert is not interrupted, the alert remains displayed for a certain amount of time (e.g., remains displayed and / or is displayed whenever the touch-sensitive display 602A transitions from an inactive state to an active state). In some examples, the certain amount of time is based on the type of workout that the alert corresponds to. For example, if the alert corresponds to swimming, the alert may remain displayed for 60 minutes, and if the alert corresponds to running or other types of workouts other than swimming, the alert may remain displayed for 30 minutes. In some examples, a notification corresponding to the user interface 1004 is sent to a notification center so that the user can view the notification after the display of the user interface 1004 has ended.

[0333] In some examples, prior to displaying user interface 1004, user interface 1064 is displayed on the touch-sensitive display 602A of device 600A, as shown in FIG. 10L. In such examples, user interface 1064 is displayed in response to a determination that the user-worn device 600A has begun an outdoor run, and user interface 1004 is displayed after displaying user interface 1064 (e.g., in response to user interface 1004 being displayed for a particular amount of time). In some examples, when user interface 1064 is displayed, user interface 1004 is displayed in response to a determination that a set of one or more "short-look" criteria are met, and user interface 1064 is displayed in response to a determination that one or more "long-look" criteria are met, as described below.

[0334] As shown in FIG. 10L, user interface 1064 includes a physical activity icon 1066 that corresponds to outdoor running. In various embodiments, physical activity icon 1064 is displayed in an animated state, as further shown in FIG. 10I. In some embodiments, content such as physical activity icon 1064 is included in both user interface 1064 and user interface 1004 (referred to as physical activity icon 1008). In such embodiments, user interface 1004 includes additional content not included in user interface 1064, such as scrollable affordance 1006. User interface 1064 further includes text indicating that user interface 1064 is being displayed because the user has been determined to be running (e.g., "it looks like you are running").

[0335] In some examples, the user interface 1064 is displayed in response to detecting a user input within a first period of time following the sensory output (e.g., thereby satisfying a short look criterion). The information in the user interface 1064 can be referred to as a first portion of information. In such examples, after the user raises their wrist to look at the user interface 1064, the user may subsequently wish to view further information associated with the user interface 1064. If the device 600A determines that the user continues to maintain the device 600A in a viewing position for a predetermined period of time (e.g., satisfying a long look criterion) after displaying the user interface 1064, the device 600A displays the user interface 1004, which can be referred to as a second portion of information. That is, in some examples, the device 600A can automatically transition from displaying the user interface 1064 to displaying the user interface 1004 when the user holds the device 600A in a viewing position and waits.

[0336] Figure 10B again illustrates user interface 1004 (as shown in Figure 10A). As described above, user interface 1004 includes start affordance 1006A. With reference to Figure 10B, user input (e.g., a tap input) 1001 corresponding to a selection of start affordance 1006A is received. Pursuant to a determination that user input 1001 is detected at start affordance 1006A in the scrollable list of affordances 1006, a physical activity tracking feature configured for outdoor running is initiated.

[0337] In response to a selection of the start affordance 1006A, a user interface 1026 (shown in FIG. 10C ) is displayed. The user interface 1026 displays data detected by the device 600A related to the outdoor run (e.g., provides feedback regarding the data). In some examples, the displayed data can be based on data detected prior to the selection of the start affordance 1006A and / or prior to the display of the user interface 1004. For example, a preliminary determination can be made that the user is performing an outdoor run. At some point after the preliminary determination, a final determination can be made that the user is performing an outdoor run, which causes the user interface 1004 to be displayed. In such examples, all data from the preliminary determination onward can be used in calculating the data to display in the user interface 1026. In another example, in response to a selection of the start affordance 1006A, it can be determined that an amount of data prior to the selection is likely related to an outdoor run (e.g., above a threshold), and this amount of data is used in calculating the data to display in the user interface 1026.

[0338] To display the data detected by device 600A, user interface 1026 includes representations 1028. In FIG. 10C, representations 1028 include total distance run 1028A (e.g., an indication of the number of miles traveled during the outdoor run), average pace per mile 1028B (e.g., an indication of the average amount of time it took device 600A to travel a mile during the outdoor run), total time 1028C (e.g., an indication of the duration of the outdoor run), and total calories 1028D (e.g., an indication of the amount of calories determined to have been burned by the user during the outdoor run). It should be appreciated that in some embodiments, user interface 1026 may include more or fewer representations.

[0339] The user interface 1026 also includes the current time, a physical activity icon (as described above), or other information determinable by the device 600A. The physical activity icon appearing in the user interface 1026 may be animated. Although FIG. 10C illustrates a particular visual appearance of the representation 1028, it should be appreciated that the representation 1028 may have a different appearance.

[0340] At some point after the workout has begun (e.g., after selection of start affordance 1006A), it may be determined that the user is no longer likely to be running outside (e.g., exceeding a threshold criterion). This determination may be based on similar data described above for starting an outdoor run, such as data detected by one or more sensors associated with device 600A. In response to a determination that the user is no longer likely to be running outside, a user interface 1038 (as shown in FIG. 10D) is displayed on touch-sensitive display 602A.

[0341] The user interface 1038 includes a scrollable list of affordances 1040 associated with various actions. For example, the scrollable list of affordances 1040 includes an end affordance 1040A, a pause affordance 1040B, a change affordance 1040C, and a dismiss affordance 1006D. The end affordance 1040A stops the physical activity tracking function corresponding to the outdoor run, and data generated by the physical tracking function is stored as a previous workout. The pause affordance 1040B pauses the physical activity tracking function corresponding to the outdoor run. The change affordance 1040C allows the user to select different types of workouts, and different physical activity tracking functions corresponding to the different types of workouts may be activated. The dismiss affordance 1006D causes the user interface 1038 to stop displaying, and the physical activity tracking function for the outdoor run continues to run.

[0342] The user interface 1038 further includes a physical activity icon 1042 that corresponds to outdoor running. The physical activity icon 1042 is an icon of a runner. In various embodiments, the physical activity icon 1042 is displayed in a static state.

[0343] In some examples, the content included in user interface 1038 may not fit within touch-sensitive display 602A, in which case the content that is not displayed may be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism 604A).

[0344] 10E, a user input (e.g., a tap input) 1005 corresponding to a selection of an end affordance 1040A is received. In accordance with a determination that the user input 1005 is detected at the end affordance 1040A in the scrollable list of affordances 1040, the physical activity tracking function for the outdoor run is discontinued. That is, based on the selection of the end affordance 1040A, the execution of the physical activity tracking function for the outdoor run is stopped. This selection may save data related to the outdoor run as a previous workout. It should be appreciated that when data is detected, the data related to the outdoor run may be stored.

[0345] 10F, in response to selecting the exit affordance 1040A, a user interface 1044 is displayed. The user interface 1044 allows for feedback regarding data detected by the device 600A regarding the outdoor run. For example, the user interface 1044 includes a representation 1046 of different types of data detected by the device 600A regarding the outdoor run. In FIG. 10F, the representation 1046 includes a total distance run 1046A (e.g., an indication of the number of miles traveled during the outdoor run), an average pace per mile 1046B (e.g., an indication of the average amount of time it took the device 600A to travel a mile during the outdoor run), a total time 1046C (e.g., an indication of the duration of the outdoor run), a total active calories 1046D (e.g., an indication of the amount of calories determined to be consumed by the user-worn device 600A during the outdoor run activity state), and a total calories 1046E (e.g., an indication of the amount of calories determined to be consumed by the user-worn device 600A during the outdoor run). It should be appreciated that in some embodiments, the user interface 1044 may include more or fewer representations.

[0346] User interface 1044 also includes an identification of the outdoor run (e.g., representation 1048), a physical activity icon (e.g., physical activity icon 1050), or other information known by device 600A. Although FIG. 10F illustrates a particular visual appearance of representation 1046, it should be appreciated that these representations may have different appearances.

[0347] FIG. 10G again illustrates the user interface 1004 (as shown in FIG. 10A and under the circumstances described with respect to FIG. 10A). As described above, the user interface 1004 includes a change affordance 1006B. Referring to FIG. 10G, a user input (e.g., a tap input) 1003 corresponding to a selection of the change affordance 1006B is received. In some examples, when selecting to change the type of training, data detected before selecting the change affordance 1006B is not configured to be associated with the new type of training. Unlike what happens (in some examples) when selecting to start a training using the affordance 1006A, for example (data detected before starting a training using the affordance 1006A can be configured to be associated with the training), when changing a training, a new training is started after the new training is selected. In other words, with the start affordance 1006A, data detected before the selection of the start affordance 1006A is used, and with the change affordance 1006B, data detected before the selection of the change affordance 1006B is not used. Pursuant to a determination that user input 1003 is detected at a change affordance 1006B in the scrollable list of affordances 1006, a user interface 1030 shown in FIG. 10H is displayed.

[0348] The user interface 1030 allows the user to select a different type of workout for the current workout. For example, if it is determined that the user is running outdoors, the user can change the outdoor run to a second type of workout, indicating that the determination of the outdoor run was incorrect. Selecting a different type of workout automatically activates a physical activity tracking function corresponding to the different type of workout.

[0349] User interface 1030 includes a scrollable list of affordances 1032 associated with corresponding physical activity tracking features related to physical activity. For example, scrollable list of affordances 1032 includes affordance 1032A (corresponding to a physical activity tracking feature for climbing stairs (called stair climbing)), affordance 1032B (corresponding to a physical activity tracking feature for outdoor running), and affordance 1032C (corresponding to a physical activity tracking feature for walking). Note that scrollable list of affordances 1032 can include additional affordances corresponding to other physical activity tracking features that are not currently displayed but may be displayed in response to a scroll input (e.g., rotation of rotatable input mechanism 604A).

[0350] In some examples, each of one or more affordances in the scrollable list of affordances 1032 includes a representation 1034 that corresponds to a physical activity associated with the affordance. The representation 1034 includes a physical activity icon that corresponds to the physical activity associated with the affordance. For example, affordance 1032A includes a physical activity icon 1034A (e.g., an icon of a person climbing stairs). Similarly, affordance 1032C includes a physical activity icon 1034D (e.g., an icon of a person walking). In various examples, the physical activity icon is displayed in a first state (e.g., a static state).

[0351] Representation 1034 further includes a workout identifier. For example, affordance 1032A includes workout identifier 1034B, indicating that affordance 1032A is associated with a stair climbing workout. Similarly, affordance 1032B includes a workout identifier, indicating that affordance 1032B is associated with an outdoor running workout.

[0352] In some examples, one or more of the affordances in the scrollable list of affordances 1032 include training goal information. For example, affordance 1032A includes training goal information 1034C indicating that the stair climbing workout associated with affordance 1032A has a predefined goal of 20 minutes. That is, when affordance 1032A is selected, the associated physical activity tracking functionality automatically tracks information about the stair climbing workout with a predefined goal of 20 minutes. Affordance 1032B includes a goal training affordance indicating that the outdoor running associated with affordance 1032B is an "open goal." The open goal display indicates to the user that the associated workout does not currently have any predefined goal. Thus, when affordance 1032B is selected, various metrics (which do not include any predefined goal) are tracked by the associated physical activity tracking functionality.

[0353] 10I illustrates a series of states of a device 600A having a touch-sensitive display 602A, which illustrates a user interface 1004 (also shown in FIG. 10A) over time.

[0354] Showing the user interface 1004 over time illustrates how a physical activity icon 1008 may be animated. For example, physical activity icon 1008A illustrates the physical activity icon 1008 in a first state, physical activity icon 1008B illustrates the physical activity icon 1008 in a second state subsequent to the first state, and further, physical activity icon 1008C illustrates the physical activity icon 1008 in a third state subsequent to the second state.

[0355] This animation can give the impression that the person is running. Animating the physical activity icon 1008 can provide feedback to the user that the device 600A has determined (e.g., detected) that a workout has begun.

[0356] 10J and 10K illustrate user interfaces displayed in response to a determination that a different type of training has been initiated. For example, different types of training may be associated with different sets of one or more criteria. When a set of one or more criteria for a particular type of training is met, a user interface for initiating a training corresponding to the particular type of training may be displayed.

[0357] 10J, a user interface 1052 of a training application is displayed on the touch-sensitive display 602A. The user interface 1052 includes a scrollable list of affordances 1054 that is similar (e.g., functions in a similar manner) to the scrollable list of affordances 1006. For example, the scrollable list of affordances 1054 includes a start affordance 1054A (corresponding to a physical activity tracking function for walking). Note that the scrollable list of affordances 1054 may not fit on the touch-sensitive display 602A. In that case, one or more of the hidden affordances may be displayed in response to a scroll input (e.g., rotation of the rotatable input mechanism 604A).

[0358] The user interface 1054 further includes a physical activity icon 1056 that corresponds to the physical activity associated with the start affordance 1054A. The physical activity icon 1056 is an icon of a person walking. In various embodiments, the physical activity icon 1056 is displayed in an animated state.

[0359] 10K, a training application user interface 1058 is displayed on the touch-sensitive display 602A. The user interface 1058 includes a scrollable list of affordances 1060 similar to (e.g., functioning in a similar manner) as the scrollable list of affordances 1006. For example, the scrollable list of affordances 1060 includes a start affordance 1060A (corresponding to a physical activity tracking function for a rowing workout). Note that the scrollable list of affordances 1060 may not fit within the touch-sensitive display 602A. In that case, one or more of the hidden affordances may be displayed in response to a scroll input (e.g., rotation of the rotatable input mechanism 604A).

[0360] The user interface 1058 further includes a physical activity icon 1062 that corresponds to the physical activity associated with the start affordance 1060A. The physical activity icon 1062 is an icon of a person rowing. In various embodiments, the physical activity icon 1062 is displayed in an animated state.

[0361] In some embodiments, instead of displaying user interface 1004, as shown in FIG. 10M, user interface 1068 is displayed. In such embodiments, if a determination is made that there are multiple types of workouts potentially started, user interface 1068 is displayed. User interface 1068 comprises a scrollable list of affordances 1070, each of which is associated with a respective action. For example, the scrollable list of affordances 1070 includes a start outdoor running affordance 1070A, a start indoor running affordance 1070B, a change affordance 1070C, and a release affordance 1070D. The start outdoor running affordance 1070A activates a physical activity tracking feature configured for outdoor running (similar to the start affordance 1006A). The start indoor running affordance 1070B activates a physical activity tracking feature configured for indoor running. The change affordance 1070C allows the user to select a different type of workout and activate the body tracking functionality configured for the different type of workout (similar to the start affordance 1006B). The cancel affordance 1070D causes the user interface 1068 to stop displaying (similar to the start affordance 1006C).

[0362] In some examples, the indoor run start affordance 1070B is associated with a type of workout that is a substitute for the type of workout corresponding to the outdoor run start affordance 1070A (in some examples, the types of workouts are associated when tracking data used for one type can be used for the other type). In such examples, the outdoor run start affordance 1070A is visually highlighted (e.g., a different color and / or a different size) compared to the indoor run start affordance 1070B (and compared to the other affordances 1070C and 1070D). In some examples, the outdoor run start affordance 1070A is visually highlighted because a determination is made based on the sensor data that the user is more likely to be running outdoors than indoors. In some examples, the indoor run start affordance 1070B is not visually highlighted compared to the change affordance 1070C and the reject affordance 1070D. In other words, indoor run start affordance 1070B, change affordance 1070C, and release affordance 1070D may appear similar, while outdoor run start affordance 1070A is visually distinct from all three. Examples of types of workouts that may typically be paired as primary and alternate workouts include outdoor / indoor running, outdoor / indoor walking, and pool / open water swimming. Although only a single alternative is shown in FIG. 10M, it should be appreciated that more than one alternative may be included in the scrollable list of affordances 1070.

[0363] In some examples, after an alert is issued (e.g., user interface 1004), a user interface for selecting to start a workout from a list of workouts (e.g., user interface 1076) includes one or more representations corresponding to the alert, as shown in Figures 10P and 10Q and described below, and such user interfaces can be navigated as shown in Figures 10N-10O and described below.

[0364] 10N illustrates a user interface 1072 displayed on the touch-sensitive display 602A of device 600A. User interface 1072 includes a number of application affordances 1074 associated with applications. For example, affordance 1074A is associated with a voice application, and affordance 1074B is associated with a training application. In some examples, user interface 1072 may be displayed to indicate which applications may be launched using device 600A. Selection of an affordance included in user interface 1072 may launch the corresponding application.

[0365] Figure 10O again illustrates user interface 1072 (shown in Figure 10N). As described above, user interface 1072 includes affordance 1074B. With reference to Figure 10O, user input (e.g., a tap input) 1007 corresponding to a selection of affordance 1074B is received. Pursuant to a determination that user input 1007 is detected at affordance 1074B, a training application corresponding to affordance 1074B is launched and user interface 1076 (described below and shown in Figure 10P) is displayed.

[0366] 10P, user interface 1076 includes a scrollable list of affordances 1078 associated with each physical activity tracking feature for each physical activity. In some examples, the scrollable list of affordances 1078 comprises at least two types of affordances: a first type of affordance and a second type of affordance. The first type of affordances are associated with physical activity tracking features that correspond to alerts issued by device 600A (e.g., user interface 1004), and the second type of affordances (e.g., 1078C) are associated with physical activities that are trackable by device 600A (but do not correspond to alerts issued by device 600A (e.g., 1004)). In some examples, a physical activity is represented in both a first type and a second type, and the scrollable list of affordances 1078 includes (1) a first affordance (of the first type of affordance) associated with the particular type of physical activity, and (2) a second affordance (of a second type of affordance that is different from the first type of affordance) associated with the particular type of physical activity. In other examples, a physical activity represented by a first type of affordance is not represented by a second type of affordance.

[0367] 10P, the scrollable list of affordances 1078 includes a plurality of affordances of a first type of affordance, affordance 1078A (corresponding to continuing a physical activity tracking function for an outdoor run started at 10 a.m.) and affordance 1078B (corresponding to continuing a physical activity tracking function for an indoor run started at 10 a.m.) The scrollable list of affordances 1078 includes a plurality of affordances of the first type of affordance in response to (1) a plurality of different alerts (e.g., user interface 1004) being issued without initiating a physical activity tracking function corresponding to one of the plurality of different alerts or (2) an alert having a plurality of types of workouts (e.g., user interface 1068) being issued without initiating a physical activity tracking function corresponding to one of the plurality of types of workouts.

[0368] Note that user interface 1076 includes a clock indicating that the time is "10:09," such that affordance 1078A represents a workout that began at 10 a.m. This indicates that selecting affordance 1078A will record tracked data from 10 a.m. onward for the current outdoor running workout, even though the user has not indicated that the outdoor running workout should begin at 10 a.m.

[0369] In some examples, the scrollable list of affordances 1078 can include additional affordances that correspond to other physical activity tracking features that are not currently displayed but can be displayed in response to a scroll input (e.g., rotation of the rotatable input mechanism 604A). Figure 10Q shows a user interface 1076 responsive to a scroll input. The user interface 1076 of Figure 10Q again includes a scrollable list of affordances 1078.

[0370] As shown in FIG. 10Q, the scrollable list of affordances 1078 includes an affordance that is a first type of affordance (i.e., affordance 1078B) and a plurality of affordances that are a second type of affordance, including affordance 1078C (corresponding to a physical activity tracking function for stair climbing training) and affordance 1078D (corresponding to a physical activity tracking function for walking). The scrollable list of affordances 1206 is configured such that a type of physical activity may be selected for the current training. In some examples, when an affordance that is a first type of affordance is selected, a training is initiated using data detected before the selection of the affordance. In such examples, when an affordance that is a second type of affordance is selected, a training is initiated that uses data detected before the selection of the affordance (and only data detected after the selection of the affordance). In some examples, the affordances that are the first type of affordances (e.g., affordance 1078A and affordance 1078B) are visually highlighted compared to the affordances that are the second type of affordances (e.g., affordance 1078C and affordance 1078D).

[0371] 11 is a flow diagram illustrating a method for displaying an alert in response to automatically determining physical activity boundaries using an electronic device, according to some embodiments. Method 1100 is performed in a device (e.g., 100, 300, 500, 600A, 600B, 800) that includes a display and one or more sensors (e.g., a gyroscope, a camera, an accelerometer, a GPS sensor, a heart rate monitor, a clock, etc., or any combination thereof). Some operations in method 1100 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0372] As described below, method 1100 provides an intuitive way to display alerts in response to automatically determining physical activity (e.g., workout) boundaries. The method reduces the cognitive burden on the user to start and stop physical activity tracking functionality, thereby resulting in a more efficient human-machine interface. For battery-powered computing devices, allowing users to track activity data more quickly and efficiently conserves power and increases the time between battery charges.

[0373] At 1102, a device (e.g., 600A) detects activity data (e.g., heart rate data, GPS data, movement data, etc.) with one or more sensors (e.g., the data detected to display user interface 1004 in FIG. 10A). In some examples, the one or more sensors used to detect the activity data are a subset of the sensors included in the electronic device (e.g., some sensors are not used to detect the activity data).

[0374] In some examples, the activity data is detected before the physical activity tracking feature (e.g., the tracking feature corresponding to 1026) is activated. In such examples, the activity data is used to determine whether to start the physical activity tracking feature (e.g., a boundary condition is the start of a workout).

[0375] At 1102, in response to detecting the activity data, pursuant to a determination that the activity data meets activity boundary alert criteria (e.g., criteria for classifying the activity data to correspond to boundaries (e.g., start, end, transition from one type of activity to another) of a user's activity (e.g., user workout)), the device (e.g., 600A) displays an activity boundary alert (e.g., a user interface including a confirmation affordance and an indication of the type of activity boundary detected) (e.g., 1004 or 1038). Displaying the activity boundary alert provides feedback to when the device detected an activity boundary. Providing improved feedback and performing an action when a set of conditions are met without requiring further user input improves device usability and provides a more efficient user-device interface (e.g., by helping the user provide appropriate inputs and reducing user mistakes when operating / interacting with the device), thereby allowing the user to use the device more quickly and efficiently, further reducing power usage and improving the device's battery life.

[0376] In some examples, the activity boundary alert (e.g., 1004) includes a first affordance (e.g., 1006A). In such examples, the device (e.g., 600A) receives a first user input (e.g., 1001) corresponding to a selection of the first affordance. In response to receiving the first user input, the device initiates a physical activity (e.g., running, high intensity interface 1026 can display using information from the physical activity tracking functionality) in response to the activity boundary alert (e.g., the physical tracking functionality corresponds to the first affordance). In some examples, the activity boundary alert includes a third affordance (e.g., 1006C). In such examples, upon selection of the third affordance, the device refrains from initiating a physical activity tracking functionality corresponding to the type of physical activity in response to the activity boundary alert. In such examples, the device continues to determine when a workout will begin.

[0377] In some examples, a physical activity tracking feature corresponding to an activity boundary alert (eg, 1004) tracks detected activity data prior to displaying the activity boundary alert.

[0378] In some examples, the activity boundary alert (e.g., 1004) corresponds to a first physical activity tracking function (e.g., an activity tracking function corresponding to a predicted type of activity (e.g., running, swimming, rowing)). In such examples, the activity boundary alert includes a second affordance (e.g., 1006). In such examples, the device receives a second user input (e.g., 1003) corresponding to a selection of the second affordance in the activity boundary alert. In response to receiving the second user input, the device displays a first user interface (e.g., 1030) including a third affordance (e.g., 1032A) corresponding to the second physical activity tracking function different from the first physical activity tracking function and a fourth affordance (e.g., 1032C) corresponding to the third physical activity tracking function different from the first physical activity tracking function. While displaying the first user interface, the device receives the third user input. In accordance with the third user input corresponding to a selection of the third affordance in the first user interface, the device configures the electronic device to track activity data detected after selection of the third affordance using the second physical activity tracking function. In accordance with a third user input corresponding to a selection of a fourth affordance in the second user interface, the device configures the electronic device to track activity data detected after selection of the fourth affordance using a third physical activity tracking functionality. In some examples, the activity boundary alert includes an animated affordance (e.g., FIG. 10I) representing a type of workout associated with the activity boundary alert.

[0379] In some examples, the activity data is detected by a first sensor of the one or more sensors. In such examples, initiating a physical activity tracking feature corresponding to the type of physical activity in response to the activity boundary alert (e.g., the body tracking feature corresponds to the first affordance) includes detecting second activity data by a second sensor different from the first sensor of the one or more sensors (e.g., the first sensor is an accelerometer and the second sensor is a GPS sensor). In some examples, the second sensor is activated from an inactive state.

[0380] In some examples, the activity data is detected while an existing physical activity tracking feature is active (eg, the tracking feature corresponding to 1026).

[0381] In some examples, activity data is detected while an existing physical activity tracking feature is active. For example, the device is already tracking a workout. In such examples, the activity boundary alert (e.g., 1038) includes a fifth affordance (e.g., 1040A). In such examples, the device receives a first fourth input (e.g., 1005) corresponding to a selection of the fifth affordance. In response to receiving the fourth user input, the device terminates the current physical activity tracking feature. Further in response to receiving the fourth user input, the device stores activity data (e.g., including activity data) detected prior to receiving the fourth user input as a previous workout.

[0382] In some examples, the activity boundary alert (e.g., 1038) includes a sixth affordance (e.g., 1040B). In such examples, the device receives a fifth user input corresponding to a selection of the sixth affordance. In response to receiving the fifth user input, the device pauses execution of the physical activity tracking function. In some examples, the activity boundary alert includes a disengagement affordance (e.g., 1040D) for not stopping recording the workout.

[0383] In some examples, the activity boundary alert (e.g., 1038) corresponds to the first physical activity tracking function. In such examples, the activity boundary alert includes a seventh affordance (e.g., 1040C). In such examples, the device receives a sixth user input (e.g., similar to 1003) corresponding to a selection of the seventh affordance. In response to receiving the sixth third input, the device initiates a process to stop execution of the first physical activity tracking function. Further in response to receiving the sixth third input, the device displays a second user interface (e.g., 1030) including an eighth affordance (e.g., 1032A) corresponding to a second physical activity tracking function different from the first physical activity tracking function and a ninth affordance (e.g., 1032C) corresponding to a third physical activity tracking function different from the first physical activity tracking function. In such examples, the device receives the seventh user input. In accordance with the seventh user input corresponding to a selection of the eighth affordance in the second user interface, the device initiates the second physical activity tracking function. In accordance with a seventh user input corresponding to a selection of a ninth affordance in the second user interface, the device initiates a third physical activity tracking function.

[0384] In some examples, the activity boundary alert includes a static affordance that represents a type of workout associated with the activity boundary alert (e.g., the runner icon in FIG. 10G).

[0385] In some examples, a determination that activity data meets the activity boundary alert criteria may be updated over time based on user interactions.

[0386] In some examples, the activity boundary alert (e.g., 1068) includes a tenth affordance (e.g., 1070B) (in some examples, the tenth affordance is an affordance for an alternative type of workout compared to the first affordance (e.g., 1070A)), and the physical activity tracking function corresponding to the activity boundary alert is the first physical activity tracking function. In such examples, the electronic device receives an eighth user input corresponding to a selection of the tenth affordance, and in response to receiving the eighth user input, initiates a second physical activity tracking function corresponding to the activity boundary alert, but the second physical activity tracking function is different from the first physical activity tracking function (in some examples, each of the first physical activity tracking function and the second physical activity tracking function uses activity data in a first manner (e.g., tracking number of miles), while a third physical activity tracking function that does not correspond to the activity boundary alert criteria uses activity data in a second manner that is different from the first manner (e.g., tracking number of laps)).

[0387] In some examples, the first affordance (e.g., 1070A) and the tenth affordance (e.g., 1070B) are ordered based on which corresponding workout is determined to be the type of workout that is more likely to be performed. For example, if it is determined that the user is more likely to be performing outdoor running than indoor running, the affordance associated with outdoor running takes precedence over the affordance associated with indoor running, as shown in FIG.

[0388] In some examples, the first affordance is highlighted relative to the tenth affordance to highlight that the training corresponding to the first affordance has been determined to be more likely to be performed than the training corresponding to the tenth affordance.

[0389] In some embodiments, the activity boundary alert is a first activity boundary alert (e.g., 1064) that includes a first content (in some embodiments, the activity boundary alert is displayed in response to a short look), and after displaying the first activity boundary alert, the electronic device displays a second activity boundary alert (e.g., 1004) that includes a second content (in some embodiments, the second activity boundary alert is displayed in response to a long look), but the second content is different from the first content (e.g., the second content includes the first content and other content) (in some embodiments, the second activity boundary alert is displayed pursuant to a determination that the look criteria have been met).

[0390] At 1106, further responsive to detecting the activity data, in accordance with a determination that the activity data does not meet the activity boundary alert criteria, the device refrains from displaying the activity boundary alert (eg, refrains from displaying 1004).

[0391] In some examples, further responsive to detecting the activity data and in accordance with a determination that the activity data meets the second activity boundary alert criteria, the device displays a second activity boundary alert (e.g., alert 1058), where the activity boundary alert criteria and the activity boundary alert (e.g., alert 1004) are associated with a first type of physical activity (e.g., running) and the second activity boundary alert criteria and the second activity boundary alert are associated with a second type of physical activity different from the first type (e.g., rowing). In accordance with a determination that the activity data does not meet the second activity boundary alert criteria, the device refrains from displaying the second activity boundary alert (e.g., refrains from displaying 1004).

[0392] In some examples, if the activity boundary alert is a first activity boundary alert, after a predetermined time (e.g., 3 minutes) has elapsed without initiating a physical activity tracking function corresponding to the first activity boundary alert, the electronic device displays a second activity boundary alert (e.g., 1004), and the physical activity tracking function corresponding to the second activity boundary alert tracks the activity data detected before displaying the first activity boundary alert.

[0393] In some examples, after displaying the activity boundary alert and before the physical activity tracking functionality is activated, the electronic device displays a third user interface (e.g., 1076) (in some examples, the third user interface is the first user interface) including a scrollable list of affordances (e.g., 1078) associated with the physical activity. In some examples, the electronic device receives a ninth user input. In some examples, pursuant to a determination that the ninth user input is detected at an eleventh affordance (e.g., 1078A) of the scrollable list of affordances, the electronic device activates a physical activity tracking functionality corresponding to the activity boundary alert (in some examples, the physical activity tracking functionality associated with the activity boundary alert tracks activity data detected prior to displaying the third user interface) (in some examples, the physical activity tracking functionality corresponding to the activity boundary alert tracks activity data detected prior to displaying the activity boundary alert). In some examples, in response to a determination that a ninth user input is detected at a twelfth affordance (e.g., 1078C) of the scrollable list of affordances, the electronic device activates a physical activity tracking function that (1) does not correspond to the activity boundary alert and (2) is distinct from the physical activity tracking function corresponding to the activity boundary alert. In some examples, the physical activity tracking function corresponding to the activity boundary alert is a first physical activity tracking function, and in response to a determination that a ninth user input is detected at a thirteenth affordance (e.g., 1078B) of the scrollable list of affordances, the electronic device activates a second physical activity tracking function corresponding to the activity boundary alert, but the second physical activity tracking function is distinct from the first physical activity tracking function, and the second physical activity tracking function corresponding to the activity boundary alert tracks activity data detected after receiving the ninth user input (in some examples, the second physical activity tracking function tracks activity data detected after invoking the second physical activity tracking function) (in some examples, one of the physical activity tracking functions corresponding to the eleventh or twelfth affordance is the same physical activity tracking function corresponding to the thirteenth affordance).

[0394] In some examples, the eleventh and thirteenth affordances are visually highlighted (e.g., different color and / or larger) compared to the twelfth affordance to indicate that the eleventh and thirteenth affordances are a different type of affordance than the twelfth affordance.

[0395] It should be noted that the process details described above with respect to method 1100 (e.g., FIG. 11) are also applicable in an analogous manner to the methods described below / above. For example, method 1100 optionally includes one or more features of the various methods described below with reference to method 700, method 900, or method 1300. For example, the user interface of method 700 may be displayed in response to the user interface of method 1100. In another example, the user interface of method 1100 leads to the user interface of method 900, which is displayed in response to generated activity data (e.g., activity data may be generated by completing a workout). In another example, the user interface of method 1300 may be displayed by pacing using method 1100. For the sake of brevity, these details will not be repeated below.

[0396] 12A-12AK show example user interfaces associated with configuring a pace alert for a training application, according to some embodiments. The user interfaces allow a user to configure a data set that will be used to calculate the pace for the pace alert. For example, the data set used includes data starting from the start of the workout (called an average). As another example, the data set used may be an amount of previous data relative to the current time, such that the data set does not include data from the start of the workout (called a rolling average). The user interfaces in these figures are used to explain the processes described below, including the process of FIG. 13.

[0397] 12A illustrates a user interface 1256 displayed on a touch-sensitive display 602A of device 600A. User interface 1256 includes a number of application affordances 1258 associated with applications. For example, affordance 1258A is associated with a voice application, and affordance 1258B is associated with a training application. In some examples, user interface 1256 may be displayed to indicate which applications may be launched using device 600A. Selection of an affordance included in user interface 1256 may cause the corresponding application to be launched.

[0398] FIG 12B again illustrates user interface 1256 (shown in FIG 12A). As described above, user interface 1256 includes affordance 1258B. With reference to FIG 12B, user input (e.g., a tap input) 1229 corresponding to a selection of affordance 1258B is received. Pursuant to a determination that user input 1229 is detected at affordance 1258B, a training application corresponding to affordance 1258B is launched and user interface 1204 (described below and shown in FIG 12C) is displayed.

[0399] 12C, user interface 1204 includes a scrollable list of affordances 1206 associated with each physical activity tracking feature for each physical activity. For example, scrollable list of affordances 1206 includes affordance 1206A (corresponding to physical activity tracking features for outdoor running), affordance 1206B (corresponding to physical activity tracking features for indoor cycling workouts), and affordance 1206C (corresponding to physical activity tracking features for walking). In some examples, scrollable list of affordances 1206 can include additional affordances corresponding to additional physical activity tracking features that are not currently displayed but can be displayed in response to a scroll input (e.g., rotation of rotatable input mechanism 604A). Scrollable list of affordances 1206 is configured such that a type of physical activity can be selected for the current workout.

[0400] In some examples, one or more of the affordances in the scrollable list of affordances 1206 include option affordances, as described further below. For example, affordance 1206A includes option affordance 1208.

[0401] 12D, a user input (e.g., a tap input) 1201 is received corresponding to a selection of option affordance 1208. Pursuant to a determination that user input 1201 is detected at optional option affordance 1208, a user interface (e.g., user interface 1210 shown in FIG. 12E) is displayed having options related to physical activity corresponding to affordance 1206A.

[0402] 12E, in response to selecting option affordance 1208 (shown in FIG. 12D), user interface 1210 is displayed. User interface 1210 provides choices for changing the way device 600A operates when performing the physical activity tracking function corresponding to affordance 1206A. User interface 1210 includes a back affordance 1212 that causes user interface 1204 (shown in FIG. 12C) to be displayed. User interface 1210 further includes a pace alert affordance 1214 that allows a user to set a pace alert for the physical activity tracking function corresponding to affordance 1206A.

[0403] Figure 12F again illustrates the user interface 1210 (shown in Figure 12E). As described above, the user interface 1210 includes a pace alert affordance 1214. With reference to Figure 12F, a user input (e.g., a tap input) 1203 corresponding to a selection of the pace alert affordance 1214 is received.

[0404] In some examples, a user interface (e.g., user interface 1216 shown in FIG. 12G) having options related to a pace alert is displayed pursuant to a determination that user input 1203 is detected at pace alert affordance 1214. In other examples, a user interface (e.g., user interface 1222 shown in FIG. 12I) having options related to pacing a pace alert is displayed pursuant to a determination that user input 1203 is detected at pace alert affordance 1214.

[0405] 12G, in response to selecting the pace alert affordance 1214, a user interface 1216 is displayed. The user interface 1216 provides options for configuring the pace alert. The user interface 1216 includes a back affordance 1220 that causes the user interface 1210 (shown in FIG. 12E) to be displayed.

[0406] The user interface 1216 further includes a scrollable list of affordances 1218 associated with various actions. For example, the scrollable list of affordances 1218 includes a pace setting affordance 1218A (corresponding to displaying a pace setting screen), an average affordance 1218B (corresponding to causing a pace to be calculated using data from an entire workout), a rolling affordance 1218C (corresponding to causing a pace to be calculated using a subset of data from less than the entire workout), a stop affordance 1218D (corresponding to stopping a pace alert), or any combination thereof. Note that in some examples, the scrollable list of affordances 1218 may not fit within the touch-sensitive display 602A. In that case, one or more of the non-displayed affordances may be displayed in response to a scroll input (e.g., rotation of the rotatable input mechanism 604A).

[0407] As used herein, pace may refer to a speed (e.g., a distance traveled by a device in a certain amount of time or an amount of time it takes a device to travel a certain distance). With respect to pace, different calculations described herein (e.g., average and rolling) may refer to changing the amount of data set of the current workout used when performing the pace calculation. For example, in the case of average, the pace calculation may be based on data detected during the entire current workout. In the case of rolling, the pace calculation may be based on data detected during the previous amount of the current position (e.g., data detected for the last mile or data detected in the last 5 minutes).

[0408] FIG 12H again illustrates user interface 1216 (shown in FIG 12G). As described above, user interface 1216 includes pace setting affordance 1218A. With reference to FIG 12H, user input (e.g., a tap input) 1205 corresponding to a selection of pace setting affordance 1218A is received. Pursuant to a determination that user input 1205 is detected at pace setting affordance 1218A, a user interface (e.g., user interface 1222 shown in FIG 12I) having options related to pacing a pace alert is displayed.

[0409] 12I, in some examples, user interface 1222 may be displayed in response to selection of pace set affordance 1218A (shown in FIG. 12H). In other examples, user interface 1222 may be displayed in response to selection of pace alert affordance 1214 in user interface 1210 (shown in FIG. 12E). User interface 1222 may provide options that allow a user to set a pace for a pace alert. User interface 1222 may include a back affordance 1228 for causing user interface 1210 to be displayed.

[0410] The user interface 1222 further includes multiple affordances for setting the time (e.g., a set minutes affordance 1224A and a set seconds affordance 1224B). The set minutes affordance 1224A is used to set the minutes of the pace. The set seconds affordance 1224B is used to set the seconds of the pace.

[0411] As shown in FIG. 12I, each affordance for setting a time is independently selectable. For example, each of the set minutes affordance 1224A and the set seconds affordance 1224B can be selected. When an affordance of the multiple affordances for setting a time is selected, the affordance may be visually highlighted. For example, in FIG. 12I, the set minutes affordance 1224A has a thicker border than the set seconds affordance 1224B, thereby indicating that the set minutes affordance 1224A is selected (e.g., focused).

[0412] User interface 1222 further includes a scrollable list of affordances 1226, each associated with a different action. For example, scrollable list of affordances 1226 includes a set pace affordance 1226A (corresponding to setting a pace specified using multiple affordances for setting a time) and a cancel affordance 1226B (corresponding to displaying a user interface for providing the option to set a pace alert, such as user interface 1216 of FIG. 12G), or any combination thereof. Note that in some examples, the scrollable list of affordances 1226 may not fit within touch-sensitive display 602A. In that case, one or more of the affordances that are not displayed may be displayed in response to a scroll input (e.g., rotation of rotatable input mechanism 604A).

[0413] FIG. 12J again illustrates the user interface 1222 (shown in FIG. 121). As described above, the user interface 1222 includes the set seconds affordance 1224B. With reference to FIG. 12J, a user input (e.g., a tap input) 1207 corresponding to a selection of the set seconds affordance 1224B is received. Pursuant to a determination that the user input 1207 is detected at the set seconds input affordance 1224B, the set seconds affordance 1224B may be made more visually prominent than the set minutes affordance 1224A. For example, selection of the set seconds affordance 1224B may cause the set seconds affordance 1224B to be made visually prominent rather than the set minutes affordance 1224A.

[0414] 12K again illustrates the user interface 1222. Referring to FIG. 12K, the set-seconds affordance 1224B is visually prominent as opposed to the set-minutes affordance 1224A. In particular, the set-seconds affordance 1224B has a thicker border than the set-minutes affordance 1224A, thereby indicating that the set-seconds affordance 1224B is selected (e.g., has focus).

[0415] FIG. 12L illustrates one embodiment of a user interface 1222 for scrolling through the set seconds affordance 1224B. Referring to FIG. 12L, a rotation input 1209 is received at the rotatable input mechanism 604A. In response to the rotation input 1209, the options for the set seconds affordance 1224B are scrolled upwards to display different options for the set seconds affordance 1224B, as shown in FIG. 12M. For example, FIG. 12M illustrates a user interface 1222 that changes the set seconds affordance 1224B from "30" (shown in FIG. 12L) to "29" (shown in FIG. 12M). Similar scrolling can occur when the set minutes affordance 1224A is selected and a rotation input 1209 is received. The opposite direction can also be scrolled for both affordances.

[0416] Figure 12N again illustrates user interface 1222 (shown in Figure 12M). As described above, user interface 1222 includes pace setting affordance 1226A. With reference to Figure 12N, user input (e.g., a tap input) 1211 corresponding to a selection of pace setting affordance 1226A is received. Pursuant to a determination that user input 1211 is detected at pace setting affordance 1226A, a user interface (e.g., user interface 1216 shown in Figure 12O) having options related to pace alerts is displayed.

[0417] 12O, in response to a selection of the set pace affordance 1226A, a user interface 1216 may be displayed. The user interface 1216 may provide options for changing how the device 600A operates when performing a physical activity tracking function corresponding to the affordance 1206A. As shown in FIG. 12O, the user interface 1216 may include a scrollable list of affordances 1218 associated with various actions. As shown in FIG. 12G, the text of the set pace affordance 1218A (shown in FIG. 12O) has been changed from "set pace" (as shown in FIG. 12G) to a pace set by the user (e.g., "8'29" MI"), such as the pace set in FIG. 12N.

[0418] As described above, the scrollable list of affordances 1218 includes average affordance 1218B. Referring to Figure 12P, a user input (e.g., a tap input) 1213 corresponding to a selection of average affordance 1218B is received, which results in the use of an average calculation for the physical activity tracking function corresponding to affordance 1206A.

[0419] 12Q illustrates the user interface 1216 in response to a selection of the average affordance 1218B. Referring to FIG. 12Q, the average affordance 1218B is updated to include an indication (e.g., a checkmark) that the pace is calculated according to the average operation.

[0420] 12R, a user input (e.g., a tap input) 1215 is received corresponding to a selection of the back affordance 1220. In some examples, pursuant to a determination that the user input 1215 is detected at the back affordance 1220, a user interface (e.g., the user interface 1210 shown in FIG. 12S) displays options that change the way device 600A operates when performing a physical activity tracking function corresponding to affordance 1206A.

[0421] 12S, in response to a selection of the back affordance 1220, a user interface 1210 may be displayed. The user interface 1210 may provide options to change how the device 600A operates when performing the physical activity tracking function corresponding to the affordance 1206A. The text of the pace alert affordance 1214 (as shown in FIG. 12S) has been updated to include an indication of the pace set by the user (e.g., “average 8’29” per mile as shown in 1214A). In some examples, the text may become updated any time the device 600A is navigated to the user interface 1210. By including “average per mile” in the text, the pace alert affordance 1214 may indicate that a pace alert for the physical activity tracking function corresponding to the affordance 1206A is calculated using an average operation as described herein.

[0422] Figure 12T again illustrates user interface 1210. With reference to Figure 12T, a user input (e.g., a tap input) 1217 is received corresponding to a selection of back affordance 1212. In some examples, pursuant to a determination that user input 1217 is detected at back affordance 1212, a user interface (e.g., user interface 1204 illustrated in Figure 12U) is displayed.

[0423] 12U, affordance 1206A is updated to include an indication of the pace set by the user (e.g., "8'29" average pace" as shown in 1208B). It should be appreciated that multiple affordances in the list of affordances 1206 can include a pace set by the user. In some examples, different affordances in the list of affordances 1206 can include different paces set by the user.

[0424] FIG. 12V again illustrates user interface 1204. Referring to FIG. 12V, a user input (e.g., a tap input) 1219 corresponding to a selection of affordance 1206A is received. Pursuant to a determination that user input 1219 is detected at affordance 1206A in the scrollable list of affordances 1206, a physical activity tracking feature configured for the outdoor run is initiated. The physical activity tracking feature may include pace alerts when the user is below, on target, or above a user-specified pace for the outdoor run. As shown in FIG. 12V, the user-specified pace is "8'29".

[0425] In response to selecting affordance 1206A, user interface 1250 (shown in FIG. 10W) ​​is displayed. User interface 1250 displays (e.g., provides feedback regarding) data detected by device 600A regarding the outdoor run. To display the data detected by device 600A, user interface 1250 includes representation 1252. 12W, the representations 1252 include an icon 1252A (e.g., an animated icon of a runner representing an outdoor run), total miles 1252B (e.g., an indication of the number of miles run during the outdoor run), total calories 1252C (e.g., an indication of the amount of calories determined to have been burned by the user during the outdoor run), average pace per mile 1252D (e.g., an indication of the average amount of time it took device 600A to run one mile during the outdoor run), total time 1252E (e.g., an indication of the duration of the outdoor run), and BPM 1252F (e.g., the calculated number of beats per minute of the heart of the user wearing device 600A). It should be appreciated that in some embodiments, user interface 1250 can include more or fewer representations similar to those shown in FIG. 12AK and described below.

[0426] While the user is running outdoors, the user's pace may exceed the set pace for outdoor running. When the user's pace exceeds the set pace for outdoor running, an alert may be displayed indicating that the user's pace exceeds the set pace for outdoor running, as shown in FIG. 12X.

[0427] With reference to FIG. 12X, an alert can be included in the user interface 1244. The alert may include an icon corresponding to the current workout and information 1246. The information 1246 can include a status 1246A and a current pace 1246B. The status 1246A can indicate whether the user is below, on target, or above the set pace for the current workout. With reference to FIG. 12X, the status 1246A indicates that the user is "above target pace." The current pace 1246B can indicate the user's current pace. For example, the current pace 1246B (shown in FIG. 12X) indicates that the user is currently running at "8'52" pace, which is calculated over the entire current workout (because of the average selected to calculate pace). Because "8'52" is above the set pace of "8'29", the text "over target pace" can be displayed.

[0428] In response to the user now running faster and increasing the pace to 8'29", the user interface 1244 may be updated to reflect that the user is on target pace. With reference to FIG. 12Y, status 1246A may be updated to indicate that the user is "on target pace", and current pace 1246B may be updated to indicate that the user's current pace, as calculated over the entire current workout, is 8'29".

[0429] In response to the user running faster and increasing the pace to 7'57", the user interface 1244 may be updated to reflect that the user is below the target pace. For example, status 1246A may be updated to indicate that the user is "on pace" and current pace 1246B may be updated to indicate that the user's current pace, as calculated over the entire current workout, is 7'57". It should be appreciated that values ​​below, on, or above the target pace may include one or...

Claims

1. 1. A method comprising: In an electronic device including a display, receiving first user activity data for a first user, the first user activity data corresponding to a first time period and a second time period; receiving second user activity data of a second user, the second user activity data corresponding to the first time period, the first time period including a first elapsed sub-period and a first unexpired sub-period relating to an activity competition between the first user and the second user; receiving third user activity data of a third user, the third user activity data corresponding to the second time period, the second time period including a second elapsed sub-period and a second unexpired sub-period relating to an activity competition between the first user and the third user; and displaying a user interface on the display, the user interface comprising: a representation of the first user activity data and the second user activity data during the first elapsed subperiod relating to the activity competition between the first user and the second user; an indication of a time amount of the first unexpired subperiod for the activity competition between the first user and the second user; a representation of the first user activity data and the third user activity data during the second elapsed subperiod relating to the activity competition between the first user and the third user; and a display of the amount of time of the second unexpired subperiod relating to the activity competition between the first user and the third user.

2. The method of claim 1 , wherein the length of the first period of time is the same as the length of the second period of time.

3. The method of claim 1 or 2, wherein the activity competition between the first user and the second user starts at a first time, and the activity competition between the first user and the third user starts at a second time different from the first time.

4. The method of claim 1 or 3, wherein the length of the first period of time is different from the length of the second period of time.

5. The user interface includes: a first portion including the representation and the indication; and a second portion visually different from the first portion, the second portion comprising: a first affordance having an identity of the second user; and a second affordance having an identity of the third user; and A method according to claim 1 , further comprising: a third affordance having an identification of a fourth user who is not participating in an active activity competition with the first user.

6. The third affordance includes a notification that the fourth user has requested to initiate an activity competition between the first user and the fourth user, and the method further comprises: Receiving a first user input corresponding to a selection of the third affordance; and 6. The method of claim 5, further comprising: initiating a process to initiate an activity competition between the first user and the fourth user in response to receiving the first user input, the activity competition between the first user and the fourth user causing first user activity data and fourth user activity data to be received for a period of time.

7. receiving, while displaying the user interface, a second user input corresponding to a request to display additional information regarding the activity competition between the first user and the second user; The method of claim 1 , further comprising: in response to receiving the second user input, displaying a second user interface including the additional information.

8. The representation of the first user activity data and the second user activity data comprises: Identification information of the first user; and Identification information of the second user; and and a representation based on a comparison of activity data for the first and second users for one or more previous time periods preceding the first time period.

9. The method of claim 5, 6, or 8, wherein the third affordance comprises a first icon indicating a previous activity competition between the first user and the fourth user.

10. 10. The method of claim 9, wherein the second affordance includes a second icon indicating a previous activity competition between the first user and the third user, the first icon having a first visual theme and the second icon having a second visual theme different from the first visual theme.

11. while displaying the user interface, receiving a third user input corresponding to a request to display an awards user interface; and displaying, on the display, a third user interface in response to receiving the third user input, the third user interface comprising: a first portion corresponding to a first type of icon, the first type of icon being related to an activity competition, the first portion including the first icon and the second icon; and a second portion corresponding to an icon of a second type, said second portion including a third icon.

12. receiving a fourth user input corresponding to a selection of the third affordance; and In response to receiving the fourth user input, displaying a third user interface including a start race affordance; and receiving a fifth user input corresponding to the race start affordance; 12. The method of any one of claims 5, 6, and 8 to 11, further comprising: initiating an activity competition between the first user and the fourth user in response to receiving the fifth user input, the activity competition between the first user and the fourth user causing first user activity data and fourth user activity data to be received for a third time period.

13. receiving a sixth user input using a rotatable input mechanism of the electronic device while displaying the user interface; 13. The method of claim 1, further comprising: in response to receiving the sixth user input, updating the user interface to display a fourth affordance for a fifth user, the fourth affordance not being displayed prior to receiving the sixth user input.

14. A computer program causing a computer to carry out the method according to any one of claims 1 to 13.

15. A memory for storing a computer program according to claim 14; and one or more processors capable of executing the computer programs stored in the memory.

16. An electronic device comprising means for carrying out the method according to any one of claims 1 to 13.

Images