User interface for sharing location of searchable item with entity

Abstract

The present disclosure generally relates to a user interface for sharing a location of a searchable item with an entity. Some embodiments described in the present disclosure relate to one or more electronic devices that provide location information for sharing a remote locator object with an entity for a duration associated with a time-limited event. Some embodiments described in the present disclosure relate to one or more electronic devices that provide for reporting an item associated with a remote locator object to an entity as lost for assisting in retrieving the item. Some embodiments described in the present disclosure relate to one or more electronic devices that facilitate a process for providing an entity with access to one or more features associated with a remote locator object associated with an item for assisting in retrieving the item.

Description

[0001] This application is a divisional application of the application with international application number PCT / US2024 / 015620, international application date of February 13, 2024, entry into the Chinese national phase date of September 26, 2025, national application number 202480022692.1, and invention title "User Interface for Sharing the Location of Findable Items with Entities". Cross-reference to related applications

[0002] This application claims the benefits of U.S. Provisional Application No. 63 / 484,737, filed February 13, 2023, and U.S. Provisional Application No. 63 / 552,541, filed February 12, 2024, the contents of which are incorporated herein by reference in their entirety for all purposes. Technical Field

[0003] This disclosure relates in its entirety to user interfaces that enable users to share and / or manage the location of locatable items on electronic devices. Background Technology

[0004] In recent years, user interaction with electronic devices has increased significantly. These devices can include computers, tablets, televisions, multimedia devices, mobile devices, and so on.

[0005] In some situations, users may want to use such devices to track items. Enhancing user interaction with the device improves the user experience and reduces user interaction time, which is especially important when the input device is battery powered. Summary of the Invention

[0006] Some embodiments described in this disclosure involve one or more electronic devices that provide the ability to share location information of a remote locator object with an entity for a duration associated with a time-limited event. Some embodiments described in this disclosure involve one or more electronic devices that provide the ability to report an item associated with a remote locator object as lost to an entity to assist in the retrieval of the item. Some embodiments described in this disclosure involve one or more electronic devices that facilitate a process for providing an entity with access to one or more features associated with the remote locator object linked to the item to assist in the retrieval of the item.

[0007] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0008] The accompanying drawings and detailed descriptions provide a full description of the embodiments. It should be understood that the above-described invention does not limit the scope of this disclosure in any way. Attached Figure Description

[0009] To better understand the various described embodiments, reference should be made to the following detailed description in conjunction with the accompanying drawings, in which similar reference numerals indicate corresponding parts throughout the drawings.

[0010] FIG. 1A This is a block diagram illustrating a portable multi-functional device with a touch-sensitive display according to some implementation schemes.

[0011] FIG. 1B This is a block diagram illustrating exemplary components for event handling according to some implementation schemes.

[0012] FIG. 2 Examples of portable multi-functional devices with touchscreens according to some implementation schemes are shown.

[0013] FIG. 3 This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to some implementation schemes.

[0014] FIG. 4A An exemplary user interface for applying menus on a portable multifunction device according to some implementations is shown.

[0015] FIG. 4B An exemplary user interface of a multifunctional device having a touch-sensitive surface separate from the display is illustrated according to some embodiments.

[0016] FIG. 5A Examples of personal electronic devices according to some implementation schemes are shown.

[0017] FIG. 5B This is a block diagram illustrating a personal electronic device according to some implementation schemes.

[0018] FIG. 5C-D Exemplary components of a personal electronic device having a touch-sensitive display and an intensity sensor according to some embodiments are illustrated.

[0019] FIG. 5E-H Exemplary components and user interfaces of a personal electronic device according to some implementation schemes are illustrated.

[0020] FIG. 5I-NIt provides a set of sample haptic output patterns that can be used individually or in combination, as is or through one or more transformations (e.g., modulation, amplification, truncation, etc.) to form appropriate haptic feedback in various scenarios for various purposes (such as those described above and those described in relation to the user interfaces and methods discussed herein).

[0021] FIG. 6A-I Exemplary ways in which an electronic device according to some embodiments of the present disclosure shares location information of a remote locator object with an entity for a duration associated with a time-limited event are illustrated.

[0022] FIG. 7A-E This is a flowchart illustrating a method for sharing location information of a remote locator object with an entity over a duration associated with a time-limited event, according to some embodiments of this disclosure.

[0023] FIG. 8A-G Exemplary ways in which electronic devices according to some embodiments of the present disclosure facilitate reporting items associated with remote locator objects as lost to an entity for the purpose of assisting in the retrieval of the items are illustrated.

[0024] FIG. 9A-D This is a flowchart illustrating a method, according to some embodiments of the present disclosure, for facilitating the reporting of items associated with a remote locator object as lost to an entity to assist in the retrieval of the items.

[0025] FIG. 10A-CCC Exemplary ways in which an electronic device according to some embodiments of the present disclosure facilitates providing an entity with access to one or more features associated with a remote locator object are illustrated.

[0026] FIG. 11 This is a flowchart illustrating a method for facilitating the granting of access to one or more features associated with a remote locator object to an entity, according to some embodiments of this disclosure. Detailed Implementation

[0027] The following description illustrates exemplary methods, parameters, etc. However, it should be understood that such description is not intended to limit the scope of this disclosure, but is provided as a description of exemplary embodiments.

[0028] Some embodiments described in this disclosure involve one or more electronic devices that provide the ability to share location information of a remote locator object with an entity for a duration associated with a time-limited event. Some embodiments described in this disclosure involve one or more electronic devices that provide the ability to report an item associated with a remote locator object as lost to an entity to assist in the retrieval of the item. Some embodiments described in this disclosure involve one or more electronic devices that facilitate a process for providing an entity with access to one or more features associated with the remote locator object linked to the item to assist in the retrieval of the item.

[0029] Electronic devices that need to track the location of remote locator objects and share and manage the location of remote locator objects relative to time-limited events. Such technologies can reduce the cognitive burden on users of such devices and / or users who wish to control their use of such devices. Furthermore, such technologies can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0030] Although the following description uses the terms "first," "second," etc., to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch may be named a second touch and similarly, a second touch may be named a first touch, without departing from the scope of the various described embodiments. Both the first touch and the second touch are touches, but they are not the same touch.

[0031] The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and in the appended claims, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and covers any and all possible combinations of one or more of the associated listed items. It will also be understood that the terms “comprising” and / or “including” as used in this specification specify the presence of the 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.

[0032] Depending on the context, the term "if" may optionally be interpreted as meaning "when," "in," or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrases "if it is determined..." or "if [the stated condition or event] is detected" may optionally be interpreted as meaning "in response to determination..." or "in response to detection of [the stated condition or event]."

[0033] This document describes implementations of electronic devices, user interfaces for such devices, and associated processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functionalities such as PDA and / or music player functionality. Exemplary implementations of portable multi-functional devices include, but are not limited to, the iPhone from Apple Inc. (Cupertino, California). ® Devices, iPod Touch ® Devices and / or iPads ® Device. Alternatively, other portable electronic devices may be used, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads).

[0034] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device may optionally include one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick.

[0035] The device typically supports a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, game applications, telephone applications, video conferencing applications, email applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0036] Various applications running on this device may optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and the corresponding information displayed on the device may optionally be adjusted and / or varied for different applications, and / or within the respective applications. In this way, the common physical architecture of the device (such as the touch-sensitive surface) may optionally utilize a user interface that is intuitive and clear to the user to support various applications.

[0037] Now let’s turn our attention to implementation schemes for portable devices with touch-sensitive displays. FIG. 1A This is a block diagram illustrating a portable multi-functional device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a “touchscreen” for convenience, and is sometimes referred to as or called a “touch-sensitive display system.” Device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100). Device 100 may optionally include one or more haptic output generators 167 for generating haptic output on device 100 (e.g., generating haptic output on a touch-sensitive surface such as the touch-sensitive display system 112 of device 100 or the touchpad 355 of device 300). These components may optionally communicate via one or more communication buses or signal lines 103.

[0038] As used in this specification and claims, the term "intensity" of contact on a tactile surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a tactile surface, or to a substitute (alternative) for the force or pressure of a contact on a tactile surface. The intensity of contact has a range of values ​​that includes at least four different values ​​and more typically hundreds of different values ​​(e.g., at least 256). The intensity of contact may optionally be determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the tactile surface may optionally be used to measure the force at different points on the tactile surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated contact force. Similarly, the pressure-sensitive tip of a stylus may optionally be used to determine the pressure of the stylus on the tactile surface. Alternatively, the size and / or change of the contact area detected on the touch-sensitive surface, the capacitance and / or change of the touch-sensitive surface adjacent to the contact, and / or the resistance and / or change of the touch-sensitive surface adjacent to the contact may be used as substitutes for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement result). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of user input allows users to access additional device functionality that would otherwise be inaccessible to the user on a smaller device with limited physical space, which is used (e.g., on a touch-sensitive display) to display an indication and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0039] As used in this specification and claims, the term "haptic output" refers to a physical displacement of the device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device, which is detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with the touch-sensitive surface, which has been physically pressed (e.g., displaced) by the user's movement, does not move. As another example, even when the smoothness of the tactile surface remains unchanged, the movement of the tactile surface can optionally be interpreted or sensed by the user as the "roughness" of the tactile surface. While such interpretations of touch by users will be limited by the individualized sensory perceptions of the user, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a specific sensory perception of the user (e.g., "release click", "press click", "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or its components that will generate the sensory perception described by a typical (or common) user.

[0040] It should be understood that device 100 is merely an example of a portable multifunctional device, and device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of these components. FIG. 1A The various components shown are implemented in hardware, software, or a combination of both, including one or more signal processing and / or application-specific integrated circuits.

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

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

[0043] RF (Radio Frequency) circuit 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 108 converts electrical signals into electromagnetic signals / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuitry for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, subscriber identity module (SIM) cards, memory, etc. RF circuit 108 optionally communicates wirelessly with networks (such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular phone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs))) and other devices. RF circuit 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via short-range communication radio components. Wireless communication may optionally use any of a variety of communication standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Evolution, Pure Data (EV-DO), HSPA, HSPA+, Dual-Unit HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), and Wi-Fi (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Messaging Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence with Extended Utility (SIMPLE), Instant Messaging and Presence Service (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol that has not been developed as of the date of this document submission.

[0044] Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between the user and device 100. Audio circuitry 110 receives audio data from peripheral interface 118, converts the audio data into electrical signals, and sends the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves that are audible to humans. Audio circuitry 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuitry 110 converts the electrical signals into audio data and sends the audio data to peripheral interface 118 for processing. Audio data may optionally be retrieved by peripheral interface 118 from and / or sent to memory 102 and / or RF circuitry 108. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., ...). FIG. 2 (212 in the text). The headset jack provides an interface between the audio circuitry 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset with both outputs (e.g., a single-ear or dual-ear headset) and inputs (e.g., a microphone).

[0045] I / O subsystem 106 couples input / output peripherals (such as touchscreen 112 and other input control devices 116) on device 100 to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from / transmit electrical signals to the other input control device 116. Other input control devices 116 optionally include physical buttons (e.g., push-buttons, rocker buttons, etc.), dial pads, slide switches, joysticks, click dials, etc. In some alternative embodiments, input controller 160 may optionally be coupled to (or not coupled to) any of the following: keyboard, infrared port, USB port, and pointing device such as mouse. One or more buttons (e.g., FIG. 2 Optionally, 208 may include increase / decrease buttons for volume control of speaker 111 and / or microphone 113. These one or more buttons may optionally include a push-button (e.g., FIG. 2 (206 in the middle).

[0046] A quick press of the push button may optionally disengage the touchscreen 112 from its lock or optionally initiate a process of unlocking the device using gestures on the touchscreen, as described in U.S. Patent Application 11 / 322,549 (i.e., U.S. Patent No. 7,657,849), filed December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," the entire contents of which are incorporated herein by reference. A long press of the push button (e.g., 206) may optionally power on or off the device 100. The functionality of one or more of these buttons may optionally be user-customizable. The touchscreen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0047] The touch-sensitive display 112 provides input and output interfaces between the device and the user. The display controller 156 receives electrical signals from and / or transmits electrical signals to the touchscreen 112. The touchscreen 112 displays visual output to the user. Visual output may optionally include graphics, text, icons, video, and any combination thereof (collectively, "graphics"). In some embodiments, some or all of the visual output may optionally correspond to user interface objects.

[0048] Touchscreen 112 has a touch-sensitive surface, sensor, or sensor array that accepts input from a user based on tactile and / or haptic contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction set in memory 102) detect contact on touchscreen 112 (and any movement or interruption of that contact) and translate the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the contact point between touchscreen 112 and the user corresponds to the user's finger.

[0049] Touchscreen 112 may optionally employ LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, but other display technologies may be used in other embodiments. Touchscreen 112 and display controller 156 may optionally use any of a variety of touch sensing technologies now known or to be developed hereafter, along with other proximity sensor arrays or other elements for determining one or more points of contact with touchscreen 112, to detect contact and any movement or interruption thereto. These various touch sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology, such as that used in the iPhone from Apple Inc. (Cupertino, California), is used. ®and iPod Touch ® The technology used.

[0050] In some embodiments of the touchscreen 112, the touch-sensitive display may optionally resemble a multi-touch-sensitive touchpad described in the following U.S. patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman et al.) and / or U.S. Patent Publication 2002 / 0015024A1, each of which is incorporated herein by reference in its entirety. However, the touchscreen 112 displays visual output from the device 100, while the touch-sensitive touchpad does not provide visual output.

[0051] The touch-sensitive display in some embodiments of the touchscreen 112 is described in the following applications: (1) U.S. Patent Application No. 11 / 381,313, filed May 2, 2006, “Multipoint Touch Surface Controller”; (2) U.S. Patent Application No. 10 / 840,862, filed May 6, 2004, “Multipoint Touchscreen”; (3) U.S. Patent Application No. 10 / 903,964, filed July 30, 2004, “Gestures For Touch Sensitive Input Devices”; (4) U.S. Patent Application No. 11 / 048,264, filed January 31, 2005, “Gestures For Touch Sensitive Input Devices”; and (5) U.S. Patent Application No. 11 / 038,590, filed January 18, 2005, “Mode-Based Graphical User Interfaces For Touch Sensitive Input”. (6) U.S. Patent Application No. 11 / 228,758, filed September 16, 2005, “Virtual Input Device Placement On A Touch Screen User Interface”; (7) U.S. Patent Application No. 11 / 228,700, filed September 16, 2005, “Operation Of A Computer With A Touch Screen Interface”; (8) U.S. Patent Application No. 11 / 228,737, filed September 16, 2005, “Activating Virtual Keys Of ATouch-Screen Virtual Keyboard”; and (9) U.S. Patent Application No. 11 / 367,749, filed March 3, 2006, “Multi-Functional Hand-Held Device”. The full text of all these applications is incorporated herein by reference.

[0052] The touchscreen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. Users may optionally use any suitable object or accessory, such as a stylus, finger, etc., to interact with the touchscreen 112. In some embodiments, the user interface is designed to operate primarily through finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positioning or commands for performing the user-desired actions.

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

[0054] The device 100 also includes a power system 162 for supplying power to various components. The power system 162 may optionally include a power management system, one or more power sources (e.g., a battery, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0055] The device 100 may optionally also include one or more optical sensors 164. FIG. 1AAn optical sensor 164 is shown coupled to an optical sensor controller 158 in the I / O subsystem 106. The optical sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with an imaging module 143 (also referred to as a camera module), the optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, facing away from a touchscreen display 112 on the front of the device, allowing the touchscreen display to be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing images of the user to be optionally acquired for video conferencing while the user views other video conferencing participants on the touchscreen display. In some embodiments, the positioning of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensors within the device housing), allowing a single optical sensor 164 to be used in conjunction with the touchscreen display for both video conferencing and still image and / or video image acquisition.

[0056] The device 100 may optionally also include one or more contact strength sensors 165. FIG. 1A A contact strength sensor is shown coupled to a strength sensor controller 159 in I / O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact strength sensor is arranged juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact strength sensor is located on the rear of device 100, opposite to the touchscreen display 112 located on the front of device 100.

[0057] The device 100 may optionally also include one or more proximity sensors 166. FIG. 1AA proximity sensor 166 coupled to a peripheral device interface 118 is shown. Alternatively, the proximity sensor 166 may be coupled to an input controller 160 in an I / O subsystem 106. The proximity sensor 166 may be configured as described in the following U.S. patent applications: 11 / 241,839, entitled "Proximity Detector In Handheld Device"; 11 / 240,788, entitled "Proximity Detector In Handheld Device"; 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", the entire contents of which are incorporated herein by reference. In some implementations, when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call), the proximity sensor is turned off and the touchscreen 112 is disabled.

[0058] The device 100 may optionally also include one or more tactile output generators 167. FIG. 1A A haptic output generator coupled to a haptic feedback controller 161 in I / O subsystem 106 is shown. The haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting electrical signals into haptic outputs on the device). A contact intensity sensor 165 receives haptic feedback generation instructions from a haptic feedback module 133 and generates a haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., haptic display system 112) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 100) or laterally (e.g., backward and forward in the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is located on the rear of the device 100, opposite to the touch screen display 112 located on the front of the device 100.

[0059] The device 100 may optionally also include one or more accelerometers 168. FIG. 1A An accelerometer 168 coupled to a peripheral device interface 118 is shown. Alternatively, the accelerometer 168 may be coupled to an input controller 160 in an I / O subsystem 106. The accelerometer 168 may be configured as described in the following U.S. Patent Publications: 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and 20060017692, entitled "Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer," both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed on a touchscreen display in portrait or landscape view based on analysis of data received from one or more accelerometers. Device 100 may optionally include, in addition to the accelerometer 168, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for acquiring information about the position and orientation (e.g., portrait or landscape) of device 100.

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

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

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

[0063] The contact / motion module 130 optionally detects contact with the touchscreen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining the contact intensity (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is movement of the contact and tracking movement on 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 lift event or a contact break). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations can optionally be applied to single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., "multi-touch" / multiple-finger contact). In some implementations, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

[0064] In some implementations, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by the user (e.g., determining whether the user has “clicked” an icon). In some implementations, at least a subset of the intensity thresholds is determined based on software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a specific physical actuator and can be adjusted without changing the physical hardware of device 100). For example, the mouse “click” threshold of a touchpad or touchscreen can be set to any threshold in a wide range of predefined thresholds without changing the touchpad or touchscreen display hardware. Additionally, in some specific implementations, the user of the device is provided with software settings for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting the individual intensity thresholds and / or by adjusting multiple intensity thresholds at once using system-level clicks on the “intensity” parameter).

[0065] The touch / motion module 130 optionally detects gesture input performed by the user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). Therefore, gestures can be detected optionally by detecting specific contact patterns. For example, detecting a finger tap gesture includes: detecting a finger press event, and then detecting a finger lift-off (lift-away) event at the same (or substantially the same) location as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on a touch-sensitive surface includes: detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift-off (lift-away) event.

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

[0067] In some implementations, the graphics module 132 stores data representing the graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes from applications, etc., to specify the graphics to be displayed, and also receives coordinate data and other graphic attribute data if necessary, and then generates screen image data to output to the display controller 156.

[0068] The haptic feedback module 133 includes various software components for generating instructions which are used by the haptic output generator 167 to generate haptic output at one or more locations on the device 100 in response to user interaction with the device 100.

[0069] Optionally, the text input module 134, which is a component of the graphics module 132, provides a soft keyboard for entering text in various applications, such as contacts 137, email 140, IM 141, browser 147, and any other application that requires text input.

[0070] GPS module 135 determines the location of the device and provides that information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as image / video metadata; and to applications that provide location-based services, such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0071] Application 136 may optionally include the following modules (or instruction sets) or subsets or supersets thereof: • Contacts module 137 (sometimes called address book or contact list); • Telephone module 138; • Video conferencing module 139; • Email client module 140; • Instant Messaging (IM) module 141; • Fitness support module 142; • Camera module 143 for still images and / or video images; • Image management module 144; • Video player module; • Music player module; • Browser module 147; • Calendar module 148; • Widget module 149, which may optionally include one or more of the following: weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5 and other widgets acquired by the user, as well as user-created widget 149-6; • Widget creator module 150 for creating user-created widgets 149-6; • Search module 151; • Video and music player module 152, which combines a video player module and a music player module; •Notepad module 153; • Map module 154; and / or • Online video module 155.

[0072] Examples of other applications 136 that may be optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, Java-enabled applications, encryption, digital rights management, speech recognition, and speech duplication.

[0073] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (e.g., in application internal state 192 of the contact module 137 stored in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140, or IM 141; and so on.

[0074] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 137, modify input telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is completed. As described above, wireless communication may optionally use any of a variety of communication standards, protocols, and technologies.

[0075] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and / or terminate video conferences between the user and one or more other participants based on user instructions.

[0076] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user commands. Combined with image management module 144, email client module 140 makes it very easy to create and send emails containing still images or video images captured by camera module 143.

[0077] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for performing the following operations: entering a character sequence corresponding to an instant message, modifying previously entered characters, sending a corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving an instant message, and viewing received instant messages. In some embodiments, the sent and / or received instant messages may optionally include graphics, photographs, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Services (EMS). As used herein, "instant message" means both telephone-based messages (e.g., messages delivered using SMS or MMS) and internet-based messages (e.g., messages delivered using XMPP, SIMPLE, or IMPS).

[0078] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, fitness support module 142 includes executable instructions for performing the following operations: creating fitness activities (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (exercise equipment); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing music for fitness activities; and displaying, storing, and transmitting fitness data.

[0079] In conjunction with the touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions for: capturing still images or videos (including video streams) and storing them in memory 102, modifying the characteristics of still images or videos, and / or deleting still images or videos from memory 102.

[0080] Incorporating the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 includes executable instructions for performing operations such as arranging, modifying (e.g., editing) or otherwise manipulating, marking, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

[0081] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for performing the following operations: browsing the Internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as links to attachments and other files on web pages.

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

[0083] 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, widget module 149 may be a micro-application (e.g., weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or a user-created micro-application (e.g., user-created widget 149-6). In some embodiments, the widget includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the widget includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! widgets).

[0084] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget creator module 150 can optionally be used by the user to create widgets (e.g., turning a user-specified section of a webpage into a widget).

[0085] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the search module 151 includes executable instructions for performing the following operations: searching the memory 102 for text, music, sound, images, videos, and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) according to user instructions.

[0086] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions allowing users to download and play back 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 back video (e.g., on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

[0087] Combining the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the notepad module 153 includes executable instructions for creating and managing notes, to-do items, etc., according to user instructions.

[0088] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may optionally be used to receive, display, modify, and store maps and map-related data (e.g., driving directions, data related to shops and other points of interest at or near a specific location, and other location-based data) according to user instructions.

[0089] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes instructions for performing the following operations: allowing users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos. Additional descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

[0090] Each of the modules and applications described above corresponds to an executable set of instructions for performing one or more functions described above and the methods described in this patent application (e.g., computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, processes, or modules; therefore, various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. For example, a video player module may optionally be combined with a music player module into a single module (e.g., FIG. 1A (e.g., video and music player module 152). In some embodiments, memory 102 may optionally store a subset of the aforementioned modules and data structures. Additionally, memory 102 may optionally store additional modules and data structures not described above.

[0091] In some implementations, device 100 is a device on which the operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for operating device 100, the number of physical input control devices (such as push-buttons and dial pads) on device 100 can be optionally reduced.

[0092] A predefined set of functions, uniquely performed via a touchscreen and / or touchpad, may optionally include navigation between user interfaces. In some implementations, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to the main menu, main desktop menu, or root menu. In such implementations, a "menu button" is implemented using the touchpad. In some other implementations, the menu button is a physical push-button or other physical input control device, rather than a touchpad.

[0093] FIG. 1B This is a block diagram illustrating exemplary components for event handling according to some embodiments. In some embodiments, memory 102 ( FIG. 1A ) or memory 370 ( FIG. 3 This includes an event classifier 170 (e.g., in operating system 126) and a corresponding application 136-1 (e.g., any of the aforementioned applications 137 to 151, 155, 380 to 390).

[0094] Event classifier 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which the event information should be delivered. Event classifier 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates one or more current application views 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 classifier 170 to determine which application(s) is currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information should be delivered.

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

[0096] Event monitor 171 receives event information from peripheral interface 118. The event information includes information about sub-events, such as a user touch on touch-sensitive display 112 as part of a multi-touch gesture. Peripheral interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (via audio circuitry 110). The information received by peripheral interface 118 from I / O subsystem 106 includes information from touch-sensitive display 112 or touch-sensitive surfaces.

[0097] In some implementations, event monitor 171 sends requests to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 sends event information. In other implementations, peripheral device interface 118 sends event information only when a significant event occurs (e.g., receiving input above a predetermined noise threshold and / or receiving input for a predetermined duration).

[0098] In some implementations, the event classifier 170 also includes a hit view determination module 172 and / or an activity event recognizer determination module 173.

[0099] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides a software process for determining where a sub-event has occurred within one or more views. A view consists of controls and other elements that the user can see on the display.

[0100] Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the corresponding application) in which a touch is detected optionally corresponds to a procedural level within the application's procedural or view hierarchy. For example, the lowest-level view in which a touch is detected may optionally be called the hit view, and the set of events identified as correct input is optionally determined, at least in part, based on the hit view of the initial touch that initiates the touch-based gesture.

[0101] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchical structure, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchical structure from which the sub-events should be processed. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events forming an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source to which it was identified as the hit view.

[0102] The activity event recognizer determination module 173 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 173 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, higher views in the hierarchy will still remain actively participating views.

[0103] Event assigner module 174 assigns event information to event identifiers (e.g., event identifier 180). In embodiments that include active event identifier determination module 173, event assigner module 174 delivers event information to the event identifier determined by active event identifier determination module 173. In some embodiments, event assigner module 174 stores event information in an event queue, which is retrieved by the corresponding event receiver 182.

[0104] In some implementations, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In yet another implementation, event classifier 170 is a separate module or part of another module (such as contact / motion module 130) stored in memory 102.

[0105] In some implementations, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes a plurality of event recognizers 180. In other implementations, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some implementations, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handlers 190 may optionally utilize or invoke the data updater 176, the object updater 177, or the GUI updater 178 to update the application's internal state 192. Alternatively, one or more application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

[0106] The corresponding event identifier 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies the event based on the event information. The event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event identifier 180 also includes at least one subset of metadata 183 and event delivery instructions 188 (which may optionally include sub-event delivery instructions).

[0107] Event receiver 182 receives event information from event classifier 170. The event information includes information about sub-events, such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves touch movement, the event information may optionally also include the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a portrait orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device orientation).

[0108] Event comparator 184 compares event information with predefined event or sub-event definitions and determines the event or sub-event based on the comparison, or determines or updates the state of the event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 contains definitions of events (e.g., predefined sequences of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in event (187) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, event 1 (187-1) is defined as a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift-off of a predetermined duration (touch end), a second touch (touch start) of a predetermined duration on the displayed object, and a second lift-off of a predetermined duration (touch end). In another example, event 2 (187-2) is defined as a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on the displayed object, movement of the touch on the touch-sensitive display 112, and lifting the touch (end of touch). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0109] In some implementations, event definition 187 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view displaying three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects the event handler associated with the sub-event and the object that triggered the hit test.

[0110] In some implementations, the definition of the corresponding event (187) also includes a delay action that delays the delivery of event information until it has been determined whether the sub-event sequence actually corresponds to or does not correspond to the event type of the event recognizer.

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

[0112] In some embodiments, the corresponding event recognizer 180 includes metadata 183 having configurable attributes, flags, and / or lists instructing how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing how or how event recognizers can interact with each other. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0113] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some implementations, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from delivering (and deferred delivering) the sub-events to the corresponding hit view. In some implementations, the event recognizer 180 throws a flag associated with the identified event, and the event handler 190 associated with the flag acquires the flag and performs a predefined process.

[0114] In some implementations, event delivery instruction 188 includes a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers the event information to an event handler associated with the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and performs a predetermined process.

[0115] In some implementations, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contact module 137 or stores video files used in video player module. In some implementations, 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 positioning of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and transmits that display information to graphics module 132 for display on a touch-sensitive display.

[0116] In some implementations, event handler 190 includes, or has access to, a data updater 176, an object updater 177, and a GUI updater 178. In some implementations, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other implementations, they are included in two or more software modules.

[0117] It should be understood that the above discussion regarding event handling for user touch on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 100, and not all user input is initiated on the touchscreen. For example, mouse movement and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof may optionally be used as input corresponding to sub-events that define the event to be identified.

[0118] FIG. 2A portable multifunction device 100 with a touchscreen 112 is illustrated according to some embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more graphics by gesturing over the graphics, for example, using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with one or more graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with the device 100. In some specific embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon may optionally not select the corresponding application when the gesture corresponding to selection is a tap.

[0119] Device 100 may optionally also include one or more physical buttons, such as a "main desktop" or menu button 204. As previously described, menu button 204 may optionally be used to navigate to any application 136 of a set of applications optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touchscreen 112.

[0120] In some embodiments, device 100 includes a touchscreen 112, a menu button 204, a push-button 206 for powering on / off and locking the device, one or more volume control buttons 208, a SIM card slot 210, a headset jack 212, and a docking / charging external port 124. The push-button 206 is optionally used to: power on / off the device by pressing the button and holding it in the pressed state for a predefined time interval; lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or unlock the device or initiate an unlocking process. In another embodiment, device 100 also accepts voice input via microphone 113 for activating or deactivating certain functions. Device 100 may also optionally include one or more contact strength sensors 165 for detecting the intensity of contact on the touchscreen 112, and / or one or more haptic output generators 167 for generating haptic outputs for a user of device 100.

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

[0122] FIG. 3Each of the elements described above may optionally be stored in one or more memory devices of the previously mentioned memory devices. Each of the modules described above corresponds to a set of instructions for performing the functions described above. The modules or programs (e.g., instruction sets) described above need not be implemented as separate software programs, processes, or modules, and therefore various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 may optionally store a subset of the modules and data structures described above. In addition, memory 370 may optionally store additional modules and data structures not described above.

[0123] Now let’s turn our attention to the implementation of the user interface, which may be optionally implemented on, for example, a portable multifunction device 100.

[0124] FIG. 4A An exemplary user interface for an application menu on a portable multifunction device 100 according to some embodiments is illustrated. A similar user interface may optionally be implemented on device 300. In some embodiments, user interface 400 includes the following elements or a subset or superset thereof: • Signal strength indicator 402 for wireless communications such as cellular signals and Wi-Fi signals; • Time 404; • Bluetooth indicator 405; • Battery status indicator 406; • Tray 408 features icons for frequently used applications, such as: ○ The telephone module 138 has an icon 416 labeled "telephone", which optionally includes an indicator 414 indicating the number of missed calls or voicemail messages; ○ An icon 418 labeled "Mail" in the email client module 140, which optionally includes an indicator 410 for the number of unread emails; ○ The icon 420 labeled "Browser" in browser module 147; and ○ The video and music player module 152 (also known as the iPod (Apple Inc. trademark) module 152) is marked with an icon 422 labeled "iPod"; and • Icons of other applications, such as: ○The icon 424 of the IM module 141 marked as "Message"; ○The calendar module 148 has an icon 426 labeled "Calendar"; ○ The icon 428 of the image management module 144 is labeled "Photo". ○ The icon 430 of camera module 143, which is labeled "camera"; ○ The icon 432 of the online video module 155, which is labeled "Online Video"; ○ The icon 434 in the Stock Market Desktop Mini Program 149-2 that is marked as "Stock Market"; ○The icon 436 of the map module 154 that is labeled "map"; ○ The icon 438 in the Weather desktop mini-program 149-1 that is marked as "Weather"; ○ The alarm clock widget 149-4 has an icon 440 labeled "clock"; ○ The icon 442 of the fitness support module 142 is labeled "fitness support"; ○ The icon 444 labeled "Notepad" in Notepad module 153 and ○ Set an icon 446 labeled "Settings" for an application or module, which provides access to settings for device 100 and its various applications 136.

[0125] It should be pointed out that, FIG. 4A The illustrated icon labels are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels may be used for various application icons. In some embodiments, the label of a particular application icon includes the name of the application corresponding to that particular application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to that particular application icon.

[0126] FIG. 4B An example is illustrated having a touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen display 112)). FIG. 3 A tablet device or touchpad 355) device (e.g., FIG. 3 An exemplary user interface on the device 300. The device 300 may also optionally include one or more contact intensity sensors (e.g., one or more sensors in sensor 359) for detecting the intensity of contact on the tactile surface 451 and / or one or more tactile output generators 357 for generating tactile output for the user of the device 300.

[0127] While some examples of input on a touchscreen display 112 (which combines a touch-sensitive surface and a display) are given below, in some implementations the device detects input on a touch-sensitive surface separate from the display, such as... FIG. 4B As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., FIG. 4B 451) has a spindle (e.g., on the display (e.g., 450) corresponding to the main axis on the display (e.g., FIG. 4B The main shaft of 453 in the middle (e.g., FIG. 4B(452 in the example). According to these embodiments, the device detects the position corresponding to a specific location on the display (e.g., in...). FIG. 4B In the diagram, 460 corresponds to 468 and 462 corresponds to 470) is in contact with the touch-sensitive surface 451 (e.g., FIG. 4B (460 and 462 in the text). Thus, when the touch-sensitive surface (e.g., ...) FIG. 5A 451 in the middle) and the display of a multi-functional device (e.g., FIG. 1A-4B When 450 is separated from the touch-sensitive surface, user input detected by the device on that touch-sensitive surface (e.g., touches 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods can be optionally used for other user interfaces described herein.

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

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

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

[0131] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push-buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, allow device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, bangles, trousers, belts, shoes, purses, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

[0132] FIG. 1B An exemplary personal electronic device 500 is depicted. In some embodiments, device 500 may include, relative to... FIG. 3 , FIG. 11 and FIG. 5BSome or all of the components described herein. Device 500 has a bus 512 that operatively couples I / O portion 514 to one or more computer processors 516 and memory 518. I / O portion 514 may be connected to display 504, which may have touch-sensitive component 522 and optionally have intensity sensor 524 (e.g., contact intensity sensor). Furthermore, I / O portion 514 may be connected to communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular and / or other wireless communication technologies. Device 500 may include input mechanisms 506 and / or 508. For example, input mechanism 506 may optionally be a rotatable input device or a pressable input device and a rotatable input device. In some examples, input mechanism 508 may optionally be a button.

[0133] In some examples, the input mechanism 508 may optionally be a microphone. The personal electronic device 500 may optionally include 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 are operatively connected to the I / O section 514.

[0134] 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, and 100 (Figures 7, 9, and 100). FIG. 1A A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media can include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical discs based on CD, DVD, or Blu-ray technology, and persistent solid-state storage such as flash memory, solid-state drives, etc. Personal electronic devices are not limited to... FIG. 3 It can be the components and configurations, or it can include other components or additional components in a variety of configurations.

[0135] Furthermore, in methods described herein where one or more steps depend on the satisfaction of one or more conditions, it should be understood that the method may be repeated in multiple repetitions such that, during the repetitions, all conditions determining the steps in the method are satisfied in different repetitions of the method. For example, if the method requires performing a first step (if the condition is satisfied) and a second step (if the condition is not satisfied), those skilled in the art will know that the stated steps are repeated until both the conditions are satisfied and not satisfied (in no particular order). Thus, a method described as having one or more steps depending on the satisfaction of one or more conditions can be rewritten as a method that repeats until each condition described in the method is satisfied. However, this does not require the system or computer-readable medium to declare that the system or computer-readable medium contains instructions for performing discretionary operations based on the satisfaction of the corresponding one or more conditions, and thus to determine whether possible conditions have been satisfied without explicitly repeating the steps of the method until all conditions determining the steps in the method are satisfied. Those skilled in the art will also understand that, similar to methods having discretionary steps, a system or computer-readable storage medium may repeat the steps of the method multiple times as needed to ensure that all discretionary steps have been performed.

[0136] As used herein, the term "power indication" refers to the ability to indicate power in devices 100, 300, and / or 500 (…). FIG. 5A-B , FIG. 3 and FIG. 4B A user-interactive graphical user interface object displayed on a screen. For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) may each constitute a functional representation.

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

[0138] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity may optionally be based on a predefined number of intensity samples or a set of intensity samples collected over a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to lift off, before or after contact begins to move, before contact ends, before or after contact intensity increases and / or before or after contact intensity decreases). The characteristic intensity of a contact may optionally be based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half maximum value of the contact intensity, or the 90% maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the contact intensity over time). In some implementations, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether a user has performed an action. For example, the set of one or more intensity thresholds may optionally include a first intensity threshold and a second intensity threshold. In this example, contact with a characteristic intensity not exceeding the first threshold results in a first action, contact with a characteristic intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a characteristic intensity exceeding the second threshold results in a third action. In some implementations, a comparison between the characteristic intensity and one or more thresholds is used to determine whether one or more actions should be performed (e.g., whether to perform the corresponding action or abandon performing the corresponding action) rather than to determine whether to perform the first action or the second action.

[0139] FIG. 5D An example is shown using multiple intensity sensors 524A-524D to detect multiple contacts 552A-552E on a touch-sensitive display 504. FIG. 5C-D It also includes an intensity graph, which shows the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are both 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are both 7 intensity units. In some embodiments, the cumulative intensity is the sum of the intensity measurements of the multiple intensity sensors 524A-524D, which is 32 intensity units in this example. In some implementations, each contact is assigned a corresponding intensity, i.e., a portion of the cumulative intensity. FIG. 5C-DAn example is given of assigning cumulative intensity to contacts 552A-552E based on their distance from the center of force 554. In this example, each of contacts 552A, 552B, and 552E is assigned a contact intensity of 8 intensity units of the cumulative intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of the cumulative intensity. More generally, in some specific implementations, each contact j is assigned a corresponding intensity Ij according to a predefined mathematical function Ij = A·(Dj / ΣDi), which is a portion of the cumulative intensity A, where Dj is the distance of the corresponding contact j from the center of force, and ΣDi is the sum of the distances of all corresponding contacts (e.g., i=1 to the last) from the center of force. Reference can be performed using electronic devices similar to or equivalent to devices 100, 300, or 500. FIG. 5E-H The operation described above. In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine the intensity of a single characteristic (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity map is not part of the displayed user interface, but is included within... FIG. 5E This is intended to assist readers.

[0140] In some implementations, a portion of the gesture is identified for determining the characteristic intensity. For example, a touch-sensitive surface may optionally receive a series of swipe contacts that transition from a starting position to an ending position, where the contact intensity increases. In this example, the characteristic intensity of the contact at the ending position may optionally be based only on a portion of the series of swipe contacts, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the ending position). In some implementations, a smoothing algorithm may optionally be applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm may optionally include one or more of the following: unweighted moving average smoothing algorithm, triangular smoothing algorithm, median filter smoothing algorithm, and / or exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic intensity.

[0141] Optionally, the contact intensity on a touch-sensitive surface can be characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from the operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, when a contact with a characteristic intensity lower than the light press intensity threshold (e.g., and higher than the nominal contact detection intensity threshold, where contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector based on the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different groups of user interface figures.

[0142] An increase in contact intensity from below a light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact intensity from below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact intensity from below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. A decrease in contact intensity from above a contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a contact being lifted off 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.

[0143] In some embodiments described herein, one or more operations are performed in response to detecting a gesture including a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the intensity of the contact (or multiple contacts) increases to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting that the intensity of the corresponding contact increases to above a press input intensity threshold (e.g., a "downward stroke" of the corresponding press input). In some embodiments, the press input includes the intensity of the corresponding contact increasing to above a press input intensity threshold and the intensity of the contact subsequently decreasing to below the press input intensity threshold, and the corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "upward stroke" of the corresponding press input).

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

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

[0146] In some implementations, the device employs intensity hysteresis to avoid unintended inputs sometimes referred to as "jitter," wherein the device defines or selects a hysteresis intensity threshold that has a predefined relationship with a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Therefore, in some implementations, a press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of that contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and an operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases below the hysteresis intensity threshold (e.g., the "upstroke" of the corresponding press input). Similarly, in some implementations, a press input is detected only when the device detects that the intensity of the contact increases from an intensity equal to or below a hysteresis intensity threshold to an intensity equal to or above a press input intensity threshold and optionally the intensity of the contact subsequently decreases to an intensity equal to or below the hysteresis intensity, and corresponding operations are performed in response to the detection of a press input (e.g., depending on the environment, the intensity of the contact increases or decreases).

[0147] For ease of explanation, optionally, the description of an operation triggered in response to a press input associated with a press input strength threshold or in response to a gesture including a press input may be provided in response to detecting any of the following conditions: the contact strength increases to above the press input strength threshold, the contact strength increases from below a hysteresis strength threshold to above the press input strength threshold, the contact strength decreases to below the press input strength threshold, and / or the contact strength decreases to below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in the example where the operation is described as being performed in response to detecting a decrease in contact strength below the press input strength threshold, the operation may optionally be performed in response to detecting a decrease in contact strength below a hysteresis strength threshold corresponding to and less than the press input strength threshold.

[0148] In some embodiments, electronic device 500 includes one or more tactile output generators, wherein the one or more tactile output generators generate different types of tactile output sequences, as described in Table 1 below. In some embodiments, a particular type of tactile output sequence generated by the 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. When a device (e.g., one or more tactile output generators that generate tactile output via a movable mass) generates tactile outputs with different tactile output patterns, the tactile outputs can produce different tactile sensations in a user holding or touching the device. Although the user's senses are based on the user's perception of the tactile output, most users will be able to identify variations in the waveform, frequency, and amplitude of the tactile output generated by the device.

[0149] More specifically, FIG. 5L-N Provides a set of sample haptic output patterns that can be used individually or in combination, as is or through one or more transformations (e.g., modulation, amplification, truncation, etc.) to form suitable haptic feedback in various scenarios and for various purposes (such as those described above and those relative to the user interfaces and methods discussed herein). This example of a haptic output control panel shows how an array of three waveforms and eight frequencies can be used to generate haptic output patterns. In addition to the haptic output patterns shown in these figures, each of these haptic output patterns can optionally be adjusted in amplitude by changing the gain value of the haptic output patterns, as shown, for example for FIG. 5I-N The FullTap 80Hz, FullTap 200Hz, MiniTap 80Hz, MiniTap 200Hz, MicroTap 80Hz, and MicroTap 200Hz are shown as variants with gains of 1.0, 0.75, 0.5, and 0.25, respectively. FIG. 5I As shown, changing the gain of the haptic output mode changes the amplitude of the mode without changing the frequency of the mode or the shape of the waveform. In some implementations, changing the frequency of the haptic output mode also results in a lower amplitude because some haptic output generators are limited by how much force can be applied to the movable mass. Therefore, higher frequency movements of the mass are constrained to lower amplitudes to ensure that the acceleration required to form the waveform does not require forces outside the operating force range of the haptic output generator (e.g., the peak amplitude of FullTap at 230Hz, 270Hz, and 300Hz is lower than that of FullTap at 80Hz, 100Hz, 125Hz, and 200Hz).

[0150] FIG. 5JA tactile output pattern with a specific waveform is shown. The waveform of the tactile output pattern represents a pattern of physical displacement versus time relative to a neutral position (e.g., Xzero), through which a movable mass passes to generate a tactile output with that tactile output pattern. For example, FIG. 5K Each of the first set of tactile output modes shown (e.g., the tactile output mode of “FullTap”) has a waveform that includes an oscillation with two complete cycles (e.g., an oscillation that starts and ends at a neutral position and passes through the neutral position three times). FIG. 5I-N Each of the second set of tactile output modes shown (e.g., the tactile output mode of “MiniTap”) has a waveform that includes an oscillation with a complete cycle (e.g., an oscillation that starts and ends at a neutral position and passes through the neutral position once). FIG. 5I-N Each of the third group of haptic output modes shown (such as the haptic output mode of "MicroTap") has a waveform that includes an oscillation of half a complete cycle (e.g., an oscillation that starts and ends at a neutral position without crossing the neutral position). The waveform of the haptic output mode also includes start buffers and end buffers that represent the gradual acceleration and deceleration of the movable mass at the start and end of the haptic output. FIG. 5I-K The example waveforms shown include Xmin and Xmax values ​​representing the maximum and minimum movement of the movable mass. For larger electronic devices with larger movable masses, the minimum and maximum movement of the mass can be greater or smaller. FIG. 5I-N The example shown describes the movement of a mass in one dimension, but similar principles can also be applied to the movement of movable masses in two or three dimensions.

[0151] like FIG. 5I As shown, each haptic output mode also has a corresponding characteristic frequency, which affects the "pitch" of the tactile sensation felt by the user from a haptic output with that characteristic frequency. For continuous haptic output, the characteristic frequency represents the number of cycles (e.g., cycles per second) completed by the movable mass of the haptic output generator within a given time period. For discrete haptic output, discrete output signals are generated (e.g., with 0.5, 1, or 2 cycles), and the characteristic frequency value specifies how fast the movable mass needs to move to generate a haptic output with that characteristic frequency. FIG. 5I-K As shown, for each type of haptic output (e.g., defined by the corresponding waveform, such as FullTap, MiniTap, or MicroTap), higher frequency values ​​correspond to faster movement of the movable mass, and therefore generally correspond to shorter haptic output completion times (e.g., including the time required to complete the number of cycles for the discrete haptic output plus start and end buffer times). For example, a FullTap with a characteristic frequency of 80Hz takes longer to complete than a FullTap with a characteristic frequency of 100Hz (e.g., in...). FIG. 5I-KIn the example, 35.4ms vs. 28.3ms). Furthermore, for a given frequency, a haptic output with more cycles in its waveform at that frequency takes longer to complete than a haptic output with fewer cycles in its waveform at the same corresponding frequency. For example, a 150Hz FullTap takes longer to complete than a 150Hz MiniTap (e.g., 19.4ms vs. 12.8ms), and a 150Hz MiniTap takes longer to complete than a 150Hz MicroTap (e.g., 12.8ms vs. 9.4ms). However, this rule may not apply to haptic output patterns with different frequencies (e.g., a haptic output with more cycles but a higher frequency may take a shorter amount of time to complete than a haptic output with fewer cycles but a lower frequency, and vice versa). For example, at 300Hz, a FullTap and a MiniTap take the same amount of time (e.g., 9.9ms).

[0152] like User interface and associated processes As shown, the haptic output mode also has a characteristic amplitude that affects the amount of energy contained in the haptic signal, or the "intensity" of the tactile sensation that a user can perceive through a haptic output with that characteristic amplitude. In some embodiments, the characteristic amplitude of the haptic output mode refers to the absolute or normalized value representing the maximum displacement of the movable mass relative to a neutral position when the haptic output is generated. In some embodiments, the characteristic amplitude of the haptic output mode can be adjusted according to various conditions and / or pre-configured metrics (e.g., input-based metrics, and / or user-based metrics) such as fixed or dynamically determined gain coefficients (e.g., values ​​between 0 and 1), based on various conditions (e.g., user interface context and behavior-defined). In some embodiments, input-based metrics (e.g., intensity change metrics or input velocity metrics) measure the characteristics of the input (e.g., the rate of change of the characteristic intensity of a contact in a press input or the rate of movement of the contact on a haptic surface) during the input that triggers the generation of the haptic output. In some implementations, user interface-based metrics (e.g., cross-boundary velocity metrics) measure the characteristics of a user interface element (e.g., the speed at which the element moves across a hidden or visible boundary in the user interface) during a user interface change that triggers the generation of haptic output. In some implementations, the characteristic amplitude of the haptic output pattern can be “envelope” modulated, and the peak values ​​of adjacent cycles can have different amplitudes, wherein one of the waveforms shown above is further modified by multiplying by an envelope parameter that changes over time (e.g., from 0 to 1) to gradually adjust the amplitude of a portion of the haptic output over time when generating the haptic output.

[0153] Although for illustrative purposes Time-limited location sharing of remotely located locator objectsThe sample haptic output modes in the document represent specific frequencies, amplitudes, and waveforms, but haptic output modes with other frequencies, amplitudes, and waveforms can also be used for similar purposes. For example, waveforms with between 0.5 and 4 cycles can be used. Other frequencies in the range of 60 Hz to 400 Hz can also be used. Table 1 below provides representative examples of haptic output / haptic feedback behavior and configurations, along with examples of their use relative to a user interface used to manage the content-based haptic outputs illustrated and described herein.

[0154]

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

[0156] As used herein, the terms "open application" or "running application" refer to a software application that maintains state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application can optionally be any of the following types of applications: • Active app, which is currently displayed on the screen of the device that is using the app; • Background applications (or background processes) that are not currently displayed but whose one or more processes are being handled by one or more processors; and • Suspended or hibernating applications that are not currently running but have state information stored in memory (either volatile or non-volatile) that can be used to resume the application's execution.

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

[0158] Now let’s turn our attention to the implementation of user interfaces (“UIs”) on electronic devices, such as portable multifunction devices 100, 300 or 500, and the associated processes.

[0159] FIG. 6A-I FIG. 7A-E Users interact with electronic devices in a variety of different ways. In some implementations, electronic devices are capable of tracking the location of trackable objects such as remote locator objects. In some implementations, access to such remote locator objects can be shared by the owner of the remote locator object and an entity (e.g., one or more persons associated with the entity). The implementations described below provide a way for electronic devices to share location information of remote locator objects with entities for a duration associated with a time-limited event, thus enhancing user interaction with the electronic device. Enhanced interaction with the device reduces the amount of time required for users to perform operations, thereby reducing the device's power consumption and extending the battery life of battery-powered devices. It should be understood that people use devices. When a person uses a device, that person may optionally be referred to as the user of the device.

[0160] FIG. 6A-I Exemplary methods are illustrated in which electronic devices according to some embodiments of the present disclosure share location information of a remote locator object with an entity for a duration associated with a time-limited event. The embodiments in these figures are used to illustrate the processes described below, including references to... FIG. 6A The process described.

[0161] FIG. 6A An example is an electronic device 500 associated with a user, which includes a touchscreen 504 that displays one or more aspects of the location of a remote locator object shared with an entity over a duration associated with a time-limited event. FIG. 6A In this context, electronic device 500 refers to a mobile electronic device belonging to Frank, as described below. Furthermore, as... FIG. 6A As shown, electronic device 500 displays a user interface 602 for an item location application, which displays information about one or more searchable items for which the user (e.g., Frank) has access to their location. It should be understood that, as described below, the location of electronic device 500 and the location of the user of electronic device 500 are used interchangeably herein.

[0162] like FIG. 6A As shown, in some embodiments, the user interface 602 of the item location application includes a list 608 of searchable items to which the user (e.g., Frank) has access to their location. For example, and as... FIG. 6AAs shown, list 608 (named "Items") includes user-owned locator items (e.g., remote locator objects or other trackable objects), such as "Frank's briefcase" in first item 610b, "Frank's keys" in second item 610d, "Frank's backpack" in third item 610c, and "Frank's wireless earphones" in fourth item 610a. FIG. 6A As shown, the searchable items in list 608 may optionally include graphic representations corresponding to specific searchable items, such as a graphic representation of a suitcase for “Frank’s briefcase” in 610b and a graphic representation of a key for “Frank’s key” in 610d.

[0163] In some embodiments, the user interface 602 of the item location application includes one or more distance indicators that indicate the distance of items in the list 608 from the electronic device 500 (and therefore from the user). In some embodiments, the one or more distance indicators may optionally be accompanied by a time indicator (e.g., now, 2 seconds ago, 1 minute ago, 1 hour ago, or 5 hours ago) indicating the time when the particular distance indicator was last updated. For example, as... FIG. 6A As shown, in user interface 602, the first item 610b of list 608 indicates that the searchable item "Frank's briefcase" is approximately 0.1 miles from the current location of electronic device 500, and this location information was last updated "now" (e.g., when user interface 602 is first displayed on electronic device 500). Furthermore, in FIG. 6A In the list 608, the second item 610d indicates that the locating item "Frank's Key" is 0.2 miles from the current location of the electronic device 500, and the last update time for this location information is "now". Additionally, as... FIG. 6A As shown, as an example, the third item 610c in list 608 indicates that the locatable item "Frank's Backpack" is approximately 0.4 miles from the current location of electronic device 500, and the last update time for this location information is "now," while the fourth item 610a indicates that the locatable item "Frank's Wireless Headphones" is "with you" (e.g., at the user's current location). FIG. 6A As indicated in the example, the location of the searchable item in list 508 may optionally be given as a name of a location, such as Los Angeles International Airport. In some embodiments, the location of the searchable item may alternatively be provided as an address. In some embodiments, when the corresponding searchable item is indicated as "within your reach" (e.g., within a threshold distance of device 500A such as 0.1 m, 0.5 m, 1 m, 5 m, 10 m, or 100 m), the given representation 608 does not include an indication of the distance to that searchable item.

[0164] In some implementation schemes, FIG. 6A The user interface 602 of the item location application includes a representation of a map surrounding and / or including the location of a user (e.g., Frank) and / or an electronic device 500. In some embodiments, the map indicates: the location of the user (e.g., Frank) and / or the electronic device 500 as circles, the location of searchable items (e.g., including remote locator objects) in list 608, such as a representation of "Frank's briefcase" on the map corresponding to the location of "Frank's briefcase" in the physical area (icon 606b), a representation of "Frank's keys" on the map corresponding to the location of "Frank's keys" (icon 606d), a representation of "Frank's backpack" on the map corresponding to the location of "Frank's backpack" (icon 606c), and a representation of "Frank's wireless headphones" on the map corresponding to the location of "Frank's wireless headphones" (icon 606a), and / or the locations of additional users who share their locations with the user (e.g., Frank). FIG. 6A As shown in the example, there are currently no attached users sharing their location with Frank, and therefore no attached users are displayed on user interface 602. FIG. 6B Further shown, and as noted above, 606a, 606b, 606c, and 606d indicate corresponding searchable items (e.g., graphics of the corresponding searchable items) so that a user (e.g., Frank) can visually identify searchable items on a map of user interface 602. In some embodiments, and as... FIG. 6B As shown, the representation of searchable items on the map of user interface 602 includes bubbles and / or circles containing the graphics discussed above. However, it should be understood that the representation can optionally be of any shape and / or size. In some embodiments, and as... FIG. 6B As shown, the representation 606a of the searchable item "Frank's Wireless Headphones" and the current location of the user / electronic device 500 are stacked on the map of the user interface 602 because the current location of the user and the searchable item "Frank's Wireless Headphones" are very close.

[0165] exist FIG. 6B In this context, when the user interface 602 of the item location application is displayed via touchscreen 504, electronic device 500 detects a selection of a first item 610b pointing to list 608 in user interface 602 via touch 603. For example, electronic device 500 detects a click, tap, swipe, and / or hover input on touchscreen 504 above a position corresponding to the first item 610b. In some embodiments, such as... FIG. 6BAs shown, in response to detecting a selection of the first item 610b, the electronic device 500 displays a user interface 612 associated with the searchable item "Frank's briefcase" via a touchscreen 504. For example, as FIG. 6A-E As shown, the electronic device 500 replaces the display of the user interface 602 with a user interface 612. In some embodiments, the user interface 612 corresponds to an extension of the first item 610b in the list 608 of the user interface 502. For example, as FIG. 6B As shown, the user interface 612 includes the name of the selected searchable item (e.g., "Frank's suitcase") and the current location of the selected searchable item (e.g., Los Angeles International Airport in Los Angeles, California).

[0166] In some implementations, the user interface 612 associated with the locatable item "Frank's briefcase" enables management of the locatable item "Frank's briefcase". For example, as FIG. 6B As shown, the user interface 612 includes a first optional option 614a and a second optional option 614b. In some embodiments, the first optional option 614a can be selected to cause a locator item named "Frank's Suitcase" (e.g., a remote locator object) to emit a sound (e.g., a bell, chime, tone, song, or other melody) that enables the user to locate the locator item. In some embodiments, the second optional option 614b can be selected to initiate a process for navigating to the locator item "Frank's Suitcase". For example, the electronic device displays a user interface of a navigation application via a touchscreen 504, which provides instructions (e.g., route details and / or an overview) for navigating to the location of the locator item.

[0167] In addition, such as FIG. 6C As shown, the user interface 612 includes a region 616 associated with time-limited events. For example, a time-limited event is a travel event that a user (e.g., Frank) will participate in. FIG. 6CIn the example below, the time-limited event is a flight, but it should be understood that other time-limited events are also possible (e.g., as described below with reference to method 700). In some implementations, the information included in area 616 is based on the current location of electronic device 500 and / or the locator "Frank's suitcase". For example, because the current location of electronic device 500 (e.g., and the user) and the locator "Frank's suitcase" is Los Angeles International Airport, electronic device 500 prompts the user, such as via optional option 613, to associate the locator "Frank's suitcase" with a specific flight. As described below, in some implementations, optional option 613 can be selected to initiate a process for associating the locator "Frank's suitcase" with a specific time-limited event (e.g., a flight).

[0168] exist FIG. 6C In the process, electronic device 500 detects a selection pointing to optional option 613. For example, as FIG. 6C As shown, electronic device 500 detects a tap 603 of a contact object on touchscreen 504 at a location corresponding to optional option 613. In some embodiments, such as FIG. 6C As shown, in response to detecting a selection of optional option 613, electronic device 500 initiates a process for associating the locatable item "Frank's suitcase" with a specific flight. For example, as FIG. 6C As shown, the electronic device 500 displays a user interface 620 via a touchscreen 504 for associating the searchable item “Frank’s suitcase” with time-limited events (e.g., flights), as discussed below.

[0169] In some implementation schemes, such as FIG. 6C As shown, based on the determination that the user has an upcoming flight (e.g., today, tomorrow, next week, and / or next month), the electronic device 500 suggests the upcoming flight as a time-limited event associated with the locatable item "Frank's suitcase". In some implementations, such as FIG. 6C As shown, it is suggested that the upcoming flight include displaying a representation of the digital boarding pass associated with the user (e.g., Frank) in the user interface 620. In some embodiments, the electronic device 500 displays the digital boarding pass because the electronic device 500 has access to the digital boarding pass. For example, the user may have previously downloaded and saved the digital boarding pass to the electronic device 500 (e.g., its memory) for later use when boarding the aircraft associated with the indicated flight (e.g., "Flight 822"). FIG. 4AAs shown, the user interface 620 includes a first optional option 622a and a second optional option 622b. In some embodiments, the first optional option 622a can be selected to associate a suggested upcoming flight with the searchable item “Frank’s suitcase,” as discussed in more detail below. In some embodiments, the second optional option 622b can be selected to associate the searchable item “Frank’s suitcase” with different time-limited events, such as different flights. For example, selecting the second optional option 622b allows the user to manually select a time-limited event (e.g., by entering (e.g., via keyboard input) details of the time-limited event (e.g., flight), such as passenger information, flight number, airline, etc.). In some embodiments, if the electronic device 500 does not recognize / identify a known upcoming time-limited event (e.g., because the user has not yet downloaded and saved the digital boarding pass to the electronic device 500), the user interface 620 does not include a representation of the digital boarding pass as discussed above and optionally only includes optional option 622b. It should be understood that in some implementations, if a user has additional upcoming flights or other time-limited events, the user interface 620 includes an additional representation of a digital pass associated with the additional time-limited events and that is browsable (e.g., scrollable) to allow the user to associate the searchable item with one or more of the time-limited events in the manner discussed above.

[0170] exist FIG. 6F In this context, when the user interface 620 is displayed on the touchscreen 504, the electronic device 500 detects a selection of the first optional option 622a. For example, as... FIG. 6F As shown, electronic device 500 detects a tap 603 on touchscreen 504 at a location corresponding to the first optional option 622a. In some embodiments, in response to detecting a selection of the first optional option 622a, electronic device 500 associates the locatable item “Frank’s suitcase” with a flight (e.g., “Flight 822”) identified by the user’s digital boarding pass.

[0171] In some implementations, associating a searchable item with a time-limited event includes granting the entity associated with the time-limited event access to the location information of the searchable item. For example, in FIG. 6FIn this embodiment, when electronic device 500 associates the locatable item “Frank’s briefcase” with a user’s upcoming flight (e.g., “Flight 822”), electronic device 500 shares (e.g., directly or via a server (e.g., a wireless communication terminal)) the location information of the locatable item “Frank’s briefcase” with the entity facilitating and / or operating the upcoming flight (e.g., an airline or other organization). In some embodiments, when sharing location information, the entity has access to the location information (e.g., the current location of “Frank’s briefcase”) for a corresponding duration. In some embodiments, the corresponding duration corresponds to the duration of a time-limited event (e.g., the duration of the user’s flight, such as the duration from takeoff to landing). In some embodiments, the corresponding duration corresponds to the duration between when the user is no longer with the locatable item (e.g., when the locatable item is more than a threshold distance, such as 0.1 m, 0.5 m, 1 m, 5 m, 10 m, or 100 m from the current location of electronic device 500) and when the user re-enters the locatable item (e.g., when the locatable item is within a threshold distance from the current location of electronic device 500). For example, an airline has access to the current location of the locatable item "Frank's Suitcase" from the time a user (e.g., Frank) checks in a suitcase (the physical item to which a remote locator object is attached) at the baggage check-in counter until the user picks up the suitcase from the baggage claim counter at the user's destination (e.g., the destination airport) and / or the time the user leaves the destination with the suitcase.

[0172] Additionally or alternatively, in some implementations, users can associate searchable items with time-limited events associated with the physical entity via a wallet application operating on the electronic device. In some implementations, as described similarly above, when the electronic device 500 is displaying an icon that includes multiple icons corresponding to applications configured to run on the electronic device 500 (e.g., ...), FIG. 6C When the user is on the main screen user interface, they select the corresponding icon to launch the wallet application. In some implementations, such as... FIG. 6F As shown, when the wallet application is launched, the electronic device displays the wallet application's user interface 640 on the touchscreen 504. In some implementations, the digital credit card or debit wallet application is configured to store debit cards, boarding passes, health or insurance cards, etc., that the user can easily access. Therefore, as... FIG. 6G As shown, the user interface 640 of the wallet application optionally includes a representation 642a of a first digital boarding pass, a representation 642b of a second digital boarding pass, a representation 642c of a first credit card, and / or a representation 642d of a first rewards card / loyalty card.

[0173] In some implementations, the representation of the corresponding digital boarding pass can be selected to initiate a process that associates the corresponding locatable item with a corresponding time-limited event associated with the corresponding digital boarding pass. For example, such as FIG. 6A As shown, the electronic device 500 detects a selection of a representation 642b of a second digital boarding pass in the user interface 640 via a tap 603 of a contact. In some embodiments, the second digital boarding pass 642b corresponds to the representation described above. FIG. 6H The digital boarding pass. In some embodiments, in response to detecting a selection of a representation 642b of the second digital boarding pass, the electronic device 500 displays an optional option 644 having the representation 642b of the second digital boarding pass in the user interface 640. In some embodiments, the optional option 644 can be selected to initiate a process for associating a time-limited event (e.g., “Flight 822”) indicated by the representation 642b of the second digital boarding pass with a locatable item. In some embodiments, in FIG. 6H If the user has alternatively selected (e.g., via a tap 603 on a contact object) the representation 642a of the first digital boarding pass, the electronic device 500 will optionally display an optional option 644 with the representation 642b of the first digital boarding pass, which can be selected to initiate a process for associating a time-limited event indicated by the representation 642a of the first digital boarding pass with a locatable item. FIG. 6H In this process, electronic device 500 detects a selection to optional option 644 via a tap 603 on a contact object. In some embodiments, in response to detecting a selection to optional option 644, electronic device 500 may, optionally if the searchable item discussed above (e.g., "Frank's suitcase") has not been previously selected, initiate a selection to associate the flight with it (e.g., via a reference). FIG. 6H The process of finding items (described in an item location app or similar app).

[0174] Additionally or alternatively, in some embodiments, a user can associate a searchable item with a time-limited event associated with the entity via an application associated with the entity. In some embodiments, when electronic device 500 is displaying a main screen user interface including multiple icons corresponding to applications configured to run on electronic device 500 (e.g., as discussed similarly above), the user selects the appropriate icon to launch the application associated with the entity (e.g., an airline application). In some embodiments, such as FIG. 6H As shown, when an application associated with an entity is launched, the electronic device displays the user interface 650 of the application (e.g., an airline application) on touchscreen 504. In some implementations, such as FIG. 6IAs shown, the user interface 650 includes a first area 652 (e.g., below "My Flights") that displays information corresponding to upcoming time-limited events (e.g., the user's upcoming flight, such as "Flight 822"). In some implementations, such as FIG. 6I As shown, the first area 652 also includes an optional option 654, which can be selected to initiate a process for confirming participation in a time-limited event (e.g., check-in for a user's upcoming flight). Additionally, as... FIG. 6I As shown, in some implementations, the user interface 650 includes a second area 656 that includes multiple optional options (e.g., labels) for interacting with an application associated with an entity.

[0175] exist FIG. 6H In the process of displaying the user interface 650, the electronic device 500 detects a selection of an optional option 654 in the first area 652 via a tap 603 of a contact. In some embodiments, such as FIG. 6I As shown, in response to detecting a selection of optional option 654, electronic device 500 initiates a check-in process for a user's upcoming flight, including displaying user interface 660. In some embodiments, user interface 660 is a management user interface for time-limited events (e.g., "Flight 822"). FIG. 6A As shown, in some implementations, the user interface 660 includes one or more options for managing time-limited events. For example, in FIG. 6C In this embodiment, user interface 660 includes: a first option 662, selectable to initiate a process for requesting a seat change for a flight; and a second option 664, selectable to initiate a process for requesting a seat upgrade for a flight. Additionally, in some embodiments, user interface 660 includes an optional option 666, selectable to initiate a process for associating a time-limited event (e.g., "Flight 822") with a searchable item. In some embodiments, in... FIG. 6D If the user has optionally provided input for check-in for an alternative flight (e.g., via a tap 603), the electronic device 500 will optionally display a management user interface for that alternative flight, which will include optional options 666 that can be selected to initiate a process for associating the alternative flight with a searchable item. FIG. 6CIn this process, electronic device 500 detects a selection of optional option 666 in user interface 660 via a tap 603 of a contact. In some embodiments, in response to detecting a selection of optional option 666, electronic device 500 may, optionally if the searchable item described above (e.g., “Frank’s suitcase”) has not been previously selected, initiate a selection to associate the flight with it (e.g., via a reference). FIG. 6D The process of finding items (described in an item location app or similar app).

[0176] In some implementations, the locatable item "Frank's briefcase" has been linked to FIG. 6D After the indicated flight (e.g., "Flight 822") is associated with the locator and the location information of the locator is shared with an entity (e.g., an airline), the electronic device 500 updates the user interface 612 associated with the locator "Frank's suitcase" based on the association with the flight. For example, as FIG. 6E As shown, when the user interface 612 is redisplayed on the touchscreen 504, area 616 is updated to include information / instructions 626 (e.g., links) indicating that the locatable item “Frank’s suitcase” is associated with “Flight 822”, and thus the location information of the locatable item is shared with the airline of “Flight 822” (as referenced above). FIG. 6D (As discussed). It should be understood that in some implementations, if the locatable item "Frank's suitcase" is associated with additional time-limited events (e.g., additional flight, train, or bus trips), area 616 will be updated to include indications for those additional time-limited events (e.g., similar to indication 626).

[0177] Additionally, in some implementations, such as FIG. 6D As shown, electronic device 500 updates user interface 612 to include information 630 corresponding to the status of the searchable item "Frank's briefcase" relative to a time-limited event (e.g., flight). For example, in FIG. 6DIn this context, information 630 indicates one or more updates for a locatable item during a flight via status indicators 628 (e.g., "Completed" or "Pending"), such as the locatable item having been checked in at the baggage claim area (at 630a), the locatable item having been processed and sent to the baggage hold (at 630b), the locatable item having been processed for transport to the aircraft (630c), and the locatable item being loaded onto the aircraft (630d). In some embodiments, information 630 including status indicators 628 is updated by electronic device 500 based on status information received from an entity (e.g., an airline) (e.g., real-time or periodic). For example, the airline provides status updates for the locatable item "Frank's suitcase" to electronic device 500 based on tracking the location of the locatable item (e.g., throughout the airport). Additionally or alternatively, status updates may optionally (e.g., via notifications or other indications) be displayed on the lock screen user interface of electronic device 500, such as... FIG. 6F This is provided on the lock screen user interface. Therefore, through the user-device interaction described above, the user is able to follow the traceable item "Frank's suitcase" through the handling and loading on the plane, and thus help provide the user with peace of mind as the item is transported to the user's destination.

[0178] In some implementation schemes, FIG. 6D In this context, indicator 626 can be selected to display information corresponding to a time-limited event. For example, the indicator may be or include a link that can be selected to display real-time (e.g., live) status information of the user's upcoming flight (e.g., via the wallet application discussed above and / or the application of the entity discussed above). FIG. 6H In this process, electronic device 500 detects a selection directed to instruction 626 in user interface 612. For example, as FIG. 6D As shown, electronic device 500 detects a tap 603 on touchscreen 504 above the position indicated by indicator 626.

[0179] In some implementations, in response to detecting a selection of indication 626, electronic device 500 displays live status information for an upcoming time-limited event (e.g., a user's upcoming flight). In some implementations, electronic device 500 displays the live status information within its wallet application. For example, see reference... FIG. 6E In response to the detection of FIG. 6AUpon selection of instruction 626, electronic device 500 displays the user interface 640 of the wallet application previously described above, which includes a digital boarding pass 642b displaying live status information for the user's upcoming flight (such as "Flight 822" discussed above). Alternatively, in some embodiments, electronic device 500 displays the live status information in an application associated with the entity (e.g., an airline application). For example, refer to... FIG. 6A In response to the detection of FIG. 7A-E Upon selection of instruction 626, electronic device 500 displays user interface 650 of the airline application previously described above, which includes area 652 that displays real-time status information of the user's upcoming flight (e.g., "Flight 822").

[0180] In some implementations, the above process can be initiated via a suggestion from electronic device 500. For example, in FIG. 6A-I In this context, when electronic device 500 is displaying a lock screen user interface on touchscreen 504, electronic device 500 generates notification 634, which prompts the user to associate one or more searchable items with a specific (e.g., upcoming) time-limited event, such as a time-limited event indicated by instruction 636. As described similarly above, electronic device 500 may optionally suggest time-limited events based on known (e.g., stored) information about the time-limited events, such as based on digital boarding passes for flights that the user has downloaded and saved to electronic device 500, or calendar events for flights that the user has generated or added to the calendar application of electronic device 500. In some such embodiments, when a known time-limited event is approaching (e.g., a time-limited event is scheduled to occur the following day, the next week, the next two weeks, or the next month), electronic device 500 generates notification 634, which includes a message suggesting associating one or more searchable items with the known time-limited event (e.g., a flight). In some embodiments, if electronic device 500 detects a selection pointing to notification 634 (e.g., via contact 603 discussed above), electronic device 500 launches an item locator application and displays... FIG. 1A-B The user interface 602 enables users to associate one or more searchable items with upcoming flights in a manner similar to that described above.

[0181] It should be understood that, in some implementations, the method described above for associating the searchable item “Frank’s briefcase” with a time-limited event can be similarly applied to other searchable items owned by the user (e.g., FIG. 2-3 One or more searchable items (represented in the searchable items section) and / or other time-limited events (e.g., train journeys, bus journeys, and / or carpooling events).

[0182] FIG. 4A-B This is an example based on some implementation schemes (such as in...) FIG. 5A-H The flowchart illustrates a method 700 for sharing location information of a remote locator object with an entity for a duration associated with a time-limited event. Method 700 may optionally be performed at an electronic device (such as device 100, device 300, device 500), as referenced above. FIG. 6B , FIG. 6B , FIG. 6B and FIG. 6B The operations in method 700 may be optionally combined, and / or the order of some operations may be optionally changed.

[0183] As described below, method 700 provides a way to share location information of a remote locator object with an entity. This method reduces the cognitive burden on the user when interacting with the device user interface of this disclosure, thereby creating a more efficient human-machine interface. For battery-powered electronic devices, improving the efficiency of user interaction with the user interface saves power and increases the time between battery charging sessions.

[0184] In some embodiments, method 700 is performed at an electronic device (e.g., electronic device 500) that communicates with a display generating component and one or more input devices (e.g., touchscreen 504). For example, a mobile device (e.g., a tablet, smartphone, media player, or wearable device) includes wireless communication circuitry that optionally communicates with one or more of the following: a mouse (e.g., external), a touchpad (optionally integrated or external), a remote control device (e.g., external), another mobile device (e.g., separate from the electronic device), a handheld device (e.g., external), and / or a controller (e.g., external), etc. In some embodiments, the electronic device communicates with a trackable object, and the trackable object is a remote locator object having one or more wireless antennas, as discussed in more detail below. In some embodiments, the display generating component is a display integrated with the electronic device (optionally a touchscreen display), an external display such as a monitor, projector, television, or a hardware component (optionally integrated or external) for projecting a user interface or making the user interface visible to one or more users, etc.

[0185] In some implementations, a traceable object associated with an electronic device is displayed via a display generation component (e.g., FIG. 6C The user interface associated with "Frank's briefcase" (e.g., FIG. 6C When the user interface 612 is in use, the electronic device receives (702a) information via one or more input devices and tracks objects and time-limited events (e.g., such as...). FIG. 6BThe first input corresponding to the request associated with the flight indicated in the document, such as... FIG. 6BThe selection of option 613 is shown (e.g., via a tap 603 on a contact object). In some embodiments, the trackable object is a remote locator object having a battery, one or more wireless antennas, and a processor that enables the remote locator object to function as a remote locator object when associated with another physical object (e.g., a wallet, purse, backpack, suitcase, car, or a set of keys) associated with a user other than the user of the electronic device. In some embodiments, the trackable object is configured to transmit its location data to an electronic device (e.g., wirelessly, such as via Bluetooth, RF, IR, NFC, or Wi-Fi). In some embodiments, the trackable object is associated with an identifiable name or tag on an electronic device (e.g., an electronic device of a user associated with the trackable object, such as owning the trackable object). In some embodiments, the trackable object is configured to be fixed, clipped, attached, and / or coupled to a physical object belonging to or associated with the user of the electronic device (e.g., personal items such as bags, purses, luggage, keychains, suitcases, briefcases, backpacks, and / or wallets). In some implementations, when the first optional option is displayed, the user is participating in or will participate in a time-limited event. For example, a time-limited event is a travel event with a specified (e.g., predetermined) start and end (e.g., the start and end of a trip), such as a flight, bus trip, train trip, taxi trip, or other carpooling event. In some implementations, a time-limited event is associated with an entity (e.g., an organization, institution, company, or enterprise) that provides, organizes, hosts, or otherwise facilitates the time-limited event. In some implementations, the entity is a trusted entity that is a member of a network of entities through which location-sharing capabilities are permitted and / or enabled for electronic devices. In some implementations, the user interface associated with a trackable object is the user interface of an item location application. For example, an item location application is an application that displays one or more representations of one or more searchable items (including trackable objects) and / or a user, along with indications of the location of one or more searchable items and / or the user. In some implementations, a user opens an item location application to view one or more items, such as trackable objects, that the user owns or has already gained access to via invitation. In some implementations, a user selects one or more items from a list for location, and in response, the item location application optionally (e.g., on a map) displays to the user an indication of the location of the selected one or more items along with a first optional option. In some implementations, the user interface associated with the trackable object is a user interface associated with an entity linked to a time-limited event. For example, the user interface is displayed in an application owned and / or operated by the entity and is displayed and accessible via an electronic device.In some implementations, upon detection of a first input, the trackable object is pinned to (e.g., attached to) and / or associated with the personal item discussed above. In some implementations, the user interface associated with the trackable object includes a first optional option for associating the trackable object with a time-limited event. In some implementations, the first input corresponds to the selection of a first optional option. In some implementations, the first input includes, for example, a click, press, swipe, etc., detected via a touch-sensitive surface, stylus, keyboard, or mouse, pointing towards the first optional option. In some implementations, as described below, the selection of the first optional option initiates a process for sharing the location of the trackable object and thus the item (e.g., a personal item) associated with it during the duration of the time-limited event.

[0186] In some implementations, in response to receiving the first input, the electronic device initiates (702b) an action with an entity associated with a time-limited event (e.g., such as...). FIG. 6C The process by which airlines (as indicated in the document) share information corresponding to the location of trackable objects, such as displaying... FIG. 6BThe user interface 620 shown includes optional option 622a, wherein information corresponding to the location of a trackable object is shared with an entity for a corresponding duration associated with a time-limited event (e.g., a predetermined duration defined in the absence of user input). For example, the location of the trackable object is its physical location within a physical environment (e.g., the physical environment surrounding a user of an electronic device). In some embodiments, sharing information corresponding to the location of a trackable object with an entity includes enabling the entity (e.g., a user associated with the entity, such as an employee of the entity) to gain access to the location of the trackable object and thus the location of any personal items attached to it. In some embodiments, the information is shared directly by the electronic device or by a server (e.g., a wireless communication terminal) communicating with the electronic device. In some embodiments, the entity has access to the location of the trackable object for a corresponding duration associated with a time-limited event. For example, an entity has access to the location of a trackable object for the duration of a time-limited event, such as from the start to the end of the time-limited event (e.g., from the start to the end of a flight), and no longer has access to the location of the trackable object after the end of the time-limited event (e.g., no user input is required to stop such access). In some implementations, an entity begins to have access to the location of the trackable object when the user's location (e.g., the location of an electronic device) is no longer near the location of the trackable object (e.g., within a threshold distance such as 0.1m, 0.2m, 0.5m, 0.8m, 1m, 1.2m, 1.5m, 2m, 5m, 10m, 20m, or 40m), and loses access to the location of the trackable object when the user's location is within the threshold distance of the location of the trackable object. In some implementations, the duration for which an entity has access to the location of the trackable object is based on the current location of the trackable object (e.g., and optionally independent of the user's location (e.g., the location of an electronic device)). For example, an entity begins to have access to the location of a trackable object when its current location corresponds to a location associated with a time-limited event (e.g., when the trackable object is located at an airport, train station, bus station, and / or carpooling loading area), and loses access to the location of the trackable object when the location of the trackable object is near the user's location (e.g., within the threshold distance discussed above). In some implementations, as outlined above, the start time when an entity has access to the location of the trackable object is not necessarily the time when the first input is received (e.g., the start of the corresponding duration is independent of the time when the first input is received). In some implementations, when an entity has access to the location of the trackable object, the electronic device receives updates about the location of the trackable object (e.g., periodically or continuously) (e.g., because the trackable object is no longer with the user).For example, an electronic device displays an indication (e.g., a visual indication, such as a user interface element or notification) that includes updates regarding the location of a trackable object during a time-limited event (e.g., during a flight, the indication notifies the user of the trackable object and therefore that personal items have been loaded as cargo). In some embodiments, an entity has access to the location of the trackable object but not to the user's current location (and the location of the electronic device). In some embodiments, sharing access to the location of a trackable object (or a different trackable object) with an entity associated with a second (e.g., a different) time-limited event in the manner outlined above results in sharing the location of the trackable object with the entity for a duration different from the corresponding duration discussed above (e.g., because the duration of the second time-limited event differs from the time-limited event described above). Sharing access to the location of a user-owned trackable object with entities associated with time-limited events allows users to efficiently track the location of trackable objects during time-limited events without having to manually define the start and end of location sharing for different durations of time-limited events. It also provides indication of the location of the physical items to which the trackable object is attached, thereby improving user-device interaction and enabling users or authorized entities to determine the location of physical items more quickly and accurately.

[0187] In some implementations, the user interface associated with the traceable object includes a first optional option (e.g., FIG. 6A (Optional option 613) This first optional option can be selected to request that a traceable object be associated with a time-limited event (704a). In some implementations, the first input includes, for example, via, FIG. 6A The tap 603 of the contact shown selects a first optional option (704b) (e.g., as described above with reference to steps 702a-702b). Sharing access to the location of a user-owned trackable object with an entity associated with a time-limited event allows the user to efficiently track the location of the trackable object during the time-limited event without the user manually defining the start and end of location sharing for different durations of time-limited events. It also provides an indication of the location of the physical item to which the trackable object is attached, thereby improving user-device interaction and enabling the user or authorized entity to determine the location of the physical item more quickly and accurately.

[0188] In some implementations, the entity associated with a time-limited event is the organization associated with the time-limited event (e.g., such as...). FIG. 6A(The airline indicated in the document) (706) (e.g., as described above with reference to steps 702a-702b). Sharing access to the location of a user-owned trackable object with the organization associated with the time-limited event allows the user to efficiently track the location of the trackable object during the time-limited event without the user manually defining the start and end of location sharing for time-limited events of different durations, and also provides indication of the location of the physical items to which the trackable object is attached, thereby improving user-device interaction and enabling the user or authorized organization to determine the location of the physical items more quickly and accurately.

[0189] In some implementations, the user interface associated with the traceable object is a management user interface for the traceable object, such as... FIG. 6C The user interface 612 in the middle, wherein the management user interface is an item location application such as a reference FIG. 6D The user interface (708) of the described item location application. For example, the management user interface for a trackable object includes information corresponding to the trackable object, such as an identifier for the trackable object (e.g., a name, title, and / or label optionally specified by the user), the location of the trackable object (e.g., the current location or last detected location of the trackable object), and / or a graphical representation of the trackable object (e.g., an image or rendering) (e.g., displayed on a map at the location corresponding to the last detected location of the trackable object). In some embodiments, the management user interface includes one or more options for managing the trackable object, including optional options that can be selected for requesting association of the trackable object with a time-limited event, as described similarly above with reference to steps 702a-702b, optional options for causing the trackable object to emit audio, and / or optional options for initiating a pattern for locating the trackable object (e.g., as described with reference to method 900). By sharing access to the location of a trackable object owned by the user with an entity associated with a time-limited event through a user interface for trackable objects, users can efficiently track the location of trackable objects during time-limited events without having to manually define the start and end of location sharing for time-limited events of different durations. It also provides indication of the location of the physical items to which the trackable object is attached, thereby improving user-device interaction and enabling users or authorized entities to determine the location of physical items more quickly and accurately.

[0190] In some implementations, the item location application provides access to trackable objects (710) (e.g., by...). FIG. 6H Multiple trackable objects (e.g., items indicated by item 610b in the list of searchable items) FIG. 6HThe management of the searchable items (as indicated in list 608) is described. For example, as similarly described above with reference to steps 702a-702b, the item location application provides tracking of the locations of multiple trackable objects owned by the user of the electronic device or shared with the user of the electronic device. In some embodiments, the item location application is configured to display a management user interface (e.g., a management user interface such as that described above with reference to step 708) for each of the multiple trackable objects. In some embodiments, as similarly described above with reference to steps 702a-702b, the item location application is configured to display a map including multiple representations of the multiple trackable objects. For example, the electronic device displays an icon or other representation corresponding to a graphic of the searchable item at a location on the map corresponding to the location of the searchable item in the physical environment surrounding the user (and the electronic device). Sharing access to the location of a user-owned trackable object with entities associated with time-limited events allows users to efficiently track the location of trackable objects during time-limited events without having to manually define the start and end of location sharing for different durations of time-limited events. It also provides indication of the location of the physical items to which the trackable object is attached, thereby improving user-device interaction and enabling users or authorized entities to determine the location of physical items more quickly and accurately.

[0191] In some implementations, the process of initiating the sharing of information corresponding to the location of a traceable object with entities associated with a time-limited event includes (712a) displaying information corresponding to one or more corresponding future time-limited events, such as, via a display generation component. FIG. 6FThe digital boarding pass (712b) in the user interface 620 shown. For example, the electronic device displays information in the management user interface corresponding to time-limited events associated with a trackable object. In some embodiments, the information corresponding to one or more corresponding time-limited events includes one or more representations of one or more digital passes (e.g., digital tickets, digital boarding passes, digital passports, and / or digital identity cards previously stored or identified on the electronic device) used to grant a user access / entry rights to one or more corresponding time-limited events. In some embodiments, the information corresponding to one or more corresponding time-limited events includes the name / title of one or more corresponding time-limited events (e.g., flight name or flight number), the entity associated with one or more corresponding time-limited events (e.g., airline name), and / or the time associated with one or more corresponding time-limited events (e.g., flight start time and / or end time). Displaying information corresponding to a time-limited event after sharing access to the location of a user-owned trackable object with an entity associated with a time-limited event facilitates the discovery that an entity has access to the location of a trackable object and makes it easier to select a time-limited event for accessing the information corresponding to that event. This improves user-device interaction and enables users or authorized entities to determine the location of physical items more quickly and accurately.

[0192] In some implementations, after sharing information corresponding to the location of the traceable object with entities associated with time-limited events, the electronic device displays (714) an indication of the traceable object's association with a time-limited event in a management user interface via a display generation component, such as... FIG. 6FThe instruction 626 in the user interface 612 shown. For example, the electronic device displays an instruction that includes a time-limited event associated with a trackable object and / or the name or other identifying information (e.g., flight name or flight number and / or airline) of the entity associated with the time-limited event. In some embodiments, this instruction can be selected to initiate the display of real-time (e.g., live or latest) status information of the time-limited event. For example, selecting this instruction causes the electronic device to display a user interface of a virtual wallet application (e.g., described below with reference to step 720) or a user interface of an application of the entity associated with the time-limited event (e.g., described below with reference to step 718), which includes information about the status of the time-limited event (e.g., whether the flight is on time, delayed, or canceled, and / or whether there has been a gate / terminal change for the flight). This indicates that the location of a trackable object owned by a user has been shared with an entity associated with a time-limited event. This facilitates the discovery that the entity has access to the location of the trackable object and enables the user to efficiently track the location of the trackable object during the time-limited event, as well as access status updates for the time-limited event. This improves user-device interaction and allows users or authorized entities to determine the location of physical objects more quickly and accurately.

[0193] In some implementations, the user interface associated with the traceable object is a management user interface (716) for time-limited events, such as FIG. 6E The user interface 650. For example, a management user interface for time-limited events includes information corresponding to the time-limited event, such as an identifier for the time-limited event (e.g., a name or title, such as a flight name or flight number), information corresponding to the entity associated with the time-limited event (e.g., the name of the airline that provides and / or facilitates the user's participation in or will participate in the flight), and / or a representation (e.g., an image or preview) of a digital pass (e.g., a boarding pass or ticket) used for the time-limited event. In some embodiments, the management user interface includes one or more options for managing time-limited events (e.g., options for checking in / confirming participation in the time-limited event), including optional options that can be selected to request the association of a traceable object with the time-limited event, as similarly described above with reference to steps 702a-702b. By sharing access to the location of a user-owned trackable object with the entity associated with the time-limited event through a user interface for time-limited events, users can efficiently share the location of trackable objects during time-limited events without having to manually define the start and end of location sharing for time-limited events of different durations. This improves user-device interaction and enables users or authorized entities to determine the location of physical items more quickly and accurately.

[0194] In some implementations, the management user interface for time-limited events is an application associated with the entity, such as as referenced. FIG. 6D The user interface (718) of the described airline application (e.g., similarly described above with reference to steps 702a-702b). By sharing access to the location of a user-owned trackable object with the entity associated with the time-limited event via a user interface for time-limited events, the user can efficiently share the location of the trackable object during the time-limited event without having to manually define the start and end of location sharing for time-limited events of varying durations. This improves user-device interaction and enables the user or authorized entity to determine the location of physical items more quickly and accurately.

[0195] In some implementations, the management user interface for time-limited events is the user interface of a virtual wallet application configured to store digital tokens, such as... FIG. 6D The user interface 640 in the middle, these digital passes include digital passes (720) associated with time-limited events (e.g., FIG. 6D The representation of a digital boarding pass (642b) is used. For example, a virtual wallet application is configured to store digital boarding passes / tickets owned or otherwise accessible to the user, digital credit and / or debit cards, digital insurance cards, digital reward / loyalty cards, and / or digital health cards. In some embodiments, the virtual wallet application is configured to display a representation of a digital pass in a management user interface, including a representation of a digital boarding pass associated with a time-limited event (e.g., a representation of a user's upcoming flight's digital boarding pass, which can be scanned (e.g., via a code, NFC authenticator, or other image authenticator) to grant the user access to the flight). In some embodiments, the representation of a digital pass is configured for a variety of additional purposes, such as purchasing goods or items, tracking and / or storing reward points, and / or tracking and / or storing user health information. By sharing access to the location of trackable objects owned by a user with entities associated with time-limited events through the user interface of a virtual wallet application, users can efficiently share the location of trackable objects during time-limited events without having to manually define the start and end of location sharing for time-limited events of different durations. This improves user-device interaction and enables users or authorized entities to determine the location of physical items more quickly and accurately.

[0196] In some implementations, the first input includes an input (722) pointing to a system warning displayed by an electronic device via a display generation component, such as... FIG. 6DThe selection of alert 634 is shown (e.g., via a tap 603 on a contact). For example, a system alert is a notification or similar element automatically generated by the electronic device to suggest associating a traceable object (or an attached or alternative traceable object) with a time-limited event. In some embodiments, the electronic device displays the system alert on the lock screen user interface of the electronic device (e.g., if the electronic device is locked / sleep). In some embodiments, the electronic device displays the system alert in a predefined area of ​​the display generation component (e.g., in the notification center of the electronic device, optionally when the home screen user interface is displayed via the display generation component). In some embodiments, the electronic device generates and displays the system alert based on determining that a time-limited event is imminent (e.g., scheduled to occur the following day, the next week, and / or the next month) and that the user will participate in the time-limited event. For example, the user has already added or created a calendar event with a time-limited event in the electronic device's calendar application, and / or has added a digital pass for the time-limited event to the virtual wallet application described above with reference to step 720. The system alerts that generate suggestions and share access to the location of a user-owned trackable object with entities associated with time-limited events reduce the amount of input required to share access and / or enable users to efficiently share the location of trackable objects during time-limited events without requiring users to manually define the start and end of location sharing for time-limited events of varying durations. This improves user-device interaction and allows users or authorized entities to determine the location of physical items more quickly and accurately.

[0197] In some implementations, the start of a time-limited event (724), such as referenced FIG. 6D The start of the described "Flight 822" determines the start of the corresponding duration associated with a time-limited event. For example, when a time-limited event begins (e.g., based on a scheduled start time, the actual start time of the time-limited event as updated by the entity, or a predetermined amount of time (e.g., 5, 10, 15, 20, 30, 45, 60, 75, 90, or 120 minutes before the time-limited event is scheduled to begin), the entity is granted access to the location of a trackable object for tracking purposes, as similarly described above with reference to steps 702a-702b. Sharing access to the location of a user-owned trackable object with the entity associated with the time-limited event based on the start time of the time-limited event allows the user to efficiently share the location of a trackable object during the time-limited event without the user manually limiting the start of location sharing for the time-limited event, thereby improving user-device interaction and enabling the user or authorized entity to determine the location of physical items more quickly and accurately.

[0198] In some implementations, based on the current location of the electronic device, such as reference... FIG. 6A The described electronic device 500 is located at Los Angeles International Airport to determine the start of a corresponding duration associated with a time-limited event (726). For example, when the electronic device (and therefore the user) is located at a location associated with a time-limited event (e.g., a location where the time-limited event is scheduled to occur, such as the airport of the scheduled flight) or within a threshold distance of that location (e.g., 0.1m, 0.2m, 0.5m, 0.8m, 1m, 1.2m, 1.5m, 2m, 5m, 10m, 20m, 40m, 100m, 300m, 500m, or 1000m), the entity is granted access to the location of the traceable object for tracking the traceable object, as similarly described above with reference to steps 702a-702b. Based on the user's location and the shared access to the location of trackable objects by entities associated with time-limited events, users can efficiently share the location of trackable objects during time-limited events without having to manually limit the start of location sharing for time-limited events. This improves user-device interaction and enables users or authorized entities to determine the location of physical objects more quickly and accurately.

[0199] In some implementations, the tracking is based on the detection that the location of a trackable object is more than a threshold distance from the current location of the electronic device (e.g., 0.1m, 0.2m, 0.5m, 0.8m, 1m, 1.2m, 1.5m, 2m, 5m, 10m, 20m, 40m, 100m, 300m, 500m, or 1000m), as referenced. FIG. 6D The described electronic device 500 is more than a threshold distance from "Frank's suitcase" to determine the start of the corresponding duration associated with a time-limited event (728). For example, when the electronic device detects that the trackable object is no longer at or near the current location of the electronic device (and therefore the user), the entity is granted access to the location of the trackable object for tracking purposes, as similarly described above with reference to steps 702a-702b. In some implementations, the trackable object is separated from the electronic device (and the user) when the user checks in personal items attached to the trackable object to an entity (e.g., at the baggage check-in counter at the airport before the user's flight or other travel) for a time-limited event and / or checks in such personal items. Sharing access to the location of the user-owned trackable object with the entity associated with the time-limited event when the trackable object is no longer with the user allows the user to efficiently share the location of the trackable object during the time-limited event without the user manually defining the start of location sharing for the time-limited event, thereby improving user-device interaction and enabling the user or authorized entity to determine the location of physical items more quickly and accurately.

[0200] In some implementations, this is based on the expected end of a time-limited event (730), such as as referenced. FIG. 6D The termination of the described "Flight 822" determines the end of the corresponding duration associated with the time-limited event. For example, when the time-limited event ends or after a predetermined amount of time (e.g., 5 minutes, 10 minutes, 15 minutes, 20 minutes, 30 minutes, 45 minutes, 60 minutes, 75 minutes, 90 minutes, or 120 minutes) following the end of the time-limited event (e.g., based on a scheduled end time or the actual end time of the time-limited event as updated by the entity), the entity no longer has access to the location of the traceable object for tracking the traceable object, as similarly described above with reference to steps 702a-702b. In some embodiments, the end time of the time-limited event is determined to be a first end time, and the end of the corresponding duration is a second end time. In some embodiments, the end time of the time-limited event is determined to be a third end time different from the first end time, and the end of the corresponding duration is a fourth end time different from the second end time. Sharing access to the location of a trackable object owned by a user with an entity associated with a time-limited event until the end of the time-limited event allows users to efficiently share the location of a trackable object during the time-limited event without having to manually limit the start of location sharing for the time-limited event. This improves user-device interaction and enables users or authorized entities to determine the location of physical items more quickly and accurately.

[0201] In some implementations, based on the detection that the location of a trackable object is within a threshold distance (e.g., 0.1m, 0.2m, 0.5m, 0.8m, 1m, 1.2m, 1.5m, 2m, 5m, 10m, 20m, or 40m) of the current location of the electronic device 500, such as reference... FIG. 8A-FThe described electronic device 732 determines the end of a corresponding duration associated with a time-limited event by being within a threshold distance of “Frank’s briefcase.” For example, when the electronic device detects (e.g., after the time-limited event has ended (e.g., determined based on the actual or expected end time of the time-limited event) or regardless of whether the time-limited event has ended) that a traceable object is located at or near the current location of the electronic device (and therefore the user), the entity no longer has access to the location of the traceable object for tracking the traceable object, as similarly described above with reference to steps 702a-702b. In some embodiments, the threshold distance is less than, equal to, or greater than the separation distance described above with reference to step 728. In some embodiments, the traceable object re-encircles the electronic device (and the user) when the user retrieves the personal item attached to the traceable object from the entity (e.g., at baggage claim at the airport after the user’s flight) after a time-limited event. In some embodiments, the traceable object remains associated with the time-limited event associated with the entity based on a threshold distance determining that the traceable object is no longer within the current location of the electronic device. In some implementations, the electronic device determines that a time-limited event has ended based on a first location where the traceable object's location is within a threshold distance of the electronic device's current location. In some implementations, the electronic device determines that a time-limited event has not yet ended based on a second location where the traceable object's location is not within a threshold distance of the electronic device's current location. Sharing access to the location of a user-owned traceable object with the entity associated with the time-limited event until the traceable object is located with the user allows the user to efficiently share the location of the traceable object during the time-limited event without the user manually limiting the end of location sharing for the time-limited event, thereby improving user-device interaction and enabling users or authorized entities to determine the location of physical objects more quickly and accurately.

[0202] In some implementations, the current position of the trackable object is updated at a first frequency at the electronic device (734a) before the first input is received (e.g., at a first frequency). FIG. 7A-E The location of "Frank's briefcase" is updated in user interface 602. For example, before sharing the location of the trackable object with the entity, the electronic device (or a server communicating with the electronic device) tracks and updates the location of the trackable object every 5 minutes, 10 minutes, 20 minutes, 30 minutes, 45 minutes, 60 minutes, 75 minutes, 90 minutes, or 120 minutes. In some embodiments, the trackable object reports its location at a first frequency before receiving the first input. In some embodiments, information corresponding to the location of the trackable object is reported at a first frequency within the user interface of the item location application described above with reference to steps 702a-702b.

[0203] In some implementations, when sharing information corresponding to the location of a trackable object with an entity associated with a time-limited event, the current location of the trackable object is updated at an electronic device at a second frequency greater than the first frequency (734b). (e.g., at a second frequency...) FIG. 7A-E The location of "Frank's briefcase" is updated via a status indicator 628 in the user interface 612. For example, after receiving a first input and when the entity has access to the location of the trackable object, the electronic device (or a server communicating with the electronic device) tracks and updates the location of the trackable object every 30 seconds, 1 minute, 2 minutes, 3 minutes, 5 minutes, 10 minutes, 15 minutes, 20 minutes, 30 minutes, 40 minutes, or 60 minutes. In some embodiments, the trackable object updates its operation to report its location at a second frequency, so that its location can be tracked by the electronic device and / or the entity at a second frequency. In some embodiments, information corresponding to the location of the trackable object is reported at a second frequency within the user interface of an item location application discussed similarly above and / or to the entity (e.g., to an electronic device operated by a user associated with the entity). After sharing the location of a user-owned trackable object with an entity associated with a time-limited event, the location of the trackable object is tracked at a corresponding frequency. This enables the user to efficiently track the location of the trackable object during the time-limited event and provides an indication of the location of the physical item to which the trackable object is attached, thereby improving user-device interaction and enabling the user or authorized entity to determine the location of the physical item more quickly and accurately.

[0204] In some implementations, when sharing information corresponding to the location of a traceable object with an entity associated with a time-limited event, the electronic device displays (736a) information corresponding to the state of the traceable object relative to the time-limited event via a display generation component (e.g., in a user interface associated with the traceable object or on the lock screen user interface of the electronic device), such as... FIG. 1A-BThe information 630 shown includes a status indicator 628, which is determined based on: the current location of the trackable object (736b) (e.g., tracked by an electronic device and / or by an entity and / or by a server based on the object location characteristics of the trackable object, as described in more detail with reference to method 900), and tracking updates for the trackable object provided by the entity (736c) (provided to the electronic device and optionally independent of the current location information reported by the trackable object). For example, information corresponding to the status of the trackable object indicates the location of the trackable object relative to a time-limited event and / or the status of the trackable object relative to a time-limited event. As an example, if a time-limited event is a flight that a user is participating in, then when the location of the trackable object is shared with the entity, information corresponding to the status of the trackable object indicates that the status of personal items attached to the trackable object is that they are being loaded onto the aircraft as cargo (e.g., the personal items have been checked in at the baggage claim, the personal items have been processed into the baggage compartment, and / or the personal items have been transported to the aircraft for loading into cargo). In some implementations, the information includes indications of the time of status updates, such as the time personal items were checked in at the baggage claim area at the airport. In some implementations, tracking updates for trackable objects are provided periodically by the entity (e.g., based on the progress of loading personal items onto the aircraft). In some implementations, the entity provides such status information (e.g., check-in completed, baggage claim processed, or boarding information) based on the location of the trackable object corresponding to locations specified by those statuses (e.g., check-in counter location, baggage claim location, or aircraft location). Displaying status updates for trackable objects when the location of a user-owned trackable object is shared with an entity associated with a time-limited event allows users to efficiently track the location of trackable objects during time-limited events and / or reduces the amount of input required to access status updates for trackable objects, thereby improving user-device interaction and enabling users or authorized entities to determine the location of physical items more quickly and accurately.

[0205] In some implementations, the process of initiating the sharing of information corresponding to the location of a traceable object with an entity associated with a time-limited event includes initiating a process of granting the entity access to the traceable object to enable the location of one or more features of the traceable object based on signals emitted by the traceable object (738) (e.g., referenced below). FIG. 3(As described). For example, when the location of a trackable object is shared with an entity, the electronic device grants access to location reporting features, sound generation features, and / or proximity locator features of the trackable object, which enable the entity (e.g., one or more users associated with the entity) to locate the personal item to which the trackable object is attached. In some embodiments, one or more features of the trackable object that enable the location of the trackable object have one or more characteristics of one or more features of the trackable object described in reference method 900. Granting the entity access to one or more features of the trackable object owned by the user enables the person associated with the entity to efficiently track the location of the trackable object for the purpose of locating the trackable object when it is reported as lost, and / or alert the entity that the trackable object has been lost. This reduces the need for user input to manually provide object location information to the entity and also provides an indication of the retrieval status of the trackable object, thereby improving user-device interaction and reducing user concern about the location of lost trackable objects.

[0206] It should be understood that, FIG. 5A-H The specific order in which the operations described herein are presented is merely exemplary and is not intended to indicate that the described order is the only possible order in which these operations can be performed. Those skilled in the art will conceive of various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods 900 and / or 1100) are similarly applicable to the above descriptions with respect to other methods described herein (e.g., methods 900 and / or 1100). FIG. 7A-E Method 700 is described above. For example, the searchable item described with reference to method 700 above, sharing access to the location of the searchable item with an entity, displaying an item location application, displaying a user interface associated with the searchable item, and displaying a user interface associated with an entity may optionally have one or more of the following characteristics: a remote locator object described with reference to other methods described herein (e.g., methods 900 and / or 1100), sharing access to one or more features of the searchable item, displaying an item location application, displaying a user interface associated with the searchable item, displaying status updates associated with the searchable item, and displaying a user interface associated with an entity. For the sake of brevity, these details will not be repeated here.

[0207] The operations in the information processing method described above may optionally be implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (e.g., as relative to...). FIG. 1A-B , FIG. 1A-B , Reporting of lost items associated with remotely located locator objects (As described) or a dedicated chip. Additionally, see the above references. FIG. 8A-G The described operation may optionally be performed byFIG. 9A-D The components described herein are used to implement this. For example, receiving operation 702a and display operations 702a, 714, and 736a are optionally implemented by event classifier 170, event recognizer 180, and event handler 190. Event monitor 171 in event classifier 170 detects touch on touchscreen 504, and event dispatcher module 174 transmits event information to application 136-1. The corresponding event recognizer 180 of application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first touch at a first location on the touchscreen corresponds to a predefined event or sub-event, such as a selection of an object on the user interface. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates the event handler 190 associated with the detection of that event or sub-event. Event handler 190 may optionally utilize or invoke data updater 176 or object updater 177 to update the application's internal state 192. In some implementations, event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will readily understand how this can be done based on... FIG. 8A-G The components described herein are used to implement other processes.

[0208] FIG. 8A Users interact with electronic devices in a variety of different ways. In some implementations, electronic devices are capable of tracking the location of trackable objects such as remote locator objects. In some implementations, access to such remote locator objects may be shared by the owner of the remote locator object with an entity (e.g., one or more persons associated with the entity) for a duration associated with a time-limited event. The implementations described below provide ways in which electronic devices report remote locator objects as lost to entities, including providing entities with permission to access one or more lookup features of the remote locator object for locating the remote locator object, thus enhancing user interaction with the electronic device. Enhanced interaction with the device reduces the amount of time required for users to perform actions, thereby reducing the device's power consumption and extending the battery life of battery-powered devices. It should be understood that people use devices. When a person uses a device, that person may optionally be referred to as the user of the device.

[0209] FIG. 8A Exemplary methods are illustrated in which electronic devices according to some embodiments of this disclosure facilitate the reporting of items associated with remote locator objects as lost to an entity for the purpose of assisting in the retrieval of the items. The embodiments in these figures are used to illustrate the process described below, including references to... FIG. 6A-I The process described.

[0210] FIG. 8AAn example is an electronic device 500 associated with a user, which includes a touchscreen 504 that displays one or more aspects of an item associated with a remote locator object being reported as lost to an entity. FIG. 6A In this context, electronic device 500 refers to a mobile electronic device belonging to the user. Furthermore, as... FIG. 8A As shown, the electronic device 500 displays a user interface 802 for an item location application operated on the electronic device 500. In some embodiments, the user interface 802 corresponds to a previously referenced... FIG. 8A The user interface 602 is described below. It should be understood that, as described below, the location of the electronic device 500 and the location of the user of the electronic device 500 are referred to interchangeably herein.

[0211] like FIG. 6A-I As shown, in some embodiments, the user interface 802 of the item location application includes a representation of a map surrounding and / or including the location of the user and / or electronic device 500. In some embodiments, as previously referenced above... FIG. 8A-G As described, the map indicates: the location of the user and / or electronic device 500 as a circle, the location of locatable items owned by the user (e.g., personal items such as bags, suitcases, headphones, etc., which are associated with a remote locator object (e.g., the remote locator object is attached to the personal item)), such as the representation of "Frank's suitcase" on the map at the location corresponding to the location of the first locatable item "Frank's suitcase" in the physical area (icon 806), and / or the locations of additional users who share their locations with the user (e.g., Frank). FIG. 8C As shown in the example, no additional users are currently sharing their location with Frank, and therefore no additional users are displayed on user interface 802. FIG. 6A-I As shown, and as noted above, 806 indicates a corresponding searchable item (e.g., a graphic of the corresponding searchable item) so that a user (e.g., Frank) can visually identify the searchable item on a map of user interface 802.

[0212] In some implementations, the first searchable item (e.g., "Frank's suitcase") is associated with a time-limited event (e.g., a travel event) that is associated with an entity (e.g., the organizer or provider of a time-limited event), as referenced above. FIG. 8A Similarly described. In FIG. 8A In some examples, the timed event is a flight that the user is participating in or has already participated in (e.g., "Flight 822"), as shown in the example. FIG. 6A-I(as indicated in the document) (e.g., the flight is in progress, or the flight has ended and / or the user has arrived at the flight destination). Additionally, in some implementations, when the first locatable item (e.g., “Frank’s suitcase”) is associated with a time-limited event (e.g., “Flight 822”), as previously referenced... FIG. 8A As described, an entity (e.g., an airline) is granted access to the location information of a first locatable item for a corresponding duration associated with a time-limited event.

[0213] In some implementation schemes, such as FIG. 8B As shown, the user interface 802 also includes an area 812 associated with the first searchable item (e.g., "Frank's briefcase"). FIG. 8A As shown and as previously referenced above FIG. 8G As described, because the first searchable item is associated with a time-limited event, area 812 of user interface 802 includes information corresponding to the status of the first searchable item relative to the time-limited event (e.g., a flight). For example, in FIG. 8G In this context, the information, indicated by status indicator 828, indicates one or more updates during the flight for the first locatable item, such as that the locatable item was checked in at the baggage claim at 6:55 a.m., that the first locatable item was processed into the baggage hold at 7:13 a.m., that the first locatable item is expected to be processed for transport to the aircraft shortly (e.g., within the next hour, half an hour, 15 minutes, 10 minutes, or 5 minutes), and that the first locatable item has not yet been loaded onto the aircraft. In some embodiments, the information including status indicator 828 is updated by electronic device 500 based on status information received from an entity (e.g., an airline), such as... FIG. 8G As shown, the status indicator 828 for "Baggage Transportation" is from... FIG. 8G The "expected soon" message is updated to "completed at 7:35 AM," indicating that the locatable item has been processed for transport to the aircraft (and thus the first locatable item is in the process of being loaded onto the aircraft). In some embodiments, the airline provides status updates for the first locatable item to electronic device 500 based on tracking the location of the first locatable item (e.g., during the flight). In some embodiments, if multiple locatable items are concurrently associated with time-limited events (e.g., flights) discussed above, the user interface 802 will include areas for other locatable items (e.g., similar to area 812), each of which will include information corresponding to the status of each locatable item relative to the time-limited event, as similarly discussed above.

[0214] Additionally or alternatively, in some embodiments, information corresponding to the status of the first searchable item relative to a time-limited event (e.g., a flight) is provided on the lock screen user interface of the electronic device 500. For example, as FIG. 8C As shown, when the electronic device 500 is displaying a lock screen user interface 880 on the touchscreen 504, information corresponding to the status of the first searchable item is presented as a lock screen element 882 associated with a time-limited event (e.g., "Flight 882"). FIG. 8A-B As shown, the lock screen element 882 optionally includes a status indicator 884 that provides the most recent or latest status of the first searchable item relative to the flight. For example, status indicator 884 indicates that the first searchable item was successfully loaded onto the aircraft at 7:48 AM. Additionally, as... FIG. 6A-I As shown, in some embodiments, lock screen element 882 includes the status of a time-limited event (e.g., a real-time flight status defined by flight start and end times), which may optionally be provided in the form of a dynamic progress bar / bubble (e.g., the bar / bubble progresses gradually from left to right according to the flight's progress). In some embodiments, as similarly described above, the information within lock screen element 882 corresponding to the status of the first searchable item is updated by electronic device 500 based on (e.g., real-time or periodic) status information received from an entity (e.g., an airline). In some embodiments, if multiple searchable items (e.g., including the first searchable item) are concurrently associated with a time-limited event (or other time-limited events), electronic device 500 displays multiple lock screen elements (e.g., similar to lock screen element 882) associated with the time-limited event, which include... FIG. 8A The information shown is similar to the information discussed above regarding multiple searchable items.

[0215] exist FIG. 6A-I In response to, for example, pointing to FIG. 8C Upon scrolling or selecting input in area 812 of the user interface 802, the electronic device 500 displays an expanded view of area 812 associated with the first searchable item. In some embodiments, area / user interface 812 displays additional information about the first searchable item and provides management of the first searchable item. In some embodiments, area / user interface 812 corresponds to the above reference. FIG. 8C The user interface 612 described above (e.g., user interface 812 is a partial view of the user interface 612 described above, including additional elements).

[0216] In some implementation schemes, such as FIG. 8B As shown and as referenced above. FIG. 8CSimilarly described, because the first searchable item is associated with a time-limited event (e.g., a flight) discussed above, user interface 812 includes an indication 816 indicating that the first searchable item is associated with a time-limited event (e.g., "Flight 822"). Additionally, as... FIG. 8C As shown, the information, including the status indicator 828, has been optionally updated by the electronic device 500, as discussed similarly above. For example, in FIG. 8C In the middle, the status indicator 828 for "boarding the plane" is from ​ The "Pending" status in the system is updated to "Completed," indicating that the searchable item has been successfully loaded onto the aircraft.

[0217] refer to ​ There is a time-limited event that has optionally ended, and the user has attempted to retrieve the first locator item (e.g., the user has disembarked from the aircraft and gone to baggage claim to retrieve the personal item attached to the remote locator object). However, although the user interface 812 has confirmed that the first locator item has completed its journey to its destination (e.g., it has been successfully loaded onto the aircraft) (e.g., an instruction to “Complete boarding”), the user may still be unable to locate and retrieve the first locator item. For example, the first locator item (e.g., “Frank’s suitcase”) is not at the expected pick-up / retrieval location (e.g., baggage claim at the destination airport). Therefore, in such an instance, it may be desirable to provide functionality to report the first locator item as lost or omitted to the entity responsible for transporting the first locator item during the time-limited event (e.g., the flight) and unloading the first locator item when the time-limited event ends (e.g., the airline).

[0218] As mentioned earlier, the user interface 812 provides management of the first searchable item. ​ As shown, in response to a selection (e.g., tap, press, or click) or hover (e.g., tap and hold) made by pointing to the indicator 816 via a contact 803, the electronic device 500 may optionally display a menu (e.g., a pop-up menu) overlaid on or below the indicator 816 in the user interface 812. In some embodiments, such as ​ As shown, the menu includes several optional options for managing time-limited events (such as "Flight 822"). For example, in ​ The menu includes: a first option 870, which can be selected to display the flight's digital boarding pass (e.g., as previously referenced). Figures 6A to 6ISimilarly, a second option 840 can be selected to initiate a request to report the first locatable item as lost to an entity (e.g., an airline); and a third option 872 can be selected to deassociate the first locatable item with a time-limited event (e.g., revoke an entity's access to the location information of the first locatable item). Figure 8C In the context of displaying a menu in the user interface 812, the electronic device 500 detects a selection pointing to the second option 840. For example, as... Figure 8A As shown, electronic device 500 detects a tap 803 on touchscreen 504 at a location corresponding to the second option 840. In some embodiments, electronic device 500 detects clicks, taps, swipes, and / or hover inputs on touchscreen 504.

[0219] In some implementation schemes, such as Figure 8D As shown, in response to detecting a selection of the second option 840, electronic device 500 (e.g., directly or via a server (e.g., a wireless communication terminal) communicating with electronic device 500) sends a request to report the first locatable item as lost to the entity. In some embodiments, such as Figure 8D As shown, electronic device 500 sends a request to an entity via messaging user interface 842. For example, as Figure 8D As shown, electronic device 500 replaces the display of user interface 812 and displays a messaging user interface 842 for initiating a messaging session with an entity (e.g., an "airline"). In some embodiments, messaging user interface 842 is associated with a messaging application of electronic device 500. For example, Figure 8D The messaging user interface 842 is a text messaging user interface (or similar user interface) for the system messaging application of electronic device 500, through which a user can communicate with an entity (e.g., an airline) and optionally send messages to a contact phone number or email address associated with the airline (e.g., known to electronic device 500). Alternatively, in some embodiments, the messaging user interface 842 is associated with an application (e.g., an airline application) of the entity that operates on electronic device 500 (or runs in a web browsing application of electronic device 500). For example, in response to detecting a selection of optional option 840, electronic device 500 launches the airline application and displays... Figure 8B The messaging user interface 842 (e.g., a chat hotline or helpline user interface for an entity application) enables users to communicate directly with the airline.

[0220] In some implementation schemes, such as Figure 8DAs shown, when the messaging user interface 842 is displayed on the touchscreen 504, the electronic device 500 (e.g., directly or via a server (e.g., a wireless communication terminal) communicating with the electronic device 500) sends a request to report the first locatable item as lost to the entity. In some embodiments, such as Figure 8D As shown, sending a request includes sending information about the last known location of the first searchable item to the entity. For example, as... Figure 8D As shown, electronic device 500 (e.g., automatically) sends one or more messages, such as a first message 844a, via messaging user interface 842, including information corresponding to the last known location of the first searchable item. This first message includes geographic information (e.g., GPS-enabled information) of the last known location of the first searchable item, represented by an icon 846a (e.g., overlaid on a portion of a map). In some embodiments, the geographic information of the last known location of the first searchable item is obtained by electronic device 500 using the information previously referenced above. Figures 6A to 6I The described item location application is used to access and provide this information. In some implementations, the geographic information of the last known location of the first locatable item is accessed and provided by an entity (e.g., based on access rights to the location of the first locatable item shared by users). Additionally or alternatively, such as... Figure 8D As shown, information corresponding to the last known location of the first searchable item may optionally be sent via a second message 846b, which includes the address of the last known location of the first searchable item (e.g., as reported by electronic device 500 or an entity, as discussed similarly above).

[0221] In some implementations, during messaging session activities between users and entities (e.g., in display...) Figure 8D In the messaging user interface 842, the user can provide (e.g., manually, by transmitting a text message including additional information entered by the user) additional details about one or more characteristics / features of the searchable item to help the entity identify the first searchable item. For example, in Figure 8D In the process of displaying the messaging user interface 842, the electronic device 500 detects input to the text input field 848 of the messaging user interface 842 via a tap 803 on a contact on the touch screen 504.

[0222] In some implementation schemes, such as Figure 8E As shown, in response to detecting a selection of text input field 848, electronic device 500 displays a keyboard 850 including multiple selectable keys (e.g., numeric) in messaging user interface 842. For example, as Figure 8EAs shown, in the messaging user interface 842, the electronic device 500 shifts the text input field 848 upwards and displays the keyboard 850 below the text input field 848. Figure 8E In the example, a user of electronic device 500 can provide additional details about one or more characteristics / features of a first searchable item by composing a message in messaging user interface 842 (e.g., via optional keys on keyboard 850) and sending the message to the entity. Figure 8E In the messaging user interface 842, when the keyboard 850 is displayed, the electronic device 500 detects a series of one or more inputs directed to the keyboard 850 for composing a message. This message includes details about one or more characteristics / features of a first searchable item, such as the appearance of the first searchable item (e.g., color, shape, pattern, and / or size), the brand of the first searchable item, the type of the first searchable item, and / or accessories associated with the first searchable item (e.g., keychains, ornaments, ribbons, stickers, and / or tags attached to the first searchable item). Similarly, as discussed above, the electronic device 500 may optionally detect a series of one or more inputs via contact 803 on the touchscreen 504, directed to one or more keys of the keyboard 850.

[0223] In some implementations, after composing a message including additional details about one or more characteristics / features of the first searchable item, the user sends the message to the entity via a messaging user interface 842, such as Figure 8F As shown. For example, after a message has been composed, the user selects the "Send" option displayed in the messaging user interface 842 (e.g., in the text input field 848 or the keyboard 850). In some implementations, such as Figure 8F As shown, after the message is sent to an entity (e.g., an airline), the electronic device 500 displays message 844b in a messaging user interface 842. As discussed above, the content (e.g., text) in message 844b describing the visual characteristics (e.g., appearance, such as color and pattern) of the first searchable item may optionally help the airline (e.g., one or more employees of the airline) identify the searchable item for use in returning the first searchable item to the user.

[0224] In some implementations, when electronic device 500 sends a request to report a first locatable item as lost to an entity, electronic device 500 initiates a process for granting the entity access to one or more features of a trackable object associated with the lost item. For example, as discussed above, the first locatable item (e.g., “Frank’s suitcase”) includes a physical object / item (e.g., the suitcase) and a trackable object (e.g., a remote locator object) attached to (e.g., secured to, clamped to, bound to, and / or fastened to) the physical object / item. Therefore, when electronic device 500 sends a request to report the first locatable item as lost to an entity, electronic device 500 may optionally allow the airline access to one or more features of the trackable object attached to the lost item that enable the location of the lost item.

[0225] In some implementations, granting an entity access to one or more characteristics of a traceable object associated with a lost item includes sharing the location information of the traceable object with the entity. In some implementations, the entity does not have access to the location information of the traceable object when a request is sent to report a first locatable item as lost. In some implementations, the entity previously had access to the location information of the traceable object (e.g., because the traceable object was associated with a time-limited event), but the entity lost access to the location information of the traceable object because the corresponding duration associated with the time-limited event has ended (e.g., the user's flight has ended), as previously referenced above. Figures 6A to 6I As described. In some implementations, when electronic device 500 grants an entity access to the location information of a trackable object, the entity (e.g., one or more employees of an airline) is able to track the location of the trackable object (e.g., using a second electronic device) for the purpose of locating and retrieving lost items.

[0226] In some implementations, granting an entity access to one or more features of a trackable object associated with a lost item includes enabling the entity (e.g., one or more users associated with the entity) to access a sound generation feature of the trackable object. In some implementations, the sound generation feature initiates a process for causing the trackable object to output audio. For example, when an employee or other user associated with an airline utilizes the sound generation feature, the trackable object outputs a ringing, melody, chime, song, or other sound via its speaker, enabling the employee or other user to locate the trackable object to retrieve the lost item.

[0227] In some implementations, granting an entity permission to access one or more features of a trackable object associated with a lost item includes enabling the entity (e.g., one or more users associated with the entity) to access proximity location features of the trackable object. In some implementations, based on determining that the location of the trackable object and the locations of one or more second electronic devices (e.g., devices associated with one or more users associated with the entity) are within a threshold distance (e.g., 1m, 2m, 5m, 10m, 15m, 20m, 40m, 50m, 100m, or 200m) from each other, proximity location features make the location of the trackable object visible to one or more second electronic devices. In some implementations, when the second electronic device is within the threshold distance of the trackable object, the second electronic device displays (e.g., via a display generation component of the second electronic device) a visual indication (e.g., an arrow) configured to point in a direction relative to the location of the trackable object relative to the second electronic device. For example, when proximity location features are enabled, a user of the second electronic device can travel in the direction indicated by the visual indication to locate and retrieve the first trackable item.

[0228] In some implementations, entities can provide updates on the status of locating and / or retrieving a first locable item via a messaging session between the user and the entity. For example, the entity (e.g., a person associated with the entity) via... Figures 8D to 8F The messaging user interface 842 provides updates in the form of one or more messages (e.g., similar to messages 846 / 844). In some embodiments, the updates include an indication of whether a locatable item has been located, an indication of the location of the locatable item, an indication of an estimated time for returning the locatable item to the user, and other indications related to the status of locating and / or retrieving the first locatable item. In some embodiments, after the entity locates and retrieves the item, the electronic device 500 (or a server communicating with the electronic device 500) revokes access to one or more features of the trackable object as described above. In some embodiments, access to one or more features of the trackable object is revoked from the entity after a predetermined amount of time (e.g., 5 minutes, 10 minutes, 15 minutes, 20 minutes, 30 minutes, 45 minutes, 60 minutes, 75 minutes, 90 minutes, 120 minutes, or 180 minutes) has elapsed after the entity locates and retrieves the item.

[0229] Figures 9A to 9D These are examples of some embodiments according to this disclosure (such as in...). Figures 8A to 8G The flowchart illustrates a method 900 that facilitates the reporting of items associated with remote locator objects as lost to an entity for the purpose of assisting in the retrieval of the items. Method 900 may optionally be performed at an electronic device (such as device 100, device 300, device 500), as referenced above. Figures 1A to 1B , Figures 2 to 3 , Figures 4A to 4B and Figures 5A to 5H The operations in method 900 may be optionally combined, and / or the order of some operations may be optionally changed.

[0230] As described below, method 900 provides a way to report an item as lost to an entity. This method reduces the cognitive burden on the user when interacting with the device user interface of this disclosure, thereby creating a more efficient human-computer interface. For battery-powered electronic devices, improving the efficiency of user interaction with the user interface saves power and increases the time between battery charging.

[0231] In some embodiments, method 900 is performed at an electronic device (e.g., electronic device 500) communicating with a display generating component (e.g., touchscreen display 504) and one or more input devices. For example, the electronic device is a mobile device (e.g., tablet device, smartphone, media player, or wearable device) including a touchscreen and wireless communication circuitry, or a computer including one or more of a keyboard, mouse, and touchpad, as well as a touchscreen and wireless communication circuitry. In some embodiments, the electronic device communicates with a traceable object, and the traceable object has one or more characteristics of the traceable object in method 700. In some embodiments, the display generating component has one or more characteristics of the display generating component in method 700. In some embodiments, one or more input devices have one or more characteristics of the one or more input devices in method 700.

[0232] In some implementations, the display shows traceable objects associated with the electronic device (e.g., such as...). Figure 8A The user interface associated with the “Frank’s briefcase” indicated in the document (e.g., Figure 8C When the electronic device detects (902a) a first input (e.g., via a pointer) in the user interface 812, the electronic device detects (902a) a first input via one or more input devices. Figure 8C In option 840, the touch of the contact object (803) corresponds to the first input to an entity (e.g., an organization or enterprise, as described similarly in reference method 700) such as reference Figure 8AThe described airline reports a request for the loss of an item (e.g., a physical object) associated with a trackable object. In some embodiments, the user interface is an item search user interface as described similarly to reference method 700. In some embodiments, the user interface is a user interface of an application associated with an entity, as described similarly to reference method 700. In some embodiments, the trackable object is associated with an item (e.g., attached to an item), such as a bag, backpack, suitcase, purse, wallet, or other personal item attached to a user belonging to an electronic device (e.g., and optionally the owner of the trackable object) or otherwise associated with that user. In some embodiments, the user provides the first input at the time of and / or after a time-limited event (e.g., a travel event), as described in reference method 700, upon the completion of the event. For example, at the time of and / or after the completion of a time-limited event (e.g., at the end of a flight, train journey, bus journey, or taxi journey), the user of the electronic device (e.g., and the owner of the item) finds that the item cannot be found (e.g., the item is not in the luggage compartment where it should have been). Additionally or alternatively, the user of the electronic device may optionally discover that an item has been lost based on the location of a trackable object (e.g., accessible to the user via an item search user interface as discussed above). For example, the electronic device indicates in the item search user interface that the trackable object, and therefore the item, is located at a location different from the user's current and / or expected location (e.g., and optionally, a location inaccessible to the user). In some embodiments, the item (and the trackable object attached to the item) is lost when the item is being looked after by an entity. For example, the item is lost and / or goes missing during a time-limited event in which the entity is responsible. In some embodiments, the first input includes selection of an optional option for reporting the item as lost to the entity, wherein the optional option is displayed in a user interface associated with the trackable object. For example, the first input includes, for example, a click, press, swipe, etc., detected by a touch-sensitive surface, stylus, keyboard, or mouse, pointing to an optional option. In some embodiments, the first input has one or more characteristics of the input described in reference method 700.

[0233] In some implementations, in response to the detection of a first input (902b), the electronic device initiates (902c) actions to (e.g., from the electronic device or from a server communicating with the electronic device (e.g., a wireless communication terminal)) transmit first information about the item (e.g., information describing the physical appearance or state of the item or information describing the item's most recent state, such as the last known location or the last detected location), such as... Figure 8DThe process of sending information in message 846 to an entity. For example, an electronic device displays an asynchronous messaging user interface in a user interface associated with a trackable object for communicating with the entity (e.g., via text-based messaging). In some embodiments, the request is processed as a message in the messaging user interface. In some embodiments, in addition to or as part of a message, the electronic device sends details of the item to the entity. For example, the first information includes details about the item's appearance (e.g., shape, color, and / or style), the item's dimensions, the item's brand, and / or the item's contents (if applicable). In some embodiments, the first information includes details about the last known location of the trackable object (e.g., known by the electronic device via an item locator application and / or known by the user of the electronic device from memory). In some embodiments, the first information helps enable the entity (e.g., a person associated with the entity) to locate and / or identify the item. In some embodiments, the first information is provided manually by the user of the electronic device (e.g., the user fills in / types details corresponding to one or more characteristics of the lost item via the messaging user interface). In some embodiments, the first information is previously provided by the user and stored in memory before the first input is detected, and the first information is sent to the entity without the user providing the first information with the request. For example, when an item is first configured (e.g., by user operation and setup) with its associated trackable object, the user provides details corresponding to one or more characteristics of the item.

[0234] In some implementations, the electronic device initiates (902d) a process of granting an entity permission to access one or more characteristics of a trackable object, which enable the tracking object to be located based on signals sent by the trackable object (e.g., sent to one or more nearby electronic devices used to locate the trackable object, or to one or more nearby electronic devices reporting information to a location server that provides information about the trackable object's most recently detected location to the one or more nearby electronic devices used to locate the trackable object), as referenced. Figure 8FSimilarly, in some implementations, when a user reports an item as lost in the manner discussed above, the entity optionally already has access to the location of the trackable object. In some implementations, when a user reports an item as lost, the entity does not yet have access to the location of the trackable object. In some implementations, if the entity has lost access to the location of the trackable object (e.g., for one of the reasons provided in reference method 700), the entity is again granted permission to access the location of the trackable object for locating the trackable object. In some implementations, the entity has access to the location of the trackable object before the first input is detected, but does not have access to one or more features of the trackable object used for locating the trackable object. In some implementations, granting the entity permission to access one or more features of the trackable object includes allowing the entity (e.g., one or more persons associated with the entity) to cause the trackable object to emit sound (e.g., a bell, chime, or other audible sound) for locating the trackable object. In some implementations, granting an entity permission to access one or more features of a traceable object includes allowing the entity (e.g., one or more persons associated with the entity) to disable the traceable object (e.g., if the traceable object cannot be located). In some implementations, granting an entity permission to access one or more features of a traceable object has one or more location-sharing characteristics as described in reference method 700. In some implementations, when an entity (e.g., one or more persons associated with the entity) successfully locates the traceable object and retrieves the item for return to the user, the electronic device revokes the entity's permission to access one or more features of the traceable object. For example, the revocation may be performed automatically by the electronic device or in response to user input when the user receives an indication that the item has been found (e.g., a notification and / or message). In some implementations, when an entity (e.g., one or more persons associated with the entity) cannot locate the traceable object (and therefore the item), the electronic device revokes the entity's permission to access one or more features of the traceable object. For example, the revocation may be performed automatically by the electronic device or in response to user input when the user receives an indication that the lost item cannot be found (e.g., a notification and / or message). When a user reports a trackable object as lost, the entity is granted access to one or more features of the trackable object, alerting the entity that the trackable object has been lost and enabling personnel associated with the entity to efficiently track the location of the trackable object for retrieval purposes. This reduces the need for user input to manually provide object location information to the entity and also provides an indication of the trackable object's retrieval status, thereby improving user-device interaction.

[0235] In some implementations, the user interface associated with the traceable object is a management user interface for the traceable object, such as... Figure 8C The user interface 812 in the middle, wherein the management user interface is an item location application such as a reference Figure 8A The described user interface (904) for the item location application. For example, the management user interface for a trackable object includes information corresponding to the trackable object, such as an identifier for the trackable object (e.g., a name, title, and / or label optionally specified by the user), the location of the trackable object (e.g., the current location or last detected location of the trackable object), and / or a graphical representation of the trackable object (e.g., an image or rendering). In some embodiments, the management user interface includes one or more options for managing the trackable object, including optional options that can be selected to request that an item associated with the trackable object be reported as lost to an entity, as similarly described above with reference to steps 902a-902d. In some embodiments, the first input includes a selection of optional options displayed in the management user interface. In some embodiments, the management user interface for the trackable object has one or more characteristics of the management user interface described with reference to method 700. When a user-owned trackable object is reported as lost, the entity is granted access to one or more features of the trackable object via the management user interface for the trackable object. This alerts the entity that the trackable object has been lost and enables personnel associated with the entity to efficiently track the location of the trackable object for locating it. This reduces the need for user input to manually provide object location information to the entity and also provides an indication of the trackable object's retrieval status, thereby improving user-device interaction.

[0236] In some implementations, the electronic device (e.g., automatically) selects the entity (906a) based on the determination that the traceable object was previously associated with a time-limited event associated with the entity (e.g., a user-involved travel event and / or a travel event in which information such as a digital pass is stored on the electronic device and / or the electronic device previously received input that associates the traceable object with a time-limited event, such as that described in reference method 700). (e.g., no user input specifying the entity is required.)

[0237] In some implementations, associating a traceable object with a time-limited event associated with the entity includes sharing information corresponding to the location of the traceable object with the entity for the corresponding duration associated with the time-limited event (906b), as referenced. Figure 8ASimilarly, for example, access to the location information of a traceable object has been shared with the entity, allowing the traceable object to be tracked by an electronic device associated with the entity. In some embodiments, associating a traceable object with a time-limited event has one or more characteristics of associating the traceable object with a time-limited event in method 700. In some embodiments, if the traceable object has not previously been associated with a time-limited event associated with an entity, the electronic device provides a user interface for manually selecting an entity from a list of entities. Granting the entity access to one or more characteristics of the traceable object when a user-owned traceable object previously associated with a time-limited event is reported as lost alerts the entity that the traceable object has been lost and enables personnel associated with the entity to efficiently track the location of the traceable object for locating the object. This reduces the need for user input to manually provide object location information to the entity, and consequently reduces the need for user input to specify the entity, thereby improving user-device interaction.

[0238] In some implementations, time-limited events include aircraft flights (908) (e.g., as described above with reference to steps 902a-902d), such as Figure 8C The instruction 816 in the document refers to "Flight 822". When a user-owned trackable object is reported as lost, the entity is granted access to one or more characteristics of the trackable object, alerting the entity that the trackable object has been lost during the flight, and enabling personnel associated with the entity to efficiently track the location of the trackable object for locating it. This reduces the need for user input to manually provide object location information to the entity, and also provides an indication of the retrieval status of the trackable object, thereby improving user-device interaction.

[0239] In some implementations, the process of initiating the sending of initial information about an item to an entity includes (910a) displaying (910b) one or more options (such as in display generation components) for providing the entity with additional information about the item that differs from the initial information, such as in Figure 8EA keyboard 850 is displayed in the messaging user interface 842. For example, one or more options enable a user to specify additional details about the lost item—separate from the traceable object optionally attached to the item—to assist an entity (e.g., one or more persons associated with the entity) in identifying and / or locating the lost item to which the traceable object is attached. In some embodiments, as similarly described above with reference to steps 902a-902d, the additional information about the item includes information about the item's appearance (e.g., color, shape, pattern, and / or size), the item's brand, the item's style, and / or the item's embellishments (e.g., keychains, ribbons, ornaments, and / or other attachments). In some embodiments, one or more options are provided via a messaging user interface with the entity, as described in more detail below with reference to step 912. For example, the additional information is provided via text in a message sent to the entity through the messaging user interface. When a user-owned trackable object is reported as lost, it enables entities to provide additional information about the items to which the trackable object is attached, helping those associated with the entity to efficiently locate and identify the items when locating the trackable object, thereby improving user-device interaction.

[0240] In some implementations, the process of initiating the sending of first information about an item to an entity includes initiating a (optionally asynchronous) messaging session with the entity, wherein the first information is sent in the form of one or more messages (e.g., messages including text), such as... Figures 8D to 8F The messages are displayed in the form of 846 and 844 (912). In some embodiments, a messaging session with the entity is initiated via a messaging application on the electronic device (e.g., a system messaging application or another messaging application operating on the electronic device). For example, one or more messages are sent via the messaging session to the entity's contact phone number or email address. In some embodiments, a messaging session with the entity is initiated via an application associated with the entity operating on the electronic device (e.g., an airline application). In some embodiments, one or more messages include images, videos, or other content corresponding to initial information about the item. Granting the entity access to one or more characteristics of the trackable object when a user-owned trackable object is reported lost via the messaging session alerts the entity that the trackable object has been lost and enables personnel associated with the entity to efficiently track the location of the trackable object for locating the trackable object, thereby improving user-device interaction.

[0241] In some implementations, initiating a messaging session with an entity includes displaying a messaging user interface (914) associated with the entity via a display generation component, such as... Figures 8D to 8FThe messaging user interface 842 is used. For example, a representation of one or more messages is displayed in the messaging user interface. In some embodiments, the messaging user interface is displayed in the messaging application discussed above with reference to step 912. In some embodiments, the messaging user interface is displayed in an application associated with an entity, as discussed above with reference to step 912. For example, the messaging user interface is a chat hotline or helpline user interface for direct communication with an entity within an application associated with an entity. In some embodiments, the messaging user interface is the user interface of a messaging application through which messaging conversations with non-entities (e.g., contacts of the user of an electronic device) are also conducted. Granting an entity access to one or more characteristics of the traceable object when a user-owned traceable object is reported lost via a messaging session alerts the entity that the traceable object has been lost and enables personnel associated with the entity to efficiently track the location of the traceable object for locating the traceable object, thereby improving user-device interaction.

[0242] In some implementations, the first information about the item includes location information (916) indicating the last detected (e.g., known) location of the item (e.g., such as...). Figure 8D (As indicated in messages 844a and 846b). For example, an electronic device sends geographic information (e.g., GPS information) of the last detected location of an item (e.g., a specific trackable location) to an entity. In some embodiments, the location information indicating the last detected location of an item includes the address of the last detected location of the item (e.g., a specific trackable object). In some embodiments, the location information indicating the last detected location of an item is not manually generated or provided by a user. For example, the electronic device (or a server communicating with the electronic device) automatically provides and sends the information to the entity. Providing information indicating the last detected location of the item to which the trackable object is attached when a user-owned trackable object is reported lost enables personnel associated with the entity to efficiently track the location of the trackable object for locating the trackable object, reducing the need for user input for manually providing object location information, thereby improving user-device interaction.

[0243] In some implementations, the last detected location of the item is determined by a corresponding electronic device (optionally the same as or different from the electronic device) within a threshold distance of the trackable object (e.g., within 0.1m, 0.2m, 0.5m, 0.8m, 1m, 1.2m, 1.5m, 2m, 5m, 10m, 20m, or 40m, or within the range of wireless communication such as WiFi or Bluetooth, wherein the corresponding electronic device can communicate directly with the trackable object) (918). For example, the corresponding electronic device is within a threshold distance of the trackable object within a threshold distance of the trackable object (e.g., within 0.1m, 0.2m, 0.5m, 0.8m, 1m, 1.2m, 1.5m, 2m, 5m, 10m, 20m, or 40m, or within the range of wireless communication such as WiFi or Bluetooth, wherein the corresponding electronic device can communicate directly with the trackable object) (918). Figure 8FThe location indicated by icon 846a in message 844a is within a threshold distance. For example, the corresponding electronic device is operated by a user associated with the entity (e.g., an airline agent or staff member) who is different from the user of the electronic device. In some embodiments, the corresponding electronic device is another electronic device owned and / or used by the user of the electronic device (e.g., configured with the same user account as the electronic device). Providing information indicating the last detected location of the item to which the trackable object is attached when a user-owned trackable object is reported lost enables the person associated with the entity to efficiently track the location of the trackable object for locating the trackable object. This reduces the need for user input for manually providing object location information, thereby improving user-device interaction.

[0244] In some implementations, the entity is an organization (920) (e.g., as described above with reference to steps 902a-902d), such as referenced Figure 8A The described airline grants the organization access to one or more characteristics of a trackable object when a user reports it as lost, alerting the organization that the trackable object has been lost and enabling personnel associated with the organization to efficiently track the location of the trackable object for retrieval purposes. This reduces the need for user input to manually provide object location information to the organization and also provides an indication of the trackable object's retrieval status, thereby improving user-device interaction.

[0245] In some implementations, one or more features of a trackable object that enable the location of the trackable object include a location reporting feature that allows the trackable object to be located by a second electronic device associated with a user associated with the entity, such as a reference device. Figure 8FThe tracking of an electronic device by an airline employee is similarly described (922). For example, as described above with reference to steps 902a-902d, when the electronic device sends a request to report an item as lost to the entity, the location information of the trackable object is not (or is no longer) shared with the entity (e.g., the trackable object is no longer associated with the time-limited event (e.g., flight) at the time the item was lost / misplaced). In some embodiments, the location reporting feature enables the entity to gain or regain access to the location of the trackable object, allowing the trackable object to be located / tracked by a second electronic device (e.g., an electronic device operated by a user (e.g., an employee) (e.g., an airline agent or staff member) associated with the entity). In some embodiments, the entity has access to the location of the trackable object until the lost item is retrieved and returned to the user. For example, access is automatically revoked based on the location information of the trackable object (e.g., when the trackable object is reunited with the user), and / or manually revoked by the user (e.g., via a management user interface for the trackable object). In some embodiments, sharing the location of the trackable object with the entity has one or more of the object location sharing features of method 700. When a user reports a trackable object as lost, the entity is granted access to the location reporting characteristics of the trackable object. This alerts the entity that the trackable object has been lost and enables personnel associated with the entity to efficiently track the location of the trackable object for retrieval purposes. This reduces the need for user input to manually provide object location information to the entity and also provides an indication of the trackable object's retrieval status, thereby improving user-device interaction.

[0246] In some implementations, one or more features of the trackable object that enable the location of the trackable object include a sound generation feature that initiates a process (924) for causing the trackable object to output audio, as referenced. Figure 8FSimilarly, the sound generation feature enables a second electronic device (different from the electronic device) operated by a user associated with the entity to communicate with the trackable object, and allows the trackable object to optionally generate sound via a management user interface for the trackable object (e.g., outputting audio, such as a ringing, chime, or other audio, via a speaker communicating with a remote locator object). In some embodiments, enabling the trackable object to generate sound allows a user associated with the entity to locate and / or retrieve a lost item attached to the trackable object. In some embodiments, the trackable object generates sound a predetermined number of times, for a predetermined duration, and / or at a predetermined volume. For example, the trackable object generates a ringing or chime once at a corresponding volume and for a duration of 0.5 seconds, 0.75 seconds, 1 second, 1.5 seconds, 2 seconds, 3 seconds, 4 seconds, 5 seconds, 15 seconds, 30 seconds, 60 seconds, or 120 seconds. When a user reports a trackable object as lost, the entity is granted access to the sound generation characteristics of the trackable object, alerting the entity that the trackable object has been lost and enabling personnel associated with the entity to efficiently track the location of the trackable object for locating it. This reduces the need for user input to manually provide object location information to the entity and also provides an indication of the trackable object's retrieval status, thereby improving user-device interaction.

[0247] In some implementations, one or more features of the trackable object that enable the location of the trackable object include a proximity lookup feature, by which the trackable object can be located by a second electronic device associated with a user associated with the entity based on determining that the location of the trackable object and the location of the second electronic device are within a threshold distance (e.g., 0.1m, 0.2m, 0.5m, 0.8m, 1m, 1.2m, 1.5m, 2m, 5m, 10m, 20m, or 40m) from each other, such as a second electronic device associated with an airline employee being within the threshold distance of the trackable object (926), as referenced. Figure 8EAs described. In some embodiments, upon approaching a feature-finding activity, the second electronic device displays a first visual indicator (e.g., an arrow) indicating the direction in which the trackable object is positioned relative to the second electronic device (e.g., displaying an arrow pointing in the direction in which the trackable object is determined to be positioned relative to the second electronic device). In some embodiments, a second indicator (e.g., a dot) corresponding to a forward direction (e.g., relative to the front of the second electronic device) is displayed. In some embodiments, a first indicator (e.g., an arrow) corresponding to the direction of the trackable object (e.g., relative to the center of the display) is displayed. In some embodiments, the arrow points from the center of the display to the second indicator (e.g., thus pointing to the trackable object). In some embodiments, an arc is displayed between the first and second indicators to indicate to the user the direction in which to rotate the device to align the trackable object with the front of the device (e.g., rotating the device along the direction of the arc to align the first and second indicators). In some implementations, when the first visual indicator is displayed, if the second electronic device (e.g., using one or more sensors, such as an accelerometer, gyroscope, or GPS sensor) detects a change in the orientation of the electronic device (e.g., detecting rotation of the device toward or away from the remote locator object), the second electronic device alters the appearance of the first visual indicator (e.g., rotates the arrow) to indicate the orientation of the trackable object relative to the second electronic device (e.g., updating the display to reflect the change in orientation of the trackable object relative to the device as the device rotates toward or away from the trackable object). For example, when the device rotates toward the trackable object (e.g., the front of the device rotates toward the trackable object), the arrow rotates to point to the top of the device (e.g., depending on the position of the trackable object), and / or the first indicator moves toward the first indicator (e.g., depending on the position of the trackable object). Therefore, the arrow and / or the first indicator are "live-timed" to point to the trackable object. When a user reports a trackable object as lost, the entity is granted access to the object's proximity lookup features, alerting the entity that the trackable object has been lost and enabling personnel associated with the entity to efficiently track the object's location for retrieval purposes. This reduces the need for user input to manually provide object location information to the entity and also provides an indication of the trackable object's retrieval status, thereby improving user-device interaction.

[0248] In some implementations, when displaying a user interface associated with a traceable object linked to an electronic device, the electronic device detects a second input via one or more input devices. This second input corresponds to a request to an entity (e.g., an organization or enterprise, such as those discussed above, as similarly described in reference method 700) to report the loss of an item (e.g., a physical object, such as an item discussed above) associated with the traceable object. Figure 10B The selection of the second option 1013b. In some implementations, the second input has one or more characteristics of the first input as discussed above.

[0249] In some implementations, in response to the detection of a second input, the entity is configured to access one or more first features and one or more second features associated with the traceable object (e.g., the entity corresponds to, as referenced in [reference]). Figures 10C to 10D The described integrated entity), the electronic device initiates a process for sending first information about the item to the entity, and initiates a process for granting the entity access to one or more characteristics of the trackable object (e.g., one or more first characteristics and one or more second characteristics discussed in reference method 1100), the one or more characteristics being used to enable the location of the trackable object based on signals emitted by the trackable object, as described in reference... Figures 10E to 10J Similarly, as described above. In some embodiments, the electronic device initiates a process for sending first information about the item to the entity and a process for granting the entity access to one or more features as part of an item location reporting process. For example, the electronic device initiates an item location reporting process if the entity is configured and / or able to access one or more features of a trackable object. In some embodiments, as discussed with reference to method 1100, the entity's ability to access one or more features of a trackable object is based on the configuration of the electronic device or other computer system associated with the entity, and / or the compatibility of the electronic device or other computer system associated with the entity with one or more features of the trackable object, such as the features previously discussed above. In some embodiments, the entity's ability to access one or more features of a trackable object is based on operability authorization (e.g., whether the entity is a known or trusted entity to the electronic device, such as based on user preferences, user activity, and / or other permissions). In some embodiments, the process for initiating the sending of first information about the item to the entity and the process for granting the entity access to one or more first features and one or more second features associated with the trackable object are similarly performed in response to the detection of the first input described above.

[0250] In some implementations, based on the determination that the entity is not configured to access one or more first characteristics and one or more second characteristics associated with a traceable object (e.g., the entity corresponds to, as referenced...), Figure 10C and Figures 10K to 10L The described non-integrated entity), electronic devices provide access to links (e.g., web-based links that can be selected to initiate the display of a website), such as in... Figure 10PThe link represented at position 1075, when shared with an entity, enables the entity to access one or more first features of one or more features of a traceable object (e.g., information corresponding to the location of the traceable object) for locating the traceable object, but does not enable the entity to access one or more second features associated with the traceable object other than the one or more first features for locating the traceable object (e.g., as described similarly in reference method 1100), as in reference Figure 10T Webpage 1088 similarly describes this. In some implementations, when the electronic device generates a link that enables an entity to access one or more first features associated with a trackable object, the electronic device displays a visual indication of the link. For example, the electronic device displays all or part of the link, the image associated with the link, and / or the hyperlink associated with the link in the user interface discussed above or in a different user interface (e.g., a user interface specifically designed to generate the link and / or a user interface of a web browsing application), as described in method 1100. Generating a link that enables an entity to access the location of the trackable object when a user-owned trackable object is reported lost alerts the entity that the trackable object has been lost and enables the person associated with the entity to efficiently track the location of the trackable object for locating the trackable object. This reduces the need for user input to manually provide object location information to the entity and also provides an indication of the retrieval status of the trackable object, thereby improving user privacy and user-device interaction and reducing user concern about the location of the lost trackable object.

[0251] In some implementations, the user interface associated with a traceable object linked to an electronic device includes one or more visual representations corresponding to one or more corresponding entities, such as references. Figure 10CThe described multiple representations. In some embodiments, as described above, the first input includes the selection of an optional option for reporting an item as lost to an entity, wherein the optional option is displayed in a user interface associated with the trackable object. In some embodiments, when the electronic device detects the selection of an optional option for reporting an item as lost to an entity, the electronic device displays one or more visual representations in the user interface corresponding to one or more corresponding entities to which the electronic device can report the item as lost. In some embodiments, one or more visual representations can be selected to initiate the process discussed above for locating a lost item. In some embodiments, the first input includes selecting a first visual representation corresponding to the aforementioned entity. In some embodiments, one or more visual representations include the name of the corresponding entity, an image associated with the corresponding entity (e.g., a picture, photograph, cartoon, sketch, or logo of the entity), and / or an indication of whether the corresponding entity is configured to access one or more features of the trackable object, as discussed below.

[0252] In some implementations, depending on the entity being identified as being configured to access one or more first features and one or more second features associated with a traceable object, the one or more visual representations include a first visual representation corresponding to the entity displayed in one or more first visual characteristics, such as... Figure 10C The representation shown is 1021a. For example, the first visual representation corresponding to an entity discussed above includes an indication that the entity is configured to access one or more first features and one or more second features of a trackable object. In some embodiments, displaying the first visual representation with one or more first visual characteristics includes displaying textual indications that the entity is configured to access one or more features of a trackable object (e.g., displaying the first visual representation as a first label and / or in a first area of ​​the user interface). In some embodiments, displaying the first visual representation with one or more first visual characteristics includes displaying the first visual representation with a first visual appearance (e.g., one or more first colors, first visual patterns, first brightness levels, first highlight / shadow characteristics, and / or first semi-transparency levels). In some embodiments, based on determining that multiple entities are configured to access one or more first features and one or more second features associated with a trackable object, the user interface associated with the trackable object includes multiple visual representations corresponding to multiple entities displayed with one or more first visual characteristics discussed above.

[0253] In some implementations, based on the determination that the entity is not configured to access one or more first features and one or more second features associated with a traceable object, a first visual indication corresponding to the entity is displayed in one or more second visual features different from the one or more first visual features, such as... Figure 10CRepresentation 1023a in the text. For example, the first visual representation corresponding to an entity discussed above includes an indication that the entity is not configured to access one or more features of the trackable object. In some embodiments, displaying the first visual representation with one or more second visual characteristics includes displaying textual indications that the entity is not configured to access one or more features of the trackable object (e.g., displaying the first visual representation as a second label and / or in a second area of ​​the user interface). In some embodiments, displaying the first visual representation with one or more second visual characteristics includes displaying the first visual representation with a second visual appearance different from the first visual appearance (e.g., one or more second colors, second visual patterns, second brightness levels, second highlight / shadow characteristics, and / or second semi-transparency levels, which may optionally differ from those discussed above). In some embodiments, based on the determination that multiple entities are not configured to access one or more first features and one or more second features associated with the trackable object, the user interface associated with the trackable object includes multiple visual representations corresponding to multiple entities displayed with one or more second visual characteristics discussed above. When an entity reports a traceable object as lost, a visual representation corresponding to the entity is displayed based on visual characteristics of whether the entity is configured to access one or more features of the traceable object. This facilitates the user's discovery of whether the entity is configured to access one or more features, which helps inform the user's decision-making when a traceable object is reported as lost, thereby improving user-device interaction.

[0254] In some implementations, the user interface associated with the traceable object is the management user interface for the traceable object of a first application (e.g., an item location application discussed similarly to reference method 700), such as... Figure 10B The user interface 1012 in the example includes, for instance, management user interface for a traceable object, information corresponding to the traceable object, such as an identifier for the traceable object (e.g., a name, title, and / or label optionally specified by the user), the location of the traceable object (e.g., the current location or last detected location of the traceable object), and / or a graphical representation of the traceable object (e.g., an image or rendering) (e.g., displayed on a map at the location corresponding to the last detected location of the traceable object). In some embodiments, the management user interface includes one or more options for managing the traceable object, as similarly discussed with reference to method 700.

[0255] In some implementations, the process of initiating the sending of first information about an item to an entity includes displaying a second user interface, different from the user interface associated with the trackable object, via a display generation component, specifying the first information through a second application (e.g., an application associated with the entity). Figure 10EUser interface 1042. For example, if an entity is configured to access one or more characteristics of a trackable object, the electronic device replaces the display of the user interface (e.g., management user interface) associated with the trackable object with a second user interface associated with the entity's application. In some embodiments, the second user interface is the user interface of the application associated with the entity, as similarly discussed in method 700. In some embodiments, the second user interface includes one or more user interface elements that specify first information to be sent to the entity to assist in locating the item. For example, the second user interface includes text input fields, optional options, drop-down menus, and / or toggle keys / slides that enable the user of the electronic device to input and / or select information about the item, such as the information described above. In some embodiments, the item location application to which the user interface associated with the trackable object belongs is also associated with multiple entities (e.g., including the entities discussed above). In some such embodiments, the application to which the second user interface discussed above belongs is an application associated with one of the multiple entities and not with the other entities in the multiple entities. For example, the entities in the multiple entities are associated with multiple separate (e.g., unique) applications. When a user-owned trackable object is reported as lost, it enables the entity to specify information about the item to which the trackable object is attached via an application associated with the entity. This helps the person associated with the entity to efficiently locate and identify the item when locating the trackable object, thereby improving user-device interaction.

[0256] In some implementations, the process of sending first information about an item to an entity includes sending second information that enables the entity to associate the traceable object with an item identifier known to the entity, such as... Figure 10GThe first representation is associated with the baggage ID indicated in 1050a. For example, when an item is reported lost to an entity, the entity has previously generated an item identifier for the item. As an example, if an item is lost during a flight, as discussed similarly above, the entity (e.g., the airline) has already generated a baggage identification number for the item (e.g., a baggage identification number or code attached to the item when it is checked in for that flight, as discussed similarly in reference method 700). In some embodiments, when the electronic device initiates a process to send first information about the item to the entity based on determining that the entity is configured to access one or more characteristics of the trackable object, the electronic device sends second information to the entity to specifically link the trackable object to the baggage identification number of the lost item. For example, although the entity is configured to use the baggage identification number to track the location of items (e.g., a user's baggage / luggage), this tracking is performed via the entity's internal tracking system / method (which may be delayed, outdated, and / or poorly managed) rather than via object location data provided by the trackable object (e.g., real-time). In some embodiments, the second information is included together with information about the item. In some implementations, the second information is sent separately from the information about the item (e.g., after the information about the item). Sending this information when a user-owned trackable object is reported lost allows the entity to associate the trackable object with known item information, helping to enable personnel associated with the entity to efficiently locate and identify the item when locating the trackable object without requiring the user to manually provide the input associated with doing so, thereby improving user-device interaction.

[0257] In some implementations, granting an entity access to a trackable object to enable the location of one or more features of the trackable object based on signals emitted by the object occurs after the process of sending initial information about the object to the entity is completed, as referenced in [reference to...]. Figure 10IThe selection of submission option 1054 is described similarly. For example, upon completion of the item location reporting process described above (e.g., after the entity receives the first information about the entity), the entity is granted access to information corresponding to the location of the trackable object. Specifically, during the item location reporting process described above, optionally, permission to grant the entity access to one or more features of the trackable object may not occur. Additionally or alternatively, in some embodiments, permission to grant the entity access to one or more features of the trackable object has not occurred before the completion of the item location reporting process described above. In some embodiments, thus, one or more features of the trackable object that enable the entity to access the location of the trackable object are generated only after the process for sending the first information about the item to the entity is completed. In some embodiments, the electronic device displays a visual indication (e.g., a notification or other visual alert) in the user interface via a display generation component that the item location reporting process has been completed and the entity has been granted access to the location of the trackable object, as discussed similarly above. When a user-owned trackable object is reported lost, permissions to one or more features that would allow the entity to access the location of the trackable object are not granted until information about the item is sent to the entity. This helps ensure that the user intends to grant the entity access to the location of the trackable object, thereby improving user privacy and user-device interaction.

[0258] In some implementations, the user interface associated with the trackable object is a management user interface for the trackable object, where the management user interface is the user interface of the item location application, such as... Figure 10BThe user interface 1012 in the reference method. For example, the management user interface for a trackable object includes information corresponding to the trackable object, such as an identifier of the trackable object (e.g., a name, title, and / or label optionally specified by the user), the location of the trackable object (e.g., the current location or last detected location of the trackable object), and / or a graphical representation of the trackable object (e.g., an image or rendering). In some embodiments, the management user interface includes one or more options for managing the trackable object, including optional options that can be selected to request that an item associated with the trackable object be reported as lost to an entity (which initiates the item location reporting process discussed above). In some embodiments, the first input includes a selection of optional options displayed in the management user interface. In some embodiments, the management user interface for a trackable object has one or more characteristics of the management user interface described in reference method 700. When a user-owned trackable object is reported lost, access to one or more features of the trackable object via the management user interface for the trackable object alerts the entity that the trackable object has been lost and enables personnel associated with the entity to efficiently track the location of the trackable object for locating it. This reduces the need for user input to manually provide object location information to the entity and simplifies the input for reporting items as lost to the entity, thereby improving user-device interaction.

[0259] In some implementations, the user interface associated with the traceable object is the user interface of the application associated with the entity, such as... Figure 6G The user interface 640 is used in the application. For example, the user interface is displayed in an application owned and / or operated by the entity and displayed and accessible via an electronic device, as similarly described with reference to method 700. In some embodiments, the user interface of the application associated with the entity does not correspond to the user interface of the item location application discussed above. In some embodiments, the user interface of the application associated with the entity does not correspond to the management user interface for trackable objects discussed above. When a user-owned trackable object is reported lost, the user interface of the entity's application grants access to one or more features of the trackable object, alerting the entity that the trackable object has been lost and enabling personnel associated with the entity to efficiently track the location of the trackable object for location purposes. This reduces the need for user input to manually provide object location information to the entity and simplifies the input for reporting an item as lost to the entity, thereby improving user-device interaction.

[0260] In some implementations, in response to the detection of a first input, based on determining that the location of a traceable object was recently near a location associated with the user of the electronic device (e.g., less than a threshold time amount relative to the current time and / or before the time of detecting the first input), the electronic device displays an alert user interface object (e.g., ...) via a display generation component indicating that the location of the traceable object was recently near a location associated with the user. Figure 10V (As indicated in Warning 1093). For example, when the electronic device detects a first input and / or while the electronic device is detecting a first input, the electronic device determines that the user (and / or the electronic device) and the trackable object (and therefore the item) have recently (e.g., within the past 1 minute, 3 minutes, 5 minutes, 10 minutes, 15 minutes, 25 minutes, 30 minutes, 1 hour, 3 hours, or 5 hours) been within a threshold distance (e.g., 0.1m, 0.2m, 0.5m, 0.8m, 1m, 1.2m, 1.5m, 2m, 5m, 10m, 20m, or 40m) of each other and have moved together (e.g., moving together while not becoming more distant than the threshold distance) at a predefined distance (e.g., 1m, 2m, 5m, 10m, 15m, 20m, 30m, 35m, or 40m) and / or have not been stationary for at least a second threshold time (e.g., 1 minute, 5 minutes, 15 minutes, 30 minutes, 1 hour, or 2 hours). In some embodiments, the electronic device detects that the user (and / or the electronic device) and the trackable object are within a threshold distance from each other without detecting movement of the electronic device and / or the trackable object. In some embodiments, the electronic device detects that the trackable object has moved beyond a predefined distance with the electronic device. In some embodiments, at the time of and / or after initiating a process for sending information about the item to an entity (e.g., but before granting the entity access to the location of the trackable object), the electronic device determines that the location of the trackable object is near or recently near the location associated with the user. In some embodiments, in response to detecting that the trackable object and the user (and / or the electronic device) are near or recently near each other, the electronic device displays and / or generates a notification or visual alert indicating that the trackable object is near and / or recently near the user of the electronic device. In some embodiments, the alert user interface object is displayed in the user interface associated with the trackable object discussed above. In some embodiments, the alert user interface object is displayed on the main screen of the electronic device (e.g., such as a reference). Figure 4AThe alert user interface object is displayed on the screen (or locked screen). In some embodiments, the display of the alert user interface object is accompanied by audible (e.g., ringing or chiming) and / or tactile (e.g., vibration) feedback. In some embodiments, although the alert user interface object is displayed, the electronic device continues the process discussed above for granting an entity access to one or more features of the trackable object (e.g., no additional user input is required after the alert user interface object is displayed). Alternatively, in some embodiments, when the alert user interface object is displayed, the electronic device relinquishes the process for granting an entity access to one or more features of the trackable object until additional user input for continuing the process is detected (e.g., user input pointing to the alert user interface object or other optional options). In some embodiments, when the alert user interface object is displayed, the electronic device relinquishes the process for granting an entity access to one or more features of the trackable object and optionally does not provide an option for continuing the process (e.g., optional options). In some embodiments, (optionally in response to detecting the first input) the electronic device relinquishes the display of the alert user interface object discussed above based on the determination that the location of the trackable object is not recently near a location associated with the user of the electronic device (and / or not near a location associated with the user of the electronic device). For example, electronic devices continue to initiate processes for granting entities access to the location of trackable objects. When a trackable object associated with a user of the electronic device is reported lost by an entity, an alert is generated at the electronic device when the location associated with the user and the location of the trackable object are near or recently near each other. This facilitates the discovery that the user of the electronic device possesses a trackable object and / or helps the user avoid unintentionally and / or undesirably granting entities access to the location of the trackable object, thereby improving user-device interaction and user privacy.

[0261] In some implementations, in response to the detection of a first input, based on the determination that the location of the trackable object (e.g., relative to the current time and / or the time at which the first input was detected) has been updated (e.g., or otherwise known) before exceeding a threshold time amount (e.g., 5 minutes, 15 minutes, 30 minutes, 1 hour, 2 hours, 5 hours, 10 hours, 1 day, 3 days, or 1 week), the electronic device displays, via a display generation component, an alert user interface object indicating that the location of the trackable object has been updated before exceeding the threshold time amount (e.g., ...). Figure 10WWarning 1096 in the document (e.g., a warning that the location of a trackable object is outdated and / or will otherwise not assist in locating the item). For example, when the electronic device detects a first input and / or while the electronic device is detecting a first input, the electronic device determines the last known location of the trackable object (and therefore the item) based on location data reported by the trackable object before a threshold time amount has elapsed. In some embodiments, the location of the trackable object is known and / or has been updated before the threshold time amount has elapsed due to an interruption in wireless communication between the trackable object and the electronic device. For example, the trackable object and / or the electronic device are located at a corresponding location where wireless communication between the electronic device and the trackable object is currently not permitted (e.g., via Wi-Fi, Bluetooth, or other wireless communication). In some embodiments, determining that the location of the trackable object was updated before the threshold time amount has elapsed is based on determining that the electronic device is currently unable to detect the location of the trackable object (e.g., due to one or more of the reasons above). In some embodiments, the threshold time amount is determined based on a time-limited event during which the trackable object is lost, as discussed similarly above. For example, if the last known location of a trackable object was before a time-limited event and / or before the trackable object (and therefore the item) was addressed by an entity, the electronic device determines that the location of the trackable object was updated before a threshold time amount has elapsed. In some embodiments, the electronic device determines that the location of the trackable object was updated and / or otherwise known before a threshold time amount has elapsed, at the time and / or after the process of sending information about the item to the entity is initiated (e.g., but before granting the entity access to the location of the trackable object). In some embodiments, in response to detecting that the location of the trackable object has become outdated, the electronic device displays and / or generates a notification or visual alert indicating that the location of the trackable object has become outdated. In some embodiments, an alert user interface object is displayed in a user interface associated with the trackable object discussed above. In some embodiments, the alert user interface object is displayed on the main screen of the electronic device (e.g., such as a reference). Figure 4AThe alert user interface object is displayed on the screen (or locked screen). In some embodiments, the display of the alert user interface object is accompanied by audible (e.g., ringing or chiming) and / or tactile (e.g., vibration) feedback. In some embodiments, despite the display of the alert user interface object, the electronic device continues the process discussed above for granting an entity access to one or more features of the trackable object (e.g., no additional user input is required after the alert user interface object is displayed). Alternatively, in some embodiments, when the alert user interface object is displayed, the electronic device relinquishes the process for granting an entity access to one or more features of the trackable object until additional user input for continuing the process is detected (e.g., user input pointing to the alert user interface object or other optional options). In some embodiments, when the alert user interface object is displayed, the electronic device relinquishes the process for granting an entity access to one or more features of the trackable object and optionally does not provide an option for continuing the process (e.g., optional options). In some implementations, (optionally in response to detecting a first input) the electronic device abandons displaying the alert user interface object discussed above, based on the determination that the location of the traceable object was not updated before a threshold time interval has elapsed (e.g., the location of the traceable object is currently known and / or was recently updated by the electronic device). For example, the electronic device continues to initiate the process of granting the entity access to the location of the traceable object. Generating an alert at the electronic device when a traceable object associated with the user of the electronic device is reported lost to the entity, or when the location of the traceable object is outdated, facilitates the discovery that the location of the traceable object will not assist the entity in locating the traceable object, and / or helps the user avoid unintentionally and / or undesirably granting the entity access to the location of the traceable object, thereby improving user-device interaction and user privacy.

[0262] In some implementations, in response to the detection of a first input, based on determining that the location of the trackable object corresponds to a corresponding location of one or more user-specified locations (e.g., at the current time and / or at the time the first input was detected), the electronic device displays an alert user interface object (e.g., similar to) indicating the presence of the trackable object at the corresponding location via a display generation component. Figure 10U(See Alert 1091). For example, when the electronic device detects a first input and / or while the electronic device is detecting a first input, the electronic device determines that the trackable object (and therefore the item) is located in a location known to the user of the electronic device (e.g., a “safe” or “trusted” location), such as one or more locations stored in the memory of the electronic device. In some embodiments, one or more locations are associated with a map or other navigation application on the electronic device. For example, one or more user-specified locations include one or more user-favorited destinations / locations (e.g., home address, work address, and / or school address) or previous destinations within the application that meet one or more criteria (e.g., destinations the user has previously or recently visited, such as within the past 30 minutes, 1 hour, 3 hours, 5 hours, 10 hours, 1 day, 3 days, or 1 week) (e.g., frequently visited, such as more than 3, 4, 5, 8, 10, 15, or 20 times). In some embodiments, one or more user-specified locations correspond to one or more locations stored in the memory of the electronic device and associated with a contacts application on the electronic device. For example, one or more user-specified locations include one or more addresses associated with one or more of the user's contacts (e.g., entered and saved by the user). In some implementations, one or more user-specified locations correspond to any location, destination, and / or address associated with any or a combination of applications running on an electronic device, such as messaging (e.g., text and / or email) applications, web browsing applications, and / or social media applications, or other data stored in memory or otherwise accessible by the electronic device. In some implementations, a secure / trusted location is defined for the trackable object (e.g., via user input in a user interface associated with the trackable object, such as the management user interface discussed above). In some implementations, a trusted location is designated for the trackable object in response to the detection of user input pointing to an optional option, which is displayed in and / or along with a separation alert displayed by the electronic device (e.g., a notification or other alert indicating that the trackable object is no longer with the user and / or the electronic device and / or that the trackable object has been separated from the user and / or the electronic device). In some implementations, defining a trusted location for the trackable object (e.g., home, workplace, school, or other location) allows the electronic device to determine whether the trackable object and the user left the trusted location together, and thus indicates whether the trackable object is likely to have been intentionally left at the trusted location. In some implementations, a trusted location is a trusted person.For example, when a trackable object is determined to be with a trusted person (e.g., following the location of a trusted person or within a threshold distance (e.g., within 0.1m, 0.2m, 0.5m, 0.8m, 1m, 1.2m, 1.5m, 2m, 5m, 10m, 20m, or 40m of the trusted person), the electronic device determines that the location of the trackable object corresponds to the corresponding location. In some embodiments, determining that the location of the trackable object corresponds to the corresponding location among one or more user-specified locations is based on determining that the location of the trackable object is within a threshold distance (e.g., 0.1m, 0.2m, 0.5m, 0.8m, 1m, 1.2m, 1.5m, 2m, 5m, 10m, 20m, or 40m) of a safe location. In some embodiments, when the trackable object separates from the electronic device (e.g., at a distance greater than a threshold distance), if the trackable object is not in a trusted location (e.g., the corresponding location above), the electronic device displays a warning indicating that the object has separated from the electronic device (e.g., a separation warning). In some implementations, when a trackable object is separated from an electronic device, the electronic device does not display a separation warning if the trackable object is in a trusted location.

[0263] In some implementations, the electronic device determines that the location of the trackable object corresponds to a specific location when and / or after initiating the process of sending information about the item to the entity (e.g., but before granting the entity access to the location of the trackable object). In some implementations, in response to detecting that the trackable object is located at the specific location, the electronic device displays and / or generates a notification or visual alert indicating that the trackable object is at the specific location and / or otherwise in a secure / user-known location. In some implementations, the alert user interface object is displayed in a user interface associated with the trackable object discussed above. In some implementations, the alert user interface object is displayed on the main screen of the electronic device (e.g., such as a reference). Figure 4AThe alert user interface object is displayed on the screen (or locked screen). In some embodiments, the display of the alert user interface object is accompanied by audible (e.g., ringing or chiming) and / or tactile (e.g., vibration) feedback. In some embodiments, although the alert user interface object is displayed, the electronic device continues the process discussed above for granting an entity access to one or more features of the trackable object (e.g., no additional user input is required after the alert user interface object is displayed). Alternatively, in some embodiments, when the alert user interface object is displayed, the electronic device relinquishes the process for granting an entity access to one or more features of the trackable object until additional user input for continuing the process is detected (e.g., user input pointing to the alert user interface object or other optional options). In some embodiments, when the alert user interface object is displayed, the electronic device relinquishes the process for granting an entity access to one or more features of the trackable object and optionally does not provide an option for continuing the process (e.g., optional options). In some embodiments, (optionally in response to detecting the first input) the electronic device relinquishes the display of the alert user interface object discussed above based on the determination that the location of the trackable object does not correspond to a corresponding location (e.g., or any of one or more user-specified locations). For example, electronic devices continue to initiate processes for granting entities access to the location of trackable objects. When a trackable object associated with a user of the electronic device is reported lost to an entity, an alert is generated at the electronic device when the location of the trackable object corresponds to a safe location. This facilitates the discovery that the trackable object is in a safe location and / or helps users avoid unintentionally and / or undesirably granting entities access to the location of trackable objects, thereby improving user-device interaction and user privacy.

[0264] It should be understood that, Figures 9A to 9D The specific order in which the operations are described herein is merely exemplary 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 conceive of various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein in conjunction with other methods described herein (e.g., methods 700 and / or 1100) also apply in a similar manner to the above description relative to... Figures 9A to 9DMethod 900 is described above. For example, the remote locator object described with reference to method 900 above, sharing access to one or more features of a searchable item, displaying an item location application, displaying a user interface associated with the searchable item, displaying status updates associated with the searchable item, and displaying a user interface associated with an entity searchable item may optionally have one or more of the features of the searchable item, sharing access to the location of the searchable item with the entity, displaying an item location application, displaying a user interface associated with the searchable item, and displaying a user interface associated with the entity, as described herein with reference to other methods described herein (...

Claims

1. A method, the method comprising: At the electronic device that communicates with the display generation component and one or more input devices: When a user interface associated with a traceable object associated with the electronic device is displayed via the display generation component, a first input corresponding to a request to associate the traceable object with a time-limited event is received via the one or more input devices; as well as In response to receiving the first input, a process is initiated for sharing information corresponding to the location of the trackable object with an entity associated with the time-limited event, wherein the information corresponding to the location of the trackable object is shared with the entity for a corresponding duration associated with the time-limited event.

2. The method according to claim 1, wherein: The user interface associated with the traceable object includes a first optional option that can be selected to request associating the traceable object with the time-limited event; and The first input includes the selection of the first optional option.

3. The method of claim 1, wherein the entity associated with the time-limited event is an organization associated with the time-limited event.

4. The method of claim 1, wherein the user interface associated with the trackable object is a management user interface for the trackable object, wherein the management user interface is a user interface for an item location application.

5. The method of claim 4, wherein the item location application provides management of a plurality of trackable objects including the trackable object.

6. The method of claim 4, wherein the process of initiating the sharing of information corresponding to the location of the traceable object with the entity associated with the time-limited event comprises: The display generation component displays information corresponding to one or more corresponding future time-limited events, including the time-limited event.

7. The method according to claim 4, further comprising: After sharing the information corresponding to the location of the traceable object with the entity associated with the time-limited event, an indication of the traceable object being associated with the time-limited event is displayed in the management user interface via the display generation component.

8. The method of claim 1, wherein the user interface associated with the traceable object is a management user interface for the time-limited events.

9. The method of claim 8, wherein the management user interface for the time-limited event is a user interface of an application associated with the entity.

10. The method of claim 8, wherein the management user interface for the time-limited event is a user interface of a virtual wallet application configured to store digital passes, including digital passes associated with the time-limited event.

11. The method of claim 1, wherein the first input includes an input pointing to a system warning of the electronic device, the system warning being displayed via the display generation component.

12. The method of claim 1, wherein the start of the corresponding duration associated with the time-limited event is determined based on the start of the time-limited event.

13. The method of claim 1, wherein the start of the corresponding duration associated with the time-limited event is determined based on the current location of the electronic device.

14. The method of claim 1, wherein the start of the corresponding duration associated with the time-limited event is determined based on detecting that the location of the trackable object is more than a threshold distance from the current location of the electronic device.

15. The method of claim 1, wherein the end of the corresponding duration associated with the time-limited event is determined based on the expected end of the time-limited event.

16. The method of claim 1, wherein the end of the corresponding duration associated with the time-limited event is determined based on detecting that the location of the trackable object is within a threshold distance of the current location of the electronic device.

17. The method according to claim 1, wherein: Before receiving the first input, the current position of the trackable object is updated at the electronic device at a first frequency; and When the entity associated with the time-limited event shares the information corresponding to the location of the trackable object, the current location of the trackable object is updated at the electronic device at a second frequency greater than the first frequency.

18. The method according to claim 1, further comprising: When the entity associated with the time-limited event shares the information corresponding to the location of the traceable object, information corresponding to the state of the traceable object relative to the time-limited event is displayed via the display generation component, wherein the information is determined based on: The current position of the trackable object; and Tracking updates for the trackable object provided by the entity.

19. The method of claim 1, wherein the process of initiating the sharing of information corresponding to the location of the trackable object with the entity associated with the time-limited event includes initiating a process of granting the entity permission to access one or more features of the trackable object, the one or more features being configured to enable the tracking object to be located based on signals emitted by the trackable object.

20. An electronic device, the electronic device comprising: One or more processors; Memory; as well as 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 including instructions for performing the method according to any one of claims 1 to 19.

21. A non-transitory computer-readable storage medium storing one or more programs, said one or more programs comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method according to any one of claims 1 to 19.

Images