User interface for creating log entries

Abstract

An electronic device detects an activity event associated with a user of the electronic device, and displays a prompt that facilitates creation of a log entry based on the activity event, displays suggested content for inclusion in a log entry of a log application, different user interfaces are displayed that include options for a user to selectively include content items of the suggested content in log entries of the logging application, and / or one or more reviews are displayed.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefits of U.S. Provisional Application No. 63 / 483,263, filed February 3, 2023; U.S. Provisional Application No. 63 / 503,759, filed May 23, 2023; and U.S. Provisional Application No. 63 / 593,206, filed October 25, 2023, the contents of which are incorporated herein by reference in their entirety for all purposes. Technical Field

[0003] The present invention relates in general to a user interface associated with the creation of log entries. Background Technology

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

[0005] In some cases, users may want to log information via electronic devices. Summary of the Invention

[0006] Some embodiments described in this disclosure involve one or more electronic devices that detect activity events associated with a user of an electronic device and provide the user with prompts for creating log entries based on such activity events. Some embodiments described in this disclosure involve one or more electronic devices that display suggested content for inclusion in log entries of a logging application. Some embodiments described in this disclosure involve one or more electronic devices that display one or more playback options. A full description of the embodiments is provided in the accompanying drawings and detailed description; it should be understood that the above-described summary of the invention does not limit the scope of this disclosure in any way.

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

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

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

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

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

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

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

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

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

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

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

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

[0019] Figures 6A to 6QQ An exemplary method is illustrated for detecting activity events according to some implementation schemes and displaying a prompt to create a log entry.

[0020] Figure 7 This is a flowchart illustrating a method 700 that, based on some implementation schemes, displays a prompt to initiate the process of creating a log entry.

[0021] Figures 8A to 8V The following are exemplary ways of displaying a user interface for logging according to some implementation schemes.

[0022] Figure 9 This is a flowchart illustrating a method 900 for displaying a user interface for logging, according to some implementation schemes.

[0023] Figure 10 This is a flowchart illustrating a method 1000 for displaying a user interface including a playback, according to some implementation schemes.

[0024] Figures 11A to 11G This section broadly illustrates how, according to some implementation schemes, the content of a suggested list of items can be selectively included in log entries of a logging application.

[0025] Figure 12 This is a flowchart illustrating a method 1200 for displaying a user interface for logging, according to some implementation schemes. Detailed Implementation

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

[0027] Users typically use multiple applications to capture or track various activities, interests, and events. For example, a user might use a camera app to capture photos of a birthday party or a fitness app to track their route or performance during a marathon. Such applications generate and store various content items (such as photos, videos, event logs, and / or maps) associated with the event or activity. Users may want to save records of important events and activities and / or remember them, such as by saving a log. Electronic devices may want to provide a logging user interface that allows users to easily add content items from different applications to log entries and / or prompts users to create log entries based on previously generated content items. Such user interfaces can reduce the cognitive burden on users of such devices and / or those who wish to create log entries and can provide enhanced privacy or security. Furthermore, such technologies can reduce processor and battery power that would otherwise be wasted on redundant user input.

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

[0029] The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and covers any and all possible combinations of one or more of the associated listed items. It will also be understood that the terms “comprising” and / or “including” as used in this specification specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

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

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

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

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

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

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

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

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

[0038] It should be understood that device 100 is merely an example of a portable multifunctional device, and device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of these components. 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.

[0039] Memory 102 optionally includes high-speed random access memory, and also 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0058] 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 program (or instruction set) 136. Furthermore, in some embodiments, memory 102 ( Figure 1A ) or 370 ( Figure 3 Storage device / global internal state 157, such as Figure 1A and Figure 3 As shown in the figure. Device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, indicating what applications, views or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from various sensors and input control devices 116 of the device; and position information relating to the device's position and / or orientation.

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

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

[0061] The contact / motion module 130 optionally detects contact with the touchscreen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., touchpads or physical click-based rotary dials). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining the contact intensity (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is movement of the contact and tracking movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disengagement). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., "multi-touch" / multiple-finger contact). In some implementations, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

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

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

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

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

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

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

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

[0069] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets thereof:

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

[0071] • Telephone module 138;

[0072] • Video conferencing module 139;

[0073] • Email client module 140;

[0074] • Instant Messaging (IM) module 141;

[0075] Fitness support module 142;

[0076] • Camera module 143 for still images and / or video images;

[0077] • Image management module 144;

[0078] • Video player module;

[0079] Music player module;

[0080] • Browser module 147;

[0081] • Calendar module 148;

[0082] • 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, as well as user-created widgets 149-6;

[0083] • Widget creator module 150 for creating user-created widgets 149-6;

[0084] • Search module 151;

[0085] • Video and music player module 152, which combines a video player module and a music player module;

[0086] • Notepad module 153;

[0087] • Map module 154; and / or

[0088] • Online video module 155.

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

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

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

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

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

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

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

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

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

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

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

[0100] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is optionally a microapplication 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 a user-created microapplication (e.g., user-created widget 149-6). In some embodiments, the widget includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the widget includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! widgets).

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

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

[0103] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions allowing users to download and play back recorded music and other sound files stored in one or more file formats such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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 separate module or part of another module (such as contact / motion module 130) stored in memory 102.

[0122] In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some 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 handlers 190 optionally utilize or invoke the data updater 176, the object updater 177, or the GUI updater 178 to update the application's internal state 192. Alternatively, one or more application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0143] • Time 404;

[0144] Bluetooth indicator 405;

[0145] • Battery status indicator 406;

[0146] • Tray 408 with icons for commonly used applications, such as:

[0147] ○ The telephone module 138 has an icon 416 labeled "telephone", which optionally includes an indicator 414 indicating the number of missed calls or voicemail messages;

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

[0149] ○ The icon 420 labeled "Browser" in browser module 147; and

[0150] ○ The video and music player module 152 (also known as the iPod (Apple Inc. trademark) module 152) is marked with an icon 422 labeled "iPod"; and

[0151] • Icons of other applications, such as:

[0152] ○The icon 424 of the IM module 141 marked as "Message";

[0153] ○The calendar module 148 has an icon 426 labeled "Calendar";

[0154] ○ The icon 428 of the image management module 144 is labeled "Photo".

[0155] ○ The icon 430 of camera module 143, which is labeled "camera";

[0156] ○ The icon 432 of the online video module 155, which is labeled "Online Video";

[0157] ○ The icon 434 labeled "Stock Market" in the Stock Market widget 149-2;

[0158] ○The icon 436 of the map module 154 that is labeled "map";

[0159] ○The weather widget 149-1 has icon 438 labeled "weather";

[0160] ○ The alarm clock widget 149-4 has an icon 440 labeled "clock";

[0161] ○ The icon 442 of the fitness support module 142 is labeled "fitness support";

[0162] ○ The icon 444 labeled "Notepad" in Notepad module 153; and

[0163] ○ The icon 446, labeled "Settings," is used to set the settings of 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, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels may be optionally used for various application icons. In some embodiments, the label of a particular application icon includes the name of the application corresponding to that particular application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to that particular application icon.

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

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

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

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

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

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

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

[0172] In some examples, the input mechanism 508 is optionally a microphone. The personal electronic device 500 optionally includes various sensors, such as a GPS sensor 532, an accelerometer 534, an orientation sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or combinations thereof, all of which are operatively connected to the I / O section 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, which, when executed by one or more computer processors 516, may cause the computer processors to perform, for example, the techniques described below, including methods 700, 900, 1000, and / or 1200. Figure 7 , Figure 9 , Figure 10 and Figure 12A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media can include, but is not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical discs based on CD, DVD, or Blu-ray technology, and persistent solid-state storage such as flash memory, solid-state drives, etc. Personal electronic devices are not limited to... Figure 5B It can be the components and configurations, or it can include other components or additional components in a variety of configurations.

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

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

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

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

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

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

[0180] Optionally, the contact intensity on a touch-sensitive surface is 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 performs an operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an operation different from the operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, when a contact with a characteristic intensity lower than the light press intensity threshold (e.g., and higher than the nominal contact detection intensity threshold, where contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector based on the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different groups of user interface figures.

[0181] An increase in contact intensity from below a light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact intensity from below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact intensity from below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. A decrease in contact intensity from above a contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a contact being lifted off the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

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

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

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

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

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

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

[0188] Table 1 below provides representative examples of haptic output / haptic feedback behaviors and configurations, as well as examples of their use relative to user interfaces used to manage the content-based haptic outputs illustrated and described herein.

[0189] Types of tactile output sequences waveform Texture (continuous) or discrete "main" 180Hz MiniTap Discrete "secondary" 80Hz MicroTap Texture "Mainly reduced" 200Hz MiniTap Discrete "Secondary reduction" 200Hz MicroTap Discrete

[0190] Table 1

[0191] As used herein, "installed application" refers to a software application that has been downloaded to an electronic device (e.g., device 100, 300, and / or 500) and is ready to be launched on the device (e.g., become open). In some implementations, the downloaded application becomes an installed application by utilizing 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 terms "open application" or "running application" refer to a software application that maintains state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application is optionally any of the following types of applications:

[0193] • Active application, which is currently displayed on the screen of the device that is using the application;

[0194] • Background applications (or background processes) that are not currently displayed but whose one or more processes are being handled by one or more processors; and

[0195] • A paused or hibernating application that is not running but has state information stored in memory (both volatile and non-volatile) that can be used to resume the execution of the application.

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

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

[0198] User interface and related processes

[0199] Prompt the user to create log entries

[0200] Users interact with electronic devices in a variety of different ways. The implementation scheme described below provides a way for electronic devices to display prompts to users, which can optionally initiate a process of creating log entries, thereby enhancing user interaction with the electronic device. Enhanced interaction with the device reduces the amount of time required for users to perform operations, thereby reducing the device's power consumption and extending the battery life of battery-powered devices. It should be understood that people use devices. When a person uses a device, that person is optionally referred to as the user of the device.

[0201] Figures 6A to 6QQ Exemplary methods for creating logging entries in a logging application according to some embodiments of this disclosure are shown. The embodiments in these figures are used to illustrate the processes described below, including references to... Figure 7 The process described.

[0202] Figure 6A An exemplary device 500A is shown, including a touchscreen 504A (e.g., touchscreen 504, display 112). Figure 6AIn this context, device 500A is displaying user interface 602, which includes application icons 605, 610, 615, 620, 625, 630, 635, 6411, 645, 650, 655, and 660. In some embodiments, user interface 602 is the main screen user interface of device 500A (e.g., as shown in reference ). Figure 4A The application includes, as described above, different application icons that can be selected to display different applications. Application icon 605 corresponds to a messaging application for initiating and maintaining messaging sessions. Application icon 610 corresponds to a calendar application for typing and managing a calendar. Application icon 615 corresponds to a calling application for initiating a phone call. Application icon 620 corresponds to a fitness application for maintaining fitness information. Application icon 625 corresponds to a stock 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 time in 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 log application for creating and accessing log entries. Application icon 660 corresponds to a camera application for taking photos.

[0203] exist Figure 6A In the process, device 500A detects the selection of application icon 655 (e.g., via contact 603). In response, Figure 6B In the device 500A, the authentication user interface 604 is displayed, and access to the logging application is only allowed when a successfully authenticated authentication input (e.g., biometrics, PIN, password, or other authentication) is received; if the authentication input is not successfully authenticated, the logging application is not displayed.

[0204] exist Figure 6B In this process, device 500A detects successfully authenticated input (e.g., via contact 603) to the authentication user interface 604. In response, Figure 6CIn the device 500A, a user interface 606 of the logging application is displayed. This user interface includes representations of log entries 608-612 already created in the logging application and optional option 614. The representation of log entry 608 corresponds to the log entry on December 14th. The representation of log entry 613 corresponds to the log entry on December 15th. The representation of log entry 612 corresponds to the log entry on December 16th. Optional option 614 allows selection to initiate a process of adding a new log entry to the logging application. Optional option 617 allows selection to initiate a process of viewing one or more animated video presentations related to the activity event and / or log entry, which will be discussed in more detail below.

[0205] exist Figure 6C In this process, device 500A detects the selection of optional option 614 (e.g., via contact 603). In response, Figure 6D In this process, device 500A updates user interface 606 to display optional options 616 and 618. Optional option 616 allows selection to initiate the process of manually creating a log entry. Optional option 618 allows selection to request prompts from device 500A to facilitate the creation of a log entry.

[0206] exist Figure 6D In this process, device 500A detects the selection of optional option 616 (e.g., via contact 603) and one or more inputs that type content into a log entry. In response, Figure 6E In this process, 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).

[0207] In some implementations, the device 500A does not require manual creation of log entries. Instead, it facilitates the creation of log entries by automatically displaying one or more prompts (e.g., without requiring user input to do so). These prompts facilitate the creation of log entries based on activity detected by the device 500A, as will be referenced. Figures 6F to 6R As described. For example. Figure 6F This describes an additional exemplary method for creating a log entry at device 500A. Figure 6F In the process, device 500A detects the selection of application icon 615 (e.g., via contact 603). In response, Figure 6G In the meantime, when device 500A detects one or more additional inputs, device 500 initiates a call to the user's "mother" via the call application.

[0208] exist Figure 6GIn this process, device 500A detects the selection of optional option 695 (e.g., via contact 603). In response, Figure 6H In the middle, device 500A ends the call with "Mom" and returns to the display user interface 602. Therefore, device 500A has detected that the user of device 500A has made a call with "Mom".

[0209] exist Figure 6H In the process, device 500A detects the selection of application icon 630 (e.g., via contact 603). In response, Figure 6I In the device 500A, a user interface 622 of a map application is displayed. This user interface includes a first portion 624 and a second portion 626. The first portion includes a representation of the map, and the second portion includes user interface elements for searching and displaying routes. The first portion 624 includes visual indications of routes 628, and the second portion 626 includes an optional button 631 selectable to initiate navigation guidance along the route.

[0210] exist Figure 6I In this process, device 500A detects the selection of optional button 631 (e.g., via contact 603) and initiates navigation guidance along route 628 (not shown) and then returns to the display user interface 602, as shown. Figure 6J As shown. Therefore, device 500A detected that the user of device 500A has traveled along route 628.

[0211] exist Figure 6J In the process, device 500A detects the selection of application icon 660 (e.g., via contact 603). In response, Figure 6K In the device 500A, a user interface 637 of a photo application is displayed. The user interface 637 includes a user-selectable button 634 that allows selection of content such as photo preview 636 (e.g., corresponding to an image currently being captured by one or more cameras of the device 500a).

[0212] exist Figure 6K In this process, device 500A detects the selection of user-selectable button 634 (e.g., via touch 603). In response, device 500A takes a picture 1 (not shown) and returns to the display user interface 602 upon detecting additional input, such as... Figure 6L As shown. Therefore, device 500A detected that the user of device 500A has taken photo 1.

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

[0214] In some implementations, prompt 638 is generated by a logging application. In some implementations, prompt 638 is generated by system-level software running on device 500A (e.g., software other than the logging application), such as the operating system of device 500A, based on activities (such as those described above) associated with various applications installed on device 500A. Optionally, prompt 638 is generated based on a logging schedule associated with the logging application (e.g., as referenced). Figure 8U(As described in option 888a). 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 is generated by the software on behalf of the application (such as on behalf of a logging application) (e.g., to warn the user that prompt 638 is not from the 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 “Recall your day at the zoo” and “Write down your trip last year”. In some embodiments, in response to detecting a selection of prompt 638, device 500A displays a picker user interface including 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 select (e.g., choose) content to provide to the logging application (or another application associated with the content or sub-prompt) (e.g., sent to the logging application or made available to the logging application). In some embodiments, the picker user interface is separate from the logging application (e.g., not part of the logging application). In some implementations, the picker user interface is displayed within the logging application. In some implementations, the picker user interface includes an acknowledgment display (such as by showing, as referenced) for providing the selected content to the logging application and optionally initiating a new log entry within the logging application. Figure 8C The described log entry user interface, in which the selected content is displayed in the logging user interface. In some implementations, the content is not provided to the logging application (e.g., sent to the logging application or made available to the logging application) until the user confirms the selection of the content (e.g., by selecting content from the picker user interface and / or by indicating a selection confirmation to maintain the privacy of the content until the user provides confirmation that the user wishes to provide the content to the logging application).

[0215] In some implementations, 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 referenced below. Figure 6L As described.

[0216] exist Figure 6L In this process, device 500A detects the selection of prompt 638 (e.g., via contact 603). In response, Figure 6MIn this embodiment, device 500A displays a user interface 640, which includes prompts 642, text or other content entry fields 644, instructions 646, a soft keyboard 648, optional options 651, 652, 654, and 656. In some implementations, device 500A displays user interface 640 overlaid on the user interface displayed when device 500A detects a selection of prompt 638, optionally without stopping the display of this user interface and / or without launching or displaying the logging application. Figure 6M In the log entry, prompt 642 includes information about the user's activity event, such as the location of the event (e.g., a zoo). Prompt 642 includes questions about the event, such as what the highlights of the event were, who was there, and how they reacted, as well as additional prompts for obtaining information about the event (e.g., what else is highlighted?). Text entry field 644 is interactive to allow input of text or other content as a response to prompt 642. Soft keyboard 648 is optional to facilitate typing text or other content into text entry field 644. Indication 646 is an indication or representation of a photograph taken by device 500A during the event (e.g., taken with mom at the zoo, thus displayed with an "M" indication overlaid on a corner of the photograph). Optional option 651 is selectable to change the prompt to a new and / or updated prompt related to the event (e.g., different questions related to the event generated and / or provided by device 500A). Optional option 652 is selectable to change the photograph to a new and / or updated photograph (e.g., taken by device 500A during the event). Option 654 can be selected to move to the next prompt to facilitate the creation of a log entry. Option 656 can be selected to end the display of the prompt to facilitate the creation of a log entry and the creation of a log entry with the content typed into the text entry field 644, part or all of the prompt 642 and / or part or all of the photograph corresponding to the instruction 646.

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

[0218] exist Figure 6N In this process, device 500A detects the selection of optional option 654 (e.g., via contact 603). In response, Figure 6OIn this process, device 500A updates user interface 640 to display a new prompt 658. Prompt 658 includes additional details about the event, such as request words used to describe it. 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 photograph associated with the event in indication 646.

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

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

[0221] exist Figure 6Q In this process, device 500A detects the selection of one or more keys on the soft keyboard 648 (e.g., via contact 603). In response, in Figure 6R In the process, device 500A updates the text entry field 644 of user interface 640 to include the text corresponding to the text in the interface. Figure 6Q The input detected in the device is used 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-based 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 such... Figure 6R The detected text content is “We met Mom there, and she was excited to see the penguins.” Device 500A optionally generates and displays an additional prompt (e.g., replacement prompt 661) with the content “What did Mom say to the penguins?” to encourage the user to type in additional details.

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

[0223] After creating the log entry, device 500A stops displaying user interface 640 and returns to displaying user interface 602 (or any user interface displayed when prompt 638 is shown and / or selected), as... Figure 6S As shown. In Figure 6S In the process, device 500A detects the selection of application icon 655 (e.g., via contact 603). In response, Figure 6T In the device 500A, a logging application user interface 606 is displayed. This user interface now includes a new log entry created via prompt 638, displayed as representation 670. Representation 670 of the log entry includes a reference to photos 1-3 associated with representation 670 and / or representation 672 of that photo (e.g., from within user interface 640).

[0224] exist Figure 6T In this process, device 500A detects the selection of representation 670 and / or representation 672 (e.g., via contact 603). In response, in Figure 6U In this process, device 500A updates user interface 606 to display log entry 674 corresponding to representation 670. Representation 670 is generated based on 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 photos or only a subset of photos presented along with the prompt.

[0225] As described in more detail with reference to method 700, device 500A optionally displays notifications of log entries (e.g., featured log entries) or generates animated video presentations for specific log entries associated with an event, person, place, or thing, and displays notifications of these log entries or animated video presentations facilitating access to these video presentations. Figure 6V At a point in time after the creation of log entry 674, device 500A displays notification 676 on user interface 602. Device 500A may optionally display 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 may optionally initiate a process of viewing an animated video presentation associated with and / or the content of log entry 674. Notification 676 includes instructions from the logging application and corresponding date and person, location, event, or thing.

[0226] exist Figure 6V In this process, device 500A detects the selection of notification 676 (e.g., via contact 603). In response, in Figure 6W In the device 500A, an animated video presentation 679 including photos and music is displayed. For example, the animated video presentation 679 includes text from a corresponding log entry, a photo from the log entry, and music associated with the log entry. The animated video presentation 679 includes an optional option 680, which allows users to save the animated video presentation 679 and / or share it with another user. Figure 6X In the meantime, device 500A continues to display animated video presentation 679, which includes the remaining photos (e.g., displaying a subsequent portion of animated video presentation 679).

[0227] In some implementations, instead of displaying it as a notification, the option to show an animated video presentation of log entry 674 is displayed in a widget (or as a widget). For example, in Figure 6Y In this context, device 500A displays a notification 683 shown as a widget on user interface 602 (e.g., a widget of a logging application that device 500A has previously received to include input in user interface 602). Similar to notification 676, notification 683 may be optionally configured to initiate a process of displaying a representation associated with a logging entry (e.g., an animated video presentation associated with logging entry 674).

[0228] As described in more detail with reference to method 700, device 500A optionally allows the user to create log entries based on content items. Figure 6Z In the process, device 500A detects the selection of application icon 635 (e.g., via contact 603). In response, Figure 6AA In this configuration, device 500A displays the user interface of a photo application and shows photo 678 after one or more additional inputs. Photo 678 is displayed along with sharing option 680, optional option 682, and optional option 684. Sharing option 680 allows users to share the photo with contacts or utilize it in another application, such as a logging application. Optional option 682 allows users to add photo 678 to a collection of favorite photos. Optional option 684 allows users to delete photo 678.

[0229] exist Figure 6AA In the process, device 500A detects the selection of sharing option 680 (e.g., via contact). In response, Figure 6BB In this embodiment, 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 In this configuration, the user interface 686 includes representations 687a-687d, optional options 688a-688d, and optional 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 these 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 sending photo 678 via email. Optional option 688c can be selected to initiate the process of transferring photo 678 to a messaging conversation. Optional option 618d can be selected to initiate the process of using photo 678 to generate a log entry. 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. Optional option 689c allows you to initiate the process of tagging and / or modifying photo 678.

[0230] exist Figure 6BB In this process, device 500A detects the selection of optional option 618d (e.g., via contact 603). In response, Figure 6CC In the middle, equipment 500A and with Figure 6M The prompt 642 is displayed in a similar manner to the user interface 640, which includes prompt 690 (e.g., overlaid on the photo user interface without launching or displaying the logging application). Prompt 690 includes information about photo 678, such as the location where the photo was taken and questions about photo 678. For example, user interface 640 includes photo 4 because photo 4 is the initial content item used as the basis for creating a log entry. User interface 640 can be combined with... Figure 6M The user interface 640 interacts in a similar way to create log entries based on photo 4.

[0231] As described in more detail with reference to method 700, device 500A optionally displays an indication of existing log entries associated with content items, as well as a display of content items (such as calendar entries). Figure 6DD In the process, device 500A detects the selection of application icon 610 (e.g., via contact 603). In response, Figure 6EE Upon receiving one or more additional inputs, device 500A displays user interface 692, which includes calendar details for a day selected by the user (e.g., December 17, 2022) and optional options 694a-694b corresponding to different calendar events for the selected day. Optional option 694a includes details of a calendar event at 8:00 AM. Optional option 694b includes details of a calendar event at 11:00 AM.

[0232] exist Figure 6EE In this process, device 500A detects the selection of 694b (e.g., via contact 603). In response, in Figure 6FF In this embodiment, device 500A extends optional option 694b to display user interface elements 695a-695c and optional option 695d. User interface element 695a displays the title of a calendar event, user interface elements 695b and 695c display a representation of the time period and / or duration of the calendar event for the selected day, and optional option 695d includes an indication that a log entry corresponds to a calendar event and can be selected to initiate the process of displaying the log 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 calendar events are associated with log entries, device 500A displays an indication of the presence of a log entry (e.g., option 695d) when displaying details of the calendar event and / or other user interfaces associated with the calendar event.

[0233] exist Figure 6FF In this process, device 500A detects the selection of optional option 695d (e.g., via contact 603). In response, Figure 6GG In the device 500A, a user interface 606 of a logging application is displayed, including a representation 670 of log entries. Option 617 allows selection to initiate a process of viewing one or more animated video presentations related to active events and / or log entries. In some embodiments, in response to... Figure 6FF The device 500A displays the contents of log entry 674 (e.g., such as...) upon input. Figure 6U (As shown in the image).

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

[0235] As described in more detail with reference to method 700, device 500A optionally allows the user to create log entries based on content items such as achievements in a fitness application. Figure 6JJ In the process, device 500A detects the selection of application icon 620 (e.g., via contact 603). In response, Figure 6KK After one or more additional inputs, device 500A opens the fitness application and displays achievement 697 (e.g., a representation of achievements obtained in the fitness application). Device 500A also displays sharing option 698, which can be selected in a similar manner to the previously described sharing option 680.

[0236] exist Figure 6KK In this process, device 500A detects the selection of sharing option 698 (e.g., via contact 603). In response, Figure 6LL In the middle, equipment 500A and in Figure 6BB In the user interface 686, photos 678 are displayed in a similar manner to achievements 697.

[0237] exist Figure 6LL In this process, device 500A detects the selection of optional option 618d (e.g., via contact 603). In response, Figure 6MM In the middle, equipment 500A and with Figure 6MThe user interface 640, which includes prompt 699, is displayed in a similar manner to prompt 642. Prompt 699 includes information about achievement 697, such as the type of activity. Prompt 699 also includes questions about the activity event. User interface 640 can also be integrated with... Figure 6M The user interface 640 interacts in a similar way to create log entries based on the achievement.

[0238] As described in more detail with reference to method 700, device 500A optionally allows the user to manually request a prompt to create a log entry. Figure 6NN In the process, device 500A displays optional options 616 and 618 (similar to...) in the user interface 606 of the logging application. Figure 6D ).exist Figure 6NN In the process, device 500A detects the selection of optional option 618. In response, in Figure 600 In the middle, device 500A displays Figure 6D User interface 640. User interface 640 optionally has Figure 6M The user interface 640 has one or more of the following characteristics. Therefore, in some embodiments, the device 500A displays the user interface 640 based on the (recent) activity of the user and / or the device 500A in response to detecting such manual input, even if such activity does not meet the criteria for displaying the prompt 638.

[0239] As described in more detail with reference to method 700, device 500A optionally allows the user to create log entries from a second device. Figure 6PP An exemplary device 500B including a touchscreen 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 and / or logged into and / or configured with the same user account as device 500A). Figure 6PP In this context, device 500B is displaying user interface 607, which optionally is a dial user interface of device 500B and includes a time indication. In some embodiments, user interface 607 is the main screen user interface of device 500B (e.g., as shown in Reference 1). Figure 4A(As described). Device 500B also displays prompt 609 on touchscreen 504B. Prompt 609 indicates its relevance to a logging application and includes an invitation to create a logging 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 may optionally be selected to initiate a process of creating a logging entry for typing into a logging application (e.g., on device 500A).

[0240] exist Figure 6PP In this process, device 500B detects the selection of prompt 609 (e.g., via contact 603). In response, Figure 6 QQ In this embodiment, device 500B extends prompt 609 and / or displays a prompt user interface (e.g., having one or more of the features of user interface 640) to include a question that can be answered as part of creating a log entry. In some embodiments, because the display size of device 500B is optionally small, the extended prompt 609 (or other user interface) includes optional options 611a-611c corresponding to a predefined answer to the displayed question, instead of the extended prompt 609 (or other user interface) including a free-form text entry field that provides an answer to the displayed question. Optional options 611a-611c are selectable for typing an answer to prompt 609 (e.g., for inclusion in a log entry). In some embodiments, the predefined response corresponding to optional options 611a-611c is an emoji response. For example, optional option 611a is selectable for typing a smiley face response to prompt 609 (e.g., for inclusion in a log entry), and optionally includes a representation of the corresponding response (e.g., an image). Option 611b allows you to type a sad face response to prompt 609 (e.g., for inclusion in a log entry), and optionally includes a representation of the corresponding response (e.g., an image). Option 611c allows you to type a related facial response to prompt 609 (e.g., for inclusion in a log entry), and optionally includes a representation of the corresponding response (e.g., an image).

[0241] Figure 7 It is shown according to such Figures 6A to 6QQ The flowchart illustrates a method 700 for displaying a prompt to a user to generate log entries in some implementations. Method 700 is optionally performed on an electronic device (such as device 100, device 300, or device 500), as referenced above. Figures 1A to 1B , Figures 2 to 3 , Figures 4A to 4Bas well as Figures 5A to 5H The operations in method 700 may be optionally combined, and / or the order of some operations may be optionally changed.

[0242] As described below, method 700 provides a way to display a prompt to the user indicating the generation of log entries. This method reduces the cognitive burden on the user when interacting with the device user interface of this disclosure, thereby creating a more efficient human-machine interface. For battery-powered electronic devices, improving the efficiency of user interaction with the user interface saves power and increases the time between battery charging.

[0243] In some implementation schemes, such as in Figure 6A In this embodiment, method 700 is performed at an electronic device (e.g., 500A) communicating with a display generating 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, smartphone, media player, or wearable device) including wireless communication circuitry that optionally communicates with one or more of the following: a mouse (e.g., external), a touchpad (optionally integrated or external), a remote control device (e.g., external), another mobile device (e.g., separate from the electronic device), a handheld device (e.g., external), and / or a controller (e.g., external), etc. In some embodiments, the display generating component is a display integrated with the electronic device (optionally a touchscreen display), an external display such as a monitor, projector, television, or a hardware component (optionally integrated or external) for projecting a user interface or making the user interface visible to one or more users, etc. In some implementations, method 700 is performed at or by a vehicle (e.g., at the infotainment system of a vehicle having or communicating with one or more display generating components and / or input devices).

[0244] In some implementations, the electronic device detects (702a) activity events associated with the 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 for Mom Figure 6I Driving to the zoo and Figure 6KThe electronic device takes photos 1 (e.g., 636) (e.g., during time periods such as 5, 10, 30, 60, 120, 240, or 480 minutes). For example, the electronic device optionally tracks actions performed by the electronic device over time. In some embodiments, these actions correspond to actions performed by the user of the electronic device during a given day. For example, these actions optionally include: the electronic device calling contacts 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 using a workout application installed on the electronic device to detect the storage and / or completion of workouts (e.g., hiking, running, and / or swimming); 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 in the electronic device; and / or the electronic device detecting the presence of the electronic device at a location (e.g., a park, restaurant, and / or the user's workplace) for an extended period of time (e.g., greater than 5, 10, 30, 60, or 120 minutes). Additionally or alternatively, in some implementations, 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, and / or the user's smartphone, all optionally logged into the same user account associated with the user).

[0245] In some implementations, in response to detecting an activity event associated with a user (702b), based on determining that the activity event meets one or more criteria, such as Figure 6GCalling Mom. In some implementations, one or more criteria include those based on one or more factors described below, which are met when the activity event is a noteworthy activity of the user of the electronic device. In some implementations, one or more criteria include those that are met when the activity event occurs within a threshold time period from the current time (e.g., within the last day, week, month, or year). For example, calling popular contacts via electronic devices (e.g., interacting with them via messaging applications installed on the electronic device, via telephone calls 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, 10, 30, 60, 120, or 240 minutes during a given time period of 30, 60, 120, 240, 480, 960, or 1920 minutes) and / or exceeding a threshold percentage of device or communication usage (e.g., more than 5%, 25%, 50%, 60%, 70%, 80%, or 90%)), recording exercise on the electronic device, or detecting movement of the electronic device from a first location to a second location that is greater than a threshold distance from the first location (e.g., greater than 3, 5, 20, 50, 100, 150, 1000, 3000, or 5000 miles) optionally meets the criteria. Alternatively, calling a phone number not stored in the electronic device and / or not associated with a contact in the electronic device's user profile, or detecting movement of the electronic device from a first location to a second location at a distance less than the aforementioned threshold (e.g., 1, 2, 3, 4, or 5 feet), may optionally not meet the criteria.

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

[0247] In some implementations, based on the determination that an activity event does not meet one or more criteria, the electronic device abandons the display (702d) of the prompt associated with the logging application via the display generation component if... Figure 6G The phone call in the example is to the zoo, which is not a welcome contact. In some implementations, if an activity event does not meet one or more criteria, and if the user of the electronic device wants to create a log entry for the activity event in the logging application, the user must manually launch the logging application and provide input from within the logging application to create the log entry. Displaying prompts 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, thus reducing the amount of input required to create log entries.

[0248] In some implementations, an activity event does not meet one or more criteria, such as if Figure 6I The route in the image is to the gas station, not the zoo. In some implementations, after detecting an activity event, the electronic device receives first user input via one or more input devices, corresponding to a request to manually create a corresponding log entry in the logging application, such as... Figure 6C Contact 603 in the middle. In some implementations, the first user input is to select the logging icon from the main screen user interface of the electronic device, or to select the option to manually create a logging entry within the user interface of the logging application.

[0249] In some implementations, in response to receiving the first user input, the electronic device initiates the manual creation of the corresponding log entry in the logging application (such as...). Figure 6C Contact 603 and Figure 6D Contact 603 in the middle) to create Figure 6E The process of logging entry 621 in the system. In some embodiments, the selection initiates the process of typing in the logging application and creating the log entry. In some embodiments, the log entry is created automatically. In another embodiment, 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 for user input, including that included in the log entry, to be typed into the user interface. Providing a manual typing point for log entries provides the user with a simple typing point for creating log entries, which is not dependent on being prompted to create log entries, thus providing increased flexibility in the creation of log entries.

[0250] In some implementations, the first user input points to a content item displayed in a first application different from the logging application (such as...). Figure 6AA(Contact 603 in the context). For example, the first application is optionally stored or installed on an 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 along with a user-selectable option that can be chosen to initiate a process of creating log entries in the logging application while stopping or not stopping the display of the first application. In some embodiments, the process of manually creating corresponding log entries in the logging application utilizes content items as part of the log entries, such as... Figure 6AA Photo 678. In some embodiments, the electronic device creates a log entry that is connected to and / or includes the content item within a logging application. In some embodiments, the electronic device displays a prompt associated with the content item as part of a process of manually creating the 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 log entries with content items provides users with a simple way to log about content items, thereby reducing the amount of input required to create log entries for content items.

[0251] In some implementations, the first user input refers to the user interface displayed in the logging application, such as... Figure 6C Contact 603 in the middle. In some implementations, logging entries are created directly from within the logging application. For example, the first user input includes selecting an option displayed in the logging application's user interface for creating a logging entry within the logging application. Providing a manual way to start a logging entry from within the logging application offers the user a simple way to create a logging entry from a user interface that expects to include options for creating a logging entry, thus reducing the amount of input required to find the point where the logging entry is created.

[0252] In some implementations, before the user interface is displayed in the logging application, the electronic device receives second user input corresponding to the request to display the logging application via one or more input devices, such as... Figure 6A Contact 603 in the system (e.g., receiving a selection of an icon for a logging application on the main screen user interface of an electronic device).

[0253] In some implementations, in response to receiving a second user input, the electronic device requests user authentication (such as...) before displaying the logging application. Figure 6B(Contact 603 in the context of logging). In some implementations, user authentication protects logging entries stored in the logging application. In some implementations, the electronic device will only allow access to the logging application upon receiving successfully authenticated input, and will not display the logging application if the authentication input is not successfully authenticated. Requiring authentication of entries for the logging application ensures the security of logging entries and improves user privacy and security.

[0254] In some implementations, user authentication includes facial recognition, fingerprint recognition, or password recognition (such as in...). Figure 6B This refers to one or more of the following methods (e.g., password authentication). In some implementations, user authentication requires the user to scan or capture 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 touchscreen of the electronic device. Requiring authentication of entries for logging applications ensures that logging entries are secure and improves user privacy and security.

[0255] In some implementations, after a log entry is created in the logging application, the electronic device displays a user interface of the logging application, comprising multiple log entries (e.g., 608, 613, 612 and / or 614) (including a log entry (e.g., 670)), via a display generation component, wherein the log entries are displayed as pages of a book on the user interface of the logging application (such as...). Figure 6C Within the user interface 606. For example, log entries are displayed one by one along with multiple log entries, and in response to detecting a selection of one of the log entries, the electronic device displays the selected log entry. In some embodiments, the content of a given log entry and / or indications of multiple log entries are displayed on one or more virtual pages of a virtual book. Displaying log entries as pages of a book in the user interface is an efficient way to arrange log entries and reduces the amount of input required to navigate to the correct log entry.

[0256] In some implementations, after a logging entry is created in the logging application, the electronic device displays a user interface of the logging application, comprising multiple logging entries (e.g., 608, 612, 613 and / or 614) (including a logging entry (e.g., 670)), via a display generation component. The multiple logging entries are displayed chronologically in the user interface of the logging application (such as...). Figure 6CWithin the user interface (606). For example, the log entry is displayed in the user interface after one or more log entries with an earlier creation and / or last edit date than the log entry itself, and / or before one or more log entries with a later creation and / or last edit date. Displaying log entries in chronological order in the user interface allows the user to easily locate the desired entry, thereby reducing the amount of input required to locate and / or access the desired entry.

[0257] In some implementations, the logging application, which includes logging entries, is accessible via electronic devices (such as...) Figure 6PP The second electronic device (500B) is associated with the device and accesses the log entries. In some embodiments, the electronic device is a tablet, watch, computer, or smart TV or set-top box. Therefore, in some embodiments, the second electronic device is a mobile phone, while the electronic device is a smartwatch. In this case, log entries are optionally typed and / or created via input at the smartwatch (e.g., the electronic device), and when the second electronic device displays a logging application, it displays log entries created in response to input detected at the electronic device. In some embodiments, the second electronic device is associated with the electronic device when both the second electronic device and the electronic device are configured and / or logged into the same user account and / or user profile. The logging application, which allows log entry creation at multiple devices, provides the user with various ways to create log entries.

[0258] In some implementations, the activity event does not meet one or more criteria, such as Figure 6AA Photo 678. In some embodiments, after detecting an activity event associated with the user and abandoning the display of a prompt associated with the logging application via a display generation component, the electronic device receives 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 an activity event, such as... Figure 6CC The prompt 690 in the document. In some implementations, the first user input points to the user interface of the logging application. For example, the first user input is a selection of a "Show Logging Prompt" button displayed in the user interface of the logging application. In some implementations, the first user input points to content such as photos, albums, maps, web searches, or podcasts.

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

[0260] In some implementations, the prompt includes one or more details related to the event, such as Figure 6CC Tip 690 in the document. In some implementations, one or more details include the type of activity performed as part of the activity event (e.g., running, phone call, travel, TV show, 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, videos, or other content associated with and / or captured during the activity event. Providing users with details of the activity facilitates the efficient creation of log entries, thereby reducing the amount of input required to correct unwanted portions of log entries.

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

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

[0263] In some implementations, based on the determination that the first user input includes emoji input, the electronic device combines the emoji input into a log entry, such as if the electronic device receives emoji input. Figure 6M In the text entry field of the system. For example, the electronic device optionally receives emoji input from the user. In some embodiments, emoji input includes detecting the selection of one or more emoji keys displayed on an emoji keyboard or other emoji user interface. For example, the electronic device optionally displays one or more emojis and prompts (or a user interface displayed in response to a selection of the prompts) to the user via a display device, and upon receiving a selection of one of the one or more emojis, types the selected emoji into a log entry. In some embodiments, emoji input is voice input pointing to an animated emoji (e.g., optionally customized by the user), and speaking the detected / recorded voice input as an animated emoji is typed into a log entry. Providing the user with various ways to input content into log entries avoids erroneous input into log entries and reduces the amount of input required to correct such erroneous input.

[0264] In some implementations, the electronic device receives first user input via one or more input devices corresponding to a request to create a corresponding log entry associated with a content item, such as... Figure 6R Contact 603 in the context of content. In some implementations, content items are photos, music, fitness achievements, video content, calendar events, routes, books, podcasts, or games.

[0265] In some implementations, in response to receiving first user input, the electronic device creates a corresponding log entry, including linking the corresponding log entry to content items, such as... Figure 6T The images 1-3 show representations of 670. In some embodiments, the representation of a content item is stored within the corresponding log entry to alert the user that the corresponding log entry is associated with a content item. Furthermore, when a user selects a representation of a 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 logging application). Providing the user with a way to link content items to log entries reduces the amount of input required to navigate to and / or display the content item associated with the log entry.

[0266] In some implementations, after receiving the first user input and creating a corresponding log entry, the electronic device receives a second user input corresponding to the request for access to content items via one or more input devices, such as... Figure 6FFContact 603 in the context of logging. For example, the second user input may optionally be 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 along with the corresponding log entry. Therefore, the second user input may optionally be a selection of a representation of the content item.

[0267] In some implementations, in response to receiving a second user input to access a 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 a display generation component, such as... Figure 6GG The representation in 670 is as follows. In some embodiments, the electronic device displays a representation of a log entry simultaneously with the content item. In some embodiments, the electronic device displays a representation of a log entry without a content item. In some embodiments, the representation of a log entry can be selected to display the content of the corresponding log entry, including the content item. In some embodiments, the representation of a log entry is a visual indication indicating that the corresponding log entry is associated with a content item. In some embodiments, the visual indication is displayed simultaneously with the content item. In some embodiments, the visual indication can be selected to open the corresponding log entry. Displaying the log record when the user revisits the content item provides the user with an efficient way to access the log record, thereby reducing the amount of input required to access the log record entry when revisiting the content item.

[0268] In some implementations, when displaying a prompt associated with the logging application (e.g., 638), the electronic device receives 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 the prompt. In some embodiments, the first user input includes a click, tap, or swipe input pointing to the prompt. In some embodiments, the electronic device displays additional user-selectable options in the prompt, which, when selected, display a user interface including one or more details related to the event, as described below.

[0269] In some implementations, in response to receiving first user input, the electronic device displays a user interface via a display generation component, including one or more details related to the activity event, such as... Figure 6MTip 642 in the document. In some implementations, details include songs listened to during the event, routes taken during the event, photos or videos taken during the event, restaurants eaten during the event, fitness information obtained during the event, people associated with the event (e.g., people appearing in photos taken during the event and / or people located at the event location during the event), podcasts listened to during the event, movies or shows watched during the event, and / or locations visited during the event. Providing users with details of their activities facilitates the efficient creation of log entries, thereby reducing the amount of input required to correct unwanted portions of log entries.

[0270] In some implementations, one or more details include one or more instructions from one or more persons associated with one or more photographs taken by the electronic device during the event, such as Figure 6M The letter "M" represents "mother". In some implementations, the electronic device determines the person associated with a photo based on photo activity stored on the electronic device. In some implementations, the person is indicated in the user interface as a representative avatar or initial. In some implementations, the identified person is those who were with the electronic device when it took pictures or videos during the event and / or even those who appeared in the pictures and / or videos taken during the event. Identifying the person associated with the event facilitates the efficient creation of log entries, thereby reducing the amount of input required to correct unwanted portions of log entries.

[0271] In some implementations, when displaying a prompt associated with the logging application (e.g., 638), the electronic device receives 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 the context of (e.g., input interacting with prompts, as described herein).

[0272] In some implementations, in response to receiving a first input, the electronic device displays a first question related to the activity event via a display generation component, such as... Figure 6M Tip 642. In some implementations, the first question concerns one or more details related to the event. For example, the first question may optionally include questions about the location of the electronic device during the event and / or the people in photographs taken by the electronic device during the event.

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

[0274] In some implementations, after receiving second user input, the electronic device displays a second question related to the activity event via a display generation component, wherein the second question is based on the first answer, such as... Figure 6O Tip 658 in the document. In some implementations, the second question is determined by a machine learning model. In some implementations, the content of the second question is based on the content of the first answer, and the content of the second question is optionally different if a different answer to the first question is provided. For example, if the first answer introduces a specific activity that occurred during the event, the second question optionally points to that specific activity. For example, if the device detects a hiking event, the first question is optionally “How was the hike today?”, and if the first answer does not mention a specific activity other than hiking, the second question is optionally “Describe the hike in three words.” However, if the first answer is “Great! There was a good place for meditation 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 answers increases the amount of content related to the event in the log entries.

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

[0276] In some implementations, after receiving second user input, the electronic device displays a second question related to the activity event via a display generation component, wherein the second question is based on one or more previous log entries in a logging application, such as if Figure 6O The prompt 658 is based on Figure 6C Details of log entries 608-612 are provided. In some implementations, the electronic device uses information typed by the user in previous log entries to determine a second question. For example, if one or more previous log entries (often) discuss meditation at a particular mountaintop, and the activity includes hiking on that mountain, the second question may optionally include a question about meditation, such as, “Hiking was nice, did you meditate today?” Providing follow-up questions based on earlier answers increases the amount of content related to the activity in the log entry.

[0277] In some implementations, one or more criteria include criteria that are met based on the relationship between the current time of day at the electronic device and information associated with the user of the electronic device, such as if Figure 6LThe prompt 638 is displayed outside of working hours (e.g., not during working hours). In some implementations, this relationship creates a “smart” time for the electronic device to prompt the user. For example, if the current time of day is 6 p.m. (e.g., the end of the day) and information associated with the user of the electronic device indicates that the user typically uses the electronic device at 6 p.m., this relationship optionally indicates that this is a “smart” time for the prompt and meets that criterion. In some implementations, the “smart” time is optionally based on the user’s preferred settings. In additional implementations, the “smart” time is optionally based on the device’s focus mode (e.g., a prompt delay when the electronic device is in a mode that suppresses one or more notifications, such as notifications for incoming calls, incoming messages, or incoming emails). Providing the prompt to the user at the appropriate time increases the likelihood of user engagement with the prompt and avoids wasting resources on displaying the prompt when interaction with it is unlikely.

[0278] In some implementations, one or more criteria include criteria satisfied based on the frequency of one or more contacts associated with user contacts and activity events on electronic devices, such as if... Figure 6G The criterion is met if the electronic device detects an activity event involving a popular contact that the device contacts relatively frequently (e.g., more than 2, 3, 5, or 10 times per day). Alternatively, the criterion is not met if the electronic device detects an activity event involving a contact that the device contacts relatively infrequently (e.g., less than 2, 3, 5, or 10 times per day).

[0279] In some implementations, one or more criteria include movement of electronic devices from a first location to a second location associated with an activity event (such as movement from home to a zoo, etc.). Figure 6I The criteria are satisfied if one or more of the following are met (as shown). For example, if the electronic device moves from a first location to a location frequently accessed by the electronic device (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 relatively infrequently accessed by the electronic device (e.g., less than once per year), the criterion is met (otherwise, the criterion is optionally not met).

[0280] In some implementations, one or more criteria include one or more photographs (such as photograph 1 (e.g., 636)) taken by an electronic device and associated with an event, such as in Figure 6KThe criteria are met if the photo includes popular contacts as described above. Alternatively, the criteria are not met if the photo does not include popular contacts. For example, the criteria are met if the photo was taken in 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). As another example, the criteria are met if the electronic device takes more than a threshold number of photos during an event (e.g., 1, 3, 5, 10, 20, 50, or 100), otherwise the criteria are not met.

[0281] In some implementations, one or more criteria include criteria satisfied based on one or more operations performed by a second electronic device associated with a user of the electronic device, wherein these operations are associated with activity events, such as if wearing a smartwatch at a zoo and carrying... Figure 6PP The device counts steps when it reaches 500B. For example, if the second electronic device is a watch 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), and the operation is recording exercise activity (optionally exceeding a threshold number of times, such as 1, 3, 5, 10, or 20 times, during a time period such as 6 hours, 12 hours, 1 day, 3 days, 7 days, or 30 days), then the criterion is met. In some implementations, if the second electronic device is a watch and the operation is playing songs frequently played by the electronic device (e.g., more than 5, 7, or 10 times per day), then 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, then the criterion is not met.

[0282] In some implementations, one or more criteria include those based on activity events accessed by electronic devices (such as...). Figure 6G The criteria are met if one or more of the content associated with "calling mom" are included in the event. For example, if the electronic device detects a call to a popular contact (e.g., a contact appearing in the event) during or after an event, the criterion is met. Similarly, if the electronic device detects that a photo is opened during or after an event (e.g., a photo taken during the event), the criterion is met.

[0283] In some implementations, one or more standards include standards met by one or more applications in one or more applications associated with activity events accessed by the electronic device, such as... Figure 6IFor example, opening a map application for zoo visits. Similarly, if an electronic device detects that a fitness application is opened during or after an event, the criteria are met. Providing criteria for prompting users allows them to recall details of the event efficiently, increasing the likelihood of engaging with prompts and reducing wasted resources on displaying prompts or creating useless log entries.

[0284] In some implementations, after an activity event is detected and a log entry associated with the activity event is created in the logging application, the electronic device displays optional options associated with the activity event via a display generation component, such as... Figure 6V Notification 676 in the document. In some embodiments, the optional options include one or more representations of the activity event. In some embodiments, the optional options include text describing the activity event. In some embodiments, the optional options are displayed on the wake-up screen user interface, lock screen user interface, or home screen user interface of the electronic device. In some embodiments, the user optional options may be selected to initiate a process of viewing an animated video presentation associated with a log entry (e.g., content included in the log entry).

[0285] In some implementations, when displaying optional options associated with an activity event (e.g., 676), the electronic device receives a first input corresponding to a selection of an optional option via one or more input devices, such as... Figure 6V Contact 603 in the middle. In some implementations, the first input includes a click, tap, or swipe input pointing to an optional option.

[0286] In some implementations, in response to receiving a first input, the electronic device displays an animated video presentation associated with a 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 6WThe animated video presentation is 679. In some embodiments, content items are photos, achievements, representations of content items such as routes, text entries, and / or emoji entries typed into the log entry when it is created. In some embodiments, the electronic device displays the animated video presentation along with music. In some embodiments, the music is not part of the log entry (e.g., the electronic device does not detect user input associating music with the log entry). Therefore, in some embodiments, the electronic device (automatically, without user input) selects the music to play and displays the animated video presentation. Providing users with the option to view animated video presentations for log entries provides efficient viewing of log entries and reduces the amount of input required to access the content of these log entries.

[0287] In some implementations, displaying optional options (e.g., 638) includes determining that one or more display criteria are met at the current time of day at the electronic device, and the electronic device displays optional options, such as... Figure 6L The prompt 638 is displayed outside of working hours (e.g., not during working hours). For example, if the current time of day is outside of working hours, the criterion is met. In some implementations, 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 when the user of the electronic device stops using the device. In some implementations, the criterion is met if the current time of day is at least a time threshold following an exercise (e.g., 15, 30, or 60 minutes). In some implementations, the criterion is met if the current time of day is at least a time threshold following an activity event (e.g., 1, 2, 5, or 7 days).

[0288] In some implementations, the electronic device abandons displaying optional options (e.g., based on the determination that the current time of day at the electronic device does not meet one or more display criteria) Figure 6L (678 in the original text). In some implementations, the criterion is not met if the current time of day falls during working hours. In some implementations, the criterion is not met if the current time of day falls during "evening hours" when users of electronic devices do not typically use them. Displaying optional options at appropriate times increases the likelihood that users will engage with the optional options, reduces wasted resources on displaying optional options when interaction with them is not possible, and avoids interruptions in device use, thus reducing errors in use.

[0289] In some implementations, optional options (e.g., 676) are displayed on the user interface of the electronic device outside the logging application, such as Figure 6VUser interface 602. In some implementations, optional options are displayed on the wake-up screen user interface, lock screen user interface, 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 / TV show playback application), or the main screen user interface of the electronic device.

[0290] In some implementations, optional options are displayed on the user interface of the logging application, such as if Figure 6V Notification 676 was displayed Figure 6T Within the user interface 606. In some embodiments, the optional options are displayed within the user interface of the logging application. In some embodiments, the optional options are displayed within a separate tab in the user interface of the logging application. Displaying optional options for animated video presentation in different user interfaces increases the likelihood of user interaction, thus reducing the amount of input required to view the animated video presentation and reducing wasted resources on displaying optional options when interaction with the optional options is not possible.

[0291] In some implementations, the animated video presentation associated with log entries includes first-party content, third-party content, or both, such as... Figure 6W The animated video presentation 679 includes Photos 1 and 2, but also includes online reviews of the zoo. In some embodiments, first-party content is content stored on electronic devices, 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 separate electronic devices or servers, such as online reviews and online photos. For example, the animated video presentation optionally includes a map taken of the event, photos from the event, and also displays the names of people involved in the event or reviews of restaurants visited during the event, wherein the reviews are optionally downloaded from a third-party server that includes reviews, photos, and / or other (optionally, crowdsourced) information about the restaurants (including the visited restaurants). Expanding the content associated with log entries to include multiple content sources provides a more comprehensive animated video presentation and reduces the need for further input for manually searching for additional information related to the event and / or log entries.

[0292] In some implementations, the display of animated video associated with log entries includes the presentation of music, such as... Figure 6WAs shown (e.g., playing music while displaying an animated video presentation). In some embodiments, the electronic device automatically selects the music (e.g., no user input is required to select the music). In some embodiments, the electronic device selects the music based on log entries. For example, if the log entry is about a fun outdoor activity, the electronic device may optionally select upbeat music for the animated video presentation. In some embodiments, the electronic device includes a user-selectable option as part of the animation presentation for the user to change the music. Incorporating music into the animated video presentation avoids the need for additional user input for playing music along with the animation presentation.

[0293] In some implementations, the prompt is displayed via a display generation component in a widget displayed in the system user interface of the electronic device, such as... Figure 6Y Notification 683 (e.g., a widget). In some embodiments, the widget is displayed on the main 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 containing 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 prompts in widgets increases the likelihood that the user will interact with them and reduces wasted resources on displaying optional options when interaction with the optional options is unlikely.

[0294] In some implementations, such as if Figure 6V Notification 676 is displayed in the corresponding Figure 6AIf the prompt is displayed within the application icon 620 of the first application, then the prompt is displayed in the first application other than the logging application. In some embodiments, the first application is a note-taking application, a music application, a fitness application, a map application, a photo application, a content viewing application, or any other application other than the logging 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 the fitness application on the device as an activity event (or part of an activity event), a 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, a prompt is optionally displayed in that application (or 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 while the electronic device is displaying an application other than the logging application increases the likelihood that the user will interact with the prompt and reduces the amount of input required to create a logging entry.

[0295] In some implementations, the electronic device receives first user input directed to the prompt via one or more input devices (e.g., Figure 6L (638 in the original text). In some implementations, the first user input includes a click, tap, or swipe to a prompt.

[0296] In some implementations, in response to receiving first user input, the electronic device displays information related to the activity event via a display generation component without stopping the display of the first application, for example, if the electronic device receives information corresponding to... Figure 6A When input is received from a prompt within the application corresponding to application icon 620, a separate user interface is overlaid on the application corresponding to application icon 620. In some embodiments, the information is displayed simultaneously with the first application within the first application or in a separate user interface overlaid on the first application. In some embodiments, the electronic device allows the user to switch between the first application and the separate user interface. Providing the user with a way to interact with prompts without leaving the first application does not interrupt the user's interaction with the first application, reduces the amount of input required to return to the first application, and reduces errors in device use.

[0297] In some implementations, log entries are accessible via a logging application, such as Figure 6TThe representation in the text is 670. In some implementations, log entries are viewable via a logging application. In some implementations, log entries are searchable via a logging application. In some implementations, log entries are accessible via a logging application. Storing log entries in the logging application provides users with an accessible repository to access log entries at a later date, thereby reducing the amount of input required to access log entries.

[0298] In some implementations, the prompt is displayed as a notification on the electronic device, such as Figure 6L The prompt 638. In some implementations, the prompt is displayed as a notification on the lock screen or other user interface. Therefore, in some implementations, the prompt is displayed in the same manner and / or within the same user interface as notifications displayed for other applications (e.g., email applications, messaging applications, phone applications, and / or calendar applications). Displaying the prompt as a notification provides the user with accessible and consistent alerts, thereby reducing the amount of input required to create logging entries and reducing errors in device use.

[0299] In some implementations, in response to detecting an activity event associated with a user, and based on determining that the activity event meets one or more criteria, an electronic device initiates a process of displaying a second prompt associated with a logging application on a second electronic device associated with that 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 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 The prompts are 609 and 603. In some embodiments, the second electronic device is a watch, and the electronic device is a telephone. Therefore, the second prompt is optionally displayed on the watch and includes one or more emoji-based example responses to the second prompt. In some embodiments, when the user selects an emoji or one or more emojis as a response, the electronic device creates a log 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 amount of input required to create log entries.

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

[0301] In some implementations, 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 6 QQ Optional options 611a-611c are provided. 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 the emoji keyboard displayed on the phone) but not text input (e.g., because the watch does not display a text keyboard with prompts). Providing the user with different input options for different prompts ensures that the prompts occupy an appropriate screen size for the corresponding device on which they are displayed.

[0302] It should be understood that, Figure 7 The specific order in which the operations described herein are presented is merely exemplary and is not intended to indicate that the described order is the only possible order in which these operations can be performed. Those skilled in the art will conceive of various ways to reorder the operations described herein.

[0303] 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., combined with...). Figures 1A to 1B , Figure 3 , Figures 5A to 5H (as described above) or application-specific chips. Furthermore, the above references... Figure 7 The operation is optionally performed by Figures 1A to 1BThe components depicted are used to implement this. For example, the detection operation 702a and display operation 702c are optionally implemented by an event classifier 170, an event recognizer 180, and an event handler 190. An event monitor 171 in the event classifier 170 detects a touch on the touchscreen 504, and an event dispatcher module 174 transmits the event information to the application 136-1. The corresponding event recognizer 180 of the application 136-1 compares the event information with a corresponding event definition 186 and determines whether a first touch at a first location on the touchscreen corresponds to a predefined event or sub-event, such as a selection of an object on the user interface. When a corresponding predefined event or sub-event is detected, the event recognizer 180 activates the event handler 190 associated with the detection of that event or sub-event. The event handler 190 optionally utilizes or invokes a data updater 176 or an object updater 177 to update the application's internal state 192. In some embodiments, the event handler 190 accesses a corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly understand how it can be based on Figures 1A to 1B The components depicted in the diagram are used to perform other processes.

[0304] Figures 8A to 8C The process for creating the first log entry in a logging application (such as the logging application described in reference methods 700, 900 and 1000) is described (e.g., to help users create their first log entry).

[0305] Figure 8A An exemplary device 500A is shown, which includes a touchscreen 504A and is displaying a user interface 802, which corresponds to Figure 6A The user interface 602 is shown. The user interface 802 includes an application icon 655, which corresponds to the one shown in the reference. Figure 6A The described logging application is used to create and access logging entries.

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

[0307] User interface 806 includes power indicators 808a, 808b, and 808c, which indicate to the user the various options available to the user for creating log entries. User interface 806 includes power indicator 808d, which can be selected to initiate the creation of a new log entry.

[0308] In response to the detection of a selection of the power indicator 808d, device 500A displays as follows: Figure 8C The log entry user interface 810 shown allows users to create new log entries. The log entry user interface 810 is optionally the 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 log entries. In some embodiments, the log entry field 812 has a reference... 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 device 500A), text message conversations, telephone calls (e.g., the date, time, and / or duration of the telephone 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 and / or accessible by device 500A.

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

[0310] When the "Moment" icon 814a is selected, the device 500A displays one or more "Moments," each "Moment" including one or more related content items, as shown in the reference. Figure 8EAs described. In some implementations, a moment is a collection of one or more related content items, such as content items having the same date or associated with the same event. In some implementations, device 500A generates, identifies, and / or stores moments (e.g., a collection of one or more related content items) on device 500 (e.g., in a logging application) based on analysis of content items stored on 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 the user's camera roll, text message conversations between the user and another person, and locations visited by the user are all associated with the user's birthday, and may group such content items into birthday-related "moments." Optionally, in addition to content items, a moment also includes metadata associated with the content items, such as the date associated with the content item, the title associated with the content item, event data associated with the content item, the 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 content items (e.g., data captured and / or generated by applications associated with content items). Optionally, device 500A generates, identifies, and / or stores moments without explicit input from the user regarding the content items to be included in the moment (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 log entries associated with these moments.

[0311] When the photo library icon 814c is selected by the user, it displays a thumbnail 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 to be included in the log entry, as shown in the reference. Figure 8I As described. When the camera icon 814b is selected, the device 500A displays the camera user interface, which allows the user to capture new photos and add them to log entries, as described in the reference. Figures 8J to 8K As described. The audio clip icon 814d, when selected, allows the user to record audio clips and add them to a log entry, as described in the reference. Figures 8L to 8M As described, the location icon 814e, when selected, displays one or more location items (e.g., a map of a previously recorded trip or the location 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.

[0312] The log entry user interface 810 optionally includes a suggested moment 816a (optionally displayed below the log entry field 812), which includes multiple content items that have been identified as related to each other, such as by association with a single event, location, and / or date that can be considered a "moment" in the user's life (e.g., by device 500A and / or by another device). The suggested moment 816a can be used as a prompt to suggest activities or events to be logged to the user. Figure 8C In the example, suggested moment 816a includes a first photo 818a, a second photo 818b, a location item 818c (e.g., a location or route on a map), 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 optionally included in suggested moments include videos, text messages, fitness activities, or other types of content items generated by various applications. In some implementations, in response to detecting a selection of suggested moment 816a (e.g., a tap on suggested moment 816a), a representation of moment 816a and / or content items 818a-818e is added to log entry field 812 and / or content entry area 817 (e.g., above log entry field 812), as referenced. Figures 8F to 8G As described.

[0313] The log entry user interface 810 also includes a power indicator 820, which, when selected, causes the contents of the log entry field to be saved as a log entry (e.g., saved to a logging application). Optionally, after saving the log entry in response to detecting a selection of the power indicator 820, the device 500A exits the log entry user interface 810 and optionally displays a log timeline interface, as shown in the reference. Figure 8N As described.

[0314] In some implementations, a user can initiate text input 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 a 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 As shown. Optionally, if the text typed by the user exceeds the capacity of the first area of ​​the log entry field 812, the device 500A expands the area of ​​the log entry field 812 within the log entry user interface 810 from the first area to a second area. After typing the desired text and / or adding content items from suggestion moment 816a and / or using icons 814a-814e to the log entry field 812, the user can save the log entry (e.g., save the content in the log entry field) by selecting the enable display 820.

[0315] exist Figure 8E In this scenario, the user selects a moment icon 814a (e.g., by tapping moment icon 814a), and device 500A responds by displaying moments 816b and 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 in moments 816b and 816c (respectively) and / or in the log entry field 812 as representations of content items 818f-818j and 818k (e.g., thumbnails, excerpts, titles, or other representations) rather than the content items themselves.

[0316] Users can optionally select a moment (e.g., moment 816a or 816b) to add that moment (e.g., optionally including metadata) and / or the content items of that moment to a log entry. For example, in response to detecting that a user has selected... Figure 8E In the moment 816b, device 500A displays representations of content items 818f-818j of moment 816b in a separate area 817 of user interface 810 (e.g., a content entry area) (such as above log entry field 812) to indicate to the user that the user has selected moment 816a for (potentially) inclusion in a log entry. Optionally, user interface 810 displays content items 818f-818j that have options (e.g., enable indicators, check boxes, or other types of options) to individually remove one or more of the selected content items, such that the selected content items are not added to the log entry. Optionally, in response to detecting a selection of moment 816b, computer system stops displaying moment 816b in its original location (e.g., below log entry field 812 and / or below icons 814a-814e).

[0317] exist Figure 8FIn the example, the user has indicated not to add content items 818g, 818i, and 818j to the log entry (e.g., exclude them from the log entry) by checking the boxes displayed along with content items 818g, 818i, and 818j. After the user has (optionally) indicated the content items to be removed, the user can provide input to add the remaining content items to the log entry field 812, such as by tapping on the area 817 displaying content items 818f-818j or by tapping in the log entry field 812. In response to detecting user input, device 500A stops displaying content items 818f-818j above the log entry field 812 in area 817, and displays content items 818f and 818h (or a representation of content items 818f and 818h) in the log entry field 812 (e.g., to be added to the log entry), as shown. Figure 8G As shown. Then, the user can (optionally) type text in log entry field 812, such as... Figure 8G As shown, log entries, including content items 818f and 818h and any typed text, are saved by selecting the power indicator 820. In some implementations, the user can delete content items from the log entry field 812 before saving the log entry, such as by selecting the content item to be deleted and providing a delete input.

[0318] In some implementations, users can select a date for a log entry that is the same as or different from the date the log entry was created. For example, such as Figure 8HAs shown, when a user begins creating a log entry, device 500A optionally displays a default date 822. The default date 822 is optionally today's date, the date associated with the 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 the logging application). In response to detecting a selection of the default date 822 (such as a tap on date 822), device 500A displays a date option menu 824, which optionally includes one or more of today's date 824a, moment date 824b (e.g., the date associated with the moment added to the log entry, such as the date the user takes a hike corresponding to that moment), photo date 824c (e.g., the date associated with the photo added to the log entry, such as the date device 500A takes the photo), and custom date 824d (e.g., the date selected by the user). In response to detecting a user's selection of one of date options 824a-824d, the device updates the default date 822 to the selected date, which is then saved as the date of the log entry. In some implementations, 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 a moment and / or photo 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 implementations, menu 824 always includes a custom date 824d to allow the user to select their own date for the log entry.

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

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

[0321] exist Figure 8H In the user interface 810, the user selects the camera icon 814b. In response to detecting the selection of the camera icon 814b, in... Figure 8J In this context, device 500A displays a camera interface 828 in an area of ​​user interface 810 (e.g., below log entry field 812). This camera interface has a preview pane 832 for displaying a live view from device 500A's camera and a virtual button 830 for capturing new photos or videos, optionally along with other optional options such as video options, flash options, zoom options, or other options. Camera interface 828 is optionally displayed within the user interface of the logging application. In response to detecting activation of the virtual button 830, device 500A uses its camera to capture a new photo 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 below. Figure 8K As shown. In some embodiments, in response to detecting activation of the virtual button 830 and after capturing a new photo, device 500A requests confirmation from the user before adding the new photo 834 to the log entry field 812. In some embodiments, when the new photo 834 is added to the log entry field 812 (automatically or in response to user confirmation of adding the new photo 834 to the log entry field 812), device 500A stops displaying the camera interface 828 and optionally displays the soft keyboard 821 so that the user can add text to the log entry field 812 (e.g., in addition to the new photo 834).

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

[0323] Figure 8L and Figure 8M An example is shown of using an audio capture application (such as a voice memo application or another audio capture application) to capture a new audio record and add that new audio record to a log entry.

[0324] exist Figure 8HIn the user interface 810, the user selects the audio clip icon 814d. In response to detecting the selection of the audio clip icon 814d, in... Figure 8L In this configuration, device 500A displays a virtual button 838 for capturing new audio recordings in an area of ​​user interface 810 (e.g., below log entry field 812) to audio capture interface 836, optionally along with other optional options such as recording volume. Audio capture interface 836 is optionally displayed in the user interface of the logging application. In response to the detection of the virtual button 838 (such as...), Figure 8L Upon first activation (as shown), device 500A begins using its microphone to capture new audio clips (e.g., ...). Figure 8L (as shown in the "New Record" section). Optionally, the device 500A displays an indication of dynamic elapsed time and / or the volume or spectral content of the audio record while recording audio. In response to detecting a second activation of the virtual button 838, the device 500A stops recording audio and optionally automatically (e.g., without additional user input) adds a new audio record (e.g., new audio record 840) to the log entry field 812, as shown. Figure 8M As shown. In some embodiments, a new audio recording 840 may be played back and / or deleted after it is added to the log entry field 812. In some embodiments, in response to detecting a second activation of the virtual button 838 and after capturing a new audio recording, 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 may be played back from the audio capture interface 836 (e.g., before being added to the log entry field 812). In some embodiments, when a new audio recording 840 is added to the log entry field 812 (automatically or in response to user confirmation of adding the new audio recording 840 to the log entry field 812), device 500A stops displaying the audio capture interface 836 and optionally displays the soft keyboard 821 so that the user can add text to the log entry field 812 (e.g., in addition to the new audio recording 840).

[0325] Figure 8N An example of a timeline user interface 842 for a logging application is depicted. Optionally, the timeline user interface 842 is displayed in response to selecting the logging application icon 655 from the user interface 602 and / or in response to selecting a display representation 820 in the log entry user interface 810. The timeline user interface 842 displays a timeline of log entry representations 844a-844c, such as those used in... Figures 8A to 8LThe log entry representation created by the techniques described herein. The log entry representation shown in timeline 842 optionally provides a preview of the corresponding log entry by including a representation of the content items and / or text included in the corresponding log entry, as depicted in log entry representations 844a-844c. Figure 8N As shown, log entries may include a combination of content items and text (e.g., log entry 844a), content items only (e.g., log entry 844b), or text only (e.g., log entry 844c). Optionally, a log entry representation corresponding to a log entry that includes a longer text entry may include a subset of the text of the log entry. For example, a log entry representation may optionally include 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 log entries may optionally include photos, videos, maps, fitness activities, podcasts (e.g., the podcast itself, a portion of the podcast, a link to the podcast, artwork associated with the podcast), text messages, books or articles (e.g., the book or article itself, a portion of the book or article, a link to the book or article, artwork associated with the book or article), or other types of content. In some embodiments, each log entry indicating 844a-844c is displayed together with an associated date (e.g., the date associated with the log entry).

[0326] 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 are shown on a single screen, the user can scroll down to view additional log entry representations.

[0327] The timeline user interface 842 optionally includes a playback capability display 848, which, when selected, causes the device 500A to display a playback selection interface in the timeline user interface 842, as referenced. Figure 8O As described.

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

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

[0330] The timeline user interface 842 optionally includes a momentary power indicator 850, which, when selected, causes the device 500A to display the momentary user interface, as referenced. Figure 8S As described.

[0331] Figure 8O An example of displaying a playback selection interface 852 in a timeline user interface 842 is shown. In some embodiments, in response to detecting a playback enablement display 848 in the timeline user interface 842... Figure 8N (As shown in the diagram) the device 500A displays a review selection interface 852, optionally at the top of the timeline user interface 842, such as... Figure 8OAs shown in the diagram. The playback selection interface 852 includes one or more playback panes, which have representations of one or more types of playback (e.g., birthday, on this day, important days, highlighted time period). In some embodiments, playback includes collages, slideshows, animated videos, or other forms of visual (and optionally, auditory) presentations generated by device 500A based on one or more previously created log entries (e.g., including content items and / or text in one or more log entries) associated with a specific date or event. For example, a birthday playback optionally includes log entries with dates associated with the user's (or someone else's) birthday. A "on this day" playback optionally includes one or more log entries with the same month and date as the current date. An "important day" playback optionally includes one or more log entries with dates determined by device 500A or by the user to be important, such as the date the user gets married or starts a new job. A "highlighted time period" playback includes one or more log entries whose dates have been determined by device 500A or by the user to be associated with a specific time period or multi-day event of potential interest (such as "autumn in Sweden"). The "Media Focus" playback includes one or more log entries whose dates have been determined by device 500A or the user to be associated with a specific time period or multi-day event, and includes (or references) music and / or video played during that time period or event. In some implementations, the playback has a reference... Figure 6V And / or one or more of the characteristics of the animated video presentation 679 described in method 700.

[0332] exist Figure 8O In the example, the playback selection interface 852 includes a first playback pane 852a associated with “birthday” playback and a second playback pane 856b associated with “on this day” playback. In some implementations, the playback selection interface 852 can be scrolled horizontally to navigate to additional playback panes, such as playback panes associated with important day playback and / or highlighted time period playback.

[0333] In some implementations, the playback panes 852a-852b are selectable to cause device 500A to display a full-screen representation of an optional playback type of the selected playback, where each playback option is associated with a specific playback. For example, in response to detecting a selection of playback pane 856a, device 500A optionally displays one or more birthday playback representations 857a-857c, each birthday playback representation associated with a “birthday” playback. The user can select a specific playback option to display the associated birthday playback (e.g., play an animated video or display a collage).

[0334] In some examples, in response to Figure 8OIn the playback selection interface 843, the selection of the power indicator 854 is detected, and the device 500A displays as follows: Figure 8P The playback interface 858 is shown. Playback interface 858 optionally displays playback representations 860a-860e associated with representative playbacks of different types of playback, and optionally displays the playback quantity associated with different types of playback. Figure 8P In the example, there are four "Important Day" replays, two "On This Day" replays, three "Birthday" replays, one "Highlighted Time Period" replay, and three "Media Focus" replays. In some implementations, the replay representation 860a-860e includes content items (or representations of content items) and / or text associated with the representative replay.

[0335] In some implementation schemes, Figure 8P The playback options 860a-860d can optionally be scrolled horizontally to display additional playback options of the same playback type. For example, the horizontal scrolling playback option 860a can optionally display one or more additional "birthday" playback options for the corresponding playback.

[0336] In some implementations, "replay" means that 860a-860d can be selected to cause device 500A to display a corresponding representative replay, such as when a single replay associated with the selected type exists. In some implementations, "replay" means that 860a-860d can be selected to cause device 500A to display additional replays (including representative replays) of the same replay type, such as when multiple replays associated with the selected type exist. For example, in response to detection... Figure 8P The option for playback in the middle represents the selection of 860b (corresponding to the "On This Day" playback type, which is in...) Figure 8P In the example with two associated replays, device 500A optionally displays a replay type user interface 862 with replay representations 860b and 860e associated with the "On This Day" replay, such as Figure 8Q As shown.

[0337] Return to Figure 8N And the timeline user interface 842, as previously discussed, in some embodiments, represents moments and / or content items (e.g., Figure 8N The representations of content items 818f and 818h shown can be selected so that device 500A displays the corresponding content item (or representation of the content item) in a full-screen interface, optionally having the ability to navigate between different content items at that instant by swiping left / right. For example, in response to detecting... Figure 8MIn the selection of content item representation 818h (which is optionally a representation of a song, such as the song title, the cover art associated with the song, or another type of representation), device 500A optionally displays content user interface 864, such as... Figure 8R As shown.

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

[0339] The content user interface 864 optionally includes an editable display 868, which, when selected, allows the user to edit a content item included in a log entry and represented by a content item display 866. Additionally or alternatively, selection of the editable display 868 allows the user to edit the log entry including the content item, such as adding text to the log entry (optionally associated with the content item).

[0340] In some implementations, if the content item represented by content item representation 866 is playable (e.g., it is a video, 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 implementations, if the content item represented by content item representation 866 is playable, content user interface 864 includes a playback enable representation 870, which, when selected, causes the content item represented by content item representation 866 to be played while remaining within content user interface 864 (e.g., in...). Figure 8R In the example, by playing song 1). In some implementations, if a content item is not playable, such as if the content item is a photo or map, the content user interface 864 abandons displaying the playback capability representation 870.

[0341] In some implementations, the content user interface 864 includes an application icon (and / or button) 872, which, 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 (such as...) Figure 8RAs shown), selecting application icon 872 optionally causes device 500A to launch the music playback 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 photo editing applications, voice memo applications, text messaging applications, or fitness applications, which may similarly be launched by device 500A in response to detecting the selection of application icon 872. For example, if a content item in the log entry is part of a text messaging conversation, the content user interface 864 optionally reproduces the portion of the text messaging 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 user input) to the portion of the conversation included in the log entry.

[0342] Return to Figure 8N With the timeline user interface 842, as previously discussed, in some embodiments, the instantaneous power indicator 850 can be selected to enable the device 500A to display... Figure 8S The instantaneous user interface shown.

[0343] The instant user interface 874 includes one or more instants 876a-876c, each instant optionally associated with an instant 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, device 500A generates instants 876a-876c based on analysis of content items stored and / or accessible on device 500A, such as by identifying content items associated with specific dates or events that the user may be interested in. In some embodiments, the instants 876a-876c displayed in the instant user interface 874 are instants that have not been previously logged by the user (e.g., not included in log entries in a logging application) and are provided to prompt the user to select instants to be logged (e.g., included in log entries).

[0344] exist Figure 8S In the example, the instant user interface 874 includes icons or buttons 886a-886d that can be selected to allow device 500A to select (e.g., filter) which instants and / or prompts are presented in the instant user interface 874. For example, in response to the selection of icon 886a (such as... Figure 8SAs shown), device 500A may display moments recommended by device 500A based on analysis of the user's previous activities or indications of interest. For example, in response to the selection of icon 886b, device 500A displays moments associated with a recent date, such as the last day, week, month, or year. For example, in response to the selection of icon 886c, device 500A may optionally display one or more text prompts to encourage the user to create a log entry and provide a topic. An example of such a prompt is "What are you grateful for today?" For example, in response to the selection of icon 886d, device 500A may optionally display 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 the detection of a selection of the displayed moment, prompt, or representation of a media item in user interface 874, device 500A may optionally display log entry user interface 810, where the selected moment, prompt, or media item is displayed above log entry field 812 (e.g., as shown in the image). Figure 8F (as shown) or in log entry field 812 (for example, as shown) Figure 8G (As shown), this provides users with a simple way to log the selected items.

[0345] In some implementations, in response to detecting a selection of moments 876a-876c, device 500A displays a menu allowing the user to create log entries that include that moment and / or its content items, such as... Figure 8T As shown.

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

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

[0348] In some implementations, in response to detecting a selection of option 884b, device 500a displays a log entry user interface 810, where the selected moment and / or content item representation 880a-880b is displayed in log entry field 812 (e.g., in a format similar to...). Figure 8G (as shown) or above log entry field 812 (for example, in a manner similar to...) Figure 8F (As shown in the diagram). Then, the user can add text, add additional content items, or save log entries, as shown in the reference. Figures 8C to 8L As described.

[0349] In some implementations, users can configure the logging application and / or device 500A to display or provide notifications that remind or encourage users to create or comment on log entries (which may be referred to as "push"). For example, users can access such notifications from a configuration settings menu associated with the logging application. Figure 8U The push-to-display user interface 886 shown is used to configure the logging application to deliver alert notifications according to various criteria.

[0350] The push-to-use user interface 886 optionally includes one or more optional options 888a-888d, which can be selected by the user to cause the device 500A to display a notification associated with option 888a-888d. Such notifications are optionally displayed in a manner similar to, for example... Figure 6V The visual manner shown and / or described in reference method 700 is as follows.

[0351] In some implementations, selecting option 888a configures device 500A to display scheduled reminder notifications according to a schedule (e.g., a schedule provided by the user or determined by device 500A). For example, selecting option 888a may optionally configure device 500A to display reminder notifications daily, weekly, or monthly at specified times, or to display reminder notifications according to another schedule. In some implementations, device 500A determines at the specified reminder notification time whether one or more criteria indicative of whether the user might expect to receive a reminder notification at the scheduled time are met. For example, device 500A may optionally determine whether device 500A is operating in notification suppression mode, or whether a calendar application on device 500A indicates that the user is in a meeting, or a phone application indicates that the user is making a call. Optionally, device 500A may temporarily or permanently suppress reminder notifications based on the determination that one or more criteria are met, and optionally provide notifications after one or more criteria are no longer met.

[0352] In some implementations, such alert notifications optionally include saved instant notifications, review notifications, and / or system instant notifications, as described in more detail below. Pre-defined alert notifications optionally include prompts for creating log entries and / or suggested topics for the log entries. In some implementations, in response to detecting a selection of a pre-defined alert notification, device 500A displays a log entry user interface 810, such as... Figure 8C As shown.

[0353] In some implementations, selecting option 888b configures device 500A to display a saved moment notification associated with a moment that has been saved in a log entry by a user (e.g., using the "Quick Add" feature) but has not yet been written by the user. In some implementations, device 500A displays saved moment notifications associated with a schedule. In some implementations, the saved moment notification includes one or more representations of content items associated with one or more saved moments. In some implementations, in response to detecting a selection of a saved moment notification, device 500a displays a log entry user interface 810, where a representation of the content item associated with the saved moment is displayed in log entry field 812 (e.g., in a format similar to...). Figure 8G (As shown in the diagram). Then, the user can add text, add additional content items, or save log entries, as shown in the reference. Figures 8C to 8M As described.

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

[0355] In some embodiments, selecting option 888d configures device 500A to display a system instant notification associated with a new instant generated, identified, and / or saved by device 500 and not yet added to a log entry by the user. In some embodiments, device 500A displays the system instant notification according to a schedule and / or when device 500A generates, identifies, and / or saves one or more new instants. In some embodiments, the system instant notification includes one or more representations of related content items (e.g., content items with the same date, location, or other relevance indication). In some embodiments, in response to detecting a selection of a system instant notification, device 500A displays an instant user interface including the system instant (e.g., ...). Figure 8T The instantaneous user interface 874). In some embodiments, in response to detecting a selection of a system instantaneous notification, device 500a displays a log entry user interface 810, wherein content items associated with the system instantaneous notification are displayed in log entry field 812 (e.g., in a manner similar to...). Figure 8G (as shown) or above log entry field 812 (for example, in a manner similar to...) Figure 8F (As shown in the diagram). Then, the user can add text, add additional content items, or save log entries, as shown in the reference. Figures 8C to 8M As described.

[0356] In some implementations, as an alternative and / or supplement to being displayed as a notification, device 500A displays an alert (e.g., corresponding to the notification described above) to create and / or comment on log entries in a widget associated with the logging application (or in the form of a widget). For example, in Figure 8V In this embodiment, device 500A displays a prompt in widget 890 of user interface 802 (e.g., the main screen user interface of device 500A) regarding a moment (e.g., a moment of saving or a system moment including content items represented by content item representations 892a and 892b) being logged. Widget 890 includes a prompt regarding logging of that moment. In some embodiments, in response to detecting a selection of widget 890, device 500a displays log entry user interface 810, wherein content item representations 892a-892b are displayed in log entry field 812 (e.g., in a manner similar to...). Figure 8G (as shown) or above log entry field 812 (for example, in a manner similar to...) Figure 8F (As shown in the diagram). Then, the user can add text, add additional content items, or save log entries, as shown in the reference. Figures 8C to 8M As described.

[0357] In some implementations, if device 500A identifies a saved instant notification, a playback notification, and / or a system instant notification within a predetermined time period of a scheduled reminder notification, device 500A waits to display the saved instant notification, playback notification, and / or system instant notification until the scheduled reminder time. For example, if device 500A is configured to provide scheduled reminder notifications, device 500A may optionally batch the notifications to be displayed at the scheduled reminder time.

[0358] Figure 9 It is shown according to such Figures 8A to 8V The flowcharts of some implementations of method 900 for logging user interface are shown. Method 900 is optionally performed at an electronic device (such as device 100, device 300, or device 500), as referenced above. Figures 1A to 1B , Figures 2 to 3 , Figures 4A to 4B as well as Figures 5A to 5H The operations in method 900 may be optionally combined, and / or the order of some operations may be optionally changed.

[0359] In some embodiments, method 900 is performed at an electronic device that communicates with a display generating 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 the following: a mouse (e.g., external), a touchpad (optionally integrated or external), a remote control device (e.g., external), another mobile device (e.g., separate from the electronic device), a handheld device (e.g., external), and / or a controller (e.g., external), etc. In some embodiments, the display generating component is a display integrated with the electronic device (optionally a touchscreen display), an external display such as a monitor, projector, television, or a hardware component (optionally integrated or external) for projecting a user interface or making the user interface visible to one or more users, etc. In some embodiments, the eye-tracking device is a camera and / or motion sensor capable of determining the direction and / or position of the user's gaze. In some implementations, method 900 is performed at or by a vehicle (e.g., at the infotainment system of a vehicle having or communicating with one or more display generating components and / or input devices).

[0360] In some embodiments, the electronic device displays (902a) a first user interface (e.g., via a display generating component). Figure 8C or Figure 8E The first user interface (810) includes logging for typing content into the logging application (e.g., ...). Figure 8M The log entry represents the log entry field in 844a) (e.g., Figure 8E Log entry field 812) and a list of suggested content items (e.g., content items 818f-818j) to be included in the log entry (e.g., Figure 8E (816b) where suggested items in the suggested items list are included in the suggested items list based at least in part on data detected by an application other than the logging application (such as the date of the item, the location of the item, the person associated with the item, the event associated with the item, or other types of data).

[0361] For example, (e.g., by an electronic device) content items 818f-818j are selected for inclusion in moment 816b because they are associated with the same date, which is detected by an application associated with the content item (e.g., a photo capture application, a map-making application, or another type of application). In some embodiments, the suggested content item list includes graphical and / or textual representations of one or more content items, such as photo or video thumbnails, map thumbnails, song or book titles, message excerpts (e.g., text messages or email messages), event titles, dates, names of people, representations of audio signals, or another type of representation of the content item. In some embodiments, the suggested content item list is displayed within visual boundaries (e.g., within rectangular, elliptical, circular, or other types of boundaries) to indicate that a content item is part of the suggested content item list. In some embodiments, the suggested content item list includes and / or is displayed with the date associated with the suggested content item list, such as with... Figure 8E The date “December 7, 2022” is associated with and displayed as part of moment 816b. For example, this date may optionally be the date on which one or more content items occur, are captured, are shared (e.g., to or by a user of an electronic device) and / or are otherwise associated with the content item.

[0362] In some implementations, a list of suggested content items (such as...) is displayed, which is intended to be included in log entries in the logging application. Figure 8E When a suggestion is made to the first user interface (816b and 816c), the electronic device receives (902b) input via one or more input devices pointing to a list of suggested content to be included in a log entry of the logging application, such as touch input, button input, voice input, or selection. Figure 8E Another type of input is suggested moments in 816b. For example, a user may optionally select a moment to include by touching any part of the moment (e.g., on a touchscreen), by tapping the moment, by verbally selecting the moment (e.g., by saying "Select a moment associated with December 7, 2022"), by providing an empty gesture pointing to the moment (e.g., an empty pinch gesture), and / or by directing their attention to the moment (e.g., 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).

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

[0364] In some implementations, the electronic device simultaneously displays, via a display generation component, a first user interface including a log entry field and a list of suggested content items for inclusion in log entries of a logging application, such as... Figure 8E The recommendations in the document are instantaneous 816b and 816c; and the navigation user interface, which includes multiple optional user interface elements (e.g., including...). Figure 8C The navigation user interface (icons 814b to 814e) allows the multiple optional user interface elements to be selected to initiate the electronic device to abandon display (e.g., stop display or not display) of the list of suggested content items to be included in the log entries of the logging application (e.g., stop display) via the display generation component. Figure 8E The recommendations in 816b and 816c) and the process of displaying content of the appropriate type for inclusion in log entries of a logging application via a display generation component, without displaying content of a different type. For example, when displaying... Figure 8E The suggestion in the middle is to instantly 816b and 816c Figure 8E When the user interface 810 is active, the electronic device receives the selection. Figure 8E The input of the photo icon 814c, and in response, displays such as Figure 8I The thumbnails of the user's photos shown (e.g., below log entry field 812) optionally stop displaying moments 816b and 816c. For example, in displaying moments including... Figure 8E The suggestion in the middle is to instantly 816b and 816c Figure 8E When the user interface 810 is active, the electronic device receives the selection. Figure 8E The camera icon 814b is input. In response to detecting a selection of the camera icon 814b, the electronic device stops displaying. Figure 8E The recommendations in the text are instantaneous for 816b and 816c, and as... Figure 8J The illustrated camera interface 828 has a preview pane 832 for displaying a live view from the device's camera and includes a virtual button 830 for capturing photos or videos for inclusion in a log entry field 812. In some embodiments, in response to detecting a selection of one of the optional user interface elements (e.g., icons 814a-814e), the electronic device stops displaying the keyboard (e.g., ...). Figure 8F The keyboard (821) and / or the keyboard display is replaced with the display of content of the corresponding type.

[0365] In some implementations, in response to receiving input pointing to a list of suggested content items for inclusion in log entries in a logging application, the device displays a keyboard for typing keyboard content into a log entry field in a second user interface, while simultaneously displaying representations of the suggested content items in the content entry area, such as... Figure 8F As shown, it is suggested that 816b be displayed in the content entry area 817 at the same time, while the keyboard 821 is displayed simultaneously.

[0366] In some implementations, the first proposed content item includes a first content item and a second content item, such as Figure 8F Content items 818f and 818g are included. In some implementations, the first and second content items are associated with an application different from the logging application (e.g., captured by and / or accessed via that application), such as... Figure 8F Content items 818f and 818g are photos (e.g., associated with photos different from the logging application), or the first content item is associated with an application different from the logging application and the second content item is associated with a second application different from the first application, such as... Figure 8F Item 818f in the content is a photo captured by a photo application, and Figure 8F Content item 818g is music (e.g., a song) associated with a music application. In some embodiments, displaying a representation 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, together with other content items from the same instant, such as content items 818h, 818i, and 818j), such as in the content entry area 817 of the user interface 810. Figure 8F The representations of content items 818f and 818g are as shown in the reference above. Figure 8F As described. In some implementations, after displaying representations of a first content item and a second content item in the content entry area, a second input requesting the removal of the first content item from the content entry area (e.g., to exclude the first content item from being added to a log entry field) is detected via one or more input devices, such as a selection. Figure 8FThe content item 818g is provided with an input for removal, as indicated by the checkbox in the content item 818g. In some embodiments, in response to detecting a second input requesting the removal of a first content item from the content entry area, the device stops displaying a representation of the first content item in the content entry area without stopping displaying (e.g., while maintaining) a representation of the second content item. For example, the user may optionally remove some or all content items from the content entry area before adding the (remaining) content items in the content entry area to a log entry.

[0367] In some implementations, after detecting a second input requesting the removal of a first content item from the content entry area, the electronic device detects user input corresponding to a request to add a content item from the content entry area to a log entry field (e.g., such as in...). Figure 8F A tap on the content entry area 817 (optionally after removing some content items from the content entry area 817), and in response to detecting user input corresponding to a request to add content items to the log entry field, the electronic device displays a representation 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. For example, in Figure 8G In the example, the electronic device detects user input corresponding to a request to add the content item 816b to the log entry field 812, while content items 818g, 818i, and 818 are marked as excluded (or optionally removed from the content entry area 817). In response to detecting user input corresponding to a request to add the moment 816b to the log entry field 812, the electronic device displays representations of content items 818f and 818h in the log entry field 812, as shown below. Figure 8H As shown, and optionally stop displaying content items 818f-818j in content entry area 817, and / or stop displaying content entry area 817. In some embodiments, after displaying a representation of a content item in log entry field 812, the electronic device detects a response to a power indication (e.g., Figure 8G The device selects a power indicator (820) and, in response to detecting a selection of a power indicator, saves the content displayed in the log entry field (e.g., text content and / or content items) as a log entry (e.g., saves it to a logging application). Optionally, the device saves log entries locally and / or remotely.

[0368] In some implementations, 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 Content item 818f is (or represents) a photograph and Figure 8E The content item 818g is (or represents) an audio clip.

[0369] In some implementations, before displaying a first user interface that includes a list of suggested content to be included in log entries of a logging application, the electronic device displays optional user interface elements (such as via a display generating component) for displaying the list of suggested content to be included in log entries of a logging application. Figure 8B The user interface 806 displays a power indicator 808d). In some embodiments, before displaying a first user interface including a list of suggested content for inclusion in log entries of a logging application, the electronic device transmits the power indicator via one or more input devices such as by detection. Figure 8B The input directed to an optional user interface element for displaying a list of suggested content to be included in log entries in a logging application is detected by detecting a selection of the power indicator 808d (e.g., by detecting a tap on the power indicator 808d, a click on the power indicator 808d, or another type of input indicating a selection of the power indicator 808d). In some embodiments, in response to detecting input directed to an optional user interface element for displaying a list of suggested content to be included in log entries in a logging application, the electronic device detects input via a display generation component such as a display... Figure 8C The log user interface 810 and suggestion moment 816a are used to display a first user interface that includes a list of suggested content for inclusion in log entries of the logging application.

[0370] In some implementations, the first user interface consumes the first display area based on determining that one or more first criteria are met, such as Figure 8C The suggestion is to instantly expand the display area of ​​the 816a. In some implementations, the first user interface consumes a second display area larger than the first display area based on determining that one or more second criteria are met, such as by... Figure 8E The suggestion in the text is that the display area consumed by the 816b and 816c instantaneously is greater than that. Figure 8C The suggested instantaneous display area of ​​816a. As another example, the device may optionally expand the area consumed by the log entry field 812 (and thus expand the area consumed by the first user interface) based on whether 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).

[0371] In some implementations, when displaying a second list of suggested content items including a second content item (optionally, when the logging user interface is not displayed), the device receives input directed to the second list of suggested content items via one or more input devices (e.g., a touch or tap on the second list of suggested content items, or another type of input). In some implementations, in response to receiving a 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 of adding additional content to the log entry of the logging application. For example, the second list of suggested content items is optionally... Figure 8T The instant 876b, and when one or more first criteria are met, the one or more first criteria optionally include when the electronic device detects a selection. Figure 8T When the first optional option 884a is entered, the electronic device may optionally save the content item in moment 876b to a 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).

[0372] In some implementations, in response to receiving a second input pointing to a second list of suggested content items for inclusion in log entries of a logging application, and based on one or more second criteria that satisfy one or more first criteria, the device displays a representation of the second content item in the content entry area of ​​the log user interface (and optionally initiates the log user interface, if it is not already displayed). For example, the first suggested content may optionally be... Figure 8T The instant 876b, and when one or more second criteria are met (the one or more second criteria optionally include when the electronic device detects selection) Figure 8T When the second optional option 884a is entered (and the criteria are met), the electronic device optionally displays the log user interface 810 (if it is not already displayed) and displays a representation of the content item of moment 876b in the content entry area 817 and / or the log entry field 812 (such as by displaying...). Figure 8G The log entry user interface 810, but in which content items 880a-880b are displayed in log entry fields 812, initiates the process of adding further content (e.g., text or additional content items) to the log entry.

[0373] Figure 10 It is shown according to such Figures 8N to 8R The illustration of some implementations includes a flowchart of a method 1000 for reviewing a user interface. Method 1000 is optionally performed on an electronic device (such as device 100, device 300, or device 500), as referenced above. Figures 1A to 1B , Figures 2 to 3 , Figures 4A to 4B as well as Figures 5A to 5H The operations in method 1000 may be optionally combined, and / or the order of some operations may be optionally changed.

[0374] In some embodiments, method 1000 is performed at an electronic device that communicates with a display generating 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 the following: a mouse (e.g., external), a touchpad (optionally integrated or external), a remote control device (e.g., external), another mobile device (e.g., separate from the electronic device), a handheld device (e.g., external), and / or a controller (e.g., external), etc. In some embodiments, the display generating component is a display integrated with the electronic device (optionally a touchscreen display), an external display such as a monitor, projector, television, or a hardware component (optionally integrated or external) for projecting a user interface or making the user interface visible to one or more users, etc. In some embodiments, the eye-tracking device is a camera and / or motion sensor capable of determining the direction and / or position of the user's gaze. In some implementations, method 1000 is performed at or by a vehicle (e.g., at the infotainment system of a vehicle having or communicating with one or more display generating components and / or input devices).

[0375] In some embodiments, the electronic device displays (1002a) a first user interface of a logging application via a display generation component. This first user interface 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). Figure 8N The log entries in the timeline user interface 842 represent the timeline of 844a-844c, and the first optional user interface elements for displaying one or more replays, such as Figure 8NThe timeline user interface 842 includes a playback capability display 848. In some embodiments, when displaying a first user interface of a logging application, including a list of log entries associated with the user and a first optional user interface element for displaying one or more playbacks, the electronic device receives (1002b) input (e.g., touch, tap, click, or other input) directed to the first optional user interface element via one or more input devices, such as in Figure 8N The timeline user interface 842 selects the input for the playback capability display 848. In some embodiments, in response to receiving input pointing to a first selectable user interface element, the electronic device displays (1002c) a group or more playbacks, such as with... Figure 8O The first view pane 856a associated with a set of “birthday” view panes 857a-857c or the second view pane 856b associated with a “on this day” view pane 857d.

[0376] In some implementations, the group of one or more replays is associated with one or more log entries that meet a criterion 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 month, day, and / or year). For example, in response to detecting... Figure 8P The option to view the image is indicated by the 860b display, allowing the electronic device to selectively display the image. Figure 8Q A playback type user interface 862, which has a playback representation associated with the current month and date (“on this day”).

[0377] In some implementations, the group of one or more replays is associated with one or more log entries that satisfy criteria when the date associated with the one or more log entries is a yearly date, such as having a... Figure 8P The "On This Day" replay is associated with the replay representations 860b and 860e in the replay type user interface 862 and / or includes the replay representation associated with the "Birthday" replay in the replay type user interface.

[0378] In some implementations, the group of one or more replays is associated with one or more log entries that meet criteria when the content type of the log entry is media content. For example, replays represent (such as...) Figure 8P The playback representation 860e is optionally associated with a log entry that is associated (e.g., included or referenced) with music and / or video played by the user during a specific time period (such as during the recent summer). In this example, in response to detecting a selection of the playback representation 860e, the electronic device optionally displays... Figure 8QThe playback type user interface 862, but with a representation of the music and / or video content played by the user during that time period (e.g., the recent summer) and a title associated with that time period, such as "Music of Summer" (instead of "On This Day").

[0379] In some implementations, displaying the set of log entries that meet one or more first criteria via the display generation component includes displaying, via the display generation component, a first set of one or more replays in a first portion, the first set of one or more replays meeting criteria (such as...) when the date associated with one or more log entries corresponding to the first set of one or more replays is a first date or within a first date range. Figure 8P The second part displays a second group of one or more replays that satisfy criteria (such as...) when the time of day associated with one or more log entries corresponding to the second group of one or more replays is the first time of day or within a time range of the first day. Figure 8P The replay in the middle represents 860b); and / or displays a third group of one or more replays in the third part, which satisfies the criteria (such as) when the content type of the log entry corresponding to the third group of one or more replays includes the first type of content. Figure 8P The playback representation in 860e includes, but includes, log entries associated with music and / or video played by the user within a specific time period.

[0380] In some implementations, aspects / operations of methods 700, 900, and / or 1000 may be interchanged, substituted, and / or added between these methods. For example, logging applications of methods 700, 900, and / or 1000 may optionally interchange, substitute, and / or add between these methods. For the sake of brevity, these details will not be repeated here.

[0381] Figures 11A to 11G This section broadly illustrates how, according to some implementation schemes, the content of a suggested list of items can be selectively included in log entries of a logging application.

[0382] Figure 11AAn example of a moment user interface 1102 is illustrated. The moment user interface 1102 includes moments 1106a-1106c, each of which is optionally associated with a moment date (or a range of moment dates) and includes text and / or representations of content items (e.g., content item representations 1108a-1108e, 1110a-1110b, 1112a-1112d). As previously discussed, in some embodiments, device 500A generates moments 1106a-1106c based on analysis of content items stored and / or accessible on device 500A, such as by identifying content items associated with specific dates or events that the user may be interested in. In some embodiments, moments 1106a-1106c displayed in the moment user interface 1102 are moments that have not previously been logged by the user (e.g., not included in log entries in a logging application) and are provided to prompt the user to select moments to be logged (e.g., included in log entries). Optionally, 1106a-1106c is a corresponding list of suggested content items. In some implementations, Figure 11A The number of content items included in the corresponding instant is greater than Figure 11A The number of content items represented in the corresponding instant. For example, instant 1106a is optionally associated with fourteen content items, but... Figure 11A In the middle, instant 1106a includes five content items representing 1108a-1108e.

[0383] exist Figure 11A In the instant user interface 1102, optional options 1104a and 1104b are included, each of which is optionally optional to allow device 500A to select (e.g., filter) which instants and / or prompts to be presented in the instant user interface 1102. For example, in response to the selection of optional option 1104a (in Figure 11A (As shown in the diagram as selected), device 500A optionally displays moments recommended by device 500A, such as based on analysis of the user's previous activities or indications of interest. In response to the selection of optional option 1104b, device 500A optionally displays moments associated with a recent date (such as the last day, week, month, or year). In some embodiments, the moment user interface 1102 includes additional optional options, such as... Figure 8S Icons 886c and 866d. In some implementations, Figure 11A The instant user interface 1102 includes Figure 11A Optional options 1104a and 1104b, but not including Figure 8S The icons 886c and 866d, such as Figure 11A As shown.

[0384] exist Figure 11A In the context of the moment, 1106a-1106c respectively include optional options 1102a-1104c, each of which is optionally selectable such that device 500A displays a user interface for a log entry including the content item corresponding to the selected optional option for the corresponding moment, such as... Figure 8F The log entry user interface 810. For example, in response to the selection of optional option 1114a, device 500A optionally displays... Figure 8G or Figure 8F The log entry user interface 810, but the content items of the selected moment 1106a (e.g., all content items of the selected moment 1106a, which optionally exceed) Figure 11A The content item (representing the number of items 1108a-1178e) is displayed in log entry field 812 (e.g., in a format similar to...). Figure 8G (as shown) or displayed above log entry field 812 (e.g., in a manner similar to...) Figure 8F (As shown). Then, the user can add text, add additional content items, or save log entries, such as references. Figures 8C to 8M As described.

[0385] exist Figure 11A In each of moments 1106a-1106c, optionally, an editing user interface is displayed for editing which content items of the corresponding moment will be included in the log entry or saved to the log from the corresponding moment. For example, in response to receiving (e.g., via...) Figure 11A Contact 1103a) Select instant 1106a (e.g., in) Figure 11A (In the instant 1106a, which is outside the area of ​​optional option 1102a), device 500A optionally displays... Figure 11B The editing user interface 1140. Figure 11A The editing user interface 1140 is used to selectively include the content of a list of suggested content items in the log entries of the instantaneous 1106a logging application.

[0386] and Figure 11A Compared to the visual display (e.g., visual indication) of instant 1106a in the instant user interface 1102, Figure 11B The editing user interface 1140 is optionally a more detailed view of moment 1106a, as further described below. For example, the editing user interface 1140 is more descriptive of moment 1106a because, in addition to other features described below, the editing user interface includes content items of moment 1106a organized by type of content item.

[0387] Figure 11BThe editing user interface 1140 includes a description 1118 of the event corresponding to moment 1106a (“Travel to Rocky Palms on Thursday”). Figure 11B The editing user interface 1140 also includes text content 1120, which indicates the corresponding amount of content items of the corresponding type included in moment 1106a. For example, text content 1120 indicates that moment 1106a includes three locations, four photos, one video, one person, and five songs.

[0388] Figure 11B The editing user interface 1140 includes user interface elements 1122a-1122e. In addition to visually indicating data (e.g., metadata) related to the corresponding content item corresponding to the corresponding user interface element, user interface elements 1122a-1122e also visually indicate the content of the corresponding type corresponding to the corresponding user interface element 1122a-1122e. For example, user interface element 1122a visually indicates that moment 1106a includes three locations, and further indicates the name of the location itself; user interface element 1122b visually indicates that moment 1106a includes four photos, and further indicates the corresponding date associated with the four photos; user interface element 1122c visually indicates that moment 1106a includes a video, and further indicates the date and location corresponding to the capture of the video; user interface element 1122d visually indicates that moment 1106a includes a person (e.g., a tagged person), and further indicates the name of this person; user interface element 1122e visually indicates that moment 1106a includes five songs, and further indicates the artist and song title associated with these songs.

[0389] Figure 11B The user interface elements 1122a-1122e each include optional options 1126a-1126e, which are used to globally select or deselect content of the corresponding type (corresponding to user interface elements 1122a-1122e) from the log entries corresponding to moment 1106a. Figure 11B In this context, optional options 1126a-1126e each occupy a state corresponding to the globally selected content of the corresponding type in the log entry for moment 1106a. Therefore, according to... Figure 11BIn the implementation scheme, optional option 1126a is optionally selected to exclude location content items from the log entry corresponding to moment 1106a; optional option 1126b is optionally selected to exclude photo content items from the log entry corresponding to moment 1106a; optional option 1126c is optionally selected to exclude video content items from the log entry corresponding to moment 1106a; optional option 1126d is optionally selected to exclude people content items from the log entry corresponding to moment 1106a; and optional option 1126e is optionally selected to exclude media content items from the log entry corresponding to moment 1106a. If the corresponding optional option 1126a-1126e is in a deselected state, the corresponding optional option 1126a-1126e can be selected to enter a selection state, in which optionally, all content items of the corresponding type corresponding to the corresponding optional option 1126a-1126e are selected for inclusion. In some implementations, the corresponding optional options 1126a-1126e in the deselected state have a first visual appearance (e.g., excluding checkmarks), and the corresponding optional options 1126a-1126e in the selected state have a second visual appearance that differs from the first visual appearance (e.g., including checkmarks), to provide the user with a visual distinction between which content item types will be included in the log entries and which content item types will not be included in the log entries.

[0390] It should be noted that in some implementations, when the electronic device responds to the detection Figure 11A Contact 1103a and display Figure 11B When the user interface 1140 is edited, all content items and / or all content item types are in a selected state (e.g., no further user input). In some implementations, when the electronic device responds to detecting... Figure 11A Contact 1103a and display Figure 11B When editing the user interface 1140, all content items and / or all content item types are deselected (e.g., no further user input).

[0391] Figure 11B The user interface elements 1122a-1122e include optional options 1128a-1128e, each of which is selectable for viewing and / or further selectively including content items corresponding to the corresponding type of content item in the log entry of moment 1106a based on each content item of the corresponding type. For example, in response to detecting via Figure 11C Contact 1103b and select optional option 1128b, device 500A can optionally display Figure 11D The editing user interface 1140.

[0392] Figure 11D The editing user interface 1140 includes a list of photo content items associated with moment 1106a (e.g., four photos of moment 1106a), from which the user can select or deselect which photos they wish to include in the log entries of moment 1106a. Figure 11D In the image, user interface elements 1130a-1130d display a list of photo content items, as user interface elements 1130a-1130d respectively include photo content 1131a-1121d. The corresponding user interface elements 1130a-1130d include details about the corresponding photo (e.g., the date and location corresponding to the photo's capture) and corresponding optional options 1132a-1132d for including or excluding the corresponding photo from the log entry for moment 1176a. Figure 11D In this context, user interface elements 1132a-1132d are optionally each in a state corresponding to the corresponding photograph included in the log entry corresponding to moment 1176a. Figure 11D In this context, each user interface element in user interface elements 1132a-1132d may optionally change its visual appearance based on whether it is selected, as discussed with reference to user interface elements 1126a-1126e. Figure 11D In this context, optional option 1128b is optionally selectable to remove user interface elements 1132a-1132d (e.g., return to...). Figure 11B The editing user interface 1140). For example, in response to detecting a selection (e.g., via... Figure 11E Contact 1103c), device 500A optionally displays Figure 11B The editing user interface 1140.

[0393] In some implementations, when a user selects or deselects a specific content item type (e.g., from...), Figure 11C User interface elements 1126a-1126e) or user interface elements corresponding to the selection or deselection of specific content items within a specific content type (e.g., Figure 11C When the user interface elements 1132a-1132d are used, by Figure 11B or Figure 11C The text content 1120 indicated by the editing user interface 1140 is updated in real time. For example, by Figure 11BThe text content 1120 indicated by the edit user interface 1140 indicates a date range of August 17, 2023 to August 20, 2023 corresponding to “Thursday trip to Rocky Palms”, and in response to detecting that a content item including (e.g., as metadata) the date August 17, 2023 is not currently selected due to user selection and that the currently selected content item includes (e.g., as metadata) the date August 17, 2023 to August 19, 2023, the device 500A optionally updates the visually indicated date range to indicate the date August 17, 2023 to August 19, 2023, instead of visually indicating the date range August 17, 2023 to August 20, 2023 for the log entry corresponding to moment 1106a. In some embodiments, the amount of content of the corresponding type visually indicated by the device 500A is updated based on user selection. For example, in response to user exclusion... Figure 11D In the editing user interface 1140, two of the four photos are displayed, and the device 500A can optionally update the other two photos besides the one shown. Figure 11D In addition to visually indicating the number of photos in user interface element 1122b, the editing user interface 1140 optionally updates... Figure 11D The editing user interface 1140 visually indicates the number of photos in the text content 1120 (e.g., description) to visually indicate two photos instead of four photos.

[0394] Return to Figure 11B The user interface 1140 includes user interface element 1124a and user interface element 1124b. (As shown in the figure) Figures 11B to 11G The user interface also includes user interface elements 1124a and 1124b. User interface element 1124a is optionally optional to allow device 500A to display a log entry field including the content of moment 1106a, the content of which is based on user selection (e.g., Figure 11B or Figure 11D The user interface element 1124b is optionally selected to allow the device 500A to save (e.g., save for later logging) based on the user's selection (e.g., ...). Figure 11B or Figure 11D The content of moment 1106a is selected for inclusion (as per the selection in the text), excluding the content entry area and / or log entry field. In some embodiments, user interface element 1124a and user interface element 1124b are respectively as relative to... Figure 8T As described in optional options 884b and 884a.

[0395] Figure 11BThe editing user interface 1140 includes optional options 1114 and optional options 1116a. In some cases, the user may wish to deselect items used for logging or added to the log from moment 1106a. In response to detecting a selection of optional option 1114 (e.g., via...), Figure 11F Contact 1103d), device 500A can be optionally displayed Figure 11A The instantaneous user interface 1102. In some cases, the user may wish to view the content of instant 1106a, or may wish to select the content of instant 1106a in another view. In response to detecting a selection of optional option 1116a (e.g., via contact 1103d), device 500A optionally displays Figure 11G The editing user interface 1142.

[0396] Figure 11G The editing user interface 1142 includes a horizontally scrollable view of the content items of moment 1106a. In the horizontally scrollable view, device 500A displays the content of moment 1106a with horizontal scrolling capability, allowing the user to optionally scroll horizontally (e.g., touch the content of moment 1106a and move horizontally) to view the content of moment 1106a and select or deselect from the content of that moment for inclusion in a log entry. Figure 11G The editing user interface 1142 includes a navigation pane 1152 for notifying the user of the position during scrolling. Figure 11G The editing user interface includes photo content 1131c, metadata 1150 of photo content 1131c (e.g., the location, date, and time of capture of photo content 1131c), and optional options 1132c for selecting or deselecting photo content 1131c for inclusion in or exclusion from log entries. Figure 11G The editing user interface 1142 optionally groups corresponding content items of the corresponding content item type in horizontal scrolling. For example, in Figure 11G In the editing user interface 1142, the four photos of moment 1106a are optionally adjacent to each other in horizontal scrolling, the three positions of moment 1106a are optionally adjacent to each other, and the five songs are optionally adjacent to each other. Figure 11G In the editing user interface 1142, there is an optional option 1132c for selecting or deselecting content items to be included in or excluded from log entries. Figure 11G In the example example, the edit user interface 1142 does not include any of the optional options 1126a-1126e. The user can return to the previous screen by selecting optional option 1116b. Figure 11F The editing user interface 1140. Figure 11GThe editing user interface 1142 is optionally scrollable to view any content item in a moment 1106a, and the metadata 1150 is optionally updated to correspond to the content of that item in the view as the user scrolls from the first content item to the second content item. For example, since the photo content 1131c is in Figure 11G In the view, device 500A therefore displays metadata 1150 corresponding to photo content 1131c. Continuing the example, in response to detecting scroll input for one of the five songs in moment 1106a, device 500A displays metadata corresponding to that one of the five songs, instead of metadata 1150 corresponding to photo content 1131c.

[0397] Figure 11F Editing user interface 1140 and Figure 11G The editing user interface 1142 is optionally updated based on a selection performed in another editing user interface. For example, when device 500A displays... Figure 11B or Figure 11D When editing the user interface 1140, the user can optionally deselect one or more content items or one or more content item types of moment 1106a, and in response to detecting an error... Figure 11B or Figure 11D The optional option 1116a can be selected, and the device 500A can be displayed arbitrarily. Figure 11G The editing user interface 1142, including one or more content items that were deselected at the moment 1106a in the editing user interface 1140, is also in Figure 11G The selection is deselected in the editing user interface 1142 (e.g., no further user input). For example, when device 500A displays... Figure 11B or Figure 11D When editing the user interface 1140, the user optionally selects one or more content items or one or more content item types of moment 1106a, and in response to detecting an action... Figure 11B or Figure 11D The optional option 1116a can be selected, and the device 500A can be displayed arbitrarily. Figure 11G The editing user interface 1142, including one or more content items selected at the moment 1106a in the editing user interface 1140, is also in Figure 11G The user is selected in the editing user interface 1142 (for example, no further user input is required).

[0398] Therefore, this implementation provides users with the ability to seamlessly create log entries and / or edit content item types and / or content items for inclusion in or exclusion from log entries without requiring additional input from the user, thus providing a simple way for the user to record selected items.

[0399] Figure 12 It is shown according to such Figures 11A to 11G The flowcharts of some implementations of method 1200 for logging user interface are shown. Method 1200 is optionally performed on an electronic device (such as device 100, device 300, or device 500), as referenced above. Figures 1A to 1B , Figures 2 to 3 , Figures 4A to 4B and Figures 5A to 5H As described. Some operations in method 1200 are optionally combined, and / or the order of some operations is optionally changed.

[0400] In some embodiments, method 1200 is performed at an electronic device that communicates with a display generating 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 the following: a mouse (e.g., external), a touchpad (optionally integrated or external), a remote control device (e.g., external), another mobile device (e.g., separate from the electronic device), a handheld device (e.g., external), and / or a controller (e.g., external), etc. In some embodiments, the display generating component is a display integrated with the electronic device (optionally a touchscreen display), an external display such as a monitor, projector, television, or a hardware component (optionally integrated or external) for projecting a user interface or making the user interface visible to one or more users, etc. In some embodiments, method 1200 is performed at or by a vehicle (e.g., at the infotainment system of a vehicle having or communicating with one or more display generating components and / or input devices).

[0401] In some embodiments, the electronic device displays (1202a) a first user interface (e.g., via a display generating component). Figure 11A The instantaneous user interface 1102), the first user interface includes: suggested content items (e.g., included in log entries of the logging application) for inclusion in log entries of the logging application. Figure 11A A list of content items in moment 1106a, such as content items 1108a-1108e (e.g., Figure 11A The moment 1106a), wherein the suggested content items in the suggested content item list are included in the suggested content item list at least in part based on data detected by an application different from the logging application (such as the date of the content item, the location of the content item, the person associated with the content item, the event associated with the content item, or other types of data); and the corresponding user interface elements (e.g., Figure 11AOptional option 1114a), this user interface element can be selected such that the suggested content items in the suggested content item list are separated from the content entry area for logging information about the suggested content item list (such as...). Figure 8F Content entry area 817 or Figure 8G The log entry field 812) also displays (1202c).

[0402] In some implementations, when the first user interface is displayed, the electronic device receives (1202d) input via one or more input devices, such as... Figure 11A Contact 1103a.

[0403] In some implementations, in response to receiving the input (1202e), based on determining that the input points to a list of suggested content items, the electronic device displays (1202f) first data including the suggested content items (e.g., ...) via a display generation component. Figure 11B Description 1118 Figure 11B The text content 1120 and / or Figure 11B Other indications of the suggested content items' data, such as visual indications in user interface elements 1122a-1122e, are shown in the second user interface (e.g., Figure 11B Editing user interface 1140 or Figure 11G The editing user interface 1142) does not display the content entry area (e.g., does not display...). Figure 8F (Log entry field 812 or content entry area 817). In some embodiments, the electronic device displays a second user interface having a content entry area and / or a log entry field.

[0404] In some implementations, in response to receiving the input (1202e), based on determining that the input points to a corresponding user interface element, the electronic device simultaneously displays (1202g) suggested content items and a content entry area of ​​the suggested content item list via a display generation component, such as displaying... Figure 8F The log entry user interface 810 includes content entry areas that contain the content items corresponding to the selected optional option at the corresponding moment. For example, in response to the selection of optional option 1114a, device 500A optionally displays... Figure 8G or Figure 8F The log entry user interface 810, but the content items of the selected moment 1106a (e.g., all content items of the selected moment 1106a, which are optionally equal to or greater than) Figure 11A The content item (representing the number of 1108a-1108e) is...

Claims

1. A method, the method comprising: At the electronic device that communicates with the display generation component and one or more input devices: The first user interface is displayed via the display generation component, the first user interface including: A list of suggested content items, which is intended to be included in log entries of a logging application, wherein the suggested content items in the list are included in the list based at least in part on data detected by an application other than the logging application; and A corresponding user interface element, which can be selected to display the suggested content items of the suggested content item list and the content entry area for logging about the suggested content item list simultaneously; When the first user interface is displayed, input is received via the one or more input devices; and In response to receiving the input: Based on the determination that the input points to the list of suggested content items, a second user interface including first data of the suggested content items is displayed via the display generation component, without displaying the content item area; and Based on the determination that the input points to the corresponding user interface element, the following content is simultaneously displayed via the display generation component: The suggested content items in the list of suggested content items; and The content entry area.

2. The method according to claim 1, wherein: The second user interface includes a first user interface element, which includes: A first user interface element corresponding to a content item of a first type in the suggested content item list, wherein the first user interface element visually indicates the first type, the number of content items of the first type, and / or other metadata associated with the content items of the first type; and A second user interface element corresponding to a second type of content item in the suggested content item list, wherein the second user interface element visually indicates the second type, the number of content items of the second type, and / or other metadata associated with the content items of the second type.

3. The method according to claim 2, wherein: The first user interface element includes a first optional option, which is used to exclude or include content items of the first content item type based on each first content item type; as well as The second user interface element includes a second optional option for excluding or including content items of the second type based on each second content item type.

4. The method according to claim 2 or 3, wherein: The first user interface element includes a first optional option for viewing content items of the first type in the suggested content item list, and the method includes: Receive input directed to the first optional option via the one or more input devices; and In response to receiving the input pointing to the first optional option, the following is simultaneously displayed via the display generation component: The first corresponding content item of the first type in the suggested content item list; and A first corresponding optional option is used to exclude or include the first corresponding content item based on each content item of the first type, rather than based on each first content item type.

5. The method according to any one of claims 2 to 4, wherein The second user interface includes a first user interface element, which includes: A third optional option is used to display a horizontally scrollable view of the content items in the suggested content items; and The method includes: Receive input pointing to a third optional option via the one or more input devices; and In response to receiving the input pointing to the third optional option, the following is displayed via the display generation component: A third user interface, comprising a horizontally scrollable view of content items in the suggested content items, and the third user interface including second user interface elements, the second user interface elements including: The first corresponding content item of the first type in the suggested content item list; and A first corresponding optional option is used to exclude or include the first corresponding content item based on each content item of the first type, rather than based on each first content item type.

6. The method of claim 5, wherein the third user interface includes a fourth optional option for displaying the second user interface, and the method comprises: When the third user interface is displayed via the display generation component: Receive input via the one or more input devices to a first optional option among the first corresponding optional options, wherein the first optional option can be selected to exclude a first corresponding content item from the inclusion of the log entry; as well as In response to receiving the input pointing to the first optional option among the first corresponding optional options, visually indicate that the first corresponding content has not been selected for inclusion in the log entry; After receiving the input pointing to the first optional option among the first corresponding optional options, input pointing to the fourth optional option is received via the one or more input devices; In response to receiving the input pointing to the fourth optional option, the second user interface is displayed via the display generation component, the second user interface including the first data modified due to the input pointing to the first optional option among the corresponding optional options.

7. An electronic device, the 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 configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: A first user interface is displayed via a display generation component, the first user interface including: A list of suggested content items, which is intended to be included in log entries of a logging application, wherein the suggested content items in the list are included in the list based at least in part on data detected by an application other than the logging application; and A corresponding user interface element, which can be selected to display the suggested content items of the suggested content item list and the content entry area for logging about the suggested content item list simultaneously; When the first user interface is displayed, input is received via one or more input devices; and In response to receiving the input: Based on the determination that the input points to the list of suggested content items, a second user interface including first data of the suggested content items is displayed via the display generation component, without displaying the content item area; and Based on the determination that the input points to the corresponding user interface element, the following content is simultaneously displayed via the display generation component: The suggested content items in the list of suggested content items; and The content entry area.

8. A non-transitory computer-readable storage medium storing one or more programs, said one or more programs comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform a method comprising: A first user interface is displayed via a display generation component, the first user interface including: A list of suggested content items, which is intended to be included in log entries of a logging application, wherein the suggested content items in the list are included in the list based at least in part on data detected by an application other than the logging application. and A corresponding user interface element, which can be selected to display the suggested content items of the suggested content item list and the content entry area for logging about the suggested content item list simultaneously; When the first user interface is displayed, input is received via one or more input devices; as well as In response to receiving the input: Based on the determination that the input points to the list of suggested content items, a second user interface including first data of the suggested content items is displayed via the display generation component, without displaying the content item area; as well as Based on the determination that the input points to the corresponding user interface element, the following content is simultaneously displayed via the display generation component: The suggested content items in the list of suggested content items; and The content entry area.

9. An electronic device, the electronic device comprising: One or more processors; Memory; A component for performing any one of the methods according to claims 1 to 6.

10. An information processing apparatus for use in an electronic device, the information processing apparatus comprising: A component for performing any one of the methods according to claims 1 to 6.

11. An electronic device, the 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 configured to be executed by the one or more processors, the one or more programs including instructions for performing any one of the methods according to claims 1 to 6.

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

Images