User interface for tracking and discovering item

Abstract

To provide an efficient man-machine interface in a device for displaying a notification of separation from a remote locator object.SOLUTION: A method executed by an electronic device including a radio antenna, a display device and one or more input devices, includes: displaying a separation alarm when a distance between a position of a remote locator object and a position of a user exceeds a separation threshold value; marking the position of the remote locator object as a safety zone of the remote locator object in response to detection of one or more input sequences while the separation alarm is being displayed; and generating no separation alarm while the remote locator object stays in the safety zone even if the distance between the position of the remote locator object and the position of the user exceeds the separation threshold value.SELECTED DRAWING: Figure 9A

Description

[Technical Field]

[0001] TECHNICAL FIELD This application relates generally to user interfaces that allow users to track and find items on electronic devices. [Background technology]

[0002] In recent years, user interaction with electronic devices has increased significantly, which may be devices such as televisions, multimedia devices, mobile devices, computers, tablet computers, etc.

[0003] In some situations, a user may wish to track items using such a device. Enhancing the user's interaction with the device improves the user experience with the device and reduces user interaction time, which is particularly important when the input device is battery operated.

[0004] It is well understood that personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized uses should be clearly indicated to users. In particular, use of personally identifiable information should comply with generally recognized privacy policies and practices that meet or exceed industry or government requirements for maintaining user privacy. Summary of the Invention

[0005] Some embodiments described in this disclosure are directed to one or more electronic devices that present a user interface for initializing a remote locator object. Some embodiments described in this disclosure are directed to one or more electronic devices that present a notification when a remote locator object is separated from a user. Some embodiments described in this disclosure are directed to one or more electronic devices that present a notification when an unknown remote locator object is tracking a user. Some embodiments described in this disclosure are directed to a user interface for a short-range locator user interface for discovering a remote locator object. Some embodiments described in this disclosure are directed to one or more electronic devices that present a user interface for discovering a remote locator object using a map user interface or using a short-range locator user interface. A full description of these embodiments is provided in the "Detailed Description of the Invention," and it should be understood that the above "Summary" does not limit the scope of the present disclosure in any way. [Brief explanation of the drawings]

[0006] For a better understanding of the various embodiments described, please refer to the following detailed description in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:

[0007] [Figure 1A] FIG. 1 is a block diagram illustrating a portable multifunction device with a touch-sensitive display according to some embodiments.

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

[0009] [Figure 2] FIG. 1 illustrates a portable multifunction device with a touch screen according to some embodiments.

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

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

[0012] [Figure 4B] 1 illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display, according to some embodiments.

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

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

[0015] [Figure 5C] FIG. 1 illustrates exemplary components of a personal electronic device having a touch-sensitive display and intensity sensor, according to some embodiments. [Figure 5D] FIG. 1 illustrates exemplary components of a personal electronic device having a touch-sensitive display and intensity sensor, according to some embodiments.

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

[0017] [Figure 5I] A set of sample tactile output patterns is provided that may be used either individually or in combination, either as is or through one or more transformations (e.g., modulation, amplification, truncation, etc.), to generate suitable tactile feedback for a variety of scenarios and purposes, such as those described above and with respect to the user interfaces and methods discussed herein. [Figure 5J] A set of sample tactile output patterns is provided that may be used either individually or in combination, either as is or through one or more transformations (e.g., modulation, amplification, truncation, etc.), to generate suitable tactile feedback for a variety of scenarios and purposes, such as those described above and with respect to the user interfaces and methods discussed herein. [Figure 5K] A set of sample tactile output patterns is provided that may be used either individually or in combination, either as is or through one or more transformations (e.g., modulation, amplification, truncation, etc.), to generate suitable tactile feedback for a variety of scenarios and purposes, such as those described above and with respect to the user interfaces and methods discussed herein. [Figure 5L] A set of sample tactile output patterns is provided that may be used either individually or in combination, either as is or through one or more transformations (e.g., modulation, amplification, truncation, etc.), to generate suitable tactile feedback for a variety of scenarios and purposes, such as those described above and with respect to the user interfaces and methods discussed herein. [Figure 5M]A set of sample tactile output patterns is provided that may be used either individually or in combination, either as is or through one or more transformations (e.g., modulation, amplification, truncation, etc.), to generate suitable tactile feedback for a variety of scenarios and purposes, such as those described above and with respect to the user interfaces and methods discussed herein. [Figure 5N] A set of sample tactile output patterns is provided that may be used either individually or in combination, either as is or through one or more transformations (e.g., modulation, amplification, truncation, etc.), to generate suitable tactile feedback for a variety of scenarios and purposes, such as those described above and with respect to the user interfaces and methods discussed herein.

[0018] [Figure 6A] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6B] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6C] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6D] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6E] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6F] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6G] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6H]1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6I] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6J] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6K] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6L] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6M] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6N] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6O] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6P] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6Q] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6R] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6S] 1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure. [Figure 6T]1 illustrates an example method for an electronic device to initialize a remote locator object, according to some embodiments of the present disclosure.

[0019] [Figure 7A] 1 is a flow diagram illustrating a method for initializing a remote locator object according to some embodiments of the present disclosure. [Figure 7B] 1 is a flow diagram illustrating a method for initializing a remote locator object according to some embodiments of the present disclosure. [Figure 7C] 1 is a flow diagram illustrating a method for initializing a remote locator object according to some embodiments of the present disclosure. [Figure 7D] 1 is a flow diagram illustrating a method for initializing a remote locator object according to some embodiments of the present disclosure.

[0020] [Figure 8A] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8B] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8C] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8D] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8E] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8F] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8G]1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8H] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8I] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8J] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8K] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8L] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8M] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8N] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8O] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 8P] 1 illustrates an example method for an electronic device to display notification of a separation from a remote locator object, according to some embodiments of the present disclosure.

[0021] [Figure 9A] 1 is a flow diagram illustrating a method for displaying notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 9B]1 is a flow diagram illustrating a method for displaying notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 9C] 1 is a flow diagram illustrating a method for displaying notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 9D] 1 is a flow diagram illustrating a method for displaying notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 9E] 1 is a flow diagram illustrating a method for displaying notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 9F] 1 is a flow diagram illustrating a method for displaying notification of a separation from a remote locator object, according to some embodiments of the present disclosure. [Figure 9G] 1 is a flow diagram illustrating a method for displaying notification of a separation from a remote locator object, according to some embodiments of the present disclosure.

[0022] [Figure 10A] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10B] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10C] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10D] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10E] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10F]1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10G] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10H] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10I] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10J] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10K] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10L] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10M] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10N] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10O] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10P] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10Q]1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. [Figure 10R] 1 illustrates an example method by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure.

[0023] [Figure 11A] 1 is a flow diagram illustrating a method for displaying notification of a pursuit by an unknown remote locator object according to some embodiments of the present disclosure. [Figure 11B] 1 is a flow diagram illustrating a method for displaying notification of a pursuit by an unknown remote locator object according to some embodiments of the present disclosure. [Figure 11C] 1 is a flow diagram illustrating a method for displaying notification of a pursuit by an unknown remote locator object according to some embodiments of the present disclosure. [Figure 11D] 1 is a flow diagram illustrating a method for displaying notification of a pursuit by an unknown remote locator object according to some embodiments of the present disclosure. [Figure 11E] 1 is a flow diagram illustrating a method for displaying notification of a pursuit by an unknown remote locator object according to some embodiments of the present disclosure.

[0024] [Figure 12A] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12B] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12C] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12D]1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12E] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12F] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12G] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12H] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12I] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12J] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12K] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12L] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12M] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12N] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12O] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12P] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12Q] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12R] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12S] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12T] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12U] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12V] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12W]1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12X] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12Y] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12Z] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12AA] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12BB] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12CC] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12DD] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12EE] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure. [Figure 12FF] 1 illustrates an example method for an electronic device to present a user interface for tracking and finding remote locator objects, according to some embodiments of the present disclosure.

[0025] [Figure 13A] 1 is a flow diagram illustrating a method for presenting a user interface for tracking and finding remote locator objects according to some embodiments of the present disclosure. [Figure 13B] 1 is a flow diagram illustrating a method for presenting a user interface for tracking and finding remote locator objects according to some embodiments of the present disclosure. [Figure 13C] 1 is a flow diagram illustrating a method for presenting a user interface for tracking and finding remote locator objects according to some embodiments of the present disclosure. [Figure 13D] 1 is a flow diagram illustrating a method for presenting a user interface for tracking and finding remote locator objects according to some embodiments of the present disclosure. [Figure 13E] 1 is a flow diagram illustrating a method for presenting a user interface for tracking and finding remote locator objects according to some embodiments of the present disclosure. [Figure 13F] 1 is a flow diagram illustrating a method for presenting a user interface for tracking and finding remote locator objects according to some embodiments of the present disclosure.

[0026] [Figure 14A] 1 is a flow diagram illustrating a method for presenting a user interface for tracking and finding remote locator objects according to some embodiments of the present disclosure. [Figure 14B] 1 is a flow diagram illustrating a method for presenting a user interface for tracking and finding remote locator objects according to some embodiments of the present disclosure. [Figure 14C] 1 is a flow diagram illustrating a method for presenting a user interface for tracking and finding remote locator objects according to some embodiments of the present disclosure. [Figure 14D]1 is a flow diagram illustrating a method for presenting a user interface for tracking and finding remote locator objects according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

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

[0028] There is a need for electronic devices for tracking the location of remote locator objects and generating notifications associated with the remote locator objects. Such techniques can reduce the cognitive burden on users who use such devices and / or wish to control the user's use of such devices. Furthermore, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

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

[0030] The terminology used in the description of the various embodiments set forth herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the term "and / or" should be understood to refer to and include 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. 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 dictates otherwise.

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

[0032] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad). Optionally, other portable electronic devices, such as laptop or tablet computers having touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads), are also used.

[0033] 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. The following discussion describes electronic devices that include a display and a touch-sensitive surface.

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

[0035] 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, a common physical architecture of the device (such as the touch-sensitive surface) optionally supports a variety of applications with user interfaces that are intuitive and transparent to the user. The various applications running on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface.

[0036] Attention now turns to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 having touch-sensitive display system 112, according to some embodiments. Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, peripherals interface 118, RF circuitry 108, other input control devices 116, and external port 124. Touch-sensitive display 112 may conveniently be referred to as a “touch screen,” and may also be known or referred to as a “touch-sensitive display system.” Device 100 optionally includes one or more contact intensity sensors 165 (e.g., on a touch-sensitive surface, such as touch-sensitive display system 112 of device 100) that detect the intensity of a contact on device 100. Device 100 optionally includes one or more tactile output generators 167 that generate tactile output on device 100 (e.g., generate tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). Device 100 optionally includes one or more optical sensors 164. These components optionally communicate via one or more communication buses or signal lines 103.

[0037] Using the intensity of contact as an attribute of user input enables user access to additional device functionality that may not otherwise be accessible to users on devices of reduced size that have limited footprint for receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons) and / or displaying affordances (e.g., on a touch-sensitive display). 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 proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact is optionally determined (or measured) using various techniques and various 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 force at various points on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values, and more typically includes hundreds (e.g., at least 256) distinct values. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated 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 and / or change in the resistance of the touch-sensitive surface proximate the contact, and / or change in the resistance of the touch-sensitive surface proximate the contact are optionally used as surrogates for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measurement of the contact force or pressure is converted to an estimate of the force or pressure, and the estimate of the force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). In some implementations, the surrogate measurement of the contact force or pressure is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurement).

[0038] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to its previous position, a physical displacement of a component of the device (e.g., the touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. In some cases, a user feels a tactile sensation such as a “downclick” or an “upclick” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that has been physically pressed (e.g., displaced) by the user's action. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive user surface (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be 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 “downclick” or an “upclick” of a physical actuator button. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

[0039] 1A may be 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. It is understood that device 100 is only one example of a portable multifunction device, and that device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have a different configuration or arrangement of its components.

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

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

[0042] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. 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. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by short-range communication radios. RF circuitry 108 optionally communicates with networks, such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or wireless networks, such as a cellular telephone network, a wireless local area network (LAN) and / or a metropolitan area network (MAN), and with other devices, via wireless communication, optionally including high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), long term evolution (LTE), near field communication, and the like.Near Field Communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), Bluetooth, Bluetooth Low Energy (BTLE), voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIP), The present invention may use any of a number of communication standards, protocols, and technologies, including, but not limited to, Instant Messaging (e.g., the extensible messaging and presence protocol (XMPP)), SMS (Simple Message Extensions), Instant Messaging and Presence Service (IMPS), Short Message Service (SMS), and / or instant messaging (e.g., the extensible messaging and presence protocol (XMPP)), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this application.

[0043] Audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Speaker 111 converts electrical signals into sound waves audible to humans. Audio circuit 110 receives audio data from peripherals interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. Audio circuit 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuit 110 converts the electrical signals into audio data and transmits the audio data to peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to memory 102 and / or RF circuit 108 by peripherals interface 118. In some embodiments, 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 detachable audio input / output peripheral, such as an output-only headphone or a headset with both an output (e.g., single or double ear headphones) and an input (e.g., a microphone).

[0044] I / O subsystem 106 couples input / output peripherals on device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes one or more input controllers 160 for display controller 156, light sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and other input or control devices. One or more input controllers 160 receive / send electrical signals from / to other input control devices 116. In some embodiments, 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. One or more buttons (e.g., 208 in FIG. 2 ) optionally include up / down buttons for volume control of speaker 111 and / or microphone 113. One or more buttons optionally include push buttons (e.g., 206 in FIG. 2 ). Other input control devices 116 optionally include physical buttons (eg, push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and the like.

[0045] A quick press of the push button optionally unlocks the touchscreen 112, or optionally initiates a process to unlock the device using gestures on the touchscreen. A longer press of a push button (e.g., 206) optionally turns power on or off to the device 100. The touchscreen 112 is used to implement virtual or soft buttons and one or more soft keyboards. The functionality of one or more of the buttons is optionally customizable by the user.

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

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

[0048] Touchscreen 112 and display controller 156 optionally detect touch and any movement or disruption 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 acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with touchscreen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used. Touchscreen 112 optionally uses light emitting diode (LED), liquid crystal display (LCD), or light emitting polymer display (LPD) technology, although other display technologies are used in other embodiments.

[0049] The touch-sensitive display in some embodiments of touchscreen 112 is, optionally, similar to a multi-touch-sensitive touchpad, but touchscreen 112 displays visual output from device 100, whereas a touch-sensitive touchpad does not provide visual output.

[0050] A user optionally contacts touchscreen 112 using any suitable object or accessory, such as a stylus, finger, or the like. In some embodiments, the device converts coarse finger input into precise pointer / cursor positions or commands for performing actions desired by the user. In some embodiments, the user interface is designed to operate primarily using finger-based contact and gestures, which may not be as precise as stylus-based input due to the larger contact area of a finger on the touchscreen. Touchscreen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi.

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

[0052] Device 100 also includes a power system 162 that provides 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)), power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), a recharging system, power failure detection circuitry, and any other components associated with generating, managing, and distributing electrical power in a portable device.

[0053] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor 164 optionally works in conjunction with imaging module 143 (also called a camera module) to capture still images or video. In some embodiments, the light sensor is located on the front of the device so that an image of a user is optionally acquired for a video conference while the user views other video conference participants on a touchscreen display. In some embodiments, the light sensor is located on the back of device 100, opposite touchscreen display 112 on the front of the device, so that the touchscreen display can be used as a viewfinder for capturing still images and / or video. In some embodiments, the position of the light sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that a single light sensor 164 is used for both video conferencing and capturing still images and / or video, along with a touchscreen display.

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

[0055] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled to peripherals interface 118. In some embodiments, the proximity sensor turns off and disables touchscreen 112 when the multifunction device is placed near a user's ear (e.g., when the user is making a phone call). Alternatively, proximity sensor 166 is optionally coupled to input controller 160 in I / O subsystem 106.

[0056] 1A shows a tactile output generator coupled to haptic feedback controller 161 in I / O subsystem 106. Device 100 also optionally includes one or more tactile output generators 167. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as 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 embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., back and forth in the same plane as the surface of device 100).

[0057] 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. In some embodiments, information is displayed on the touchscreen display in portrait or landscape orientation based on analysis of data received from the one or more accelerometers. In addition to accelerometer(s) 168, device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information regarding the location and orientation (e.g., portrait or landscape) of device 100.

[0058] In some embodiments, software components stored in memory 102 include operating system 126, applications (or instruction sets) 136, communications module (or instruction sets) 128, touch / motion module (or instruction sets) 130, text input module (or instruction sets) 134, graphics module (or instruction sets) 132, and Global Positioning System (GPS) module (or instruction sets) 135. Additionally, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device / global internal state 157, as shown in FIGS. 1A and 3. Device / global internal state 157 includes one or more of: active application state indicating which applications, if any, are currently active; display state indicating which applications, views, or other information occupy various regions of touchscreen display 112; sensor state including information obtained from the device's various sensors and input control devices 116; and location information regarding the device's position and / or orientation.

[0059] Operating system 126 (e.g., WINDOWS, Darwin, RTXC, LINUX, UNIX, OS X, iOS, or an embedded operating system such as VxWorks) includes various software components and / or drivers that control and manage general system tasks (e.g., memory management, storage control, power management, etc.) and facilitate communication between various hardware and software components.

[0060] The 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 the RF circuitry 108 and / or the external ports 124. In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors. The external ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) are adapted to couple to other devices directly or indirectly via a network (e.g., the Internet, wireless LAN, etc.).

[0061] Contact / motion module 130, optionally in conjunction with display controller 156, detects contact with touchscreen 112 and other touch-sensing devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 receives contact data from the touch-sensitive surface. Contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger-down event), determining the intensity 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 contact movement 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 of the contact). Determining the movement of the contact point, as represented by the series 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., a single finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on the touchpad.

[0062] In some embodiments, contact / motion module 130 uses one or more sets of intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). For example, a mouse “click” threshold for a trackpad or touchscreen display can be set to any of a wide range of pre-defined thresholds without modifying the trackpad or touchscreen display hardware. In some embodiments, 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 threshold of a particular physical actuator, but can be adjusted without modifying the physical hardware of device 100). Additionally, in some implementations, a user of the device is provided with a software setting to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once via a system-level click “intensity” parameter).

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

[0064] As used herein, the term "graphic" 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, video, animation, etc. Graphics module 132 includes various known software components that render and display graphics on touchscreen 112 or other display, including components that vary the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics.

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

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

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

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

[0069] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: ● Video player module, ● Music player module, ● 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 images and / or video; ● Image management module 144; ● Browser module 147, ● Calendar module 148, • a widget module 149, optionally including one or more of a dictionary widget 149-5, a weather widget 149-1, a stocks widget 149-2, an alarm clock widget 149-4, a calculator widget 149-3, and other widgets obtained by the user, and a user-created widget 149-6; ● a widget creator module 150 for creating user-created widgets 149-6; ● Search module 151, a video and music player module 152 that integrates a music player module and a video player module; ● Memo module 153, Map module 154, and / or ● Online video module 155.

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

[0071] Contacts module 137, in conjunction with touchscreen 112, contact / motion module 130, graphics module 132, text input module 134, and display controller 156, is optionally used to manage an address book or contact list (e.g., stored in memory 102 or in the application internal state 192 of contacts module 137 in memory 370), including adding name(s) to the address book, removing name(s) from the address book, associating phone number(s), address(es), email address(es), or other information with names, associating images with names, 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, etc.

[0072] As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies. Telephone module 138, in conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, contact / motion module 130, graphics module 132, text input module 134, and display controller 156, is optionally used to enter character sequences corresponding to telephone numbers, access one or more telephone numbers in contacts module 137, modify entered telephone numbers, dial respective telephone numbers, place calls, and disconnect or hang up when the call is completed.

[0073] Videoconferencing module 139 includes executable instructions to cooperate with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, contact / motion module 130, graphics module 132, text input module 134, contact module 137, telephone module 138, display controller 156, light sensor controller 158, and light sensor 164 to initiate, conduct, and end a videoconference between a user and one or more other participants according to the user's instructions.

[0074] Email client module 140 includes executable instructions that cooperate with RF circuitry 108, touchscreen 112, contact / motion module 130, graphics module 132, text input module 134, and display controller 156 to create, send, receive, and manage emails in response to user instructions. In cooperation with image management module 144, email client module 140 greatly facilitates the creation and sending of emails with still or video images captured by camera module 143.

[0075] As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS). Instant messaging module 141 includes executable instructions to cooperate with RF circuitry 108, touchscreen 112, contact / motion module 130, graphics module 132, text input module 134, and display controller 156 to enter character sequences corresponding to instant messages, modify previously entered characters, send respective instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephony-based instant messages, or SIMPLE, XMPP, or IMPS for Internet-based instant messages), receive instant messages, and view received instant messages. In some embodiments, 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).

[0076] The training support module 142 includes executable instructions to cooperate with the RF circuitry 108, the touchscreen 112, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, the display controller 156, and the music player module to create workouts (e.g., with time, distance, and / or calorie burn goals), select and play music for workouts, communicate with training sensors (sports devices), receive training sensor data, calibrate sensors used to monitor workouts, and display, store, and transmit training data.

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

[0078] Image management module 144 includes executable instructions that cooperate with touchscreen 112, contact / motion module 130, graphics module 132, text input module 134, display controller 156, and camera module 143 to compose, label, delete, modify (e.g., edit), or otherwise manipulate, present (e.g., in a digital slideshow or album), and store still and / or video images.

[0079] Browser module 147, in conjunction with RF circuitry 108, touchscreen 112, contact / motion module 130, graphics module 132, text input module 134, and display controller 156, contains executable instructions to browse the Internet according to user instructions, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0080] Calendar module 148 includes executable instructions that cooperate with RF circuitry 108, touchscreen 112, contact / motion module 130, graphics module 132, text input module 134, email client module 140, display controller 156, and browser module 147 to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) according to user instructions.

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

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

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

[0084] In some embodiments, device 100 optionally includes MP3 player functionality. Video and music player module 152 includes executable instructions that, 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, 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 for displaying, presenting, or otherwise playing videos (e.g., on touchscreen 112 or on an external display connected via external port 124).

[0085] The notes module 153 includes executable instructions that cooperate with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134 to create and manage to-do lists, notes, and the like according to user instructions.

[0086] Map module 154, in conjunction with RF circuitry 108, touchscreen 112, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, browser module 147, and display controller 156, is used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data regarding businesses and other points of interest at or near a particular location, and other location-based data), optionally in accordance with user instructions.

[0087] Online video module 155, in conjunction with touchscreen 112, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, browser module 147, and display controller 156, contains instructions that enable a user to receive, access, browse (e.g., by streaming and / or downloading), play (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140.

[0088] The above-identified modules and applications each correspond to a set of executable instructions that perform one or more of the functions previously described and methods described herein (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules; thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. 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). Additionally, memory 102 optionally stores additional modules and data structures not described above.

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

[0090] The set of predefined functions performed only 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, home menu, or root menu from any user interface displayed on device 100. In some embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad. In other such embodiments, the "menu button" is implemented using the touchpad.

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

[0092] Event sorter 170 includes event monitor 171 and event dispatcher module 174. Event sorter 170 receives event information and determines which application 136-1 to deliver the event information to and application view 191 for application 136-1. In some embodiments, application 136-1 includes application internal state 192 that indicates the current application view that is 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 which application(s) is / are currently active, and application internal state 192 is used by event sorter 170 to determine which application view 191 to deliver the event information to.

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

[0094] Event monitor 171 receives event information from peripherals interface 118. 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 (via audio circuitry 110). The event information includes information about a sub-event (e.g., a user touch as part of a multi-touch gesture on touch-sensitive display 112). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

[0095] In some embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receipt of an input above a predetermined noise threshold and / or for more than a predetermined duration). In other embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information.

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

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

[0098] 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, within which information is displayed and touch-based gestures occur. In some embodiments, the lowest-level view in which a touch is detected is optionally referred to as the hit view, and the set of events that are recognized as appropriate input is optionally determined based at least in part on the hit view of the initial touch that initiates the touch gesture. Thus, the application view (of the respective application) in which a touch is detected optionally corresponds to a programmatic level within the application's programmatic or view hierarchy.

[0099] When an application has multiple views arranged in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process sub-events. Hit view determination module 172 receives information related to the sub-events of a touch-based gesture. In most situations, the hit view is the lowest-level view in which an initiating 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 as the touch or input source identified as the hit view.

[0100] Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive a particular sequence of sub-events. In some 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 determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to the area associated with one particular view, views higher in the hierarchy still remain actively participating views.

[0101] Event dispatcher module 174 dispatches event information to event recognizers (e.g., event recognizer 180). In some embodiments, event dispatcher module 174 stores event information obtained by each event receiver 182 in an event queue. 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.

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

[0103] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for processing touch events that occur within a respective view of the application's user interface. Typically, each application view 191 includes multiple event recognizers 180. Each application view 191 of application 136-1 includes one or more 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, each 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. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in respective application views 191. Alternatively, one or more of application views 191 include one or more respective event handlers 190.

[0104] Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. 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). Event recognizer 180 includes event receiver 182 and event comparator 184.

[0105] 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 movement of a touch. When the sub-event involves a touch movement, the event information also optionally includes the speed and direction of the sub-event. Depending on the sub-event, the event information also includes additional information, such as the position of the sub-event. In some embodiments, 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).

[0106] In some embodiments, event comparator 184 includes event definition 186. Event comparator 184 compares event information to predefined event or sub-event definitions and determines an event or sub-event, or determines or updates the state of an event or sub-event, based on the comparison. Event definition 186 includes definitions of events (e.g., a predefined sequence of sub-events), such as Event 1 (187-1) and Event 2 (187-2). In some embodiments, sub-events within Event 187 include, for example, touch start, touch end, touch movement, touch cancellation, and multiple touches. In one example, Event 2 (187-2) is a drag on a displayed object. Drag includes, for example, a touch (or contact) on a displayed object to a predetermined stage, a touch movement across touch-sensitive display 112, and a touch lift-off (touch end). In another example, Event 1 (187-1) is a double tap on a displayed object. A double tap includes, for example, a first touch on a display object relative to a predetermined stage (touch start), a first lift-off (touch end) relative to the predetermined stage, a second touch on a display object relative to the predetermined stage (touch start), and a second lift-off (touch end) relative to the predetermined stage. In some embodiments, the event also includes information regarding one or more associated event handlers 190.

[0107] In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, if a touch is detected on touch-sensitive display 112 in an application view in which three user interface objects are displayed on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggers the hit test. In some embodiments, event definition 187 includes a definition of the event for each user interface object.

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

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

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

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

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

[0113] In some embodiments, object updater 177 creates and updates objects used in 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. In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contacts module 137 or stores video files used in a video player module.

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

[0115] 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 using input devices, although not all of them are initiated on a touchscreen. For example, verbal commands, mouse movements and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds, pen stylus input, contact movements such as tapping, dragging, scrolling on a touchpad, device movement, detected eye movement, biometric input, and / or any combination thereof, are optionally utilized as inputs corresponding to sub-events that define the event to be recognized.

[0116] FIG. 2 illustrates portable multifunction device 100 having touchscreen 112, according to some embodiments. The touchscreen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user may select one or more of the graphics by performing a gesture on the graphics, for example, using one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). 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 rolling (right to left, left to right, upward and / or downward) of a finger in contact with device 100. In some embodiments, selection of one or more graphics is performed when the user breaks contact with the one or more graphics. In some implementations or situations, accidental contact with a graphic does not select the graphic, for example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon optionally does not select the corresponding application.

[0117] Device 100 optionally also includes one or more physical buttons, such as a "home" button or menu button 204. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on touchscreen 112. As previously mentioned, menu button 204 is optionally used to navigate to any application 136 within a set of applications running on device 100.

[0118] In some embodiments, device 100 includes touchscreen 112, menu button 204, pushbuttons 206 for powering the device on / off and locking the device, volume control buttons 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external docking / charging port 124. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touchscreen 112 and / or one or more tactile output generators 167 for generating a tactile output to a user of device 100. Pushbutton 206 is optionally used to power the device on / off by pressing and holding the button down for a predetermined period of time, to lock the device by pressing and releasing the button before the predetermined time has elapsed, and / or to unlock the device or initiate the unlocking process. In an alternative embodiment, device 100 also accepts verbal input via microphone 113 to activate or deactivate certain functions.

[0119] FIG. 3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, according to some embodiments. 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 need not be portable. 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 interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interface 330, including 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 that generates tactile output on device 300 (e.g., similar to tactile output generator 167 described above with reference to FIG. 1A ), and sensors 359 (e.g., light, acceleration, proximity, touch-sensing, and / or contact intensity sensors similar to contact intensity sensor 165 described above with reference to FIG. 1A ). Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310. 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.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, 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, disc authoring module 388, and / or spreadsheet module 390, whereas memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

[0120] 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 function described above. 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. The above-identified modules or programs (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured.

[0121] Attention is now optionally directed to user interface embodiments, for example, as implemented on portable multifunction device 100.

[0122] 4A shows an exemplary 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 with icons of frequently used applications, such as: o An icon 416 of the phone module 138, optionally including an indicator 414 of the number of missed calls or voicemail messages; o An icon 418 of the email client module 140, optionally including an indicator 410 of the number of unread emails; icon 422 of the video and music player module 152, ○ Browser module 147 icon 420, ● Icons of other applications, such as: ○ Icon 424 of IM module 141, ○ Icon 442 of Training Support Module 142, ○ Icon 430 of camera module 143, ○ Icon 428 in Image Management Module 144, ○ Calendar module 148 icons 426, ○ Weather widget 149-1 icon 438, ○ Stock widget 149-2 icon 434, ○ Alarm clock widget 149-4 icon 440, ○ Icon 444 of Memo module 153, ○ Icon 436 of map module 154, ○ Icon 432 of online video module 155, o An icon 446 for a settings application or module that provides access to settings related to the device 100 and its various applications 136.

[0123] In some embodiments, the label for each application icon includes the name of the application corresponding to the respective application icon, hi some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.

[0124] 4B shows an exemplary user interface on a device (e.g., device 300 of FIG. 3) that has 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 tactile output generators 357 for generating tactile outputs to a user of device 300 and / or 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.

[0125] Although some of the following examples are given with reference to input on touchscreen display 112 (which combines a touch-sensitive surface and a display), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B . According to these embodiments, the device detects contacts 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 some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B ) has a primary axis (e.g., 452 in FIG. 4B ) that corresponds to a primary axis (e.g., 453 in FIG. 4B ) on the display (e.g., 450). In this way, 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 when the touch-sensitive surface is separate from the display. It should be understood that similar methods are optionally used for the other user interfaces described herein.

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

[0127] FIG. 5A shows an exemplary personal electronic device 500. 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 ). Device 500 includes a body 502. In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touch screen 504 (or the touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of contact (e.g., touch) being applied. The one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface actions on device 500.

[0128] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Examples of physical input mechanisms include push buttons and rotatable mechanisms. Input mechanisms 506 and 508, if included, may be physical. In some embodiments, device 500 has one or more attachment mechanisms. These attachment mechanisms allow a user to wear device 500. Such attachment mechanisms, if included, may 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.

[0129] FIG. 5B illustrates an exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 can include input mechanism 506 and / or 508. Input mechanism 506 is optionally a rotatable input device or a depressible and rotatable input device, for example. In some examples, input mechanism 508 is optionally a button. Device 500 has a bus 512 that operably couples an I / O section 514 to one or more computer processors 516 and memory 518. I / O section 514 can be connected to a display 504, which can have touch-sensing components 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, I / O section 514 can be connected to a communication unit 530 that receives application and operating system data using Wi-Fi, Bluetooth, near-field communication (NFC), cellular, and / or other wireless communication technologies.

[0130] 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 operably connected to I / O section 514. In some embodiments, input mechanism 508 is optionally a microphone.

[0131] 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 cause the computer processors to perform the techniques described below, including processes 700, 900, 1100, 1300, and 1400 (FIGS. 7, 9, 11, 13, and 14). In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, 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, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and resident solid-state memory such as flash, solid-state drives, and the like. A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. 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.

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

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

[0134] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. The characteristic intensity is optionally based on a set of a predetermined number of intensity samples, i.e., intensity samples collected during a predetermined time (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detecting the contact, before detecting liftoff of the contact, before or after detecting the start of contact movement, 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). In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity of a contact is optionally based on one or more of the maximum intensity of the contact, the average intensity of the contact, the mean intensity of the contact, the top 10 percentile intensity of the contact, the half maximum intensity of the contact, the 90th percentile intensity of the contact, etc. In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action 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 not exceeding the first threshold results in a first action, a contact having a characteristic intensity above the first intensity threshold but not exceeding the second intensity threshold results in a second action, and a contact having a characteristic intensity above the second threshold results in a third action. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the comparison between the characteristic intensity and one or more thresholds is not used to determine whether the first action or the second action should be performed, but rather to determine whether one or more actions should be performed (e.g., whether to perform the respective action or to forgo performing the respective action).

[0135] FIG. 5C illustrates the detection of multiple contacts 552A-552E on the 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 relative to intensity units. In this example, intensity sensors 524A and 524D each measure 9 intensity units, and intensity sensors 524B and 524C each measure 7 intensity units. In some implementations, the aggregate intensity is the sum of the intensity measurements of multiple intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity that is a fraction of the aggregate intensity. FIG. 5D illustrates assigning aggregate intensities to contacts 552A-552E based on their distance from the center of force 554. More generally, in some implementations, each contact j is assigned a respective intensity Ij, which is a fraction of an aggregate intensity A, according to a predetermined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance from the center of force to each contact j, and ΣDi is the sum of the distances from the center of force to all respective contacts (e.g., from i=1 to the end). In this example, contacts 552A, 552B, and 552E are each assigned a contact intensity of 8 intensity units of the aggregate intensity, and contacts 552C and 552D are each assigned a contact intensity of 4 intensity units of the aggregate intensity. The operations described with reference to FIGS. 5C-5D can be performed using electronic devices similar to or identical to device 100, 300, or 500. In some embodiments, an intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). In some embodiments, the characteristic intensity of a contact is based on one or more intensities of the contact. Note that the intensity diagrams are not part of the displayed user interface, but are included in FIGS. 5C-5D as an aid to the reader.

[0136] In some embodiments, 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 a triangular smoothing algorithm, an unweighted moving average smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact for purposes of determining the characteristic intensity. In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, the touch-sensitive surface optionally receives successive swipe contacts that transition from a start position to an end position at which 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 successive swipe contacts (e.g., only the portion of the swipe contact at the end position) rather than the entire swipe contact.

[0137] The intensity of a contact on the touch-sensitive surface is optionally characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an action different from an action normally associated with clicking a physical mouse button or trackpad. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device performs an action normally associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is not detected), the device follows the movement of the contact on the touch-sensitive surface and moves the focus selector without performing an action associated with the light press intensity threshold or the deep press intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent across various sets of values for a user interface.

[0138] An increase in the characteristic intensity of a contact from an intensity below the deep intensity threshold to an intensity above the deep intensity threshold may be referred to as inputting a "deep press." An increase in the characteristic intensity of a contact from an intensity below the light intensity threshold to an intensity between the light and deep intensity thresholds may be referred to as inputting a "light press." A decrease in the characteristic intensity of a 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 lift-off of the contact from the touch surface. An increase in the characteristic intensity of a contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light intensity threshold may be referred to as detecting contact on the touch surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.

[0139] In some embodiments described herein, one or more actions are performed in response to detecting a gesture including a respective press input or in response to detecting a respective press input performed by a respective contact (or multiple contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or multiple contacts) above a press input intensity threshold. In some embodiments, the press input includes an increase in intensity of the respective contact above the press input intensity threshold followed by a decrease in intensity of the contact below the press input intensity threshold, and the respective action is performed in response to detecting a subsequent decrease in intensity of the respective contact below the press input threshold (e.g., an "upstroke" of the respective press input). In some embodiments, the respective action is performed in response to detecting an increase in intensity of the respective contact above the press input intensity threshold (e.g., a "downstroke" of the respective press input).

[0140] 5E-5H illustrate the detection of a gesture including a press input corresponding to an increase in the intensity of contact 562 from an intensity below a light press intensity threshold (e.g., "ITL") in FIG. 5E to an intensity above a deep press intensity threshold (e.g., "ITD") in FIG. 5H. The gesture performed by contact 562 is detected on touch-sensitive surface 560, and cursor 576 is displayed over application icon 572B corresponding to app2 on displayed user interface 570, which includes application icons 572A-572D displayed within predefined region 574. In some embodiments, the gesture is detected on touch-sensitive display 504. An intensity sensor detects the intensity of the contact on touch-sensitive surface 560. Contact 562 is maintained on touch-sensitive surface 560. The device determines that the intensity of contact 562 peaks above a deep press intensity threshold (e.g., "ITD"). In some embodiments, this intensity, which is compared to one or more intensity thresholds, is a characteristic intensity of the contact. In response to detecting the gesture, contact 562 having an intensity above a deep press intensity threshold (e.g., "ITD") during the gesture causes reduced-scale representations 578A-578C (e.g., thumbnails) of recently opened documents to be displayed for app 2, as shown in Figures 5F-5H. Note that the intensity diagrams for contact 562 are not part of the displayed user interface, but are included in Figures 5E-5H as an aid to the reader.

[0141] In some embodiments, the display of representations 578A-578C includes animation. For example, as shown in FIG. 5F, representation 578A is initially displayed adjacent to application icon 572B. Representations 578A-578C form an array above icon 572B. As the animation progresses, representation 578A moves upward and representation 578B is displayed adjacent to application icon 572B, as shown in FIG. 5G. Then, as shown in FIG. 5H, representation 578A moves upward, representation 578B moves upward toward representation 578A, and representation 578C is displayed adjacent to application icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, as shown in FIGS. 5F-5G, with representations 578A-578C appearing and moving upward as the intensity of contact 562 increases toward a deep press intensity threshold (e.g., "ITD"). 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 can be performed using an electronic device similar to or identical to device 100, 300, or 500.

[0142] In some embodiments, the device employs intensity hysteresis to avoid accidental input, sometimes referred to as “jitter,” and the device defines or selects a hysteresis intensity threshold that has a predetermined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). In some embodiments, a press 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 press input intensity threshold, and optionally a subsequent decrease in the intensity of the contact back to an intensity below the hysteresis intensity, and a respective action is performed in response to detecting the press 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). In some embodiments, the press input includes an increase in the intensity of the respective contact above a press input intensity threshold, followed by a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and the respective action is performed in response to detecting the subsequent decrease in the intensity of the respective contact below the hysteresis intensity threshold (e.g., an “upstroke” of the respective press input).

[0143] For ease of explanation, descriptions of operations performed in response to a press input associated with a press input intensity threshold, or a gesture including a press input, are optionally triggered in response to detecting any of: an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold; an increase in the intensity of the contact above the press input intensity threshold; a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold; and / or a decrease in the intensity of the contact below the press input intensity threshold. Further, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of the contact below a press input intensity threshold, the operation 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 press input intensity threshold.

[0144] In some embodiments, electronic device 500 includes one or more tactile output generators that generate different types of tactile output sequences, as described in Table 1 below. When tactile outputs with different tactile output patterns are generated by the device (e.g., via one or more tactile output generators that move a moving mass to generate the tactile output), the tactile outputs can cause different tactile sensations when a user holds or touches the device. Although a user's sensations are based on the user's perception of the tactile output, most users are able to distinguish changes in the waveform, frequency, and amplitude of the tactile output generated by the device. In some embodiments, a particular type of tactile output sequence generated by one or more tactile output generators of the device corresponds to a particular tactile output pattern. For example, a tactile output pattern specifies characteristics of the tactile output, such as the amplitude of the tactile output, the shape of the moving waveform of the tactile output, the frequency of the tactile output, and / or the duration of the tactile output.

[0145] More specifically, Figures 5I-5K provide a set of sample tactile output patterns that may be used, either individually or in combination, either directly or through one or more transformations (e.g., modulation, amplification, truncation, etc.), to generate suitable tactile feedback for a variety of scenarios and purposes, such as those described above and with respect to the user interfaces and methods discussed herein. In addition to the tactile output patterns shown in these figures, each of these tactile output patterns is optionally adjusted in amplitude by varying the gain value for the tactile output pattern, as shown, for example, in Figures 5L-5N for FullTap 80 Hz, FullTap 200 Hz, MiniTap 80 Hz, MiniTap 200 Hz, MicroTap 80 Hz, and MicroTap 200 Hz, shown with gain variations of 1.0, 0.75, 0.5, and 0.25, respectively. This example palette of tactile outputs shows how a set of three waveforms and eight frequencies can be used to create an array of tactile output patterns. As shown in Figures 5L-5N, varying the gain of the tactile output pattern changes the amplitude of the pattern without changing the frequency or waveform shape of the pattern. In some embodiments, varying the frequency of the tactile output pattern also results in lower amplitudes. This is because some tactile output generators have limitations on the force they can apply to the moving mass. Therefore, mass movement at higher frequencies is constrained to lower amplitudes to ensure that the acceleration required to generate the waveform does not require forces outside the operating force range of the tactile output generator (e.g., the peak amplitudes of full taps at 230 Hz, 270 Hz, and 300 Hz are lower than those at 80 Hz, 100 Hz, 125 Hz, and 200 Hz).

[0146] FIGS. 5I-5N illustrate tactile output patterns having particular waveforms. The waveforms of a tactile output pattern represent the pattern of physical displacement relative to a neutral position (e.g., Xzero) versus the time that elapses before the movable mass generates a tactile output in that tactile output pattern. The example waveforms shown in FIGS. 5I-5N include Xmin and Xmax values that represent the maximum and minimum limits of the movable mass's movement. Larger electronic devices with larger movable masses may have larger or smaller minimum and maximum limits of mass movement. While the examples shown in FIGS. 5I-5N describe the movement of a mass in one dimension, similar principles would apply to the movement of a movable mass in two or three dimensions. For example, the first set of tactile output patterns (e.g., "full tap" tactile output patterns) shown in FIG. 5I each have waveforms that include oscillations with two complete cycles (e.g., oscillations that start and end at the neutral position and cross the neutral position three times). A second set of tactile output patterns (e.g., "mini-tap" tactile output patterns) shown in Figure 5J each have waveforms that include oscillations that include one full cycle (e.g., oscillations that start and end at a neutral position and cross the neutral position once). A third set of tactile output patterns (e.g., "micro-tap" tactile output patterns) shown in Figure 5K each have waveforms that include oscillations that include one-half of a full cycle (e.g., oscillations that start and end at a neutral position and do not cross the neutral position). The tactile output pattern waveforms also include start and end buffers that represent the gradual acceleration and deceleration of the moving mass at the beginning and end of the tactile output.

[0147] As shown in FIGS. 5I-5K, each tactile output pattern also has a corresponding characteristic frequency that affects the tactile "pitch" a user experiences from a tactile output having that characteristic frequency. For discrete tactile outputs, a discrete output signal (e.g., having 0.5, 1, or 2 cycles) is generated, and the characteristic frequency value specifies how fast the moving mass must move to generate a tactile output having that characteristic frequency. For continuous tactile outputs, the characteristic frequency represents the number of cycles (e.g., cycles per second) completed by the moving mass of the tactile output generator within a given period of time. As shown in FIGS. 5I-5N, for each type of tactile output (defined by a respective waveform, such as a full tap, mini tap, or micro tap), a higher frequency value corresponds to a faster movement(s) of the moving mass and, therefore, generally, a shorter time to complete the tactile output (e.g., including the time to complete the number of cycles required for the discrete tactile output plus the start and end buffer times). For example, a full tap with a characteristic frequency of 80 Hz takes longer to complete than a full tap with a characteristic frequency of 100 Hz (e.g., 35.4 ms vs. 28.3 ms in FIG. 5I). Additionally, for a given frequency, a tactile output with more cycles in its waveform at each frequency takes longer to complete than a tactile output with fewer cycles in its waveform at the same respective frequency. For example, a full tap at 150 Hz takes longer to complete than a mini-tap at 150 Hz (e.g., 19.4 ms vs. 12.8 ms), which in turn takes longer to complete than a micro-tap at 150 Hz (e.g., 12.8 ms vs. 9.4 ms). However, this regularity may not hold for tactile output patterns of different frequencies (e.g., a tactile output with more cycles but a higher frequency may take less time to complete than a tactile output with fewer cycles but a lower frequency, and vice versa). For example, at 300 Hz, a full tap takes just as long as a mini tap (eg, 9.9 ms).

[0148] As shown in FIGS. 5I-5K, the tactile output pattern also has a characteristic amplitude, which affects the amount of energy contained in the tactile signal, or the tactile "intensity" that a user may feel due to a tactile output having that characteristic amplitude. In some embodiments, the characteristic amplitude of the tactile output pattern is adjustable, for example, by a gain factor (e.g., a value between 0 and 1) that is fixed or dynamically determined according to various conditions (e.g., customized based on the context and behavior of the user interface) and / or a pre-set metric (e.g., an input-based metric and / or a user-interface-based metric). In some embodiments, the characteristic amplitude of the tactile output pattern refers to an absolute or normalized value that represents the maximum displacement of the moving mass from a neutral position when generating a tactile output. In some embodiments, a user-interface-based metric (e.g., a boundary-crossing velocity metric) indicates a characteristic of a user interface element during a change in the user interface that triggers the generation of a tactile output (e.g., the velocity of an element's movement across a hidden or visible boundary in the user interface). In some embodiments, an input-based metric (e.g., an intensity change metric or an input velocity metric) evaluates a characteristic of the input during input that triggers generation of the tactile output (e.g., the rate of change of the characteristic intensity of the contact in a press input, or the velocity of movement of the contact across the touch-sensitive surface). In some embodiments, the characteristic amplitude of the tactile output pattern may be modulated by an "envelope," where peaks in adjacent cycles may have different amplitudes, and one of these waveforms may be further modulated by an envelope parameter multiplication that varies over time (e.g., from 0 to 1), gradually adjusting the amplitude of portions of the tactile output over time while the tactile output is being generated.

[0149] While Figures 5I-5K depict specific amplitudes, frequencies, and waveforms of sample tactile output patterns for illustrative purposes, tactile output patterns having other amplitudes, frequencies, and waveforms may be used for similar purposes. Other frequencies ranging from 60 Hz to 400 Hz may also be used. For example, waveforms having 0.5 to 4 cycles may be used. Table 1 below provides representative examples of tactile output / haptic feedback behaviors and configurations and their use with respect to user interfaces for managing content-based tactile output illustrated and described herein. [Table 1]

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

[0151] As used herein, the terms "running application" or "open application" refer to a software application that has state information 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 application: ● the active application currently displayed on the display screen of the device on which the application is being used; Suspended or hibernated applications that are not running but have state information stored in memory (volatile and non-volatile, respectively) and that can be used to resume the execution of the application; and ● 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.

[0152] Generally, opening a second application while a first application is running does not close the first application. When a second application is displayed and the first application is terminated, the first application becomes a background application. As used herein, the term "closed application" refers to a software application that does not have retained state information (e.g., state information for a closed application is not stored in the device's memory). Thus, closing an application includes stopping and / or removing the application process for the application and removing state information for the application from the device's memory.

[0153] Attention is now directed to embodiments of user interfaces (“UIs”) and related processes implemented on an electronic device such as portable multifunction device 100, device 300, or device 500. User Interface and Related Processes Initialize the remote locator object

[0154] Users interact with electronic devices in many different ways. In some embodiments, the electronic device can track the location of an object, such as a remote locator object. In some embodiments, a remote locator object that supports location tracking functionality can be attached to an item that does not support location tracking functionality. The embodiments described below provide a way for an electronic device to initialize a remote locator object, thereby enhancing a user's interaction with the electronic device. Enhancing interaction with the device reduces the amount of time a user needs to perform an action, thus reducing the device's power usage and increasing battery life for battery-powered devices. It is understood that people use devices. When a person uses a device, that person is optionally referred to as the device's user.

[0155] 6A-6T illustrate example methods by which an electronic device initializes a remote locator object according to some embodiments of the present disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to FIGS. 7A-7D.

[0156] 6A-6T illustrate an electronic device 500 initializing a remote locator object. FIG. 6A illustrates an exemplary device 500 including a touchscreen 504. As shown in FIG. 6A, the electronic device 500 presents a home screen user interface 610. In some embodiments, the home screen user interface 610 is an application launch user interface. For example, the home screen user interface 610 includes multiple selectable options (e.g., icons 424, 426, 416, 432, 434, 436, 440, 446, 450, and 452) that, when selected, cause the electronic device 500 to launch or otherwise present applications. In some embodiments, the home screen user interface 610 includes multiple pages or tabs and includes all launchable applications installed on the electronic device 500. In some embodiments, the home screen user interface 610 includes a subset of the launchable applications installed on the electronic device 500.

[0157] 6A also shows exemplary remote locator object 600 in an uninitialized state. In some embodiments, the remote locator object is a device that includes a battery, one or more wireless antennas, and a low-power processor that enables the device to function as a dedicated remote locator object when associated with another physical object (e.g., a wallet, a handbag, a backpack, a suitcase, a car, a set of keys, etc.). In some embodiments, the remote locator object is a multi-purpose device with location tracking capabilities, such as a smartphone, a tablet, a computer, or a watch. In some embodiments, the remote locator object 600 can transmit location data to an electronic device. For example, the remote locator object 600 optionally includes a GPS locator. In some embodiments, the remote locator object 600 does not include location tracking capabilities and relies on other electronic devices (e.g., device 500, etc.) to receive location data. In some embodiments, the remote locator object 600 can wirelessly communicate with other electronic devices, such as electronic device 500 (e.g., via Bluetooth, RF, IR, NFC, etc.). In some embodiments, a remote locator object has an uninitialized state and an initialized state. For example, when a remote locator object is first manufactured, the remote locator object is in the uninitialized state. In the uninitialized state, the remote locator object is not assigned a label or associated with any particular user or user account. In the initialized state, the remote locator object is assigned a label and / or associated with a respective user or user account. In some embodiments, initializing the remote locator object includes transferring initialization data to the remote locator object and storing the data on the remote locator object.In some embodiments, the remote locator object does not store the initialization data; instead, the electronic device (e.g., device 500) or a server stores the initialization data and associates the data with the remote locator object's unique identifier (e.g., serial number).

[0158] In some embodiments, when the remote locator object 600 is placed within a threshold distance (e.g., 1 inch, 2 inches, 5 inches, etc.) of the device 500, the remote locator object 600 pairs with, or more generally, communicates with, the electronic device 500, as shown in FIG. 6B. In some embodiments, pairing the remote locator object 600 with the electronic device 500 includes establishing an NFC communication link between the remote locator object 600 and the electronic device 500. In some embodiments, the electronic device 500 receives identification information from the remote locator object 600 (e.g., the remote locator object's serial number, etc.). In some embodiments, the remote locator object 600 uses the electronic device 500's location tracking capabilities to update its internal location information. In some embodiments, the remote locator object 600 can upload its location information to a server. In some embodiments, the remote locator object 600 can upload its location data to a server via a wireless communication link (e.g., Bluetooth, WiFi, etc.). In some embodiments, the remote locator object 600 can communicate with an electronic device (e.g., device 500) and upload location data even if the remote locator object 600 has not previously been paired with the electronic device (e.g., while the remote locator object 600 is in an uninitialized state, or while the remote locator object 600 is in an initialized state but not paired with a respective electronic device).

[0159] In some embodiments, in response to placing the remote locator object 600 adjacent to the electronic device 500, the electronic device 500 displays a user interface 620 to complete the pairing (e.g., initialization) process, as shown in FIG. 6C . In some embodiments, the user interface 620 is an overlay superimposed on a user interface (e.g., user interface 610) that was displayed on the device 500 before pairing was initiated. In some embodiments, the user interface 620 includes a representation 622 of the remote locator object 600. In some embodiments, the representation 622 is an icon of the remote locator object 600. In some embodiments, the representation 622 is a three-dimensional and / or interactable model of the remote locator object 600. For example, in some embodiments, a user input on the representation 622 optionally causes the representation 622 to spin or rotate in accordance with the user input. In some embodiments, the representation 622 spins, rotates, or otherwise animates on its own (e.g., without user intervention). For example, Figures 6D-6E show a representation 622 that rotates without user input.

[0160] In some embodiments, user interface 620 includes selectable option 624 (e.g., a button, an affordance, etc.). In some embodiments, selection of selectable option 624 initiates a process to initialize (e.g., configure, etc.) remote locator object 600 and pair remote locator object 600 with electronic device 500 and / or a user account associated with device 500. In FIG. 6E, user input 603 is received selecting selectable option 624 indicating a user's request to initialize remote locator object 600 and connect (e.g., pair) remote locator object 600 to electronic device 500. In response to the user input, device 500 displays user interface 630, as shown in FIG. 6F.

[0161] In some embodiments, user interface 630 is a user interface for selecting a label (e.g., a name or other identifier) for remote locator object 600. In some embodiments, user interface 630 includes one or more predefined labels (e.g., "bag," "backpack," "key") that the user can select as a label for object 600. In some embodiments, the one or more predefined labels are provided as a list 632 of options. In some embodiments, list 632 is scrollable to reveal more predefined labels. In some embodiments, list 632 is displayed in a rolodex style, with the central item being the largest and the size of the items decreasing based on distance from the center. For some items, the central item is the currently selected item, as indicated by box 634.

[0162] In some embodiments, list 632 includes a custom option (e.g., "Other") for providing a custom label. FIGS. 6F-6H show a sequence of one or more user inputs to navigate to and select the custom option. In some embodiments, in response to the user input, the device displays a virtual keyboard 638, such as in FIG. 6I. In some embodiments, the "Other" option becomes a text entry field 634. In some embodiments, the user can use virtual keyboard 638 to enter a custom identifier into text field 634.

[0163] In some embodiments, user interface 636 includes a selectable option 636 to confirm the label to be used for the remote locator object 600. In some embodiments, after the user confirms the label of the remote locator object 600, device 500 displays user interface 640, as shown in FIG. 6J. In some embodiments, user interface 640 is a connection progress splash user interface indicating that the pairing process is underway. In some embodiments, user interface 640 includes a representation 622 of the remote locator object 600. In some embodiments, user interface 640 displays the selected identifier in the user's name (e.g., "John's Key," so that the remote locator object 600 is, or is attached to, John's key). In some embodiments, pairing to the remote locator object 600 includes creating a profile on electronic device 500 (e.g., and / or on a cloud server) specific to the remote locator object 600.

[0164] In some embodiments, after the pairing process is successfully completed and the remote locator object 600 is initialized, the device 500 displays a user interface 650, as shown in FIG. 6K. In some embodiments, the user interface 650 includes a label 652 indicating the remote locator object being displayed on the user interface 650 (e.g., the remote locator object 600, "John's Keys"). In some embodiments, the user interface 650 includes a label 654 indicating the location status of the remote locator object 600. In some embodiments, the location status of the remote locator object 600 is that it is within a threshold distance (e.g., 1 foot, 2 feet, 3 feet, etc.) from the user such that the "With You" label is displayed. In some embodiments, the label 654 additionally or alternatively includes an indication of when the location of the remote locator object 600 was most recently updated. For example, as shown in FIG. 6K, the location data of the remote locator object 600 was updated "just now" (e.g., within 1 second, within 30 seconds, within 1 minute, within 2 minutes, etc.).

[0165] In some embodiments, user interface 650 includes a map 656. In some embodiments, map 656 displays a map of locations around remote locator object 600 (e.g., a 1-mile radius, a 2-mile radius, a give mile radius, etc.). In some embodiments, map 656 includes an icon 658 representing remote locator object 600. In some embodiments, icon 658 indicates the current location of remote locator object 600. In some embodiments, user interface 650 includes one or more functions available for remote locator object 600 that are selectable to view or activate the respective function. For example, selectable option 659-1 corresponds to a location discovery function for remote locator object 600. In some embodiments, selection of selectable option 659-1 causes the display of a user interface for locating remote locator object 600 in an application for tracking and finding items (e.g., similar to the processes described below with respect to methods 1300 and 1400). In some embodiments, selectable option 659-2 corresponds to a separation warning function for remote locator object 600. In some embodiments, selection of selectable option 659-2 toggles the separation warning feature on or off. Separation warnings for remote locator objects are described in more detail below with respect to method 900. In some embodiments, selectable option 659-3 causes the display of a user interface for selecting and / or managing trusted locations and / or people for remote locator object 600. Trusted locations for remote locator objects are described in more detail below (as described in more detail below with respect to method 900). In some embodiments, selectable options 659-1 through 659-3 are not selectable options, but rather non-interactive indicators that show the user available features.

[0166] In some embodiments, user interface 650 includes selectable option 657-1. In some embodiments, selection of selectable option 657-1 causes display of an application for tracking and finding items (e.g., a "Discover" app) and navigation to a user interface within the application for managing (e.g., viewing and editing) settings for remote locator object 600. In some embodiments, user interface 650 includes selectable option 657-2 that is selectable to dismiss user interface 650 and display the user interface that was displayed before initialization began (e.g., user interface 610).

[0167] In Figure 6K, user input 603 is detected selecting selectable option 657-1, which corresponds to a request to customize the settings of remote locator object 600. In some embodiments, in response to user input 603, electronic device 500 displays user interface 660, as shown in Figure 6L. In some embodiments, user interface 660 is a user interface of an application for tracking and locating items (e.g., electronic device 500 launched the application in response to user input 603).

[0168] In FIG. 6L , user interface 660 includes a label 662 indicating the remote locator object being displayed on user interface 660 (e.g., remote locator object 600, "John's Key"). In some embodiments, user interface 660 includes a label 664 indicating the location status of remote locator object 600. In some embodiments, the location status of remote locator object 600 is that it is within a threshold distance (e.g., 1 foot, 2 feet, 3 feet, etc.) from the user such that the "With You" label is displayed. In some embodiments, label 664 additionally or alternatively includes an indication of when the location of remote locator object 600 was most recently updated. For example, as shown in FIG. 6L , the location data for remote locator object 600 was updated "just now" (e.g., within 1 second, within 30 seconds, within 1 minute, within 2 minutes, etc.). In some embodiments, label 664 includes a description of the location closest to where remote locator object 600 is located. For example, as shown in FIG. 6L, remote locator object 600 is determined to be "near home."

[0169] In some embodiments, user interface 660 includes selectable option 666-1 and selectable option 666-2 corresponding to features available to remote locator object 600. In some embodiments, selection of selectable option 666-1 causes the display of a user interface for locating remote locator object 600 (e.g., similar to the processes described below with respect to methods 1300 and 1400). In some embodiments, selection of selectable option 666-2 causes remote locator object 600 to emit an audible sound. In some embodiments, selectable option 666-2 is a toggle button, and remote locator object 600 emits an audible sound continuously until electronic device 500 receives a second user input that selects selectable option 666-2 and disables the audible sound. In some embodiments, selectable option 666-2 is not a toggle button, and remote locator object 600 emits an audible sound as long as the user selects selectable option 666-2. Thus, in some embodiments, remote locator object 600 emits an audible tone only while the user selects selectable option 666-2.

[0170] In some embodiments, user interface 660 includes an option to set notification settings for the remote locator object 600. In some embodiments, the notification settings include a selectable option 668 that is selectable to edit notification settings regarding separation alerts. In some embodiments, user interface 660 includes options to add and / or manage people with whom the remote locator object 600 is shared. In some embodiments, if the remote locator object 600 is not currently shared with anyone, selectable option 669 displays "Add People." Separation alert and sharing operations are described in more detail below with respect to FIGS. 8A-8P. In some embodiments, user interface 660 includes a selectable option 667 to change the name (e.g., label) of the remote locator object 600. In some embodiments, as shown in FIG. 6M (after scrolling down the user interface), user interface 600 includes a selectable option 665 to mark the remote locator object 600 as lost. Further discussion of the characteristics of a remote locator object being marked as lost is discussed in more detail below with respect to Figures 10N-10R.

[0171] In some embodiments, user interface 660 includes a selectable option 663 to dismiss user interface 660 (e.g., complete setting options for remote locator object 600). In FIG. 6M, user input 603 is received selecting selectable option 663. In some embodiments, in response to user input 603, electronic device 500 dismisses user interface 660 and displays user interface 670, as shown in FIG. 6N. In some embodiments, user interface 670 is the home screen of an application for tracking and finding items (e.g., a "Discover" app). In some embodiments, user interface 670 includes a map 672 and a list 676 of tracked items. In some embodiments, map 672 includes an icon 674-1 that indicates the current location of electronic device 500. In some embodiments, map 672 includes an icon that indicates the location of a tracked item. For example, in some embodiments, map 672 includes an icon 674-2 that indicates the location of a "spouse's key." In some embodiments, the map 672 does not display icons for items that are determined to be with the electronic device (e.g., with the user). In some embodiments, the map 672 displays icons for items that are determined to be with the electronic device (e.g., with the user, such as keys).

[0172] In some embodiments, list 676 includes one or more items whose locations are being tracked. For example, in FIG. 6N, list 676 includes items 678-1 through 678-3. In embodiments, each item includes an icon (e.g., or other representation) corresponding to the item, a label for the item (e.g., key, spouse's key, tablet, etc.), and location information for the item (e.g., with you, near spouse's work, home). In some embodiments, the item includes information about whether notifications for the item have been ignored and the time remaining to ignore notifications for the item (e.g., as described in more detail). In some embodiments, the item includes information about when location information was last updated (e.g., as described in more detail). In some embodiments, the item includes information about how far the item is from the user (e.g., 1 foot away, 5 miles away, 15 feet away, etc.). In some embodiments, each of items 678-1 through 678-4 is selectable to display a user interface specific to the respective item (e.g., similar to the user interfaces described with reference to FIGS. 6L-6M). In Figure 6N, list 676 includes list item 678-1 corresponding to the user's key, list item 678-2 corresponding to the user's spouse's key, and list item 678-3 corresponding to the user's tablet. As shown in Figure 6N, user interface 670 displays location information for the user's remote locator object (item 678-1), remote locator objects shared with the user (e.g., item 678-2), electronic devices (e.g., item 678-3), and optionally other people (not shown). In some embodiments, list 676 is a scrollable list that can be scrolled to display more tracked items. In some embodiments, map 672 displays only the items displayed in list 676, and scrolling through list 676 causes map 672 to update to show the location of the item currently displayed in list 676.In some embodiments, the map 672 displays all items that are being tracked and not just the items currently displayed in the list 676 .

[0173] 6O-6T illustrate embodiments in which device 500 is placed within a threshold distance of a remote locator object that is already in an initialized state. FIG. 6O shows device 500 and remote locator object 600. In FIG. 6O, remote locator object 600 has been initialized and previously associated with the user and / or user account of device 500. Thus, in some embodiments, remote locator object 600 is paired with device 500. In FIG. 6P, device 500 is placed at a threshold distance (e.g., within NFC communication range) of remote locator object 600. In some embodiments, in response to placing device 500 within the threshold distance of remote locator object 600, device 500 communicates with remote locator object 600 and displays user interface 680 superimposed on a user interface previously displayed on device 500. In some embodiments, user interface 680 is a "quick" control sheet displaying one or more selectable options for performing a subset of the functions available in remote locator object 600. In FIG. 6P, user interface 680 includes a selectable toggle 682 for toggling separation warnings on or off (e.g., as described in further detail below with respect to FIGS. 8A-8P). In some embodiments, toggle 682 includes a textual description of how many location exceptions apply to remote locator object 600 (e.g., as described in further detail below with respect to FIGS. 8A-8P). In some embodiments, user interface 680 includes a selectable option 684 that is selectable to display navigation to a user interface within an application for tracking and finding items (e.g., a "Discover" app) and an application for managing (e.g., viewing and editing) settings for remote locator object 600 (e.g., similar to user interface 660 described above with respect to FIGS. 6L-6M).

[0174] FIG. 6Q shows device 500 and remote locator object 600. In FIG. 6Q, remote locator object 600 has been initialized and is associated with another user (e.g., not the user or user account of device 500). In FIG. 6Q, remote locator object 600 is not associated with the user of the device and is not currently sharing location information with the user of device 500. In FIG. 6R, device 500 is placed at a threshold distance (e.g., within NFC communication range) of remote locator object 600. In response to placing device 500 within the threshold distance of remote locator object 600, device 500 communicates with remote locator object 600 and displays user interface 690 superimposed on a user interface previously displayed on device 500. In some embodiments, user interface 690 is a “quick” control sheet that displays one or more selectable options for performing functions available in remote locator object 600. 6R, because the remote locator object 600 is not associated with or shared with the user, user interface 690 includes selectable option 692 and selectable option 694. In some embodiments, selectable option 692 is selectable to ignore the remote locator object 600 (e.g., to suppress tracking alerts, as described in more detail below with respect to FIGS. 10A-10R). In some embodiments, selectable option 694 is selectable to request a share of the remote locator object 600 from the owner of the remote locator object 600.

[0175] In FIG. 6R, user input 603 is received selecting selectable option 694. In some embodiments, in response to the user input, a notification 696 is displayed on the device (e.g., device 500) of the owner of the remote locator object 600 (e.g., the user account associated therewith), as shown in FIG. 6S. In some embodiments, the notification 696 indicates to the owner of the remote locator object 600 that a person (e.g., John) has requested to share the remote locator object 600. In some embodiments, the notification 696 is selectable to display options for sharing the remote locator object 600. For example, in FIG. 6S, user input 603 is received selecting the notification 696. In some embodiments, in response to the user input, the device 500 displays a user interface 698. In some embodiments, the user interface 698 is a user interface for managing users with whom the respective remote locator object is shared, as described in more detail below with respect to FIGS. 8K-8N. In some embodiments, user interface 698 is automatically displayed with the requestor, and the owner of the remote locator object can select the requestor and begin the process of sharing the remote locator object with the requestor (e.g., without the owner having to search for or otherwise enter the requestor's account information).

[0176] 7A-7D are flow diagrams illustrating a method 700 for initializing a remote locator object according to some embodiments, such as Figures 6A-6T. Method 700 is optionally performed on an electronic device, such as device 100, device 300, or device 500, as described above with reference to Figures 1A-1B, 2-3, 4A-4B, and 5A-5H. Some operations in method 700 are optionally combined and / or the order of some operations is optionally changed.

[0177] As described below, method 700 provides a way to initialize a remote locator object. This method reduces the cognitive burden on a user when interacting with the user interface of a device of the present disclosure, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, improving the efficiency of the user's interaction with the user interface conserves power and increases the time between battery charges.

[0178] In some embodiments, such as in FIG. 6B , an electronic device having one or more wireless antennas, a display device, and one or more input devices (e.g., a mobile device (e.g., a tablet, smartphone, media player, or wearable device) including a touchscreen and wireless communication circuitry, or a computer including one or more of a keyboard, mouse, trackpad, and touchscreen, and wireless communication circuitry) detects (702) via one or more wireless antennas, such as in FIG. 6B , that a remote locator object (e.g., a device capable of communicating with the electronic device wirelessly, such as via Bluetooth and / or WiFi (the device may optionally be attached to a user's item, such as a user's key, a user's handbag, etc.)) is in the vicinity of the electronic device.

[0179] In some embodiments, in response to detecting that a remote locator object is near the electronic device (e.g., within a threshold distance, such as 5, 10, or 20 feet, within the effective range of a wireless communication protocol, such as NFC, Bluetooth, or WiFi), the electronic device displays (704) via the display device a configuration user interface for configuring the remote locator object within a predetermined region of the display, such as that shown in FIG. 6C (e.g., displayed in an overlay over what was displayed via the display device before the remote locator object was detected near the electronic device, such as an overlay over the bottom half or third of the displayed content). In some embodiments, the configuration user interface is not displayed if the remote locator object has previously been configured by this or another electronic device.

[0180] In some embodiments, after displaying the settings user interface via the display device, the electronic device displays (706) an identifier user interface for selecting an identifier for the remote locator object, such as in FIG. 6F , within a predefined region of the user interface displayed via the display device (e.g., in response to selection of a settings affordance for configuring the remote locator object). In some embodiments, selection of the settings affordance causes the remote locator object and / or the electronic device to enter a configuration process, which includes initializing the remote locator object, pairing the remote locator object with the electronic device, or otherwise identifying the remote locator object as owned by the user of the electronic device, and / or configuring the behavior of the remote locator object and / or the electronic device. In some embodiments, the identifier user interface is also displayed as an overlay on top of what was displayed before the remote locator object was detected near the electronic device. In some embodiments, the identifier user interface is a user interface of the settings user interface (e.g., a displayed page on a settings user interface overlay object). In some embodiments, the identifier user interface includes one or more predefined identifiers (e.g., “key,” “handbag,” “backpack,” etc.). In some embodiments, the user can provide a custom identifier, hi some embodiments, the identifiers are displayed in a scrollable list or a scrollable rolodex.

[0181] In some embodiments, while displaying the identifier user interface, the electronic device detects one or more user inputs via one or more input devices (708) selecting a corresponding identifier for the remote locator object, such as in FIG. 6G (e.g., receives user input selecting a name for the remote locator object, such as “key,” “handbag,” etc., that provides a description of the remote locator object). In some embodiments, after the corresponding identifier for the remote locator object is selected (e.g., in response to receiving input to proceed through a configuration user interface or in response to selecting a default identifier for the remote locator object), the electronic device displays (710) a user interface with additional information regarding the functionality of the remote locator object, including a description of at least one function of the remote locator object, such as in FIG. 6K (e.g., displays a configuration confirmation page or a configuration summary page for the remote locator device). In some embodiments, the configuration confirmation page provides the user with one or more selectable options for performing other configuration processes or selecting other settings for the remote locator object. For example, the configuration confirmation page includes a selectable option to launch an application dedicated to managing and locating remote locator objects and / or other electronic devices. In some embodiments, the settings confirmation page includes indicators of different functionality available for the remote locator object, for example, the remote locator object can optionally be wirelessly discovered (e.g., provide relative or absolute location information to the electronic device so that the electronic device can triangulate the relative or absolute location of the remote locator object), which is indicated in the additional information, the remote locator object can optionally cause a warning to be displayed on the electronic device when the remote locator object is separated from the electronic device, which is indicated in the additional information, etc.In some embodiments, the electronic device also identifies the remote locator object with a combination of a corresponding identifier and the name of the user of the device (e.g., labeling the remote locator object with the user's name and an indication that the remote locator object is associated with a "key" or a "handbag," etc.).

[0182] The above-described method of configuring a remote locator object (e.g., by detecting the presence of a remote locator object and displaying a configuration user interface for selecting an identifier and accessing the functionality of a remote indicator object) provides a user with the ability to configure the remote locator object (e.g., by displaying a configuration user interface that allows the user to assign a label to the remote locator object and perform other configuration functions), thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing the user with a way to remotely configure the remote locator object without requiring a dedicated device to perform the configuration of the remote locator object), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0183] In some embodiments, the configuration user interface is displayed (712) when the remote locator object is detected near the electronic device while the remote locator object is in a first state (e.g., an initial state where the remote locator object is not configured (e.g., not currently configured with a user account)), such as in FIG. 7C . In some embodiments, when the device is in the initial state where the remote locator object is not configured, the electronic device displays the configuration user interface when the electronic device is placed near the remote locator object indicating a request to configure the remote locator object. In some embodiments, placing the electronic device near the remote locator object creates a wireless communication connection between the electronic device and the remote locator object (e.g., via a wireless communication protocol such as NFC, Bluetooth, WiFi Direct, or WiFi). In some embodiments, after establishing the wireless communication connection, the electronic device determines that the remote locator object is in the initial state (e.g., the remote locator object sends a signal to the electronic device that the remote locator object is in the initial state). In some embodiments, a remote locator object is in a first state (e.g., an initial state) if the remote indicator object has never been configured on any electronic device, has never been configured on its corresponding electronic device (e.g., optionally, has been configured on another electronic device but not on its corresponding electronic device), or has been reset to factory settings (e.g., a factory reset). In some embodiments, if the remote locator object is not in the first state (e.g., an initial state), detecting the remote locator object near the electronic device does not cause the display of a configuration user interface. In some embodiments, instead of the configuration user interface, a different user interface is displayed on the electronic device for performing other functions associated with the remote locator object other than configuring the remote locator object.

[0184] The above-described method of configuring a remote locator object (e.g., by detecting the presence of the remote locator object when the remote locator object is in a first state) provides a user with the ability to configure the remote locator object when the remote locator object is in an appropriate state for configuration (e.g., by displaying a configuration user interface when the remote locator object has not yet been configured) and does not provide a user with the ability to configure the remote locator object when the remote locator object is not in an appropriate state for configuration, thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by automatically determining that the remote locator object has not yet been configured and that configuration is required when the remote locator object is placed near the electronic device, and displaying a configuration user interface), and additionally reducing power usage and improving the battery life of the electronic device by allowing a user to use the electronic device more quickly and efficiently.

[0185] In some embodiments, the default region occupies less than all of the displayed user interface, and a representation of at least a portion of the user interface that was displayed (immediately prior to) detecting the remote locator object near the electronic device is displayed (714) over a portion of the user interface that is outside the default region, such as in FIG. 6C (e.g., the configuration user interface is displayed superimposed over an application or home screen that is not associated with the remote locator object). For example, if the electronic device is displaying a respective user interface (e.g., of a particular application or system user interface) and then the user interacts with the electronic device to initiate a remote locator object configuration process (e.g., by placing the remote locator object near the electronic device), the configuration user interface is displayed in an overlay over what was previously displayed (the user interface of the particular application or system user interface). In some embodiments, the overlay is displayed superimposed over the bottom (e.g., bottom half, bottom third, bottom quarter, etc.) of the displayed content.

[0186] The above-described methods of displaying a configuration user interface (e.g., by displaying a user interface that occupies less than all of the user and is overlaid on top of a user interface that was previously displayed before entering the configuration process) provide the user with a minimally intrusive user interface for configuring a remote locator object (e.g., by displaying a configuration user interface that does not encompass the entire screen and is overlaid on top of previously displayed content), thereby simplifying the interaction between the user and the electronic device, improving usability of the electronic device, making the user-device interface more efficient (e.g., by allowing the user to quickly return to the previous interface after completing the configuration process without having to navigate away from the previously displayed user interface and navigate back to that user interface after completing configuration of the remote locator object, or by allowing the user to maintain a view of the previous user interface while performing configuration of the remote locator object), and additionally reducing power usage and improving battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0187] In some embodiments, the identifier user interface includes a plurality of predefined identifiers (e.g., keys, cars, handbags, computers, backpacks, etc.) (716), such as in FIG. 6F. In some embodiments, a predefined identifier from the plurality of predefined identifiers is selectable to set the identifier of the remote locator object being configured. For example, if a user (e.g., John) selects the predefined identifier "keys," the remote locator object is hereafter referred to as "John's keys." In some embodiments, the plurality of predefined identifiers are displayed in a scrollable list or rolodex-style list. In some embodiments, after selecting an identifier from the identifier user interface, the configuration process performs an initialization of the remote locator object and displays a user interface indicating that the electronic device is connected to the remote locator object.

[0188] The above-described method of configuring a remote locator object (e.g., by displaying multiple predefined identifiers for the user to select from) allows for quick selection of an identifier for a remote locator object, thereby simplifying interaction between the user and the electronic device, improving usability of the electronic device, making the user-device interface more efficient (e.g., by providing the user with commonly used identifiers and allowing the user to quickly select the identifier that best matches the remote locator object being configured), and additionally reducing power usage and improving battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0189] In some embodiments, detecting one or more user inputs selecting the corresponding identifier for the remote locator object includes detecting user input to provide a custom identifier (736), such as in FIG. 6I (e.g., the identifier user interface includes an option for the user to provide a custom identifier). In some embodiments, the option for the user to provide a custom identifier is displayed along with a list of multiple predefined identifiers (e.g., at the bottom of a scrollable or rolodex-style list). For example, one of the identifier options in the list containing multiple predefined identifiers is an option to provide a custom identifier (e.g., an “Other” option). In some embodiments, selection of the option to provide a custom identifier causes a virtual keyboard to be displayed for the user to provide the custom identifier. In some embodiments, the virtual keyboard (e.g., a soft keyboard) is displayed at the bottom of the screen and displaces the identifier user interface upward. In some embodiments, after the user enters the custom identifier text and dismisses the virtual keyboard, the identifier user interface returns to its original position before being displaced by the virtual keyboard.

[0190] The above-described method of configuring a remote locator object (e.g., by receiving a custom identifier from a user) allows for more flexible / robust device configuration (e.g., by receiving user input providing a custom identifier for the remote locator object), thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing the user with the ability to select from multiple predefined identifiers as well as the ability to provide a custom identifier), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0191] In some embodiments, displaying the configuration user interface includes displaying a pairing animation including a representation of the remote locator object and a selectable affordance for initiating the pairing process (e.g., displaying an image or animation of the remote locator object), such as in FIG. 6J . In some embodiments, the animation of the remote locator object is a three-dimensional object (e.g., a 3D model) that automatically rotates. In some embodiments, a user can interact with the animation of the remote locator object to rotate the remote locator object according to the user's interaction. In some embodiments, the configuration user interface includes a selectable option (e.g., an affordance) (e.g., a “Connect” button) that initiates the process of pairing the remote locator object with the electronic device. In some embodiments, after receiving input from a user selecting the selectable option to initiate the pairing process (e.g., user input corresponding to a request to pair the remote locator object with the electronic device), the configuration user interface displays a user interface indicating that the pairing process is in progress (e.g., the configuration user interface displays “Connecting”). In some embodiments, after selecting a selectable option that initiates the process of pairing the remote locator objects, the configuration user interface displays an identifier user interface for the user to select an identifier for the remote locator object.

[0192] The above-described method of configuring a remote locator object (e.g., by displaying a pairing animation for the remote locator object and a selectable option to initiate configuration of the remote locator object) provides the user with confirmation that they intend to initiate configuration of the remote locator object (e.g., by displaying a representation of the remote locator object and initiating the configuration process after the user selects a selectable option to confirm that they wish to initiate configuration of the remote locator object), thereby simplifying the interaction between the user and the electronic device and improving usability of the electronic device, making the user-device interface more efficient (e.g., by providing the user with the ability to confirm configuration of the remote locator object without initiating the configuration process when the user unintentionally places the electronic device near the remote locator object without intending to configure the remote locator object), and additionally reducing power usage and improving battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently while reducing errors in use of the device.

[0193] In some embodiments, the user interface with additional information regarding the remote locator object's capabilities includes a map with an indication of the remote locator object's location (720), where the remote locator object is identified by a corresponding identifier and the name of the device's user, such as in FIG. 6K (e.g., displayed in the user interface with additional information regarding the remote locator object's capabilities after completing a setup process to pair the remote locator object with the electronic device). In some embodiments, the user interface with additional information includes an indication (e.g., title, label, etc.) that the user interface refers to the remote locator object that was just paired using the selected identifier (e.g., "John's key"). In some embodiments, the user interface with additional information includes a map of the remote locator object's current location. In some embodiments, the map includes an indicator of the remote locator object's current location and / or the electronic device's current location. In some embodiments, the map includes locations of other objects (e.g., other remote locator objects, other devices, etc.) being tracked by the electronic device. In some embodiments, the map displays only the remote locator object's current location without displaying the locations of other devices being tracked by the electronic device. In some embodiments, the indicator of the current location of the remote locator object is an icon representing the remote locator object (eg, a key icon).

[0194] The above-described method of completing the configuration of a remote locator object (e.g., by displaying in a user interface additional information about the remote locator object, including a map of the remote locator object's current location) provides the user with confirmation that the remote locator object was successfully configured and its current location (e.g., by displaying information about the remote locator object's current location, the remote locator object's selected identifier, and associated functions that can be performed), thereby simplifying the interaction between the user and the electronic device and improving the usability of the electronic device, making the user-device interface more efficient (e.g., by displaying to the user a confirmation page that allows the user to visually confirm that the configuration was successful without requiring the user to navigate to a separate user interface to confirm that the configuration was successful), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0195] In some embodiments, a user interface with additional information regarding the functionality of the remote locator object includes information about features of the remote locator object (722), such as in FIG. 6K (e.g., the user interface with additional information includes one or more indications of the features of the remote locator object). In some embodiments, the indications are selectable to perform actions corresponding to the respective features of the remote locator object. In some embodiments, the features of the remote locator object include features for discovering or otherwise locating the remote locator object using a device tracking and discovery application. In some embodiments, the features of the remote locator object include features for managing notifications and / or alerts associated with the remote locator object, including alerts that are displayed when a user is separated from the remote locator object. In some embodiments, the features of the remote locator object include features for managing trusted locations and / or people (e.g., so that the location of the remote locator object is shared with trusted people and / or so that alerts are not generated when the remote locator object is separated from the user but with trusted people and / or trusted locations).

[0196] The above-described method of displaying features of a remote locator object (e.g., by displaying in a user interface having information about the features of the remote locator object after the user has completed configuration of the remote locator object) enables the electronic device to inform the user of key features available in the remote locator object within a single user interface after the user has completed configuration (e.g., by displaying a user interface having information about multiple features of the remote locator object), thereby simplifying the interaction between the user and the electronic device and improving the usability of the electronic device, making the user-device interface more efficient (e.g., by determining that the user is likely to desire information about the features of the remote locator object after the user has successfully configured and paired the remote locator object), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0197] In some embodiments, a user interface with additional information regarding the functionality of the remote locator object includes information indicating that the remote locator object has been detected as being held by a user of the device (724), such as in FIG. 6K (e.g., the user interface with additional information includes a text label for the current location of the remote locator object). In some embodiments, if the current location is within a threshold distance to the user (e.g., 3 feet, 5 feet, 10 feet), the text label displays "With You" or any other suitable label indicating that the object is being held by a user. In some embodiments, the text label for the current location of the remote locator object includes a text label indicating the time the current location was updated and / or refreshed. For example, in some embodiments, the location refresh time text label displays "Just Checked" if the location was updated (e.g., refreshed) within a threshold time (e.g., 1 minute, 5 minutes, etc.). In some embodiments, if the refresh time is greater than the threshold time, the location refresh time optionally indicates when the most recent refresh occurred (e.g., "Checked 5 minutes ago" or "Last checked 5 minutes ago").

[0198] The above-described method of displaying information regarding the functionality of a remote locator object (e.g., by indicating that the user is holding the remote locator object) allows an electronic device to indicate to a user that the remote locator object is properly tracking and / or reporting its location (e.g., by displaying an indication that the user is holding the remote locator object) and that it is properly receiving the location of the remote locator object such that it can automatically determine that the remote locator object is with the user, thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by automatically determining and displaying that the remote locator object is with the user without requiring the user to separately determine that the location of the remote locator object is in the same location as the user), and additionally reducing power usage and improving the battery life of the electronic device by allowing a user to use the electronic device more quickly and efficiently.

[0199] In some embodiments, the user interface with additional information about the functionality of the remote locator object includes a selectable user interface object (726) associated with an application corresponding to the remote locator object, such as in FIG. 6K (e.g., the user interface with additional information includes a selectable option selectable to launch or otherwise display an application for discovering and tracking devices (e.g., including the remote locator object and, optionally, other electronic devices)). In some embodiments, the electronic device detects (728) a selection of the selectable user interface object and, in response to detecting the selection of the selectable user interface object, displays (730) a user interface for the application corresponding to the remote locator object, such as in FIG. 6K (e.g., replacing the display of an additional information pane of a settings user interface and a background user interface, such as a home screen or an application that was running when the remote locator object was detected near the electronic device, with the application corresponding to the remote locator object (e.g., an application for discovering and tracking devices)). In some embodiments, when the application for discovering and tracking devices is displayed, the application navigates to a user interface specific to each remote locator object (e.g., a specific user interface for viewing and / or managing the settings of each remote locator object).

[0200] The above-described methods of providing additional settings (e.g., by providing a selectable option to display an application corresponding to the remote locator object) provide a quick setup process for the user (e.g., by performing an initial setup of the device in response to receiving a user selection of a selectable option to display a user interface of an application corresponding to the remote locator object, but displaying a setup user interface to provide a selectable option to display an application corresponding to the remote locator object), but also provide options to adjust more advanced settings of the remote locator object, thereby simplifying the interaction between the user and the electronic device, improving usability of the electronic device, making the user-device interface more efficient (e.g., by providing the user with the ability to change additional settings after successfully configuring the remote locator device without requiring the user to manually navigate to the application corresponding to the remote locator object), and additionally reducing power usage and improving battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0201] In some embodiments, the electronic device detects (732), via one or more wireless antennas, that a respective remote locator object associated with a respective user account different from the user account associated with the electronic device is in proximity (e.g., within 1 inch, 2 inches, or 3 inches) to the electronic device (e.g., a user performs an NFC tap gesture (with the electronic device) on a remote locator object owned / configured by another user or not otherwise associated with the user of the electronic device), such as in FIG. 6R. In some embodiments, in response to detecting that the respective remote locator object is in proximity to the electronic device, the electronic device displays (734), via a display device, an informational user interface indicating that the respective remote locator object is associated with a user account other than the user account associated with the electronic device, the informational user interface including a first selectable option selectable to request sharing and access to the respective remote locator object from the respective user account with the user account associated with the electronic device, such as in FIG. 6R (e.g., displaying a user interface different from the settings user interface on the electronic device corresponding to the remote locator object). In some embodiments, the user interface includes a selectable option to request a sharing of the remote locator object from the owner of the remote locator object (e.g., the user account for which the remote locator object is configured). In some embodiments, requesting a share causes a notification to appear on the electronic device of the owner of the remote locator object. In some embodiments, the owner of the electronic device can accept the share request and set a time for sharing the remote locator object with the user for a predetermined period of time, similar to the method for sharing a remote locator object described above.In some embodiments, after sharing a remote locator object with a user, the user can view and / or track the location of the remote locator object via their electronic device (e.g., using an application for tracking and locating objects).

[0202] The above-described method of requesting the sharing of a remote locator object (e.g., by displaying a user interface with selectable options to request the sharing of a remote locator object from the owner of the remote locator object) enables quick and efficient requests to share a remote locator object from the owner of the remote locator object, thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing a quick way for the owner of the remote locator object to share the remote locator object with the user without having to navigate to a separate user interface to manually share the remote locator object with the user), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0203] It should be understood that the particular order described for the operations in Figures 7A-7D is merely illustrative and is not intended to indicate that the described order is the only order in which the operations can be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that other process details described herein with respect to other methods described herein (e.g., methods 900, 1100, 1300, and 1400) are also applicable in a similar manner to method 700 described above with respect to Figures 7A-7D. For example, initializing the remote locator object described above with reference to method 700 optionally has one or more of the characteristics described herein with reference to other methods described herein (e.g., methods 900, 1100, 1300, and 1400), such as presenting a detachment notification, presenting a tracking notification, and discovering the remote locator object. For the sake of brevity, those details will not be repeated here.

[0204] The operations in the information processing methods described above are optionally performed by running one or more functional modules in an information processing device, such as a general-purpose processor (e.g., as described above in connection with FIGS. 1A-1B, 3, 5A-5H) or an application-specific chip. Additionally, the operations described above with reference to FIGS. 7A-7D are optionally performed by the components shown in FIGS. 1A-1B. For example, displaying operations 704, 706, 710, 730, and 734 and detecting operations 702, 708, 728, and 732 are optionally performed by event sorter 170, event recognizer 180, and event processor 190. Event monitor 171 of event sorter 170 detects contacts on touchscreen 504, and event dispatcher module 174 delivers the event information to application 136-1. Each event recognizer 180 of application 136-1 compares the event information to a respective event definition 186 to determine whether a first contact at a first location on the touchscreen corresponds to a predefined event or sub-event, such as selecting an object on a user interface. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of that event or sub-event. Event handler 190 optionally utilizes or invokes a data updater 176 or an object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a corresponding GUI updater 178 to update what is displayed by the application. Similarly, it will be apparent to one skilled in the art how other processes can be implemented based on the components shown in FIGS. 1A-1B. Notification of detachment from a remote locator object

[0205] Users interact with electronic devices in many different ways. In some embodiments, the electronic device can track the location of objects, such as remote locator objects. In some embodiments, remote locator objects that support location tracking functionality can be attached to items that do not support location tracking functionality. The embodiments described below provide a way for an electronic device to provide an alert that a remote locator object associated with the user has become separated from the user, thereby enhancing the user's interaction with the electronic device. Enhancing interaction with the device reduces the amount of time the user needs to perform an action, thus reducing the device's power usage and increasing battery life for battery-powered devices. It is understood that people use devices. When a person uses a device, the person is optionally referred to as the user of the device.

[0206] 8A-8P illustrate example methods by which an electronic device displays notification of a separation from a remote locator object, according to some embodiments of the present disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to FIGS. 9A-9G.

[0207] 8A-8P illustrate an electronic device 500 displaying a notification of separation from a remote locator object. FIG. 8A illustrates an exemplary device 500 including a touchscreen 504. As shown in FIG. 8A, the electronic device 500 presents a lock screen user interface 800 (e.g., a wake screen user interface). In some embodiments, the lock screen user interface 800 is a user interface that is displayed when the electronic device 500 wakes up (e.g., from a sleep (low power) state or a locked state). In some embodiments, the lock screen user interface 800 includes a notification 802. In some embodiments, the notification 802 notifies the user that a respective remote locator object labeled "keys" (e.g., as described with reference to method 700) has been separated from the user and is no longer with the user. In some embodiments, the notification 802 includes the label of the remote locator object (e.g., "John's Keys"). In some embodiments, notification 802 displays location information such as the distance from the user to the determined location of the remote locator object (e.g., 2 miles) and when the most recent location update occurred (e.g., "right now").

[0208] In some embodiments, notification 802 is displayed when electronic device 500 (e.g., or a server) determines that the remote locator object is separated from the user. For example, in some embodiments, when the remote locator object is a threshold distance (e.g., 10 feet, 50 feet, 100 feet, 1 mile, etc.) from the user, electronic device 500 triggers notification 802 to inform the user that the user is separated from the remote locator object.

[0209] As described above with reference to method 700, in some embodiments, a remote locator object can update, receive, and / or transmit location data to a server via an electronic device even if the remote locator object is not paired with the respective electronic device (e.g., another mobile phone that the remote locator object has passed by). Thus, a remote locator object can update its location information even if the remote locator object is separated from electronic device 500. While notification 802 is shown as being displayed on lock screen user interface 800, it will be understood that notification 802 can be displayed on other user interfaces (e.g., in any context in which other notifications can be displayed).

[0210] In some embodiments, if electronic device 500 moves within a threshold distance of the respective remote locator object, notification 802 is dismissed or otherwise removed from display on electronic device 500. In some embodiments, the threshold distance that triggers the display of notification 802 includes hysteresis, such that a certain threshold distance is required to trigger the notification, while a second, smaller threshold distance is required to automatically dismiss the notification.

[0211] 8A , user input 803 selecting notification 802 is received (e.g., a tap on a touchscreen directed at notification 802). In some embodiments, in response to the user input, device 500 displays user interface 810, as shown in FIG. 8B . In some embodiments, user interface 810 is a user interface for an application for tracking and finding items (e.g., a “Discover” app) specific to each remote locator object. In some embodiments, user interface 810 includes a map 811 that displays the determined location of each remote locator object. In some embodiments, map 811 displays an icon 812 corresponding to the current location of electronic device 500 (e.g., the user's current location) and an icon 814 corresponding to the current location of each remote locator object.

[0212] In some embodiments, user interface 810 includes a label 816 that indicates the remote locator object being displayed on user interface 810 (e.g., remote locator object, "John's Keys"). In some embodiments, user interface 810 includes a label 818 that indicates the location status of the remote locator object. In some embodiments, the location status of the remote locator object is more than a threshold distance from the user, resulting in the display of the "Separate" label. In some embodiments, label 818 additionally or alternatively includes an indication of when the location of the remote locator object was most recently updated. For example, as shown in FIG. 8B, the location data for the remote locator object was updated "just now" (e.g., within 1 second, within 30 seconds, within 1 minute, within 2 minutes, etc.). In some embodiments, label 818 includes a description of the location closest to where the remote locator object is located. For example, as shown in FIG. 8B, the remote locator object is determined to be "near a restaurant."

[0213] In some embodiments, user interface 810 includes selectable option 819-1 and selectable option 819-2 that correspond to features available to the remote locator object. In some embodiments, selection of selectable option 819-1 causes the display of a user interface for locating the remote locator object (e.g., similar to the processes described below with respect to methods 1300 and 1400). In some embodiments, selection of selectable option 819-2 causes the remote locator object to emit an audible sound. In some embodiments, selectable option 819-2 is a toggle button, and the remote locator object emits an audible sound continuously until electronic device 500 receives a second user input that selects selectable option 819-2 and disables the audible sound. In some embodiments, selectable option 819-2 is not a toggle button, and the remote locator object emits an audible sound as long as the user selects selectable option 819-2. Thus, in some embodiments, the remote locator object emits an audible tone only while the user selects selectable option 819-2.

[0214] In some embodiments, user interface 810 includes a selectable toggle 819-3 to toggle separation alerts on or off. For example, selecting selectable option 819-3 when separation alerts are enabled disables separation alerts, and selecting selectable option 819-3 when separation alerts are disabled enables separation alerts. In some embodiments, selectable option 819-3 indicates the number of exceptions (e.g., trusted locations) that exist to trigger a separation alert (e.g., notification 802). In some embodiments, trusted locations (e.g., exceptions) are specific to each tracked remote locator object, and thus a different set of trusted locations is maintained for each remote locator object. It is understood that trusted people can also be added as exceptions that trigger separation alerts. For example, a user can add another user (e.g., a "trusted user") so that a separation alert is not generated for the user when a remote locator object is separated from the user but with the trusted user. More details about trusted locations are provided below with respect to Figures 8E-8I.

[0215] In FIG. 8B , user input 803 is received selecting selectable option 819-1. In some embodiments, in response to the user input, device 500 enters a discovery mode and displays user interface 820, as shown in FIG. 8C . In some embodiments, based on the distance to the remote locator object, device 500 enters a first discovery mode (e.g., a map-based discovery mode for long distances) or a second discovery mode (for short distances) (e.g., similar to the processes described below with respect to methods 1300 and 1400). In FIG. 8C , device 500 enters the first discovery mode, which corresponds to discovering the remote locator object using navigation with a map application. In FIG. 8C , user interface 820 is a user interface for a map displaying directions from the current location of device 500 to the location of the remote locator object. In some embodiments, the map displays an icon 812 corresponding to the user's current location, an icon 814 corresponding to the determined location of the remote locator object (e.g., a "key"), and a route 822 corresponding to the path taken to reach the remote locator object. In some embodiments, user interface 820 includes a card 824 for configuring a navigation mode and initiating navigation. In some embodiments, card 824 includes a description 829 and selectable options 826. In some embodiments, description 829 includes information about the route distance, travel time length, whether the route is the quickest route, etc. In some embodiments, selectable option 826 is selectable to initiate navigation to a remote locator object. In some embodiments, card 824 includes selectable options 828-1, 828-2, and 828-3 that change the navigation mode. For example, selectable option 828-1 is selectable to set navigation for driving directions, selectable option 828-2 is selectable to set navigation for walking directions, and selectable option 828-3 is selectable to set navigation for public transportation directions.

[0216] 8D-8J illustrate an example process for managing a remote locator object separation alert. FIG. 8D illustrates user interface 870 corresponding to a home screen of an application for tracking and finding items. In some embodiments, user interface 870 is similar to user interface 670 described above with respect to FIG. 6N. In FIG. 8D, while displaying user interface 870, user input 803 is detected by selecting item 878-1, which corresponds to a remote locator object labeled "Key." In some embodiments, in response to user input 803, device 500 displays user interface 830, as shown in FIG. 8E. In some embodiments, user interface 830 is similar to user interface 660 described above with respect to FIG. 6L.

[0217] In some embodiments, user input 803 is detected by selecting a selectable option 838 to set the isolation warning setting for the respective remote locator object. In some embodiments, in response to user input 803, device 500 displays user interface 840, as shown in FIG. 8F.

[0218] In some embodiments, user interface 840 provides the user with options to modify notification settings for each remote locator object (e.g., John's key). For example, in some embodiments, user interface 840 includes toggle 842 for toggling separation warnings (e.g., notifications 802, etc.) on or off (e.g., enabled or disabled). In some embodiments, user interface 840 displays a list of locations that have previously been set as trusted locations for the respective remote locator object (e.g., or optionally, for other remote locator objects), such as location 844-1 and location 844-2.

[0219] In some embodiments, if a location has not been set as a trusted location, user interface 840 only includes a selectable option 846 to add a trusted location. In some embodiments, as shown in FIG. 8F , user interface 840 displays trusted locations 844-1 and trusted locations 844-2. In some embodiments, the trusted locations listing includes an icon representing the trusted location (e.g., a map icon), a trusted location label (e.g., “Home” or “Work”) optionally selected by the user, and an indication (e.g., a check mark) that the trusted location is currently enabled. In some embodiments, trusted locations 844-1 and trusted locations 844-2 are selectable to enable or disable the trusted location. In some embodiments, when the trusted location is disabled, the check mark is removed from the display to indicate that the trusted location is not currently enabled. As described above, a trusted location is one for which a notification will not be triggered if the remote locator object is further than a threshold distance from the user but within a predetermined radius / distance of the trusted location. In some embodiments, when selectable option 842 is toggled off, user interface 840 does not display the trusted locations option (as described below with respect to FIG. 8J).

[0220] In FIG. 8F, user input 803 is detected by selecting selectable option 846 to add a new trusted location. In some embodiments, in response to user input 803, device 500 displays user interface 850 for adding a new trusted location, as shown in FIG. 8G. In some embodiments, user interface 850 displays text entry field 852 in which the user can enter an address to add a trusted location via address entry. In some embodiments, user interface 850 includes map 854. In some embodiments, map 854 includes pin 856 with which the user can interact with and move around the map. In some embodiments, a trusted location can be added by moving pin 856 to a desired location and setting the location as a trusted location (e.g., by clicking the "Done" affordance). In some embodiments, pin 856 is anchored in the center of map 854, and the user can set the trusted location by panning the map so that the pin is at the intended location.

[0221] In some embodiments, user interface 850 includes radius options 858-1 through 858-4. In some embodiments, the user can select a radius for the trusted location. For example, the user can select a small radius (e.g., selectable option 858-1: 50 feet, 100 feet, 200 feet, etc.), a medium radius (e.g., selectable option 858-2: 100 feet, 200 feet, 500 feet, etc.), or a large radius (e.g., selectable option 858-3: 400 feet, 600 feet, 1000 feet, etc.) around the trusted location within which a separation notification will not be triggered. In some embodiments, the user can select selectable option 858-4 to provide a custom radius for the trusted location. In some embodiments, map 854 displays a visual indication of the radius selected by the user (e.g., shown as a dotted circle around pin 856). As shown in FIG. 8G, selectable option 858-1, which corresponds to the small radius, is currently selected. In FIG. 8G , user input 803 is received selecting selectable option 858-2, which corresponds to a medium radius. In some embodiments, in response to the user input, map 854 is updated to reflect the selected radius size, as shown in FIG. 8H . As shown in FIG. 8H , the dotted circle around pin 856 is now a “medium” size. In some embodiments, the user can perform a pinch gesture on map 854 to increase or decrease the size of the dotted circle and provide a custom radius. In some embodiments, in response to the user's gesture to increase or decrease the size of the dotted circle, device 500 automatically moves the radius selection to selectable option 858-4, which corresponds to the custom radius option.

[0222] In FIG. 8I , after the user successfully adds a new trusted location, the new trusted location is displayed in user interface 840 (e.g., trusted locations 844-3). It is understood that the set of trusted locations is specific to each remote locator object, and each remote locator object maintains its own set of trusted locations. In FIG. 8I , user input 803 is detected by selecting toggle 842. In some embodiments, in response to the user input, separation warnings are disabled entirely for the respective remote locator object (e.g., but not disabled for other remote locator objects for which separation warnings have not been disabled). In some embodiments, in response to the user input, device 500 updates user interface 840 to remove the display of the trusted locations list item, as shown in FIG. 8J . In some embodiments, in response to the user re-enabling separation warnings for the respective remote locator object, the trusted locations list item is re-displayed (e.g., the set of trusted locations for the respective remote locator object is restored).

[0223] 8K-8N show an exemplary process for sharing a remote locator object with another user. In FIG. 8K, device 500 displays user interface 830. In some embodiments, user interface 830 is similar to user interface 660 described above with respect to FIG. 6L. In some embodiments, if the respective remote locator object is currently shared with another user, the user with whom the respective remote locator object is shared is displayed on user interface 830 (e.g., user 837-1). In some embodiments, if the respective remote locator object is not shared with anyone, selectable option 839 displays "Add people," and if the respective remote locator object is shared with other users, selectable option 839 displays "Manage people."

[0224] In some embodiments, user input 803 is detected by selecting selectable option 839 to manage people with whom the respective remote locator object is shared (e.g., manage sharing settings for the respective remote locator object). In some embodiments, in response to user input 803, device 500 displays user interface 860, as shown in FIG. 8L. In some embodiments, user interface 870 is a user interface for selecting people with whom the respective remote locator object is shared. In some embodiments, sharing a remote locator object with another user provides the other user with the same functionality as the owner of the remote locator object. For example, the user with whom the remote locator object is shared can set and receive separation alerts, track the location of the remote locator object, and identify the location of the remote locator object (e.g., similar to list item 678-2 shown in FIG. 6N, which corresponds to the user's spouse sharing the remote locator object with the user).

[0225] In some embodiments, as shown in FIG. 8L , user interface 860 includes one or more users with whom the user is currently sharing the remote locator object, with whom the user has previously shared the remote locator object, or with whom the user is sharing or has shared other remote locator objects. In some embodiments, each user in the user's listing is selectable (e.g., as indicated by a check mark or lack of a check mark, respectively) to toggle (e.g., enable or disable) sharing with the respective user. In some embodiments, the user can add or remove users from the list of potential users with whom to share. In some embodiments, user input 803 is received selecting “sister” users with whom the user will share the respective remote locator object.

[0226] In some embodiments, in response to user input 803 selecting a “sister” user with which to share the respective remote locator object, device 500 displays card 870 (e.g., a user interface) superimposed on user interface 860, as shown in FIG. 8M. In some embodiments, card 870 provides the user with one or more options for how long to share the remote locator object with the “sister” user. For example, in some embodiments, selectable option 872 corresponds to (and can be selected to share) the remote locator object until the end of the day, and selectable option 874 corresponds to (and can be selected to share) the remote locator object indefinitely (e.g., until the user manually disables sharing with the “sister” user). In some embodiments, other possible time periods are possible. In some embodiments, card 870 includes selectable option 876 that can be selected to cancel the process of sharing with the “sister” user and dismiss card 870.

[0227] In FIG. 8M , user input 803 is received selecting selectable option 872 to share with “sister” users until the end of the day. In some embodiments, in response to the user input, device 500 begins the process of sharing the respective remote locator object with the “sister” users until the end of the day. In some embodiments, after sharing the respective remote locator object with the “sister” users, user interface 830 displays user 837-2 in the list of users with whom the respective remote locator object is shared, as shown in FIG. 8N . In some embodiments, user 837-2 is displayed with a description that the “sister” users can locate the item and that the sharing will expire in 9 hours and 8 minutes. In some embodiments, each list item (e.g., users 837-1 and 837-2) is selectable to change the respective user's sharing options (e.g., to remove sharing or set or remove a time limit on sharing). It will be understood that the set of users with whom each remote locator object is shared is specific to each remote locator object, and that each remote locator object maintains its own set of shared users.

[0228] 8O-8P illustrate example embodiments of an expanded detachment notification. In FIG. 8O, device 500 displays lock screen user interface 800 with notification 802. In FIG. 8O, contact 803 is detected on the touchscreen selecting notification 802. In some embodiments, contact 803 has an intensity above a certain intensity threshold (e.g., a long press, a force press, etc.). In some embodiments, in response to contact 803 exceeding a certain intensity threshold (or longer than a threshold duration), notification 802 expands into expanded notification 802, as shown in FIG. 8P. In some embodiments, expanded notification 802 includes map 804. In some embodiments, map 804 includes icon 806 indicating the current location of electronic device 500. In some embodiments, map 804 includes icon 808 indicating the location of each remote locator object (e.g., John's keys).

[0229] In some embodiments, enhanced notification 802 includes selectable options 809-1, 809-2, and 809-3 that perform actions related to the remote locator object. In some embodiments, selectable option 809-1 is selectable to locate the remote locator object using an application for tracking and finding items, similar to the process described above with respect to FIGS. 8B-8C. In some embodiments, selectable option 809-2 is selectable to cause the respective remote locator object to emit an audible sound. In some embodiments, selectable option 809-3 is selectable to add the current location of the respective remote locator object to a list of trusted locations and display a user interface 850 similar to user interface 850 described above with respect to FIG. 8G. For example, in response to a user selection of selectable option 809-3, user interface 850 is displayed with map 854 automatically (e.g., without user input) panned to a position such that pin 856 is placed at the determined location of the key. In some embodiments, text entry field 852 is automatically populated with an address corresponding to the location of the key (e.g., and therefore the location of pin 856). Thus, a user can quickly add the current location of a remote locator object without having to manually enter the current address of the remote locator object or adjust the map so that pin 856 is placed at the location of the remote locator object.

[0230] 9A-9G are flow diagrams illustrating a method 900 for displaying notification of separation from a remote locator object according to some embodiments, such as in FIGS. 8A-8P. Method 900 is optionally performed on an electronic device, such as device 100, device 300, or device 500, as described above with reference to FIGS. 1A-1B, 2-3, 4A-4B, and 5A-5H. Some operations in method 900 are optionally combined and / or the order of some operations is optionally changed.

[0231] As described below, method 900 provides a way to display notification of separation from a remote locator object. This method reduces the cognitive burden on a user when interacting with the user interface of a device of the present disclosure, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, improving the efficiency of the user's interaction with the user interface conserves power and increases the time between battery charges.

[0232] In some embodiments, such as in FIG. 8A , an electronic device having one or more wireless antennas, a display device, and one or more input devices (e.g., a mobile device (e.g., a tablet, smartphone, media player, or wearable device) including a touch screen and wireless communication circuitry, or a computer including one or more of a keyboard, mouse, trackpad, and touch screen, and wireless communication circuitry) communicates with a first remote locator object (e.g., a remote locator object that can communicate with the electronic device wirelessly, such as via Bluetooth and / or WiFi. The device can optionally be attached to a user's item, such as a user's key, a user's handbag, etc. In some embodiments, the remote locator object can provide location information to one or more electronic devices. While a remote locator object is associated with a user (e.g., a remote locator object is configured to be associated with a user and / or user account of an electronic device and / or electronic device), obtain information indicating that an amount of separation between a location associated with the user (e.g., as determined based on a device associated with the user, such as a watch, cell phone, or electronic device) and a location associated with a first remote locator object has increased beyond a first separation threshold (e.g., a distance threshold between the location associated with the user and the location associated with the remote locator object (e.g., 50 feet, 200 feet, 500 feet, ½ mile)), such as in FIG. 8A (902). In some embodiments, the information is obtained from a server tracking the user's location relative to the location of the first remote locator object. In some embodiments, the remote locator object has one or more sensors (e.g., GPS sensors) for determining the location of the remote locator object.

[0233] In some embodiments, the remote locator object can transmit location information to one or more electronic devices (that may or may not be associated with an associated user). In some embodiments, the location information is transmitted to a server that is tracking the location of the first remote locator object. In some embodiments, the remote locator object can transmit identification information (e.g., the remote locator object's serial number, an identifier of the remote locator object's associated user, etc.) to an electronic device (that may or may not be associated with a user) that has one or more sensors (e.g., a GPS sensor) for determining location. In some embodiments, using the identification information and / or one or more sensors in the electronic device that received the identification information from the remote locator object, the server can receive information regarding the location (or approximate location) of the remote locator object (e.g., the electronic device that received the identification information transmits the identification information and / or its own location information of the electronic device to the server). In some embodiments, the information is obtained by the electronic device that determines that the first remote locator object is more than a threshold distance from the electronic device using direct wireless communication techniques between the electronic device and the first remote locator object (e.g., rather than communication with or through the server).

[0234] In some embodiments, in response to obtaining information indicating that the amount of separation between the location associated with the user and the location associated with the first remote locator object has increased beyond a first separation threshold, the electronic device generates (904) a separation alert at the electronic device indicating that the first remote locator object has been separated from the user (e.g., displaying a notice or other alert on the electronic device indicating that the remote locator object is no longer with the user), such as in FIG. 8A . In some embodiments, the notice or other alert includes an identifier associated with the remote locator object, such as a “keys” or “handbag,” indicating that the user’s “keys” or “handbag” are no longer with the user.

[0235] The above-described method of alerting a user of separation from a remote locator object (e.g., by providing a separation alert when it is determined that the remote locator object is farther than a threshold distance from the electronic device) provides the user with notification that the remote locator object is no longer with the user (e.g., by obtaining information that the distance between the electronic device and the remote locator object is farther than a threshold distance and providing a separation alert to the user), thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by quickly providing the user with a warning that the user has become separated from the remote locator object), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0236] In some embodiments, the separation warning includes a visual element displayed via a display device (906) (e.g., generating the separation warning includes displaying a visual warning, such as a notification, on the electronic device), and while displaying the separation warning, the electronic device detects (908) a sequence of one or more inputs that includes (starts with) an input directed at the separation warning, such as in FIG. 8A (e.g., receiving a contact (e.g., a long press) longer than a threshold time or a contact (e.g., a force press) having an intensity exceeding a threshold intensity on the separation warning, causing display of an expanded separation warning (e.g., an expanded notification)). In some embodiments, the expanded separation warning displays a map with the determined location of the remote locator object and one or more options associated with the remote locator object. In some embodiments, the one or more options include an option to mark the current location of the remote locator object as a trusted location so that the separation warning is not displayed when the remote locator object is separated from the user and in a trusted location.

[0237] In some embodiments, in response to detecting a sequence of one or more inputs (e.g., including a user input selecting a selectable option to mark the current location of the remote locator object as a trusted location), the electronic device marks (910) the location associated with the first remote locator object as a safe zone for the remote locator object, where the safety zone for each remote locator object is an area within which the device will not generate a separation alert (e.g., add the current location of the remote locator object as a safe zone (e.g., trusted location)) when the amount of separation between the location associated with the user and the location associated with the respective remote locator object is greater than (increases beyond) a first separation threshold while the respective remote locator object remains within the safe zone, such as in FIG. 8P . In some embodiments, objects within the radius of the safety zone do not generate a separation alert when determined to be separated from the user. In some embodiments, the radius of the safety zone is adjustable, and each trusted location has its own set radius. In some embodiments, each remote locator object and / or device being tracked has its own set of trusted locations and / or safety zones. In some embodiments, the safety zone is a trusted location or a trusted person. In some embodiments, when the remote locator object is determined to be with the trusted location (e.g., following the location of the trusted person or within a certain threshold distance, such as 1 foot, 2 feet, 3 feet, etc., of the trusted person), no separation alert is generated.

[0238] The above-described method of setting a safe zone for a remote locator object (e.g., by providing a selectable option on a separation alert to add the current location of the remote locator object as a safe zone) provides a user with an easy way to add the current location of a remote locator object as a safe zone (e.g., by providing a selectable option that can be selected to have the current location of a remote locator object that is triggering a separation alert added as a safe zone in which the separation alert will not be triggered), thereby simplifying the interaction between the user and the electronic device and improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing a shortcut way for the user to add a location as a safe zone without requiring the user to perform additional input or navigate to a separate user interface and / or enter an address or manually set the location as a safe zone), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0239] In some embodiments, the sequence of one or more inputs includes user input (912) that sets the size and / or shape of the safe zone (e.g., selects a radius, a center point, and / or otherwise defines the boundaries of the safe location), such as in FIGS. 8G-8H. In some embodiments, the user is presented with one or more pre-defined radii. In some embodiments, the user can provide a custom radius or boundaries for the safe location.

[0240] The above-described method of setting a safety zone for a remote locator object (e.g., by receiving user input that sets the size and / or shape of the safety zone) allows for quick and efficient setting of the safety zone area, thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., without requiring the user to potentially add multiple safety zones to cover the area intended by the user or generating excessive separation warnings when the remote locator object is in a location that the user considers safe but cannot be covered by the size and shape of the fixed safety zone), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0241] In some embodiments, marking a location associated with a first remote locator object as a safe zone for the remote locator object includes marking a person other than the user as a safe person, and a separation alert is not generated (958) when the amount of separation between the location associated with the user and the location associated with the respective remote locator object is greater than a first separation threshold while the respective remote locator object remains within a safe person threshold distance, such as in FIG. 8H (e.g., the safe zone can be a trusted person). In some embodiments, a separation alert is not generated when the remote locator object is determined to be within a certain threshold distance (e.g., 1 foot, 2 feet, 3 feet) of a trusted person. For example, a user can set their spouse as a trusted person for a remote locator object attached to the user's key, so that when the spouse takes the key (and remote locator object), no separation alert is generated, even if the remote locator object is further than the threshold distance from the user.

[0242] The above-described method of setting a safe zone for a remote locator object (e.g., by setting a trusted person as the safe zone for the remote locator object) avoids the need to set multiple safe zones when the remote locator object is with a trusted person (e.g., by setting a person as a safe zone so that separation alerts are not generated when the remote locator object is with the person), thereby simplifying the interaction between the user and the electronic device and improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing a way to set a portable safe zone without requiring the user to continually update the safe zone for the remote locator object or ignore separation alerts), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0243] In some embodiments, the user is associated (914) with multiple remote locator objects, including a second remote locator object, such as in FIG. 8D (e.g., the user may associate and / or pair multiple remote locator objects with an electronic device and / or the user's user account, or otherwise track multiple remote locator objects (e.g., another user optionally shares the location of the remote locator object with the user)). In some embodiments, while the respective regions are set as safe zones for the first remote locator object but not as safe zones for the second remote locator object, and the first remote locator object and the second remote locator object are associated with respective locations within the safe zones (916) (e.g., the first and second remote locator objects are located at the respective locations. In some embodiments, the first remote locator object has its respective location marked as a safe zone (e.g., or the respective locations are within the radius of the respective safe zone). In some embodiments, the second remote locator object does not have its respective location marked as a safe zone), the electronic device obtains (918) information indicating that the amount of separation between the location associated with the user (e.g., as determined based on a device associated with the user, such as a watch or cell phone) and the location associated with the first remote locator object has increased beyond a first separation threshold (e.g., a distance threshold between the location associated with the user and the location associated with the remote locator object), such as in FIG. 8A . In some embodiments, the information is obtained from a server that tracks the user's location relative to the location of the first remote locator object. In some embodiments, the information is obtained by the electronic device that determines that the first remote locator object is more than a threshold distance from the electronic device.

[0244] In some embodiments, the electronic device obtains (920) information indicating that an amount of separation between a location associated with the user (e.g., as determined based on a device associated with the user, such as a watch or cell phone) and a location associated with a second remote locator object has increased beyond a first separation threshold (e.g., a distance threshold between a location associated with the user and a location associated with the remote locator object), such as in FIG. 8A . In some embodiments, the information is obtained from a server that is tracking the user's location relative to the location of the first remote locator object. In some embodiments, the information is obtained by the electronic device determining that the first remote locator object is more than a threshold distance away from the electronic device.

[0245] In some embodiments, in response to obtaining information indicating that an amount of separation between a location associated with the user and a location associated with a first remote locator object has increased beyond a first separation threshold and obtaining information indicating that an amount of separation between a location associated with the user and a location associated with a second remote locator object has increased beyond the first separation threshold, the electronic device generates (922) a separation alert indicating that the second remote locator object has been separated from the user, without generating a separation alert indicating that the first remote locator object has been separated from the user, such as in FIG. 8A (e.g., setting safe locations for the first remote locator object without setting safe locations for the second remote locator object). In some embodiments, the set of safe locations for the first remote locator object is a different set of safe locations for the second remote locator object. In some embodiments, each remote locator object has its own dedicated set of safe locations. In some embodiments, the set of safe locations for each remote locator object is global, such that all users who have access to each remote locator object (e.g., can see the remote locator object's location through association and / or sharing) have the same global set of safe locations. In some embodiments, each user has their own set of safe locations for each remote locator object (e.g., each user can set safe locations for each remote locator object without affecting the safe locations of other users).

[0246] The above-described method of managing safety zones for remote locator objects (e.g., by maintaining a different set of safety zones for each remote locator object and generating a separation alert if the remote locator object's location is not within the specified safety zone for that given remote locator object) provides a user with a way to set different safety zones for different remote locator objects (e.g., by maintaining a set of safety zones for each remote locator object), thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by allowing the user to set different safety zones for different remote locator objects so that separation alerts are not generated unnecessarily), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0247] In some embodiments, the separation alert includes a map with a representation of a location associated with the first remote locator object (924), such as in FIG. 8P (e.g., the expanded separation alert is displayed in response to receiving user input directed to the separation alert that meets one or more criteria). In some embodiments, the one or more criteria are met when the input is a contact that is longer than a threshold time (e.g., 0.1 seconds, 0.3 seconds, 0.5 seconds), or a contact that has an intensity greater than a certain threshold, or any combination thereof. In some embodiments, the expanded separation alert displays a map with the determined location of the remote locator object. In some embodiments, the expanded separation alert includes an option to mark the current location of the remote locator object as a trusted location.

[0248] The above-described method of setting a safe zone for a remote locator object (e.g., by displaying a map including a representation of the current location of the remote locator object) provides the user with the ability to view and confirm the location set in the safe zone, thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by displaying a map with a current location indicator of the current location of the removed locator object after adding the safe zone, without the user having to navigate to a separate user interface to confirm the current location of the remote locator object or verify the location of the safe zone and / or remote locator object), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0249] In some embodiments, the separation alert includes an indication of the time the location associated with the first remote locator object was determined, such as in FIG. 8A , and an indication of the distance between the location associated with the first remote locator object and a location associated with the user (926) (e.g., the separation alert displays a text indicator of the distance between the electronic device and the remote locator object (e.g., “2 miles away”) and / or a text indicator of the most recent location update of the remote locator object (e.g., “checked just now” or “last checked 5 minutes ago”)). In some embodiments, the text indicator updates as the distance changes.

[0250] The above-described method of displaying a separation warning (e.g., by displaying the distance from the user to the remote locator object and the time its location was last determined) provides the user with a quick way to see how far away the remote locator object is and when the object was last seen at that location, thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by letting the user know how far the remote locator object is from the user and when its location was last determined), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0251] In some embodiments, the electronic device obtains (928) information indicating that an amount of separation between a location associated with the user and a location associated with the first remote locator object is less than a corresponding separation threshold (e.g., the distance between the remote locator object and the user falls below a separation threshold, such as a distance defined as the effective range limit of direct communication between the electronic device and the first remote locator object (e.g., 10 feet, 20 feet, 40 feet), etc.), such as described in FIG. 8A . In some embodiments, in response to obtaining information indicating that an amount of separation between a location associated with the user and a location associated with the first remote locator object is less than the corresponding separation threshold, the electronic device stops (930) presenting a separation warning (e.g., stops displaying the separation warning, stops outputting a tactile or audio output associated with the separation warning, etc.), such as described in FIG. 8A . In some embodiments, if the amount of separation between the location associated with the user and a location associated with the first remote locator object increases, the device again presents the separation warning.

[0252] The above-described methods of displaying separation warnings (e.g., by displaying a separation warning when the remote locator object is greater than a threshold distance from the user and by removing the separation warning when the remote locator object is less than a corresponding separation threshold) ensure that separation warnings are not displayed unless applicable (e.g., by ceasing to display the separation warning when the remote locator object is determined to be within a corresponding threshold distance from the user), thereby simplifying the interaction between the user and the electronic device and improving usability of the electronic device, making the user-device interface more efficient (e.g., by ceasing to display the separation warning when the remote locator object is determined to be currently within a particular threshold distance from the user without requiring the user to access the separation warning to determine whether the remote locator object is actually separated from the user), and additionally reducing power usage and improving battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0253] In some embodiments, the corresponding separation threshold is less than the first separation threshold (932), such as described in FIG. 8A (e.g., by 2 feet, 5 feet, 10 feet, etc. to avoid repeatedly presenting separation warnings and stopping the presentation of separation warnings when the user is exactly at the first separation threshold).

[0254] The above-described methods of displaying separation warnings (e.g., by ceasing the display of separation warnings when the remote locator object is below a corresponding separation threshold that is below the separation threshold for generating a separation warning) prevent separation warnings from being displayed and removed too frequently (e.g., by using hysteresis when displaying and removing the notification), thereby simplifying the interaction between the user and the electronic device and improving usability of the electronic device, making the user-device interface more efficient (e.g., by preventing separation warnings from being continuously displayed and removed when the user is at or near the threshold distance for generating a separation warning), and additionally reducing power usage and improving battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0255] In some embodiments, the electronic device receives (934) a request to view location information of a plurality of physical objects (e.g., one or more remote locator objects, one or more other devices, such as a watch, phone, computer, tablet, etc.) at the electronic device (e.g., selection of a separation alert, such as a separation alert or a tap gesture on a selectable affordance within the separation alert), such as in FIG. 8D . In some embodiments, in response to detecting the request to view location information of the plurality of physical objects, the electronic device displays (936) a status user interface including location information of the plurality of physical objects, including the first remote locator object (e.g., displaying an application for finding and / or locating objects and / or electronic devices in response to user input), such as in FIG. 8D . In some embodiments, the application for finding and / or locating objects is configured to locate and / or track the remote locator objects. In some embodiments, the application for finding and / or locating objects is configured to characterize and / or track the locations of a plurality of objects, such as the remote locator objects and / or other electronic devices. In some embodiments, in response to user input, the electronic device displays a user interface of the application including a map and / or list of objects being tracked. In some embodiments, a map and / or list of tracked objects is displayed along with an indication of each object's location (e.g., a text label and / or location on the map), including whether each object is with the user or near a landmark (e.g., work, home, another user, etc.).

[0256] The above-described methods of displaying location information for multiple objects (e.g., by displaying a user interface having location information for multiple objects being tracked by the device) provide a user with the ability to view multiple objects being tracked within a single user interface, thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing a single user interface that allows the user to view the location and status of all objects being tracked by the electronic device without the user having to navigate to a separate user interface to view location information for each object being tracked), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0257] In some embodiments, one or more representations of the physical object are marked with an indication that the physical object is located at a first location (e.g., home or work) identified in the descriptor selected by the user (938), such as in FIG. 8D. In some embodiments, the indication is a text indicator indicating that the object is "near home" or "near work." In some embodiments, the indication is a corresponding icon on a map indicating that the respective object is near a particular landmark (e.g., the map displays a location indicator for "home" or "work").

[0258] The above-described methods of indicating the location of a tracked object (e.g., by displaying a descriptive label of the tracked object's location) provide the user with a convenient label of the tracked object's location, thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by automatically labeling the tracked object's location with a user-selected descriptor without the user having to separately determine whether the object's location corresponds to a known location), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0259] In some embodiments, one or more representations of the physical object are marked (940) with an indication that the physical object is in a predefined location relative to a location associated with the user, such as in FIG. 8D (e.g., displaying a "with me" indicator when the remote locator object is determined to be within a particular distance (e.g., 1 foot, 3 feet, 5 feet, etc.) of the user).

[0260] The above-described method of indicating the location of a tracked object (by displaying a descriptive label that the object is with the user if the location is within a threshold distance from the user) provides the user with an at-a-glance description of whether the object is with the user (e.g., by displaying a label that the object is with the user), thereby simplifying the interaction between the user and the electronic device and improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing a simple descriptive label without the user having to separately determine whether the object's location is the same location as the user), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0261] In some embodiments, while displaying the status user interface, the electronic device detects (942) a sequence of one or more inputs including a selection of a selectable user interface object corresponding to a request to add a safe zone, such as in FIG. 8F (e.g., the user navigates to an area of the status user interface for managing trusted locations (e.g., safe zones) of remote locator objects and / or selects a selectable option to add a trusted location). In some embodiments, in response to detecting a sequence of one or more inputs including a selection of a selectable user interface object corresponding to a request to add a safe zone, the electronic device adds (944) a safety zone to the location selected by the user, the safety zone for each remote locator object being an area in which the device will not generate a separation alert (e.g., allow the user to add a new safe zone or trusted location) when the amount of separation between the location associated with the user and the location associated with the respective remote locator object is greater than (increases beyond) a first separation threshold while the respective remote locator object remains within the safe zone, such as in FIG. 8I ).

[0262] In some embodiments, the electronic device displays a user interface for managing safety zones in response to user input for managing safety zones of a remote locator object. In some embodiments, one or more previously set safety zones are presented to the user so that the user can toggle a previously set safety zone on (so that a separation alert is not triggered) or off (so that a separation alert is triggered). In some embodiments, the user interface for managing safety zones includes an option to select a new safety zone. In some embodiments, selecting a selectable option to add a new safety zone displays a user interface for adding a new safety zone. In some embodiments, the user interface for adding a new safety zone includes a map and / or a text field. In some embodiments, the user can move the map around and select a location on the map as a safety location (e.g., move a pin around or drop a pin on the map). In some embodiments, the user can type an address into the text field to select the address as a safety location. In some embodiments, as the user moves the map around, the text field is updated with the current address of the pin. In some embodiments, as the user types an address into the text field, the map is updated to show the location of the address.

[0263] The above-described method of setting a safe zone for a remote locator object (e.g., by adding a location as a safe zone where a separation alert will not be generated) provides a user with the ability to set a specific location as a location where a remote locator object is expected to be, prevents unnecessary display of separation alerts (e.g., by disabling the separation alert when the remote locator object is determined to be within the safe zone), thereby simplifying the interaction between the user and the electronic device and improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing a way for the user to suppress the separation alert without having to receive it, interact with it, and determine that the remote locator object is in a safe position), and additionally reduces power usage and improves the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0264] In some embodiments, the sequence of one or more inputs, including the selection of a selectable user interface object corresponding to the request to add a safety zone, includes the selection of a respective size for the safety zone from a number of predefined sizes (e.g., small (e.g., 100 feet, 300 feet, 500 feet), medium (¼ mile, ½ mile), large (1 mile, 2 miles)), such as in FIG. 8G (946). In some embodiments, the user may select the radius of the safety zone around the location the user wants to add. In some embodiments, the map user interface for adding a new safety zone displays an indication of the radius or size of the safety zone (e.g., a circular zone around a center point).

[0265] The above-described method of setting a safety zone for a remote locator object (e.g., by receiving a user selection of the size of the safety zone) allows for quick and efficient setting of the safety zone, thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing an easy way to set the size of the safety zone without the user having to add multiple safety zones to cover the desired safety zone size or without the user having to perform additional user input to provide a custom size each time the user adds a new safety zone), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0266] In some embodiments, the sequence of one or more inputs including the selection of a selectable user interface object corresponding to the request to add a safety zone includes an input corresponding to a dynamically selected size of the safety zone (e.g., a drag input to select a radius of the safety zone) (948), such as in FIG. 8G. In some embodiments, the user can resize the circular zone displayed on the map of the user interface for adding a new safety zone. In some embodiments, the user can provide a custom radius or area for the safety zone (e.g., by entering a specific radius rather than selecting a predefined size or manually resizing on the map).

[0267] The above-described method of setting a safe zone for a remote locator object (e.g., by receiving user input to manually adjust the size of the safe zone) provides the user with fine-grained control over the size of the safe zone, thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing an easy way to modify the size of the safe zone to arrive at a desired custom safe zone size), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0268] In some embodiments, while displaying the status user interface, the electronic device detects (950) a sequence of one or more inputs including a selection of a selectable user interface object corresponding to a request to share a location of each of the plurality of physical objects with a corresponding user other than the user of the device (e.g., the user navigates to an area of the status user interface for managing users with whom the remote locator object is shared and / or selects a selectable option to add a shared user), such as in FIGS. 8K-8L. In some embodiments, in response to detecting a sequence of one or more inputs including a selection of a selectable user interface object corresponding to a request to share the location of one of the physical objects with another user, the electronic device enables (952) the corresponding user to access a plurality of features corresponding to the location of each of the physical objects, including one or more of: determining a location of the respective physical object; receiving a separation alert when an amount of separation between the location of the respective physical object and the location of the other user exceeds a corresponding separation threshold; and selecting an identifier associated with the physical object (e.g., sharing the remote locator object with another user).

[0269] In some embodiments, one or more previously shared users are presented to the user, allowing the user to toggle previously shared users on or off. In some embodiments, a user interface for managing shared users includes an option to select a new shared user. In some embodiments, sharing a remote locator object with another user provides the other user with the ability to track and / or view the location of the remote locator object. In some embodiments, the other user may have access to all or a subset of the remote locator object's features available to the user (e.g., owner) of the remote locator object. For example, in some embodiments, the shared user may receive isolation alerts for the remote locator object and / or manage the remote locator object's safety zone.

[0270] The above-described methods of sharing a remote locator object with another user (e.g., by sharing with another user a remote locator object that includes the ability to track the location of the remote locator object) provide users with the ability to share features of their respective remote locator objects with other users (e.g., by automatically providing users receiving the share with multiple features that are also available to the owner of the remote locator object so that multiple users can track the remote locator object), thereby simplifying interaction between the user and the electronic device and improving usability of the electronic device, making the user-device interface more efficient (e.g., by providing a way to share a remote locator object with other users without having to use multiple remote locator objects, each associated with a different user, to achieve the same functionality), and additionally reducing power usage and improving battery life of the electronic device by allowing users to use the electronic device more quickly and efficiently.

[0271] In some embodiments, a sequence of one or more inputs including a selection of a selectable user interface object corresponding to a request to share the location of one of the physical objects with another user includes enabling sharing for a limited period of time (e.g., a limited time selected by the user, such as one hour, the rest of the day, etc.), such as in FIG. 8M (954). In some embodiments, once a user selects a user with whom to share the remote locator object, the user is presented with an option to select how long to share the remote locator object for. In some embodiments, the user is provided with a predetermined duration, such as the rest of the day or indefinitely. In some embodiments, the user can provide a custom duration.

[0272] The above-described methods of sharing a remote locator object with another user (e.g., by sharing the remote locator object with another user for a user-specified duration) avoid the need for the device to require additional input to turn off sharing, thereby simplifying the interaction between the user and the electronic device and improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing a way for the user to set the duration for sharing the remote locator object with other users without having to navigate to a separate user interface and / or remember to remove sharing with other users after the desired time), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0273] In some embodiments, when the location of the first remote locator object is shared with a second user (956), while the first remote locator object is associated with the second user, the electronic device obtains information indicating that an amount of separation between a location associated with the second user (e.g., as determined based on a device associated with the user, such as a watch or cell phone) and a location associated with the first remote locator object has increased beyond a first separation threshold (e.g., a distance threshold between a location associated with the second user and a location associated with the remote locator object), such as in FIG. 8A . In some embodiments, the information is obtained from a server tracking the second user's location relative to the location of the first remote locator object. In some embodiments, the information is obtained by the electronic device (e.g., the second user's electronic device) determining that the first remote locator object is more than a threshold distance away from the electronic device.

[0274] In some embodiments, in response to obtaining information indicating that the amount of separation between the location associated with the user and the location associated with the first remote locator object has increased beyond a first separation threshold, the electronic device generates (956) a separation alert at the electronic device indicating that the first remote locator object has become separated from the second user, such as as in FIG. 8A (e.g., instead of or in addition to generating a separation alert at the device associated with the first user, this separation alert is generated at the device associated with the second user). In some embodiments, this separation alert is not generated when the remote locator object is associated with multiple users, as long as the remote locator object is within the first separation threshold of at least one of the multiple users. For example, the separation alert received by each corresponding user is specific to the occurrence of separation between the remote locator object and the corresponding user. In some embodiments, each shared user receives a separation alert each time the first user (e.g., the owner) becomes separated from the remote locator object.

[0275] The above-described method of sharing a remote locator object with another user (e.g., by generating a separation alert for the shared user) provides a warning to the shared user that the shared user has separated from the remote locator object (e.g., by determining whether the corresponding shared user has separated from the remote locator object and displaying a separation alert to the corresponding shared user), thereby simplifying the interaction between the user and the electronic device and improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing a way for the shared user to receive the separation alert without the device owner having to separately notify the shared user of the separation or track the location of the remote locator object to determine whether it is still with the shared user), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0276] It should be understood that the particular order described for the operations in Figures 9A-9G is merely illustrative and is not intended to indicate that the described order is the only order in which the operations can be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that other process details described herein with respect to other methods described herein (e.g., methods 700, 1100, 1300, and 1400) are also applicable in a similar manner to method 900 described above with respect to Figures 9A-9G. For example, presenting a detachment notification as described above with reference to method 900 optionally has one or more of the characteristics, such as initializing a remote locator object, presenting a tracking notification, and discovering a remote locator object, as described herein with reference to other methods described herein (e.g., methods 700, 1100, 1300, and 1400). For the sake of brevity, those details will not be repeated here.

[0277] The operations in the information processing methods described above are optionally performed by running one or more functional modules in an information processing device, such as a general-purpose processor (e.g., as described above in connection with FIGS. 1A-1B, 3, 5A-5H) or an application-specific chip. Additionally, the operations described above with reference to FIGS. 9A-9G are optionally performed by the components shown in FIGS. 1A-1B. For example, displaying operation 936 and detecting operations 908, 942, 950 are optionally performed by event sorter 170, event recognizer 180, and event processor 190. Event monitor 171 of event sorter 170 detects a contact on touchscreen 504, and event dispatcher module 174 delivers the event information to application 136-1. Each event recognizer 180 of application 136-1 compares the event information with a respective event definition 186 to determine whether a first contact at a first location on the touchscreen corresponds to a predefined event or sub-event, such as selecting an object on a user interface. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates event handler 190 associated with the detection of that event or sub-event. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a corresponding GUI updater 178 to update what is displayed by the application. Similarly, it will be apparent to one skilled in the art how other processes can be implemented based on the components shown in FIGS. 1A-1B. Remote locator object tracking notification

[0278] Users interact with electronic devices in many different ways. In some embodiments, a remote locator object can report its location to the electronic device. The embodiments described below provide a way for the electronic device to provide an alert that an unknown remote locator object is tracking the user's location, thereby enhancing the user's interaction with the electronic device. Enhancing interaction with the device reduces the amount of time the user needs to perform an action, thus reducing the device's power usage and increasing battery life for battery-powered devices. It is understood that people use devices. When a person uses a device, that person is optionally referred to as the device's user.

[0279] 10A-10R illustrate example methods by which an electronic device displays a notification of a pursuit by an unknown remote locator object, according to some embodiments of the present disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to FIGS. 11A-11E.

[0280] 10A-10R illustrate an electronic device 500 displaying a notification of tracking by an unknown remote locator object. FIG. 10A illustrates an exemplary device 500 including a touchscreen 504. As shown in FIG. 10A, the electronic device 500 presents a lock screen user interface 1000 (e.g., a wake screen user interface). In some embodiments, the lock screen user interface 1000 is a user interface that is displayed when the electronic device 500 wakes up (e.g., from a sleep or locked state). In some embodiments, the lock screen user interface 1000 includes a notification 1002. In some embodiments, the notification 1002 notifies the user that an unknown remote locator object (e.g., optionally, a “locator”) is tracking (e.g., following) the user's location. In some embodiments, the notification 1002 hides personal information of the owner of the remote locator object, such as the object's label and the owner's name. In some embodiments, the notification 1002 indicates to the user that the owner of the unknown remote locator object can view the location of the remote locator object.

[0281] In some embodiments, notification 1002 is displayed when electronic device 500 (e.g., or a server) determines that the location of the remote locator object is tracking the user's location. In some embodiments, a remote locator object is determined to be tracking the user's location if the remote locator object's location is the same as (or within a threshold distance, such as 5 feet, 10 feet, 20 feet, etc.) the user's location for a threshold time (e.g., 30 minutes, 1 hour, 2 hours). In some embodiments, a remote locator object is determined to be tracking the user's location if the remote locator object's location is the same as the user's location after traveling a threshold distance (e.g., 1 mile, 2 miles, 3 miles). In some embodiments, a remote locator object is determined to be tracking the user's location if the remote locator object's location is within a threshold distance (e.g., 2 feet, 3 feet, 4 feet, 10 feet) from the user. In some embodiments, a corresponding remote locator object is determined to be unknown if the corresponding remote locator object is not associated with the user / user account of device 500 and is not shared with the user / user account of device 500 (e.g., associated with another user account). In some embodiments, a remote locator object that was previously shared with a user but is not currently shared with the user is also considered to be an unknown remote locator object that triggers a tracking alert. In some embodiments, any combination of the above may be a factor or requirement for determining whether a remote locator object is tracking a user.

[0282] Although notification 1002 is shown as being displayed on lock screen user interface 1000, it is understood that notification 1002 may be displayed on other user interfaces (e.g., in any situation in which other notifications may be displayed).

[0283] In FIG. 10A , user input 1003 is received by selecting notification 1002. In some embodiments, in response to the user input, electronic device 500 displays user interface 1010, as shown in FIG. 10B . In some embodiments, user interface 1010 is a card user interface overlaid on another user interface (e.g., a home screen user interface, etc.). In some embodiments, user interface 1010 includes a map 1012 showing the current location of the user (e.g., of the remote locator object that is tracking the user). In some embodiments, user interface 1010 includes selectable options 1014-1 through 1014-3 that perform functions on the remote locator object that is tracking the user. In some embodiments, selectable option 1014-1 is selectable to allow the unknown remote locator object to track the user for the remainder of the day (e.g., thereby suppressing future tracking alerts for the corresponding unknown remote locator object for the remainder of the day). In some embodiments, selectable option 1014-2 is selectable to allow the unknown remote locator object to track the user indefinitely (e.g., thus suppressing all future tracking alerts for the corresponding unknown remote locator object). In some embodiments, selectable option 1014-3 is selectable to provide more information about the remote locator object.

[0284] 10B, user input 1003 is received by selecting selectable option 1014-1. In some embodiments, in response to the user input, device 500 initiates a process to allow the unknown remote locator to track the user's location for the remainder of the day. In some embodiments, once the unknown remote locator is allowed to track the user's location, tracking alerts (e.g., notification 1002, etc.) are no longer displayed on device 500 for the remainder of the current day. In some embodiments, after tracking by the unknown remote locator object is allowed, the unknown remote locator object is added to the user's application for tracking and finding items and, optionally, displayed on user interface 1020 as an item that device 500 is tracking, such as in FIG. 10C. In some embodiments, user interface 1020 is similar to user interface 670. In some embodiments, user interface 1020 lists item 1026-1 corresponding to the unknown remote locator object. In some embodiments, item 1026-1 indicates the amount of time for which tracking alerts will be suppressed (e.g., for an additional 8 hours and 13 minutes). In some embodiments, item 1026-1 does not reveal the name or label of the owner of the remote locator object, protecting the privacy of the owner of the remote locator object (e.g., the user account associated with it). In some embodiments, while tracking by an unknown remote locator object is permitted, the user may receive a separation alert if the unknown remote locator object separates from the user's location by more than a threshold distance (e.g., 10 feet, 30 feet, 100 feet), similar to separation alert 802 described above with respect to Figures 8A-8P.

[0285] 10D, user input 1003 is received by selecting selectable option 1014-2 in user interface 1010. In some embodiments, in response to the user input, device 500 displays user interface 1030, as shown in FIG. 10E. In some embodiments, to allow tracking indefinitely, device 500 requires the user to bring device 500 within a threshold distance (e.g., 1 inch, 3 inches, 5 inches) of the unknown remote locator object. In some embodiments, this ensures that the user has found the unknown remote locator object and / or that the user knows exactly which item is tracking the user's location (e.g., and does not accidentally acknowledge the wrong object). In some embodiments, user interface 1030 instructs the user to tap the unknown remote locator object using device 500 (e.g., bring device 500 within a threshold distance of the unknown remote locator object). In some embodiments, user interface 1030 includes an illustration 1032 (e.g., a still image, a short video, an animation, etc.) of tapping the remote locator object with device 500. In some embodiments, the user interface 1030 includes a selectable option 1034 that can be selected to cause the unknown remote locator object to emit an audible sound.

[0286] 10F, the user brings device 500 within the threshold distance of unknown remote locator object 1000. In some embodiments, in response to bringing device 500 within the threshold distance of unknown remote locator object 1000, communication is established between device 500 and unknown remote locator object 1000. In some embodiments, device 500 confirms that unknown remote locator object 1000 is the unknown remote locator object that is tracking the user's location. In some embodiments, in response to bringing device 500 within the threshold distance of unknown remote locator object 1000, device 500 initiates a process to authorize the unknown remote locator object to track the user's location for the remainder of the day (e.g., or optionally, until the user removes authorization). In some embodiments, after the unknown remote locator object is authorized, it is added to user interface 1020 (e.g., similar to that described above with respect to FIG. 10C) as shown in FIG. 10G. In some embodiments, item 1026-1 is displayed with an indicator that the remote locator object will be ignored indefinitely, hi some embodiments, item 1026-1 is selectable to change the user's permission settings (e.g., to set a time limit for ignoring the object, or to remove permission, etc.).

[0287] 10H, user input 1003 is received by selecting selectable option 1014-3 in user interface 1010. In some embodiments, in response to the user input, device 500 displays user interface 1040, as shown in FIG. 10I. In some embodiments, user interface 1040 displays a representation 1042 of the remote locator object that is tracking the user. In some embodiments, representation 1042 is an icon of the remote locator object. In some embodiments, representation 1042 is an interactable model of the remote locator object. For example, in some embodiments, user input on representation 1042 optionally causes representation 1042 to spin or rotate in accordance with the user input. In some embodiments, representation 1042 spins, rotates, or otherwise animates on its own (e.g., without user intervention).

[0288] In some embodiments, user interface 1040 includes selectable options 1044-1, 1044-2, and 1044-3. In some embodiments, selectable option 1044-1 is selectable to cause the remote locator object to emit an audible sound, allowing a user to find the remote locator object. In some embodiments, selectable option 1044-2 is selectable to allow a user to ignore the remote locator object (e.g., in a process similar to that described above with respect to FIGS. 10B-10G). In some embodiments, selectable option 1044-3 is selectable to display instructions to disable the remote locator object. For example, in FIG. 10J, user input 1003 is received selecting selectable option 1044-3. In some embodiments, in response to the user input, device 500 displays user interface 1050. In some embodiments, user interface 1050 displays a representation 1052 of the remote locator object. In some embodiments, representation 1052 is an animation illustrating the steps of disassembling and disabling the remote locator object (e.g., optionally removing the battery in the remote locator object), as shown in Figures 10K-10M. Selection of selectable option 1054 causes device 500 to stop displaying user interface 1050 without allowing the remote locator object to track the user's location.

[0289] 10N-10P illustrate example embodiments for displaying a tracking notification for an unknown remote locator object that has been marked as lost by the owner of the unknown remote locator object. In FIG. 10N, notification 1002 is displayed on lock screen user interface 1000. In some embodiments, notification 1002 indicates that the lost locator is tracking the user's location. In some embodiments, notification 1002 is displayed on device 500 in response to determining that the location of the lost remote locator object is tracking the user's location. Thus, in some embodiments, notification 1002 for a lost remote locator object is triggered based on the same factors and / or requirements that triggered notification 1002 described above with respect to FIG. 10A (e.g., except that notification 1002 indicates that the remote locator object has been lost).

[0290] 10N, user input 1003 is received selecting notification 1002. In some embodiments, in response to the user input, device 500 displays user interface 1060, as shown in FIG. 10O. In some embodiments, user interface 1060 displays a representation 1062 of the remote locator object (e.g., similar to representation 1042). In some embodiments, user interface 1060 includes selectable options 1064-1, 1064-2, and 1064-3. In some embodiments, selectable option 1064-1 is selectable to display a message from the owner of the lost remote locator object. In some embodiments, selectable option 1064-2 is selectable to cause the lost remote locator object to emit an audible sound. In some embodiments, selectable option 1064-3 is selectable to display instructions to disable the remote locator object (e.g., similar to user interface 1050 described above with respect to FIGS. 10K-10M).

[0291] In FIG. 10O , user input 1003 is received by selecting selectable option 1064-1. In some embodiments, in response to the user input, device 500 updates user interface 1060 to reveal a message 1066 provided by the object's owner. In some embodiments, selectable option 1064-1 is updated from being selectable to reveal a message from the owner to being selectable to initiate a process to contact the owner of the lost remote locator object. In some embodiments, the process of contacting the owner of the lost remote locator object includes displaying one or more selectable options to contact the owner using one or more communication mediums (e.g., call, text, email, etc.). In some embodiments, the privacy of the remote locator object's owner is maintained (e.g., the owner's name, contact details are not revealed to the user) unless the owner chooses to reveal personal details (e.g., by including personal information in message 1066).

[0292] 10Q-10R illustrate example embodiments in which device 500 is placed within a threshold distance (e.g., an NFC communication distance of 1, 3, 5 inches, etc.) of a remote locator object 1000 that has been marked as lost (but is not tracking the user's location). FIG. 10Q shows device 500 and remote locator object 1000. In FIG. 10Q, remote locator object 1000 has been marked as lost by the owner of remote locator object 1000. In FIG. 10R, the user brings device 500 within the threshold distance of remote locator object 1000. In some embodiments, in response to placing device 500 within the threshold distance of remote locator object 1000, device 500 communicates with remote locator object 1000 and displays user interface 1080 superimposed on a user interface previously displayed on device 500 (e.g., user interface 1070). In some embodiments, user interface 1080 is a "quick" control sheet that displays information about the remote locator object 1000 and one or more selectable options for contacting the owner of the remote locator object 1000 (or its associated user account). In some embodiments, user interface 1080 displays a message 1082 from the owner of the remote locator object 1000. In some embodiments, user interface 1080 includes selectable options 1084-1, 1084-2, and 1084-3. In some embodiments, selectable option 1084-1 is selectable to send the location of the remote locator object 1000 to the owner. In some embodiments, selectable option 1084-2 is selectable to send a text message to the owner. In some embodiments, selectable option 1084-3 is selectable to call the owner.In some embodiments, similar to those described above, the privacy of the owner of the remote locator object is maintained (e.g., the owner's name, contact details are not revealed to the user) unless the owner chooses to reveal personal details (e.g., by including personal information in message 1082).

[0293] 11A-11E are flow diagrams illustrating a method 700 for displaying notification of tracking by an unknown remote locator object, according to some embodiments, such as in FIGS. 10A-10R. Method 1100 is optionally performed in an electronic device, such as device 100, device 300, or device 500, as described above with reference to FIGS. 1A-1B, 2-3, 4A-4B, and 5A-5H. Some operations in method 1100 are optionally combined, and / or the order of some operations is optionally changed.

[0294] As described below, method 1100 provides a way to display notification of tracking by an unknown remote locator object. This method reduces the cognitive burden on a user when interacting with the user interface of a device of the present disclosure, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, improving the efficiency of the user's interaction with the user interface conserves power and increases the time between battery charges.

[0295] In some embodiments, such as in FIG. 10A , an electronic device having one or more wireless antennas, a display device, and one or more input devices (e.g., a mobile device (e.g., a tablet, smartphone, media player, or wearable device) including a touchscreen and wireless communication circuitry, or a computer including one or more of a keyboard, mouse, trackpad, and touchscreen and wireless communication circuitry) automatically presents 1102 a tracking alert indicating that a remote locator object not associated with the user meets the tracking criteria (e.g., the remote locator object is tracking or otherwise following the location of the user and / or electronic device) without user input, such as in FIG. 10A (e.g., displaying a notice or other alert on the electronic device indicating that an unknown remote locator object (e.g., a remote locator object not associated with and / or shared with the user) is tracking the user and / or electronic device) pursuant to a determination that the remote locator object associated with a user other than the user of the electronic device meets the tracking criteria (e.g., the remote locator object is tracking or otherwise following the location of the user and / or electronic device) while the remote locator object is near the electronic device (e.g., within 3 feet, 10 feet, 20 feet of the user). In some embodiments, the tracking criteria are met if the location of the remote locator object has been following or tracking the electronic device for longer than a threshold time / distance (e.g., time and / or distance, e.g., for the last 20 feet, 50 feet, 100 feet, the last 5 minutes, 10 minutes, 15 minutes, etc.).

[0296] In some embodiments, a remote locator object is considered to be following or tracking an electronic device if the location of the remote locator object is within 1, 2, or 3 feet of the electronic device for a threshold time and / or distance. In some embodiments, a remote locator object is considered to be following or tracking an electronic device if the distance between the remote locator object and the electronic device does not change substantially (e.g., within 5%, 10%, or 15%) over a threshold amount (of time and / or distance). In some embodiments, any combination of these criteria is contemplated. In some embodiments, a detailed tracking alert is displayed in response to selection of a tracking alert (e.g., selection of a tracking alert, such as by tapping on a tracking alert). In some embodiments, if a remote locator object not associated with a user does not meet the tracking criteria, a tracking alert is not displayed. In some embodiments, a remote locator object not associated with a user but shared with the user does not meet the tracking criteria and therefore does not trigger a tracking alert. In some embodiments, if one or more of the above criteria are not met, the tracking criteria are not met.

[0297] The above-described method of alerting a user that an unknown remote locator object meets tracking criteria (e.g., by automatically displaying a tracking alert to the user when the unknown remote locator object is tracking the user) provides a warning to the user when a remote locator object is tracking the user (e.g., by automatically displaying a tracking alert without user input when it is determined that the remote locator object is tracking the user), thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing a warning to the user that a potentially unauthorized remote locator object is tracking the user's location), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0298] In some embodiments, the tracking criteria may include a requirement that a location associated with a remote locator object is within a predetermined threshold distance of a location associated with a user (e.g., an unidentified remote locator object is within a threshold distance (e.g., 1 foot, 2 feet, 3 feet) from the user), a requirement that a location associated with a remote locator object remains within a threshold distance of a location associated with a user for at least a threshold time (e.g., a remote locator object remains within a threshold distance from the user for a threshold time (e.g., 5 minutes, 15 minutes, 30 minutes)), a requirement that a remote locator object is not associated with a user (e.g., , that the unconfirmed remote locator object is not owned by or otherwise shared with the user (in some embodiments, the unconfirmed remote locator object is owned by or otherwise associated with another user)), and that the remote locator object is reporting its location to another user (e.g., that the unconfirmed remote locator object is configured and paired with or otherwise associated with another user / user account such that the other user can track the location of the remote locator object and therefore the user's location) (1104). In some embodiments, the tracking criteria include a requirement that the remote locator object remains within a threshold distance from the user, even if the user moves or otherwise changes location. In some embodiments, the tracking criteria include a requirement that the remote locator object remains within a threshold distance from the user over a threshold distance amount (e.g., 50 feet, 100 feet, 200 feet, etc.) traveled by the user. In some embodiments, the tracking criteria include any combination of these requirements.

[0299] The above-described method of alerting a user that an unknown remote locator object satisfies the tracking criteria (e.g., by determining that one or more tracking criteria are met) allows the electronic device to determine that a remote locator object is truly tracking the user and avoid unnecessarily displaying tracking alerts (e.g., by requiring satisfaction of certain conditions when determining that the remote locator object is tracking the user), thereby simplifying the interaction between the user and the electronic device and improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing a warning to the user that an unauthorized remote locator object is tracking the user's location when it is likely that the remote locator object is actually tracking the user's location), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently while reducing errors in using the device.

[0300] In some embodiments, the tracking alert includes selectable options (1108) that include information that allows the user to visually identify the remote locator object (e.g., a visual or textual description of the remote locator object, such as a virtual three-dimensional model of the remote locator object), such as in FIG. 10I.

[0301] The above-described methods of alerting a user that an unknown remote locator object meets tracking criteria (e.g., by displaying information such as a visual illustration of the remote locator object to enable the user to identify the remote locator object) provide the user with the ability to find and identify the remote locator object that is tracking the user (e.g., by displaying an illustration of the remote locator object), thereby simplifying the interaction between the user and the electronic device, improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing the user with the ability to find and identify the remote locator object without requiring the user to perform separate research to determine what the remote locator object may look like), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0302] In some embodiments, the tracking alert includes a selectable option to ignore future alerts that the remote locator object meets the tracking criteria (1106), such as in FIG. 10B (e.g., the tracking alert includes a selectable option selectable to ignore tracking of the remote locator object such that tracking alerts for unconfirmed remote locator objects are suppressed or otherwise not displayed). In some embodiments, the user can set a duration for ignoring remote locator objects.

[0303] The above-described method of ignoring tracking alerts (e.g., by providing a selectable option to ignore future tracking alerts associated with a remote locator object) provides the user with the option to disable the alert for a remote locator object when the remote locator object is known to the user, preventing further display of tracking alerts that the user must perform additional input to dismiss, thereby simplifying the interaction between the user and the electronic device and improving usability of the electronic device, making the user-device interface more efficient (e.g., by giving the user the option to automatically dismiss future alerts without unnecessarily providing the user with alerts and requiring the user to verify each time that they should ignore the tracking alert), and additionally reducing power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0304] In some embodiments, the electronic device detects 1110 a sequence of one or more inputs including a selection of a selectable option to ignore future alerts that the remote locator object meets the tracking criteria (e.g., a selection of a “Dismiss Alert” affordance followed by a selection of a “Until the End of Day” affordance), such as in FIG. 10B . In some embodiments, in response to receiving user input selecting the “Dismiss Alert” affordance, the device displays a user interface including a selectable option to select the duration for how long to ignore the alert. In some embodiments, predetermined duration options are displayed, such as a selectable “Until the End of Day” affordance to dismiss the tracking alert until the end of day and / or a selectable “Indefinitely” affordance to begin the process of dismissing the tracking alert indefinitely. In some embodiments, in response to detecting a sequence of one or more inputs including a selection of a selectable option to ignore future alerts that the remote locator object meets the tracking criteria, the electronic device discontinues displaying future alerts that the remote locator object meets the tracking criteria (1112) for a predetermined time threshold (e.g., 1 hour, 2 hours, until the end of the day, until the end of the week), such as in FIG. 10C . In some embodiments, a user may provide a custom duration. In some embodiments, even while the device discontinues displaying future alerts that the remote locator object meets the tracking criteria, the device continues to generate alerts that other remote locator objects meet the tracking criteria, if other remote locator objects meet the tracking criteria (e.g., discontinuing tracking applies only to the particular remote locator object whose tracking was detected).

[0305] The above-described method of dismissing tracking alerts (e.g., by ceasing the display of future alerts for a predetermined time period in response to detecting a selection of an option to ignore the alert for a predetermined time period) provides a user with the ability to disable tracking alerts for a predetermined time period when the user expects a remote locator object to be following the user for a predetermined time period, thereby simplifying the interaction between the user and the electronic device, improving usability of the electronic device, making the user-device interface more efficient (e.g., by providing a user with the ability to suppress tracking alerts for a predetermined time period without requiring the user to dismiss future tracking alerts and later re-enable the tracking alerts after a predetermined time period or without requiring the user to continue dismissing the tracking alerts for a predetermined time period), and additionally reducing power usage and improving battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0306] In some embodiments, in response to detecting a sequence of one or more inputs including selection of a selectable option to ignore future alerts that the remote locator object meets the tracking criteria, the electronic device adds (1114) the remote locator object to a set of physical objects available for viewing within a location tracking status user interface on the device, such as as in FIG. 10C (e.g., adding an unconfirmed remote locator object to a status user interface that includes physical objects associated with the user after receiving user input to ignore future tracking alerts). In some embodiments, when the remote locator object is added to the tracking status user interface, the remote locator object is displayed with an indication of its location relative to a location associated with the user and / or an indication of how long the user has been ignoring the remote locator object's location. In some embodiments, when the remote locator object is added to the tracking status user interface, the name of the owner of the remote locator object is not indicated. For example, the remote locator object is identified as "someone's locator," "unknown locator," etc.

[0307] The above-described method of ignoring a warning that an unknown remote locator object meets the tracking criteria (e.g., by adding the remote locator object to the set of objects being tracked by the electronic device when the user selects to ignore the tracking warning associated with the remote locator object) provides a reminder to the user that the remote locator object is still tracking the user even after the user dismisses the tracking warning (e.g., by displaying the remote locator object that is tracking the user along with the set of objects being tracked by the user), thereby simplifying the interaction between the user and the electronic device and improving the usability of the electronic device, making the user-device interface more efficient (e.g., by providing t...

Claims

1. An electronic device having one or more wireless antennas, a display device, and one or more input devices, Detecting via the one or more wireless antennas that a remote locator object is in proximity to the electronic device; In response to detecting that the remote locator object is near the electronic device, displaying, via the display device, a configuration user interface for configuring the remote locator object within a predetermined area of the display; After displaying the setting user interface via the display device, displaying an identifier user interface for selecting an identifier of the remote locator object within the predetermined area of the user interface displayed via the display device; detecting, while displaying the identifier user interface, one or more user inputs via the one or more input devices selecting a corresponding identifier of the remote locator object; displaying, after the corresponding identifier of the remote locator object is selected, a user interface with additional information regarding the functionality of the remote locator object, the user interface with additional information including a description of at least one functionality of the remote locator object and identifying the remote locator object by a combination of the corresponding identifier and a name of a user of the device; A method comprising:

2. The method of claim 1 , wherein the configuration user interface is displayed when the remote locator object is detected in the vicinity of the electronic device while the remote locator object is in a first state.

3. 3. The method of claim 1 or 2, wherein the predetermined area occupies less than all of the displayed user interface, and a representation of at least a portion of the user interface that was displayed before detecting the remote locator object near the electronic device is displayed on a portion of the user interface that is outside the predetermined area.

4. The method of claim 1 , wherein the identifier user interface includes a plurality of predefined identifiers.

5. The method of claim 4 , wherein detecting one or more user inputs that select the corresponding identifier of the remote locator object comprises detecting user input that provides a custom identifier.

6. 6. The method of claim 1, wherein displaying the configuration user interface comprises displaying a pairing animation including a representation of the remote locator object and a selectable affordance for initiating a pairing process.

7. 7. A method according to claim 1, wherein the user interface having additional information about the functionality of the remote locator object includes a map having an indication of the location of the remote locator object, where the remote locator object is identified by the corresponding identifier and the name of the user of the device.

8. The method of claim 1 , wherein the user interface with additional information about the functionality of the remote locator object includes information about a plurality of features of the remote locator object.

9. 9. The method of claim 1, wherein the user interface having additional information regarding the functionality of the remote locator object includes information indicating that the remote locator object has been detected as being held by the user of the device.

10. the user interface having additional information about the functionality of the remote locator object includes a selectable user interface object associated with an application corresponding to the remote locator object; The method comprises: Detecting a selection of the selectable user interface object; In response to detecting a selection of the selectable user interface object, displaying a user interface of the application corresponding to the remote locator object; Including, 10. The method according to any one of claims 1 to 9.

11. detecting, via the one or more wireless antennas, respective remote locator objects associated with respective user accounts different from a user account associated with the electronic device in proximity to the electronic device; In response to detecting that the respective remote locator object is in the vicinity of the electronic device, displaying via the display device an informational user interface indicating that the respective remote locator object is associated with a user account other than the user account associated with the electronic device, the informational user interface including a first selectable option selectable to request from the respective user account to share and access the respective remote locator object with the user account associated with the electronic device; Further comprising:

11. The method according to any one of claims 1 to 10.

12. one or more processors; Memory and One or more programs; wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: Detecting via one or more wireless antennas that a remote locator object is in proximity to the electronic device; In response to detecting that the remote locator object is near the electronic device, displaying, via a display device, a configuration user interface for configuring the remote locator object within a predetermined area of the display; After displaying the setting user interface via the display device, displaying an identifier user interface for selecting an identifier of the remote locator object within the predetermined area of the user interface displayed via the display device; detecting, while displaying the identifier user interface, one or more user inputs via one or more input devices selecting corresponding identifiers of the remote locator objects; displaying, after the corresponding identifier of the remote locator object is selected, a user interface having additional information regarding the functionality of the remote locator object, the additional information including a description of at least one function of the remote locator object and identifying the remote locator object by a combination of the corresponding identifier and a name of a user of the device. An electronic device containing instructions.

13. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to: Detecting, via one or more wireless antennas, a remote locator object in proximity to the electronic device; In response to detecting that the remote locator object is near the electronic device, displaying, via a display device, a configuration user interface for configuring the remote locator object within a predetermined area of the display; After displaying the setting user interface via the display device, displaying an identifier user interface for selecting an identifier of the remote locator object within the predetermined area of the user interface displayed via the display device; detecting, while displaying the identifier user interface, one or more user inputs via one or more input devices selecting a corresponding identifier of the remote locator object; displaying, after the corresponding identifier of the remote locator object is selected, a user interface with additional information regarding the functionality of the remote locator object, the user interface with additional information including a description of at least one functionality of the remote locator object and identifying the remote locator object by a combination of the corresponding identifier and a name of a user of the device; A non-transitory computer-readable storage medium for causing a method to be performed, comprising:

14. 1. An electronic device comprising: one or more processors; Memory and means for detecting, via one or more wireless antennas, the presence of a remote locator object in the vicinity of said electronic device; means for displaying, via a display device, a configuration user interface for configuring the remote locator object within a predetermined area of the display in response to detecting that the remote locator object is near the electronic device; means for displaying, after displaying the setting user interface via the display device, an identifier user interface for selecting an identifier of the remote locator object within the predetermined area of the user interface displayed via the display device; means for detecting, while displaying the identifier user interface, one or more user inputs via one or more input devices selecting corresponding identifiers of the remote locator objects; means for displaying, after the corresponding identifier of the remote locator object is selected, a user interface having additional information regarding the functionality of the remote locator object, the user interface having additional information including a description of at least one function of the remote locator object and identifying the remote locator object by a combination of the corresponding identifier and a name of a user of the device; An electronic device comprising:

15. 1. An information processing apparatus for use in an electronic device, comprising: means for detecting, via one or more wireless antennas, the presence of a remote locator object in the vicinity of said electronic device; means for displaying, via a display device, a configuration user interface for configuring the remote locator object within a predetermined area of the display in response to detecting that the remote locator object is near the electronic device; means for displaying, after displaying the setting user interface via the display device, an identifier user interface for selecting an identifier of the remote locator object within the predetermined area of the user interface displayed via the display device; means for detecting, while displaying the identifier user interface, one or more user inputs via one or more input devices selecting corresponding identifiers of the remote locator objects; means for displaying, after the corresponding identifier of the remote locator object is selected, a user interface having additional information regarding the functionality of the remote locator object, the user interface having additional information including a description of at least one function of the remote locator object and identifying the remote locator object by a combination of the corresponding identifier and a name of a user of the device; An information processing device comprising:

16. one or more processors; Memory and One or more programs; 12. An electronic device comprising: one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 1 to 11.

17. 12. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method of any one of claims 1 to 11.

18. An electronic device having one or more wireless antennas, a display device, and one or more input devices, obtaining information indicating that, while a first remote locator object is associated with a user, an amount of separation between a location associated with the user and a location associated with the first remote locator object has increased beyond a first separation threshold; In response to obtaining the information indicating that the amount of separation between the location associated with the user and the location associated with the first remote locator object has increased beyond the first separation threshold, generating, at the electronic device, a separation alert indicating that the first remote locator object has become separated from the user; A method comprising:

19. the separation warning includes a visual element displayed via the display device; The method comprises: detecting a sequence of one or more inputs, including an input directed to the separation warning, while displaying the separation warning; 19. The method of claim 18, further comprising: in response to detecting the sequence of one or more inputs, marking a location associated with the first remote locator object as a safe zone for the remote locator object, wherein the safety zone for each remote locator object is an area within which the device will not generate a separation alert when the amount of separation between the location associated with the user and the location associated with the respective remote locator object is greater than the first separation threshold while the respective remote locator object remains within the safe zone.

20. The method of claim 19 , wherein the sequence of one or more inputs includes a user input that sets the size and / or shape of the safety zone.

21. 21. The method of claim 19 or 20, wherein marking the location associated with the first remote locator object as a safe zone for the remote locator object includes marking a person other than the user as a safe person, and wherein a separation alert is not generated when the amount of separation between the location associated with the user and the location associated with the respective remote locator object is greater than the first separation threshold while the respective remote locator object remains within the safe person threshold distance.

22. the user is associated with a plurality of remote locator objects, including a second remote locator object; the method comprising: while each region is established as a safe zone for the first remote locator object but not as a safe zone for the second remote locator object, and the first remote locator object and the second remote locator object are associated with respective locations within the safe zones; obtaining information indicating that an amount of separation between a location associated with the user and a location associated with the first remote locator object has increased beyond the first separation threshold; obtaining information indicating that an amount of separation between a location associated with the user and a location associated with the second remote locator object has increased beyond the first separation threshold; generating, at the electronic device, a separation alert indicating that the second remote locator object has been separated from the user without generating a separation alert indicating that the first remote locator object has been separated from the user, in response to obtaining the information indicating that the amount of separation between the location associated with the user and the location associated with the first remote locator object has increased beyond the first separation threshold and obtaining the information indicating that the amount of separation between the location associated with the user and the location associated with the second remote locator object has increased beyond the first separation threshold; 22. The method of any one of claims 18 to 21, further comprising:

23. 23. The method of any one of claims 18 to 22, wherein the separation warning includes a map having a representation of the location associated with the first remote locator object.

24. 24. The method of any one of claims 18 to 23, wherein the separation warning includes an indication of a time when the location associated with the first remote locator object was determined and an indication of a distance between the location associated with the first remote locator object and the location associated with the user.

25. obtaining information indicating that the amount of separation between the location associated with the user and the location associated with the first remote locator object is less than a corresponding separation threshold; ceasing to present the separation alert in response to obtaining the information indicating that the amount of separation between the location associated with the user and the location associated with the first remote locator object is less than the corresponding separation threshold; and 25. The method of any one of claims 18 to 24, comprising:

26. 26. The method of claim 25, wherein the corresponding separation threshold is less than the first separation threshold.

27. receiving, at the electronic device, a request to view location information of a plurality of physical objects; In response to detecting the request to view location information of the plurality of physical objects, displaying a status user interface including location information of a plurality of physical objects including the first remote locator object; Including, 27. The method of any one of claims 18 to 26.

28. 28. The method of claim 27, wherein one or more representations of a physical object are marked with an indication that the physical object is located at a first location identified in a descriptor selected by the user.

29. 29. The method of claim 27 or 28, wherein one or more representations of a physical object are marked with an indication that the physical object is in a predefined position defined relative to the location associated with the user.

30. detecting, while displaying the status user interface, a sequence of one or more inputs including a selection of a selectable user interface object corresponding to a request to add a safety zone; and adding a safety zone to a location selected by the user in response to detecting the sequence of one or more inputs including a selection of the selectable user interface object corresponding to a request to add a safety zone, wherein the safety zone of each remote locator object is an area in which the device does not generate a separation warning when the amount of separation between the location associated with the user and the location associated with the respective remote locator object is greater than the first separation threshold while the respective remote locator object remains within the safety zone.

31. 31. The method of claim 30, wherein the sequence of one or more inputs including a selection of the selectable user interface object corresponding to the request to add the safety zone includes a selection of a size for each of the safety zones from a plurality of predefined sizes.

32. 32. The method of claim 30 or 31, wherein the sequence of one or more inputs including the selection of the selectable user interface object corresponding to the request to add the safety zone includes an input corresponding to a dynamically selected size of the safety zone.

33. detecting, while displaying the status user interface, a sequence of one or more inputs including a selection of a selectable user interface object corresponding to a request to share the position of each of the plurality of physical objects with a corresponding user other than the user of the device; In response to detecting the sequence of one or more inputs including a selection of the selectable user interface object corresponding to the request to share the location of one of the physical objects with another user, enabling the corresponding user to access a plurality of features corresponding to the location of the respective physical object, including one or more of: determining a location of the respective physical object; receiving a separation alert when an amount of separation between the location of the respective physical object and a location of the other user exceeds a corresponding separation threshold; and selecting an identifier associated with the physical object; 33. The method of any one of claims 27 to 32, comprising:

34. 34. The method of claim 33, wherein the sequence of one or more inputs including a selection of the selectable user interface object corresponding to the request to share the location of one of the physical objects with another user includes enabling the sharing for a limited period of time.

35. when the location of the first remote locator object is shared with a second user; obtaining information indicating that, while the first remote locator object was associated with the second user, an amount of separation between a location associated with the second user and a location associated with the first remote locator object increased beyond the first separation threshold; In response to obtaining the information indicating that the amount of separation between the location associated with the user and the location associated with the first remote locator object has increased beyond the first separation threshold, generating, at the electronic device, a separation alert indicating that the first remote locator object has become separated from the second user; 35. The method of claim 33 or 34, comprising:

36. one or more processors; Memory and One or more programs; wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: obtaining information indicating that, while a first remote locator object is associated with a user, an amount of separation between a location associated with the user and a location associated with the first remote locator object has increased beyond a first separation threshold; generating, at the electronic device, a separation alert indicating that the first remote locator object has become separated from the user, in response to obtaining the information indicating that the amount of separation between the location associated with the user and the location associated with the first remote locator object has increased beyond the first separation threshold. An electronic device containing instructions.

37. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to: obtaining information indicating that, while a first remote locator object is associated with a user, an amount of separation between a location associated with the user and a location associated with the first remote locator object has increased beyond a first separation threshold; In response to obtaining the information indicating that the amount of separation between the location associated with the user and the location associated with the first remote locator object has increased beyond the first separation threshold, generating, at the electronic device, a separation alert indicating that the first remote locator object has become separated from the user; A non-transitory computer-readable storage medium for causing a method to be performed, comprising:

38. 1. An electronic device comprising: one or more processors; Memory and means for obtaining information indicating that, while a first remote locator object is associated with a user, an amount of separation between a location associated with the user and a location associated with the first remote locator object has increased beyond a first separation threshold; means for generating, at the electronic device, a separation alert indicating that the first remote locator object has become separated from the user, in response to obtaining the information indicating that the amount of separation between the location associated with the user and the location associated with the first remote locator object has increased beyond the first separation threshold; An electronic device comprising:

39. 1. An information processing apparatus for use in an electronic device, comprising: means for obtaining information indicating that, while a first remote locator object is associated with a user, an amount of separation between a location associated with the user and a location associated with the first remote locator object has increased beyond a first separation threshold; means for generating, at the electronic device, a separation alert indicating that the first remote locator object has become separated from the user, in response to obtaining the information indicating that the amount of separation between the location associated with the user and the location associated with the first remote locator object has increased beyond the first separation threshold; An information processing device comprising:

40. one or more processors; Memory and One or more programs; 36. An electronic device comprising: one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 18 to 35.

41. 36. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method of any one of claims 18 to 35.

42. one or more processors; Memory and means for carrying out the method of any one of claims 18 to 35; An electronic device comprising:

43. 1. An information processing apparatus for use in an electronic device, comprising: Means for carrying out the method according to any one of claims 18 to 35, An information processing device comprising:

44. An electronic device having one or more wireless antennas, a display device, and one or more input devices, while a remote locator object associated with a user other than the user of the electronic device is in the vicinity of the electronic device; pursuant to determining that the remote locator object satisfies a tracking criterion, automatically presenting, without user input, a tracking alert indicating that the remote locator object not associated with the user satisfies the tracking criterion; Including, method.

45. The tracking criteria are: a requirement that the location associated with the remote locator object be within a predetermined threshold distance of a location associated with the user; a requirement that the location associated with the remote locator object remains within a threshold distance of a location associated with the user for at least a threshold time; a requirement that the remote locator object is not associated with the user; and 45. The method of claim 44, including one or more of the following requirements: the remote locator object is reporting a location to another user.

46. 46. The method of claim 44 or 45, wherein the tracking alert includes a selectable option that includes information that allows the user to visually identify the remote locator object.

47. 47. The method of any one of claims 44 to 46, wherein the tracking alert includes a selectable option to ignore future alerts that the remote locator object meets the tracking criteria.

48. detecting a sequence of one or more inputs including a selection of the selectable option to ignore future alerts that the remote locator object meets the tracking criteria; responsive to detecting the sequence of one or more inputs including selection of the selectable option to ignore future alerts that the remote locator object meets the tracking criteria, ceasing to display future alerts that the remote locator object meets the tracking criteria for a predetermined time threshold; 48. The method of claim 47, further comprising:

49. 49. The method of claim 48, further comprising, in response to detecting the sequence of one or more inputs including selection of the selectable option to ignore future warnings that the remote locator object meets the tracking criteria, adding the remote locator object to a set of physical objects available for viewing in a location tracking status user interface on the display device.

50. detecting a sequence of one or more inputs including a selection of the selectable option to ignore future alerts that the remote locator object meets the tracking criteria; in response to detecting the sequence of one or more inputs including selection of the selectable option to ignore future warnings that the remote locator object meets the tracking criteria, canceling the display of future warnings that the remote locator object meets the tracking criteria; 50. The method of any one of claims 47 to 49, further comprising:

51. detecting a sequence of one or more inputs including a selection of the selectable option to ignore future alerts that the remote locator object meets the tracking criteria; In response to detecting the sequence of one or more inputs including a selection of the selectable option to ignore future warnings that the remote locator object meets the tracking criteria, prompting the user to confirm the input to ignore future warnings that the remote locator object meets the tracking criteria by performing a default action involving both the remote locator object and the device; 51. The method of claim 47 or 50, further comprising:

52. 52. The method of claim 51, wherein the predetermined action includes bringing the remote locator object within a predetermined distance of the electronic device.

53. Detecting a sequence of one or more inputs including a selection of a selectable option that displays additional information about the remote locator object that meets the tracking criteria; displaying an option to disable the remote locator object in response to detecting the sequence of one or more inputs including selection of the selectable option that displays additional information about the remote locator object that meets the tracking criteria; and 53. The method of any one of claims 47 to 52, further comprising:

54. detecting a selection of the option to invalidate the remote locator object; in response to detecting a selection of the option to disable the remote locator object, displaying instructions that, when followed, prevent the remote locator object from reporting a location of the remote locator object; 54. The method of claim 53, further comprising:

55. 55. The method of any one of claims 44 to 54, further comprising: in response to obtaining information indicating that an amount of separation between a location associated with the user and a location associated with the remote locator object has increased beyond a first separation threshold, generating, at the electronic device, a separation alert indicating that the remote locator object has become separated from the user, in accordance with a determination that the user has requested to ignore future alerts that the remote locator object satisfies the tracking criteria.

56. 56. The method of any one of claims 44 to 55, further comprising, in accordance with a determination that the remote locator object has been marked as lost, the tracking alert including an indication that the remote locator object has been marked as lost.

57. detecting a sequence of one or more inputs, including an input directed to the tracking alert, corresponding to a request to display a message from the owner of the remote locator object; displaying a message from the owner of the remote locator object in response to detecting the one or more inputs, including the input directed to the tracking alert; 57. The method of claim 56, comprising:

58. 58. The method of claim 57, including displaying, while displaying the message from the owner, one or more selectable options that, when selected, initiate a process of communicating with the owner.

59. displaying an option to disable the remote locator object while displaying the message from the owner; and in response to detecting a selection of the option to disable the remote locator object, displaying instructions that, when followed, prevent the remote locator object from reporting a location of the remote locator object; 59. The method of claim 58, further comprising:

60. causing the remote locator object to emit an audible sound in response to the remote locator object receiving user input corresponding to a request to play a sound; 60. The method of any one of claims 44 to 59, further comprising:

61. the remote locator object is marked as lost, and the method comprises: and, pursuant to determining that the remote locator object is within a predetermined distance of the electronic device, displaying via the display device an indication that the remote locator object has been marked as lost, a message from the owner of the remote locator object, and one or more selectable options that, when selected, initiate a process of communicating with the owner of the remote locator object.

61. The method of any one of claims 44 to 60.

62. one or more processors; Memory and One or more programs; wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: while a remote locator object associated with a user other than the user of the electronic device is in the vicinity of the electronic device; pursuant to determining that the remote locator object satisfies a tracking criterion, automatically presenting, without user input, a tracking alert indicating that the remote locator object not associated with the user satisfies the tracking criterion. An electronic device containing instructions.

63. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to: while a remote locator object associated with a user other than the user of the electronic device is in the vicinity of the electronic device; pursuant to determining that the remote locator object satisfies a tracking criterion, automatically presenting, without user input, a tracking alert indicating that the remote locator object not associated with the user satisfies the tracking criterion; A non-transitory computer-readable storage medium for causing a method to be performed, comprising:

64. 1. An electronic device comprising: one or more processors; Memory and means for, while a remote locator object associated with a user other than the user of the electronic device is in the vicinity of the electronic device, means for automatically presenting, without user input, a tracking alert indicating that the remote locator object not associated with the user satisfies the tracking criteria in accordance with a determination that the remote locator object satisfies the tracking criteria; An electronic device comprising:

65. 1. An information processing apparatus for use in an electronic device, comprising: means for, while a remote locator object associated with a user other than the user of the electronic device is in the vicinity of the electronic device, means for automatically presenting, without user input, a tracking alert indicating that the remote locator object not associated with the user satisfies the tracking criteria in accordance with a determination that the remote locator object satisfies the tracking criteria; An information processing device comprising:

66. one or more processors; Memory and One or more programs; 62. An electronic device comprising: one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 44 to 61.

67. 62. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method of any one of claims 44 to 61.

68. one or more processors; Memory and means for carrying out the method of any one of claims 44 to 61; An electronic device comprising:

69. 1. An information processing apparatus for use in an electronic device, comprising: means for carrying out the method of any one of claims 44 to 61; An information processing device comprising:

70. In an electronic device having a display device and one or more input devices, displaying, while in a remote locator object find mode, via the display device, a first visual indicator indicating a direction in which the remote locator object is located relative to the electronic device; detecting a change in orientation of the electronic device while displaying the first visual indicator; In response to detecting the change in orientation of the electronic device, modifying an appearance of the first visual indicator to indicate an orientation in which the remote locator object is located relative to the electronic device; A method comprising:

71. changing the appearance of the first visual indicator to indicate the direction in which the remote locator object is located relative to the electronic device; rotating the first visual indicator as the device is rotated; changing a color of at least a portion of the user interface in accordance with determining that the first visual indicator has a predetermined alignment with a first portion of the device; 71. The method of claim 70, comprising:

72. 72. The method of claim 70 or 71, further comprising generating a sequence of tactile outputs when the orientation of the device changes relative to the location associated with the remote locator object.

73. 73. The method of claim 72, further comprising: generating a tactile output that is different from the tactile output in the sequence of tactile outputs generated when the orientation of the device changes relative to the location associated with the remote locator object in accordance with a determination that the orientation of the device relative to the location associated with the remote locator object satisfies a first orientation criterion.

74. prior to entering the remote locator object discovery mode, displaying an information user interface for the remote locator object including information about the remote locator object along with selectable user interface objects for discovering the remote locator object; detecting a selection of the user interface object to locate the remote locator object while displaying the information user interface of the remote locator object; entering the remote locator object discovery mode in response to detecting a selection of the user interface object for discovering the remote locator object; 74. The method of any one of claims 70 to 73, further comprising:

75. 75. The method of any one of claims 70 to 74, wherein the first visual indicator is a simulated object that changes appearance as the orientation of the device changes such that the first visual indicator remains in a substantially fixed orientation relative to at least a portion of physical space.

76. receiving a request to enter an augmented reality discovery mode; In response to the request to enter the augmented reality discovery mode, displaying a representation of a field of view of one or more cameras of the device and displaying a virtual object at a location determined based on the location associated with the remote locator object; 76. The method of any one of claims 70 to 75, further comprising:

77. 77. The method of claim 76, wherein the request to enter the augmented reality discovery mode includes changing an orientation of the device from a first orientation to a second orientation.

78. 78. The method of claim 76 or 77, further comprising, in response to the request to enter the augmented reality discovery mode, displaying an animation of the first visual indicator flying towards the location associated with the remote locator object in the physical space.

79. 79. The method of any one of claims 76 to 78, further comprising generating a tactile output corresponding to entering the augmented reality mode.

80. 80. The method of any one of claims 70 to 79, wherein the remote locator object finder mode includes a selectable affordance for requesting the generation of a sound at the remote locator object.

81. 81. The method of any one of claims 70 to 80, wherein the remote locator object discovery mode includes a textual description of a direction from the location of the device to the location associated with the remote locator object.

82. 82. The method of any one of claims 70 to 81, wherein the remote locator object discovery mode includes a stationary element in a predetermined portion of the user interface and an element that changes size as a predetermined portion of the first visual indicator moves closer to and farther away from the stationary element.

83. when the device is oriented such that the predetermined portion of the first visual indicator has a predetermined orientation relative to the stationary element; Modifying the appearance of the stationary element; generating a tactile output corresponding to the change in appearance of the stationary element; 83. The method of claim 82, further comprising:

84. 84. The method of claim 83, wherein the visual indicator has the predetermined orientation when within a predetermined range of orientations.

85. 85. The method of claim 83 or 84, further comprising generating a sequence of discrete tactile outputs while the device is oriented so that the predetermined portion of the first visual indicator has a predetermined orientation relative to the stationary element, wherein spacing between the discrete tactile outputs varies as the distance between the device and the remote locator object changes.

86. 86. The method of any one of claims 70 to 85, further comprising replacing the display of the first visual indicator, which changes appearance to indicate the orientation in which the remote locator object is located relative to the electronic device, with a second visual indicator, which changes appearance based on the change in distance between the device and the remote locator object, regardless of the orientation in which the remote locator object is located relative to the electronic device, when the distance between the device and the remote locator object decreases below a predetermined distance threshold.

87. generating a sequence of discrete tactile outputs, the spacing between which varies based on changes in distance between the device and the remote locator object, in accordance with determining that the distance between the device and the remote locator object exceeds a predetermined threshold; ceasing to generate the sequence of discrete tactile outputs and generating a continuous tactile output in response to a determination that the distance between the device and the remote locator object is below the predetermined threshold; 87. The method of any one of claims 70 to 86, further comprising:

88. 88. The method of claim 87, wherein the continuous tactile output changes tactile output characteristics based on a change in distance between the device and the remote locator object.

89. While in the remote locator object discovery mode, in which the first visual indicator indicating the direction in which the remote locator object is located relative to the electronic device is displayed via the display device, detecting that the remote locator object is at a position within the environment of the electronic device that corresponds to a field of view of a camera of the electronic device; In response to detecting that the remote locator object is at the position in the environment of the electronic device corresponding to the field of view of the camera of the electronic device, displaying, via the display device, a camera user interface displaying content captured by the camera of the electronic device, and a first visual indication superimposed on the content captured by the camera at a position within the content corresponding to the position of the remote locator object within the field of view of the camera; 89. The method of any one of claims 70 to 88, further comprising:

90. 90. The method of claim 89, further comprising, in response to a distance between the electronic device and the remote locator object decreasing below a predetermined distance threshold, replacing display of the first visual indicator with a second visual indicator surrounding the location in the content that corresponds to the location of the remote locator object within the field of view of the camera.

91. one or more processors; Memory and One or more programs; wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: displaying, while in a remote locator object find mode, via a display device, a first visual indicator indicating an orientation in which the remote locator object is located relative to the electronic device; detecting a change in orientation of the electronic device while displaying the first visual indicator; and modifying an appearance of the first visual indicator to indicate an orientation of the remote locator object relative to the electronic device in response to detecting the change in orientation of the electronic device. An electronic device containing instructions.

92. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to: displaying, while in a remote locator object find mode, via a display device, a first visual indicator indicating a direction in which the remote locator object is located relative to the electronic device; detecting a change in orientation of the electronic device while displaying the first visual indicator; and in response to detecting the change in orientation of the electronic device, changing an appearance of the first visual indicator to indicate an orientation in which the remote locator object is located relative to the electronic device.

93. 1. An electronic device comprising: one or more processors; Memory and means for displaying, while in a remote locator object find mode, via a display device, a first visual indicator indicating an orientation in which the remote locator object is located relative to the electronic device; means for detecting a change in orientation of the electronic device while displaying the first visual indicator; means for modifying an appearance of the first visual indicator to indicate an orientation of the remote locator object relative to the electronic device in response to detecting the change in orientation of the electronic device; An electronic device comprising:

94. 1. An information processing apparatus for use in an electronic device, comprising: means for displaying, while in a remote locator object find mode, via a display device, a first visual indicator indicating an orientation in which the remote locator object is located relative to the electronic device; means for detecting a change in orientation of the electronic device while displaying the first visual indicator; means for modifying an appearance of the first visual indicator to indicate an orientation of the remote locator object relative to the electronic device in response to detecting the change in orientation of the electronic device; An information processing device comprising:

95. one or more processors; Memory and One or more programs; 91. An electronic device comprising: one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 70 to 90.

96. 91. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method of any one of claims 70 to 90.

97. one or more processors; Memory and means for carrying out the method of any one of claims 70 to 90; An electronic device comprising:

98. 1. An information processing apparatus for use in an electronic device, comprising: Means for carrying out the method of any one of claims 70 to 90; An information processing device comprising:

99. In an electronic device having a display device and one or more input devices, displaying on the display device an information user interface for the remote locator object including information about the remote locator object along with a selectable user interface object for initiating a remote locator object discovery mode for discovering the remote locator object; detecting a selection of the user interface object to locate the remote locator object while displaying the information user interface of the remote locator object; in response to detecting a selection of the user interface object to locate the remote locator object; displaying a first discovery mode including a map user interface having directions to the remote locator object according to determining that the device is farther than a first threshold distance from a location associated with the remote locator object; displaying a second discovery mode different from the first discovery mode and indicating the location of the remote locator object relative to the current location of the device in accordance with determining that the device is less than the first threshold distance from the location associated with the remote locator object; A method comprising:

100. 100. The method of claim 99, wherein the user interface of the second discovery mode includes a plurality of objects, one or more characteristics of the plurality of objects changing as the distance between the device and the remote locator object changes.

101. 101. The method of claim 100, wherein altering the characteristics of the plurality of objects as the distance between the device and the location associated with the remote locator object changes comprises one or more of: increasing the number of objects as the device approaches the location associated with the remote locator object; increasing the brightness of the objects as the device approaches the location associated with the remote locator object; changing the color of the objects as the device approaches the location associated with the remote locator object; and increasing the speed of movement of the objects as the device approaches the location associated with the remote locator object.

102. 102. The method of claim 100 or 101, wherein the plurality of user interface elements react to changes in the position and / or orientation of the device based on a rate of movement of the device, regardless of a distance between the device and the location associated with the remote locator object.

103. 103. The method of claim 102, wherein a majority of the plurality of user interface elements are displayed within a first set of locations on the user interface that are closer to the location associated with the remote locator object than a second set of locations on the user interface that are farther from the location associated with the remote locator object.

104. detecting a change in the location of the device while displaying the second discovery mode; in response to detecting the change in location of the device, switching from the second discovery mode to a third discovery mode different from the second discovery mode in accordance with a determination that the device is less than a second threshold distance from a location associated with the remote locator object; 104. The method of any one of claims 99 to 103, further comprising:

105. 105. The method of claim 104, wherein the second discovery mode includes a plurality of objects that roughly respond to changes in distance between the device and a location associated with the remote locator object without indicating a precise direction from the device to the remote locator object, and the third discovery mode includes a direction indicator that indicates a direction toward the remote locator object.

106. 106. The method of claim 105, wherein switching from the second discovery mode to the third discovery mode includes animating the plurality of objects merging to form the directional indicator.

107. detecting a change in the location of the device while displaying the third discovery mode; in response to detecting the change in location of the device, switching from the third discovery mode to the second discovery mode in accordance with a determination that the device is farther than the second threshold distance from a location associated with the remote locator object; Further comprising:

107. The method of any one of claims 104 to 106.

108. detecting a change in the location of the device while displaying the third discovery mode; in response to detecting the change in location of the device, switching from the third discovery mode to a fourth discovery mode different from the second discovery mode in accordance with a determination that the device is less than a third threshold distance from a location associated with the remote locator object; Further comprising:

108. The method of any one of claims 104 to 107.

109. 109. The method of claim 108, wherein the fourth discovery mode includes a graphical indicator that expands or contracts to indicate a change in distance between the device and a location associated with the remote locator object.

110. detecting, while in the fourth discovery mode, that the device is within a fourth threshold distance of the location associated with the remote locator object; responsive to detecting that the device is within the fourth threshold distance of the location associated with the remote locator object, replacing a display of a portion of the user interface with a representation of the remote locator object; 110. The method of claim 108 or 109, comprising:

111. the second discovery mode includes a first one or more non-directional visual indications of a distance between the device and a location associated with the remote locator object without a corresponding tactile output; 111. The method of any one of claims 108 to 110, wherein the fourth discovery mode includes a second one or more non-directional visual indications of distance between the device and a location associated with the remote locator object along with a corresponding tactile output.

112. the third discovery mode includes a corresponding discrete tactile output that changes based on a change in orientation of the device relative to the location associated with the remote locator object; 112. The method of any one of claims 108 to 111, wherein the fourth discovery mode includes a corresponding continuous tactile output that changes based on a change in distance between the device and a location associated with the remote locator object.

113. one or more processors; Memory and One or more programs; wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: displaying on a display device an information user interface for the remote locator object including information about the remote locator object along with a selectable user interface object for initiating a remote locator object discovery mode for discovering the remote locator object; detecting a selection of the user interface object to locate the remote locator object while displaying the information user interface of the remote locator object; in response to detecting a selection of the user interface object to locate the remote locator object; displaying a first discovery mode including a map user interface having directions to the remote locator object in accordance with determining that the device is farther than a first threshold distance from a location associated with the remote locator object; displaying a second discovery mode different from the first discovery mode and indicating the location of the remote locator object relative to the current location of the device in response to determining that the device is less than the first threshold distance from the location associated with the remote locator object. An electronic device containing instructions.

114. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to: displaying on a display device an information user interface for the remote locator object including information about the remote locator object along with a selectable user interface object for initiating a remote locator object discovery mode for discovering the remote locator object; detecting a selection of the user interface object to locate the remote locator object while displaying the information user interface of the remote locator object; in response to detecting a selection of the user interface object to locate the remote locator object; displaying a first discovery mode including a map user interface having directions to the remote locator object according to determining that the device is farther than a first threshold distance from a location associated with the remote locator object; displaying a second discovery mode different from the first discovery mode and indicating the location of the remote locator object relative to the current location of the device in accordance with determining that the device is less than the first threshold distance from the location associated with the remote locator object; performing a method including A non-transitory computer-readable storage medium.

115. one or more processors; Memory and means for displaying, on a display device, an information user interface for the remote locator object including information about the remote locator object along with a selectable user interface object for initiating a remote locator object discovery mode for discovering the remote locator object; means for detecting selection of the user interface object to locate the remote locator object while displaying the information user interface of the remote locator object; in response to detecting a selection of the user interface object to locate the remote locator object; displaying a first discovery mode including a map user interface having directions to the remote locator object in accordance with determining that the device is farther than a first threshold distance from a location associated with the remote locator object; displaying a second discovery mode different from the first discovery mode and indicating the location of the remote locator object relative to the current location of the device in response to determining that the device is less than the first threshold distance from the location associated with the remote locator object. Means and An electronic device comprising:

116. 1. An information processing apparatus for use in an electronic device, comprising: means for displaying, on a display device, an information user interface for the remote locator object including information about the remote locator object along with a selectable user interface object for initiating a remote locator object discovery mode for discovering the remote locator object; means for detecting selection of the user interface object to locate the remote locator object while displaying the information user interface of the remote locator object; in response to detecting a selection of the user interface object to locate the remote locator object; displaying a first discovery mode including a map user interface having directions to the remote locator object in accordance with determining that the device is farther than a first threshold distance from a location associated with the remote locator object; displaying a second discovery mode different from the first discovery mode and indicating the location of the remote locator object relative to the current location of the device in response to determining that the device is less than the first threshold distance from the location associated with the remote locator object. Means and Equipped with Information processing device.

117. one or more processors; Memory and One or more programs; 130. An electronic device comprising: one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 99 to 112.

118. 113. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method of any one of claims 99 to 112.

119. one or more processors; Memory and means for carrying out the method of any one of claims 99 to 112; An electronic device comprising:

120. 1. An information processing apparatus for use in an electronic device, comprising:

113. An information processing device comprising means for carrying out the method of any one of claims 99 to 112.

121. one or more processors; Memory and means for carrying out the method according to any one of claims 1 to 11; An electronic device comprising:

122. 1. An information processing apparatus for use in an electronic device, comprising: An information processing device comprising means for carrying out the method according to any one of claims 1 to 11.

Images