User interface for location-dependent communications

Abstract

The invention relates to a user interface for location-dependent communication. The present disclosure generally relates to managing location-related communications for an electronic device associated with a user account.

Description

[0001] This application is a divisional application of the Chinese invention patent application with the application date of May 22, 2020, the national application number 202080040230.4, and the invention name “User Interface for Location-Related Communications”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Provisional Patent Application Serial No. 62 / 856,005, filed on June 1, 2019, and entitled “USER INTERFACES FOR LOCATION-RELATED COMMUNICATIONS,” and U.S. Patent Application Serial No. 16 / 669,187, filed on October 30, 2019, and entitled “USER INTERFACES FOR LOCATION-RELATED COMMUNICATIONS,” the contents of which are hereby incorporated by reference in their entirety. Technical Field

[0004] The present disclosure relates generally to computer user interfaces and, more particularly, to techniques for managing location-related communications of electronic devices associated with a user account. Background Art

[0005] An electronic device may include hardware and / or software for identifying the current location of the electronic device. Such a device may also transmit its location to one or more other devices. Summary of the invention

[0006] However, some techniques for using electronic devices to manage location-related communications of electronic devices associated with user accounts are often cumbersome and inefficient. For example, some prior art techniques use complex and time-consuming user interfaces that may include multiple keystrokes or keystrokes. Prior art techniques require more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices. Prior art techniques may also fail to provide adequate notification and security for sensitive, location-related communications.

[0007] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for managing location-related communications of electronic devices associated with user accounts. Such methods and interfaces optionally supplement or replace other methods for managing location-related communications of electronic devices associated with user accounts. Such methods and interfaces reduce the cognitive burden imposed on users and produce more efficient human-computer interfaces. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges.

[0008] An exemplary method is described herein. An exemplary method includes, at an electronic device having a display device: when the electronic device is associated with a first user account, the first user account shares the location of the electronic device with one or more user accounts other than the first user account: receiving an indication that a second user account is requesting to be notified of a change in the location of the electronic device relative to a first geographic location that satisfies a set of criteria; after receiving an indication that the second user account is requesting to be notified of a change in the location of the electronic device relative to the first geographic location that satisfies the set of criteria: based on determining that a set of notification criteria is satisfied, the set of notification criteria includes criteria that are satisfied when an indication that the second user account is requesting to be notified has been received, displaying a notification via the display device indicating that the second user account is requesting to be notified of a change in the location of the electronic device relative to the first geographic location that satisfies the set of criteria.

[0009] An exemplary non-transitory computer-readable storage medium is described herein. An exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: when the electronic device is associated with a first user account, the first user account shares the location of the electronic device with one or more user accounts other than the first user account: receiving an indication that a second user account is requesting to be notified of a change in the location of the electronic device relative to a first geographic location that satisfies a set of criteria; after receiving an indication that the second user account is requesting to be notified of a change in the location of the electronic device relative to the first geographic location that satisfies the set of criteria: based on determining that a set of notification criteria are satisfied, the set of notification criteria includes criteria that are satisfied when an indication that the second user account is requesting to be notified has been received, displaying a notification via the display device indicating that the second user account is requesting to be notified of a change in the location of the electronic device relative to the first geographic location that satisfies the set of criteria.

[0010] An exemplary transient computer-readable storage medium is described herein. An exemplary transient computer-readable storage medium, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: when the electronic device is associated with a first user account, the first user account shares the location of the electronic device with one or more user accounts other than the first user account: receiving an indication that a second user account is requesting to be notified of a change in the location of the electronic device relative to a first geographic location that satisfies a set of criteria; after receiving an indication that the second user account is requesting to be notified of a change in the location of the electronic device relative to the first geographic location that satisfies the set of criteria: based on determining that a set of notification criteria are satisfied, the set of notification criteria includes criteria that are satisfied when an indication that the second user account is requesting to be notified has been received, displaying a notification via the display device indicating that the second user account is requesting to be notified of a change in the location of the electronic device relative to the first geographic location that satisfies the set of criteria.

[0011] An exemplary electronic device is described herein. An exemplary electronic device includes a display device; one or more processors; a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: when the electronic device is associated with a first user account, the first user account shares the location of the electronic device with one or more user accounts other than the first user account: receiving an indication that a second user account is requesting to be notified of a change in the location of the electronic device relative to a first geographic location that satisfies a set of criteria; after receiving an indication that the second user account is requesting to be notified of a change in the location of the electronic device relative to the first geographic location that satisfies the set of criteria: based on determining that a set of notification criteria are satisfied, the set of notification criteria includes criteria that are satisfied when an indication that the second user account is requesting to be notified has been received, displaying a notification via the display device indicating that the second user account is requesting to be notified of a change in the location of the electronic device relative to the first geographic location that satisfies the set of criteria.

[0012] An exemplary electronic device includes a display device; and an apparatus for performing the following operations when the electronic device is associated with a first user account, and the first user account shares the location of the electronic device with one or more user accounts other than the first user account: receiving an indication that a second user account is requesting to be notified of changes in the location of the electronic device relative to a first geographic location that satisfy a set of criteria; after receiving an indication that the second user account is requesting to be notified of changes in the location of the electronic device relative to the first geographic location that satisfy the set of criteria: based on determining that a set of notification criteria are satisfied, the set of notification criteria includes criteria that are satisfied when an indication that the second user account is requesting to be notified has been received, displaying a notification via the display device indicating that the second user account is requesting to be notified of changes in the location of the electronic device relative to the first geographic location that satisfy the set of criteria.

[0013] An exemplary method includes, at an electronic device: when evaluating a current location associated with a user account relative to a geographic location and a time range: based on determining that the current location associated with the user account does not have a predefined relationship with the geographic location within the time range, generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location; and based on determining that the current location associated with the user account does not have a predefined relationship with the geographic location at a time outside the time range, abandoning generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location.

[0014] An exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: when evaluating a current location associated with a user account relative to a geographic location and a time range: based on determining that the current location associated with the user account does not have a predefined relationship with the geographic location within the time range, generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location; based on determining that the current location associated with the user account does not have a predefined relationship with the geographic location at a time outside the time range, abandoning generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location.

[0015] An exemplary transient computer-readable storage medium, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: when evaluating a current location associated with a user account relative to a geographic location and a time range: based on determining that the current location associated with the user account does not have a predefined relationship with the geographic location within the time range, generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location; based on determining that the current location associated with the user account does not have a predefined relationship with the geographic location at a time outside the time range, abandoning generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location.

[0016] An exemplary electronic device includes one or more processors; a memory, the memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: when evaluating a current location associated with a user account relative to a geographic location and a time range: based on determining that the current location associated with the user account does not have a predefined relationship with the geographic location within the time range, generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location; based on determining that the current location associated with the user account does not have a predefined relationship with the geographic location at a time outside the time range, abandoning generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location.

[0017] An exemplary electronic device includes a device for performing the following operations when evaluating a current location associated with a user account relative to a geographic location and a time range: based on determining that the current location associated with the user account does not have a predefined relationship with the geographic location within the time range, generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location; based on determining that the current location associated with the user account does not have a predefined relationship with the geographic location at a time outside the time range, abandoning generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location.

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

[0019] Thus, a faster, more efficient method and interface is provided for devices for managing location-related communications of electronic devices associated with user accounts, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for managing location-related communications of electronic devices associated with user accounts. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, wherein like reference numerals designate corresponding parts throughout the several views.

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

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

[0023] Figure 2 A portable multifunction device with a touch screen according to some embodiments is shown.

[0024] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.

[0025] Figure 4A An exemplary user interface for a menu of applications on a portable multifunction device is shown according to some embodiments.

[0026] Figure 4B An exemplary user interface is shown for a multifunction device having a touch-sensitive surface that is separate from the display according to some embodiments.

[0027] Figure 5A A personal electronic device according to some embodiments is shown.

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

[0029] FIG. 6A to FIG. 6U An exemplary user interface is shown for managing location-related communications for electronic devices associated with a user account according to some embodiments.

[0030] Figure 7 is a flow chart illustrating a method for managing location-related communications of electronic devices associated with a user account according to some embodiments.

[0031] Figure 8is a flowchart illustrating a method for managing location-related communications of electronic devices associated with a user account according to some embodiments. DETAILED DESCRIPTION

[0032] The following description sets forth exemplary methods, parameters, etc. However, it should be appreciated that such description is not intended to limit the scope of the present disclosure, but is provided as a description of exemplary embodiments.

[0033] There is a need for electronic devices to provide efficient methods and interfaces for managing location-related communications of electronic devices associated with user accounts. For example, a parent can manage notifications that indicate when another device (e.g., a child's device associated with the child's user account) is not in an expected geographic location for a specific period of time. Such techniques can reduce the cognitive burden on users managing location-related communications of electronic devices associated with user accounts, thereby increasing productivity. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0034] Below, Figure 1A to Figure 1B , Figure 2 , Figure 3 , FIG. 4A to FIG. 4B and FIG. 5A to FIG. 5B A description of example devices for performing techniques for managing location-related communications of electronic devices is provided. FIG. 6A to FIG. 6U An exemplary user interface for managing location-related communications of electronic devices associated with a user account is shown. Figure 7 is a flow chart illustrating a method for managing location-related communications of electronic devices associated with a user account according to some embodiments. Figure 8 is a flowchart illustrating a method for managing location-related communications of electronic devices associated with a user account according to some embodiments. FIG. 6A to FIG. 6U The user interface in the Figure 7 and Figure 8 The process is described below in the process.

[0035] 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 element. For example, a first touch can be named a second touch and similarly a second touch can 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.

[0036] The terms used in the description of various described embodiments herein are only for the purpose of describing specific embodiments, and are not intended to be limited. As used in the description of various described embodiments and in the appended claims, the singular forms "one" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more items in the associated listed items. It will also be understood that the term "includes", "including", "comprises" and / or "comprising" when used in this specification specifies the presence of stated features, integers, steps, operations, elements and / or parts, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their grouping.

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

[0038] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple iPod from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Other portable electronic devices, such as laptops or tablets with touch-sensitive surfaces (e.g., touch screen displays and / or trackpads) are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or trackpads).

[0039] 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 optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse and / or joystick.

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

[0041] Various applications executed on the device 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 corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or adjusted and / or varied within the respective applications. In this way, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports a variety of applications with a user interface that is intuitive and clear to the user.

[0042] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1A is a block diagram showing a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to as or referred to as a "touch-sensitive display system." The 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 device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0043] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four different values ​​and more typically includes hundreds of different values ​​(e.g., at least 256). The intensity of a contact is optionally 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 touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute 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 the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). 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 the 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 the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical control / mechanical control, such as a knob or button).

[0044] As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "release click" to a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when there is no change in the smoothness of the touch-sensitive surface, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. Although such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user.

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

[0046] Memory 102 optionally includes high-speed random access memory, and optionally also includes 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 optionally controls other components of device 100 to access memory 102.

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

[0048] RF (radio frequency) circuit 108 receives and sends RF signals, also referred to as electromagnetic signals. RF circuit 108 converts electrical signals into / 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 circuits 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, user identity modules (SIM) cards, memories, and the like. RF circuit 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also referred to as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communications (NFC) fields, such as through short-range communications radio components. Wireless communication optionally uses 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, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols that have not been developed as of the filing date of this document.

[0049] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to humans. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals into audio data and transmits the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., Figure 2 The headset jack provides an interface between the audio circuit 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset having both output (e.g., a single or dual-ear headset) and input (e.g., a microphone).

[0050] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller 160 is optionally coupled to any of the following (or none of the following): a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g., Figure 2 208) optionally includes an increase / decrease button for volume control of the speaker 111 and / or the microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2 206).

[0051] A quick press of the push button optionally disengages the lock of the touch screen 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image" (i.e., U.S. Patent No. 7,657,849), which is hereby incorporated by reference in its entirety. A long press of the push button (e.g., 206) optionally turns the device 100 on or off. The functions of one or more buttons are optionally user-customizable. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0052] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

[0053] The touch screen 112 has a touch-sensitive surface, sensor, or sensor group that accepts input from a user based on tactile and / or haptic contact. The touch screen 112 and display controller 156 (together with any associated modules and / or instruction sets in memory 102) detect contact on the touch screen 112 (and any movement or interruption of the contact) and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to a finger of the user.

[0054] The touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. The touch screen 112 and display controller 156 optionally use any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112 to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as in the Apple ® from Apple Inc. (Cupertino, California). and iPod The technology used in.

[0055] The touch-sensitive display in some embodiments of the touch screen 112 is optionally similar to the multi-touch-sensitive trackpad described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman et al.), and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, the touch screen 112 displays visual output from the device 100, while the touch-sensitive trackpad does not provide visual output.

[0056] In some embodiments, the touch-sensitive display of the touch screen 112 is as described in the following patent applications: (1) U.S. patent application No. 11 / 381,313, entitled “Multipoint Touch Surface Controller,” filed on May 2, 2006; (2) U.S. patent application No. 10 / 840,862, entitled “Multipoint Touchscreen,” filed on May 6, 2004; (3) U.S. patent application No. 10 / 903,964, entitled “Gestures For Touch Sensitive Input Devices,” filed on July 30, 2004; (4) U.S. patent application No. 11 / 048,264, entitled “Gestures For Touch Sensitive Input Devices,” filed on January 31, 2005; (5) U.S. patent application No. 11 / 086,874, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed on January 18, 2005 and (9) U.S. patent application No. 11 / 367,749, filed on March 3, 2006, entitled “Multi-Functional Hand-Held Device.” All of these applications are hereby incorporated by reference in their entirety.

[0057] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​the finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the actions desired by the user.

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

[0059] The device 100 also includes a power system 162 for powering the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, 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 a portable device.

[0060] Device 100 optionally also includes one or more optical sensors 164 . Figure 1AAn optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. 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 the imaging module 143 (also called a camera module), the optical sensor 164 optionally captures a static image or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for static images and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that the user's image is optionally obtained for video conferencing while the user views other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that a single optical sensor 164 is used with the touch screen display for both video conferencing and static image and / or video image acquisition.

[0061] Device 100 optionally also includes one or more depth camera sensors 175 . Figure 1A A depth camera sensor coupled to a depth camera controller 169 in the I / O subsystem 106 is shown. The depth camera sensor 175 receives data from the environment to create a three-dimensional model of an object (e.g., a face) within the scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with the imaging module 143 (also referred to as a camera module), the depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by the imaging module 143. In some embodiments, the depth camera sensor is located at the front of the device 100, so that an image of the user with depth information is optionally obtained for video conferencing while the user is viewing other video conference participants on the touch screen display, and a selfie with depth map data is captured. In some embodiments, the depth camera sensor 175 is located at the rear of the device, or at both the rear and front of the device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that the depth camera sensor 175 is used with the touch screen display for both video conferencing and still image and / or video image acquisition.

[0062] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1AA contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite to touch screen display 112 located on the front of device 100.

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

[0064] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1AA tactile output generator is shown coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component; and / or an electromechanical device for converting energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component for converting an electrical signal into a tactile output on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates a tactile output on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one tactile output generator is arranged in parallel or adjacent to a touch-sensitive surface (e.g., a touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 100) or laterally (e.g., backward and forward in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on the back of the device 100, opposite the touch screen display 112 located on the front of the device 100.

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

[0066] 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. In addition, in some embodiments, memory 102 ( Figure 1A ) or 370( Figure 3 ) storage device / global internal state 157, such as Figure 1A and Figure 3 . The device / global internal state 157 includes one or more of the following: an active application state, which indicates which applications (if any) are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; a sensor state, including information obtained from the device's various sensors and input control devices 116; and position information about the device's position and / or posture.

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

[0068] The communication module 128 facilitates communication with other devices through one or more external ports 124, and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.

[0069] The contact / motion module 130 optionally detects contact with the touch screen 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 contact has occurred (e.g., detecting a finger press event), determining the contact strength (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking the 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 contact disconnection). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of a contact point optionally includes determining a 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 are optionally applied to a single point of contact (e.g., a single finger contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on a touch pad.

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

[0071] The contact / motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event, and then detecting a finger lift (lift-off) event at the same location (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 the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event.

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

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

[0074] Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator 167 to produce tactile output at one or more locations on device 100 in response to user interaction with device 100 .

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

[0076] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for use in location-based dialing; to the camera 143 as picture / video metadata; and to applications that provide location-based services, such as the Weather widget, the Local Pages widget, and the Maps / Navigation widget).

[0077] The application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:

[0078] Contacts module 137 (sometimes called address book or contact list);

[0079] Telephone module 138;

[0080] Video conferencing module 139;

[0081] Email client module 140;

[0082] Instant messaging (IM) module 141;

[0083] Fitness support module 142;

[0084] A camera module 143 for still images and / or video images;

[0085] Image management module 144;

[0086] Video player module;

[0087] Music player module;

[0088] Browser module 147;

[0089] Calendar module 148;

[0090] A widget module 149, which optionally includes one or more of the following: a weather widget 149-1, a stock widget 149-2, a calculator widget 149-3, an alarm widget 149-4, a dictionary widget 149-5, and other widgets acquired by the user, and a user-created widget 149-6;

[0091] A widget creator module 150 for forming a user-created widget 149-6;

[0092] Search module 151;

[0093] Video and music player module 152, which merges the video player module and the music player module;

[0094] Memo module 153;

[0095] Map module 154; and / or

[0096] Online video module 155.

[0097] Examples of other applications 136 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, voice recognition, and voice replication.

[0098] In conjunction with the touch screen 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., stored in the application internal state 192 of the contact module 137 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 the like.

[0099] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, phone module 138 is optionally used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in contact module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0100] In combination with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact / motion module 130, the graphics module 132, the text input module 134, the contact module 137 and the telephone module 138, the video conferencing module 139 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.

[0101] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / 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 instructions. In conjunction with image management module 144, email client module 140 makes it very easy to create and send emails with still images or video images captured by camera module 143.

[0102] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0103] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154 and the music player module, the fitness support module 142 includes executable instructions for creating a fitness (e.g., with time, distance and / or calorie burn goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.

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

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

[0106] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions, including searching, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0107] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the email client module 140 and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying and storing calendars and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

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

[0109] In combination with the RF circuit 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134 and browser module 147, the desktop widget creator module 150 is optionally used by a user to create a desktop widget (e.g., converting a user-specified portion of a web page into a desktop widget).

[0110] In combination with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the search module 151 includes executable instructions for 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) in accordance with user instructions.

[0111] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch screen 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 (trademark of Apple Inc.).

[0112] In conjunction with the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, the memo module 153 includes executable instructions for creating and managing memos, to-do items, etc. according to user instructions.

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

[0114] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions for performing the following operations: allowing a user to access, browse, receive (e.g., by streaming and / or downloading), playback (e.g., on the touch screen or on an external display connected via external port 124), send an email with a link to a specific online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a specific online video. Additional descriptions of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on 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 on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.

[0115] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as independent software programs, processes, or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. For example, a video player module is optionally combined with a music player module into a single module (e.g., Figure 1A In some embodiments, the memory 102 optionally stores a subset of the above modules and data structures. In addition, the memory 102 optionally stores additional modules and data structures not described above.

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

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

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

[0119] Event classifier 170 receives event information and determines the application 136-1 and the application view 191 of application 136-1 to which the event information is to be delivered. Event classifier 170 includes event monitor 171 and event distributor 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 executing. 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 is to be delivered.

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

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

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

[0123] In some embodiments, the event classifier 170 also includes a hit view determination module 172 and / or an active event identifier determination module 173.

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

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

[0126] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy where 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 that form an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

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

[0128] Event distributor module 174 distributes event information to event recognizers (e.g., event recognizers 180). In embodiments including active event recognizer determination module 173, event distributor module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event distributor module 174 stores the event information in an event queue, which is retrieved by corresponding event receivers 182.

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

[0130] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, the corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more event recognizers in event recognizers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit or application 136-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views in application view 191 include one or more corresponding event handlers 190. In addition, 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.

[0131] 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 metadata 183 and at least a subset of event delivery instructions 188 (which optionally include sub-event delivery instructions).

[0132] Event receiver 182 receives event information from event classifier 170. 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 the movement of the touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another orientation (for example, from a longitudinal orientation to a transverse orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

[0133] Event comparator 184 compares event information with predefined event or sub-event definitions, and determines an event or sub-event based on the comparison, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 includes the definition of an event (e.g., a predefined sequence 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, the definition of event 1 (187-1) is a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on a displayed object, a first lift-off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on a displayed object, and a second lift-off (touch end) of a predetermined duration. In another example, the definition of event 2 (187-2) is a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on a displayed object, movement of the touch on the touch-sensitive display 112, and lifting of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0134] In some embodiments, event definition 187 includes definitions of events for corresponding user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view 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 an event handler associated with a sub-event and the object that triggered the hit test.

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

[0136] When a corresponding event recognizer 180 determines that a sequence of sub-events 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 of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

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

[0138] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, 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 sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with the tag obtains the tag and performs a predefined process.

[0139] In some embodiments, the event delivery instructions 188 include 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 a sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or with an actively participating view receives the event information and performs a predetermined process.

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

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

[0142] It should be understood that the above discussion of event processing of user touches 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 touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or hold; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events defining the event to be recognized.

[0143] Figure 2A portable multifunction device 100 with a touch screen 112 according to some embodiments is shown. The touch screen 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 of these graphics by, for example, making gestures on the graphics 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 will occur when the user interrupts contact with the 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 rolling of fingers that have been in contact with the device 100 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

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

[0145] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and for locking the device, one or more volume adjustment buttons 208, a user identity module (SIM) card slot 210, an earphone jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and keeping the button in a pressed state for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval passes; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input for activating or deactivating certain functions through a microphone 113. The device 100 also optionally includes one or more contact strength sensors 165 for detecting the strength of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for a user of the device 100.

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

[0147] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the previously mentioned memory device. Each module in the above-mentioned modules corresponds to the instruction set for performing the above-mentioned functions. The above-mentioned modules or programs (e.g., instruction sets) do not have to be implemented as independent software programs, processes or modules, and therefore the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores the subset of the above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0148] Attention is now turned to an embodiment of a user interface that is optionally implemented on, for example, portable multifunction device 100.

[0149] Figure 4A An exemplary user interface of an application menu on portable multifunction device 100 according to some embodiments is shown. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

[0150] Signal strength indicators 402 for wireless communications such as cellular signals and Wi-Fi signals;

[0151] Time 404;

[0152] Bluetooth indicator 405;

[0153] Battery status indicator 406;

[0154] A tray 408 with icons for commonly used applications, such as:

[0155] o An icon 416 of the phone module 138 labeled "Phone," which optionally includes an indicator 414 of the number of missed calls or voicemails;

[0156] o an icon 418 of the email client module 140 labeled “Mail”, the icon 418 optionally including an indicator 410 of the number of unread emails;

[0157] o An icon 420 labeled "Browser" of the browser module 147; and

[0158] o An icon 422 labeled “iPod” for a video and music player module 152 (also referred to as an iPod (trademark of Apple Inc.) module 152); and

[0159] Icons for other apps, such as:

[0160] o Icon 424 labeled "Message" of IM module 141;

[0161] o An icon 426 labeled “Calendar” of the calendar module 148;

[0162] o Icon 428 labeled “Photos” of the image management module 144;

[0163] o An icon 430 labeled “Camera” of the camera module 143;

[0164] ○ Icon 432 labeled “Online Video” of the online video module 155;

[0165] ○ Icon 434 labeled “Stock Market” of the Stock Market Desktop Applet 149-2;

[0166] o An icon 436 labeled “Map” of the map module 154;

[0167] ○ Icon 438 labeled “Weather” of the Weather widget 149-1;

[0168] ○ Icon 440 labeled as “Clock” of the alarm clock desktop applet 149-4;

[0169] o An icon 442 labeled “Fitness Support” of the fitness support module 142;

[0170] o An icon 444 labeled "Memo" of the memo module 153; and

[0171] o An icon 446 labeled “Settings” for a settings application or module that provides access to settings for the device 100 and its various applications 136 .

[0172] It should be noted that Figure 4A The icon labels shown in are exemplary only. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels are optionally used for various application icons. In some embodiments, the label of a corresponding application icon includes the name of the application corresponding to the corresponding application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

[0173] Figure 4B A touch-sensitive surface 451 (eg, touch screen display 112) is shown having a touch-sensitive surface 451 (eg, Figure 3 tablet or touch pad 355) device (e.g., Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating tactile output for a user of device 300.

[0174] Although some of the examples below are given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the principal axis (for example, Figure 4B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 4B 460 corresponds to 468 and 462 corresponds to 470) in contact with touch-sensitive surface 451 (e.g., Figure 4B Thus, when the touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g., Figure 4B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is separated, the device is used to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

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

[0176] Figure 5AAn exemplary personal electronic device 500 is shown. Device 500 includes a body 502. In some embodiments, device 500 may include a body 502 relative to devices 100 and 300 (e.g., Figures 1A to 4B ) some or all of the features described in the foregoing. In some embodiments, device 500 has a touch-sensitive display screen 504, referred to hereinafter as touch screen 504. As an alternative or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more strength sensors for detecting the intensity of contact (e.g., touch) applied. One or more strength sensors of touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of touch. The user interface of device 500 can respond to touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 500.

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

[0178] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 500.

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

[0180] In some examples, input mechanism 508 is optionally a microphone. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, orientation sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and / or combinations thereof, all of which are operably connected to I / O portion 514.

[0181] 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 and 800 ( Figure 7 and Figure 8). Computer-readable storage media can be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with instruction execution systems, devices, and apparatuses. 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 may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memories such as flash memory, solid-state drives, and the like. Personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other components or additional components in a variety of configurations.

[0182] As used herein, the term "indicative representation" refers to an optional feature of the apparatus 100, 300, and / or 500 ( Figure 1A , Figure 3 and FIG. 5A to FIG. 5B ) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

[0183] 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 implementations that include a cursor or other position 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), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the particular user interface element is adjusted according to the detected input. In the case that a touch-screen display (e.g., Figure 1A A touch-sensitive display system 112 or Figure 4AIn some implementations of the touch screen 112 in FIG. 1 , a contact detected on the touch screen acts as a “focus selector” such that when an input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus moves from one area of ​​the user interface to another area of ​​the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a trackpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

[0184] 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 is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 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 be lifted off, before or after contact starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the value at the top 10% of the intensity of the contact, the half-maximum value of the intensity of the contact, the 90% maximum value of the intensity of the contact, 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 intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation) rather than to determine whether to perform the first operation or the second operation.

[0185] In some embodiments, a portion of a gesture is identified for determining characteristic strength. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting position and reaches an end position, where the contact strength increases. In this example, the characteristic strength of the contact at the end position is optionally based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end position). In some embodiments, a smoothing algorithm is optionally applied to the strength of the swipe contact before determining the characteristic strength of the contact. For example, a smoothing algorithm optionally includes one or more of the following: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow peaks or depressions in the strength of the swipe contact to achieve the purpose of determining the characteristic strength.

[0186] The intensity of contact on the touch-sensitive surface is optionally characterized relative to one or more intensity thresholds such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button of a physical mouse or trackpad. 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 of a physical mouse or trackpad. In some embodiments, when a contact having a characteristic intensity lower than the light press intensity threshold (e.g., and higher than a nominal contact detection intensity threshold, contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector according to the movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally speaking, unless otherwise stated, these intensity thresholds are consistent between different groups of user interface illustrations.

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

[0188] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes 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 strength of the contact (or multiple contacts) increases to above a press input strength threshold. In some embodiments, the corresponding operation is performed in response to detecting that the strength of the corresponding contact increases to above the press input strength threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in the strength of the corresponding contact to above the press input strength threshold and the strength of the contact subsequently decreases to below the press input strength threshold, and the corresponding operation is performed in response to detecting that the strength of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "up stroke" of the corresponding press input).

[0189] In some embodiments, the device employs intensity hysteresis to avoid unexpected inputs sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predefined relationship to a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the intensity of the corresponding contact to above the press input intensity threshold and a subsequent decrease in the intensity of the contact to below the hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the hysteresis intensity threshold (e.g., an "upward stroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and, optionally, that the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in contact intensity or a decrease in contact intensity, depending on the circumstances).

[0190] For ease of explanation, optionally, a description of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture including a press input is triggered in response to detecting any of the following: contact intensity increasing to above the press input intensity threshold, contact intensity increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, contact intensity decreasing to below the press input intensity threshold, and / or contact intensity decreasing to below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operation is optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

[0191] Attention is now turned to embodiments of a user interface ("UI") and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

[0192] FIG. 6A to FIG. 6U An exemplary user interface for managing location-related communications of an electronic device associated with a user account according to some embodiments is shown. The user interface in these figures is used to illustrate the Figure 7 and Figure 8The processes described below are the processes of the processes in . As discussed in more detail below, it should be understood that these processes involve various steps that can be performed across different electronic devices. Non-limiting examples of such steps may include instructions to calculate, determine, grant, revoke or deny permission for an account to use data in a particular manner, and instructions to display objects such as notifications or prompts. In some embodiments, one or more steps may be performed at a first electronic device (e.g., electronic device 6000A) including one or more features of device 100, device 300, and device 500. In some embodiments, one or more steps may be performed at a second electronic device (e.g., electronic device 6000B) including one or more features of device 100, device 300, and device 500. In some embodiments, one or more steps may be performed at a third electronic device such as a server. In some embodiments, one or more steps are performed at any combination of the first electronic device, the second electronic device, and the third electronic device.

[0193] FIG. 6A to FIG. 6U Exemplary user inputs and corresponding changes to a user interface are shown, which may be displayed on an electronic device (e.g., electronic device 6000) having a display 6002 (in some cases a touch-sensitive display (e.g., 112)). In the present disclosure, the electronic devices described may be referenced using reference numerals 6000, 6000A, or 6000B. Generally speaking, reference numeral 6000A is used to refer to a first electronic device (e.g., a parent's electronic device), reference numeral 6000B is used to refer to a second electronic device that is different from the first electronic device (e.g., a child's electronic device), and reference numeral 6000 is used to indiscriminately refer to the first electronic device, the second electronic device, or both. Similarly, various features of electronic device 6000 may be referenced by "A" or "B" designations to distinguish two instances of similar features. For example, reference numeral 6002A is used to refer to a display component of electronic device 6000A, reference numeral 6002B is used to refer to a display component of electronic device 6000B, and reference numeral 6002 is generally used to refer to the display of electronic device 6000, and then indiscriminately refers to the display of the first electronic device, the display of the second electronic device, or both.

[0194] In some embodiments, an electronic device is associated with a user account. For example, electronic device 6000A is an electronic device associated with a parent's user account, and electronic device 6000B is an electronic device associated with a child's user account. It should be understood that, in addition to authorizing at least one of the accounts to share data, user accounts do not need a specific relationship with each other. However, for simplicity, the following disclosure uses an embodiment in which one of the user accounts is a parent's user account and another user account is a child's user account. Specifically, parents are referred to as "mom" and children are referred to as "Jane". Therefore, electronic device 6000A may be referred to as mom's device 6000A in this article, and electronic device 6000B may be referred to as Jane's device 6000B in this article. Similarly, parents' accounts may be referred to as "mom's account", and children's accounts may be referred to as "Jane's account". Where appropriate, similar naming is used in other cases.

[0195] In some embodiments, a user account may be authorized to share location data between user accounts. For example, according to the present disclosure, Jane has set up her user account in a manner that authorizes Mom's account to receive location data indicating the location (e.g., GPS coordinates) of one or more electronic devices associated with Jane's account at one or more electronic devices associated with Mom's account. Therefore, Jane is said to have authorized Mom to receive location data for Jane's electronic devices. Therefore, Mom's account is authorized (by Jane's account) to manage location data associated with Jane's account.

[0196] The following disclosure describes various embodiments in which Mom manages location-related communications with Jane by establishing a geo-fence (e.g., a virtual boundary based on a specific geographic location (e.g., a specific geographic area)) for a specific time period, which is assumed to be represented by the location of one or more electronic devices of Jane (e.g., Jane's device 6000B or Jane's device 6100B). In such embodiments, Mom manages Jane's location so that she is notified (e.g., by receiving a notification from Mom's device 6000A) when Jane is not at an expected location within a specific time range. This enables Mom to be alerted to situations in which Jane is not at an expected location (e.g., school) without requiring Mom to constantly monitor Jane's location using, for example, a map application. In fact, unless Mom is notified otherwise, Mom can assume that Jane is at school during the specified time period.

[0197] Reference now Fig. 6A, Mom's device 6000A is shown displaying a location management user interface 6005. The location management user interface 6005 includes Jane's account information 6004, which includes information related to Jane's account available on Mom's device 6000A. Jane's account information 6004 includes a device list 6006 for indicating devices associated with Jane's user account, and a notification list 6008 for viewing and managing location-based notifications (e.g., geo-fence notifications) created for Jane's account. Fig. 6A As shown, the devices listed by Jane include Jane's phone 6006-1, which refers to Fig. 6F Jane's device 6000B is shown, and Jane's watch 6006-2 refers to Fig.6I Jane's device 6100B is shown. Notification list 6008 includes a first geofence identifier 6008-1 corresponding to an existing geofence notification for notifying Mom's account when Jane (e.g., Jane's device 6000B) arrives home. Notification list 6008 also includes a notification creation affordance 6009 that can be selected to create a new geofence notification.

[0198] like Fig. 6A As shown, Mom's device 6000A detects input 6010 (e.g., user input, such as a tap gesture) on the notification creation affordance 6009, and in response, displays Figure 6B The notification creation user interface 6012 is shown.

[0199] Notification creation user interface 6012 is a user interface for creating a geo-fence notification for Jane's account. Figure 6B As shown, notification creation user interface 6012 includes location-based notification type area 6014, location selection area 6016, time selection area 6018, and date customization area 6020. In some embodiments, notification creation user interface 6012 may include a recurring affordance 6022 for setting the geo-fence notification as a recurring notification. In some embodiments, geo-fence notifications default to recurring notifications unless otherwise specified.

[0200] The location-based notification type area 6014 includes selectable options for setting notification conditions for the geofence. For example, the arrival notification type 6014-1 sets a condition that is met when Jane arrives at a specific location (e.g., within a specific time period). Thus, the arrival notification type will notify Mom (e.g., by displaying a notification on Mom's device 6000A) when Jane arrives at the specified location. The departure notification type 6014-2 sets a condition that is met when Jane leaves a specific location (e.g., during a specific time period). Thus, the departure notification type will notify Mom when Jane leaves the specified location. The expected location notification type 6014-3 sets a condition that is met when Jane is not at a specific location within a specific time period. Thus, the expected location notification type will notify Mom when Jane is not at the specified location at any time during the specified time period. For example, a notification will be triggered if Jane is not at the specified location at the start of the time period, or if Jane leaves the specified location after the time period starts and before the time period ends. Figure 6B As shown, the selected geo-fence notification type is the expected location notification type 6014-3.

[0201] The location selection area 6016 includes selectable options for setting a location component for the selected geofence notification type (expected location notification type 6014-3). In some embodiments, the location option is a user-defined location that indicates a location within the boundaries of the geofence (e.g., the center point of the geofence). Figure 6B , the location options include home 6016-1 and school 6016-2. The location options also include a location creation option 6016-3, which can be selected to create a new location. In some embodiments, the user can create a new location option by selecting the location creation option 6016-3 and specifying a new location, and then adding the new location to the location selection area 6016. In some embodiments, specifying a new location may include entering location information (e.g., address information, coordinates, etc.) and / or selecting a location on a map. Figure 6B As shown, the selected location option is school 6016-2. Therefore, the geo-fence notification is configured to notify mom Jane if she is not at school during the set time period.

[0202] In some embodiments, the boundaries of the geofence can be adjusted relative to any of the selected locations (e.g., home, school, or other created locations) by adjusting the boundaries of the geofence on a map showing the selected locations. For example, Mom can select one of the location options to view a map of the location with a representation of the geofence boundaries (see, e.g., Figure 6S ), and the boundaries (e.g., diameter) of the geofence can be adjusted by adjusting the zoom level of the displayed map while the geofence boundaries remain stationary relative to the map display area.

[0203] The time selection area 6018 includes options for setting a time period for the selected geo-fence notification type (expected location notification type 6014-3). In some embodiments, the time selection options include a start time 6018-1 and an end time 6018-2. Figure 6B As shown, the start time is 9:00AM and the end time is 3:00PM. In this embodiment, the geo-fence notification is configured to notify mom that Jane is not at school between 9:00AM and 3:00PM.

[0204] The date customization area 6020 includes selectable options for setting specific days of the week when the geofence is active. Figure 6B As shown, options 6020-1 to 6020-5 are selected and correspond to Monday, Tuesday, Wednesday, Thursday, and Friday. Options 6020-6 and 6020-7, which correspond to Saturday and Sunday, respectively, are not selected. Therefore, geofence notifications are active on weekdays and inactive on weekends. Therefore, geofence notifications are configured to notify Mom if Jane is not in school between 9:00AM and 3:00PM on weekdays. If Jane is not in school at any time other than 9:00AM to 3:00PM on weekdays, Mom will not be notified.

[0205] The recurring indication 6022 is set to "on", indicating that the geofence notification is a recurring notification that will repeat indefinitely or until otherwise specified. For example, the geofence will repeat once a week.

[0206] exist Figure 6B , Mom's device 6000A detects input 6024 on completion indication 6026 and, in response, displays a confirmation user interface 6028, such as Figure 6C Confirmation user interface 6028 summarizes the conditions of the geofence and displays a create notification enable indication 6030 for confirming the creation of the geofence and a cancel enable indication 6032 for canceling the creation of the geofence. If the geofence is confirmed (e.g., by selecting create notification enable indication 6030), an invitation is sent to Jane's account to accept the conditions of the geofence, as described below with reference to Figures 6F to 6K discussed in more detail.

[0207] exist Figure 6C , Mom's device 6000A detects input 6034 on create notification indicator 6030 and, in response, Fig.6D Jane's account information 6004 is displayed, wherein the notification list 6008 is updated to show the FIG. 6A to FIG. 6CThe second geo-fence identifier 6008-2 corresponding to the geo-fence notification created in Fig.6D As shown, while the geofence is pending acceptance by Jane's account, the second geofence identifier 6008-2 is shown as having an "invite sent" status identifier 6036. This indicates that Jane's account has been sent an invitation to accept the terms of the geofence notifications, but Jane's account has not yet accepted the terms of the geofence. If Jane's account does not accept the terms of the geofence, then if Jane's device violates the geofence (for example, if Jane is not at school between 9AM and 3PM on a weekday, the geofence will not be activated, and in some embodiments, the second geofence identifier 6008-2 will be removed from the notification list 6008, then Mom's account is not authorized to receive notifications. In some embodiments, even if Jane's account does not accept the terms of the geofence notification request, Mom's account continues to receive location information for Jane's account. After Jane's account has accepted the terms of the geofence, the status identifier 6036 is removed, as shown. Fig. 6E shown.

[0208] Figures 6F to 6K Various embodiments are shown in which an invitation to accept the terms of the geo-fence notification is displayed for Jane to accept. In some embodiments, the invitation can be displayed on Jane's device 6000B, such as FIG. 6F to FIG. 6H as well as Figure 6K In some embodiments, the invitation may be displayed on Jane's device 6100B, such as Fig.6I and Figure 6J In some embodiments, Jane's device 6100B is a wearable device (e.g., a smart watch) having a display 6102B.

[0209] In some embodiments, the display of an invitation (e.g., as a notification) is triggered by various conditions. For example, in some embodiments, such as Fig. 6F As shown, when a geo-fence is created by the mother's account (e.g., when selecting to create a notification indicator 6030, as shown in Figure 6C In some embodiments, if the geofence is not a recurring event (e.g., a one-time geofence), an invitation is displayed when the geofence is created. Fig. 6F In FIG. 6 , Jane's device 6000B displays a lock screen user interface 6038. The lock screen user interface 6038 includes a notification 6040 displayed at 10:09 AM, Saturday, June 1, which corresponds to the account of Mom on FIG. 6A to FIG. 6CNotification 6040 invites Jane's account to accept the conditions of the geofence created by Mom's account, thereby authorizing Mom's account to access Jane's device (e.g., 6000B or 6100B, depending on which device is configured to represent Jane's location, such as Figure 6M In some embodiments, Jane can interact with notification 6040 to accept or decline the invitation to authorize geofence notifications. If Jane accepts the invitation, Jane's account continues to share location data with Mom's account and authorizes Mom's account to receive notifications if Jane's device violates the geofence. If Jane declines the invitation (or otherwise does not accept the invitation), Jane's account continues to share location data with Mom's account based on the previous authorization to share location data, but does not authorize Mom's account to receive notifications if Jane's device violates the geofence.

[0210] In some embodiments, an invitation is displayed when one or more components specified by a geofence (e.g., a location component, a time component) are met. Figure 6G An implementation scheme is shown in which a notification 6040 is displayed on a lock screen user interface 6038 when the start time component of the geofence is met. Figure 6G Two instances of Jane's device 6000B are shown, where each instance of Jane's device corresponds to a specific time. Jane's device 6000B-1 represents the state of Jane's device 6000B at 8:59 AM on Monday, June 3. Jane's device 6000B-2 represents the state of Jane's device 6000B at 9:00 AM on Monday, June 3. Figure 6G As shown, notification 6040 is not displayed on Jane's device 6000B until 9:00 AM on Monday, June 3, which corresponds to Figure 6B The start time set in (for example, 9:00AM on weekdays.

[0211] Another example: Figure 6H An implementation scheme for displaying notification 6040 when the location component of a geo-fence is satisfied is shown. Figure 6HTwo instances of a map and Jane's device are shown, wherein each instance of the map corresponds to an instance of Jane's device. Jane's device 6000B-3 represents the state of Jane's device 6000B of the detected location of the device, which is represented by map 6042-1. Jane's device 6000B-4 represents the state of Jane's device 6000B of the detected location of the device, which is represented by map 6042-2. Each instance of a map (e.g., map 6042-1 and map 6042-2) includes a geofence boundary 6044 on the map (representing the location component specified for the geofence) and a representation 6046 of Jane's device 6000B. As shown in map 6042-1, representation 6046 is not located within geofence boundary 6044, indicating that Jane's device 6000B is not located at the location specified by the geofence. Therefore, Jane's device 6000B-3 does not display notification 6040 on the lock screen user interface 6038 because the location of Jane's device 6000B does not satisfy the location component of the geofence. However, as shown in map 6042-2, representation 6046 is within geofence boundary 6044, indicating that Jane's device 6000B is located at the location specified by the geofence. Therefore, Jane's device 6000B-4 displays notification 6040 (e.g., on lock screen user interface 6038) because the location of Jane's device 6000B satisfies the location component of the geofence. In some embodiments, notification 6040 is displayed when both the time component and the location component of the geofence are satisfied.

[0212] In some embodiments, the invitation may be displayed on various electronic devices associated with Jane's account. Fig.6I and Figure 6J An embodiment is shown in which the invitation is displayed on Jane's device 6100B, which is shown as a wearable device, such as a smart watch. Fig.6I In FIG. 6A , the invitation is displayed as notification 6048, which is similar to notification 6040. Notification 6048 includes a text area 6048-1 that displays the invitation Jane accepts. FIG. 6A to FIG. 6C Notification 6048 also includes: an acceptance indication 6048-2, which can be selected to accept the invitation (thereby authorizing Mom's account to receive notifications if Jane's device violates the geofence); and a dismiss indication 6048-3, which can be selected to dismiss the invitation without authorizing Mom's account to receive notifications if Jane's device violates the geofence. In some embodiments, for example Figure 6JAs shown, Jane's device 6100B, in response to detecting selection of acceptance affordance 6048-2, displays user interface 6050. User interface 6050 includes map 6052 showing a representation of the location of the geo-fence and text 6054 indicating the terms of the geo-fence and confirming to Jane that she has accepted the terms of the geo-fence, authorizing Mom's account to receive notifications that Jane (e.g., Jane's device 6100B or Jane's device 6000B) is not at school between 9AM and 3PM on weekdays.

[0213] In some embodiments, notification 6040 (or notification 6048) can be dismissed without immediately accepting the invitation. In such embodiments, the invitation can be dismissed from a location management user interface associated with Jane's account (e.g., Figure 6K In some embodiments, Jane's device 6000B displays the location management user interface 6056 in response to detecting one or more inputs for the notification. For example, Jane's device 6000B displays the location management user interface 6056 in response to detecting one or more inputs for the notification. Figure 6H The notification 6040 is displayed by tapping the input Figure 6K 6056 in the location management user interface.

[0214] exist Figure 6K , Jane's device 6000B displays a location management user interface 6056 that includes a map 6058 showing locations associated with user accounts that are authorized to share location data with Jane's account. For example, map 6058 shows a representation 6060 indicating a location on map 6058 that is associated with Mom's account (e.g., the location of Mom's device 6000A). Location management user interface 6056 also includes a user account area 6062 that includes data related to user accounts that are authorized to share location data with Jane's account. Figure 6K As shown, the user account area 6062 includes an indication of acceptance by FIG. 6A to FIG. 6CItem 6064 of an invitation to Mom's account to create the terms of geofence notification. Item 6064 specifies the terms of the geofence notification and includes an acceptance indication 6064-1 for accepting the terms of the geofence notification and a rejection indication 6064-2 for rejecting the terms of the geofence notification. If Jane accepts the terms of the geofence notification, Jane's account continues to share location data with Mom's account and authorizes Mom's account to receive notifications if Jane's device violates the geofence. If Jane rejects the terms of the geofence notification, Jane's account continues to share location data with Mom's account based on the previous authorization for sharing location data, but does not authorize Mom's account to receive notifications if Jane's device violates the geofence.

[0215] Figure 6K Jane's acceptance of the terms of the geofence notification is depicted. Specifically, Jane's device 6000B detects input 6066 on acceptance affordance 6064-1 and, in response, updates item 6064, such as Figure 6L As shown, text 6064-3 is displayed to Jane confirming that she has accepted the terms of the geo-fencing and indicating that Mom's account is authorized to receive notifications that Jane (e.g., Jane's device 6100B or Jane's device 6000B) is not at school between 9AM and 3PM on weekdays.

[0216] Figures 6L to 6N Various embodiments are shown for managing geofence notifications associated with Jane's account.

[0217] exist Figure 6L , Jane's device 6000B detects input 6068 on the "I" indication 6070, and in response, displays a notification management user interface 6072, such as Figure 6M Notification management user interface 6072 includes location-based notification information associated with Jane's account, such as location information 6074 indicating a detected location associated with Jane's account (e.g., the location of Jane's device 6000B), map settings options 6076, and device options 6078 for selecting a specific device for determining a location associated with Jane's account. For example, in Figure 6M , device option 6078 indicates that Jane's location is associated with the location of Jane's device 6000B. However, in some embodiments, device option 6078 may be updated to select Jane's device 6100B or other electronic device associated with Jane's user account so that the location of the selected device is associated with Jane's location.

[0218] like Figure 6MAs shown, the notification management user interface 6072 also includes an authorized geo-fence notification list 6080, which indicates that Jane's account has authorized geo-fence notifications for other user accounts. Figure 6M As shown, the geo-fence notification list is grouped by the user account that has authorized the geo-fence notification. For example, the geo-fence notification list 6080-1 represents a group of four geo-fence notifications that have been authorized for the mom's account. Similarly, the geo-fence notification list 6080-2 represents a group of two geo-fence notifications that have been authorized for the dad's account, and the geo-fence notification list 6080-3 represents a single geo-fence notification that has been authorized for the brother's account.

[0219] exist Figure 6M , Jane's device 6000B detects input 6082 on geofence notification list 6080-1, and in response, displays notification detail user interface 6084 showing details of geofence notifications that have been authorized for Mom's account, such as Figure 6N shown.

[0220] Notification details user interface 6084 includes additional details of geofence notifications authorized for Mom's account. Figure 6N 6086 includes representations of authorized geofence notifications created by Jane's account. These correspond to geofence notifications created by Jane's account (e.g., in a format similar to that described above with respect to Figure 6B 000B is not at home between 11PM and 7AM.

[0221] Notification details user interface 6084 also includes an area 6088 with representations of authorized geofence notifications created by Mom's account. These correspond to those created by Mom's account (e.g., in a manner similar to that described above with respect to Figure 6B The method discussed above) and the geo-fence notification authorized by Jane's account, so that when the conditions for geo-fence notification are met, Mom's account is notified. For example, 6088-1 corresponds to FIG. 6A to FIG. 6C6088-2 corresponds to a geofence notification created by Mom's account (and authorized by Jane's account) when Jane's device 6000B is not at school between 9AM and 3PM. Additionally, representation 6088-3 corresponds to a geofence notification created by Mom's account (and authorized by Jane's account) when Jane's device 6000B arrives home.

[0222] In some embodiments, the geo-fence notifications represented in the notification details user interface 6084 can be deauthorized by Jane's account and removed from the notification details user interface 6084. For example, in response to Jane's device 6000B detecting a swipe input on representation 6088-2, Jane's account removes authorization for the corresponding geo-fence notification. As a result, Jane's device 6000B removes representation 6088-2 from the notification details user interface 6084, and updates the geo-fence notification list 6080-1 to reflect the removal of the geo-fence notification (e.g., updating the geo-fence notification list 6080-1 to indicate that a group of three geo-fence notifications are authorized for Mom's account).

[0223] FIG. 6O to FIG. 6U Various embodiments are depicted showing how a detected change in Jane's location (e.g., the location of Jane's device 6000B) may or may not satisfy the Figure 6K Authorized by Jane's account in FIG. 6A to FIG. 6C , and shows a notification that is displayed (e.g., on Mom's device 6000A, Jane's device 6000B, or both) due to a detected change in location violating the geofence.

[0224] FIG. 6O to FIG. 6Q An embodiment is shown in which Jane's location violates the geo-fence because Jane's device 6000B is not located at the designated location of the geo-fence (e.g., school) at the designated start time (e.g., 9AM on a weekday). Fig.6O Includes map 6090, which is similar to Figure 6H 6042 shown in FIG. 6090 includes a representation 6092 of Jane's device 6000B and a geo-fence boundary 6094. Fig.6O As shown, the representation 6092 of Jane's device was outside the geo-fence boundary 6094 at 9:00 AM on Monday. Therefore, Jane's location violates the geo-fence. Therefore, Mom's device 6000A displays a notification 6096 (e.g., on the lock screen user interface 6095) indicating that Jane did not arrive at school at 9 AM.

[0225] In some embodiments, Jane's device 6000B displays a notification 6098 (e.g., on the lock screen user interface 6038) to prompt Jane that she has violated the geo-fence and notifies Mom's account of the violation. In some embodiments, notification 6098 is displayed only when Jane violates the geo-fence for the first time.

[0226] In some embodiments, Mom's device 6000A may display different user interfaces in response to detecting different inputs on a displayed notification (e.g., notification 6096, notification 6120, or notification 6122). For example, in some embodiments, in response to detecting a tap gesture input on a notification, Mom's device 6000A displays location management user interface 6005. Figure 6S An example of this process is described in more detail. In some embodiments, in response to detecting a long press input on the notification, Mom's device 6000A displays a pop-up user interface showing various options available in response to Jane violating the geofence. Fig.6O An example of this process is described in more detail. It should also be understood that notifications can be displayed as other user interface objects, such as banners. Notifications can also be displayed on user interfaces other than the lock screen user interface. For example, a user interface can be associated with an application operating on the electronic device 6000, and the notification is displayed as a banner that appears above the user interface at the top of the display 6002.

[0227] like Fig.6O As shown, Mom's device 6000A detects a long press input 6104 on notification 6096 and, in response, displays a pop-up user interface 6106, such as Figure 6P Pop-up user interface 6106 includes various selectable options for responding to notification 6096. For example, pop-up user interface 6106 includes map option 6108, contact option 6110, mute option 6112, "notify when Jane arrives" option 6114, and delete option 6116. Map option 6108 includes map 6108-1, which is similar to Fig.6O Map 6090 is shown with a representation 6108-2 of Jane's device 6000A and geo-fence boundary 6108-3. Map option 6108 shows Jane's location on the map (eg, when notification 6096 is displayed or when input 6104 is detected).

[0228] In some embodiments, the pop-up user interface 6106 is a user interface that displays a set of options without completely launching an application for executing the options. However, the options available in the pop-up user interface 6106 can be selected to launch an application for executing the selected options. For example, in some embodiments, the map option 6108 corresponds to an option for launching an application for displaying a map user interface showing a real-time representation of Jane's location on an expanded map. For example, in response to detecting a selection of the map option 6108, Mom's device 6000A displays the location management user interface 6005 to show a map user interface (e.g., similar to the map user interface) that depicts a real-time representation of Jane's location on a map. Figure 6S Map 6130 shown in location management user interface 6005 shown).

[0229] In some embodiments, in response to detecting selection of the contact option 6110, Mom's device 6000A displays one or more options for contacting Jane's device 6000B (e.g., via a phone call, instant message, email, or video communication session).

[0230] In some embodiments, in response to detecting selection of the mute option 6112, Mom's device 6000A does not display reminders for the geofence for the remainder of the day. This may be useful for scenarios where Mom knows that Jane's location will again violate or will continue to violate the geofence (e.g., Jane is on vacation with Mom) and Mom wishes not to be notified of any such future violations for the remainder of the day.

[0231] In some embodiments, in response to detecting selection of the delete option 6116, Mom's device 6000A dismisses the notification 6096 and, in some embodiments, deletes the geofence entirely.

[0232] In some embodiments, in response to detecting a selection of the "Notify when Jane arrives" option 6114, Mom's device 6000A dismisses notification 6096 and displays the notification at a later time if Jane's location matches the location specified under the geo-fence conditions. This may be useful in situations where Mom knows Jane will be late for school (e.g., Jane has a doctor's appointment) but wants to know that Jane eventually makes it to school as expected. Figure 6P and Figure 6Q An embodiment is shown in which the "Notify when Jane arrives" option 6114 is selected.

[0233] like Figure 6P As shown, Mom's device 6000A detects input 6118 on the "Notify when Jane arrives" option 6114 at 9:00 AM. Figure 6QJane is shown arriving at school one hour later (e.g., 10:00 AM), and Mom's device 6000A displays a notification 6120 informing Mom that Jane has arrived at school. In some embodiments, Jane's device 6000B does not display any notifications in this scenario (e.g., the lock screen user interface 6038 does not include notifications).

[0234] Figure 6R and Figure 6S An embodiment is shown in which Jane's location violates the geo-fence because Jane's device 6000B leaves the geo-fence's designated location (e.g., school) before a designated end time (e.g., 3PM on a weekday). Figure 6R As shown, the representation 6092 of Jane's device 6000B is outside the geo-fence boundary 6094 at 2:30 PM on Monday. Therefore, Jane's location violates the geo-fence. Therefore, Mom's device 6000A displays a notification 6122 indicating that Jane left school before 3 PM.

[0235] In some embodiments, Jane's device 6000B displays notification 6124 to prompt Jane that she has violated the geo-fence and notifies mom's account of the violation. In some embodiments, notification 6124 is displayed only when Jane violates the geo-fence for the first time.

[0236] As described above, in some embodiments, Mom's device 6000A may display different user interfaces in response to detecting different inputs on the displayed notification. Figure 6R , Mom's device 6000A detects a tap gesture input 6126 on notification 6122, and in response, displays a location management user interface 6005 associated with Mom's account, such as Figure 6S As shown. Location management user interface 6005 is similar to location management user interface 6056, which is a location management user interface associated with Jane's account. Therefore, Mom's device 6000A can perform operations similar to those discussed above with respect to location management user interface 6056. For example, location management user interface 6005 includes a map 6130 showing locations associated with user accounts that are authorized to share location data with Mom's account, including a representation 6132 indicating a location on map 6130 associated with Jane's account (e.g., the location of Jane's device 6000B), and a geo-fence boundary 6134. As shown Figure 6S As shown, map 6130 shows that Jane's location is outside the boundaries of the geofence.

[0237] The location management user interface 6005 also includes an item 6128 associated with Jane's account. In some embodiments, in response to detecting the selection of item 6128, Mom's device 6000A displays Jane's account information 6004 (e.g., see Fig. 6A ).

[0238] Figure 6T An embodiment is shown in which Jane's location is within the boundaries of the geo-fence during the specified time range and therefore does not violate the geo-fence. Figure 6T As shown, representation 6092 of Jane's device 6000B is within geofence boundary 6094 at 2:30 PM on Monday. Since the geofence is active from 9:00 AM to 3:00 PM on weekdays, Jane's presence at school meets the constraints of the geofence. Therefore, Jane does not violate the geofence. Therefore, neither Mom's device 6000A nor Jane's device 6000B displays any notification regarding the geofence violation. Therefore, lock screen user interface 6095 and lock screen user interface 6038 do not include any notifications.

[0239] Figure 6U An embodiment is shown in which Jane's location is outside the boundaries of the geo-fence, but because the time is outside the specified range, Jane has not violated the geo-fence. Figure 6U As shown, representation 6092 of Jane's device 6000B was outside geofence boundary 6094 at 3:30 PM on Monday. Because the geofence was active from 9:00 AM to 3:00 PM on weekdays, Jane did not violate the geofence. Therefore, neither Mom's device 6000A nor Jane's device 6000B displays any notification regarding the geofence violation. Therefore, lock screen user interface 6095 and lock screen user interface 6038 do not include any notifications.

[0240] It should be understood that one or more of the operations disclosed herein (including those discussed below with respect to methods 700 and 800) may be performed across various combinations of electronic devices discussed herein. For example, in some embodiments, Jane's device 6000B (or Jane's device 6100B) evaluates the location data of Jane's device, determines when the geofence is violated, and causes a corresponding notification to be displayed at Mom's device 6000A and optionally at Jane's device 6000B. For example, Jane's device may send a notification directly to Mom's device 6000A for display, or may send a notification indirectly by sending information to a server, which in turn causes the notification to be displayed at Mom's device 600. In some embodiments, Mom's device 6000A evaluates the location data of Jane's device, determines when the geofence is violated, and causes a corresponding notification to be displayed at Mom's device 6000A and optionally at Jane's device 6000B (e.g., directly or indirectly through a server). In some embodiments, the server evaluates the location data of Jane's device, determines when the geofence is violated, and causes a corresponding notification to be displayed at Mom's device 6000A and, optionally, at Jane's device 6000B.

[0241] Figure 7 700 is a method flow chart illustrating a method for managing location-related communications of electronic devices associated with a user account using an electronic device according to some embodiments. Method 700 is performed at a device (e.g., 100, 300, 500, 6000, or 6100B) having a display (e.g., 112). Some operations in method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0242] As described below, method 700 provides an intuitive way to manage location-related communications of electronic devices associated with a user account. The method reduces the cognitive burden of managing location-related communications of electronic devices associated with a user account, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to more quickly and efficiently manage location-related communications of electronic devices associated with a user account saves power and increases the interval between battery charges.

[0243] When an electronic device (e.g., 6000; 6100) is associated with a first user account (e.g., Jane's account), the first user account shares the location of the electronic device with one or more user accounts other than the first user account, and the electronic device performs (702) the steps described below.

[0244] The electronic device receives (704) an indication that a second user account (e.g., mom's account) (e.g., a remote user or device that has been authorized (e.g., by a first user account associated with the electronic device) to receive location data for the electronic device) is requesting to be notified of a change in the location of the electronic device relative to a first geographic location (e.g., school) (e.g., a physical address, coordinates, a defined area, or a geographic landmark) that satisfies a set of criteria (e.g., a set of location-based criteria) (e.g., a set of criteria evaluated relative to a predetermined time period (e.g., a time range)) (e.g., data associated with the request; received directly from an external electronic device associated with the second user account; received from a location tracking server that receives the request from the external electronic device). In some embodiments, the time range is set by the second user account (e.g., using an external electronic device associated with the second user account). In some embodiments, the set of criteria is met when the current location of the electronic device does not match (or is transitioning from a match to a mismatch) with the first geographic location. In some embodiments, the set of criteria is met when the current location of the electronic device matches (or transitions from a mismatch to a match) with the first geographic location. In some embodiments, the set of criteria is evaluated based on the current location of the electronic device within a predetermined time period.

[0245] In some embodiments, the set of criteria includes criteria that are satisfied when the location of the electronic device (e.g., 6000B; 6100B) does not have a predefined relationship with a first geographic location (e.g., the electronic device is not located in the first geographic location) within a time range (e.g., a time range specified by a first user account) (e.g., a time range specified by a second user account).

[0246] In some embodiments, the method further includes: when the electronic device (e.g., 6000B; 6100B) is associated with a first user account, the first user account shares the location of the electronic device with one or more user accounts other than the first user account, and when evaluating (e.g., by the electronic device; by the server; by a second electronic device associated with a second user account) the location of the electronic device relative to the first geographic location and time range, one or more of the following steps are performed. Based on determining that the location of the electronic device does not have a predefined relationship with the first geographic location within the time range (e.g., the electronic device is not located at the first geographic location at any time within the time range), a prompt (6096; 6098; 6122; 6124) is generated indicating that the location of the electronic device does not have a predefined relationship with the first geographic location. In some embodiments, generating the prompt includes displaying the prompt on the electronic device. In some embodiments, generating the prompt includes causing the prompt to be displayed on an electronic device associated with the second user account (e.g., mom's device 6000A). Based on determining that the location of the electronic device does not have a predefined relationship with the first geographic location at a time outside the time range (e.g., the electronic device is not located at the first geographic location at a time outside the time range), abandoning generating a prompt indicating that the location of the electronic device does not have a predefined relationship with the first geographic location (e.g., see Figure 6U ). Selectively generating a prompt indicating that the location of the electronic device does not have a predefined relationship with the first geographic location provides feedback to the user to indicate when the evaluated condition fails to meet the specified criteria. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0247] In some embodiments, when the electronic device is associated with a first user account, the first user account shares the location of the electronic device with one or more user accounts other than the first user account, and when evaluating (e.g., by the electronic device; by the server; by a second electronic device associated with a second user account) the location of the electronic device relative to the first geographic location and time range, the method further includes: based on determining that the location of the electronic device has a predefined relationship with the first geographic location within the time range (e.g., the electronic device is located at the first geographic location within the time range), abandoning generating a prompt indicating that the location of the electronic device does not have a predefined relationship with the first geographic location (e.g., see Figure 6T). When the location of the electronic device has the predefined relationship within the time range, forgoing generating a prompt indicating that the location of the electronic device does not have the predefined relationship with the first geographic location provides feedback to the user to indicate when the evaluated condition fails to meet the specified location criteria within the specified time range. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0248] In some embodiments, displaying a notification indicating that the second user account is requesting to be notified of changes in the location of the electronic device relative to the first geographic location that satisfy the set of criteria occurs at a time corresponding to the time range (e.g., at the beginning of the time range or a short time after the beginning) (e.g., see Figure 6G In some embodiments, the notification is displayed only when the start time of the time range is reached for the first time. In some embodiments, displaying the notification at a time that matches the start time in the time range provides an enhanced layer of security and preserves the privacy of the tracked user by providing information that the location of the device is being tracked, which is particularly useful in scenarios where a malicious actor has access to the tracked user device and the malicious actor sets geofence and time period parameters and confirms the geofence and time period on the tracked user device without the knowledge or consent of the tracked user.

[0249] In some embodiments, the set of criteria includes criteria that are met when the location of the electronic device does not match (e.g., or is transitioning from a match to a mismatch) the first geographic location. In some embodiments, when the location of the electronic device is not in the first geographic location (e.g., within a time range) (e.g., see Fig.6O and Figure 6R ), the second user account request is notified.

[0250] In some embodiments, the set of criteria includes when the location of the electronic device is consistent with the first geographic location (e.g., see Figure 6Q ) matches (e.g., or transitions from a mismatch to a match). In some embodiments, when the location of the electronic device does not match the first geographic location (e.g., within a time range), the second user account is notified (e.g., 6096), and in response, the second user account requests to be notified (e.g., see 6096) when the electronic device reaches the first geographic location (e.g., within a time range). Figure 6P 6118 by selecting the "Notify when Jane arrives" option 6114).

[0251] Method 700 also includes, after the electronic device receives an indication that the second user account is requesting to be notified of a change in the electronic device's location relative to the first geographic location that satisfies the set of criteria, the electronic device performing ( 706 ) one or more of the following steps.

[0252] Based on determining that a set of notification criteria are met, the set of notification criteria includes criteria that are met when an indication has been received that a second user account is requesting to be notified, the electronic device displays (708) a notification (e.g., 6040, 6048) (e.g., a prompt, a banner) via a display device indicating that the second user account is requesting to be notified of changes in the location of the electronic device relative to the first geographic location that meet the set of criteria. In some embodiments, the indication includes text identifying the second user account and / or text describing the set of criteria. In some embodiments, the set of notification criteria is met by receiving the indication. In some embodiments, after receiving the indication, the set of notification criteria is met when the location of the electronic device relative to the first geographic location meets the set of criteria. Displaying a notification indicating that the second user account is requesting to be notified of changes in the location of the electronic device relative to the first geographic location that meet the set of criteria provides feedback to the user indicating that the remote user account is requesting to use location data for notification purposes. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0253] In some embodiments, the one or more user accounts other than the first user account include a second user account (e.g., mom's account) (e.g., the first user account shares the location of the electronic device with the second user account), and the method further includes one or more of the following steps. After displaying a notification (e.g., 6040, 6048) indicating that the second user account is requesting to be notified of a change in the location of the electronic device relative to the first geographic location that satisfies the set of criteria, and before authorizing (granting) the request to be notified of a change in the location of the electronic device relative to the first geographic location that satisfies the set of criteria (e.g., in some embodiments, after explicitly denying the request to notify the electronic device of a change relative to the first geographic location that satisfies the set of criteria): sharing the location of the electronic device with the second user account. In some embodiments, even after the electronic device denies the request to notify the second user account that the change in the electronic device relative to the first geographic location satisfies the set of criteria, the first user account continues to share the location of the electronic device with the second user account. After displaying the notification, and before authorizing the request to be notified (or after explicitly denying the request), sharing the location of the electronic device with the second user account allows the user to continue to share location data with the second user account without requiring the user to provide additional input to resume location data sharing with the second user account. This reduces the number of inputs required to resume location data shared with the second user account. Reducing the number of inputs required to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), thereby further reducing power usage and extending the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0254] In some embodiments, after displaying a notification (e.g., 6040, 6048) indicating that the second user account is requesting to be notified of changes in the location of the electronic device (e.g., 6000B, 6100B) relative to the first geographic location that satisfy the set of criteria, the method includes one or more of the following steps. Based on determining that the current location of the electronic device relative to the first geographic location satisfies the set of criteria (e.g., within the time range) and based on determining that authorization has been received (e.g., explicit authorization for a specific request; prior authorization based on the identity of the requesting device) to notify the second user account when the location of the electronic device relative to the first geographic location satisfies the set of criteria, notifying (e.g., displaying notification 6096) (e.g., transmitting data to a device associated with the second user account; transmitting data to a notification server, which notifies the second user account) the second user account that the current location of the electronic device relative to the first geographic location satisfies the set of criteria (e.g., within the time range (e.g., the location of the electronic device is not at the first geographic location at any time within the time range)). Based on determining that the current location of the electronic device relative to the first geographic location satisfies the set of criteria, and based on determining that authorization has been received to notify the second user account when the location of the electronic device relative to the first geographic location does not satisfy the set of criteria, foregoing notifying the second user account that the current location of the electronic device relative to the first geographic location satisfies the set of criteria. When the set of criteria is met and authorization has been received to notify the second user account, notifying the second user account that the current location of the electronic device relative to the first geographic location satisfies the set of criteria, providing an enhanced layer of security and preserving the privacy of the first user account by requiring authorization from the second user account to receive notifications related to the location associated with the first user account. Similarly, when the set of criteria is met and authorization has not been received to notify the second user account, foregoing notifying the second user account that the current location of the electronic device relative to the first geographic location satisfies the set of criteria, providing an enhanced layer of security and preserving the privacy of the first user account by requiring authorization from the second user account to receive notifications related to the location associated with the first user account.

[0255] In some embodiments, when the location of the electronic device has a predefined relationship with the first geographic location (e.g., when the electronic device is located in the first geographic location) (e.g., see Figure 6H), a notification indicating that the second user account is requesting to be notified of changes in the location of the electronic device relative to the first geographic location that satisfy the set of criteria (6040, 6048) occurs. In some embodiments, the notification is displayed only the first time the electronic device is located in the first geographic location. In some embodiments, displaying the notification when the device has a predefined relationship with the first geographic location provides an enhanced layer of security and maintains the privacy of the tracked user by providing information that the location of the device is being tracked, which is particularly useful in scenarios where a malicious actor has access to the tracked user device and the malicious actor sets geo-fence and time period parameters and confirms the geo-fence and time period on the tracked user device without the knowledge or consent of the tracked user.

[0256] In some embodiments, in response to receiving an indication that a second user account is requesting to be notified of a change in the location of the electronic device relative to the first geographic location that satisfies the set of criteria, displaying a notification (e.g., 6040, 6048) indicating that the second user account is requesting to be notified of a change in the location of the electronic device relative to the first geographic location that satisfies the set of criteria occurs (e.g., see Fig. 6F In some embodiments, the second user account (e.g., the mother's account) sets the conditions of the geo-fence (e.g., FIG. 6A to FIG. 6C ), and the electronic device receives the indication (and displays a notification) shortly (e.g., immediately) after the geofence is created.

[0257] In some embodiments, after displaying a notification indicating that the second user account is requesting to be notified of changes in the location of the electronic device relative to the first geographic location that meet the set of criteria (e.g., 6040, 6048), the method further includes one or more of the following steps. Based on determining that authorization has been received to notify the second user account when the location of the electronic device relative to the first geographic location meets the set of criteria (e.g., explicit authorization for a specific request; pre-authorization based on the identity of the requesting device), and when a second set of notification criteria is met, the second set of notification criteria includes a first criterion that is met when the set of criteria is met (e.g., the current location of the electronic device relative to the first geographic location meets the set of criteria (e.g., within a time range)), a notification (e.g., 6098, 6124) indicating that the location of the electronic device relative to the first geographic location (e.g., current location) meets the set of criteria is displayed by a display device (e.g., 6002). In some embodiments, the notification includes text identifying the second user account and / or text describing the set of criteria. In some embodiments, a notification is displayed to notify the second user account that a notification about the location of the user's electronic device is being sent to the second user account. This provides an element of privacy for the user by making the user aware of instances in which the user's personal information (e.g., location information) is shared with other user accounts. Based on determining that authorization has been received to notify a second user account when the location of the electronic device relative to the first geographic location satisfies the set of criteria, and that a second set of notification criteria is not satisfied, forgoing displaying a notification indicating that the location of the electronic device relative to the first geographic location (e.g., current location) satisfies the set of criteria.

[0258] In some embodiments, the second set of notification criteria includes second criteria that are met when the set of criteria are met for the first time (e.g., the notification is only displayed the first time the set of criteria are met).

[0259] In some embodiments, when the current location of the electronic device is within the start time of the time range (e.g., see Fig.6O ) does not have a predefined relationship with the first geographic location (for example, the electronic device is not located at the first geographic location), the set of criteria is met.

[0260] In some embodiments, after the electronic device receives an indication that a second user account (e.g., mom's account) is requesting to be notified of changes in the electronic device's location relative to the first geographic location that satisfy the set of criteria, and based on determining that the set of notification criteria is not satisfied (e.g., after receiving the indication, the current location of the electronic device relative to the first geographic location (e.g., 6000B, 6100B) fails to satisfy the set of criteria), the electronic device abandons (710) displaying a notification indicating that the second user account is requesting to be notified of changes in the electronic device's location relative to the first geographic location that satisfy the set of criteria (e.g., see Figure 6GJane's device 6000B-1 in (see, for example, Figure 6H Jane's device 6000B-3).

[0261] In some embodiments, the method also includes displaying (e.g., before receiving the indication; after receiving the indication) a notification management interface (e.g., 6072) via a display device (e.g., 6002), the notification management interface including a group (e.g., 6080) of one or more indications (e.g., 6080-1, 6080-2, 6080-3), each indicating a request to be notified of a change in the position of the electronic device relative to a geographic location.

[0262] In some embodiments, the notification management interface includes location-based notification information (e.g., 6074, 6076, 6078) for a first user account (e.g., Jane's account) (e.g., address information, map settings, options for sharing location information associated with the first user account).

[0263] In some embodiments, according to the corresponding (e.g., the user account making the request to be notified; the user account to be notified) for each indication in the set of one or more indications (e.g., in Figure 6M In some embodiments, the group of one or more indications includes a user account corresponding to the user account corresponding to the group of indications, and a representative indication of the number of notifications associated with the user account. Organizing the group of one or more indications according to the user account corresponding to each indication in the group of one or more indications provides an organized and easily navigable user interface that reduces the number of inputs required for the user to locate the indication. Reducing the number of inputs required for the user to locate the indication enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which in addition reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0264] In some embodiments, the group of one or more indications that each corresponds to a request to be notified of a change in the location of the electronic device relative to a geographic location includes one or more of the following. A first subset of one or more indications (e.g., 6086-1, 6086-2) that each corresponds to a request to be notified of a change in the geographic location of the electronic device created by a first user account (e.g., Jane's account). A second subset of one or more indications (e.g., 6088-1, 6088-2) that each corresponds to a request to be notified of a change in the geographic location of the electronic device created by a user account other than the first user account (e.g., Mom's account) (e.g., a user account in one or more user accounts other than the first user account). In some embodiments, a first subset of one or more indications is grouped together (e.g., in area 6086), and a second subset of one or more indications is grouped together (e.g., in area 6088) (e.g., and separated from the first subset of one or more indications). Grouping the first and second subsets of one or more indications together provides an organized and easily navigable user interface that reduces the number of inputs required for a user to locate an indication in each subset. Reducing the number of user inputs required for positioning indications enhances device operability and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0265] In some embodiments, the method further includes one or more of the following steps. While displaying a notification management interface (e.g., notification details user interface 6084) (e.g., in some embodiments, notification management user interface 6072 includes notification details user interface 6084), a first set of one or more inputs is received, the first set of one or more inputs corresponding to a request to cancel authorization to be notified of a first request for a change in the position of the electronic device relative to the geographic location. In response to receiving the first set of one or more inputs: removing authorization for notification of a change in the position of the electronic device relative to the geographic location. In some embodiments, removing authorization for notification includes stopping displaying an indication in the group of one or more indications (e.g., 6086-1, 6086-2, 6088-1, 6088-2, 6080-1, 6080-2, 6080-3), the indication corresponding to the first request to be notified of a change in the position of the electronic device relative to the geographic location. In some embodiments, the first set of one or more inputs is a swipe input. In some embodiments, the first set of one or more inputs is a swipe input on an indication of the group of one or more indications, the swipe input corresponding to a request to be notified of a change in the position of the electronic device relative to the geographic location, followed by a tap gesture on the delete affordance. Removing authorization for notifications of changes in the location of the electronic device relative to a geographic location in response to receiving a first set of one or more inputs provides a quick and convenient method of reducing the number of inputs required to remove authorization for notifications. Reducing the number of inputs required to remove authorization for notifications enhances the operability of the device and makes the user device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), thereby further reducing power usage and extending the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0266] It should be noted that the process described above with respect to method 700 (eg Figure 7 ) also applies in a similar manner to the methods described below. For example, method 800 optionally includes one or more features of the various methods described above with reference to method 700. For example, after the notification displayed in step 708 has been accepted, the steps of method 800 are performed. For the sake of brevity, these details are not repeated below.

[0267] Figure 8 800 is a method flow chart illustrating a method for managing location-related communications of electronic devices associated with a user account using an electronic device according to some embodiments. Method 800 is performed at a device (e.g., 100, 120, 300, 310, 500, 516, 6000, 6100B). Some operations in method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0268] As described below, method 800 provides an intuitive way to manage location-related communications of electronic devices associated with a user account. The method reduces the cognitive burden of managing location-related communications of electronic devices associated with a user account, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to more quickly and efficiently manage location-related communications of electronic devices associated with a user account saves power and increases the interval between battery charges.

[0269] Method 800 includes performing one or more of the following steps on an electronic device (e.g., a server) (e.g., an electronic device with a display device (e.g., a touch-sensitive display)) (e.g., Jane's device 6000B; Jane's device 6100B) (e.g., Mom's device 6000A). In some embodiments, the electronic device is associated with a user account that evaluates the current location (e.g., a child's account; Jane's account). In some embodiments, the electronic device is associated with a second user account (e.g., a parent's account, a mom's account), which is authorized to receive location data of an electronic device (e.g., Jane's device 6000B; Jane's device 6100B) associated with a user account (e.g., a child's user account) that evaluates the current location. In some embodiments, the electronic device is a server that is authorized to receive location data of an electronic device (e.g., Jane's device 6000B; Jane's device 6100B) associated with a user account (e.g., Jane's account) that evaluates the current location.

[0270] Method 800 includes performing (802) one or more of the following steps when evaluating (e.g., tracking or monitoring) a current location (e.g., a current location of an electronic device associated with the user account) associated with a user account (e.g., Jane's account) relative to a geographic location (e.g., a school) (e.g., a physical address, coordinates, a defined area, or geographic landmark) and a time range (e.g., between 9:00 AM and 3:00 PM on weekdays) (e.g., a time range specified by the user account) (e.g., a time range specified by a second user account (e.g., Mom's account)).

[0271] Based on determining that the current location associated with the user account does not have a predefined relationship with the geographic location within the time range (e.g., the electronic device associated with the user account is not located at the geographic location at any time within the time range), the electronic device generates (804) an indication that the current location associated with the user account (e.g., Jane's account) does not have a predefined relationship with the geographic location (e.g., school) (e.g., see Fig.6O )(See, for example, Figure 6R ) (e.g., notifications such as pop-ups or banners) (e.g., 6096, 6098, 6122, 6124). In some embodiments, generating a prompt includes displaying a prompt on an electronic device (e.g., when the electronic device is associated with a user account (e.g., a child account) or associated with a second user account (e.g., a parent account)). In some embodiments, generating a prompt includes causing an external electronic device to display a prompt (e.g., when the electronic device is a server). In some embodiments, the external electronic device is an electronic device associated with a user account. In some embodiments, the external electronic device is an electronic device associated with a second user account. When the current location does not have a predefined relationship within a time range, a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location is generated, and feedback indicating that the evaluated condition violates the specified criteria is provided to the user. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0272] In some embodiments, when the current location associated with the user account matches (e.g., or transitions from not matching to matching) a geographic location (e.g., see Figure 6T ), the user account has a predefined relationship with the geographic location.

[0273] In some embodiments, the reminder is on the first date (e.g., Monday, June 3, if Fig.6O 6104 on notification 6096), and the prompt includes a first user interface object (e.g., a "Mute today" affordance; mute option 6112) that, when selected, initiates a process for preventing display of subsequent prompts that were generated on a first date and associated with an evaluation of a current location associated with the user account within that time range (future prompts for geofences and time ranges are not displayed for the remainder of the day when the first user interface object is selected). In some embodiments, the first user interface object is displayed in response to a long press input 6104 on notification 6096.

[0274] In some embodiments, the prompt includes a second user interface object (e.g., a "Contacts" affordance; Contacts option 6110) that, when selected, initiates a process for contacting (e.g., calling, emailing, instant messaging, video conferencing) an external electronic device (e.g., Jane's device 6000B; Jane's device 6100B) associated with a user account (e.g., Jane's account). In some embodiments, the second user interface object is displayed in response to a long press input 6104 on notification 6096.

[0275] In some embodiments, the prompt includes a third user interface object (e.g., a "Notify when Jane arrives" affordance; a "When Jane Arrives" option 6114) that, when selected, initiates a process for: when evaluating the current location associated with the user account within a time range relative to the geographic location, and based on determining that the current location associated with the user account has a predefined relationship with the geographic location (e.g., within the time range) (e.g., at a time outside the time range), generating a second prompt (e.g., 6120), the second prompt indicating that the current location associated with the user account has a predefined relationship with the geographic location (e.g., when the electronic device associated with the user account is at the geographic location or transitions from a location that does not match the geographic location to a location that matches the geographic location, generating a second prompt (e.g., see Figure 6Q ). In some embodiments, in response to a long press input 6104 on notification 6096, a third user interface object is displayed. Generating a second prompt indicating that the current location associated with the user account has a predefined relationship with the geographic location provides feedback to the user indicating that the condition being evaluated was previously not met and is now met. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0276] In some embodiments, the prompt includes a fourth user interface object (e.g., a map icon representation; map option 6108), which, when selected, initiates a process for displaying a map representing a current location associated with the user account (e.g., associated with an external electronic device associated with the user account). In some embodiments, the prompt includes a representation of a map (e.g., 6108-1) (e.g., the fourth user interface object is a representation of a map representing a location associated with the user account), and the map displayed in response to selection of the fourth user interface object includes an option to expand the map or view an expanded map. In some embodiments, the fourth user interface object is displayed in response to a long press input 6104 on notification 6096.

[0277] In some embodiments, a prompt (e.g., 6096) is generated when the current location associated with the user account does not match the geographic location at the start time of the time range (e.g., a prompt is generated when the time period begins and the electronic device associated with the user account is not located within the geofence) (e.g., see Fig.6O ). In some embodiments, determining that the current location associated with the user account does not have a predefined relationship with the geographic location within the time range includes determining that the current location associated with the user account does not match the geographic location at the start time of the time range.

[0278] In some embodiments, when the current location associated with the user account changes from a geographic location with a predefined relationship within the time range to a geographic location that does not have a predefined relationship within the time range (for example, when the electronic device associated with the user account leaves the geofence within the time period), a prompt (for example, 6122, 6124) is generated (for example, see Figure 6R ). In some embodiments, determining that the current location associated with the user account does not have a predefined relationship with the geographic location within the time range includes determining that the current location associated with the user account has transitioned from having a predefined relationship with the geographic location within the time range to not having a predefined relationship with the geographic location within the time range.

[0279] Based on determining that the current location associated with the user account does not have a predefined relationship with the geographic location at times outside the time range (e.g., the electronic device associated with the user account is not located at the geographic location at times outside the time range), the electronic device forgoes (806) generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location (e.g., see Figure 6U). When the current location does not have the predefined relationship at a time outside the time range, forgoing generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location, providing feedback to the user indicating that the evaluated condition does not violate the specified criteria (by not generating a prompt). Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0280] In some embodiments, when evaluating a current location associated with a user account (e.g., Jane's account) relative to a geographic location (e.g., school) and a time range (e.g., between 9:00 AM and 3:00 PM on weekdays), based on determining that the current location associated with the user account has a predefined relationship with the geographic location at a time outside the time range (e.g., the electronic device associated with the user account is located at the geographic location at a time outside the time range) (e.g., Jane's device 6000B is located at school at 3:30 PM on Monday), the electronic device abandons (808) generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location. When the current location does not have a predefined relationship at a time outside the time range, the electronic device abandons generating a prompt indicating that the current location associated with the user account has a predefined relationship with the geographic location, and provides feedback to the user (by not generating a prompt) indicating that the condition being evaluated does not violate the specified criteria. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0281] In some embodiments, when evaluating (e.g., tracking or monitoring) a current location associated with a user account relative to a geographic location and a time range, based on determining that the current location associated with the user account has a predefined relationship with the geographic location within the time range (e.g., the electronic device associated with the user account was located at the geographic location at a time within the time range), the electronic device abandons (810) generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location (e.g., see Figure 6T). When the current location has a predefined relationship at a time within the time range, forgoing generating a prompt indicating that the current location associated with the user account does not have a predefined relationship with the geographic location, providing feedback to the user indicating that the condition being evaluated does not violate the specified criteria (by not generating a prompt). Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0282] In some embodiments, the electronic device (e.g., 6000) has a display device (e.g., 6002) (e.g., a touch-sensitive display) (e.g., at an electronic device associated with a second user account (e.g., Mom's device 6000A)), and the method also includes performing one or more of the following steps. Before evaluating the current location associated with a user account (e.g., Jane's account) relative to a geographic location and a time range (e.g., and when the user account shares the location of the electronic device associated with the user account with one or more user accounts other than the user account (e.g., Mom's account)), the following is displayed via the display device: 1) a location user interface object (e.g., 6016-2), which, when selected, initiates a process for specifying a geographic location; 2) a date user interface object (e.g., 6020-1 to 6020-7), which, when selected, initiates a process for specifying a date component of the time range; and 3) a time user interface object (e.g., 6018-1, 6018-2), which, when selected, initiates a process for specifying a time component of the time range. In some embodiments, the boundaries of the geofence are set by detecting a user selection of a location user interface object. In some embodiments, this includes receiving user input, which includes location information, such as an address, coordinates, a defined area on a map, or a geographical landmark. In some embodiments, the user can view the geographic location on the map and manipulate the map to adjust the boundaries of the geofence (e.g., by adjusting the zoom level of the map). In some embodiments, the time range is set by detecting a user selection of a date user interface object and a time user interface object. In some embodiments, this includes detecting a user selection of a date on which the time range should start. In some embodiments, this includes detecting a user selection of a specific date in a week on which the time range should be repeated (e.g., selecting an option for repeating the time range from Monday to Friday but not on Saturday or Sunday). In some embodiments, this includes detecting a user selection of a start time and an end time within the time range (e.g., starting at 9:00AM and ending at 3:00PM).

[0283] In some embodiments, when a current location associated with a user account (e.g., Jane's account) is evaluated relative to a geographic location and a time range (e.g., and when the user account shares the location of an electronic device associated with the user account with one or more user accounts outside of the user account), the electronic device generates (and in some embodiments, transmits; causes transmission of) a notification (e.g., 6040, 6048) for display at an external electronic device associated with the user account (e.g., Jane's device 6000B, Jane's device 6100B), the notification including that a second user account (e.g., a remote user or device that has been authorized (e.g., by the user account associated with the electronic device) to receive location data associated with the user account; the user account associated with the electronic device) is requesting to be notified of external electronic devices associated with the user account within the time range. An indication of a change in the associated location relative to the geographic location (e.g., text 6048-1). In some embodiments, the electronic device associated with the user account is a first electronic device (e.g., Jane's device 6000B). In some embodiments, the electronic device associated with the user account is a second electronic device different from the first electronic device (e.g., Jane's device 6100B). In some embodiments, the notification is the notification displayed in step 708 discussed above with respect to method 700. Generating a notification including an indication that the second user account is requesting to be notified of changes in the location associated with the user account relative to the geographic location within the time range provides an enhanced layer of security and preserves the privacy of the tracked user by providing the user with an indication that another user account is intended to receive notifications related to the location associated with the user account.

[0284] In some embodiments, in response to determining that a current location associated with a user account (e.g., Jane's account) has a predefined relationship with the geographic location within a time range (e.g., the electronic device associated with the user count is located at the geographic location regardless of the time range) (e.g., see Figure 6H ), a notification is generated (e.g., 6040, 6048). In some embodiments, a notification is generated only when the location of the user account has a predefined relationship with the geographic location for the first time. In some embodiments, generating a notification when a device has a predefined relationship with a geographic location provides an enhanced layer of security and maintains the privacy of the tracked user by providing information that the location of the device is being tracked, which is particularly useful in scenarios where a malicious actor has access to the tracked user device and the malicious actor sets geo-fence and time period parameters and confirms geo-fence and time period on the tracked user device without the knowledge or consent of the tracked user.

[0285] In some embodiments, a notification is generated at a time corresponding to a time range (e.g., matching the start of the time range) (e.g., generating a notification at or near the start of the time range) (e.g., see Figure 6G ). In some embodiments, a notification is generated only when the start time of the time range is reached for the first time. In some embodiments, generating a notification at a time that matches the start time in the time range provides an enhanced layer of security and preserves the privacy of the tracked user by providing information that the location of the device is being tracked, which is particularly useful in scenarios where a malicious actor has access to the tracked user device and the malicious actor sets geofence and time period parameters and confirms the geofence and time period on the tracked user device without the knowledge or consent of the tracked user.

[0286] Note that the above reference method 800 (eg, Figure 8 ) also applies in a similar manner to the methods described above. For example, method 700 optionally includes one or more features of the various methods described above with reference to method 800. For example, after accepting the notification displayed in step 708 of method 700, the steps of method 800 are performed. For the sake of brevity, these details are not repeated below.

[0287] For the purpose of explanation, the preceding description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. These embodiments are selected and described in order to best explain the principles of these technologies and their practical applications. Others skilled in the art can thus best utilize these technologies and various embodiments with various modifications suitable for the intended specific use.

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

[0289] As described above, one aspect of the present technology is to collect and use data from various resources to improve the management of location-related communications of electronic devices. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

[0290] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit the user. For example, the personal information data can be used to track the location of the user's device. In addition, the present disclosure also anticipates other uses of the personal information data that benefit the user. For example, health and fitness data can be used to provide insights into the user's overall health or can be used as positive feedback to individuals using technology to pursue health goals.

[0291] This disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. In addition, such collection / sharing should be performed after receiving informed consent from the user. In addition, such entities should consider taking any necessary steps to defend and secure access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including specific considerations of jurisdiction. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained in each country for different types of personal data.

[0292] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates that hardware elements and / or software elements may be provided to prevent or block access to such personal information data. For example, with respect to tracking the location of an electronic device, the present technology may be configured to allow a user to choose to "opt in" or "opt out" to participate in the collection of personal information data at any time during or after registration for a service. As another example, a user may choose not to provide certain location data during a specified time period. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then be reminded again just before the personal information data is accessed by the application.

[0293] In addition, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how data is stored (e.g., aggregating data between users), and / or other methods when appropriate.

[0294] Therefore, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or part of such personal information data.

Claims

1. A method comprising: At Electronic Equipment: When evaluating the current location associated with a user account relative to the geographic location and time frame: generating a prompt indicating that the current location associated with the user account does not have the predefined relationship with the geographic location during the time range based on determining that the current location associated with the user account does not have the predefined relationship with the geographic location; as well as Based on determining that the current location associated with the user account does not have the predefined relationship with the geographic location at a time outside the time range, abandoning generating a prompt indicating that the current location associated with the user account does not have the predefined relationship with the geographic location.

2. The method of claim 1 , comprising, when evaluating the current location associated with the user account relative to the geographic location and the time range: Based on determining that the current location associated with the user account has a predefined relationship with the geographic location at a time outside the time range, forgoing generating a prompt indicating that the current location associated with the user account does not have the predefined relationship with the geographic location.

3. The method according to any one of claims 1 to 2, comprising, when evaluating the current location associated with the user account relative to the geographic location and the time range: Based on determining that the current location associated with the user account has a predefined relationship with the geographic location during the time range, forgoing generating a prompt indicating that the current location associated with the user account does not have the predefined relationship with the geographic location.

4. The method according to any one of claims 1 to 2, wherein: The electronic device has a display device, and the method further includes: Prior to evaluating the current location associated with the user account relative to the geographic location and the time range: Displayed by the display device: a location user interface object that, when selected, initiates a process for specifying the geographic location; a date user interface object that, when selected, initiates a process for specifying a date component of the time range; and A time user interface object that, when selected, initiates a process for specifying a time component of the time range.

5. The method according to any one of claims 1 to 2, further comprising: Prior to evaluating the current location associated with the user account relative to the geographic location and the time range: A notification is generated for display at an external electronic device associated with the user account, the notification including an indication that a second user account is requesting to be notified of changes in the location associated with the user account relative to the geographic location during the time range.

6. The method according to claim 5, wherein: The notification is generated in response to determining that the current location associated with the user account has the predefined relationship with the geographic location during the time range.

7. The method according to claim 5, wherein: The notification is generated at a time corresponding to the time range.

8. The method according to any one of claims 1 to 2, wherein: generating the reminder on a first date, and The prompt includes a first user interface object that, when selected, initiates a process for preventing display of a subsequent prompt that was generated on the first date and is associated with an evaluation of the current location associated with the user account relative to the geographic location during the time range.

9. The method according to any one of claims 1 to 2, wherein: The prompt includes a second user interface object that, when selected, initiates a process for contacting an external electronic device associated with the user account.

10. The method according to any one of claims 1 to 2, wherein: The prompt includes a third user interface object that, when selected, initiates a process for performing the following operations: When the current location associated with the user account is evaluated relative to the geographic location during the time range, and based on determining that the current location associated with the user account has the predefined relationship with the geographic location, a second prompt is generated indicating that the current location associated with the user account has the predefined relationship with the geographic location.

11. The method according to any one of claims 1 to 2, wherein: The prompt includes a fourth user interface object that, when selected, initiates a process for displaying a map representing the current location associated with the user account.

12. The method according to any one of claims 1 to 2, wherein: The prompt is generated when the current location associated with the user account does not match the geographic location at the start time of the time range.

13. The method according to any one of claims 1 to 2, wherein: The prompt is generated when the current location associated with the user account transitions from having the predefined relationship with the geographic location during the time range to not having the predefined relationship with the geographic location during the time range.

14. The method according to any one of claims 1 to 2, wherein: When the current location associated with the user account matches the geographic location, the user account has the predefined relationship with the geographic location.

15. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 14.

16. An electronic device, comprising: one or more processors; as well as A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 14.

17. An electronic device comprising: Device for carrying out the method according to any one of claims 1 to 14.

Images