EP4537280A1 - Interfaces utilisateur pour créer des entrées de journalisation - Google Patents

Interfaces utilisateur pour créer des entrées de journalisation

Info

Publication number
EP4537280A1
EP4537280A1 EP23735909.6A EP23735909A EP4537280A1 EP 4537280 A1 EP4537280 A1 EP 4537280A1 EP 23735909 A EP23735909 A EP 23735909A EP 4537280 A1 EP4537280 A1 EP 4537280A1
Authority
EP
European Patent Office
Prior art keywords
journaling
application
displaying
user
user interface
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP23735909.6A
Other languages
German (de)
English (en)
Inventor
Joseph-Alexander P. Weil
Daniel J. Zigmond
Mariah W. Whitmore
Adeeti V. Ullal
Nadaleen F. TEMPELMAN-KLUIT
Nathan A. Russak
Joanna M. Newman
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Inc filed Critical Apple Inc
Priority claimed from PCT/US2023/024389 external-priority patent/WO2023239625A1/fr
Publication of EP4537280A1 publication Critical patent/EP4537280A1/fr
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/168—Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
    • G06F16/1815—Journaling file systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04842—Selection of displayed objects or displayed text elements
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04845—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range for image manipulation, e.g. dragging, rotation, expansion or change of colour
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
    • G06F3/04883—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures for inputting data by handwriting, e.g. gesture or text

Definitions

  • This relates generally to user interfaces associated with creating journaling entries.
  • Some embodiments described in this disclosure are directed to one or more electronic devices that display suggested content for inclusion in a journal entry of a journaling application.
  • Some embodiments described in this disclosure are directed to one or more electronic devices that display one or more lookbacks.
  • the full descriptions of the embodiments are provided in the Drawings and the Detailed Description, and it is understood that the Summary provided above does not limit the scope of the disclosure in any way.
  • personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
  • personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
  • FIG. 1 A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.
  • FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.
  • Figs. 6A-6QQ illustrate exemplary ways of detecting activity events and displaying a prompt to create journaling entries in accordance with some embodiments.
  • Fig. 7 is a flow diagram illustrating a method 700 of displaying a prompt that is selectable to initiate a process to create a journal entry in accordance with some embodiments.
  • Fig. 9 is a flow diagram illustrating a method 900 of displaying user interfaces for journaling in accordance with some embodiments.
  • Fig. 10 is a flow diagram illustrating a method 1000 for displaying user interfaces including lookbacks in accordance with some embodiments.
  • journaling user interfaces that allow the user to easily add content items from different applications to a journal entry and/or to prompt the user to create journal entries based on previously generated content items.
  • Such user interfaces can reduce the cognitive burden on a user who uses such devices and/or wishes to create journaling entries, and can provide enhanced privacy or security. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
  • first could be termed a second touch
  • first touch could be termed a first touch
  • second touch could be termed a first touch
  • the first touch and the second touch are both touches, but they are not the same touch.
  • the term “if’ is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context.
  • the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
  • an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
  • the device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
  • applications such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
  • the various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface.
  • One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application.
  • a common physical architecture (such as the touch- sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
  • FIG. 1 A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display 112 in accordance with some embodiments.
  • Touch-sensitive display 112 is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.”
  • Device 100 includes memory 102 (which optionally includes one or more computer-readable storage mediums), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external port 124.
  • Device 100 optionally includes one or more optical sensors 164.
  • Device 100 optionally includes one or more contact intensity sensors 165 for detecting intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100).
  • Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.
  • the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface.
  • the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements).
  • the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user’s sense of touch.
  • a component e.g., a touch-sensitive surface
  • another component e.g., housing
  • the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device.
  • a touch-sensitive surface e.g., a touch-sensitive display or trackpad
  • the user is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button.
  • a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”)
  • the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
  • Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic 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.
  • RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals.
  • RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals.
  • RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth.
  • an antenna system an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth.
  • SIM subscriber identity module
  • RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication.
  • the RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio.
  • NFC near field communication
  • the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.1 In, and/or IEEE 802.1 lac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g.,
  • Patent Application 11/322,549 “Unlocking a Device by Performing Gestures on an Unlock Image,” filed December 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety.
  • a longer press of the push button e.g., 206 optionally turns power to device 100 on or off.
  • the functionality of one or more of the buttons are, optionally, user-customizable.
  • Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
  • Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact.
  • Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112.
  • user-interface objects e.g., one or more soft keys, icons, web pages, or images
  • a point of contact between touch screen 112 and the user corresponds to a finger of the user.
  • Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments.
  • Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112.
  • touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112.
  • projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
  • a touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety.
  • touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
  • a touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (l) U.S. Patent Application No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. Patent Application No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. Patent Application No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed July 30, 2004; (4) U.S. Patent Application No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed January 31, 2005; (5) U.S. Patent Application No.
  • Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi.
  • the user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth.
  • the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen.
  • the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
  • Device 100 optionally also includes one or more contact intensity sensors 165.
  • FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in EO subsystem 106.
  • Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface).
  • Contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment.
  • contact intensity information e.g., pressure information or a proxy for pressure information
  • the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user’s ear (e.g., when the user is making a phone call).
  • Device 100 optionally also includes one or more accelerometers 168.
  • FIG. 1 A shows accelerometer 168 coupled to peripherals interface 118.
  • accelerometer 168 is, optionally, coupled to an input controller 160 in I/O subsystem 106.
  • Accelerometer 168 optionally performs as described in U.S. Patent Publication No. 20050190059, “Accel eration -based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety.
  • information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers.
  • Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100.
  • Device/global internal state 157 includes one or more of active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including information obtained from the device’s various sensors and input control devices 116; and location information concerning the device’s location and/or attitude.
  • Operating system 126 e.g, Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks
  • Operating system 126 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.
  • Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124.
  • External port 124 e.g. Universal Serial Bus (USB), FIREWIRE, etc.
  • USB Universal Serial Bus
  • FIREWIRE FireWire
  • the external port is a multi-pin (e.g, 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
  • Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
  • contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon).
  • at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware.
  • a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
  • Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed.
  • graphics includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
  • graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
  • Calendar module 148 • Calendar module 148;
  • Map module 154 • Map module 154;
  • workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
  • create workouts e.g., with time, distance, and/or calorie burning goals
  • communicate with workout sensors sports devices
  • receive workout sensor data calibrate sensors used to monitor a workout
  • select and play music for a workout and display, store, and transmit workout data.
  • camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
  • calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
  • map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
  • maps e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data
  • FIG. IB is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.
  • memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).
  • event sorter 170 e.g., in operating system 126
  • application 136-1 e.g., any of the aforementioned applications 137-151, 155, 380-390.
  • event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
  • Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch- sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
  • FIG. 1 Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur.
  • the application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
  • Hit view determination module 172 receives information related to sub-events of a touch-based gesture.
  • hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of subevents that form an event or potential event). 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 for which it was identified as the hit view.
  • Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
  • operating system 126 includes event sorter 170.
  • application 136-1 includes event sorter 170.
  • event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
  • a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170.
  • Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192.
  • one or more of the application views 191 include one or more respective event handlers 190.
  • one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
  • a respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information.
  • Event recognizer 180 includes event receiver 182 and event comparator 184.
  • event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
  • Event receiver 182 receives event information from event sorter 170.
  • the event information includes information about a sub-event, for example, a touch or a touch movement.
  • the event information also includes additional information, such as location of the sub-event.
  • the event information optionally also includes speed and direction of the sub-event.
  • events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
  • a respective event recognizer 180 determines that the series of subevents do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process subevents of an ongoing touch-based gesture.
  • Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204.
  • menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100.
  • the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
  • Each of the above-identified elements in FIG. 3 is, optionally, stored in one or more of the previously mentioned memory devices.
  • Each of the above-identified modules corresponds to a set of instructions for performing a function described above.
  • the aboveidentified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments.
  • memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.
  • FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3) that is separate from the display 450 (e.g., touch screen display 112).
  • Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.
  • one or more contact intensity sensors e.g., one or more of sensors 359
  • tactile output generators 357 for generating tactile outputs for a user of device 300.
  • finger inputs e.g., finger contacts, finger tap gestures, finger swipe gestures
  • one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input).
  • a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact).
  • a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact).
  • a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact).
  • multiple user inputs it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
  • FIG. 5A illustrates exemplary personal electronic device 500.
  • Device 500 includes body 502.
  • device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1 A-4B).
  • device 500 has touch-sensitive display screen 504, hereafter touch screen 504.
  • touch screen 504 optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied.
  • the one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data that represents the intensity of touches.
  • the user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device 500.
  • Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed November 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
  • device 500 has one or more input mechanisms 506 and 508.
  • Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms.
  • device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
  • FIG. 5B depicts exemplary personal electronic device 500.
  • device 500 can include some or all of the components described with respect to FIGS. 1A, IB, and 3.
  • Device 500 has bus 512 that operatively couples VO section 514 with one or more computer processors 516 and memory 518.
  • VO section 514 can be connected to touch screen 504, which can have touch-sensitive component 522 and, optionally, intensity sensor 524 (e.g., contact intensity sensor).
  • VO section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques.
  • Device 500 can include input mechanisms 506 and/or 508.
  • Input mechanism 506 is, optionally, a rotatable input device or a depressible and rotatable input device, for example.
  • Input mechanism 508 is, optionally, a button, in some examples.
  • Memory 518 of personal electronic device 500 can include one or more non- transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including methods 700, 900, and/or 1000 (Figs. 7, 9, and 10).
  • a computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device.
  • the storage medium is a transitory computer-readable storage medium.
  • the storage medium is a non-transitory computer-readable storage medium.
  • system or computer readable medium contains instructions for performing the contingent operations based on the satisfaction of the corresponding one or more conditions and thus is capable of determining whether the contingency has or has not been satisfied without explicitly repeating steps of a method until all of the conditions upon which steps in the method are contingent have been met.
  • a system or computer readable storage medium can repeat the steps of a method as many times as are needed to ensure that all of the contingent steps have been performed.
  • the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1 A, 3, and 5A-5B).
  • an image e.g., icon
  • a button e.g., button
  • text e.g., hyperlink
  • a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input.
  • an input e.g., a press input by the contact
  • a particular user interface element e.g., a button, window, slider, or other user interface element
  • focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface.
  • the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user’s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact).
  • the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact).
  • a predefined time period e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds
  • a characteristic intensity of a contact is, optionally, based on one or more of a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like.
  • the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time).
  • the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user.
  • one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold.
  • the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input).
  • the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
  • the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold).
  • the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold.
  • the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
  • the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold.
  • the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
  • closing an application refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
  • UI user interfaces
  • portable multifunction device 100 such as portable multifunction device 100, device 300, or device 500.
  • Figs. 6A-6QQ illustrate exemplary ways of creating journaling entries in a journaling application in accordance with some embodiments of the disclosure.
  • the embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to Fig. 7.
  • Application icon 655 corresponds to a journaling application for creating and accessing journaling entries.
  • Application icon 660 corresponds to a camera application for taking photos.
  • device 500A detects selection of application icon 655 (e.g., via contact 603).
  • device 500A displays an authentication user interface 604 and only allows entry to the journaling application upon receiving authentication input (e.g., biometric, PIN, passcode or other authentication) that is successfully authenticated and will not display the journaling application if the authentication input is not successfully authenticated.
  • authentication input e.g., biometric, PIN, passcode or other authentication
  • device 500A detects an authentication input to authentication user interface 604 that is successfully authenticated (e.g., via contact 603).
  • device 500A displays a user interface 606 of the journaling application that includes representations of journaling entries 608-612 that have already been created in the journaling application, and selectable option 614.
  • Representation of journaling entry 608 corresponds to a journaling entry from December 14th.
  • Representation of journaling entry 613 corresponds to a journaling entry from December 15th.
  • Representation of journaling entry 612 corresponds to a journaling entry from December 16th.
  • Selectable option 614 is selectable to initiate a process to add a new journaling entry to the journaling application.
  • Selectable option 617 is selectable to initiate a process to view one or more animated video presentations that are related to activity events and/or journaling entries, discussed in more detail hereinafter.
  • device 500A detects selection of selectable option 614 (e.g., via contact 603).
  • device 500A updates user interface 606 to display selectable options 616 and 618.
  • Selectable option 616 is selectable to initiate a process to manually create a journaling entry.
  • Selectable option 618 is selectable to request a prompt from device 500 A to facilitate creation of a journaling entry.
  • device 500A detects selection of selectable option 616 (e.g., via contact 603) and one or more inputs to enter content into the journaling entry.
  • device 500A updates user interface 606 to display journaling entry 621, including the content manually provided by a user to device 500A (e.g., via manual soft keyboard entry and/or manual voice entry).
  • device 500A facilitates creation of journaling entries by automatically (e.g., without user input for doing so) displaying one or more prompts that facilitate the creation of journaling entries based on activities detected by device 500A, as will be described with reference to Figs. 6F-6R.
  • Fig. 6F represents an additional exemplary way of creating a journaling entry at device 500A.
  • device 500A detects selection of application icon 615 (e.g., via contact 603).
  • device 500 initiates a call via the calling application to the user’s “Mom.”
  • device 500A detects selection of application icon 630 (e.g., via contact 603).
  • device 500A displays user interface 622 of the map application that includes a first portion 624 that includes a representation of a map and a second portion 626 that includes a user interface element for searching and displaying routes.
  • First portion 624 includes a visual indication of a route 628
  • second portion 626 includes selectable button 631 that is selectable to initiate navigation directions along the route.
  • device 500A detects selection of selectable button 631 (e.g., via contact 603) and initiates navigation directions along route 628 (not shown) and subsequently returns to displaying user interface 602, as shown in Fig. 6J. Thus, device 500A detects that the user of device 500A has traveled along route 628.
  • device 500A detects selection of application icon 660 (e.g., via contact 603).
  • device 500A displays user interface 637 of the photo application.
  • User interface 637 includes user selectable button 634 that is selectable to take photos, such as of the contents of photo preview 636 (e.g., corresponding to images currently being captured by one or more cameras of device 500a).
  • device 500A optionally tracks various activities performed by device 500A (e.g., such as activities described above), and determines whether those activities satisfy criteria for generating and displaying a prompt for facilitating the creation of a journaling entry that is based on those activities. For example, in Fig. 6L, after the various activities described previously have been performed, and upon determining that those activities satisfy one or more criteria to facilitate the generation of a prompt, device 500A displays a prompt 638 on the lock screen 619 of device 500A.
  • activities performed by device 500A e.g., such as activities described above
  • Device 500A optionally displays prompt 638 on any of a number of user interfaces displayed by device 500A, such as the lock screen user interface, the user interface of an application, or any other user interface currently being displayed by device 500A when device 500A determines to display prompt 638.
  • a user can also be prompted on any number of personal or communal devices, including tablet, phone, smartwatch, TV, speaker, or other devices in a connected ecosystem.
  • Prompt 638 indicates that it is related to the journaling application and includes details regarding the activity event of going to the zoo.
  • Prompt 638 includes a description of where the user went (e.g., route to zoo) and a photo the user took as part of the activities (e.g., photo 1).
  • Prompt 638 is selectable to initiate a process to create a journaling entry in the journaling application.
  • prompt 638 includes a graphical or textual indication that it was generated by the software on behalf of the application, such as on behalf of the journaling application (e.g., to alert the user that the prompt 638 is not from the journaling application).
  • prompt 638 can include multiple sub-prompts (e.g., prompts that are each associated with different activities and/or events), such as by including both “Reflect on your day at the zoo” and “Write about the trip you took last year” (for example).
  • device 500A in response to detecting a selection of prompt 638, displays a picker user interface that includes representations of content associated with prompt 638 (optionally, including representations of content associated with each of the sub-prompts of prompt 638), from which the user can pick (e.g., select) content to provide (e.g., transmit or make accessible to) to the journaling application (or to another application associated with the content or the sub-prompt).
  • the picker user interface is separate from (e.g., not part of) the journaling application.
  • the picker user interface is displayed within the journaling application.
  • device 500A detects selection of prompt 638 (e.g., via contact 603).
  • device 500A displays user interface 640 that includes a prompt 642, a text or other content entry field 644, an indication 646, a soft keyboard 648, selectable option 651 selectable option 652, selectable option 654, and selectable option 656.
  • device 500A displays user interface 640 overlaid on the user interface that was displayed when device 500A detected selection of prompt 638, optionally without ceasing display of that user interface and/or without launching or displaying the journaling application.
  • Indication 646 is an indication or representation of a photo taken by device 500A during the activity event (e.g., taken at the zoo with mom, thus displayed with an “M” indication overlaid on a corner of the photo).
  • Selectable option 651 is selectable to change the prompt to a new and/or updated prompt related to the activity event (e.g., a different question generated and/or provided by device 500A related to the activity event).
  • Selectable option 652 is selectable to change the photo to a new and/or updated photo (e.g., taken by device 500A during the activity event).
  • Selectable option 654 is selectable to move to the next prompt for facilitating the creation of the journaling entry.
  • Selectable option 656 is selectable to end the display of prompt(s) for facilitating the creation of the journaling entry and for creating the journaling entry with the content entered into text entry field 644, parts of or all of prompt 642 and/or parts of or all of the photo corresponding to indication 646.
  • device 500A detects selection of one or more keys in soft keyboard 648 (e.g., via contact 603).
  • device 500A updates text entry field 644 of user interface 640 to include content corresponding to the input detected in Fig. 6Q as a response to prompt 661.
  • device 500A generates and displays one or more additional follow-on prompts based on text and/or other content entered by the user.
  • device 500A optionally analyzes text or other content entered in text entry field 644 using a large language model (or other artificial intelligence-based and/or natural-language- based approach) to generate and display appropriate follow-on prompts and interact with the user.
  • device 500A in response to detecting the text content “We also met mom there and she was excited to see the penguins” as shown in Fig. 6R, device 500A optionally generates and displays an additional prompt (e.g., replacing prompt 661) that says “What did mom say about the penguins?” to encourage the user to enter additional details.
  • an additional prompt e.g., replacing prompt 661
  • device 500A detects selection of representation 670 and/or representation 672 (e.g., via contact 603).
  • device 500A updates user interface 606 to display a journal entry 674 that corresponds to representation 670.
  • device 500A optionally allows users to create a journaling entry based on a content item.
  • device 500A detects selection of application icon 635 (e.g., via contact 603).
  • application icon 635 e.g., via contact 603
  • device 500A detects selection of selectable option 695d (e.g., via contact 603).
  • device 500A displays user interface 606 of the journaling application including representation 670 of a journaling entry.
  • Selectable option 617 is selectable to initiate a process to view one or more animated video presentations that are related to activity events and/or journaling entries.
  • device 500A displays the content of journaling entry 674 (e.g., such as illustrated in Fig. 6U).
  • device 500A detects selection of sharing option 698 (e.g., via contact 603).
  • device 500A displays achievement 697 in user interface 686 in a similar way that photo 678 is displayed in user interface 686 in Fig. 6BB.
  • device 500A optionally allows users to create a journaling entry from a second device.
  • Fig. 6PP illustrates an exemplary device 500B that includes touch screen 504B.
  • Device 500B is optionally associated with device 500A (e.g., device 500A is a smart phone logged into and/or configured with a user account, and device 500B is a smart watch that is paired with device 500A and/or is logged into and/or configured with the same user account).
  • device 500B is displaying user interface 607, which is optionally a watch face user interface of device 500B and includes an indication of time.
  • Selectable options 61 la-611c are selectable to enter a response to prompt 609 (e.g., for inclusion in the journaling entry).
  • the predefined responses corresponding to selectable options 61 la-611c are emoji responses.
  • selectable option 61 la is selectable to enter a smiling face response to prompt 609 (e.g., for inclusion in the journaling entry), and optionally includes a representation (e.g., image) of the corresponding response.
  • Selectable option 61 lb is selectable to enter a sad face response to prompt 609 (e.g., for inclusion in the journaling entry), and optionally includes a representation (e.g., image) of the corresponding response.
  • Selectable option 611c is selectable to enter a concerned face response to prompt 609 (e.g., for inclusion in the journaling entry), and optionally includes a representation (e.g., image) of the corresponding response.
  • Fig. 7 is a flow diagram illustrating a method 700 of displaying a prompt to a user to generate journaling entries in accordance with some embodiments, such as in Figs. 6A-6QQ.
  • the method 700 is optionally performed at an electronic device such as device 100, device 300, or device 500 as described above with reference to Figs. 1 A-1B, 2-3, 4A-4B and 5A-5H.
  • Some operations in method 700 are, optionally combined and/or order of some operations is, optionally, changed.
  • the electronic device may include, for example, a mobile device (e.g., a tablet, a smartphone, a media player, or a wearable device) including wireless communication circuitry, optionally in communication with one or more of a mouse (e.g., external), trackpad (optionally integrated or external), touchpad (optionally integrated or external), 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.).
  • a mobile device e.g., a tablet, a smartphone, a media player, or a wearable device
  • wireless communication circuitry optionally in communication with one or more of a mouse (e.g., external), trackpad (optionally integrated or external), touchpad (optionally integrated or external), remote control device (e.g., external), another mobile device (e.g., separate from the electronic device), a handheld device (e.g., external), and/or
  • the electronic device detects the above operations being performed by one or more other electronic devices associated with the user (e.g., a smartwatch of the user, a tablet computer of the user, and/or a smartphone of the user, which are optionally all logged into the same user account, which is associated with the user).
  • a smartwatch of the user e.g., a smartwatch of the user, a tablet computer of the user, and/or a smartphone of the user, which are optionally all logged into the same user account, which is associated with the user.
  • the user selectable option is selectable to initiate a process to enter the journaling application and/or a process to receive input for content that will be entered into the journaling application via the prompt (e.g., without displaying the journaling application).
  • the prompt includes information about the user activity event (e.g., information such as the location of the activity event, the time of the activity event, and/or photos from the activity event).
  • the journaling application is an application that receives and/or stores journal entry input from a user of the electronic device.
  • the electronic device forgoes display (702d), via the display generation component, of the prompt associated with the journaling application, such as if the phone call in Fig. 6G was to the zoo which is not a popular contact.
  • the user of the electronic device if the activity event does not satisfy the one or more criteria, if the user of the electronic device wants to create a journal entry for the activity event in the journaling application, the user of the electronic device must manually launch the journaling application and provide input from within the journaling application to create the journal entry. Displaying a prompt to a user of the electronic device to provide content to a journaling application based on the user’s activity provides the user with an easy and personalized platform for creating journal entries, thus reducing the number of inputs needed to create journal entries.
  • the first user input is directed to a content item displayed in a first application different from the journaling application, such as contact 603 in Fig. 6AA.
  • the first application is optionally stored or installed on the electronic device and is capable of communicating with the journaling application.
  • 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, podcast or games.
  • the content item is displayed with a user selectable option that is selectable to initiate a process to create a journal entry in the journaling application with or without ceasing display of the first application.
  • the process to manually create the respective journaling entry in the journaling application utilizes the content item as part of the journaling entry, such as photo 678 in Fig. 6AA.
  • the electronic device creates a journaling entry within the journaling application that connects to and/or includes the content item.
  • the electronic device displays a prompt associated with the content item as part of the process to manually create the respective journaling entry.
  • the electronic device displays a journal entry user interface that is configured to receive user input for populating the journal entry, where the journal entry already includes the content item. Automatically populating the journal entry with the content item provides the user with an easy way to journal about content items, thus reducing the number of inputs needed to create journal entries for content items.
  • the first user input is directed to a user interface displayed in the journaling application, such as contact 603 in Fig. 6C.
  • the journaling entry is created directly from within the journaling application.
  • the first user input includes selection of an option displayed in a user interface of the journaling application for creating a journal entry in the journaling application.
  • the electronic device before displaying the user interface in the journaling application, receives, via the one or more input devices, a second user input corresponding to a request to display the journaling application, such as contact 603 in Fig. 6A (e.g., receiving selection of an icon for the journaling application on a home screen user interface of the electronic device).
  • a second user input corresponding to a request to display the journaling application, such as contact 603 in Fig. 6A (e.g., receiving selection of an icon for the journaling application on a home screen user interface of the electronic device).
  • the electronic device in response to receiving the second user input, requires user authentication before displaying the journaling application, such as contact 603 in Fig. 6B.
  • the user authentication protects the journaling entries stored in the journaling application.
  • the electronic device will only allow entry to the journaling application upon receiving authentication input that is successfully authenticated, and will not display the journaling application if the authentication input is not successfully authenticated. Requiring authentication for entry to the journaling application ensures the journaling entries are secure and improves user privacy and security.
  • the user authentication includes one or more of a facial identification, a fingerprint identification, or a passcode identification, such as shown as a passcode identification in Fig. 6B.
  • the user authentication requires the user to scan or take an image of their face via one or more cameras of the electronic device, to scan their fingerprint via one or more fingerprint sensors of the electronic device, and/or enter a passcode via the touch screen of the electronic device. Requiring authentication for entry to the journaling application ensures the journaling entries are secure and improves user privacy and security.
  • the content of a given journal entry and/or the indications of the plurality of journal entries are displayed on one or more virtual pages of a virtual book. Displaying the journal entries in the user interface as a page of a book is an efficient manner of laying out the journal entries, and reduces the number of inputs needed to navigate to the correct journal entry.
  • the electronic device displays, via the display generation component, a user interface of the journaling application including a plurality of journaling entries (e.g., 608, 612, 613, and/or 614), including the journaling entry (e.g., 670), where the plurality of journaling entries are displayed chronologically within the user interface of the journaling application, such as user interface 606 in Fig. 6C.
  • the journal entry is displayed in the user interface after one or more journal entries with an earlier creation and/or last edit date than the journal entry, and/or before one or more journal entries with a later creation and/or last edit date.
  • the journaling application including the journaling entry, is accessible via a second electronic device that is associated with the electronic device, such as device 500B in Fig. 6PP.
  • the electronic device is a tablet, a watch, a computer, or a smart tv or set-top box. Accordingly, and in some embodiments, the second electronic device is a mobile phone while the electronic device is a smart watch.
  • the activity event does not satisfy the one or more criteria, such as photo 678 in Fig. 6AA.
  • the electronic device receives, via the one or more input devices, a first user input directed to the journaling application corresponding to a request for a respective prompt associated with the journaling application, wherein the respective prompt is associated with the activity event, such as prompt 690 in Fig. 6CC.
  • the first user input is directed to a user interface of the journaling application.
  • the first user input is selection of a “display journaling prompt” button displayed in the user interface of the journaling application.
  • the first user input is directed to content such as photos, albums, maps, web searches, or podcasts.
  • the electronic device in response to receiving the first user input, displays, via the display generation component, the respective prompt (e.g., 690), wherein input directed to the respective prompt (e.g., 690) initiates a process to provide input for a respective journaling entry associated with the activity event in the journaling application, such as by entering text into text entry field 644 and selecting selectable option 656 in Fig. 6CC.
  • the prompt optionally includes a user selectable option, as will be described below.
  • the prompt optionally includes information about the experience or information about the user activity event, as will be described below.
  • user input can cause the electronic device to manually display the respective prompt, which optionally includes information to guide the user through creating the journal entry, as described herein.
  • Providing the user with an option to request a prompt provides the user with a quick way to display information related to recent activities to write about, thus reducing battery usage for the electronic device.
  • the electronic device in response to receiving the first user input, and in accordance with a determination that the first user input includes speech input, the electronic device incorporates the speech input into the journaling entry, such as if the electronic device received speech input into text entry field 644 in Fig. 6M. For instance, the electronic device optionally receives speech input from the user for a longer entry that the user does not want to manually type. In some embodiments, the speech input is entered into the journaling entry as text.
  • the electronic device optionally displays one or more emojis to the user along with the prompt (or the user interfaces displayed in response to selection of the prompt) via the display device and, upon receiving selection of one of the one or more emojis, enters the selected emoji in the journaling entry.
  • the emoji input is speech input directed to an animated emoji (e.g., optionally customized by the user), and the animated emoji speaking the detected/recorded speech input is entered into the journaling entry.
  • the electronic device receives, via the one or more input devices, first user input corresponding to a request to create a respective journal entry associated with a content item, such as contact 603 in Fig. 6R.
  • the content item is a photo, music, fitness achievement, video content, calendar event, route, book, podcast, or game.
  • the electronic device in response to receiving the first user input, creates the respective journal entry, including linking the respective journal entry to the content item, such as photos 1-3 with representation 670 in Fig. 6T.
  • a representation of the content item is stored within the respective journaling entry to alert the user that the respective journaling entry is associated with the content item.
  • the electronic device optionally displays a user interface of an application (e.g., optionally different from a user interface of the journaling application) that includes the content item. Providing a way for the user to link a content item with a journaling entry reduces the number of inputs needed to navigate to and/or display content items that are associated with j oumaling entries.
  • the electronic device after receiving the first user input and creating the respective journal entry, receives, via the one or more input devices, a second user input corresponding to a request to access the content item, such as contact 603 in Fig. 6FF.
  • the second user input is optionally a selection of the content item within a respective content browsing and/or playback application that is not the journaling application.
  • a representation of the content item is stored with the respective journal entry.
  • the second user input is optionally a selection of the representation of the content item.
  • the electronic device in response to receiving the second user input to access the content item, accesses (e.g., displays) the content item (e.g., 678) and displays, via the display generation component, a representation of the respective journal entry, such as representation 670 in Fig. 6GG.
  • the electronic device displays a representation of the journal entry concurrently with the content item.
  • the electronic device displays a representation of the journal entry without the content item.
  • the representation of the journal entry is selectable to display the (content of the) respective journal entry, including the content item, n some embodiments, the representation of the journal entry is a visual indication that indicates that the respective journal entry is associated with the content item.
  • the visual indication is displayed concurrently with the content item. In some embodiments, the visual indication is selectable to open the respective journal entry. Surfacing the journaling entry when the user revisits the content item provides the user with an efficient way to access the journaling entry, thus reducing the number of inputs needed to access the journaling entry when revisiting the content item.
  • the electronic device while displaying the prompt (e.g., 638) associated with the journaling application, receives, via the one or more input devices, a first user input directed to the prompt associated with the journaling application, such as contact 603 in Fig. 6L.
  • the first user input includes a click, a tap or a swipe input directed to the prompt.
  • the electronic device displays, in the prompt, an additional user selectable option that when selected displays the below- described user interface that includes the one or more details related to the event.
  • the electronic device in response to receiving the first user input, displays, via the display generation component, a user interface that includes one or more details related to the activity event, such as prompt 642 in Fig. 6M.
  • the details include a song listened to during the activity event, a route taken during the activity event, photos or videos taken during the activity event, a restaurant eaten at during the activity event, fitness information obtained during the activity event, people associated with the activity event (e.g., people who appeared in photos taken during the activity event and/or people who were located at the location(s) of the activity event during the activity event), a podcast listened to during the activity event, a movie or show watched during the activity event, and/or a location visited during the activity event.
  • Providing the user with details of the activity facilitates efficient creation of the journal entry, thus reducing the number of inputs needed to correct undesired portions of the journal entry.
  • the one or more details include one or more indications of one or more people associated with one or more photos taken by the electronic device during the activity event, such as the “M” to represent mom in Fig. 6M.
  • the electronic device determines the people associated with the photos based on photo activity stored on the electronic device.
  • the people are indicated in the user interface as a representative avatar or initial.
  • the people identified are those people that were with the electronic device when the electronic device took pictures or video during the activity event and/or those people that appear in the pictures and/or videos taken during the activity even. Identifying people associated with the activity event facilitates efficient creation of the journal entry, thus reducing the number of inputs needed to correct undesired portions of the journal entry.
  • the electronic device in response to receiving the first user input, displays, via the display generation component, a first question related to the activity event, such as prompt 642 in Fig. 6M.
  • the first question is a question related to one or more details associated with the activity event.
  • the first question optionally includes a question about a location at which the electronic device was located during the activity event, and/or a person within a picture the electronic device took during the activity event.
  • the electronic device while displaying the first question (e.g., 642) related to the activity event, receives, via the one or more input devices, a second user input corresponding to a first response that indicates a response to the first question, wherein at least a portion of the first response is included in the journaling entry, such as text entry field 644 in Fig. 6N.
  • the response includes text input provide by the user (e.g., via a hardware or software keyboard), and includes the user’s response to the first question: for example, a description of the location and the person’s reaction to the location.
  • the journaling entry includes one or both of the descriptions. Prompting the user and incorporating details of the response into the journal entry facilitates efficient population of content into a journal entry.
  • the electronic device displays, via the display generation component, a second question related to the activity event, wherein the second question is based on information associated with the activity event such as if prompt 658 in Fig. 60 is based on the response in text entry field 44 in Fig. N.
  • the information associated with the activity event includes a song listened to during the activity event, a route taken during the activity event, photos taken during the activity event, a restaurant eaten at during the activity event, fitness information obtained during the activity event, people associated with the activity event, a podcast listened to during the activity event, a movie or show watched during the activity event, and/or a location visited during the activity event.
  • the electronic device utilizes information entered by the user in prior journaling entries to determine the second question. For instance, if one or more of the prior journaling entries (often) discuss meditation at the top of a particular hill, and the activity event includes a hike at the particular hill, the second question optionally includes a question about meditation such as “nice hike, did you meditate today?” Providing follow-up questions based on earlier responses increases the amount of content in the journal entry that is relevant to the activity event.
  • the electronic device visits relatively infrequently (e.g., less than 1 time a year), the criterion is satisfied (and optionally not satisfied if otherwise).
  • the one or more criteria include a criterion that is satisfied based on one or more of operations performed by a second electronic device associated with the user of the electronic device, wherein the operations are associated with the activity event, such as if a smart watch was worn at the zoo and counted steps while carrying device 500B of Fig. 6PP.
  • the one or more criteria include a criterion that is satisfied based on one or more of content accessed by the electronic device that is associated with the activity event, such as calling Mom in Fig. 6G. For instance, if the electronic device detects calling a popular contact as described above during or following the activity event (e.g., a contact that was present at the activity event), the criterion is satisfied. For instance, if the electronic device detects opening a photo during or following the activity event (e.g., a photo taken during the activity event), the criterion is satisfied.
  • the electronic device displays, via the display generation component, a selectable option that is associated with the activity event, such as notification 676 in Fig. 6V.
  • the selectable option includes one or more representations of the activity event.
  • the selectable option includes text describing the activity event.
  • the selectable option is displayed on a wake screen user interface, a lock screen user interface, or a home screen user interface of the electronic device.
  • the user selectable option is selectable to initiate a process to view an animated video presentation associated with the journaling entry (e.g., of the content included in the journaling entry).
  • the electronic device while displaying the selectable option (e.g., 676) that is associated with the activity event, receives, via the one or more input devices, a first input corresponding to selection of the selectable option, such as contact 603 in Fig. 6V.
  • the first input includes a click, a tap or a swipe input directed to the selectable option.
  • the electronic device in response to receiving the first input, displays, via the display generation component, an animated video presentation associated with journaling entry, wherein the animated video presentation associated with the journaling entry includes one or more entries of the journaling entry and one or more content items associated with the activity event, such as animated video presentation 679 in Fig. 6W.
  • the content items are photos, achievements, representations of content items such as a route, text entries, and/or emoji entries that were entered into the journaling entry when it was created.
  • the electronic device displays the animated video presentation along with music.
  • the music was not part of the journaling entry (e.g., the electronic device did not detect input from the user to associate the music with the journaling entry).
  • the displaying of the animated video presentation associated with the journaling entry includes presenting music, such as shown in Fig. 6W (e.g., playing the music concurrently with displaying the animated video presentation).
  • the electronic device auto-selects the music (e.g., without user input for selecting the music).
  • the electronic device selects the music based on the journaling entry. For instance, if the journaling entry is about an outside fun activity, the electronic device will optionally select upbeat music for the animated video presentation.
  • the electronic device includes a user selectable option as part of the animated presentation for the user to change the music. Incorporating music into the animated video presentation avoids the need for additional user input to play music along with the animated presentation.
  • the prompt is displayed, via the display generation component, in a widget displayed in a system user interface of the electronic device, such as notification 683 (e.g., widget) in Fig. 6Y.
  • the widget is displayed on the home screen user interface of the electronic device.
  • the widget is displayed on a side screen user interface of the electronic device (e.g., a user interface that includes one or more widgets for different applications, including the widget including the prompt).
  • the widget includes the same information included in the prompt.
  • the widget includes a portion of the information included in the prompt. Displaying the prompt in a widget increases the likelihood the user will interact therewith, and reduces wasting resources on displaying the selectable option when it is unlikely to be interacted with.
  • the prompt is displayed in a first application other than the journaling application, such as if notification 676 of Fig. 6 V is displayed within the application that corresponds to application icon 620 of Fig. 6A.
  • the first application is a notes application, a music application, a fitness application, a maps application, a photos application, a content viewing application or any other application other than the journaling application.
  • the prompt is displayed in the first application based on the activity event being associated with the first application. For instance, if the electronic device detects accomplishment of an achievement defined by a fitness application on the device as an activity event (or part of the activity event), a prompt is optionally displayed in the fitness application.
  • the prompt is optionally displayed in that application (or the more applications).
  • the prompt is displayed in the first application merely because the electronic device is displaying a user interface of the first application at the time the prompt is to be displayed. Prompting the user while the electronic device is displaying an application other than the journaling application increases the likelihood the user will interact with the prompt, and reduces the number of inputs to create journaling entries.
  • the electronic device receives, via the one or more input devices, a first user input directed to the prompt (e.g., 638 in Fig. 6L).
  • the first user input includes a click, a tap or a swipe input directed to the prompt.
  • the electronic device in response to receiving the first user input, displays, via the display generation component, information related to the activity event without ceasing display of the first application, such as if the electronic device receives an input to a prompt in the application that corresponds to application icon 620 in Fig. 6A, a separate user interface would be overlaid on application that corresponds to application icon 620.
  • the information is concurrently displayed with the first application in a separate user interface within or overlaid on the first application.
  • the electronic device enables the user to switch between the first application and the separate user interface. Providing the user with a way to interact with the prompt and not leave the first application does not disrupt the user’s interaction with the first application, reduces the number of inputs to return to the first application, and reduces errors in device usage.
  • the prompt is displayed as a notification on the electronic device, such as prompt 638 in Fig. 6L.
  • the prompt is displayed, as a notification, on a lock screen or other user interface.
  • the prompt is displayed as a notification in the same manner and/or in the same user interfaces that notifications for other applications (e.g., email application, messaging application, phone application, and/or calendar applications) are displayed. Displaying the prompt as a notification provides the user with an accessible and consistent alert, thus reducing the number of inputs to create a journaling entry and reducing errors in device usage.
  • the electronic device in response to detecting the activity event associated with the user, and in accordance with the determination that the activity event satisfies the one or more criteria, the electronic device initiates a process to display a second prompt associated with the journaling application on a second electronic device associated with the electronic device (e.g., the electronic device and the second electronic device are both logged into and/or configured with the same user account or user profile), where input directed to the second prompt initiates a process to provide input for the journaling entry associated with the activity event in the journaling application, such as prompt 609 and contact 603 in Fig. 6PP.
  • the second electronic device is a watch and the electronic device is a phone.
  • the phone displays a prompt that is optionally configured to receive both emoji inputs (e.g., from an emoji keyboard displayed by the phone) and/or text inputs (e.g., from a text keyboard displayed by the phone).
  • emoji inputs e.g., from an emoji keyboard displayed by the phone
  • text inputs e.g., from a text keyboard displayed by the phone
  • the second prompt displayed by the second electronic device is configured to accept input of the first type but not the second type, such as selectable option 61 la-611c in Fig. 6QQ.
  • the second electronic device is a watch that is associated with the phone (e.g., as described previously)
  • the watch displays a prompt that is optionally configured to receive emoji inputs (e.g., from an emoji keyboard displayed by the phone) but not text inputs (e.g., because the watch does not display a text keyboard with the prompt).
  • Providing the user with different input options for different prompts ensures the prompts occupy appropriate screen size for the respective devices on which they are displayed.
  • detecting operation 702a and displaying operation 702c are, optionally, implemented by event sorter 170, event recognizer 180, and event handler 190.
  • Event monitor 171 in event sorter 170 detects a contact on touch screen 504, and event dispatcher module 174 delivers the event information to application 136-1.
  • Figs. 8A-8C depict a flow for creating a first journal entry in a journaling application (e.g., to assist a user in creating their first journal entry), such as the journaling application described with reference to methods 700, 900, and 1000.
  • a journaling application e.g., to assist a user in creating their first journal entry
  • device 500A detects selection of application icon 655 (e.g., via contact 803).
  • device 500a displays user interface 806 as shown in Fig. 8B, optionally after displaying an authentication user interface such as described with reference to Fig. 6B.
  • User interface 806 includes affordances 808a, 808b, and 808c that indicate, to the user, various options the user has for creating a journal entry.
  • User interface 806 includes affordance 808d, which is selectable to initiate creation of a new journal entry.
  • journal entry user interface 810 In response to detecting a selection of affordance 808d, device 500A displays journal entry user interface 810 as shown in Fig. 8C to allow the user to create a new journal entry.
  • Journal entry user interface 810 is optionally a user interface of the journaling application.
  • Journal entry user interface 810 includes journal entry field 812 for adding text and/or content items to a journal entry.
  • journal entry field 812 has one or more of the characteristics of text entry field 644 described with reference to Fig. 6M.
  • Content items that can be added to a journal entry using journal entry user interface 810 include, for example, photos, videos, audio clips, locations (e.g., routes or specific locations that have previously been mapped or otherwise captured by device 500A), some or all of a text message conversation, phone calls (e.g., a date, time, and/or duration of a phone call, along with the name of the caller/callee), fitness activities, songs, playlists, books, articles, podcasts, health metrics, images of electronic tickets, links to any of these types of content, and/or or other types of content items that are generated by and/or accessible to device 500A.
  • locations e.g., routes or specific locations that have previously been mapped or otherwise captured by device 500A
  • phone calls e.g., a date, time, and/or duration of a phone call, along with the name of the caller/callee
  • fitness activities e.g., songs, playlists, books, articles, podcasts, health metrics, images of electronic tickets, links to any of
  • Journal entry user interface 810 includes moments icon 814a, camera icon 814b, photo library icon 814c, audio clip icon 814d, and location icon 814e, which collectively provide a navigation user interface as described below.
  • Moments icon 814a when selected, causes device 500A to display one or more “moments” each including one or more related content items as described with reference to Fig. 8E.
  • moments are collections of one or more related content items, such as content items having the same date or that are associated with the same event.
  • device 500A generates, identifies, and/or stores moments (e.g., collections of one or more related content items) on device 500 (e.g., in the journaling application) based on analysis of content items stored on and/or accessible to device 500A, such as by identifying content items that are associated with a particular date or event that may be of interest to the user.
  • device 500A may determine that several photos in the user’s camera roll, a text message conversation between the user and another person, and a location that was visited by the user are all associated with the date of the user’s birthday, and may group such content items into a birthday-related “moment.”
  • a moment includes, in addition to the content items, metadata associated with the content items, such as a date associated with the content items, a title associated with the content items, event data associated with the content items, a location associated with the content items, or other types of metadata.
  • device 500A determines and/or generates (e.g., automatically) the metadata based on information embedded in or associated with the content items (e.g., data captured and/or generated by an application associated with the content item).
  • device 500A generates, identifies, and/or stores moments without explicit inputs regarding content items to include in a moment from the user (e.g., device 500A generates moments automatically, in the background). As described herein, device 500A may present such “moments” to the user to prompt the user to create journal entries associated with the moments.
  • Photo library icon 814c when selected by the user, displays thumbnails of the user’s photo library in journal entry user interface 810 (e.g., below journal entry field 812) and allows the user to select one or more photos for inclusion in the journal entry, as described with reference to Fig. 81.
  • Camera icon 814b when selected, causes device 500A to display a camera user interface that allows a user to capture a new photo and add it to the journal entry, as described with reference to Figs. 8J-8K.
  • Audio clip icon 814d when selected, allows the user to record an audio clip and add it to a journal entry as described with reference to Figs. 8L-8M.
  • Location icon 814e when selected, displays one or more location items (e.g., maps of previously recorded trips or locations of previous activities) and allows the user to select one or more of the location items for inclusion in journal entry field 812.
  • Journal entry user interface 810 optionally includes a suggested moment 816a (optionally, displayed below journal entry field 812) that includes multiple content items that have been determined (e.g., by device 500A and/or by another device), to be related to each other, such as by being associated with a single event, location, and/or date that may be considered a “moment” in the user’s life.
  • Suggested moment 816a may serve as a prompt to suggest, to the user, an activity or event to journal about.
  • suggested moment 816a includes a first photograph 818a, a second photograph 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 book).
  • location item 818c e.g., a location or route on a map
  • audio item 818d e.g., an audio clip or song
  • a media item 818e e.g., a podcast or book.
  • Other types of content items that are optionally included in a suggested moment include videos, text messages, fitness activities, or other types of content items generated by various applications.
  • moment 816a and/or representations of content items 818a-818e are added to journal entry field 812 and/or to a content entry region 817 (e.g., above journal entry field 812), as described with reference to Figs. 8F-8G.
  • Journal entry user interface 810 also includes affordance 820, which when selected causes the content of the journal entry field to be saved as a journal entry (e.g., to the journaling application).
  • affordance 820 when selected causes the content of the journal entry field to be saved as a journal entry (e.g., to the journaling application).
  • device 500A exits journal entry user interface 810 and optionally displays a journal timeline interface as described with reference to Fig. 8N.
  • a user can initiate text entry into journal entry field 812 by selecting journal entry field 812 (e.g., by tapping within journal entry field 812).
  • device 500A displays a soft keyboard 821 in user interface 810 to allow the user to enter text, as shown in Fig. 8D.
  • device 500A expands an area of journal entry field 812 within journal entry user interface 810 from a first area to a second area if the user enters more text than can fit in the first area of journal entry field 812.
  • journal entry After entering the desired text and/or adding content items from the suggested moment 816a and/or using icons 814a-814e to the journal entry field 812, the user can save the journal entry (e.g., save the content in journal entry field) by selecting affordance 820.
  • a user selects moments icon 814a (e.g., by tapping moments icon 814a) and device 500A responds by displaying moment 816b and moment 816c.
  • Moment 816b includes multiple content items 818f-818j that are optionally associated with a first date (e.g., December 7, 2022).
  • Moment 816c includes a single content item 818k that is optionally associated with a second date (e.g., November 30, 2022).
  • Content items 818f-818j and 818k can 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 journal entry field 812, as representations (e.g., thumbnails, excerpts, titles, or other representations) of content items 818f-818j and 818k rather than as the content items themselves.
  • a user can optionally select a moment (e.g., moment 816a or 816b) to add the moment (e.g., optionally including metadata) and/or content items of the moment to a journal entry.
  • a moment e.g., moment 816a or 816b
  • device 500A displays representations of the content items 818f-818j of moment 816b in a separate region 817 (e.g., a content entry region) of user interface 810, such as above journal entry field 812, to indicate to the user that the user has selected moment 816a for (potential) inclusion in the journal entry.
  • user interface 810 displays content items 818f-818j with an option (e.g., an affordance, a checkbox, or another type of option) to individually remove one or more of the selected content items so that the selected content items will not be added to the journal entry.
  • an option e.g., an affordance, a checkbox, or another type of option
  • the computer system in response to detecting selection of moment 816b, ceases to display moment 816b in its original location (e.g., below journal entry field 812 and/or below icons 814a-814e).
  • Fig. 8F the user has indicated that content items 818g, 818i, and 818j are not to be added to (e.g., are to be excluded from) the journal entry by checking boxes that are displayed with content items 818g, 818i, and 818j .
  • the user can provide an input to add the remaining content items to the journal entry field 812, such as by tapping on the region 817 in which the content items 818f-818j are displayed or tapping in journal entry field 812.
  • device 500A In response to detecting the user input, device 500A ceases to display content items 818f-818j in the region 817 above journal entry field 812, and displays content items 818f and 818h (or representations of content items 818f and 818h) in the journal entry field 812 (e.g., to be added to the journal entry), as shown in Fig. 8G.
  • the user can then (optionally) enter text in the journal entry field 812, as shown in Fig. 8G, and save the journal entry including content items 818f and 818h and any entered text by selecting affordance 820.
  • the user can delete content items from journal entry field 812 before saving the journal entry, such as by selecting the content item to be deleted and providing a delete input.
  • the user can select a date for the journal entry that is the same as or different from the date on which the journal entry is created.
  • device 500A optionally displays a default date 822 when a user begins to create a journal entry.
  • the default date 822 is optionally today’s date, a date associated with added moments or content items (e.g., moment 816b and/or content items 818f and 818g), or another default date that is selected by device 500A or configured by the user (e.g., as a configuration setting associated with the journaling application).
  • device 500A In response to detecting a selection of default date 822 (such as a tap on date 822), device 500A displays a menu 824 of date options that optionally includes one or more of today’s date 824a, date of moment 824b (e.g., a date associated with a moment added to the journal entry, such as the date that the user went on a hike corresponding to the moment), date from photos 824c (e.g., a date associated with a photo(s) added to the journal entry, such as the date that the photo(s) were taken by device 500A), and custom date 824d (e.g., a date of the user’s choosing).
  • date of moment 824b e.g., a date associated with a moment added to the journal entry, such as the date that the user went on a hike corresponding to the moment
  • date from photos 824c e.g., a date associated with a photo(s) added to the journal entry, such as the date that the photo(s) were
  • device In response to detecting a user selection of one of date options 824a-824d, device updates the default date 822 to the selected date, which will then be saved as the date of the journal entry.
  • menu 824 excludes (e.g., does not display) one or more of date options 824a-824d. For example, if the user has not added a moment and/or photo to the journal entry, menu 824 optionally excludes date options 824b and/or 824c, respectively. As another example, if the default date 822 is today’s date, menu 824 optionally excludes date option 824a. In some embodiments, menu 824 always includes custom date 824d to allow the user to choose their own date for the journal entry.
  • Fig. 81 illustrates an example of allowing a user to select photos from a photo library to add to a journal entry.
  • the user selects photo library icon 814c in user interface 810.
  • device 500A displays, in a region of user interface 810 (e.g., below journal entry field 812), representations (e.g., thumbnails) of photos 815a-815f from the user’s photo library.
  • the user can optionally select one or more of the photos 815a-815f for inclusion in journal 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 a journal entry.
  • Figs. 8J and 8K illustrate an example of using a camera user interface and/or application to capture a new photo and add it to a journal entry in the journaling application.
  • device 500A In response to detecting an activation of virtual button 830, device 500A captures a new photo using a camera of device 500A and optionally automatically (e.g., without additional user input) adds the new photo (e.g., new photo 834) to journal entry field 812, as shown in Fig. 8K. In some embodiments, in response to detecting an activation of virtual button 830 and after capturing the new photo, device 500A requests confirmation from the user before adding the new photo 834 to journal entry field 812.
  • the new photo e.g., new photo 834
  • device 500A when the new photo 834 is added to the journal entry field 812 (either automatically or in response to a user confirmation to add the new photo 834 to the journal entry field 812), device 500A ceases to display the camera interface 828 and optionally displays soft keyboard 821 to enable the user to add text to the journal entry field 812 (e.g., in addition to new photo 834).
  • device 500A in response to detecting an activation of virtual button 830, device 500A begins to capture a new video using a camera of device 500A. In response to detecting a subsequent activation of virtual button 830, device 500A stops recording the new video and optionally adds the new video to journal entry field 812 (this process is not shown) in a manner similar to that described above and shown in Fig. 8J.
  • Figs. 8L and 8M illustrate an example of using an audio capture application (e.g., a voice memo application or another audio capture application) to capture a new audio recording and add it to a journal entry.
  • an audio capture application e.g., a voice memo application or another audio capture application
  • the user selects audio clip icon 814d in user interface 810.
  • device 500A displays, in a region of user interface 810 (e.g., below journal entry field 812), an audio capture interface 836 a virtual button 838 for capturing a new audio recording, optionally along with other selectable options such as a recording volume option. Audio capture interface 836 is optionally displayed in the user interface of the journaling application.
  • device 500A In response to detecting a first activation of virtual button 838 (such as shown in Fig. 8L), device 500A begins to capture a new audio clip (e.g., “New Recording” shown in Fig. 8L) using a microphone of device 500A. Optionally, device 500A displays a dynamic elapsed time and/or an indication of the volume or spectral content of the audio recording as it is recorded. In response to detecting a second activation of virtual button 838, device 500A ceases to record the audio recording and optionally automatically (e.g., without additional user input) adds the new audio recording (e.g., new audio recording 840) to journal entry field 812, as shown in Fig. 8M.
  • a new audio clip e.g., “New Recording” shown in Fig. 8L
  • device 500A displays a dynamic elapsed time and/or an indication of the volume or spectral content of the audio recording as it is recorded.
  • device 500A In response to detecting a second
  • new audio recording 840 can be played back and/or deleted after it is added to journal entry field 812.
  • device 500A in response to detecting the second activation of virtual button 838 and after capturing the new audio recording, device 500A requests confirmation from the user before adding the new audio recording 840 to journal entry field 812.
  • the new audio recording can be played back from the audio capture interface 836 (e.g., before adding to the journal entry field 812).
  • device 500A when the new audio recording 840 is added to the journal entry field 812 (either automatically or in response to a user confirmation to add the new audio recording 840 to the journal entry field 812), device 500A ceases to display the audio capture interface 836 and optionally displays soft keyboard 821 to enable the user to add text to the journal entry field 812 (e.g., in addition to new audio recording 840).
  • Fig. 8N depicts an example of a timeline user interface 842 of the journaling application.
  • timeline user interface 842 is displayed in response to a selection of the journaling application icon 655 from user interface 602 and/or in response to selection of affordance 820 in the journal entry user interface 810.
  • Timeline user interface 842 displays a timeline of journal entry representations 844a-844c, such as representations of journal entries that were created using techniques described in Figs. 8A-8L.
  • Journal entry representations shown in timeline 842 optionally provide a preview of the corresponding journal entry by including representations of content items and/or text that are included in the corresponding journal entry, as depicted in journal entry representations 844a-844c.
  • journal entries optionally include photos, videos, maps, fitness activities, podcasts (e.g., the podcast itself, a portion of the podcast, a link to the podcast, art 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, art associated with the book or article), or other types of content.
  • each journal entry indication 844a- 844c is displayed with an associated date (e.g., the date associated with the journal entry).
  • timeline user interface 842 displays journal entry representations 844a-844c in chronological order, with a journal entry representation corresponding to the most recently added journal entry shown at the top of timeline user interface 842. If the user has created more journal entries than are shown in a single screen, the user can scroll down to see additional journal entry representations.
  • Timeline user interface 842 optionally includes add affordance 846, which when selected causes device 500A to display journal entry user interface 810 for adding a new journal entry.
  • journal entry representation 844a-844c in timeline user interface 842 causes device 500A to display text and/or content items associated with the journal entry in a full-screen format, in which each content item and/or textual content is displayed in a full screen and the user can navigate between screens displaying content items by providing left/right swipe inputs.
  • selecting a content item in a journal entry 844a-844c displayed in timeline user interface 842 causes device 500A to display the selected content item in a full-screen interface.
  • selecting “Song 1” content item in journal entry 844b causes device 500A to display a full-screen music interface such as described with reference to Fig. 8R.
  • Timeline user interface 842 optionally includes moments affordance 850, which when selected causes device 500A to display a moments user interface, as described with reference to Fig. 8S.
  • Fig. 80 illustrates an example of displaying a lookback selection interface 852 in timeline user interface 842.
  • device 500A in response to detecting a selection of lookback affordance 848 (shown in Fig. 8N) in timeline user interface 842, device 500A displays a lookback selection interface 852 in timeline user interface 842, optionally at the top of timeline user interface 842, such as shown in Fig. 80.
  • Lookback selection interface 852 includes one or more lookback panes with representations of one or more types of lookbacks (e.g., Birthdays, On This Day, Significant Days, Highlighted Time Period).
  • a lookback includes a collage, slideshow, animated video, or other form of visual (and optionally, audible) presentation generated by device 500A based on one or more previously created journal entries (e.g., including content items and/or text in one or more journal entries) that are associated with a particular date or event.
  • journal entries e.g., including content items and/or text in one or more journal entries
  • An “On This Day” lookback optionally includes one or more journal entries having the same month and day as the current date.
  • a “Significant Day” lookback optionally includes one or more journal entries have a date that is determined, by device 500A or by the user, to be significant, such as a date on which the user got married or started a new job.
  • a “Highlighted Time Period” lookback includes one or more journal entries having dates that have been determined by device 500A or the user to be associated with a particular period of time or multi-day event that is potentially of interest, such as “Fall in Sweden.”
  • a “Media Focus” lookback includes one or more journal entries having dates that have been determined by device 500A or the user to be associated with a particular period of time or multi-day event and that include (or reference) music and/or videos played during that time period or event.
  • a lookback has one or more of the characteristics of animated video presentation 679 described with reference to Fig. 6V and/or method 700.
  • lookback selection interface 852 includes a first lookback pane 852a associated with “Birthdays” lookbacks and a second lookback pane 856b associated with “On This Day” lookbacks.
  • lookback selection interface 852 is horizontally scrollable to navigate to additional lookback panes, such as lookback panes associated with Significant Days lookbacks and/or Highlighted Time Period lookbacks.
  • lookback panes 852a-852b are selectable to cause device 500A to display a full screen of selectable lookback representations of the selected lookback type, where each lookback option is associated with a particular lookback.
  • device 500A in response to detecting a selection of lookback pane 856a, device 500A optionally displays one or more Birthday lookback representations 857a-857c, each of which is associated with a “Birthday” lookback.
  • a user can select a particular lookback option to display the associated Birthday lookback (e.g., to play the animated video or display the collage).
  • lookback interface 858 in response to detecting a selection of affordance 854 in lookback selection interface 843 in Fig. 80, device 500A displays lookback interface 858 as shown in Fig. 8P.
  • Lookback interface 858 optionally displays lookback representations 860a- 860e that are associated with representative lookbacks of the different types of lookbacks, and optionally displays a quantity of lookbacks associated with the different types of lookbacks.
  • lookback representations 860a- 860e include content items (or representations of content items) and/or text associated with the representative lookback.
  • lookback representations 860a-860d of Fig. 8P are optionally horizontally scrollable to reveal additional lookback representations of the same lookback type.
  • horizontally scrolling lookback option 860a optionally reveals one or more additional “Birthday” lookback representations that can be selected to display the corresponding lookback.
  • lookback representations 860a-860d are selectable to cause device 500A to display the corresponding representative lookback, such as in the case when there is a single lookback associated with the selected type.
  • lookback representations 860a-860d are selectable to cause device 500A to display additional lookbacks of the same lookback type (including the representative lookback), such as in the case when there are multiple lookbacks associated with the selected type. For example, in response to detecting a selection of lookback representation 860b in Fig. 8P (corresponding to an “One This Day” lookback type, which has two associated lookbacks in the example of Fig. 8P), device 500A optionally displays lookback type user interface 862 with lookback representations 860b and 860e associated with “On This Day” lookbacks, as shown in Fig. 8Q.
  • moments and/or representations of content items are selectable to cause device 500A to display the corresponding content item(s) (or a representation of the content item) in a fullscreen interface, optionally with the ability to navigate between different content items in the moment by left/right swiping.
  • device 500A in response to detecting a selection of content item representation 818h in Fig. 8M (which is, optionally, a representation of a song, such as the title of the song, cover art associated with the song, or another type of representation), optionally displays content user interface 864, as shown in Fig. 8R.
  • Content user interface 864 includes a second content item representation 866, which may be the same as or different than content item representation 843 displayed in timeline user interface 842. In some embodiments, content item representation 866 is larger than content item representation 843.
  • Content user interface 864 optionally includes editing affordance 868, which when selected, allows the user to edit the content item included in the journal entry and represented by content item representation 866. Additionally or alternatively, selection of editing affordance 868 allows the user to edit the journal entry that includes the content item, such as to add text to the journal entry (optionally to be associated with the content item).
  • content item represented by content item representation 866 if it is playable (e.g., it is a video, an audio recording, or another type of playable content) it can be played from content user interface 864 without launching an application associated with the content item.
  • content user interface 864 includes playback affordance 870, which when selected, causes the content item represented by content item representation 866 to play (e.g., by playing Song 1, in the example of Fig. 8R) while remaining within content user interface 864.
  • content user interface 864 forgoes display of playback affordance 870 if the content item is not playable, such as if the content item is a photograph or map.
  • content user interface 864 includes application icon and/or button 872 which, when selected, causes device 500A to launch an application associated with the content item represented by content item representation 866. For example, if the content item is a song (as shown in Fig. 8R), selection of application icon 872 optionally causes device 500A to launch a music-playing application associated with the song.
  • moments affordance 850 is selectable to cause device 500A to display a moments user interface, shown in Fig. 8S.
  • Moments user interface 874 includes one or more moments 876a-876c, each of which is, optionally, associated with a moment date 884a-884c and includes text and/or representations of one or more content items (e.g., content item representations 878a-878e, 880a-880b, 882a-882d).
  • device 500A generates moments 876a-876c based on analysis of content items stored and/or accessible on device 500A, such as by identifying content items that are associated with a particular date or event that may be of interest to the user.
  • moments 876a-876c that are displayed in moment user interface 874 are moments that have not previously been journaled about by the user (e.g., are not included in a journal entry in the journaling application) and are provided to prompt the user to select a moment to journal about (e.g., to include in a journal entry).
  • moments user interface 874 includes icons or buttons 886a-886d, which are selectable to cause device 500A to select (e.g., filter) which moments and/or prompts to present in moments user interface 874.
  • device 500A displays moments that are recommended by device 500A, such as based on analysis of previous activities or indications of interests of the user.
  • device 500A displays moments that are associated with recent dates, such as dates within the last day, week, month, or year.
  • device 500A in response to selection of icon 886c, device 500A optionally displays one or more textual prompts to encourage the user to create a journal entry and provide a topic. An example of such a prompt would be “What are you pleased for today?”
  • device 500A in response to selection of icon 886d, device 500A optionally displays representations of one or more media items (e.g., books, songs, articles, podcasts, or other types of media content) that the user may wish to include in a journal entry.
  • device 500A In response to detecting a selection of a displayed moment, prompt, or representation of a media item in moments user interface 874, device 500A optionally displays journal entry user interface 810 with the selected moment, prompt or media item displayed above journal entry field 812 (e.g., as shown in Fig. 8F) or within journal entry field 812 (e.g., as shown in Fig. 8G), thereby providing a simple way for the user to journal about the selected item.
  • device 500 A in response to detecting selection of a moment 876a- 876c, displays a menu that allows the user to create a journal entry that includes the moment and/or content items in the moment, as shown in Fig. 8T.
  • device 500A in response to detecting a selection of moment 876b, displays menu 884 that includes a first selectable option 884a and a second selectable option 884b.
  • device 500a In response to detecting selection of option 884a, device 500a creates a new journal entry that includes the content items represented by content item representations 880a-880b and saves the journal entry (e.g., without the user providing additional inputs). Optionally, device 500A saves the journal entry while continuing to display moments user interface 874, without displaying journal entry user interface 810.
  • device 500a in response to detecting selection of option 884b, displays journal entry user interface 810 with the selected moment and/or content item representations 880a-880b displayed in journal entry field 812 (e.g., in a manner similar to that shown in Fig. 8G) or above journal entry field 812 (e.g., in a manner similar to that shown in Fig. 8F).
  • the user can then add text, add additional content items, or save the journal entry as described with reference to Figs. 8C-8L.
  • a user can configure the journaling application and/or device 500A to display or provide notifications (which may be referred to as “nudges”) that remind or encourage the user to create or review journal entries.
  • nudges notifications
  • a user can invoke display of a nudges user interface 886 as shown in Fig. 8U, such as from a configuration settings menu associated with the journaling application, to configure the journaling application to send reminder notifications in accordance with various criteria.
  • Nudges user interface 886 optionally includes one or more selectable options 888a-888d that can be selected, by the user, to cause device 500A to display notifications associated with the options 888a-888d. Such notifications are optionally displayed in a visual manner similar to that shown in Fig. 6V and/or described with reference to method 700, for example.
  • selection of option 888a configures device 500A to display scheduled reminder notifications in accordance with a schedule (e.g., a schedule provided by the user or determined by device 500A). For example, selection of option 888a optionally configures device 500A to display reminder notifications at a specified time daily, weekly, or monthly, or in accordance with another schedule. In some embodiments, device 500A determines, at the specified reminder notification time, whether one or more criteria are met that indicate whether the user is likely to want to receive a reminder notification at the scheduled time.
  • a schedule e.g., a schedule provided by the user or determined by device 500A.
  • selection of option 888a optionally configures device 500A to display reminder notifications at a specified time daily, weekly, or monthly, or in accordance with another schedule.
  • device 500A determines, at the specified reminder notification time, whether one or more criteria are met that indicate whether the user is likely to want to receive a reminder notification at the scheduled time.
  • device 500A optionally determines whether device 500A is operating in a notification suppression mode, or if a calendar application on device 500A indicates that the user is in a meeting, or if a telephone application indicates that the user is on a call.
  • device 500A temporarily or permanently suppresses the reminder notification in accordance with a determination that the one or more criteria are met, and optionally provides the notification later after the one or more criteria are no longer met.
  • reminder notifications optionally include saved moment notifications, lookback notifications, and/or system moment notifications described in more detail below.
  • Scheduled reminder notifications optionally include a prompt to create a journal entry and/or a suggested topic for a journal entry.
  • device 500A in response to detecting selection of a scheduled reminder notification, displays journal entry user interface 810, such as shown in Fig. 8C.
  • selection of option 888b configures device 500A to display saved moment notifications associated with moments that have been saved in a journal entry by the user (e.g., using a “quick add” function) but have not been written about by the user.
  • device 500A displays saved moment notifications associated in accordance with a schedule.
  • saved moment notifications include one or more representations of content items that are associated with one or more saved moments.
  • device 500a in response to detecting selection of a saved moment notification, displays journal entry user interface 810 with content item representations associated with the saved moment displayed in journal entry field 812 (e.g., in a manner similar to that shown in Fig. 8G). The user can then add text, add additional content items, or save the journal entry as described with reference to Figs. 8C-8M.
  • selection of option 888c configures device 500A to display lookback notifications associated with one or more existing journal entries.
  • device 500A displays lookback notifications in accordance with a schedule and/or in accordance with a determination that a journal entry is associated with the same month and day as the current month and day.
  • device 500A in response to detecting selection of a lookback notification, displays the corresponding lookback associated with one or more journal entries.
  • selection of option 888d configures device 500A to display system moment notifications associated with new moments that are generated, identified and/or saved by device 500 and have not yet been added by the user to a journal entry.
  • device 500A displays system moment notifications in accordance with a schedule and/or when one or more new moments are generated, identified, and/or saved by device 500A.
  • system moment notifications include one or more representations of related content items (e.g., content items having the same date, location, or other indication of relatedness).
  • device 500A in response to detecting selection of a system moment notification, displays a moments user interface (e.g., moments user interface 874 of Fig. 8T) that includes the system moment.
  • device 500a in response to detecting selection of a system moment notification, displays journal entry user interface 810 with content item representations associated with the system moment displayed in journal entry field 812 (e.g., in a manner similar to that shown in Fig. 8G) or above journal entry field 812 (e.g., in a manner similar to that shown in Fig. 8F).
  • the user can then add text, add additional content items, or save the journal entry as described with reference to Figs. 8C-8M.
  • device 500A displays reminders (e.g., corresponding to the above-described notifications) to create and/or review journal entries in (or in the form of) a widget associated with the journaling application.
  • reminders e.g., corresponding to the above-described notifications
  • a widget associated with the journaling application For example, in Fig. 8V, device 500A displays a prompt to journal about a moment (e.g., a saved moment or system moment that includes content items represented by content item representations 892a and 892b) in widget 890 in user interface 802 (e.g., a home screen user interface of device 500A).
  • Widget 890 includes a prompt to journal about the moment.
  • device 500a in response to detecting selection of widget 890, displays journal entry user interface 810 with content item representations 892a-892b displayed in journal entry field 812 (e.g., in a manner similar to that shown in Fig. 8G) or above journal entry field 812 (e.g., in a manner similar to that shown in Fig. 8F).
  • the user can then add text, add additional content items, or save the journal entry as described with reference to Figs. 8C-8M.
  • device 500A if device 500A identifies a saved moment notification, lookback notification, and/or system moment notification within a predetermined time period of a scheduled reminder notification, device 500A waits to display the saved moment notification, lookback notification, and/or system moment notification until the scheduled reminder time. For example, device 500A optionally batches notifications for display at a scheduled reminder time, if device 500A is configured to provide scheduled reminder notifications.
  • Fig. 9 is a flow diagram illustrating a method 900 of displaying user interfaces for journaling in accordance with some embodiments, such as in Figs. 8A-8V.
  • the method 900 is optionally performed at an electronic device such as device 100, device 300, or device 500 as described above with reference to Figs. 1 A-1B, 2-3, 4A-4B and 5A-5H.
  • Some operations in method 900 are optionally combined and/or the order of some operations is, optionally, changed.
  • the display generation component is a display integrated with the electronic device (optionally a touch screen display), external display such as a monitor, projector, television, or a hardware component (optionally integrated or external) for projecting a user interface or causing a user interface to be visible to one or more users, etc.
  • method 900 is performed at or by an automobile (e.g., at an infotainment system of an automobile having or in communication with one or more display generation components and/or input devices).
  • the electronic device displays (902a), via the display generation component, a first user interface (e.g., user interface 810 of Fig. 8C or 8E) including a a journal entry field (e.g., journal entry field 812 of Fig. 8E) for entering content into a journal entry of a journaling application (e.g., journal entry representation 844a of Fig. 8M) and a list (e.g., moment 816b of Fig.
  • a first user interface e.g., user interface 810 of Fig. 8C or 8E
  • a journal entry field e.g., journal entry field 812 of Fig. 8E
  • a list e.g., moment 816b of Fig.
  • suggested content items e.g., content items 818f-818j
  • suggested content items of the list of suggested content items are included in the list of suggested content items based at least in part on data detected by an application different from the journaling application (such as a date of the content item, a location of the content item, a person associated with the content item, an event associated with the content item, or other types of data).
  • content items 818f-818j are selected (e.g., by the electronic device) for inclusion in moment 816b because they are associated with the same date, where the date is detected by an application associated with the content item (e.g., a photo capture application, a mapping application, or another type of application).
  • the list of suggested content items includes graphical and/or textual representations of one or more of the content items, such as a photo or video thumbnail, a map thumbnail, a song or book title, an excerpt of a message (e.g., a text message or email message), an event title, a date, a name of a person, a representation of an audio signal, or another type of representation of the content item.
  • the list of suggested content items is shown within a visual boundary (e.g., within a rectangle, oval, circle, or other type of boundary) to indicate that the content items are part of the list of suggested content items.
  • the list of suggested content items includes and/or is displayed with a date associated with the list of suggested content items, such as the date “December 7, 2022” associated with moment 816b in Fig. 8E and displayed as part of moment 816b.
  • the date is optionally a date on which one or more of the content items occurred, were captured, were shared (e.g., either to the user of the electronic device or by the user of the electronic device), and/or with which the content items are otherwise associated.
  • the electronic device while displaying the first user interface including the list of suggested content items for inclusion in the journal entry of the journaling application, such as suggested moments 816b and 816c in Fig. 8E, the electronic device receives (902b), via the one or more input devices, an input directed to the list of suggested content for inclusion in the journal entry of the journaling application, such as a touch contact input, a button input, a voice input, or another type of input selecting suggested moment 816b in Fig. 8E.
  • an input directed to the list of suggested content for inclusion in the journal entry of the journaling application such as a touch contact input, a button input, a voice input, or another type of input selecting suggested moment 816b in Fig. 8E.
  • the electronic device in response to receiving the input directed to the list of suggested content items for inclusion in the journal entry of the journaling application, displays (902c) representations of the suggested content items in a content entry region concurrently with displaying the journal entry field, such as illustrated with representations of content items in suggested moment 816b being displayed in content entry region 817 of Fig. 8G above journal entry field 812 (e.g., while journal entry field 812 is concurrently displayed).
  • the electronic device in response to receiving the input directed to the list of suggested content items for inclusion in the journal entry of the journaling application, the electronic device ceases to display the list of suggested content items (e.g., ceases to display moment 816b below the journal entry field).
  • the electronic device concurrently displays, via the display generation component: the first user interface including the journal entry field and the list of suggested content items for inclusion in the journal entry of the journaling application, such as suggested moments 816b and 816c in Fig. 8E, and a navigation user interface including a plurality of selectable user interface elements (e.g., a navigation user interface that includes icons 814b through 814e of Fig.
  • thumbnails of the user’s photos e.g., below journal entry field 812
  • the electronic device receives an input selecting camera icon 814b of Fig. 8E.
  • the electronic device ceases to display suggested moments 816b and 816c in Fig. 8E and displays, as illustrated in Fig.
  • a camera interface 828 having a preview pane 832 for displaying a live view from a camera of the device, and including a virtual button 830 for capturing a photo or video for inclusion in journal entry field 812.
  • the electronic device in response to detecting a selection of one of the selectable user interface elements (e.g., icons 814a-814e), the electronic device ceases to display a keyboard (e.g., keyboard 821 of Fig. 8F) and/or replaces display of a keyboard with display of the content of the respective type.
  • a keyboard e.g., keyboard 821 of Fig. 8F
  • displaying representations of the suggested content items in the content entry region of the journaling application includes displaying a representation of the first content item and a representation of the second content item in the content entry region (optionally, along with other content items from the same moment, such as content items 818h, 818i, and 818j) in the content entry region, such as representations of content items 818f and 818g in Fig. 8F being displayed in the content entry region 817 of the user interface 810 as described above with reference to Fig. 8F.
  • the device after displaying the representation of the first content item and the representation of the second content item in the content entry region, detecting, via the one or more input devices, a second input requesting to remove the first content item from the content entry region (e.g., to exclude the first content item from being added to the journal entry field), such as an input selecting content item 818g in Fig. 8F for removal as illustrated with the checked box in content item 818g.
  • the device in response to detecting the second input requesting to remove the first content item from the content entry region, the device ceases to display the representation of the first content item in the content entry region without ceasing to display (e.g., while maintaining display of) the representation of the second content in the content entry region.
  • the user can optionally remove some or all of the content items from the content entry region before adding the (remaining) content items in the content entry region to the journal entry.
  • the electronic device detects a user input corresponding to a request to add content items of moment 816b to journal entry field 812 while content items 818g, 818i, and 818, are marked for exclusion (or optionally have already been removed from content entry region 817).
  • the electronic device displays representations of content items 818f and 818h in journal entry field 812 as shown in Fig. 8H, and optionally ceases to display content items 818f-818j in content entry region 817, and/or ceases to display content entry region 817.
  • the electronic device after displaying representations of content items in the journal entry field 812, the electronic device detects a selection of an affordance (e.g., affordance 820 in Fig. 8G), and in response to detecting the selection of the affordance, saves the content that is displayed in the journal entry field (e.g., text content and/or content items) as a journal entry (e.g., to the journaling application).
  • the device saves the journal entry locally and/or remotely.
  • the first content item is a first type and the second content item is a second type different from the first type, such as content item 818f of Fig. 8E being (or representing) a photo and content item 818g of Fig. 8E being (or representing) an audio clip.
  • the electronic device displays, via the display generation component, a selectable user interface element for displaying the list of suggested content for inclusion in the journal entry of the journaling application, such as by displaying affordance 808d in user interface 806 of Fig. 8B.
  • the electronic device detects, via the one or more input devices, an input directed to the selectable user interface element for displaying the list of suggested content for inclusion in the journal entry of the journaling application, such as by detecting a selection of affordance 808d of Fig.
  • the electronic device in response to detecting the input directed to the selectable user interface element for displaying the list of suggested content for inclusion in the journal entry of the journaling application, displays, via the display generation component, the first user interface including the list of suggested content for inclusion in the journal entry of the journaling application, such as by displaying journal user interface 810 and suggested moment 816a of Fig. 8C.
  • the first user interface consumes a first display area in accordance with a determination that one or more first criteria is satisfied, such as the display area of suggested moment 816a of Fig. 8C. In some embodiments, the first user interface consumes a second display area, greater than the first display area, in accordance with a determination that one or more second criteria are satisfied, such as the display area consumed by suggested moments 816b and 816c in Fig. 8E, which is greater than the display area of suggested moment 816a of Fig. 8C.
  • the device optionally expands the area consumed by journal entry field 812 (and therefore the area consumed by the first user interface) in accordance with a determination that an amount of text entered into journal 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.
  • a threshold amount of text such as greater than 2, 3, 5, 8, 10, 20, or 30 lines of text.
  • the device while displaying a second list of suggested content items including second content items (optionally, while the journal user interface is not displayed), receives, via the one or more input devices, an input directed to the second list of suggested content items (e.g., a touch or tap on the second list of suggested content items, or another type of input).
  • an input directed to the second list of suggested content items e.g., a touch or tap on the second list of suggested content items, or another type of input.
  • the device in response to receiving the second input directed to the second list of suggested content items for inclusion in the journal entry of the journaling application, and in accordance with a determination that one or more first criteria are satisfied, saves (e.g., generates and/or stores) the second content items in a journal entry of the journal application without initiating a process to add further content to the journal entry of the journaling application.
  • the device in response to receiving the second input directed to the second list of suggested content items for inclusion in the journal entry of the journaling application, and in accordance with a determination that one or more second criteria, different from the one or more first criteria, are satisfied, displays representations of the second content items in the content entry region of the journal user interface (and optionally launches the journal user interface, if it is not already displayed).
  • the first suggested content is optionally moment 876b of Fig. 8T, and when the one or more second criteria are satisfied, which optionally include a criterion that is satisfied when the electronic device detects input selecting second selectable option 884a of Fig.
  • method 1000 is performed at an electronic device in communication with a display generation component and one or more input devices.
  • a mobile device e.g., a tablet, a smartphone, a media player, or a wearable device
  • wireless communication circuitry optionally in communication with one or more of a mouse (e.g., external), trackpad (optionally integrated or external), touchpad (optionally integrated or external), 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.).
  • a mouse e.g., external
  • trackpad optionally integrated or external
  • touchpad optionally integrated or external
  • remote control device e.g., external
  • another mobile device e.g., separate from the electronic device
  • a handheld device e.g., external
  • a controller e.g., external
  • the display generation component is a display integrated with the electronic device (optionally a touch screen display), external display such as a monitor, projector, television, or a hardware component (optionally integrated or external) for projecting a user interface or causing a user interface to be visible to one or more users, etc.
  • method 1000 is performed at or by an automobile (e.g., at an infotainment system of an automobile having or in communication with one or more display generation components and/or input devices).
  • the electronic device displays (1002a), via the display generation component, a first user interface of a journaling application including a list of journal entries associated with a user (e.g., journal entries generated and/or saved by the user in the journaling application, such as while logged in to the journaling application), such as timeline of journal entry representations 844a-844c in timeline user interface 842 of Fig. 8N and a first selectable user interface element for displaying one or more lookbacks, such as lookback affordance 848 in timeline user interface 842 of Fig. 8N.
  • a first user interface of a journaling application including a list of journal entries associated with a user (e.g., journal entries generated and/or saved by the user in the journaling application, such as while logged in to the journaling application), such as timeline of journal entry representations 844a-844c in timeline user interface 842 of Fig. 8N and a first selectable user interface element for displaying one or more lookbacks, such as lookback affordance 848 in timeline user interface 8
  • the electronic device while displaying the first user interface of the journaling application including the list of journal entries associated with the user and the first selectable user interface element for displaying one or more lookbacks, the electronic device receives (1002b), via the one or more input devices, an input (e.g., a touch, tap, click, or other input) directed to the first selectable user interface element, such as an input selecting lookback affordance 848 in timeline user interface 842 of Fig. 8N.
  • an input e.g., a touch, tap, click, or other input
  • the electronic device in response to receiving the input directed to the first selectable user interface element, displays (1002c), via the display generation component, a set of one or more lookbacks, such as first lookback pane 856a associated with a set of “Birthdays” lookbacks 857a-857c in Fig. 80 or second lookback pane 856b associated with an “On This Day” lookback 857d.
  • a set of one or more lookbacks such as first lookback pane 856a associated with a set of “Birthdays” lookbacks 857a-857c in Fig. 80 or second lookback pane 856b associated with an “On This Day” lookback 857d.
  • the set of one or more lookbacks are associated with one or more journal entries that satisfy a criterion that is satisfied when a date associated with the one or more journal entries is within a range of dates (e.g., a range between two dates, or a range of a single date, which can include the month, day, and/or year).
  • a range of dates e.g., a range between two dates, or a range of a single date, which can include the month, day, and/or year.
  • the electronic device in response to detecting selection of lookback representation 860b in Fig. 8P, the electronic device optionally displays a lookback type user interface 862 of Fig. 8Q with lookback representations associated with the current month and day (“On This Day”).
  • the set of one or more lookbacks are associated with one or more journal entries that satisfy a criterion that is satisfied when a date associated with the one or more journal entries is an annual date, such as lookback type user interface 862 with lookback representations 860b and 860e associated with “On This Day” lookbacks in Fig. 8P and/or a lookback type user interface including lookback representations associated with “Birthdays” lookback.
  • the set of one or more lookbacks are associated with one or more journal entries that satisfy a criterion that is satisfied when a type of content of the journal entries is media content.
  • a lookback representation such as lookback representation 860e of Fig. 8P
  • journal entries associated with (e.g., that include or reference) music and/or videos played by the user over the specific time period, such as over a most recent summer.
  • the electronic device in response to detecting selection of the lookback representation 860e, the electronic device optionally displays a lookback type user interface 862 of Fig. 8Q, but with representations of music and/or video content that the user played the over the time period (e.g., the most recent summer) and with a heading associated with the time period, such as “Music Over the Summer” (instead of “On This Day”).
  • displaying, via the display generation component, the set of journal entries that satisfy the one or more first criteria includes displaying, via the display generation component: in a first portion, a first set of one or more lookbacks that satisfy a criterion that is satisfied when a date associated with one or more journal entries corresponding to the first set of one or more lookbacks is a first date or is within a first range of dates, such as lookback representation 860a in Fig.
  • aspects/operations of methods 700, 900, and/or 1000 may be interchanged, substituted, and/or added between these methods.
  • journaling application of methods 700, 900, and/or 1000 are optionally interchanged, substituted, and/or added between these methods.
  • these details are not repeated here.
  • this gathered data may include personal information data that uniquely identifies or can be used to identify a specific person.
  • personal information data can include demographic data, location-based data, online identifiers, telephone numbers, email addresses, home addresses, data or records relating to a user’s health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other personal information.
  • the present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users.
  • the personal information data can be used to detect activity events. Accordingly, use of such personal information data enables users to be prompted with activity events to create journaling entries.
  • other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used, in accordance with the user’s preferences to provide insights into their general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.
  • the present disclosure contemplates that those entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices.
  • such entities would be expected to implement and consistently apply privacy practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
  • Such information regarding the use of personal data should be prominent and easily accessible by users, and should be updated as the collection and/or use of data changes.
  • Personal information from users should be collected for legitimate uses only. Further, such collection/sharing should occur only after receiving the consent of the users or other legitimate basis specified in applicable law.
  • policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations that may serve to impose a higher standard. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health
  • the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data.
  • the present technology can be configured to allow users to select to "opt in” or "opt out” of participation in the collection of personal information data during registration for services or anytime thereafter.
  • users can select not to provide personal data and/or device or object location data.
  • users can select to limit the length of time personal data and/or device or object location data is maintained or entirely block the development of a baseline location profile.
  • the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an application that their personal information data and/or location data will be accessed and then reminded again just before personal information data is accessed by the application.
  • data de-identification can be used to protect a user’s privacy. De-identification may be facilitated, when appropriate, by removing identifiers, controlling the amount or specificity of data stored (e.g., collecting location data at city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods such as differential privacy.
  • the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, location data and notifications can be delivered to users based on aggregated non-personal information data or a bare minimum amount of personal information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Business, Economics & Management (AREA)
  • Data Mining & Analysis (AREA)
  • Human Resources & Organizations (AREA)
  • Databases & Information Systems (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

Dans certains modes de réalisation, un dispositif électronique détecte un événement d'activité associé à un utilisateur du dispositif électronique et affiche une invite qui permet la création d'une entrée de journalisation sur la base de l'événement d'activité, affiche un contenu suggéré pour une inclusion dans une entrée de journal d'une application de journalisation, et/ou affiche une ou plusieurs consultations.
EP23735909.6A 2022-06-05 2023-06-04 Interfaces utilisateur pour créer des entrées de journalisation Pending EP4537280A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202263365875P 2022-06-05 2022-06-05
US202363483263P 2023-02-03 2023-02-03
US202363503759P 2023-05-23 2023-05-23
PCT/US2023/024389 WO2023239625A1 (fr) 2022-06-05 2023-06-04 Interfaces utilisateur pour créer des entrées de journalisation

Publications (1)

Publication Number Publication Date
EP4537280A1 true EP4537280A1 (fr) 2025-04-16

Family

ID=94192407

Family Applications (1)

Application Number Title Priority Date Filing Date
EP23735909.6A Pending EP4537280A1 (fr) 2022-06-05 2023-06-04 Interfaces utilisateur pour créer des entrées de journalisation

Country Status (2)

Country Link
EP (1) EP4537280A1 (fr)
CN (2) CN119317932A (fr)

Also Published As

Publication number Publication date
CN119317932A (zh) 2025-01-14
CN120653166A (zh) 2025-09-16

Similar Documents

Publication Publication Date Title
US12477061B2 (en) Providing user interfaces based on use contexts and managing playback of media
US11095946B2 (en) User interfaces for recommending and consuming content on an electronic device
AU2019266054B2 (en) User interfaces for sharing contextually relevant media content
JP2019215874A (ja) 文脈的関連メディアコンテンツを検索するためのユーザインタフェース
US12278918B2 (en) Utilizing context information with an electronic device
US12602142B2 (en) User interfaces for sharing contextually relevant media content
WO2022165279A1 (fr) Interfaces utilisateur et systèmes et procédés associés pour partager des parties d'éléments de contenu
US20240264719A1 (en) User interfaces for creating journaling entries
AU2023208169B2 (en) User interfaces for sharing contextually relevant media content
EP4407426B1 (fr) Mise à disposition de verrouillage de capture multimédia pour interface utilisateur graphique
WO2023239677A1 (fr) Recherche d'arrêts dans des itinéraires à arrêts multiples
US20240152267A1 (en) User interfaces for creating journaling entries
CN110456948A (zh) 用于推荐和消费电子设备上的内容的用户界面
US20250130697A1 (en) User interfaces for collaborative content playlists
WO2023239623A1 (fr) Interfaces utilisateur pour un contenu de messagerie
CN120653166A (zh) 用于创建日志记录条目的用户界面
US12041287B2 (en) User interfaces and associated systems and processes for accessing content items via content delivery services
WO2025264419A1 (fr) Techniques de gestion d'événements
CN121444056A (zh) 用于移动设备上的内容项的用户界面

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20241129

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)