User interface for creating log entries

Abstract

The invention relates to a user interface for creating log entries. In some implementations, an electronic device detects an activity event associated with a user of the electronic device and displays a prompt to facilitate creation of a logging entry based on the activity event, displays suggested content for incorporating a logging entry of a logging application, and / or displays one or more reviews.

Description

[0001] This application is a divisional application of the patent application with application number 202380045008.7, application date June 4, 2023, and invention name “User interface for creating log entry”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Application No. 63 / 365,875, filed on June 5, 2022, and entitled “User Interfaces for Creating Journaling Entries,” U.S. Provisional Application No. 63 / 483,263, filed on February 3, 2023, and entitled “User Interfaces for Creating Journaling Entries,” U.S. Provisional Application No. 63 / 503,759, filed on May 23, 2023, and entitled “User Interfaces for Creating Journaling Entries,” and U.S. Provisional Application No. 63 / 470,940, filed on June 4, 2023, and entitled “Privacy-Preserving Presentation of Content Item Bundles,” the contents of which are incorporated herein by reference in their entirety for all purposes. Technical Field

[0004] The present invention generally relates to user interfaces associated with creating journal entries. Background Art

[0005] In recent years, users' interactions with electronic devices have increased significantly. These devices may include computers, tablet computers, televisions, multimedia devices, mobile devices, etc.

[0006] In some cases, a user may wish to perform logging via an electronic device. Summary of the Invention

[0007] Some embodiments described in this disclosure relate to one or more electronic devices that detect activity events associated with users of the electronic devices and provide prompts to the users for creating log entries based on such activity events. Some embodiments described in this disclosure relate to one or more electronic devices that display suggested content for inclusion in log entries of a logging application. Some embodiments described in this disclosure relate to one or more electronic devices that display one or more replays. A comprehensive description of the embodiments is provided in the accompanying drawings and detailed description, and it should be understood that the invention summary provided above does not limit the scope of the present disclosure in any way.

[0008] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] 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, in which like reference numerals designate corresponding parts throughout the several views.

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

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

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

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

[0014] Figure 4A An exemplary user interface for an application menu on a portable multifunction device according to some embodiments is shown.

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

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

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

[0018] Figures 5C to 5D Example components of a personal electronic device with a touch-sensitive display and an intensity sensor are shown according to some embodiments.

[0019] Figures 5E to 5H Exemplary components and user interfaces of a personal electronic device according to some embodiments are shown.

[0020] Figures 6A to 6QQ An exemplary manner of detecting an activity event and displaying a prompt to create a log entry is shown according to some embodiments.

[0021] Figure 7 is a flow diagram illustrating a method 700 of displaying a prompt selectable to initiate the process of creating a log entry, according to some embodiments.

[0022] Figures 8A to 8V An exemplary manner of displaying a user interface for logging is generally shown according to some embodiments.

[0023] Figure 9 is a flowchart illustrating a method 900 of displaying a user interface for logging, according to some embodiments.

[0024] Figure 10 is a flow diagram illustrating a method 1000 for displaying a user interface including a replay, according to some embodiments. DETAILED DESCRIPTION

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

[0026] Users often use multiple applications to capture or track various activities, interests and events. For example, a user may use a camera application to capture photos at a birthday party, or use a fitness application to capture the user's route or performance during a marathon. Such applications generate and store various content items (such as photos, videos, activity logs and / or maps) associated with an event or activity. A user may wish to save a record of important events and activities and / or remember important events and activities, such as by saving a log. An electronic device may wish to provide a log recording user interface that allows the user to easily add content items from different applications to a log entry and / or prompt the user to create a log entry based on previously generated content items. Such user interfaces can alleviate the cognitive burden of users who use such devices and / or wish to create log entries, and can provide enhanced privacy or security. In addition, such technology can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0027] Although the following description uses the terms "first," "second," etc. to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. 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.

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

[0029] 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 [stated condition or event] is detected" are optionally interpreted to mean "upon determining," or "in response to determining," or "upon detecting [stated condition or event]," or "in response to detecting [stated condition or event]," depending on the context.

[0030] 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 music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch 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 touch pads), are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads).

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

[0032] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a rendering 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.

[0033] 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 the touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and clear to the user.

[0034] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1A 1 is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display 112 according to some embodiments. 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." Device 100 includes 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, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and external ports 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of contacts on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating 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.

[0035] 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) for 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, the 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 surrogate for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the surrogate measurement of the contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurement). In some embodiments, the surrogate measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functionality that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0036] 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 a device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device that will be detected by a user using the user's sense of touch. For example, when a device or a component of the device is in contact with a surface that is touch-sensitive to a user (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 that corresponds to a perceived change in a physical property 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" on 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 was physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when the smoothness of the touch-sensitive surface does not change, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. While 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.

[0037] 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 are implemented in hardware, software, or a combination of both, including one or more signal processing and / or application specific integrated circuits.

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

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

[0040] RF (radio frequency) circuitry 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuitry 108 converts electrical signals into / from electromagnetic signals and communicates with a communication network and other communication devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a subscriber identity module (SIM) card, memory, and the like. RF circuitry 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also known 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 circuitry 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via a short-range communication radio. The 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), IEEE 802.11f, IEEE 802.11g ... 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 Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

[0041] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the 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 sends 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 sends the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or sent 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 with both output (e.g., a single or dual-ear headset) and input (e.g., a microphone).

[0042] The I / O subsystem 106 couples input / output peripherals on the device 100, such as the touch-sensitive display 112 and other input control devices 116, to a peripherals interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, 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 / transmit electrical signals from / to 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 controllers 160 are optionally coupled to any (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 up / down button for volume control of the speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2 206 in ).

[0043] A quick press of the push button optionally unlocks the touch-sensitive display 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. patent application Ser. No. 11 / 322,549, filed Dec. 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," (i.e., U.S. Pat. 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 or soft buttons and one or more soft keyboards.

[0044] 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 transmits electrical signals to the touch screen. 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.

[0045] The touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the 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 that 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 the user's finger.

[0046] 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 ® Touch Controller from Apple Inc. (Cupertino, California). and iPod The technology used in

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

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

[0049] The touch screen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or appendage, such as a stylus, a finger, or the like, 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 ​​a finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positioning or commands for performing the actions desired by the user.

[0050] In some embodiments, in addition to the touch screen, the device 100 optionally includes a touchpad (not shown) for activating or deactivating specific functions. In some embodiments, the touchpad is a touch-sensitive area of ​​the device that, unlike the 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.

[0051] Device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power fault detection circuitry, 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.

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

[0053] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1A A contact force sensor is shown coupled to force sensor controller 159 in 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 a 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 with 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 touch screen display 112 located on the front of device 100.

[0054] Device 100 optionally also includes one or more proximity sensors 166 . Figure 1AA 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 application serial numbers: 11 / 241,839, entitled “Proximity Detector In Handheld Device”; 11 / 240,788, entitled “Proximity Detector In Handheld Device”; 11 / 620,702, entitled “Using Ambient Light Sensor To Augment Proximity Sensor Output”; 11 / 586,862, entitled “Automated Response To And Sensing Of User Activity In Portable Devices”; and 11 / 638,251, entitled “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entireties. 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.

[0055] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1A A 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 speakers or other audio components; and / or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components for converting electrical signals into tactile outputs on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates tactile outputs on the device 100 that can be felt by the user of the device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112) and optionally generates tactile outputs by moving the touch-sensitive surface vertically (e.g., inward / outward toward the surface of the device 100) or laterally (e.g., back and forth 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.

[0056] Device 100 optionally also includes one or more accelerometers 168 . Figure 1A An accelerometer 168 is shown coupled to the peripherals interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 in the I / O subsystem 106. The accelerometer 168 optionally implements as described in the following U.S. Patent Publication Nos. 20050190059, entitled “Acceleration-based Theft Detection System for Portable Electronic Devices” and 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 on the touch screen display in a portrait view or a landscape view based on analysis of data received from one or more accelerometers. The device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to the accelerometer 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 100.

[0057] 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: active application state, which indicates which application, if any, is currently active; display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; sensor state, which includes information obtained from the device's various sensors and input control devices 116; and position information relating to the device's position and / or posture.

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

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

[0060] 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 down event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there has been 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 ceased (e.g., detecting a finger up event or contact break). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of a contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single-finger contact) or multiple points of contact simultaneously (e.g., "multi-touch" / multiple-finger contact). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on the touchpad.

[0061] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action 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 threshold of a particular physical actuator and can be adjusted without changing the physical hardware of the device 100). For example, a mouse "click" threshold for a touchpad or touchscreen can be set to any one of a large range of predefined thresholds without changing the touchpad or touchscreen display hardware. Additionally, in some embodiments, 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).

[0062] 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). Thus, 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.

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

[0064] 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 specifying the graphics to be displayed from an application or the like, along with coordinate data and other graphic attribute data if necessary, and then generates screen image data for output to the display controller 156.

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

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

[0067] 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 a weather widget, a local yellow pages widget, and a map / navigation widget).

[0068] Application 136 optionally includes the following modules (or instruction sets), or a subset or superset thereof:

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

[0070] Telephone module 138;

[0071] Video conferencing module 139;

[0072] Email client module 140;

[0073] Instant messaging (IM) module 141;

[0074] Fitness support module 142;

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

[0076] Image management module 144;

[0077] Video player module;

[0078] Music player module;

[0079] Browser module 147;

[0080] Calendar module 148;

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

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

[0083] Search module 151;

[0084] Video and music player module 152, which combines the video player module and the music player

[0085]

[0086] Note module 153;

[0087] Map module 154; and / or

[0088] Online video module 155.

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

[0090] In combination with the touch screen 112, display controller 156, touch / motion module 130, graphics module 132 and text input module 134, the contacts module 137 is optionally used to manage an address book or contact list (for example, stored in the application internal state 192 of the contacts 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 so on.

[0091] 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 character sequence corresponding to a phone number, access one or more phone numbers in contacts module 137, modify an entered phone number, dial the 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.

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

[0093] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, transmitting, 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 transmit emails with still images or video images captured by camera module 143.

[0094] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the instant messaging module 141 includes executable instructions for entering a character sequence corresponding to an instant message, modifying previously entered characters, sending the corresponding instant message (e.g., using the 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 instant messages sent and / or received optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages transmitted using SMS or MMS) and Internet-based messages (e.g., messages transmitted using XMPP, SIMPLE, or IMPS).

[0095] 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 a fitness; and displaying, storing, and sending fitness data.

[0096] In combination 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.

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

[0098] 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 for, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0099] 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 a calendar and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

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

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

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

[0103] 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, as well as 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.).

[0104] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the note module 153 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.

[0105] In combination with the RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, 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.

[0106] 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 allowing a user to access, browse, receive (e.g., by streaming and / or downloading), play back (e.g., on the touch screen or on an external display connected via external port 124), send an email with a link to a particular online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a particular 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.

[0107] 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 1AIn 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.

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

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

[0110] Figure 1B 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).

[0111] 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 an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes an application internal state 192 that 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.

[0112] 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 application 136-1 resumes execution, user interface state information indicating that information is being displayed or is ready to be displayed by application 136-1, a state queue for enabling the user to return to a previous state or view of application 136-1, and a repeat / undo queue of previous actions taken by the user.

[0113] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 sends 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.

[0114] In some embodiments, event monitor 171 transmits requests at predetermined intervals to peripheral device interface 118. In response, peripheral device interface 118 sends event information. In other embodiments, peripheral device interface 118 sends 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).

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

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

[0117] 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 programmatic levels within the application's programmatic or view hierarchy. For example, the lowest-level view in which a touch is detected is optionally referred to as a hit view, and the set of events recognized as correct input is optionally determined based at least in part on the hit view of the initial touch that started the touch-based gesture.

[0118] 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 that should handle the sub-events. 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.

[0119] 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, views higher in the hierarchy will still remain actively participating views.

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

[0121] 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 part of another module stored in memory 102, such as contact / motion module 130.

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

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

[0124] The event receiver 182 receives event information from the event classifier 170. The event information includes information about sub-events such as touches or touch movements. 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 a touch, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a portrait orientation to a landscape 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).

[0125] The event comparator 184 compares the event information with predefined event or sub-event definitions and determines the event or sub-event based on the comparison, or determines or updates the state of the event or sub-event. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes the definition of the event (e.g., a predefined sequence of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, the 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 the displayed object, a first lift-off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on the 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.

[0126] 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 that is associated with the sub-event and the object that triggered the hit test.

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

[0128] When a corresponding event recognizer 180 determines that a sequence of sub-events does not match any event in event definitions 186, the corresponding event recognizer 180 enters the 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.

[0129] In some embodiments, 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 for 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.

[0130] 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 delivering (and deferred delivery of) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a flag associated with the identified event, and the event handler 190 associated with the flag retrieves the flag and performs a predefined process.

[0131] In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and executes a predetermined process.

[0132] 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 positioning of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and transmits the display information to graphics module 132 for display on a touch-sensitive display.

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

[0134] It should be understood that the above discussion of event handling for user touches on a touch-sensitive display also applies to other forms of user input utilizing 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 holddowns; contact movement on a touchpad, such as taps, drags, scrolls, etc.; stylus input; movement of the device; spoken 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.

[0135] Figure 2A portable multifunction device 100 with a touch screen 112 according to some embodiments is illustrated. 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 the 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 the one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or rolling of the finger that has made contact with the device 100 (from right to left, from left to right, up and / or down). In some implementations or in some cases, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon does not select the corresponding application when the gesture corresponding to selection is a tap.

[0136] 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 optionally being 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.

[0137] 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 subscriber identity module (SIM) card slot 210, a headset 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 holding it in the depressed state for a predefined time interval; to lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or to 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 via the microphone 113. The device 100 also optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for the user of the device 100.

[0138] Figure 33 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 does not have to be portable. In some embodiments, the 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 gaming system, or a control device (e.g., a home controller or an industrial controller). The 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. The device 300 includes an input / output (I / O) interface 330 having a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above referenced device). Figure 1A Tactile output generator 167 as described above), sensor 359 (e.g., optical sensor, acceleration sensor, proximity sensor, touch sensitive sensor and / or contact intensity sensor (similar to the above reference Figure 1A 310). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU 310. In some embodiments, memory 370 stores data related to 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.

[0139] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the memory device mentioned previously.Each module in the above-mentioned modules corresponds to the instruction set for performing the function described above.Above-mentioned modules or programs (for example, instruction set) need not 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 above-mentioned modules and data structure.In addition, memory 370 optionally stores additional modules and data structure not described above.

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

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

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

[0143] Time 404;

[0144] Bluetooth indicator 405;

[0145] Battery status indicator 406;

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

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

[0148] o An icon 418 of the email client module 140 labeled "Mail," which optionally includes an indicator 410 of the number of unread emails;

[0149] o An icon 420 labeled "Browser" for the browser module 147; and

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

[0151] Icons for other apps, such as:

[0152] o Icon 424 labeled "Messages" of the IM module 141;

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

[0154] o Icon 428 labeled "Photos" of the image management module 144;

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

[0156] ○ An icon 432 labeled “Online Video” of the online video module 155;

[0157] ○ Icon 434 labeled “Stock Market” of the Stock Market widget 149-2;

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

[0159] ○ Icon 438 labeled “Weather” of weather widget 149-1;

[0160] ○ Icon 440 labeled “Clock” of the alarm clock widget 149-4;

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

[0162] o An icon 444 labeled "Notes" for the notes module 153; and

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

[0164] It should be pointed out that Figure 4A The illustrated icon labels are merely exemplary. For example, the icon 422 of the 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 respective application icon includes the name of the application corresponding to the respective 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.

[0165] Figure 4B A touch-sensitive surface 451 (eg, touch screen display 112) is illustrated as being separate from a display 450 (eg, touch screen display 112). Figure 3 tablet or touchpad 355) of the 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.

[0166] Although some of the examples below will be given with reference to input on a touch screen display 112 (where the touch-sensitive surface and 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 main 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 ) at contact with touch-sensitive surface 451 (e.g., Figure 4B 460 and 462 in FIG. 4. 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 interface 450 in FIG. 1 is separated, the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0167] Additionally, 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, when the cursor is at the location of a tap gesture, the tap gesture is optionally replaced by a mouse click (e.g., instead of detecting contact and then 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 mice and finger contacts are optionally used simultaneously.

[0168] Figure 5AAn exemplary personal electronic device 500 is illustrated. The device 500 includes a body 502. In some embodiments, the device 500 may include components related to devices 100 and 300 (e.g., Figures 1A to 4B ) some or all of the features described in . In some embodiments, device 500 has a touch-sensitive display screen 504, referred to hereinafter as touch screen 504. Alternatively, or in addition to touch screen 504, device 500 also 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 intensity sensors for detecting the intensity of the contact (e.g., touch) applied. The one or more intensity sensors of touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of device 500 can respond to the touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 500.

[0169] 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, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed on May 8, 2013, published as WIPO Patent Publication No. WO / 2013 / 169849; and International Patent Application Serial No. PCT / US2013 / 069483, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed on November 11, 2013, published as WIPO Patent Publication No. WO / 2014 / 105276, each of which is hereby incorporated by reference in its entirety.

[0170] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, 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.

[0171] Figure 5B An exemplary personal electronic device 500 is depicted. In some embodiments, the device 500 may include information about 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. The I / O portion 514 can be connected to a touch screen 504, which can have a touch-sensitive component 522 and optionally a strength sensor 524 (e.g., a contact strength sensor). In addition, the I / O portion 514 can 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, the input mechanism 506 is optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, the input mechanism 508 is optionally a button.

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

[0173] 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 methods 700, 900, and / or 1000. Figure 7 、 Figure 9 and Figure 10). 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.

[0174] In addition, in the method described herein where one or more steps depend on having met one or more conditions, it should be understood that the method can be repeated in multiple repetitions so that in the process of repetition, all conditions of the steps in the method of determining the method have been met in different repetitions of the method. For example, if the method needs to perform the first step (if the condition is met), and perform the second step (if the condition is not met), then those of ordinary skill will know that the steps stated are repeated until both the condition is met and the condition is not met (in no particular order). Therefore, the method described as having one or more steps depending on having met one or more conditions can be rewritten as a method of repeating until each condition described in the method is met. However, this does not require a system or computer-readable medium to declare that the system or computer-readable medium includes instructions for performing a contingent operation based on the satisfaction of the corresponding one or more conditions, and is therefore able to determine whether a possible situation has been met without explicitly repeating the steps of the method until all conditions of the steps in the method of determining the method have been met. Those of ordinary skill in the art will also understand that, similar to the method with a contingent step, a system or computer-readable storage medium can repeat the steps of the method as needed multiple times to ensure that all contingent steps have been performed.

[0175] As used herein, the term "indicator" refers to an indication that is optionally provided on device 100, 300, and / or 500 ( Figure 1A 、 Figure 3 and Figures 5A to 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.

[0176] 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 FIG, the particular user interface element is adjusted according to the detected input. In the case of a touch screen display (e.g., a touch screen display) that enables direct interaction with user interface elements on the touch screen display Figure 1A touch-sensitive display system 112 or Figure 4A In some implementations of the touch screen 112 in FIG, 2 , a contact detected on the touch screen acts as a “focus selector” such that when 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 according to 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 according to 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 generally 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 touchpad 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).

[0177] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some 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 begins to move, before contact ends, before or after contact is detected to increase in intensity, and / or before or after contact is detected to decrease in intensity). 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 in 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.

[0178] Figure 5C Detecting multiple contacts 552A-552E on touch-sensitive display 504 using multiple intensity sensors 524A-524D is shown. Figure 5C Also included is an intensity graph that shows the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are both 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are both 7 intensity units. In some implementations, the cumulative intensity is the sum of the intensity measurements of multiple intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a corresponding intensity, which is a portion of the cumulative intensity. Figure 5D554. The cumulative strength assigned to contacts 552A-552E based on their distance from the center of force 554 is shown. In this example, each of contacts 552A, 552B, and 552E is assigned a strength of the contact of 8 strength units of the cumulative strength, and each of contacts 552C and 552D is assigned a strength of the contact of 4 strength units of the cumulative strength. More generally, in some embodiments, each contact j is assigned a corresponding strength Ij that is a portion of the cumulative strength A according to a predefined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance of the corresponding contact j from the center of force, and ΣDi is the sum of the distances of all corresponding contacts (e.g., i=1 to the last) from the center of force. The reference may be performed using an electronic device similar to or identical to device 100, 300, or 500. Figure 5C-5D In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, the intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity map is not part of the displayed user interface, but is included in the Figure 5C-5D To assist readers.

[0179] In some embodiments, a portion of a gesture is identified for use in determining the characteristic strength. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting position and reaches an ending position where the contact strength increases. In this example, the characteristic strength of the contact at the ending 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 ending position). In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic strength of the contact. For example, the 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 dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic strength.

[0180] The intensity of the 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 is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, contacts below the nominal contact detection intensity threshold are no longer detected), the device will move the focus selector in accordance with 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.

[0181] 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 a 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 a 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.

[0182] 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 an increase in the intensity of the contact (or multiple contacts) to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting an increase in the intensity of the corresponding contact to above the press input intensity threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the 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 press input intensity threshold, and the corresponding operation is performed in response to detecting a subsequent decrease in the intensity of the corresponding contact to below the press input threshold (e.g., an "up stroke" of the corresponding press input).

[0183] Figure 5E-5HDetection of a gesture is shown, the gesture comprising contact 562 with an intensity from below Figure 5E Light press intensity threshold in L ”) increases to a value higher than Figure 5H The deep press intensity threshold in D ”). On the displayed user interface 570 including application icons 572A-572D displayed in the predefined area 574, when the cursor 576 is displayed over the application icon 572B corresponding to application 2, a gesture performed using the contact 562 is detected on the touch-sensitive surface 560. In some embodiments, the gesture is detected on the touch-sensitive display 504. The intensity sensor detects the intensity of the contact on the touch-sensitive surface 560. The device determines whether the intensity of the contact 562 is within the deep press intensity threshold (e.g., “IT D ”) reaches a peak above. Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture, and according to the intensity rising to the deep press intensity threshold (e.g., “IT D ”) above contact 562, displays scaled representations 578A-578C (e.g., thumbnails) of documents recently opened for application 2, as shown in FIG. Figure 5F-5H In some embodiments, the intensity is a characteristic intensity of the contact compared to one or more intensity thresholds. It should be noted that the intensity map for contact 562 is not part of the displayed user interface, but is included in the Figure 5E-5H To assist readers.

[0184] In some embodiments, the display of representations 578A-578C includes animation. For example, representation 578A is initially displayed near application icon 572B, as shown in FIG. Figure 5F As the animation progresses, representation 578A moves upward and representation 578B is displayed near application icon 572B, as shown. Figure 5G Then, representation 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed near application icon 572B, as shown in FIG. Figure 5H . Indicators 578A-578C form an array above icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, such as Figure 5F-5G , where representations 578A-578C appear and decrease as the intensity of contact 562 moves toward a deep press intensity threshold (e.g., “IT D In some embodiments, the intensity according to which the animation progresses is the characteristic intensity of the contact. The reference may be performed using an electronic device similar to or identical to device 100, 300, or 500. Figures 5E to 5H The operation described.

[0185] 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 a 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 "upstroke" 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).

[0186] For ease of explanation, 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 optionally triggered in response to detecting any of the following: contact intensity increasing 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 below the press input intensity threshold, and / or contact intensity decreasing 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.

[0187] In some embodiments, the electronic device 500 includes one or more tactile output generators, wherein the one or more tactile output generators generate different types of tactile output sequences, as described in Table 1 below. In some embodiments, the specific type of tactile output sequence generated by the one or more tactile output generators of the device corresponds to a specific tactile output pattern. For example, the tactile output pattern specifies the characteristics of the tactile output, such as the amplitude of the tactile output, the shape of the motion waveform of the tactile output, the frequency of the tactile output, and / or the duration of the tactile output. When a device (e.g., one or more tactile output generators that generate tactile output via moving a movable mass) generates tactile output with different tactile output patterns, the tactile output can produce different tactile sensations in a user holding or touching the device. Although the user's senses are based on the user's perception of the tactile output, most users will be able to identify changes in the waveform, frequency, and amplitude of the tactile output generated by the device.

[0188] Table 1 below provides representative embodiments of haptic output / haptic feedback behaviors and configurations, and their use with respect to embodiments of user interfaces for managing content-based haptic output as shown and described herein.

[0189]

[0190] Table 1

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

[0192] As used herein, the term "open application" or "executing application" refers to a software application that has persisted state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or executing application is optionally any of the following types of applications:

[0193] The active app currently displayed on the display of the device on which the app is being used;

[0194] Background applications (or background processes), which are not currently displayed but for which one or more processes are being processed by one or more processors; and

[0195] Not running but stored in memory (volatile and non-volatile respectively)

[0196] A suspended or dormant application that contains status information that can be used to resume execution of the application.

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

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

[0199] User interface and associated processes

[0200] Prompt the user to make a logging entry

[0201] Users interact with electronic devices in many different ways. The embodiments described below provide ways for an electronic device to display prompts to a user that can be selected to initiate the process of creating a log entry, thereby enhancing the user's interaction with the electronic device. This enhanced interaction with the device reduces the amount of time required for the user to perform actions, thereby reducing the device's power usage and extending the battery life of battery-powered devices. It should be understood that people use devices. When a person uses a device, that person is optionally referred to as a user of the device.

[0202] Figures 6A to 6QQ An exemplary manner of creating a log entry in a logging application according to some embodiments of the present disclosure is shown. The embodiments in these figures are used to illustrate the process described below, including reference to Figure 7 The process described.

[0203] Figure 6A An exemplary device 500A is shown that includes a touch screen 504A (e.g., touch screen 504, display 112). Figure 6A , device 500A is displaying user interface 602, which includes application icon 605, application icon 610, application icon 615, application icon 620, application icon 625, application icon 630, application icon 635, application icon 6411, application icon 645, application icon 650, application icon 655, and application icon 660. In some embodiments, user interface 602 is a home screen user interface of device 500A (e.g., as shown in FIG. Figure 4A) and includes different application icons that can be selected to display different applications, as described above. Application icon 605 corresponds to a messaging application for initiating and maintaining messaging sessions. Application icon 610 corresponds to a calendar application for entering and managing a calendar. Application icon 615 corresponds to a call application for initiating phone calls. Application icon 620 corresponds to a fitness application for maintaining fitness information. Application icon 625 corresponds to a stocks application for monitoring stock activity. Application icon 630 corresponds to a map application for searching maps and generating and following routes. Application icon 635 corresponds to a clock application for displaying the time at one or more locations. Application icon 641 corresponds to a settings application for maintaining the configuration of device 500. Application icon 645 corresponds to a music application for accessing, downloading, and playing music. Application icon 650 corresponds to a store application for purchasing additional applications. Application icon 655 corresponds to a journal application for creating and accessing journal entries. Application icon 660 corresponds to a camera application for taking photos.

[0204] exist Figure 6A , device 500A detects selection of application icon 655 (e.g., via contact 603). In response, Figure 6B , device 500A displays an authentication user interface 604 and allows access to the logging application only upon receiving a successfully authenticated authentication input (e.g., a biometric, PIN, password, or other authentication), and does not display the logging application if the authentication input is not successfully authenticated.

[0205] exist Figure 6B In FIG, device 500A detects a successfully authenticated authentication input (e.g., via contact 603) to authentication user interface 604. In response, Figure 6C , device 500A displays a user interface 606 of a logging application that includes representations of log entries 608-612 that have been created in the logging application and a selectable option 614. The representation of log entry 608 corresponds to the log entry for December 14. The representation of log entry 613 corresponds to the log entry for December 15. The representation of log entry 612 corresponds to the log entry for December 16. Selectable option 614 can be selected to initiate the process of adding a new log entry to the logging application. Selectable option 617 can be selected to initiate the process of viewing one or more animated video presentations associated with the activity event and / or the log entry, which will be discussed in more detail below.

[0206] exist Figure 6CIn , device 500A detects selection of selectable option 614 (e.g., via contact 603). In response, Figure 6D , device 500A updates user interface 606 to display selectable options 616 and 618. Selectable option 616 may be selected to initiate the process of manually creating a log entry. Selectable option 618 may be selected to request a prompt from device 500A to facilitate the creation of a log entry.

[0207] exist Figure 6D In , device 500A detects selection of selectable option 616 (e.g., via contact 603) and one or more inputs that enter content into a log record entry. In response, Figure 6E , device 500A updates user interface 606 to display log entry 621, which includes content manually provided to device 500A by the user (e.g., via manual soft keyboard entry and / or manual voice entry).

[0208] In some embodiments, rather than requiring manual creation of a log entry, device 500A facilitates creation of a log entry by automatically (e.g., without requiring user input to do so) displaying one or more prompts that facilitate creation of a log entry based on activity detected by device 500A, as will be described with reference to FIG. Figures 6F to 6R For example, Figure 6F An additional exemplary manner of creating a log record entry at device 500A is shown. Figure 6F , device 500A detects selection of application icon 615 (e.g., via contact 603). In response, Figure 6G , and when device 500A detects one or more additional inputs, device 500 initiates a call to the user's "Mom" via the calling application.

[0209] exist Figure 6G In , device 500A detects selection of selectable option 695 (e.g., via contact 603). In response, Figure 6H , device 500A ends the call with "Mom" and returns to displaying user interface 602. Thus, device 500A detects that the user of device 500A has placed a call with "Mom."

[0210] exist Figure 6H , device 500A detects selection of application icon 630 (e.g., via contact 603). In response, Figure 6I, device 500A displays a user interface 622 of a map application, the user interface including a first portion 624 including a representation of a map and a second portion 626 including user interface elements for searching for and displaying a route. The first portion 624 includes a visual indication of a route 628, and the second portion 626 includes a selectable button 631 that is selectable to initiate navigation directions along the route.

[0211] exist Figure 6I , device 500A detects selection of selectable button 631 (eg, via contact 603) and initiates navigation directions along route 628 (not shown) and then returns to displaying user interface 602, as shown. Figure 6J Thus, device 500A detects that the user of device 500A has traveled along route 628 .

[0212] exist Figure 6J , device 500A detects selection of application icon 660 (e.g., via contact 603). In response, Figure 6K , device 500A displays a user interface 637 for a photo application. User interface 637 includes a user-selectable button 634 that is selectable to take a photo of the contents of a photo preview 636 (e.g., corresponding to an image currently being captured by one or more cameras of device 500a).

[0213] exist Figure 6K , device 500A detects selection of user selectable button 634 (e.g., via contact 603). In response, device 500A takes photo 1 (not shown) and returns to displaying user interface 602 when additional input is detected, such as Figure 6L As shown. Therefore, device 500A detects that the user of device 500A has taken photo 1.

[0214] As described in more detail with reference to method 700, device 500A may optionally track various activities performed by device 500A (e.g., such as those described above) and determine whether those activities meet criteria for generating and displaying prompts that facilitate creation of log entries based on those activities. Figure 6L, after the various activities described previously have been performed, and upon determining that these activities meet one or more criteria that prompt the generation of a prompt, device 500A displays prompt 638 on the lock screen 619 of device 500A. When device 500A determines to display prompt 638, device 500A optionally displays prompt 638 on any of a plurality of user interfaces displayed by device 500A, such as a lock screen user interface, an application user interface, or any other user interface currently displayed by device 500A. The user may also be prompted on any number of personal or public devices, including tablets, phones, smartwatches, TVs, speakers, or other devices in a connected ecosystem. Prompt 638 indicates that it is related to a logging application and includes details about an activity event to the zoo. Prompt 638 includes a description of where the user is going (e.g., directions to the zoo) and a photo taken by the user as part of the activity (e.g., Photo 1). Prompt 638 is selectable to initiate the process of creating a logging entry in the logging application.

[0215] In some embodiments, prompt 638 is generated by a logging application. In some embodiments, prompt 638 is generated by system-level software (e.g., software other than the logging application) running on device 500A, such as by an operating system of device 500A, based on activities associated with various applications installed on device 500A (such as those described above). Optionally, prompt 638 is generated according to a logging schedule associated with the logging application (e.g., as described in reference to FIG. Figure 8UOption 888a of ). Optionally, if prompt 638 is generated by software other than the application associated with the content and / or activity, prompt 638 includes a graphical or textual indication that it was generated by software on behalf of an application (such as on behalf of a logging application) (e.g., to alert the user that prompt 638 is not from a logging application). In some embodiments, prompt 638 may include multiple sub-prompts (e.g., each associated with a different activity and / or event), such as by including (for example) both "Remember your day at the zoo" and "Write about your trip last year." In some embodiments, in response to detecting a selection of prompt 638, device 500A displays a picker user interface that includes a representation of the content associated with prompt 638 (optionally, including a representation of the content associated with each of the sub-prompts of prompt 638), from which the user can pick (e.g., select) the content to provide to the logging application (or another application associated with the content or sub-prompt) (e.g., to be sent to the logging application or made accessible to the logging application). In some embodiments, the picker user interface is separate from (e.g., not part of) the logging application. In some embodiments, the picker user interface is displayed within the logging application. In some embodiments, the picker user interface includes a confirmation affordance (such as by displaying a checkbox as shown in FIG. 10 ) for providing the selected content to the logging application and optionally initiating a new log entry in the logging application. Figure 8C In some embodiments, the content is not provided to the logging application (e.g., sent to the logging application or made accessible to the logging application) until the user confirms selection of the content (such as by selecting the content from a picker user interface and / or by selecting a confirmation affordance to maintain the privacy of the content until the user provides confirmation that the user wishes to provide the content to the logging application).

[0216] In some embodiments, in response to detecting a selection of prompt 638, device 500A displays a different user interface (e.g., instead of displaying a picker user interface), as described below with reference to Figure 6L described.

[0217] exist Figure 6L In , device 500A detects selection of prompt 638 (e.g., via contact 603). In response, Figure 6M, device 500A displays user interface 640 that includes prompt 642, text or other content entry field 644, indication 646, soft keyboard 648, selectable option 651, selectable option 652, selectable option 654, and selectable option 656. In some embodiments, device 500A displays user interface 640 overlaid on the user interface that was displayed when device 500A detected selection of prompt 638, optionally without ceasing display of the user interface and / or without launching or displaying a logging application. Figure 6M In the log entry, prompt 642 includes information about the user's activity event, such as the location of the activity event (e.g., a zoo). Prompt 642 includes questions about the activity event, such as what were the highlights of the activity event, who was there, and how they reacted to the activity event, as well as additional prompts for obtaining information about the activity event (e.g., what else stood out?). Text entry field 644 is interactive for entering text or other content in response to prompt 642 for the log entry. Soft keyboard 648 is selectable to facilitate entering text or other content into text entry field 644. Indication 646 is an indication or representation of a photo taken by device 500A during the activity event (e.g., "taken with Mom at the zoo," thus indicated by an "M" indicator overlaid on a corner of the photo). Selectable option 651 is selectable to change the prompt to a new and / or updated prompt related to the activity event (e.g., a different question related to the activity event generated and / or provided by device 500A). Selectable option 652 is selectable to change the photo to a new and / or updated photo (e.g., taken by device 500A during the activity event). Selectable option 654 is selectable to move to the next prompt to facilitate creating a log entry. Selectable option 656 is selectable to end display of the prompt to facilitate creating a log entry and create a log entry with the content typed into text entry field 644, part or all of prompt 642, and / or part or all of the photo corresponding to indication 646.

[0218] exist Figure 6M In , device 500A detects selection of one or more keys in soft keyboard 648 (e.g., via contact 603). In response, Figure 6N , device 500A updates text entry field 644 of user interface 640 to include the text entry field 644 corresponding to Figure 6M The content of the input detected in, as a response to prompt 642.

[0219] exist Figure 6N In , device 500A detects selection of selectable option 654 (e.g., via contact 603). In response, Figure 6O, device 500A updates user interface 640 to display a new prompt 658. Prompt 658 includes additional details about the active event, such as a request word used to describe the active event. Prompt 658 is updated based on input in response to a previous prompt, the history of the electronic device, or both. Device 500A also updates user interface 640 to display a new photo associated with the active event in indication 646.

[0220] exist Figure 6O In , device 500A detects selection of one or more keys in soft keyboard 648 (e.g., via contact 603). In response, Figure 6P , device 500A updates text entry field 644 of user interface 640 to include the text entry field 644 corresponding to Figure 6O The content of the input detected in, as a response to prompt 642.

[0221] exist Figure 6P In , device 500A detects selection of selectable option 654 (e.g., via contact 603). In response, Figure 6Q , device 500A updates user interface 640 to display a new prompt 661. Prompt 661 includes additional details about the active event and / or a general question about what else is outstanding about the active event and / or the day. Device 500A also updates user interface 640 to display a new photo associated with the active event in indication 646.

[0222] exist Figure 6Q In , device 500A detects selection of one or more keys in soft keyboard 648 (e.g., via contact 603). In response, Figure 6R , device 500A updates text entry field 644 of user interface 640 to include the text entry field 644 corresponding to Figure 6Q , as a response to prompt 661. Optionally, device 500A generates and displays one or more additional follow-up prompts based on the text and / or other content typed by the user. For example, device 500A optionally uses a large language model (or other artificial intelligence and / or natural language-based methods) to analyze the text or other content typed in text entry field 644 to generate and display appropriate follow-up prompts and interact with the user. For example, in response to Figure 6R Shown as detecting the text content "We also met Mom there and she was excited to see the penguins," device 500A optionally generates and displays an additional prompt (e.g., replacing prompt 661) that reads "What did Mom say to the penguins?" to encourage the user to enter additional details.

[0223] In response to selection of selectable option 656 (eg, via contact 603), device 500A creates a log entry corresponding to the activity event (eg, trip to the zoo) and adds the log entry to the logging application.

[0224] After creating the log record entry, device 500A stops displaying user interface 640 and returns to displaying user interface 602 (or whatever user interface was displayed when prompt 638 was displayed and / or selected), as shown in FIG. Figure 6S As shown. Figure 6S , device 500A detects selection of application icon 655 (e.g., via contact 603). In response, Figure 6T , device 500A displays journaling application user interface 606, which now includes a new journal entry created via prompt 638, shown as representation 670. Representation 670 of the journal entry includes references to photos 1-3 associated with representation 670 and / or representations 672 of the photos (e.g., from within user interface 640).

[0225] exist Figure 6T In FIG, device 500A detects selection of representation 670 and / or representation 672 (eg, via contact 603). In response, Figure 6U , device 500A updates user interface 606 to display a log entry 674 corresponding to representation 670. Representation 670 is generated based on the input received in response to the previously described prompt. Representation 670 may include exactly the content entered into text entry field 644, or may include a modified version of the content entered into text entry field 644. Furthermore, representation 670 may include all of the photos presented with the prompt or only a subset of the photos.

[0226] As described in more detail with reference to method 700, device 500A optionally presents notifications of log entries (e.g., featured log entries) or generates animated video presentations for particular log entries associated with events, people, places, or things, and displays notifications of these log entries or facilitates access to these video presentations. Figure 6V , at a point in time after creating log entry 674, device 500A displays notification 676 on user interface 602. Device 500A optionally displays notification 676 on any user interface currently displayed on device 500A. Notification 676 corresponds to an animated video presentation or some other representation of the corresponding log entry. Notification 676 is selectable to initiate a process of viewing an animated video presentation associated with and / or associated with the content of log entry 674. Notification 676 includes an indication that the notification originated from a logging application, as well as an indication of the corresponding date and person, place, event, or thing.

[0227] exist Figure 6V In , device 500A detects selection of notification 676 (e.g., via contact 603). In response, Figure 6W , device 500A displays an animated video presentation 679 that includes photos and music. For example, animated video presentation 679 includes text from a corresponding journal entry, photos from the journal entry, and music related to the journal entry. Animated video presentation 679 includes a selectable option 680 that can be selected to save animated video presentation 679 and / or share it with another user. Figure 6X , device 500A continues to display the animated video presentation 679 including the remaining photos (e.g., displays a subsequent portion of the animated video presentation 679).

[0228] In some embodiments, instead of being displayed as a notification, an option to display an animated video rendering of the log entry 674 is displayed in (or in the form of) a widget. For example, in Figure 6Y , device 500A displays notification 683, which is shown as a widget on user interface 602 (e.g., a widget of a logging application for which device 500A has previously received input to include in user interface 602). Similar to notification 676, notification 683 is selectable to initiate a process of displaying a representation associated with a logging entry (e.g., an animated video presentation associated with logging entry 674).

[0229] As described in more detail with reference to method 700, device 500A optionally allows a user to create a log entry based on a content item. Figure 6Z , device 500A detects selection of application icon 635 (e.g., via contact 603). In response, Figure 6AA , device 500A displays a user interface for a photo application and, after one or more additional inputs, displays photo 678. Photo 678 is displayed along with a share option 680, a selectable option 682, and a selectable option 684. Share option 680 is selectable to share the photo with a contact or utilize the photo in another application, such as a journaling application. Selectable option 682 is selectable to add photo 678 to a collection of favorite photos. Selectable option 684 is selectable to delete photo 678.

[0230] exist Figure 6AA In , device 500A detects selection of share option 680 (eg, via contact). In response, Figure 6BB , device 500A displays photo 678 in user interface 686. User interface 686 is optionally a user interface through which photo 678 can be shared. Figure 6BB , user interface 686 includes representations 687a-687d, selectable options 688a-688d, and selectable options 689a-689c. Representations 687a-687d represent messaging conversations that can be selected to initiate the process of sending and / or using photo 678 within those messaging conversations. Optional option 688a can be selected to initiate the process of sending photo 678 to a nearby device. Optional option 688b can be selected to initiate the process of emailing photo 678. Optional option 688c can be selected to initiate the process of transferring photo 678 to the messaging conversation. Optional option 688d can be selected to initiate the process of generating a log entry using photo 678. Optional option 688d can be selected to initiate the process of uploading and / or using photo 678 in a corresponding social media application. Optional option 689a can be selected to copy photo 678. Optional option 689b can be selected to add photo 678 to a collection of favorite photos. Selectable option 689c may be selected to initiate the process of marking and / or modifying photo 678.

[0231] exist Figure 6BB In , device 500A detects selection of selectable option 618d (eg, via contact 603). In response, Figure 6CC In the example, device 500A is connected to Figure 6M The user interface 640 including the prompt 690 is displayed in a manner similar to the prompt 642 in FIG. 1 (e.g., overlaid on the photo user interface without launching or displaying the journaling application). The prompt 690 includes information about the photo 678, such as the location where the photo was taken and a question about the photo 678. For example, the user interface 640 includes photo 4 because photo 4 is the initial content item that is the basis for creating the journaling entry. The user interface 640 can be similar to the prompt 642 in FIG. Figure 6M The user interface 640 in FIG. 4 interacts in a similar manner to create a log entry based on the photo 4.

[0232] As described in more detail with reference to method 700, device 500A optionally displays an indication of existing journal entries related to the content item along with a display of the content item (such as a calendar entry). Figure 6DD In FIG, device 500A detects selection of application icon 610 (eg, via contact 603). In response, Figure 6EE , and after one or more additional inputs, device 500A displays a user interface 692 that includes calendar details for a day selected by the user (e.g., December 17, 2022) and selectable options 694a-694b for different calendar events corresponding to the selected day. Selectable option 694a includes details for a calendar event at 8:00 a.m. Selectable option 694b includes details for a calendar event at 11:00 a.m.

[0233] exist Figure 6EE In , device 500A detects selection of 694b (e.g., via contact 603). In response, Figure 6FF , device 500A expands selectable option 694b to display user interface elements 695a-695c and selectable option 695d. User interface element 695a displays the title of the calendar event, user interface elements 695b and user interface element 695c display the time period and / or duration of the calendar event of the selected day, and selectable option 695d includes an indication that the log record entry corresponds to the calendar event and can be selected to initiate the process of displaying the log record entry. User interface element 695b includes details about the calendar event, such as the date and time of the calendar event. Therefore, in some embodiments, since the calendar event is associated with the log record entry, when displaying the details of the calendar event and / or other user interfaces associated with the calendar event, device 500A displays an indication of the existence of the log record entry (e.g., option 695d).

[0234] exist Figure 6FF In , device 500A detects selection of selectable option 695d (e.g., via contact 603). In response, Figure 6GG , device 500A displays a user interface 606 of a logging application including a representation 670 of a log entry. Selectable option 617 may be selected to initiate viewing of one or more animated video presentations associated with the activity event and / or log entry. In some embodiments, in response to Figure 6FF , device 500A displays the contents of log entry 674 (e.g., such as Figure 6U shown in ).

[0235] As described in more detail with reference to method 700, device 500A optionally displays an indication of existing log entries related to the content item along with a display of the content item (such as one or more photos). Figure 6HH , device 500A detects selection of application icon 635 (e.g., via contact 603). In response, Figure 6II, device 500A displays a user interface of a photo application and displays photo representations 696a-696d and corresponding indications of whether the corresponding photos are associated with a log entry. Photo representation 696a (corresponding to photo 1) is associated with (e.g., included in) a log entry for December 17 and is therefore displayed along with an indication of the log entry that is optionally selectable to display the log entry and optionally includes information about the log entry (e.g., the date of the log entry and / or an icon of the log application). Photo representation 696b (corresponding to photo 2) is associated with (e.g., included in) the same log entry for December 17 and is therefore displayed along with the same indication of the log entry. Photo representation 696c (corresponding to photo 3) is associated with (e.g., included in) the same log entry for December 17 and is therefore displayed along with the same indication of the log entry. However, photo representation 696d (corresponding to photo 4) is not associated with a log entry and, therefore, is not displayed with an indication of the log entry.

[0236] As described in more detail with reference to method 700, device 500A optionally allows a user to create a journal entry based on a content item, such as an achievement in a fitness application. Figure 6JJ In FIG, device 500A detects selection of application icon 620 (eg, via contact 603). In response, Figure 6KK , and after one or more additional inputs, device 500A opens the fitness application and displays achievements 697 (e.g., representations of achievements earned in the fitness application). Device 500A also displays a share option 698 that can be selected in a similar manner to the previously described share option 680.

[0237] exist Figure 6KK In , device 500A detects selection of share option 698 (e.g., via contact 603). In response, Figure 6LL In the example, device 500A is used with Figure 6BB Achievements 697 are displayed in user interface 686 in a similar manner to how photos 678 are displayed in user interface 686.

[0238] exist Figure 6LL In , device 500A detects selection of selectable option 618d (eg, via contact 603). In response, Figure 6MM In the example, device 500A is connected to Figure 6MThe user interface 640 including the prompt 699 is displayed in a similar manner to the prompt 642 in FIG. The prompt 699 includes information about the achievement 697, such as the type of activity. The prompt 699 also includes questions about the activity event. The user interface 640 can also be connected to Figure 6M The user interface 640 is interacted with in a similar manner to create a journal entry based on the achievement.

[0239] As described in more detail with reference to method 700, device 500A optionally allows a user to manually request a prompt to create a log entry. Figure 6NN , device 500A displays selectable options 616 and 618 in the user interface 606 of the logging application (similar to Figure 6D ).exist Figure 6NN In , device 500A detects selection of selectable option 618. In response, Figure 6OO , device 500A displays Figure 6D The user interface 640 optionally has Figure 6M Thus, in some embodiments, device 500A displays user interface 640 based on (recent) activities of the user and / or device 500A, in response to detecting manual input to do so, even if those activities do not meet the criteria for displaying prompt 638.

[0240] As described in more detail with reference to method 700 , device 500A optionally allows a user to create logging entries from a second device. Figure 6PP An exemplary device 500B including a touch screen 504B is shown. Device 500B is optionally associated with device 500A (e.g., device 500A is a smartphone logged into and / or configured with a user account, and device 500B is a smartwatch paired with device 500A and / or logged into and / or configured with the same user account). Figure 6PP , device 500B is displaying user interface 607, which is optionally a watch face user interface of device 500B and includes a time indication. In some embodiments, user interface 607 is a home screen user interface of device 500B (e.g., as shown in FIG. Figure 4A). Device 500B also displays prompt 609 on touch screen 504B. Prompt 609 indicates that it is related to a logging application and includes an invitation to create a log entry. Prompt 609 is optionally displayed on device 500B in response to meeting the same criteria as prompt 638 displayed on device 500A. In some embodiments, prompt 609 is displayed instead of prompt 638 displayed on device 500A. In some embodiments, prompt 609 is displayed on device 500B and prompt 638 is displayed on device 500A. Prompt 609 can be optionally selected to initiate the process of creating a log entry for typing into the logging application (e.g., on device 500A).

[0241] exist Figure 6PP In , device 500B detects selection of prompt 609 (e.g., via contact 603). In response, Figure 6QQ In some embodiments, device 500B expands prompt 609 and / or displays a prompt user interface (e.g., having one or more of the characteristics of user interface 640) including a question that can be responded to as part of creating a log record entry. In some embodiments, because the display size of device 500B is optionally small, the expanded prompt 609 (or other user interface) includes selectable options 611a-611c corresponding to predefined responses to the displayed questions, rather than the expanded prompt 609 (or other user interface) including a free-form text entry field for providing a response to the displayed question. Optional options 611a-611c are selectable to enter a response to prompt 609 (e.g., for inclusion in a log record entry). In some embodiments, the predefined response corresponding to optional options 611a-611c is an emoticon response. For example, optional option 611a is selectable to enter a smiley face response to prompt 609 (e.g., for inclusion in a log record entry) and optionally includes a representation (e.g., an image) of the corresponding response. Selectable option 611b may be selected to enter a sad face response to prompt 609 (e.g., for inclusion in a log entry), and optionally include a representation (e.g., image) of the corresponding response. Selectable option 611c may be selected to enter a relevant facial response to prompt 609 (e.g., for inclusion in a log entry), and optionally include a representation (e.g., image) of the corresponding response.

[0242] Figure 7 It is shown that according to Figures 6A to 6QQ Flowchart of method 700 of displaying a prompt to a user to generate a log record entry in some embodiments of the present invention. Method 700 is optionally performed on an electronic device (such as device 100, device 300 or device 500), as described above with reference to Figure 1A to Figure 1B 、 Figures 2 to 3 、 Figures 4A to 4B and Figures 5A to 5H Some operations in method 700 are optionally combined, and / or the order of some operations is optionally changed.

[0243] As described below, method 700 provides a method for displaying a prompt to a user to generate a log entry. This method reduces the cognitive burden on the user when interacting with the device user interface of the present disclosure, thereby creating a more efficient human-computer interface. For battery-powered electronic devices, improving the efficiency of user interaction with the user interface saves power and increases the time between battery charges.

[0244] In some embodiments, such as Figure 6A In the embodiment of the present invention, method 700 is performed at an electronic device (e.g., 500A) in communication with a display generation component (e.g., 504A) and one or more input devices (e.g., 504A). The electronic device may include, for example, a mobile device (e.g., a tablet, a smartphone, a media player, or a wearable device) that includes wireless communication circuitry that optionally communicates with one or more of: a mouse (e.g., external), a trackpad (optionally integrated or external), a touchpad (optionally integrated or external), a remote control device (e.g., external), another mobile device (e.g., separate from the electronic device), a handheld device (e.g., external), and / or a controller (e.g., external). In some embodiments, the display generation component is a display (optionally a touch screen display) integrated with the electronic device, an external display such as a monitor, a projector, a television, or a hardware component (optionally integrated or external) for projecting a user interface or making a user interface visible to one or more users. In some embodiments, the eye tracking device is a camera and / or motion sensor capable of determining the direction and / or location of the user's gaze. In some embodiments, method 700 is performed at or by a vehicle (e.g., at an infotainment system of the vehicle having or communicating with one or more display generating components and / or input devices).

[0245] In some embodiments, the electronic device detects (702a) an activity event associated with a user of the electronic device, wherein the activity event corresponds to one or more operations performed by the electronic device, such as Figure 6G Calling mom, Figure 6I Drive to the zoo and Figure 6K10 minutes, 30 minutes, 60 minutes, 120 minutes, 240 minutes, or 480 minutes). For example, the electronic device optionally tracks operations performed by the electronic device over time. In some embodiments, these operations correspond to actions performed by a user of the electronic device in a given day. For example, these operations optionally include: the electronic device calling a contact stored in the electronic device; the electronic device detecting movement of the electronic device from a first location to a second location (e.g., from a first city to a second city, from a first state to a second state, and / or from a first address to a second address); the electronic device detecting storage and / or completion of a workout (e.g., hiking, running, and / or swimming) using a workout application installed on the electronic device; the electronic device displaying content (e.g., podcasts, music, TV shows, and / or movies) to the user of the electronic device; the electronic device taking photos and / or videos and / or parsing photos and / or videos to match one or more contacts stored on the electronic device; and / or the electronic device detecting the presence of the electronic device at a location (e.g., a park, a restaurant, and / or the user's workplace) for an extended period of time (e.g., greater than 5 minutes, 10 minutes, 30 minutes, 60 minutes, or 120 minutes). Additionally or alternatively, in some embodiments, the electronic device detects the above operations performed by one or more other electronic devices associated with the user (e.g., the user's smartwatch, the user's tablet computer, and / or the user's smartphone, which are optionally all logged into the same user account associated with the user).

[0246] In some embodiments, in response to detecting an activity event associated with a user (702b), the activity event is determined to satisfy one or more criteria, such as Figure 6GIn some embodiments, the one or more criteria include a criterion that is satisfied when the activity event is a noteworthy activity by the user of the electronic device based on one or more factors described below. In some embodiments, the one or more criteria include a criterion that is satisfied when the activity event occurs within a threshold amount of time from the current time (e.g., within the last day, week, month, or year). For example, the criteria are optionally satisfied by the electronic device calling a popular contact (e.g., a contact with whom the electronic device interacts via a messaging application installed on the electronic device, via a phone call from the electronic device, and / or other communication applications installed on the electronic device for more than a threshold amount of time (e.g., more than 5 minutes, 10 minutes, 30 minutes, 60 minutes, 120 minutes, or 240 minutes during a given 30 minute, 60 minute, 120 minute, 240 minute, 480 minute, 960 minute, or 1920 minute time period) and / or exceeding a threshold proportion of device usage or communication usage (e.g., more than 5%, 25%, 50%, 60%, 70%, 80%, or 90%), recording an exercise in the electronic device, or detecting movement of the electronic device from a first location to a second location greater than a threshold distance from the first location (e.g., greater than 3 miles, 5 miles, 20 miles, 50 miles, 100 miles, 150 miles, 1000 miles, 3000 miles, or 5000 miles). Alternatively, calling a telephone number by the electronic device that is not stored in the electronic device and / or not associated with a contact in the user profile of the electronic device, or detecting movement of the electronic device from a first location to a second location less than the above-mentioned threshold distance (e.g., 1 foot, 2 feet, 3 feet, 4 feet, or 5 feet), optionally does not satisfy the criteria.

[0247] In some embodiments, the electronic device displays (702c) on the electronic device via a display generating component a prompt associated with the logging application, wherein input directed to the prompt associated with the logging application initiates a process of providing input for a logging entry associated with the activity event in the logging application, such as Figure 6L638 in the prompt. The prompt optionally includes user-selectable options, as will be described below. The prompt is optionally a notification displayed on a lock screen user interface, a wake screen user interface, or a home screen user interface of the electronic device. In some embodiments, the user-selectable options are selectable to initiate a process of typing into a logging application and / or a process of receiving input of content to be typed into the logging application via the prompt (e.g., without displaying the logging application). In some embodiments, the prompt includes information about the user activity event (e.g., information such as the location of the activity event, the time of the activity event, and / or a photo of the activity event). In some embodiments, the logging application is an application that receives and / or stores log entry input from a user of the electronic device.

[0248] In some embodiments, based on determining that the activity event does not meet one or more criteria, the electronic device forgoes displaying (702d) a prompt associated with the logging application via the display generation component if Figure 6G The call in the activity event is to the zoo, which is not a popular contact. In some embodiments, if the activity event does not meet one or more criteria, if the user of the electronic device wishes to create a log entry for the activity event in the logging application, the user of the electronic device must manually launch the logging application and provide input from within the logging application to create the log entry. Displaying a prompt to the user of the electronic device to provide content to the logging application based on the user's activity provides the user with a simple and personalized platform for creating log entries, thereby reducing the number of inputs required to create a log entry.

[0249] In some embodiments, an activity event does not meet one or more criteria, such as if Figure 6I In some embodiments, after detecting the activity event, the electronic device receives a first user input via one or more input devices corresponding to a request to manually create a corresponding log entry in the log application, such as Figure 6C 603. In some embodiments, the first user input is selecting a logging icon from a home screen user interface of the electronic device, or selecting an option to manually create a logging entry within a user interface of a logging application.

[0250] In some embodiments, in response to receiving the first user input, the electronic device initiates manual creation of a corresponding log entry in a log application (such as Figure 6C Contact 603 and Figure 6D Contact 603) to create Figure 6EIn some embodiments, the selection initiates the process of typing into the logging application and creating the log entry. In some embodiments, the log entry is created automatically. In alternative embodiments, the electronic device requires additional user input to create the log entry. In some embodiments, initiating the process of manually creating the log entry includes displaying a user interface into which user input included in the log entry is typed. Providing a manual typing point for the log entry provides the user with a simple typing point for creating the log entry that does not rely on being prompted to create the log entry, thereby providing increased flexibility in the creation of the log entry.

[0251] In some embodiments, the first user input is directed to a content item displayed in a first application that is different from the logging application (such as Figure 6AA 603 in contact). For example, the first application is optionally stored or installed on the electronic device and is capable of communicating with the logging application. In some embodiments, the first application is an application that stores and / or displays content items such as photos, music, fitness achievements, video content, calendar events, routes, books, podcasts, or games. In some embodiments, the content items are displayed with a user-selectable option that can be selected to initiate the process of creating a log entry in the logging application with or without stopping the display of the first application. In some embodiments, the process of manually creating a corresponding log entry in the logging application utilizes the content item as part of the log entry, such as Figure 6AA 678 in. In some embodiments, the electronic device creates a log entry within a logging application that is connected to and / or includes the content item. In some embodiments, the electronic device displays a prompt associated with the content item as part of a process of manually creating a corresponding log entry. In an alternative embodiment, the electronic device displays a log entry user interface configured to receive user input for populating the log entry, wherein the log entry already includes the content item. Automatically populating the log entry with the content item provides a simple way for the user to log about the content item, thereby reducing the amount of input required to create a log entry for the content item.

[0252] In some embodiments, the first user input is directed to a user interface displayed in the logging application, such as Figure 6CIn some embodiments, the log entry is created directly from within the logging application. For example, the first user input includes selecting an option displayed in a user interface of the logging application for creating a log entry in the logging application. Providing a manual way to start a log entry from within the logging application provides a simple way for the user to create a log entry from a user interface that is expected to include an option to create a log entry, thereby reducing the amount of input required to find the log entry creation point.

[0253] In some embodiments, before displaying the user interface in the logging application, the electronic device receives a second user input corresponding to a request to display the logging application via one or more input devices, such as Figure 6A 603 in (eg, receiving selection of an icon for a logging application on a home screen user interface of an electronic device).

[0254] In some embodiments, in response to receiving the second user input, the electronic device requires user authentication (such as Figure 6B In some embodiments, user authentication protects the log entries stored in the logging application. In some embodiments, the electronic device will only allow access to the logging application upon receiving a successfully authenticated authentication input, and will not display the logging application if the authentication input is not successfully authenticated. Requiring authentication for entries in the logging application ensures that the logging entries are secure and improves user privacy and security.

[0255] In some embodiments, user authentication includes facial recognition, fingerprint recognition, or password recognition (such as in Figure 6B In some embodiments, user authentication requires the user to scan or take an image of their face via one or more cameras of the electronic device, scan their fingerprint via one or more fingerprint sensors of the electronic device, and / or enter a password via the touch screen of the electronic device. Requiring authentication for entries to the logging application ensures that the logging entries are secure and improves user privacy and security.

[0256] In some embodiments, after creating a journal entry in the journal application, the electronic device displays a user interface of the journal application including multiple journal entries (e.g., 608, 613, 612, and / or 614) (including the journal entry (e.g., 670)) via the display generation component, wherein the journal entries are displayed as pages of a book in the user interface of the journal application (such as Figure 6CIn some embodiments, the content of a given log entry and / or an indication of the plurality of log entries are displayed on one or more virtual pages of a virtual book. Displaying the log entries as pages of a book in the user interface is an efficient way to arrange the log entries and reduces the number of inputs required to navigate to the correct log entry.

[0257] In some embodiments, after creating a log entry in the log application, the electronic device displays a user interface of the log application including multiple log entries (e.g., 608, 612, 613 and / or 614) (including the log entry (e.g., 670)) via the display generation component, wherein the multiple log entries are displayed in the user interface of the log application (such as Figure 6C The log entry may be displayed in the user interface 606. For example, the log entry may be displayed in the user interface after one or more log entries having an earlier creation and / or last edit date than the log entry, and / or before one or more log entries having a later creation and / or last edit date. Displaying the log entries in chronological order in the user interface enables the user to easily locate a desired entry, thereby reducing the number of inputs required to locate and / or access the desired entry.

[0258] In some embodiments, a logging application that includes logging entries is accessible via a computer connected to an electronic device such as Figure 6PP In some embodiments, the electronic device is a tablet computer, a watch, a computer, a smart TV, or a set-top box. Therefore, in some embodiments, the second electronic device is a mobile phone, and the electronic device is a smart watch. In this case, optionally, a log entry is typed and / or created via an input at a smart watch (e.g., an electronic device), and when the second electronic device displays a log recording application, the second electronic device displays the log entry created in response to the input detected at the electronic device. In some embodiments, when the second electronic device and the electronic device are both configured with and / or logged into the same user account and / or user profile, the second electronic device is associated with the electronic device. Allowing log entry creation at multiple devices and / or a log recording application to display various ways of creating log entries is provided to the user.

[0259] In some embodiments, an activity event does not meet one or more criteria, such as Figure 6AAIn some embodiments, after detecting an activity event associated with a user and abandoning displaying a prompt associated with a logging application via a display generating component, the electronic device receives a first user input directed to the logging application via one or more input devices, the first user input corresponding to a request for a corresponding prompt associated with the logging application, wherein the corresponding prompt is associated with the activity event, such as Figure 6CC In some embodiments, the first user input is directed to a user interface of the logging application. For example, the first user input is a selection of a "Show Logging Tips" button displayed in the user interface of the logging application. In some embodiments, the first user input is directed to content such as a photo, a photo album, a map, a web search, or a podcast.

[0260] In some embodiments, in response to receiving the first user input, the electronic device displays a corresponding prompt (e.g., 690) via the display generation component, wherein input directed to the corresponding prompt (e.g., 690) initiates an action such as by typing text into the text entry field 644 and selecting Figure 6CC The process of providing input for a corresponding log entry associated with the activity event in the logging application using the optional option 656 in the prompt. The prompt optionally includes user-selectable options, as will be described below. The prompt optionally includes information about the experience or information about the user's activity event, as will be described below. Thus, in some embodiments, even if the activity event does not meet one or more criteria, the user input can cause the electronic device to manually display a corresponding prompt, which optionally includes information guiding the user to create a log entry, as described herein. Providing the user with the option to request the prompt provides the user with a quick way to display information related to the recent activity to be written, thereby reducing battery usage of the electronic device.

[0261] In some embodiments, the reminder includes one or more details related to the activity event, such as Figure 6CC In some embodiments, the one or more details include the type of activity performed as part of the activity event (e.g., a run, a phone call, a trip, a television program, a podcast, and / or music), the friends involved in the activity event (e.g., friends or family), the time of the activity event (e.g., from a first specific time to a second specific time and / or a specific date), and / or photos or videos or other content associated with and / or captured during the activity event. Providing the user with details of the activity facilitates efficient creation of log entries, thereby reducing the amount of input required to correct undesirable portions of the log entry.

[0262] In some embodiments, while displaying a prompt (e.g., 638) associated with a logging application, the electronic device receives a first user input directed to the prompt (e.g., 638) via one or more input devices, such as Figure 6L 603 in (e.g., selection of the prompt, a tap and hold directed to the prompt, or a swipe input directed to the prompt). In some embodiments, the first user input is an input directed to one or more user interfaces displayed by the electronic device in response to detecting a selection of the prompt.

[0263] In some embodiments, in response to receiving the first user input, and based on determining that the first user input includes voice input, the electronic device incorporates the voice input into the log record entry, such as if the electronic device receives the voice input Figure 6M 644 in the text entry field 644. For example, the electronic device optionally receives voice input from the user to obtain a longer entry that the user does not want to type manually. In some embodiments, the voice input is typed into the log record entry as text.

[0264] In some embodiments, based on determining that the first user input includes an emoticon input, the electronic device incorporates the emoticon input into the log record entry, such as if the electronic device receives the emoticon input Figure 6M . For example, the electronic device optionally receives emoji input from the user. In some embodiments, the emoji input includes detecting a selection of one or more emoji keys displayed in an emoji keyboard or other emoji user interface. For example, the electronic device optionally displays one or more emojis and a prompt to the user via a display device (or a user interface displayed in response to a selection of the prompt), and upon receiving a selection of one of the one or more emojis, enters the selected emoji into the log entry. In some embodiments, the emoji input is a voice input directed to an animated emoji (e.g., optionally customized by the user), and the animated emoji speaking the detected / recorded voice input is entered into the log record entry. Providing users with various ways to enter content into log entries avoids erroneous entry of log entries and reduces the number of inputs required to correct such erroneous entry.

[0265] In some embodiments, the electronic device receives a first user input via one or more input devices corresponding to a request to create a corresponding log entry associated with the content item, such as Figure 6R 603. In some embodiments, the content item is a photo, music, fitness achievement, video content, calendar event, route, book, podcast, or game.

[0266] In some embodiments, in response to receiving the first user input, the electronic device creates a corresponding log entry, including linking the corresponding log entry to the content item, such as Figure 6T 670 . In some embodiments, a representation of the content item is stored in the corresponding log entry to alert the user that the corresponding log entry is associated with the content item. In addition, when the user selects the representation of the content item, the electronic device optionally displays a user interface of the application that includes the content item (e.g., optionally different from the user interface of the log entry application). Providing a way for the user to link the content item with the log entry reduces the number of inputs required to navigate to and / or display the content item associated with the log entry.

[0267] In some embodiments, after receiving the first user input and creating the corresponding log entry, the electronic device receives a second user input corresponding to a request to access the content item via one or more input devices, such as Figure 6FF 603 in the contact. For example, the second user input is optionally a selection of a content item within a corresponding content browsing and / or playback application that is not a logging application. In some embodiments, a representation of the content item is stored with the corresponding log entry. Thus, the second user input is optionally a selection of a representation of the content item.

[0268] In some embodiments, in response to receiving the second user input to access the content item, the electronic device accesses (e.g., displays) the content item (e.g., 678) and displays a representation of the corresponding log entry via the display generation component, such as Figure 6GG In some embodiments, the electronic device displays a representation of the log entry simultaneously with the content item. In some embodiments, the electronic device displays a representation of the log entry without the content item. In some embodiments, the representation of the log entry is selectable to display (the content of) the corresponding log entry, including the content item. In some embodiments, the representation of the log entry is a visual indication indicating that the corresponding log entry is associated with the content item. In some embodiments, the visual indication is displayed simultaneously with the content item. In some embodiments, the visual indication is selectable to open the corresponding log entry. Appearing the log record when the user revisits the content item provides an efficient way for the user to access the log record, thereby reducing the number of inputs required to access the log record entry when revisiting the content item.

[0269] In some embodiments, while displaying a prompt associated with a logging application (e.g., 638), the electronic device receives a first user input directed to the prompt associated with the logging application via one or more input devices, such as Figure 6LIn some embodiments, the first user input includes a click, tap, or swipe input directed to the prompt. In some embodiments, the electronic device displays an additional user-selectable option in the prompt that, when selected, displays a user interface described below that includes one or more details related to the event.

[0270] In some embodiments, in response to receiving the first user input, the electronic device displays, via the display generation component, a user interface including one or more details related to the activity event, such as Figure 6M In prompt 642. In some embodiments, the details include songs listened to during the active event, routes taken during the active event, photos or videos taken during the active event, restaurants eaten during the active event, fitness information obtained during the active event, people associated with the active event (e.g., people who appear in photos taken during the active event and / or people who were at the location of the active event during the active event), podcasts listened to during the active event, movies or shows watched during the active event, and / or locations visited during the active event. Providing the user with details of the activity facilitates efficient creation of log entries, thereby reducing the amount of input required to correct undesirable portions of the log entry.

[0271] In some embodiments, the one or more details include one or more indications of one or more people associated with one or more photos taken by the electronic device during the active event, such as Figure 6M In some embodiments, the electronic device determines the persons associated with the photos based on the photo activity stored on the electronic device. In some embodiments, the persons are indicated in the user interface as representative avatars or initials. In some embodiments, the persons identified are those who were with the electronic device when the electronic device captured the pictures or videos during the activity event and / or even those who appeared in the pictures and / or videos captured during the activity. Identifying the persons associated with the activity event facilitates efficient creation of log entries, thereby reducing the number of inputs required to correct undesired portions of the log entries.

[0272] In some embodiments, while displaying a prompt associated with a logging application (e.g., 638), the electronic device receives a first user input directed to the prompt associated with the logging application via one or more input devices, such as Figure 6L Contact 603 in (e.g., input to interact with the prompt, as described herein).

[0273] In some embodiments, in response to receiving the first input, the electronic device displays a first question related to the activity event via the display generation component, such as Figure 6MIn some embodiments, the first question is a question about one or more details associated with the event. For example, the first question optionally includes a question about the location of the electronic device during the event and / or people in a photo taken by the electronic device during the event.

[0274] In some embodiments, while displaying a first question related to the activity event (e.g., 642), the electronic device receives, via one or more input devices, a second user input corresponding to a first response indicating a response to the first question, wherein at least a portion of the first response is included in a log record entry, such as Figure 6N 644 in the text entry field. In some embodiments, the response includes text input provided by the user (e.g., via a hardware or software keyboard) and includes the user's response to the first question: for example, a description of the location and a person's reaction to the location. In some embodiments, the log entry includes one or both descriptions. Prompting the user and incorporating the details of the response into the log entry facilitates efficient filling of the log entry with content.

[0275] In some embodiments, after receiving the second user input, the electronic device displays a second question related to the activity event via the display generation component, wherein the second question is based on the first response, such as Figure 6O 658 in prompt. In some embodiments, the second question is determined by a machine learning model. In some embodiments, the content of the second question is based on the content of the first response, and if a different response to the first question is provided, the content of the second question is optionally different. For example, if the first response introduces a specific activity that occurred during the activity event, the second question is optionally directed to that specific activity. For example, if the device detects an activity event of hiking, the first question is optionally "How was your hike today?", and if the first response does not mention a specific activity other than hiking, the second question is optionally "Describe the hike in three words." However, if the first response is "Great! There was a great place to meditate along the way" - "meditation" corresponds to an activity different from hiking - the second question is optionally "Describe today's meditation in three words." Providing subsequent questions based on earlier responses increases the amount of content related to the activity event in the log entry.

[0276] In some embodiments, after receiving the second user input, the electronic device displays a second question related to the active event via the display generation component, wherein the second question is based on information associated with the active event, such as if Figure 6OThe prompt 658 in is based on the response in the text entry field 44 in Figure N. In some embodiments, information associated with the active event includes songs listened to during the active event, routes taken during the active event, photos taken during the active event, restaurants eaten during the active event, fitness information obtained during the active event, people associated with the active event, podcasts listened to during the active event, movies or shows watched during the active event, and / or locations visited during the active event. For example, the first question is optionally based on a person detected at the active event, such as "How about lunch with Abby?" because Abby was determined by the electronic device to be present at the active event. Providing subsequent questions based on earlier responses increases the amount of content related to the active event in the log entry.

[0277] In some embodiments, after receiving the second user input, the electronic device displays a second question related to the activity event via the display generation component, where the second question is based on one or more previous logging entries in the logging application, such as if Figure 6O Tip 658 in the Figure 6C In some embodiments, the electronic device determines the second question using information entered by the user in previous log entries. For example, if one or more of the previous log entries (often) discusses meditation at the top of a particular mountain, and the activity event includes a hike on the particular mountain, the second question optionally includes a question about meditation, such as "Nice hike, did you meditate today?" Providing follow-up questions based on earlier responses increases the amount of content in the log entry that is relevant to the activity event.

[0278] In some embodiments, the one or more criteria include criteria that are satisfied based on a relationship between the current time of day at the electronic device and information associated with a user of the electronic device, such as if Figure 6LIn some embodiments, the prompt 638 in is displayed outside working hours (for example, rather than being displayed during working hours). In some embodiments, this relationship creates a "smart" time for electronic equipment to prompt the user. For example, if the current time of the day is 6 o'clock in the afternoon (for example, the end of the day) and the information associated with the user of the electronic equipment indicates that the user usually uses the electronic equipment at 6 o'clock in the afternoon, then this relationship optionally indicates that this is the "smart" time for prompting, and meets the standard. In some embodiments, "smart" time is optionally based on the setting preferred by the user. In additional embodiments, "smart" time is optionally based on the focus mode of the device (for example, when the electronic equipment is in a mode that suppresses one or more notifications (for example, for incoming calls, incoming messages or incoming emails), prompting delays). Providing prompts to users at appropriate times increases the possibility of user participation in prompts, and avoids wasting resources on display prompts when prompts are unlikely to interact with them.

[0279] In some embodiments, the one or more criteria include criteria that are satisfied based on one or more frequencies with which the user of the electronic device contacts contacts associated with the activity event, such as if Figure 6G For example, if the electronic device detects that an activity event involves a popular contact that the electronic device contacts relatively frequently (e.g., more than 2, 3, 5, or 10 times per day) (e.g., the popular contact appears in the activity event), the criterion is met. Alternatively, if the electronic device detects that an activity event involves a contact that the electronic device contacts relatively infrequently (e.g., less than 2, 3, 5, or 10 times per day), the criterion is not met.

[0280] In some embodiments, the one or more criteria include movement of the electronic device from a first location to a second location associated with the activity event (such as from a home to a zoo, for example). Figure 6I For example, if the electronic device moves from a first location to a location that the electronic device frequently visits (e.g., more than 2, 3, 5, or 7 times per week), the criterion is met (otherwise, the criterion is optionally not met). Alternatively, if the electronic device moves from a first location to a second location, and the second location is a location that the electronic device relatively infrequently visits (e.g., less than 1 time per year), the criterion is met (otherwise, the criterion is optionally not met).

[0281] In some embodiments, the one or more criteria include one or more photos associated with the event taken by the electronic device (such as taking photo 1 (e.g., 636), such as in Figure 6KFor example, if the photo includes a popular contact as described above, the criterion is met. Alternatively, if the photo does not include a popular contact, the criterion is not met. For example, if the photo is taken at a location that is not frequently visited (e.g., less than once a year) (such as when the user of the electronic device is on vacation), the criterion is met. As another example, if the electronic device takes more than a threshold number (e.g., 1, 3, 5, 10, 20, 50, or 100 photos during the activity event, the criterion is met, otherwise the criterion is not met.

[0282] In some embodiments, the one or more criteria include criteria that are satisfied based on one or more of the operations performed by a second electronic device associated with the user of the electronic device, where the operations are associated with an activity event, such as if a smartwatch is worn at a zoo and carried Figure 6PP , 5, 10, or 20 times during a time period such as 6 hours, 12 hours, 1 day, 3 days, 7 days, or 30 days), the criterion is met. In some embodiments, if the second electronic device is a watch and the operation is playing a song that the electronic device plays frequently (e.g., more than 5, 7, or 10 times per day), the criterion is met. On the other hand, if the second electronic device (e.g., a watch) performs an operation that is not significantly different from the operation performed by the second electronic device on a typical day, the criterion is not met.

[0283] In some embodiments, the one or more criteria include a method based on a user's activity event (such as a Figure 6G For example, if the electronic device detects a call to a popular contact (e.g., a contact that appears in the active event) during or after the active event, the criterion is met. For example, if the electronic device detects a photo (e.g., a photo taken during the active event) being opened during or after the active event, the criterion is met.

[0284] In some embodiments, the one or more criteria include criteria satisfied based on one or more applications of one or more applications accessed by the electronic device that are associated with the activity event, such as Figure 6IFor example, if the electronic device detects that a fitness app is opened during or after an activity event, the criteria are met. For example, if the electronic device detects that a map app is opened during or after an activity event, the criteria are met. Providing criteria for prompting users allows users to recall details of the activity event in an efficient manner, thereby increasing the likelihood of engaging with the prompt and reducing the waste of resources displaying prompts or creating useless logging entries.

[0285] In some embodiments, after detecting an activity event and creating a log entry associated with the activity event in a log application, the electronic device displays selectable options associated with the activity event via a display generating component, such as Figure 6V In some embodiments, the selectable options include one or more representations of the activity event. In some embodiments, the selectable options include text describing the activity event. In some embodiments, the selectable options are displayed on a wake screen user interface, a lock screen user interface, or a home screen user interface of the electronic device. In some embodiments, the user selectable option is selectable to initiate a process of viewing an animated video presentation associated with the log entry (e.g., of the content included in the log entry).

[0286] In some embodiments, while displaying selectable options associated with an active event (e.g., 676), the electronic device receives a first input corresponding to a selection of the selectable option via one or more input devices, such as Figure 6V 603. In some embodiments, the first input includes a click, tap, or swipe input directed to a selectable option.

[0287] In some embodiments, in response to receiving the first input, the electronic device displays an animated video presentation associated with the log entry via a display generation component, wherein the animated video presentation associated with the log entry includes one or more entries of the log entry and one or more content items associated with the activity event, such as Figure 6WIn some embodiments, the content item is a photo, an achievement, a representation of a content item, such as a route, a text entry, and / or an emoji entry that is typed into the log entry when the log entry is created. In some embodiments, the electronic device displays the animated video presentation along with the music. In some embodiments, the music is not part of the log entry (e.g., the electronic device does not detect an input from the user associating the music with the log entry). Therefore, in some embodiments, the electronic device (automatically, without user input) selects the music to be played and displays the animated video presentation. Providing the user with the option of viewing the animated video presentation for the log entry provides efficient viewing of the log entry and reduces the number of inputs required to access the content of these log entries.

[0288] In some embodiments, displaying selectable options (e.g., 638) includes the electronic device displaying selectable options based on determining that the current time of day at the electronic device satisfies one or more display criteria, such as Figure 6L In some embodiments, the prompt 638 is displayed outside of working hours (e.g., rather than during working hours). For example, if the current time of day is outside of working hours, the criterion is met. In some embodiments, the criterion is met if the current time of day is at least a time threshold (e.g., 15, 30, or 60 minutes) earlier than the typical time of day that the user of the electronic device stops using the electronic device. In some embodiments, the criterion is met if the current time of day is at least a time threshold (e.g., 15, 30, or 60 minutes) after a workout. In some embodiments, the criterion is met if the current time of day is at least a time threshold (e.g., 1, 2, 5, or 7 days) after an activity event.

[0289] In some embodiments, based on determining that the current time of day at the electronic device does not meet one or more display criteria, the electronic device forgoes displaying a selectable option (e.g., Figure 6L In some embodiments, the criterion is not met if the current time of day is during work hours. In some embodiments, the criterion is not met if the current time of day is during "evening hours" when the user of the electronic device does not typically use the electronic device. Displaying selectable options at appropriate times increases the likelihood that the user will engage with the selectable options, reduces wasting resources on displaying selectable options when interaction with the selectable options is not possible, and avoids interruptions in the use of the device, thereby reducing errors in use.

[0290] In some embodiments, the selectable option (e.g., 676) is displayed on a user interface of the electronic device outside of the logging application, such as Figure 6V602. In some embodiments, the selectable options are displayed on a wake screen user interface, a lock screen user interface, a user interface of an application other than a logging application (e.g., a photo application, a messaging application, an email application, and / or a movie / television program playback application), or a home screen user interface of the electronic device.

[0291] In some embodiments, selectable options are displayed on the user interface of the logging application, such as if Figure 6V Notification 676 is displayed on Figure 6T In some embodiments, the selectable options are displayed within the user interface of the logging application. In some embodiments, the selectable options are displayed within a separate tab of the user interface of the logging application. Displaying the selectable options for the animated video presentation in a different user interface increases the likelihood of user interaction, thereby reducing the number of inputs required to view the animated video presentation, and reduces wasting resources on displaying the selectable options when interaction with the selectable options is not possible.

[0292] In some embodiments, the animated video presentation associated with the log entry includes first-party content, third-party content, or both, such as Figure 6W The animated video presentation 679 includes photo 1 and photo 2, but also includes an online review of the zoo. In some embodiments, first-party content is content stored on an electronic device, such as key photos, songs, web searches, photos, people and / or faces, names, routes and / or maps, and locations. In some embodiments, third-party content is stored on a separate electronic device or server, such as online reviews and online photos. For example, the animated video presentation optionally includes a map taken to the event, photos from the event, and also displays the names of the people involved in the event or reviews of restaurants visited during the event, where the reviews are optionally downloaded from a third-party server that includes reviews, photos and / or other (optionally, crowdsourced) information about restaurants (including restaurants visited). Expanding the content associated with the log record entry to include multiple content sources provides a more comprehensive animated video presentation and reduces the need for further input to manually search for additional information related to the event and / or log record entry.

[0293] In some embodiments, the display of the animated video presentation associated with the log entry includes presentation of music, such as Figure 6WIn some embodiments, the electronic device automatically selects the music (e.g., without user input for selecting the music). In some embodiments, the electronic device selects the music based on the log entry. For example, if the log entry is about a fun outdoor activity, the electronic device will optionally select upbeat music for the animated video presentation. In some embodiments, the electronic device includes a user-selectable option as part of the animated presentation for the user to change the music. Incorporating music into the animated video presentation avoids the need for additional user input to play the music along with the animated presentation.

[0294] In some embodiments, the prompt is displayed in a widget displayed in the system user interface of the electronic device via a display generating component, such as Figure 6Y In some embodiments, the widget is displayed on the home screen user interface of the electronic device. In some embodiments, the widget is displayed on the side screen user interface of the electronic device (e.g., a user interface including one or more widgets for different applications, including a widget including a prompt). In some embodiments, the widget includes the same information included in the prompt. In some embodiments, the widget includes a portion of the information included in the prompt. Displaying the prompt in the widget increases the likelihood that the user will interact with it and reduces the waste of resources on displaying selectable options when it is unlikely that the selectable options will be interacted with.

[0295] In some embodiments, such as if Figure 6V The notification 676 is displayed on the Figure 6AIn some embodiments, the prompt is displayed in the first application other than the journaling application. In some embodiments, the first application is a note application, a music application, a fitness application, a map application, a photo application, a content viewing application, or any other application other than the journaling application. In some embodiments, the prompt is displayed in the first application based on an activity event associated with the first application. For example, if the electronic device detects the completion of an achievement defined by a fitness application on the device as an activity event (or part of an activity event), the prompt is optionally displayed in the fitness application. As another example, if the electronic device determines the use of an application (or multiple applications) as part of an activity event, the prompt is optionally displayed in the application (or the multiple applications). In some embodiments, the prompt is displayed in the first application simply because the electronic device is displaying the user interface of the first application when the prompt is to be displayed. Prompting the user when the electronic device is displaying an application other than the journaling application increases the likelihood that the user will interact with the prompt and reduces the number of inputs required to create a journal entry.

[0296] In some embodiments, the electronic device receives a first user input (e.g., Figure 6L 638). In some embodiments, the first user input includes a click, tap, or swipe input directed to the prompt.

[0297] In some embodiments, in response to receiving the first user input, the electronic device displays information related to the activity event via the display generation component without stopping the display of the first application, for example, if the electronic device receives a corresponding Figure 6A In some embodiments, the information is displayed simultaneously with the first application in the separate user interface within the first application or overlaid on the first application. In some embodiments, the electronic device enables the user to switch between the first application and the separate user interface. Providing a way for the user to interact with the prompt without leaving the first application does not interrupt the user's interaction with the first application, reduces the number of inputs returned to the first application, and reduces errors in device use.

[0298] In some embodiments, the logging entries are accessible via a logging application, such as Figure 6T670 in the representation. In some embodiments, the log entry is viewable via the logging application. In some embodiments, the log entry is searchable via the logging application. In some embodiments, the log entry is accessible via the logging application. Storing the log entry in the logging application provides a user with an accessible repository to access the log entry at a later date, thereby reducing the number of inputs required to access the log entry.

[0299] In some embodiments, the reminder is displayed as a notification on an electronic device, such as Figure 6L 638 in the prompt. In some embodiments, the prompt is displayed as a notification on the lock screen or other user interface. Thus, in some embodiments, the prompt is displayed as a notification in the same manner and / or in the same user interface as notifications are displayed for other applications (e.g., an email application, a messaging application, a phone application, and / or a calendar application). Displaying the prompt as a notification provides an accessible and consistent warning to the user, thereby reducing the amount of input required to create a log entry and reducing errors in device use.

[0300] In some embodiments, in response to detecting an activity event associated with a user, and based on determining that the activity event satisfies one or more criteria, the electronic device initiates a process of displaying a second prompt associated with a logging application on a second electronic device associated with the electronic device (e.g., both the electronic device and the second electronic device are logged into and / or configured with the same user account or user profile), wherein input directed to the second prompt initiates a process of providing input for a logging entry associated with the activity event in the logging application, such as Figure 6PP 609 and contact 603 in. In some embodiments, the second electronic device is a watch and the electronic device is a phone. Therefore, the second prompt is optionally displayed on the watch and includes an example response to the second prompt in the form of one or more emojis. In some embodiments, when the user selects an emoji or one or more emojis as a response, the electronic device creates a log record entry including these emoji responses. In some embodiments, if the second prompt is displayed on the second electronic device, the prompt is not displayed on the electronic device. In some embodiments, if the prompt is displayed on the electronic device, the second prompt is not displayed on the second electronic device. In some embodiments, the prompt is displayed on the electronic device and the second prompt is displayed on the second electronic device. Prompting the user on different electronic devices associated with the electronic device increases the likelihood that the user will interact with the prompt, thereby reducing the number of inputs to create a log record entry.

[0301] In some embodiments, the prompt displayed by the electronic device is configured to accept a first type and a second type of input, such as Figure 6L In some embodiments, the first type of input is an emoji input and the second type of input is a text (e.g., speech) input. For example, if the electronic device is a phone, the phone displays a prompt that is optionally configured to receive both emoji input (e.g., from an emoji keyboard displayed by the phone) and / or text input (e.g., from a text keyboard displayed by the phone).

[0302] In some embodiments, the second prompt displayed by the second electronic device is configured to accept the first type of input but not the second type of input, such as Figure 6QQ 611a-611c in . For example, if the second electronic device is a watch associated with a phone (e.g., as previously described), the watch displays a prompt that is optionally configured to receive emoji input (e.g., from an emoji keyboard displayed by the phone) but not text input (e.g., because the watch does not display a text keyboard with the prompt). Providing the user with different input options for different prompts ensures that the prompts occupy the appropriate screen size for the respective device on which they are displayed.

[0303] It should be understood that Figure 7 The specific order in which the operations are described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations can be performed. A person of ordinary skill in the art will recognize many ways to reorder the operations described herein.

[0304] The operations in the above information processing method are optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (e.g., a processor in combination with a processor). Figure 1A to Figure 1B 、 Figure 3 、 Figures 5A to 5H In addition, the above reference Figure 7 The operation is optionally performed by Figure 1A to Figure 1B. For example, the detection operation 702a and the display operation 702c are optionally implemented by the event classifier 170, the event identifier 180, and the event handler 190. The event monitor 171 in the event classifier 170 detects contact on the touch screen 504, and the event distributor module 174 transmits the event information to the application 136-1. The corresponding event identifier 180 of the application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first position on the touch screen corresponds to a predefined event or sub-event, such as the selection of an object on the user interface. When the corresponding predefined event or sub-event is detected, the event identifier 180 activates the event handler 190 associated with the detection of the event or sub-event. The event handler 190 optionally utilizes or calls the data updater 176 or the object updater 177 to update the application internal state 192. In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly know how to Figure 1A to Figure 1B The components depicted in the implementation of other processes.

[0305] Figures 8A to 8C A process for creating a first log record in a logging application (such as the logging application described with reference to methods 700 , 900 , and 1000 ) is depicted (eg, to help a user create their first log record).

[0306] Figure 8A An exemplary device 500A is shown that includes a touch screen 504A and is displaying a user interface 802 that corresponds to Figure 6A The user interface 602 shown in FIG. The user interface 802 includes an application icon 655, which corresponds to the application icon 655 shown in FIG. Figure 6A The described logging application for creating and accessing logging entries.

[0307] exist Figure 8A , device 500A detects selection of application icon 655 (e.g., via contact 803). In some embodiments, in response to detecting selection of application icon 655 and based on determining that the user has not previously saved a log entry (e.g., the user is invoking the logging application for the first time), device 500a optionally displays a menu item such as a reference icon. Figure 6B The described authentication UI then displays as Figure 8B User interface 806 is shown.

[0308] User interface 806 includes affordances 808a, 808b, and 808c that indicate to the user the various options the user has for creating a log entry. User interface 806 includes affordance 808d that is selectable to initiate creation of a new log entry.

[0309] In response to detecting selection of affordance 808d, device 500A displays the following Figure 8C The log entry user interface 810 is shown to allow a user to create a new log entry. The log entry user interface 810 is optionally a user interface of a logging application. The log entry user interface 810 includes a log entry field 812 for adding text and / or content items to the log entry. In some embodiments, the log entry field 812 has a reference to Figure 6M One or more of the characteristics of the described text entry field 644. Content items that can be added to a log entry using the log entry user interface 810 (and / or other user interfaces described herein) include, for example, photos, videos, audio clips, locations (e.g., routes or specific locations that have been previously mapped or otherwise captured by the device 500A), text message conversations, phone calls (e.g., the date, time, and / or duration of the phone call, along with the names of the caller / callee), fitness activities, songs, playlists, books, articles, podcasts, health metrics, images of e-tickets, links to any of these types of content, and / or some or all of other types of content items generated by and / or accessible to the device 500A.

[0310] The log entry user interface 810 includes a moments icon 814a, a camera icon 814b, a photo gallery icon 814c, an audio clip icon 814d, and a location icon 814e, which together provide a navigation user interface as described below.

[0311] The moment icon 814a, when selected, causes the device 500A to display one or more "moments," each of which includes one or more related content items, such as a reference to a video or video. Figure 8EAs described. In some embodiments, a moment is a collection of one or more related content items, such as content items with the same date or associated with the same event. In some embodiments, device 500A generates, identifies and / or stores a moment (e.g., a collection of one or more related content items) on device 500 (e.g., in a logging application) based on an analysis of content items stored on device 500A and / or accessible by the device, such as by identifying content items associated with a specific date or event that the user may be interested in. For example, device 500A may determine that several photos in a user's camera roll, a text message conversation between the user and another person, and locations visited by the user are all associated with the date of the user's birthday, and such content items may be grouped into birthday-related "moments." Optionally, in addition to content items, moments also include metadata associated with the content items, such as a date associated with the content item, a title associated with the content item, event data associated with the content item, a location associated with the content item, or other types of metadata. Optionally, device 500A determines and / or generates (e.g., automatically) metadata based on information embedded in or associated with the content item (e.g., data captured and / or generated by an application associated with the content item). Optionally, device 500A generates, identifies, and / or stores moments without explicit input from the user regarding the content items to be included in the moments (e.g., device 500A automatically generates moments in the background). As described herein, device 500A may present such "moments" to the user to prompt the user to create a log entry associated with these moments.

[0312] The photo library icon 814c, when selected by the user, displays thumbnails of the user's photo library in the log entry user interface 810 (e.g., below the log entry field 812) and allows the user to select one or more photos for inclusion in the log entry, as shown in FIG. Figure 8I The camera icon 814b, when selected, causes the device 500A to display a camera user interface that allows the user to capture a new photo and add it to a log entry, as described in reference to FIG. Figures 8J to 8K The audio clip icon 814d, when selected, allows the user to record an audio clip and add it to a log entry, as described in reference Figures 8L to 8M The location icon 814 e , when selected, displays one or more location items (eg, a map of a previously logged trip or the locations of a previous activity) and allows the user to select one or more of these location items for inclusion in the log entry field 812 .

[0313] The log entry user interface 810 optionally includes a suggested moment 816a (optionally displayed below the log entry field 812) that includes a plurality of content items that have been determined (e.g., by the device 500A and / or by another device) to be related to one another, such as by being associated with a single event, location, and / or date that can be considered a "moment" in the user's life. The suggested moment 816a can serve as a prompt to the user suggesting an activity or event to record. Figure 8C In the example of , the suggested moment 816a includes a first photo 818a, a second photo 818b, a location item 818c (e.g., a location on a map or a route), an audio item 818d (e.g., an audio clip or song), and a media item 818e (e.g., a podcast or a book). Other types of content items that are optionally included in the suggested moments include videos, text messages, fitness activities, or other types of content items generated by various applications. In some embodiments, in response to detecting a selection of the suggested moment 816a (e.g., a tap on the suggested moment 816a), representations of the moment 816a and / or content items 818a-818e are added to the log entry field 812 and / or the content entry area 817 (e.g., above the log entry field 812), as shown in reference Figures 8F to 8G described.

[0314] Log entry user interface 810 also includes an affordance 820 that, when selected, causes the contents of the log entry fields to be saved as a log entry (e.g., to a logging application). Optionally, after saving the log entry in response to detecting selection of affordance 820, device 500A exits log entry user interface 810 and optionally displays the log timeline interface, as described with reference to FIG. Figure 8N described.

[0315] In some embodiments, the user can initiate text entry into the log entry field 812 by selecting the log entry field 812 (e.g., by tapping within the log entry field 812). In response to detecting the selection of the log entry field 812, the device 500A displays a soft keyboard 821 in the user interface 810 to allow the user to type text, such as Figure 8D Optionally, if the user types more text than can fit in the first area of ​​log entry field 812, device 500A expands the area of ​​log entry field 812 within log entry user interface 810 from the first area to the second area. After typing the desired text and / or adding content items from suggested moments 816a and / or using icons 814a-814e to log entry field 812, the user can save the log entry (e.g., save the content in the log entry field) by selecting affordance 820.

[0316] exist Figure 8E , the user selects moment icon 814a (e.g., by tapping moment icon 814a), and device 500A responds by displaying moment 816b and moment 816c. Moment 816b includes multiple content items 818f-818j, optionally associated with a first date (e.g., December 7, 2022). Moment 816c includes a single content item 818k, optionally associated with a second date (e.g., November 30, 2022). Content items 818f-818j and 818k may include, for example, photos, videos, maps, audio clips, media content, or other types of content items. Content items 818f-818j and 818k are optionally displayed as representations (e.g., thumbnails, excerpts, titles, or other representations) of content items 818f-818j and 818k in moments 816b and 816c (respectively) and / or in log entry field 812, rather than the content items themselves.

[0317] The user may optionally select a moment (e.g., moment 816a or 816b) to add the moment (e.g., optionally including metadata) and / or the content item of the moment to the log entry. For example, in response to detecting that the user has selected Figure 8E In response to detecting the selection of moment 816b, device 500A displays representations of content items 818f-818j of moment 816b in a separate area 817 (e.g., a content input area) of user interface 810 (e.g., above log entry field 812) to indicate to the user that the user has selected moment 816a for (potential) inclusion in the log entry. Optionally, user interface 810 displays content items 818f-818j with options (e.g., affordances, checkboxes, or another type of option) to individually remove one or more of the selected content items so that the selected content items are not added to the log entry. Optionally, in response to detecting the selection of moment 816b, the computer system stops displaying moment 816b in its original location (e.g., below log entry field 812 and / or below icons 814a-814e).

[0318] exist Figure 8FIn the example of , the user has indicated that content items 818 g, 818 i, and 818 j are not to be added to the log entry (e.g., excluded from the log entry) by checking a box displayed with content items 818 g, 818 i, and 818 j. After the user has (optionally) indicated the content items to be removed, the user may provide input to add the remaining content items to the log entry field 812, such as by tapping on the area 817 where content items 818 f-818 j are displayed, or by tapping in the log entry field 812. In response to detecting the user input, the device 500A stops displaying content items 818 f-818 j in the area 817 above the log entry field 812 and displays content items 818 f and 818 h (or representations of content items 818 f and 818 h) in the log entry field 812 (e.g., to be added to the log entry), as shown. Figure 8G The user may then (optionally) enter text in the log entry field 812, as shown. Figure 8G 818f and 818h and any typed text by selecting affordance 820. In some embodiments, the user can delete a content entry from log entry field 812 before saving the log entry, such as by selecting the content entry to be deleted and providing a delete input.

[0319] In some embodiments, the user can select a date for the log entry that is the same as or different from the date the log entry was created. Figure 8HAs shown, when the user begins creating a log entry, device 500A optionally displays a default date 822. Default date 822 is optionally today's date, a date associated with an added moment or content item (e.g., moment 816b and / or content items 818f and 818g), or another default date selected by device 500A or configured by the user (e.g., as a configuration setting associated with a log recording application). In response to detecting a selection of default date 822 (such as a tap on date 822), device 500A displays a date options menu 824, which optionally includes one or more of today's date 824a, moment date 824b (e.g., a date associated with the moment added to the log entry, such as the date the user took the hike corresponding to the moment), photo date 824c (e.g., a date associated with a photo added to the log entry, such as the date the photo was taken by device 500A), and a custom date 824d (e.g., a date selected by the user). In response to detecting the user's selection of one of the date options 824a-824d, the device updates the default date 822 to the selected date, which will then be saved as the date for the log entry. In some embodiments, menu 824 excludes (e.g., does not display) one or more of date options 824a-824d. For example, if the user has not yet added moments and / or photos to the log entry, menu 824 optionally excludes date options 824b and / or 824c, respectively. As another example, if the default date 822 is today's date, menu 824 optionally excludes date option 824a. In some embodiments, menu 824 always includes a custom date 824d to allow the user to select their own date for the log entry.

[0320] Figure 8I An example is shown that allows the user to select a photo from a photo library to add to a log entry. Figure 8H In FIG. 8 , the user selects the photo gallery icon 814 c in the user interface 810. In response to detecting the selection of the photo gallery icon 814 c, Figure 8I , device 500A displays representations (e.g., thumbnails) of photos 815a-815f from the user's photo library in an area of ​​user interface 810 (e.g., below log entry field 812). The user may optionally select one or more of photos 815a-815f for inclusion in log entry field 812 (e.g., by tapping or clicking one or more of photos 815a-815f), such as to add the selected photos to the log entry.

[0321] Figure 8J and Figure 8KAn example of using a camera user interface and / or application to capture a new photo and add the new photo to a log entry in a logging application is shown.

[0322] exist Figure 8H In FIG. 8 , the user selects the camera icon 814 b in the user interface 810. In response to detecting the selection of the camera icon 814 b, Figure 8J , device 500A displays a camera interface 828 in an area of ​​user interface 810 (e.g., below log entry field 812) having a preview pane 832 for displaying a live view from device 500A's camera and a virtual button 830 for capturing a new photo or video, optionally along with other selectable options such as a video option, a flash option, a zoom option, or other options. Camera interface 828 is optionally displayed within the user interface of the logging application. In response to detecting activation of virtual button 830, device 500A captures a new photo using device 500A's camera and optionally automatically (e.g., without additional user input) adds the new photo (e.g., new photo 834) to log entry field 812, as shown. Figure 8K In some embodiments, in response to detecting activation of virtual button 830 and after capturing a new photo, device 500A requests confirmation from the user before adding new photo 834 to log entry field 812. In some embodiments, when new photo 834 is added to log entry field 812 (automatically or in response to user confirmation to add new photo 834 to log entry field 812), device 500A ceases displaying camera interface 828 and optionally displays soft keyboard 821 to enable the user to add text to log entry field 812 (e.g., in addition to new photo 834).

[0323] Alternatively, if the video option is selected in camera interface 828, then in response to detecting activation of virtual button 830, device 500A begins capturing a new video using the camera of device 500A. In response to detecting subsequent activation of virtual button 830, device 500A stops recording the new video and optionally continues recording in a manner similar to that described above. Figure 8J The new video is added to the log entry field 812 in the manner shown in (this process is not shown).

[0324] Figure 8L and Figure 8M An example is shown of using an audio capture application (eg, a voice memo application or another audio capture application) to capture a new audio recording and add the new audio recording to a log entry.

[0325] exist Figure 8HIn FIG. 8 , the user selects the audio clip icon 814d in the user interface 810. In response to detecting the selection of the audio clip icon 814d, Figure 8L , device 500A displays a virtual button 838 for capturing a new audio recording to an audio capture interface 836 in an area of ​​user interface 810 (e.g., below log entry field 812), optionally along with other selectable options such as a recording volume option. Audio capture interface 836 is optionally displayed in the user interface of the logging application. In response to detecting virtual button 838 (e.g., Figure 8L ), device 500A begins capturing a new audio clip using the microphone of device 500A (e.g., Figure 8L 840 ). Optionally, device 500A displays an indication of the dynamic elapsed time and / or volume or spectral content of the audio recording while recording the audio recording. In response to detecting a second activation of virtual button 838, device 500A stops recording the audio recording and optionally automatically (e.g., without additional user input) adds a new audio recording (e.g., new audio recording 840 ) to log entry field 812 , as shown. Figure 8M As shown. In some embodiments, the new audio recording 840 can be played back and / or deleted after it is added to the log entry field 812. In some embodiments, in response to detecting the second activation of the virtual button 838 and after capturing the new audio recording, the device 500A requests confirmation from the user before adding the new audio recording 840 to the log entry field 812. In some embodiments, the new audio recording can be played back from the audio capture interface 836 (e.g., before being added to the log entry field 812). In some embodiments, when the new audio recording 840 is added to the log entry field 812 (automatically or in response to user confirmation that the new audio recording 840 is added to the log entry field 812), the device 500A stops displaying the audio capture interface 836 and optionally displays the soft keyboard 821 to enable the user to add text to the log entry field 812 (e.g., in addition to the new audio recording 840).

[0326] Figure 8N An example of a timeline user interface 842 for a logging application is depicted. Optionally, timeline user interface 842 is displayed in response to selecting logging application icon 655 from user interface 810 and / or in response to selecting affordance 820 in logging user interface 602. Timeline user interface 842 displays a timeline of log entry representations 844a-844c, such as that used in Figures 8A to 8LThe log entry representations shown in timeline 842 optionally provide previews of corresponding log entries by including representations of content items and / or text included in the corresponding log entries, as depicted in log entry representations 844a-844c. Figure 8N As shown, a log entry may include a combination of content items and text (e.g., log entry representation 844a), only content items (e.g., log entry representation 844b), or only text (e.g., log entry representation 844c). Optionally, a log entry representation corresponding to a log entry that includes a longer text entry includes a subset of the text of the log entry. For example, a log entry representation optionally includes the first 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10 lines of the text of the corresponding log entry. As previously discussed, content items in a log entry optionally include photos, videos, maps, fitness activities, podcasts (e.g., the podcast itself, a portion of a podcast, a link to a podcast, artwork associated with a podcast), text messages, books or articles (e.g., a book or article itself, a portion of a book or article, a link to a book or article, artwork associated with a book or article), or other types of content. In some embodiments, each log entry indication 844a-844c is displayed together with an associated date (e.g., a date associated with the log entry).

[0327] Optionally, the timeline user interface 842 displays log entry representations 844a-844c in chronological order, with the log entry representation corresponding to the most recently added log entry shown at the top of the timeline user interface 842. If the user has created more log entries than can be shown in a single screen, the user can scroll down to view additional log entry representations.

[0328] The timeline user interface 842 optionally includes a rewind affordance 848 that, when selected, causes the device 500A to display a rewind selection interface in the timeline user interface 842, as shown in FIG. Figure 8O described.

[0329] The timeline user interface 842 optionally includes an add enable indication 846, which, when selected, causes the device 500A to display the log entry user interface 810 for adding a new log entry.

[0330] Optionally, selection of a log entry representation 844a-844c in the timeline user interface 842 causes the device 500A to display the text and / or content items associated with the log entry in a full-screen format, wherein each content item and / or text content is displayed full screen and the user can navigate between screens displaying content items by providing left / right swipe inputs. Optionally, selecting a content item in the log entries 844a-844c displayed in the timeline user interface 842 causes the device 500A to display the selected content item in a full-screen interface. For example, selecting the "Song 1" content item in the log entry 844b causes the device 500A to display a full-screen music interface, such as reference 844b. Figure 8R described.

[0331] The timeline user interface 842 optionally includes a momentary affordance 850 that, when selected, causes the device 500A to display a momentary user interface, as shown in FIG. Figure 8S described.

[0332] Figure 8O An example of displaying a replay selection interface 852 in the timeline user interface 842 is shown. In some embodiments, in response to detecting a replay affordance 848 ( Figure 8N ), device 500A displays a review selection interface 852 in the timeline user interface 842, optionally at the top of the timeline user interface 842, such as Figure 8O. The review selection interface 852 includes one or more review panes having representations of one or more types of reviews (e.g., birthdays, on this day, important days, highlighted time periods). In some embodiments, the review includes a collage, slideshow, animated video, or other form of visual (and optionally, auditory) presentation generated by the device 500A based on one or more previously created log entries associated with a particular date or event (e.g., including content items and / or text in one or more log entries). For example, a birthday review optionally includes log entries with dates associated with the user's (or other people's) birthday. The "on this day" review optionally includes one or more log entries with the same month and day as the current date. The "important days" review optionally includes one or more log entries with dates determined by the device 500A or by the user to be important, such as the date the user gets married or starts a new job. The "highlight time period" review includes one or more log entries whose dates have been determined by the device 500A or the user to be associated with a particular time period or multi-day event (such as "autumn in Sweden") of potential interest. A "Media Focus" replay includes one or more log entries whose dates have been determined by the device 500A or the user to be associated with a particular time period or multi-day event, and which include (or reference) music and / or video played during that time period or event. Figure 6V and / or one or more of the characteristics of the animated video presentation 679 described by method 700 .

[0333] exist Figure 8O In the example shown in FIG, the review selection interface 852 includes a first review pane 852a associated with a "Birthday" review and a second review pane 856b associated with a "On This Day" review. In some embodiments, the review selection interface 852 can be scrolled horizontally to navigate to additional review panes, such as review panes associated with important day reviews and / or highlight time period reviews.

[0334] In some embodiments, the review panes 852a-852b are selectable to cause the device 500A to display a full screen of selectable review representations of the selected review type, wherein each review option is associated with a particular review. For example, in response to detecting selection of the review pane 856a, the device 500A optionally displays one or more birthday review representations 857a-857c, each associated with a "Birthday" review. The user can select a particular review option to display the associated birthday review (e.g., play an animated video or display a collage).

[0335] In some examples, in response to Figure 8OIn the review selection interface 843, the selection of the enable indication 854 is detected, and the device 500A displays the following Figure 8P The replay interface 858 shown. The replay interface 858 optionally displays replay representations 860a-860e associated with representative replays of different types, and optionally displays replay amounts associated with the different types of replays. Figure 8P In the example shown in FIG, there are four “Important Days” replays, two “On This Day” replays, three “Birthdays” replays, one “Highlight Time Period” replay, and three “Media Focus” replays. In some embodiments, the replay representations 860a-860e include content items (or representations of content items) and / or text associated with the representative replays.

[0336] In some embodiments, Figure 8P The replay representations 860a-860d are optionally horizontally scrollable to reveal additional replay representations of the same replay type. For example, horizontally scrolling replay option 860a optionally reveals one or more additional "birthday" replay representations that can be selected to display the corresponding replay.

[0337] In some embodiments, the review representations 860a-860d are selectable to cause the device 500A to display a corresponding representative review, such as if there is a single review associated with the selected type. In some embodiments, the review representations 860a-860d are selectable to cause the device 500A to display additional reviews (including the representative review) of the same review type, such as if there are multiple reviews associated with the selected type. For example, in response to detecting Figure 8P The selection of the review representation 860b in the Figure 8P ), device 500A optionally displays a review-type user interface 862 with review representations 860b and 860e associated with the "On This Day" review, as shown in FIG. Figure 8Q shown.

[0338] Return to Figure 8N and timeline user interface 842, as previously discussed, in some embodiments, representations of moments and / or content items (e.g., Figure 8N 818f and 818h) may be selected to cause device 500A to display the corresponding content item (or representation of a content item) in a full screen interface, optionally with the ability to navigate between different content items at that instant by swiping left / right. Figure 8MUpon selection of a content item representation 818h (which is optionally a representation of a song, such as the title of the song, cover art associated with the song, or another type of representation), device 500A optionally displays a content user interface 864, such as Figure 8R shown.

[0339] Content user interface 864 includes a second content item representation 866, which can be the same as or different from content item representation 843 displayed in timeline user interface 842. In some embodiments, content item representation 866 is larger than content item representation 843.

[0340] Content user interface 864 optionally includes an edit affordance 868 that, when selected, allows the user to edit a content item included in the log entry and represented by content item representation 866. Additionally or alternatively, selection of edit affordance 868 allows the user to edit the log entry including the content item, such as to add text to the log entry (optionally associated with the content item).

[0341] In some embodiments, if the content item represented by content item representation 866 is playable (e.g., it is a video, an audio recording, or another type of playable content), the content item can be played from content user interface 864 without launching an application associated with the content item. In some embodiments, if the content item represented by content item representation 866 is playable, content user interface 864 includes a playback enablement 870 that, when selected, causes the content item represented by content item representation 866 to be played while remaining within content user interface 864 (e.g., Figure 8R In the example of , by playing song 1). In some embodiments, if the content item is not playable, such as if the content item is a photo or a map, the content user interface 864 forgoes displaying the playback affordance 870.

[0342] In some embodiments, the content user interface 864 includes an application icon and / or button 872 that, when selected, causes the device 500A to launch an application associated with the content item represented by the content item representation 866. For example, if the content item is a song (e.g., Figure 8R), selection of application icon 872 optionally causes device 500A to launch a music playing application associated with the song. Other types of content items included in the log entry may be associated with other types of applications, such as a photo editing application, a voice memo application, a text messaging application, or a fitness application, which may similarly be launched by device 500A in response to detecting selection of application icon 872. For example, if the content item in the log entry is part of a text message conversation, content user interface 864 optionally reproduces the portion of the text message conversation included in the log entry in full screen. If the user selects application icon 872, device 500A launches the corresponding text messaging application and navigates (e.g., automatically, without input from the user) to the portion of the conversation included in the log entry.

[0343] Return to Figure 8N and timeline user interface 842. As previously discussed, in some embodiments, the momentary affordance 850 is selectable to cause the device 500A to display Figure 8S The instantaneous user interface shown.

[0344] The moment user interface 874 includes one or more moments 876a-876c, each moment optionally associated with a moment date 884a-884c and including text and / or representations of one or more content items (e.g., content item representations 878a-878e, 880a-880b, 882a-882d). As previously discussed, in some embodiments, the device 500A generates moments 876a-876c based on an analysis of content items stored and / or accessible on the device 500A, such as by identifying content items associated with a particular date or event that may be of interest to the user. In some embodiments, the moments 876a-876c displayed in the moment user interface 874 are moments that have not previously been logged by the user (e.g., not included in a log entry in a logging application) and are provided to prompt the user to select a moment to be logged (e.g., included in a log entry).

[0345] exist Figure 8S In the example of FIG, the moment user interface 874 includes icons or buttons 886a-886d that are selectable to cause the device 500A to select (e.g., filter) which moments and / or prompts are presented in the moment user interface 874. For example, in response to selection of icon 886a (e.g., Figure 8S), device 500A displays moments recommended by device 500A, such as based on an analysis of the user's prior activity or indications of interest. For example, in response to selection of icon 886b, device 500A displays moments associated with recent dates, such as dates within the last day, week, month, or year. For example, in response to selection of icon 886c, device 500A optionally displays one or more text prompts to encourage the user to create a log entry and provide a subject. An example of such a prompt is "What are you thankful for today?" For example, in response to selection of icon 886d, device 500A optionally displays representations of one or more media items (e.g., books, songs, articles, podcasts, or other types of media content) that the user may wish to include in the log entry. In response to detecting selection of the displayed moment, prompt, or representation of a media item in user interface 874, device 500A optionally displays a log entry user interface 810 in which the selected moment, prompt, or media item is displayed above log entry field 812 (e.g., as shown in FIG. Figure 8F ) or within the log entry field 812 (e.g., as Figure 8G ), thereby providing users with a simple way to log selected items.

[0346] In some embodiments, in response to detecting selection of a moment 876a-876c, device 500A displays a menu that allows the user to create a journal entry that includes the moment and / or content items of the moment, such as Figure 8T shown.

[0347] like Figure 8T As shown, in response to detecting selection of moment 876b, device 500A displays a menu 884 including a first selectable option 884a and a second selectable option 884b.

[0348] In response to detecting selection of option 884a, device 500a creates a new log entry including the content item represented by content item representations 880a-880b and saves the log entry (e.g., without requiring the user to provide additional input). Optionally, device 500A saves the log entry while continuing to display transient user interface 874 without displaying log entry user interface 810.

[0349] In some embodiments, in response to detecting selection of option 884b, device 500a displays log entry user interface 810, wherein the selected moment and / or content item representations 880a-880b are displayed in log entry field 812 (e.g., in a format similar to Figure 8G ) or above the log entry field 812 (e.g., in a manner similar to Figure 8F The user can then add text, add additional content items, or save the log entry, as shown in the reference Figures 8C to 8L described.

[0350] In some embodiments, the user can configure the logging application and / or device 500A to display or provide notifications (which may be referred to as "nudges") that remind or encourage the user to create or comment on a log entry. For example, the user can invoke a nudge, such as from a configuration settings menu associated with the logging application. Figure 8U A display of a nudge user interface 886 is shown to configure the logging application to deliver reminder notifications based on various criteria.

[0351] The nudge user interface 886 optionally includes one or more selectable options 888a-888d that can be selected by the user to cause the device 500A to display notifications associated with the options 888a-888d. Such notifications are optionally displayed in a manner similar to, for example, Figure 6V The visual representation shown and / or described with reference to method 700 is shown.

[0352] In some embodiments, selection of option 888a configures the device 500A to display a scheduled reminder notification according to a schedule (e.g., a schedule provided by the user or determined by the device 500A). For example, selection of option 888a may optionally configure the device 500A to display a reminder notification at a specified time daily, weekly, or monthly, or to display a reminder notification according to another schedule. In some embodiments, the device 500A determines at the specified reminder notification time whether one or more criteria indicating whether the user may wish to receive a reminder notification at the scheduled time are met. For example, the device 500A optionally determines whether the device 500A is operating in notification suppression mode, or whether a calendar application on the device 500A indicates that the user is in a meeting, or whether a phone application indicates that the user is on a call. Optionally, the device 500A temporarily or permanently suppresses the reminder notification based on determining that one or more criteria are met, and optionally provides a notification after one or more criteria are no longer met.

[0353] In some embodiments, such reminder notifications optionally include saved moment notifications, review notifications, and / or system moment notifications, as described in more detail below. Scheduled reminder notifications optionally include a prompt to create a log entry and / or a suggested topic for a log entry. In some embodiments, in response to detecting selection of a scheduled reminder notification, device 500A displays a log entry user interface 810, such as Figure 8C shown.

[0354] In some embodiments, selection of option 888b configures the device 500A to display saved moment notifications associated with moments that have been saved in a log entry by a user (e.g., using a "quick add" feature) but have not yet been written by the user. In some embodiments, the device 500A displays saved moment notifications associated according to a schedule. In some embodiments, the saved moment notifications include one or more representations of content items associated with one or more saved moments. In some embodiments, in response to detecting selection of a saved moment notification, the device 500a displays the log entry user interface 810, wherein representations of content items associated with the saved moment are displayed in the log entry field 812 (e.g., in a format similar to Figure 8G The user can then add text, add additional content items, or save the log entry, as shown in the reference Figures 8C to 8M described.

[0355] In some embodiments, selection of option 888c configures device 500A to display a review notification associated with one or more existing log entries. In some embodiments, device 500A displays the review notification according to a schedule and / or based on determining that the log entry is associated with the same month and day as the current month and day. In some embodiments, in response to detecting selection of the review notification, device 500A displays the corresponding review associated with the one or more log entries.

[0356] In some embodiments, selection of option 888d configures the device 500A to display system moment notifications associated with new moments generated, identified, and / or saved by the device 500 and that have not yet been added to a log entry by the user. In some embodiments, the device 500A displays system moment notifications according to a schedule and / or when the device 500A generates, identifies, and / or saves one or more new moments. In some embodiments, the system moment notifications include one or more representations of related content items (e.g., content items with the same date, location, or other indication of relevance). In some embodiments, in response to detecting a selection of the system moment notification, the device 500A displays a moment user interface (e.g., Figure 8T In some embodiments, in response to detecting selection of a system moment notification, device 500a displays a log entry user interface 810 in which a representation of a content item associated with the system moment is displayed in a log entry field 812 (e.g., in a format similar to Figure 8G ) or above the log entry field 812 (e.g., in a manner similar to Figure 8F The user can then add text, add additional content items, or save the log entry, as shown in the reference Figures 8C to 8M described.

[0357] In some embodiments, instead of and / or in addition to being displayed as a notification, device 500A displays a reminder (e.g., corresponding to the notification described above) to create and / or comment on a log entry in (or in the form of) a widget associated with the logging application. Figure 8V In some embodiments, device 500A displays a prompt in a widget 890 in a user interface 802 (e.g., a home screen user interface of device 500A) regarding logging a moment (e.g., a saved moment or system moment including content items represented by content item representations 892a and 892b). Widget 890 includes a prompt regarding logging the moment. In some embodiments, in response to detecting selection of widget 890, device 500a displays a log entry user interface 810 in which content item representations 892a-892b are displayed in a log entry field 812 (e.g., in a format similar to Figure 8G ) or above the log entry field 812 (e.g., in a manner similar to Figure 8F The user can then add text, add additional content items, or save the log entry, as shown in the reference Figures 8C to 8M described.

[0358] In some embodiments, if the device 500A identifies a saved instant notification, a review notification, and / or a system instant notification within a predetermined time period of a predetermined reminder notification, the device 500A waits to display the saved instant notification, the review notification, and / or the system instant notification until the predetermined reminder time. For example, if the device 500A is configured to provide a predetermined reminder notification, the device 500A optionally batches the notifications for display at the predetermined reminder time.

[0359] Figure 9 It is shown that according to Figures 8A to 8V Flowchart of method 900 for displaying a user interface for logging in some embodiments of the present invention. Method 900 is optionally performed on an electronic device (such as device 100, device 300, or device 500), as described above with reference to Figure 1A-1B 、 Figure 2-Figure 3 、 Figure 4A-4B as well as Figures 5A-5H Some operations in method 900 are optionally combined, and / or the order of some operations is optionally changed.

[0360] In some embodiments, method 900 is performed at an electronic device that communicates with a display generation component and one or more input devices. For example, a mobile device (e.g., a tablet, smartphone, media player, or wearable device) includes wireless communication circuitry that optionally communicates with one or more of: a mouse (e.g., external), a trackpad (optionally integrated or external), a touchpad (optionally integrated or external), a remote control device (e.g., external), another mobile device (e.g., separate from the electronic device), a handheld device (e.g., external), and / or a controller (e.g., external), etc. In some embodiments, the display generation component is a display (optionally a touch screen display) integrated with the electronic device, an external display such as a monitor, a projector, a television, or a hardware component (optionally integrated or external) for projecting a user interface or making a user interface visible to one or more users, etc. In some embodiments, the eye tracking device is a camera and / or motion sensor capable of determining the direction and / or location of the user's gaze. In some embodiments, method 900 is performed at or by an automobile (e.g., at an infotainment system of the automobile having or communicating with one or more display generating components and / or input devices).

[0361] In some embodiments, the electronic device displays (902a) a first user interface (eg, Figure 8C or Figure 8E 810), the first user interface including a logging function for entering content into a logging application (e.g., Figure 8M The log entry representation 844a) in the log entry field (e.g., Figure 8E 818f-818j) and a list of suggested content items (e.g., content items 818f-818j) for inclusion in the log entry (e.g., Figure 8E moment 816b), wherein the suggested content item in the list of suggested content items is included based at least in part on data detected by an application other than the logging application (such as a date of the content item, a location of the content item, a person associated with the content item, an event associated with the content item, or other types of data).

[0362] For example, content items 818f-818j are selected (e.g., by an electronic device) for inclusion in moment 816b because they are associated with the same date, where the date is detected by an application associated with the content items (e.g., a photo capture application, a map making application, or another type of application). In some embodiments, the list of suggested content items includes a graphical and / or textual representation of one or more content items, such as a photo or video thumbnail, a map thumbnail, a song or book title, a message excerpt (e.g., a text message or email message), an event title, a date, a person's name, a representation of an audio signal, or another type of representation of a content item. In some embodiments, the list of suggested content items is displayed within a visual boundary (e.g., within a rectangular, elliptical, circular, or other type of boundary) to indicate that the content item is part of the list of suggested content items. In some embodiments, the list of suggested content items includes and / or is displayed with a date associated with the list of suggested content items, such as with Figure 8E 7, 2022, is associated with and displayed as part of moment 816b in the electronic device. For example, the date is optionally a date on which one or more content items occurred, were captured, were shared (e.g., to or by a user of the electronic device), and / or were otherwise associated with.

[0363] In some embodiments, a list of suggested content items (such as Figure 8E When the first user interface of the suggestion moments 816b and 816c in the journal entry is displayed, the electronic device receives (902b) an input via one or more input devices pointing to a list of suggested content for inclusion in a journal entry of the journaling application, such as a touch contact input, a button input, a voice input, or a selection. Figure 8E For example, the user can optionally select a moment to include by touching anywhere on the moment (e.g., on a touch screen), by clicking on the moment, by verbally selecting the moment (such as by saying "select the moment associated with December 7, 2022"), by providing an empty gesture pointing to the moment (such as an empty pinch gesture), and / or by directing their attention to the moment (e.g., such as in an augmented reality or virtual reality application with gaze detection, where the electronic device can detect that the user is looking at the moment).

[0364] In some embodiments, in response to receiving input pointing to a list of suggested content items for inclusion in a log entry for a logging application, the electronic device displays (902c) representations of the suggested content items in the content entry area while displaying the log entry fields, such as shown as where a representation of the content item at the suggested moment 816b is displayed. Figure 8GThe electronic device displays the list of suggested content items in content entry area 817 above the log entry field 812 (e.g., when the log entry field 812 is simultaneously displayed). Optionally, in response to receiving input pointing to the list of suggested content items for inclusion in a log entry for the logging application, the electronic device ceases to display the list of suggested content items (e.g., ceases to display moment 816b below the log entry field).

[0365] In some embodiments, the electronic device simultaneously displays via the display generation component: a first user interface including a log entry field and a list of suggested content items for inclusion in the log entry of the logging application, such as Figure 8E and a navigation user interface comprising a plurality of selectable user interface elements (e.g., comprising Figure 8C 814b to 814e of the navigation user interface), each of which is selectable to initiate the electronic device to abandon display (e.g., stop displaying or not displaying) the list of suggested content items for inclusion in the log entry of the log recording application via the display generation component (e.g., stop displaying or not displaying the list of suggested content items for inclusion in the log entry of the log recording application). Figure 8E 816b and 816c in the suggestion moments 816b and 816c), and the process of displaying the corresponding type of content for inclusion in the log entry of the logging application via the display generation component without displaying content of a type different from the corresponding type. For example, when the display includes Figure 8E The suggested moments 816b and 816c Figure 8E When the user interface 810 is displayed, the electronic device receives a selection Figure 8E 814c, and in response, displays such as Figure 8I 816b and 816c. For example, in a display including Figure 8E The suggested moments 816b and 816c Figure 8E When the user interface 810 is displayed, the electronic device receives a selection Figure 8E In response to detecting the selection of the camera icon 814b, the electronic device stops displaying Figure 8E The suggested moments 816b and 816c, and as Figure 8J 814a-814e, the electronic device stops displaying the keyboard (e.g., Figure 8Fkeyboard 821) and / or replace the display of the keyboard with the display of the corresponding type of content.

[0366] In some embodiments, in response to receiving input pointing to a list of suggested content items for inclusion in a log entry for the logging application, the device displays a keyboard for typing content into the log entry field of the second user interface while displaying representations of the suggested content items in the content entry area, such as Figure 8F As shown, the suggestion moment 816b is displayed in the content entry area 817, and the keyboard 821 is simultaneously displayed.

[0367] In some embodiments, the first suggested content item includes a first content item and a second content item, such as Figure 8F In some embodiments, the first content item and the second content item are associated with (e.g., captured by and / or accessed via) an application other than the logging application, such as Figure 8F The content items 818f and 818g in FIG are photos (e.g., associated with a photo application other than the logging application), or the first content item is associated with an application other than the logging application and the second content item is associated with a second application other than the first application, such as Figure 8F The content item 818f in is a photo captured by the photo application, and Figure 8F In some embodiments, displaying representations of suggested content items in the content entry area of ​​the logging application includes displaying a representation of a first content item and a representation of a second content item in the content entry area (optionally, along with other content items from the same moment, such as content items 818h, 818i, and 818j), such as displayed in content entry area 817 of user interface 810. Figure 8F The content items 818f and 818g are represented as shown above with reference to Figure 8F In some embodiments, after displaying a representation of the first content item and a representation of the second content item in the content entry area, detecting a second input, such as selecting , via one or more input devices to remove the first content item from the content entry area (e.g., to exclude the first content item from being added to the log entry field) Figure 8F818g in the content entry area for removal, as indicated by a check mark in content item 818g. In some embodiments, in response to detecting the second input requesting removal of the first content item from the content entry area, the device stops displaying the representation of the first content item in the content entry area without stopping displaying (e.g., while maintaining display) the representation of the second content item in the content entry area. For example, the user may optionally remove some or all of the content items from the content entry area before adding the (remaining) content items in the content entry area to the log entry.

[0368] In some embodiments, after detecting the second input requesting to remove the first content item from the content entry area, the electronic device detects user input corresponding to a request to add the content item in the content entry area to the log entry field (e.g., such as in Figure 8F , optionally after removing some content items from content entry area 817), and in response to detecting user input corresponding to a request to add a content item to the log entry field, the electronic device displays representations of one or more content items of the first suggested content item in the log entry field, including the second content item and excluding the first content item. Figure 8G In the example of FIG, the electronic device detects user input corresponding to a request to add a content item of moment 816b to log entry field 812, while content items 818g, 818i, and 818 are marked as excluded (or optionally have been removed from content entry area 817). In response to detecting the user input corresponding to a request to add moment 816b to log entry field 812, the electronic device displays representations of content items 818f and 818h in log entry field 812, as shown. Figure 8H As shown, and optionally stops displaying content items 818f-818j in content entry area 817, and / or stops displaying content entry area 817. In some embodiments, after displaying a representation of the content item in log entry field 812, the electronic device detects a change to the affordance (e.g., Figure 8G The device may detect selection of an affordance 820 in the log entry field, and in response to detecting selection of the affordance, save the content displayed in the log entry field (e.g., text content and / or content item) as a log entry (e.g., to a logging application). Optionally, the device saves the log entry locally and / or remotely.

[0369] In some embodiments, the first content item is of a first type and the second content item is of a second type different from the first type, such as Figure 8E The content item 818f is (or represents) a photograph and Figure 8E The content item 818g is (or represents) an audio clip.

[0370] In some embodiments, before displaying a first user interface including a list of suggested content for inclusion in a log entry for a logging application, the electronic device displays, via a display generating component, an optional user interface element for displaying a list of suggested content for inclusion in a log entry for a logging application (such as by displaying a list of suggested content for inclusion in a log entry for a logging application). Figure 8B In some embodiments, before displaying the first user interface including a list of suggested content for inclusion in a log entry for the logging application, the electronic device receives a request via one or more input devices, such as by detecting a request. Figure 8B In some embodiments, in response to detecting input directed to an optional user interface element for displaying a list of suggested content for inclusion in a log entry for the logging application, the electronic device generates a display, such as by displaying a selection of the enable representation 808d, of the enable representation 808d (e.g., by detecting a tap on the enable representation 808d, a click on the enable representation 808d, or another type of input indicating selection of the enable representation 808d). Figure 8C The journal user interface 810 and suggestion moments 816a are used to display a first user interface including a list of suggested content for inclusion in a journal entry of the journaling application.

[0371] In some embodiments, the first user interface consumes the first display area based on determining that one or more first criteria are met, such as Figure 8C In some embodiments, the first user interface consumes a second display area that is larger than the first display area based on determining that one or more second criteria are met, such as by Figure 8E The display area consumed by the proposed moments 816b and 816c is greater than Figure 8C As another example, the device optionally expands the area consumed by the log entry field 812 (and therefore the area consumed by the first user interface) based on determining that the amount of text typed into the log entry field 812 is greater than a threshold amount of text (such as greater than 2, 3, 5, 8, 10, 20, or 30 lines of text).

[0372] In some embodiments, while displaying a second list of suggested content items including a second content item (optionally, while not displaying a log user interface), the device receives input (e.g., a touch or tap on the second list of suggested content items, or another type of input) via one or more input devices directed to the second list of suggested content items. In some embodiments, in response to receiving the second input directed to the second list of suggested content items for inclusion in a log entry of the logging application, and based on determining that one or more first criteria are met, the device saves (e.g., generates and / or stores) the second content item in the log entry of the logging application without initiating a process to add additional content to the log entry of the logging application. For example, the second list of suggested content is optionally Figure 8T moment 876b, and when one or more first criteria are met, the one or more first criteria optionally including when the electronic device detects the selection Figure 8T If the criteria are met when the first selectable option 884a is entered, the electronic device optionally saves the content item in moment 876b to the log entry (e.g., by creating a log entry that includes the content item in moment 876b) without initiating a process for adding additional content to the log entry (e.g., not displaying the log user interface 810, not displaying the keyboard, and / or not displaying a representation of the second content item in the content entry area 817 and / or in the log entry field 812 of the log user interface 810).

[0373] In some embodiments, in response to receiving a second input pointing to a second list of suggested content items for inclusion in a log entry of the logging application, and based on determining that one or more second criteria different from the one or more first criteria are satisfied, the device displays a representation of the second content item in the content entry area of ​​the log user interface (and optionally launches the log user interface if it is not already displayed). For example, the first suggested content is optionally Figure 8T At the moment 876b, and when one or more second criteria are met (the one or more second criteria optionally include when the electronic device detects the selection Figure 8T 84a), the electronic device optionally displays the logbook user interface 810 (if not already displayed) and displays a representation of the content item of the moment 876b into the content input area 817 and / or the logbook entry field 812 (such as by displaying Figure 8G 810, but with content item representations 880a-880b displayed in log entry fields 812), thereby initiating a process of adding further content (e.g., text or additional content items) to the log entry.

[0374] Figure 10 It is shown that according to Figures 8N to 8R Flowchart of method 1000 for displaying a user interface including playback in some embodiments. Method 1000 is optionally performed on an electronic device (such as device 100, device 300, or device 500), as described above with reference to Figure 1A to Figure 1B 、 Figures 2 to 3 、 Figures 4A to 4B and Figures 5A to 5H Some operations in method 1000 may be optionally combined, and / or the order of some operations may be optionally changed.

[0375] In some embodiments, method 1000 is performed at an electronic device that communicates with a display generation component and one or more input devices. For example, a mobile device (e.g., a tablet, smartphone, media player, or wearable device) includes wireless communication circuitry that optionally communicates with one or more of: a mouse (e.g., external), a trackpad (optionally integrated or external), a touchpad (optionally integrated or external), a remote control device (e.g., external), another mobile device (e.g., separate from the electronic device), a handheld device (e.g., external), and / or a controller (e.g., external), etc. In some embodiments, the display generation component is a display (optionally a touch screen display) integrated with the electronic device, an external display such as a monitor, a projector, a television, or a hardware component (optionally integrated or external) for projecting a user interface or making a user interface visible to one or more users, etc. In some embodiments, the eye tracking device is a camera and / or motion sensor capable of determining the direction and / or location of the user's gaze. In some embodiments, method 1000 is performed at or by an automobile (e.g., at an infotainment system of the automobile having or communicating with one or more display generating components and / or input devices).

[0376] In some embodiments, the electronic device displays (1002a) via a display generating component a first user interface of a logging application that includes a list of log entries associated with the user (e.g., log entries generated and / or saved by the user in the logging application (such as when logging into the logging application)), such as Figure 8N The timeline user interface 842 of the log entry representations 844a-844c of the timeline and a first selectable user interface element for displaying one or more replays, such as Figure 8NIn some embodiments, while displaying a first user interface of a logging application including a list of log entries associated with a user and a first selectable user interface element for displaying one or more replays, the electronic device receives (1002b) input (e.g., a touch, tap, click, or other input) directed to the first selectable user interface element via one or more input devices, such as in Figure 8N In some embodiments, in response to receiving input directed to the first selectable user interface element, the electronic device displays (1002c) via the display generation component a set of one or more replays, such as Figure 8O or a first review pane 856a associated with a set of "Birthday" reviews 857a-857c or a second review pane 856b associated with an "On This Day" review 857d.

[0377] In some embodiments, the set of one or more review views is associated with one or more log entries that meet criteria that are met when the date associated with the one or more log entries is within a date range (e.g., a range between two dates, or a range of a single date, which may include a month, day, and / or year). Figure 8P For the selection of the replay representation 860b, the electronic device optionally displays Figure 8Q A replay-type user interface 862 having a replay representation associated with the current month and day ("On This Day").

[0378] In some embodiments, the set of one or more review views is associated with one or more log entries that meet criteria that are met when the date associated with the one or more log entries is an annual date, such as having a Figure 8P The review type user interface 862 includes review representations 860b and 860e associated with the "On This Day" review and / or a review type user interface including a review representation associated with the "Birthday" review.

[0379] In some embodiments, the set of one or more replays is associated with one or more log entries that meet the criteria that are met when the content type of the log entry is media content. For example, a replay representation (such as Figure 8P The replay representation 860e) is optionally associated with a log entry that is associated with (e.g., includes or references) music and / or videos played by the user during a specific time period (e.g., during the recent summer). In this example, in response to detecting selection of the replay representation 860e, the electronic device optionally displays Figure 8Q, but with representations of the music and / or video content played by the user during the time period (e.g., the most recent summer) and a title associated with that time period, such as "Summer Music" (rather than "On This Day").

[0380] In some embodiments, displaying, via the display generation component, the set of logbook entries that meet one or more first criteria includes displaying, via the display generation component, in a first portion a first set of one or more lookbacks that meet criteria that are met when a date associated with one or more logbook entries corresponding to the first set of one or more lookbacks is a first date or within a first date range (such as Figure 8P 860a); displaying in a second portion a second set of one or more replays that meet criteria (such as a time of day associated with one or more log entries corresponding to the second set of one or more replays) that is satisfied when the time of day is a first time of day or within a time range within the first day. Figure 8P and / or displaying a third set of one or more replays in a third portion, the third set of one or more replays satisfying the criteria (such as Figure 8P , but includes representations of log entries associated with music and / or videos played by the user during a particular time period).

[0381] In some embodiments, aspects / operations of methods 700, 900, and / or 1000 may be interchanged, replaced, and / or added between these methods. For example, the logging application of methods 700, 900, and / or 1000 may optionally be interchanged, replaced, and / or added between these methods. For the sake of brevity, these details will not be repeated here.

[0382] As described above, one aspect of the present technology is the collection and use of data available from specific and legitimate sources to improve a user's ability to create log entries. The present disclosure contemplates that, in some instances, the collected data may include personal information data that uniquely identifies or can be used to identify a specific person. Such personal information data may include demographic data, location-based data, online identifiers, phone numbers, email addresses, home addresses, data or records related to a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other personal information.

[0383] This disclosure recognizes that the use of such personal information data within the present technology can be used to benefit users. For example, personal information data can be used to detect activity events. Thus, using such personal information data enables users to be notified of activity events and to create log entries. Furthermore, this disclosure contemplates other uses of personal information data that benefit users. For example, health and fitness data can be used based on user preferences to provide insights into their overall health or as positive feedback to individuals using technology to pursue health goals.

[0384] This disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information will adhere to established privacy policies and / or practices. Specifically, such entities are expected to implement and consistently apply privacy practices generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. Such information regarding the use of personal data should be prominently displayed and easily accessible to users and updated as the collection and / or use of data changes. Users' personal information should be collected only for lawful uses. Furthermore, such collection / sharing should occur only after receiving user consent or other lawful basis as provided by applicable law. Furthermore, such entities should consider taking any necessary steps to protect and secure access to such personal information and ensure that other entities with access to such personal information comply with the other entities' privacy policies and procedures. Furthermore, such entities may subject themselves to third-party assessments to demonstrate compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific types of personal information being collected and / or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations that may impose higher standards. 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.

[0385] Notwithstanding 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 providing hardware elements and / or software elements to prevent or block access to such personal information data. For example, such as with respect to an advertising delivery service, the technology of the present invention 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 the service. As another example, a user may choose not to provide personal data and / or device or object location data. As another example, a user may choose to limit the length of time that personal data and / or device or object location data is retained or to completely prohibit the development of a baseline location profile. In addition to providing "opt-in" and "opt-out" options, the present disclosure also contemplates providing notifications related to access or use of personal information. For example, a user may be notified when downloading an application that their personal information data and / or location data will be accessed, and then reminded again before the personal information data is accessed by the application.

[0386] Furthermore, it is the intention of the present disclosure that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting the collection of data 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 where appropriate by removing identifiers, controlling the amount or specificity of stored data (e.g., collecting location data at a city level rather than an address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods such as differential privacy.

[0387] Thus, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, this disclosure also contemplates that various embodiments may be implemented without requiring access to such personal information data. That is, various embodiments of the present technology will not be unable to function properly due to the lack of all or part of such personal information data. For example, location data and notifications may be delivered to users based on aggregated non-personal information data or an absolute minimum amount of personal information.

[0388] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0389] For purposes of explanation, the foregoing description has been described with reference to specific embodiments. However, the above illustrative discussion is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teachings. The embodiments have been chosen and described in order to best illustrate the principles of the invention and its practical application so as to enable others skilled in the art to best utilize the invention and the various described embodiments with various modifications suitable for the specific purposes contemplated.

Claims

1. A method comprising: At an electronic device in communication with a display generating component and one or more input devices: detecting an activity event associated with a user of the electronic device, wherein the activity event corresponds to one or more operations performed by the electronic device; and In response to detecting the activity event associated with the user: displaying, via the display generating component, a prompt associated with a logging application on the electronic device based on a determination that the activity event satisfies one or more criteria, wherein input directed to the prompt associated with the logging application initiates providing input in the logging application for a logging entry associated with the activity event, and Based on determining that the activity event does not satisfy the one or more criteria, Displaying the prompt associated with the logging application via the display generating component is foregone.

2. The method of claim 1 , wherein the activity event does not meet the one or more criteria, the method further comprising: After detecting the activity event, receiving, via the one or more input devices, a first user input corresponding to a request to manually create a corresponding log entry in the logging application; and In response to receiving the first user input, a process of manually creating the corresponding logging entry in the logging application is initiated.

3. A method according to claim 2, wherein the first user input is directed to a content item displayed in a first application different from the logging application, and the process of manually creating the corresponding logging entry in the logging application utilizes the content item as part of the logging entry. The method of claim 2 , wherein the first user input is directed to a user interface displayed in the logging application.

5. The method according to claim 4, further comprising: prior to displaying the user interface in the logging application, receiving, via the one or more input devices, a second user input corresponding to a request to display the logging application; as well as In response to receiving the second user input, user authentication is required before displaying the logging application. The method of claim 5 , wherein the user authentication comprises one or more of: facial recognition, fingerprint recognition, or password recognition.

7. The method according to claim 1, further comprising: After creating the journal entry in the journal application, a user interface of the journal application including a plurality of journal entries including the journal entry is displayed via the display generation component, wherein the journal entries are displayed within the user interface of the journal application as pages of a book.

8. The method according to claim 1, further comprising: After creating the log entry in the log application, a user interface of the log application is displayed via the display generation component, the user interface including multiple log entries, the multiple log entries including the log entry, wherein the multiple log entries are displayed in chronological order within the user interface of the log application.

9. The method of claim 1, wherein the logging application including the logging entries is accessible via a second electronic device associated with the electronic device.

10. The method of claim 1 , wherein the activity event does not meet the one or more criteria, the method further comprising: after detecting the activity event associated with the user and forgoing displaying the prompt associated with the logging application via the display generating component, receiving, via the one or more input devices, a first user input corresponding to a request for a corresponding prompt associated with the logging application, the first user input being directed to the logging application, wherein the corresponding prompt is associated with the activity event; as well as In response to receiving the first user input, the respective prompt is displayed via the display generating component, wherein input directed to the respective prompt initiates a process of providing input in the logging application for a respective logging entry associated with the activity event. The method of claim 1 , wherein the prompt includes one or more details related to the activity event.

12. The method according to claim 1, further comprising: while displaying the prompt associated with the logging application, receiving, via the one or more input devices, a first user input directed to the prompt; as well as In response to receiving the first user input: incorporating the voice input into the log entry based on determining that the first user input includes voice input; as well as Based on determining that the first user input includes an emoticon input, the emoticon input is incorporated into the log record entry.

13. The method according to claim 1, further comprising: receiving, via the one or more input devices, a first user input corresponding to a request to create a respective log entry associated with the content item; as well as In response to receiving the first user input, creating the respective log entry includes linking the respective log entry to the content item.

14. The method according to claim 13, further comprising: After receiving the first user input and creating the corresponding log entry, receiving, via the one or more input devices, a second user input corresponding to a request to access the content item; as well as In response to receiving the second user input to access the content item, the content item is accessed and a representation of the corresponding log entry is displayed via the display generation component.

15. The method according to claim 1, further comprising: receiving, via the one or more input devices, a first user input directed to the prompt associated with the logging application while displaying the prompt associated with the logging application; as well as In response to receiving the first user input, a user interface is displayed via the display generation component, the user interface including one or more details related to the activity event.

16. The method of claim 15, wherein the one or more details include one or more indications of one or more people associated with one or more photographs taken by the electronic device during the activity event.

17. The method according to claim 1, further comprising: receiving, via the one or more input devices, a first user input directed to the prompt associated with the logging application while the prompt associated with the logging application is displayed; in response to receiving the first user input, displaying, via the display generating component, a first question related to the activity event; as well as While displaying the first question related to the activity event, receiving a second user input via the one or more input devices, the second user input corresponding to a first response indicating a response to the first question, wherein at least a portion of the first response is included in the log record entry.

18. The method according to claim 17, further comprising: After receiving the second user input, a second question related to the activity event is displayed via the display generation component, wherein the second question is based on the first response.

19. The method according to claim 17, further comprising: After receiving the second user input, a second question related to the active event is displayed via the display generation component, wherein the second question is based on information associated with the active event.

20. The method according to claim 17, further comprising: After receiving the second user input, a second question related to the activity event is displayed via the display generation component, wherein the second question is based on one or more previous logging entries in the logging application.

21. The method of claim 1, wherein the one or more criteria include criteria that are satisfied based on a relationship between a current time of day at the electronic device and information associated with the user of the electronic device.

22. The method of claim 1, wherein the one or more criteria include criteria satisfied based on one or more of the following: a frequency with which the user of the electronic device contacts a contact associated with the activity event; movement of the electronic device from a first location to a second location associated with the activity event; a photo associated with the activity event taken by the electronic device; an operation performed by a second electronic device associated with the user of the electronic device, wherein the operation is associated with the activity event; content associated with the activity event and accessed by the electronic device; or One or more applications associated with the activity event accessed by the electronic device detect a relationship to the person / phone call you dialed.

23. The method of claim 1, further comprising: after detecting the activity event and after creating the logging entry associated with the activity event in the logging application, displaying, via the display generating component, selectable options associated with the activity event; receiving, via the one or more input devices, a first input corresponding to a selection of the selectable option while displaying the selectable option associated with the active event; as well as In response to receiving the first input, an animated video presentation associated with a log entry is displayed via the display generation component, wherein the animated video presentation associated with the log entry includes one or more entries in the log entry and one or more content items associated with the activity event.

24. The method of claim 23, wherein displaying selectable options comprises: displaying the selectable options based on determining that the current time of day at the electronic device satisfies one or more display criteria; as well as Based on determining that the current time of day at the electronic device does not satisfy the one or more display criteria, displaying the selectable option is foregone.

25. The method of claim 23, wherein the selectable options are displayed on: On a user interface of the electronic device outside of the logging application; or The logging application's user interface.

26. The method of claim 23, wherein the animated video presentation associated with the log entry comprises first-party content, third-party content, or both.

27. The method of claim 23, wherein the displaying of the animated video presentation associated with the journal entry includes presenting music.

28. The method of claim 1, wherein the prompt is displayed in a widget via the display generation component, the widget being displayed in a system user interface of the electronic device.

29. The method of claim 1, wherein the prompt is displayed in a first application other than the logging application.

30. The method of claim 29, further comprising: receiving, via the one or more input devices, a first user input directed to the prompt; as well as In response to receiving the first user input, information related to the activity event is displayed via the display generation component without ceasing display of the first application.

31. The method of claim 1, wherein the logging entries are accessible via the logging application.

32. The method of claim 1, wherein the prompt is displayed as a notification on the electronic device.

33. The method of claim 1, further comprising: In response to detecting the activity event associated with the user, and based on determining that the activity event satisfies the one or more criteria, initiating a process of displaying a second prompt associated with the logging application on a second electronic device associated with the electronic device, wherein input directed to the second prompt initiates a process of providing input in the logging application for the logging entry associated with the activity event.

34. The method of claim 33, wherein: The prompt displayed by the electronic device is configured to accept a first type and a second type of input, and The second prompt displayed by the second electronic device is configured to accept the first type of input but not the second type of input.

35. An electronic device, comprising: one or more processors; Memory; and One or more programs, wherein the one or more programs are stored in the memory and include instructions configured to be executed by the one or more processors, the instructions being used to perform the method according to any one of claims 1 to 34.

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

Images