User interface for enabling activities

Abstract

The present disclosure generally relates to user interfaces for enabling activities. In some embodiments, an exemplary user interface for invoking an activity associated with an application is described. In some embodiments, an exemplary user interface for customizing displayed content based on the circumstances in which the content is invoked is described. In some embodiments, an exemplary user interface for managing applications for enabling activities is described. In some embodiments, an exemplary user interface for managing settings for applications for enabling activities is described.

Description

[0001] This case is a divisional application of the application with international application number PCT / US2021 / 025051, international application date of March 31, 2021, entry into the Chinese national phase date of December 1, 2022, national application number 202180040304.9, and invention title "User Interface for Enabling Activities".

[0002] Cross-references to related applications

[0003] This application claims U.S. Provisional Application Serial No. 63 / 008,586, filed April 10, 2020, entitled “USER INTERFACES FOR ENABLING AN ACTIVITY”; U.S. Provisional Application Serial No. 63 / 022,869, filed May 11, 2020, entitled “USER INTERFACES FOR ENABLING AN ACTIVITY”; U.S. Provisional Application Serial No. 63 / 032,970, filed June 1, 2020, entitled “USER INTERFACES FOR ENABLING AN ACTIVITY”; Danish Patent Application Serial No. PA202070633, filed September 23, 2020, entitled “USER INTERFACES FOR ENABLING AN ACTIVITY”; and Danish Patent Application Serial No. PA202070633, filed September 23, 2020, entitled “USER INTERFACES FOR ENABLING AN ACTIVITY”. Priority is claimed in Danish patent application serial number PA202070634 concerning “ACTIVITY”. The contents of these patent applications are incorporated herein by reference in their entirety. Technical Field

[0004] This disclosure relates in general to computer user interfaces, and more specifically to techniques for enabling activities using a computer system. Background Technology

[0005] A computer system may include applications installed on the computer system. Installed applications can be used on the computer system to perform operations. Applications not available on the computer system may be downloaded and installed (such as from an application store accessible on the computer system). Summary of the Invention

[0006] However, some technologies used to enable activity using computer systems (e.g., electronic devices) are often cumbersome and inefficient. For example, some existing technologies use complex and time-consuming user interfaces that may involve multiple keystrokes or button presses. These technologies require more time than necessary, resulting in wasted user time and device power. This latter consideration is particularly important in battery-powered computer systems.

[0007] Therefore, this technology provides computer systems with faster and more efficient methods and interfaces for enabling activities. Such methods and interfaces optionally complement or replace other methods for enabling activities. These methods and interfaces reduce the cognitive burden on users and result in more efficient human-computer interfaces. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charging. These methods and interfaces also provide quick, efficient, and easy access to perform activities using the computer system. These methods and interfaces also inform users that the computer system is available to perform activities that the user may not yet be aware of.

[0008] According to some embodiments, a method is described that executes at a computer system communicating with a display generation component and one or more input devices. The method includes: detecting the occurrence of a trigger condition for initiating an activity associated with a first application; in response to detecting the occurrence of the trigger condition, displaying a first user interface via the display generation component, wherein displaying the first user interface includes simultaneously displaying: a description of the activity and a first optional user interface object for taking an action associated with the activity; while displaying the first user interface, detecting activation of the first optional user interface object via the one or more input devices; and in response to detecting activation of the first optional user interface object: based on a determination that the first application is unavailable on the computer system, displaying via the display generation component a second user interface configured to perform the activity without downloading at least a portion of the first application.

[0009] According to some embodiments, a non-transitory computer-readable storage medium is described, which stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices. The one or more programs include instructions for performing the following operations: detecting the occurrence of a trigger condition for initiating an activity associated with a first application; in response to detecting the occurrence of the trigger condition, displaying a first user interface via the display generation component, wherein displaying the first user interface includes simultaneously displaying: a description of the activity and a first optional user interface object for taking an action associated with the activity; detecting activation of the first optional user interface object via the one or more input devices while displaying the first user interface; and in response to detecting activation of the first optional user interface object: based on a determination that the first application is unavailable on the computer system, displaying via the display generation component a second user interface configured to perform the activity without downloading at least a portion of the first application.

[0010] According to some embodiments, a transient computer-readable storage medium is described, which stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices. The one or more programs include instructions for performing the following operations: detecting the occurrence of a trigger condition for initiating an activity associated with a first application; displaying a first user interface via the display generating component in response to detecting the occurrence of the trigger condition, wherein displaying the first user interface includes simultaneously displaying: a description of the activity and a first optional user interface object for taking an action associated with the activity; detecting activation of the first optional user interface object via the one or more input devices while displaying the first user interface; and, in response to detecting activation of the first optional user interface object: displaying a second user interface via the display generating component, configured to perform the activity without downloading at least a portion of the first application, based on a determination that the first application is unavailable on the computer system.

[0011] According to some embodiments, a computer system is described, the computer system including a display generation component, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for performing the following operations: detecting the occurrence of a trigger condition for initiating an activity associated with a first application; in response to detecting the occurrence of the trigger condition, displaying a first user interface via the display generation component, wherein displaying the first user interface includes simultaneously displaying: a description of the activity and a first optional user interface object for taking an action associated with the activity; detecting activation of the first optional user interface object via the one or more input devices while displaying the first user interface; and in response to detecting activation of the first optional user interface object: based on a determination that the first application is unavailable on the computer system, displaying a second user interface via the display generation component, configured to perform the activity without downloading at least a portion of the first application.

[0012] According to some embodiments, a computer system is described. The computer system includes: a display generation component; one or more input devices; means for performing the following operations: detecting the occurrence of a trigger condition for initiating an activity associated with a first application; means for performing the following operations: in response to detecting the occurrence of the trigger condition, displaying a first user interface via the display generation component, wherein displaying the first user interface includes simultaneously displaying: a description of the activity and a first optional user interface object for taking an action associated with the activity; means for performing the following operations: while displaying the first user interface, detecting activation of the first optional user interface object via the one or more input devices; and means for performing the following operations: in response to detecting activation of the first optional user interface object: based on a determination that the first application is unavailable on the computer system, displaying via the display generation component a second user interface configured to perform the activity without downloading at least a portion of the first application.

[0013] According to some embodiments, a method is described that is executed at a computer system communicating with a display generation component and one or more input devices. The method includes: detecting a request to invoke a first application via the one or more input devices; and, in response to detecting the request to invoke the first application, displaying a first user interface corresponding to the first application via the display generation component, wherein: based on a determination that a request to invoke the first application has occurred in a first context, displaying the first user interface includes first content in a corresponding area of ​​the first user interface; and based on a determination that a request to invoke the first application has occurred in a second context different from the first context, displaying the first user interface includes second content in a corresponding area of ​​the first user interface, wherein the second content is different from the first content.

[0014] According to some embodiments, a non-transitory computer-readable storage medium is described, which stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices. The one or more programs include instructions for performing the following operations: detecting a request to invoke a first application via the one or more input devices; and, in response to detecting the request to invoke the first application, displaying a first user interface corresponding to the first application via the display generation component, wherein: based on a determination that a request to invoke the first application has occurred in a first context, displaying the first user interface includes first content in a corresponding area of ​​the first user interface; and based on a determination that a request to invoke the first application has occurred in a second context different from the first context, displaying the first user interface includes second content in a corresponding area of ​​the first user interface, wherein the second content is different from the first content.

[0015] According to some embodiments, a transient computer-readable storage medium is described, which stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices. The one or more programs include instructions for performing the following operations: detecting a request to invoke a first application via the one or more input devices; and, in response to detecting the request to invoke the first application, displaying a first user interface corresponding to the first application via the display generation component, wherein: based on a determination that a request to invoke the first application has occurred in a first context, displaying the first user interface includes first content in a corresponding area of ​​the first user interface; and based on a determination that a request to invoke the first application has occurred in a second context different from the first context, displaying the first user interface includes second content in a corresponding area of ​​the first user interface, wherein the second content is different from the first content.

[0016] According to some embodiments, a computer system is described, the computer system including a display generation component, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for performing the following operations: detecting a request to invoke a first application via the one or more input devices; and, in response to detecting the request to invoke the first application, displaying a first user interface corresponding to the first application via the display generation component, wherein: based on a determination that a request to invoke the first application has occurred in a first context, displaying the first user interface includes displaying first content in a corresponding area of ​​the first user interface; and based on a determination that a request to invoke the first application has occurred in a second context different from the first context, displaying the first user interface includes displaying second content in a corresponding area of ​​the first user interface, wherein the second content is different from the first content.

[0017] According to some embodiments, a computer system is described. The computer system includes: a display generation component; one or more input devices; means for performing the following operations: detecting a request to invoke a first application via the one or more input devices; and means for performing the following operations: in response to detecting the request to invoke the first application, displaying a first user interface corresponding to the first application via the display generation component, wherein: based on a determination that a request to invoke the first application has occurred in a first context, displaying the first user interface includes displaying first content in a corresponding area of ​​the first user interface; and based on a determination that a request to invoke the first application has occurred in a second context different from the first context, displaying the first user interface includes displaying second content in a corresponding area of ​​the first user interface, wherein the second content is different from the first content.

[0018] According to some embodiments, a method is described that is executed at a computer system communicating with a display generation component and one or more input devices. The method includes: accumulating, over a period of time, a plurality of automatically downloaded applications to assist in performing a context-dependent task, wherein the plurality of applications includes a first application having first usage information and a second application having second usage information; after the plurality of applications have been automatically downloaded, receiving, via the one or more input devices, a request to display a representation of the automatically downloaded applications available on the computer system; and in response to receiving the request, displaying, via the display generation component, a user interface for accessing the automatically downloaded applications, wherein the user interface provides access to a subset of the plurality of automatically downloaded applications, excluding one or more applications that do not meet corresponding usage criteria, wherein: based on a determination that the first usage information meets the corresponding usage criteria, the subset of the plurality of automatically downloaded applications includes the first application; based on a determination that the first usage information does not meet the corresponding usage criteria, the subset of the plurality of automatically downloaded applications excludes the first application; based on a determination that the second usage information meets the corresponding usage criteria, the subset of the plurality of automatically downloaded applications includes the second application; and based on a determination that the second usage information does not meet the corresponding usage criteria, the subset of the plurality of automatically downloaded applications excludes the second application.

[0019] According to some embodiments, a non-transitory computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices. The one or more programs include instructions for performing the following operations: accumulating, over a period of time, a plurality of automatically downloaded applications to assist in performing a context-dependent task, wherein the plurality of applications includes a first application having first usage information and a second application having second usage information; after the plurality of applications have been automatically downloaded, receiving, via the one or more input devices, a request to display a representation of the automatically downloaded applications available on the computer system; and in response to receiving the request, displaying, via a display generation component, a user interface for accessing the automatically downloaded applications, wherein the user interface provides access to a subset of the plurality of automatically downloaded applications, excluding one or more applications that do not meet a corresponding usage criterion, wherein: based on a determination that the first usage information meets the corresponding usage criterion, the subset of the plurality of automatically downloaded applications includes the first application; based on a determination that the first usage information does not meet the corresponding usage criterion, the subset of the plurality of automatically downloaded applications excludes the first application; based on a determination that the second usage information meets the corresponding usage criterion, the subset of the plurality of automatically downloaded applications includes the second application; and based on a determination that the second usage information does not meet the corresponding usage criterion, the subset of the plurality of automatically downloaded applications excludes the second application.

[0020] According to some embodiments, a transient computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices. The one or more programs include instructions for performing the following operations: accumulating, over a period of time, a plurality of automatically downloaded applications to assist in performing a context-dependent task, wherein the plurality of applications includes a first application having first usage information and a second application having second usage information; after the plurality of applications have been automatically downloaded, receiving, via the one or more input devices, a request to display a representation of the automatically downloaded applications available on the computer system; and in response to receiving the request, displaying, via a display generation component, a user interface for accessing the automatically downloaded applications, wherein the user interface provides access to a subset of the plurality of automatically downloaded applications, excluding one or more applications that do not meet a corresponding usage criterion, wherein: based on a determination that the first usage information meets the corresponding usage criterion, the subset of the plurality of automatically downloaded applications includes the first application; based on a determination that the first usage information does not meet the corresponding usage criterion, the subset of the plurality of automatically downloaded applications excludes the first application; based on a determination that the second usage information meets the corresponding usage criterion, the subset of the plurality of automatically downloaded applications includes the second application; and based on a determination that the second usage information does not meet the corresponding usage criterion, the subset of the plurality of automatically downloaded applications excludes the second application.

[0021] According to some embodiments, a computer system is described, the computer system including a display generation component, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for performing the following operations: accumulating, over a period of time, a plurality of automatically downloaded applications to assist in performing a context-dependent task, wherein the plurality of applications includes a first application having first usage information and a second application having second usage information; after the plurality of applications have been automatically downloaded, receiving, via the one or more input devices, a request to display a representation of the automatically downloaded applications available on the computer system; and in response to receiving the request, displaying, via a display generation component, a user interface for accessing the automatically downloaded applications, wherein the user interface provides access to a subset of the plurality of automatically downloaded applications, excluding one or more applications that do not meet a corresponding usage criterion, wherein: based on a determination that the first usage information meets the corresponding usage criterion, the subset of the plurality of automatically downloaded applications includes the first application; based on a determination that the first usage information does not meet the corresponding usage criterion, the subset of the plurality of automatically downloaded applications excludes the first application; based on a determination that the second usage information meets the corresponding usage criterion, the subset of the plurality of automatically downloaded applications includes the second application; and based on a determination that the second usage information does not meet the corresponding usage criterion, the subset of the plurality of automatically downloaded applications excludes the second application.

[0022] According to some embodiments, a computer system is described. The computing system includes: a display generation component; one or more input devices; means for performing the following operations: accumulating, over a period of time, a plurality of automatically downloaded applications to assist in performing a context-dependent task, wherein the plurality of applications includes a first application having first usage information and a second application having second usage information; means for performing the following operations: after the plurality of applications have been automatically downloaded, receiving via the one or more input devices a request to display a representation of the automatically downloaded applications available on the computer system; and means for performing the following operations: in response to receiving the request, displaying via the display generation component a user interface for accessing the automatically downloaded applications, wherein the user interface provides access to a subset of the plurality of automatically downloaded applications, excluding one or more applications that do not meet corresponding usage criteria, wherein: based on a determination that the first usage information meets the corresponding usage criteria, the subset of the plurality of automatically downloaded applications includes the first application; based on a determination that the first usage information does not meet the corresponding usage criteria, the subset of the plurality of automatically downloaded applications excludes the first application; based on a determination that the second usage information meets the corresponding usage criteria, the subset of the plurality of automatically downloaded applications includes the second application; and based on a determination that the second usage information does not meet the corresponding usage criteria, the subset of the plurality of automatically downloaded applications excludes the second application.

[0023] According to some embodiments, a method is described that is executed at a computer system communicating with one or more input devices. The method includes: detecting the occurrence of a triggering condition for initiating activity associated with a first application; when the first application is not installed on the computer system: installing a second application on the computer system and based on the detected triggering condition, the second application being configured to perform activity without downloading at least a portion of the first application; and setting one or more system permissions for the second application; after setting the one or more system permissions for the second application, installing the first application on the computer system; and after installing the first application on the computer system: setting one or more system permissions for the first application based on the one or more system permissions for the second application, based on a determination that the second application was installed on the computer system when the first application was installed; and setting the one or more system permissions for the first application based on default system permissions, based on a determination that the second application was not installed on the computer system when the first application was installed.

[0024] According to some embodiments, a non-transitory computer-readable storage medium is described, which stores one or more programs configured to be executed by one or more processors of a computer system communicating with one or more input devices. The one or more programs include instructions for performing the following operations: detecting the occurrence of a triggering condition for initiating activity associated with a first application; when the first application is not installed on the computer system: installing a second application on the computer system and based on the detected triggering condition, the second application being configured to perform activity without downloading at least a portion of the first application; and setting one or more system permissions for the second application; after setting the one or more system permissions for the second application, installing the first application on the computer system; and after installing the first application on the computer system: setting one or more system permissions for the first application based on the one or more system permissions for the second application, based on a determination that the second application was installed on the computer system when the first application was installed; and setting the one or more system permissions for the first application based on default system permissions, based on a determination that the second application was not installed on the computer system when the first application was installed.

[0025] According to some embodiments, a transient computer-readable storage medium is described, the transient computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system communicating with one or more input devices. The one or more programs include instructions for performing the following operations: detecting the occurrence of a triggering condition for initiating activity associated with a first application; when the first application is not installed on the computer system: installing a second application on the computer system and based on the detected triggering condition, the second application being configured to perform activity without downloading at least a portion of the first application; and setting one or more system permissions for the second application; after setting the one or more system permissions for the second application, installing the first application on the computer system; and after installing the first application on the computer system: setting one or more system permissions for the first application based on the one or more system permissions for the second application, based on a determination that the second application was installed on the computer system when the first application was installed; and setting the one or more system permissions for the first application based on default system permissions, based on a determination that the second application was not installed on the computer system when the first application was installed.

[0026] According to some embodiments, a computer system is described, the computer system including one or more input devices, one or more processors, and memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for performing the following operations: detecting the occurrence of a trigger condition for initiating activity associated with a first application; when the first application is not installed on the computer system: installing a second application on the computer system and based on the detected trigger condition, the second application being configured to perform activity without downloading at least a portion of the first application; and setting one or more system permissions for the second application; after setting the one or more system permissions for the second application, installing the first application on the computer system; and after installing the first application on the computer system: setting one or more system permissions for the first application based on the one or more system permissions for the second application, based on a determination that the second application was installed on the computer system when the first application was installed; and setting the one or more system permissions for the first application based on default system permissions, based on a determination that the second application was not installed on the computer system when the first application was installed.

[0027] According to some embodiments, a computer system is described. The computer system includes: means for performing the following operations: detecting the occurrence of a triggering condition for initiating activity associated with a first application; means for performing the following operations: when the first application is not installed on the computer system: installing a second application on the computer system and based on the detected triggering condition, the second application being configured to perform activities without downloading at least a portion of the first application; and setting one or more system permissions for the second application; means for performing the following operations: after setting the one or more system permissions for the second application, installing the first application on the computer system; and after installing the first application on the computer system, means for performing the following operations: setting one or more system permissions for the first application based on the one or more system permissions for the second application, based on a determination that the second application was installed on the computer system when the first application was installed; and setting the one or more system permissions for the first application based on default system permissions, based on a determination that the second application was not installed on the computer system when the first application was installed.

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

[0029] Therefore, faster and more efficient methods and interfaces are provided for devices to enable activities, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. These methods and interfaces can complement or replace other methods used to enable activities. Attached Figure Description

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

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

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

[0033] Figure 2 A portable multi-functional device with a touchscreen is shown according to some embodiments.

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

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

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

[0037] Figure 5A A personal electronic device according to some implementation schemes is shown.

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

[0039] Figure 6 An exemplary device connected via one or more communication channels according to some implementation schemes is shown.

[0040] Figures 7A to 7AZAn exemplary user interface for invoking activities associated with an application, according to some implementation schemes, is shown.

[0041] Figures 8A to 8B This is a flowchart illustrating a method for using computer system calls to associate activities with an application, according to some implementation schemes.

[0042] Figures 9A to 9T An exemplary user interface is shown, according to some implementation schemes, for customizing content displayed based on a call.

[0043] Figures 10A to 10C This is a flowchart illustrating a method for customizing content based on the content displayed using computer system calls, according to some implementation schemes.

[0044] Figures 11A to 11S An exemplary user interface for managing applications used to enable activities is shown according to some implementation schemes.

[0045] Figures 12A to 12D This is a flowchart illustrating a method for managing applications that enable activities using a computer system, according to some implementation schemes.

[0046] Figures 13A to 13V An exemplary user interface for managing settings of applications that enable activities using a computer system, according to some implementation schemes, is shown.

[0047] Figures 14A to 14B This is a flowchart illustrating a method for managing settings for applications that enable activities using a computer system, according to some implementation schemes. Detailed Implementation

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

[0049] Electronic devices are needed that provide efficient methods and interfaces for enabling activities. For example, there is a need for electronic devices that can suggest or enable activities corresponding to applications not installed on or available on the electronic device. Another example is the need for electronic devices that can initiate activities corresponding to applications not installed on or available on the electronic device, even when those applications are not installed. Yet another example is the need for quick and easy access to download and install the application used for the activity when it is not installed or available on the electronic device. Such technologies can reduce the cognitive burden on users accessing activities using electronic devices, thereby increasing productivity. Furthermore, such technologies can reduce processor and battery power wasted otherwise on redundant user input.

[0050] under, Figures 1A to 1B , Figure 2 , Figure 3 , Figures 4A to 4B and Figures 5A to 5B A description of an exemplary device for implementing technologies used to enable activities is provided. Figure 6 An exemplary device connected via one or more communication channels according to some implementation schemes is shown. Figures 7A to 7AZ An exemplary user interface for invoking activities associated with an application, according to some implementation schemes, is shown. Figures 8A to 8B This is a flowchart illustrating a method for using computer system calls to associate activities with an application, according to some implementation schemes. Figures 7A to 7AZ The user interface in the document is used to illustrate the process described below, including Figures 8A to 8B The process in. Figures 9A to 9T An exemplary user interface is shown, according to some implementation schemes, for customizing content displayed based on a call. Figures 10A to 10C This is a flowchart illustrating a method for customizing content based on the content displayed using computer system calls, according to some implementation schemes. Figures 9A to 9T The user interface in the document is used to illustrate the process described below, including Figures 10A to 10C The process in. Figures 11A to 11S An exemplary user interface for managing applications used to enable activities is shown according to some implementation schemes. Figures 12A to 12D This is a flowchart illustrating a method for managing applications that enable activities using a computer system, according to some implementation schemes. Figures 11A to 11S The user interface in the document is used to illustrate the process described below, including Figures 12A to 12D The process in. Figures 13A to 13V An exemplary user interface for managing settings of applications that enable activities using a computer system, according to some implementation schemes, is shown. Figures 14A to 14BThis is a flowchart illustrating a method for managing settings for applications that enable activities using a computer system, according to some implementation schemes. Figures 13A to 13V The user interface in the document is used to illustrate the process described below, including Figures 14A to 14B The process in.

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

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

[0053] Depending on the context, the term "if" may optionally be interpreted as meaning "when," "at," or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrases "if determination..." or "if detection [the stated condition or event]" may optionally be interpreted as meaning "in response to determination..." or "in response to detection [the stated condition or event]."

[0054] This document describes implementations of electronic devices, user interfaces for such devices, and related processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functions such as PDA and / or music player functionality. Exemplary implementations of portable multi-functional devices include, but are not limited to, those from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Optionally, other portable electronic devices may be used, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). In some embodiments, the electronic device is a computer system that communicates with a display generating component (e.g., via wireless or wired communication). The display generating component is configured to provide visual output, such as a display via a CRT monitor, a display via an LED monitor, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. As used herein, “display” content includes displaying content (e.g., video data rendered or decoded by display controller 156) by transmitting data (e.g., image data or video data) to an integrated or external display generating component via a wired or wireless connection to visually generate content.

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

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

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

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

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

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

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

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

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

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

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

[0066] I / O subsystem 106 couples input / output peripherals on device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from / send electrical signals to the other input control device 116. The other input control device 116 optionally includes physical buttons (e.g., push-buttons, rocker buttons, etc.), dial pads, slide switches, joysticks, click dials, etc. In some embodiments, input controller 160 is optionally coupled to (or not coupled to) any of the following: keyboard, infrared port, USB port, and pointing device such as mouse. One or more buttons (e.g., Figure 2 Optionally, 208) includes an increase / decrease button for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include a push-button (e.g., Figure 2(Ref. 206 in the original text). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a touchpad, as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as for tracking user gestures (e.g., hand gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system.

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

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

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

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

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

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

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

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

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

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

[0077] The device 100 optionally also includes one or more depth camera sensors 175. Figure 1A A depth camera sensor is shown coupled to a depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment to create a 3D model of an object (e.g., a face) within the scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as a camera module), depth camera sensor 175 may optionally be used to determine depth maps of different portions of an image captured by imaging module 143. In some embodiments, the depth camera sensor is located at the front of device 100, such that user images with depth information are optionally acquired for video conferencing while the user views other video conferencing participants on a touchscreen display, and selfies with depth map data are captured. In some embodiments, depth camera sensor 175 is located at the rear of the device, or both the rear and front of device 100. In some embodiments, the position of depth camera sensor 175 may be changed by the user (e.g., by rotating a lens and sensor within the device housing), such that depth camera sensor 175 is used in conjunction with a touchscreen display for both video conferencing and still image and / or video image acquisition.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0091] Optionally, the text input module 134, a component of the graphics module 132, provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application that requires text input).

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

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

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

[0095] • Telephone module 138;

[0096] • Video conferencing module 139;

[0097] • Email client module 140;

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

[0099] Fitness support module 142;

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

[0101] • Image management module 144;

[0102] • Video player module;

[0103] Music player module;

[0104] • Browser module 147;

[0105] • Calendar module 148;

[0106] • Desktop mini-program module 149, which optionally includes one or more of the following: weather desktop mini-program 149-1, stock market desktop mini-program 149-2, calculator desktop mini-program 149-3, alarm clock desktop mini-program 149-4, dictionary desktop mini-program 149-5, and other desktop mini-programs obtained by the user, and desktop mini-programs created by the user 149-6;

[0107] • Desktop app creator module 150 for creating user-created desktop apps 149-6;

[0108] • Search module 151;

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

[0110] • Notes module 153;

[0111] • Map module 154; and / or

[0112] • Online video module 155.

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

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

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

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

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

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

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

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

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

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

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

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

[0125] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, the desktop applet creator module 150 can optionally be used by the user to create desktop applets (e.g., converting user-specified portions of a webpage into desktop applets).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0154] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some implementations, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and delaying) the sub-event to the corresponding hit view. In some implementations, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with that tag retrieves the tag and executes a predefined procedure.

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

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

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

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

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

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

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

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

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

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

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

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

[0167] • Time 404;

[0168] Bluetooth indicator 405;

[0169] • Battery status indicator 406;

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

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

[0172] The email client module 140 has an icon 418 labeled "Mail", which optionally includes an indicator 410 for the number of unread emails;

[0173] The browser module 147 has an icon 420 labeled "Browser"; and

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

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

[0176] Icon 424 of the οIM module 141, labeled "Message";

[0177] The icon 426 of the calendar module 148 is labeled "Calendar";

[0178] The icon 428 of the image management module 144 is labeled "photo";

[0179] The icon 430 of the camera module 143 is labeled "camera";

[0180] The icon 432 of the online video module 155 is labeled "Online Video";

[0181] The icon 434 in the Stock Market Desktop Mini Program 149-2 is labeled "Stock Market";

[0182] The icon 436 of the map module 154 is labeled "map";

[0183] The icon 438 in the Weather Desktop Mini Program 149-1 is marked as "Weather".

[0184] The icon labeled "Clock" in the alarm clock desktop mini-program 149-4 is 440;

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

[0186] The icon 444 labeled "Notes" in the Notes module 153; and

[0187] The icon 446, labeled "Settings," is used to set the settings of the device 100 and its various applications 136.

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

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

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

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

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

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

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

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

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

[0197] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions, which, when executed by one or more computer processors 516, may cause the computer processors to perform, for example, the techniques described below. The computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical discs based on CD, DVD, or Blu-ray technology, and persistent solid-state storage such as flash memory, solid-state drives, etc. The personal electronic device 500 is not limited to... Figure 5B It can be the components and configurations, or it can include other components or additional components in a variety of configurations.

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

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

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

[0201] Figure 6 Exemplary devices are illustrated that connect via one or more communication channels to participate in transactions, according to some embodiments. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are configured to optionally detect input (e.g., specific user input, NFC field) and optionally transmit payment information (e.g., using NFC). The one or more electronic devices optionally include NFC hardware and are configured to support NFC.

[0202] Electronic devices (e.g., devices 100, 300, and 500) are optionally configured to store payment account information associated with each of one or more payment accounts. Payment account information includes one or more of the following: a person's or company name, a billing address, a login name, a password, an account number, an expiry date, a security code, a telephone number, a bank (e.g., an issuing bank) associated with the payment account, and a card network identifier. In some embodiments, payment account information includes images, such as photographs of payment cards (e.g., photographs taken by and / or received by the device). In some embodiments, the electronic device receives user input that includes at least some payment account information (e.g., receiving user-inputted credit, debit, account, or shopping card number and expiry date). In some embodiments, the electronic device detects at least some payment account information from an image of the payment card (e.g., captured by the device's camera sensor). In some embodiments, the electronic device receives at least some payment account information from another device (e.g., another user device or server). In some implementations, the electronic device receives payment account information from a server associated with another service (e.g., an application for renting or selling audio and / or video files), where the user or the user device's account has previously made purchases for that other service or has identified payment account data.

[0203] In some implementations, a payment account is added to an electronic device (e.g., devices 100, 300, and 500), such that payment account information is securely stored on the electronic device. In some implementations, after a user initiates such a process, the electronic device transmits the payment account information to a transaction coordination server, which then communicates with a server (e.g., a payment server) operated by the account's payment network to ensure the validity of the information. The electronic device is optionally configured to receive scripts from a server that allows the electronic device to program the account's payment information onto a secure element.

[0204] In some implementations, communication between electronic devices 100, 300, and 500 facilitates transactions (e.g., general or specific transactions). For example, a first electronic device (e.g., 100) may function as a configuration or management device and may send new or updated payment account data (e.g., information about new accounts, updated information about existing accounts, and / or warnings about existing accounts) to a second electronic device (e.g., 500). Alternatively, the first electronic device (e.g., 100) may send data to the second electronic device reflecting information about a payment transaction facilitated at the first electronic device. This information may optionally include one or more of the following: payment amount, account used, purchase time, and whether the default account has been changed. The second device (e.g., 500) may optionally use such information to update the default payment account (e.g., based on a learning algorithm or explicit user input).

[0205] Electronic devices (e.g., 100, 300, 500) are configured to communicate with each other via any of a variety of networks. For example, devices may communicate using Bluetooth connectivity 608 (e.g., including traditional Bluetooth connectivity or Bluetooth Low Energy connectivity) or using a WiFi network 606. Communication between user devices may optionally be tailored to reduce the likelihood of inappropriate sharing of information between devices. For example, communication regarding payment information may require the communicating devices to be paired (e.g., associated with each other via explicit user interaction) or associated with the same user account.

[0206] In some embodiments, electronic devices (e.g., 100, 300, 500) communicate with a point-of-sale (POS) payment terminal 600, which optionally supports NFC. This communication may optionally utilize various communication channels and / or technologies. In some embodiments, the electronic devices (e.g., 100, 300, 500) use NFC channel 610 to communicate with the payment terminal 600. In some embodiments, the payment terminal 600 uses a peer-to-peer NFC mode to communicate with the electronic devices (e.g., 100, 300, 500). The electronic devices (e.g., 100, 300, 500) are optionally configured to transmit signals to the payment terminal 600, including payment information of a payment account (e.g., a default account or an account selected for a specific transaction).

[0207] In some implementations, continuing the transaction includes transmitting a signal containing payment information, including an account such as a payment account. In some implementations, continuing the transaction includes reconfiguring an electronic device (e.g., 100, 300, 500) to respond as a contactless payment card (e.g., an NFC-enabled contactless payment card), and then transmitting the account credentials via NFC to, for example, a payment terminal 600. In some implementations, after transmitting the account credentials via NFC, the electronic device is reconfigured not to respond as a contactless payment card (e.g., authorization is required before it can be reconfigured to respond as a contactless payment card via NFC).

[0208] In some embodiments, the generation and / or transmission of the signal is controlled by a secure element in an electronic device (e.g., 100, 300, 500). Prior to issuing payment information, the secure element optionally requests specific user input. For example, the secure element optionally requests: detection of a worn electronic device, detection of a button press, detection of a password input, detection of a touch, detection of one or more option selections (e.g., option selections received during interaction with an application), detection of a fingerprint signature, detection of a voice or voice command, and / or detection of a gesture or movement (e.g., rotation or acceleration). In some embodiments, if a communication channel (e.g., an NFC communication channel) is established with another device (e.g., payment terminal 600) within a defined time period from the detection of input, the secure element issues payment information for transmission to the other device (e.g., payment terminal 600). In some embodiments, the secure element is a hardware component controlling the issuance of secure information. In some embodiments, the secure element is a software component controlling the issuance of secure information.

[0209] In some implementations, the protocols associated with transaction participation depend on, for example, the device type. For instance, the conditions for generating and / or transmitting payment information may differ for wearable devices (e.g., device 500) and telephones (e.g., device 100). For example, the generation and / or transmission conditions for wearable devices may include detecting that a button has been pressed (e.g., after security verification), while the corresponding conditions for telephones do not require a button press but rather require detecting a specific interaction with the application. In some implementations, the conditions for transmitting and / or publishing payment information include receiving specific input from each of a plurality of devices. For example, publishing payment information may optionally require detecting a fingerprint and / or password at one device (e.g., device 100) and mechanical input (e.g., button press) at another device (e.g., device 500).

[0210] Payment terminal 600 optionally uses payment information to generate a signal to be transmitted to payment server 604, thereby determining whether the payment is authorized. Payment server 604 optionally includes any device or system configured to receive payment information associated with a payment account and determine whether a proposed purchase is authorized. In some embodiments, payment server 604 includes a server of an issuing bank. Payment terminal 600 communicates directly with payment server 604 or indirectly via one or more other devices or systems (e.g., a server of an acquiring bank and / or a server of a card network).

[0211] Payment server 604 optionally uses at least some of the payment information from the payment information to identify a user account from a database of user accounts (e.g., 602). For example, each user account includes payment information. Accounts are optionally located by locating an account that has specific payment information that matches the information from the POS communication. In some implementations, payment is refused when the provided payment information is inconsistent (e.g., the expiry date does not correspond to a credit card number, debit card number, or shopping card number) or when no account includes payment information that matches the information from the POS communication.

[0212] In some implementations, user account data further identifies one or more constraints (e.g., credit limit); current or previous balance; previous transaction dates, locations, and / or amounts; account status (e.g., active or frozen); and / or authorization instructions. In some implementations, the payment server (e.g., 604) uses this data to determine whether to authorize a payment. For example, the payment server may refuse payment if adding a purchase amount to the current balance would result in exceeding the account limit, if the account is frozen, if previous transaction amounts exceed a threshold, or if the number or frequency of previous unusual transactions exceeds a threshold.

[0213] In some implementations, payment server 604 responds to POS payment terminal 600 with indications regarding whether the proposed purchase is authorized or rejected. In some implementations, POS payment terminal 600 signals to electronic devices (e.g., 100, 300, 500) to identify the result. For example, when a purchase (e.g., via a transaction coordination server managing transactions on a user device) is authorized, POS payment terminal 600 sends a receipt to electronic devices (e.g., 100, 300, 500). In some cases, POS payment terminal 600 presents an output indicating the result (e.g., visual or audio output). Payment may be transmitted to the merchant as part of the authorization process or may be transmitted later.

[0214] In some implementations, electronic devices (e.g., 100, 300, 500) participate in transactions completed without involving the POS payment terminal 600. For example, upon detecting received mechanical input, a secure element in the electronic device (e.g., 100, 300, 500) issues payment information to allow an application on the electronic device to access that information (e.g., and transmit that information to a server associated with the application).

[0215] In some implementations, the electronic device (e.g., 100, 300, 500) is in a locked or unlocked state. In the locked state, the electronic device is powered on and operable, but it is prevented from performing a predefined set of operations in response to user input. This predefined set of operations may include navigating between user interfaces, activating or deactivating a predefined set of functions, and activating or deactivating certain applications. The locked state can be used to prevent unintentional or unauthorized use of certain functions of the electronic device, or to activate or deactivate certain functions on the electronic device. In the unlocked state, the electronic device 100 is powered on and operable, and is not prevented from performing at least a portion of a predefined set of operations that cannot be performed when in the locked state.

[0216] When a device is in a locked state, it is said to be locked. In some implementations, a locked device can respond to user input from a restricted group, including input corresponding to an attempt to switch the device to an unlocked state or input corresponding to turning off the device.

[0217] In some implementations, the secure element is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or algorithms. In some implementations, the secure element provides (or publishes) payment information (e.g., account and / or transaction-specific dynamic security codes). In some implementations, the secure element provides (or publishes) payment information in response to the device receiving authorization, such as user authentication (e.g., fingerprint authentication; password authentication; double pressing of a hardware button when the device is unlocked, and optionally while the device has been continuously on the user's wrist since being unlocked by providing authentication credentials, wherein the device's continued presence on the user's wrist is determined by periodically checking contact between the device and the user's skin). For example, the device detects a fingerprint at the device's fingerprint sensor (e.g., a fingerprint sensor integrated into a button). The device determines whether the fingerprint matches a registered fingerprint. Based on the determination that the fingerprint matches a registered fingerprint, the secure element provides (or publishes) payment information. Based on the determination that the fingerprint does not match a registered fingerprint, the secure element abandons providing (or publishing) payment information.

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

[0219] As used herein, the terms "open application" or "running application" refer to a software application that maintains state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application is optionally any of the following types of applications:

[0220] • The active application currently displayed on the screen of the device that is using the application;

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

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

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

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

[0225] Figures 7A to 7AZ Exemplary user interfaces for invoking activities associated with an application, according to some implementation schemes, are shown. The user interfaces in these figures are used to illustrate the processes described below, including... Figures 8A to 8B The process in.

[0226] Figure 7AA computer system 700 (e.g., an electronic device; a smartphone; a smartwatch; a tablet computer; a mobile device) is illustrated, which communicates with a display generating component 702A (e.g., a display, a touch-sensitive display) and one or more input devices (e.g., a touch-sensitive surface integrated with the display generating component 702A; one or more position sensors (e.g., a GPS sensor); one or more image sensors (e.g., a camera); mechanical input devices). Figure 7A In this embodiment, computer system 700 displays a user interface 704, such as a wake-up screen (e.g., a lock screen), via display generation component 702A. In some embodiments, the wake-up screen is a user interface displayed when the display generation component of the computer system transitions from an inactive (e.g., off) state to an active (e.g., on) state. In some embodiments, the lock screen is a user interface displayed when the computer system is operating in a locked state, in which at least some functions of the computer system are restricted (e.g., until the computer system is unlocked).

[0227] In some embodiments, computer system 700 (via one or more location sensors (e.g., GPS sensors) communicating with computer system 700) detects (e.g., determines) that computer system 700 is (e.g., has entered) a first corresponding location (e.g., a shop; restaurant; coffee shop; bakery). In some embodiments, computer system 700 detects that the system is in the first corresponding location when displaying a user interface 704 on a wake-up screen. In some embodiments, computer system 700 detects that the system is in the first corresponding location when displaying a different user interface (e.g., a user interface for a different application). In some embodiments, computer system 700 detects that the system is in the first corresponding location when display generation component 702 is in a turned-off state.

[0228] exist Figure 7BIn response to detecting (e.g., determining) that the computer system 700 is in a first corresponding location, the computer system 700 displays a form user interface 706 corresponding to the first corresponding location via a display generation component 702 (e.g., and overlaid on a portion of the user interface 704). The form user interface 706 includes an information area 706A that includes information about the first corresponding location (e.g., the name of the first corresponding location; the address of the first corresponding location; an identifier / identification number (e.g., object number; branch number; table number) associated with activities that can be performed at the first corresponding location (e.g., reserving an object for rent (e.g., a bicycle; a car); ordering menu items such as food and / or drinks)) and a power indication 706B (e.g., an optional user interface object; an activatable user interface object), which, when activated, initiates a process for enabling activities associated with the first corresponding location (e.g., ordering; reserving; purchasing) on ​​the computer system 700. In some implementations, the form user interface includes a graphical element that appears as a form and is displayed (e.g., a pop-up) above the current user interface, and has a similar appearance to a graphical element (e.g., a form) that appears (e.g., a pop-up) when other predefined events such as pairing headphones or controlling music on a main audio device occur.

[0229] exist Figures 7B to 7N In the exemplary user interface depicted, the first corresponding location is the first restaurant (e.g., a restaurant named "Food King"). In some embodiments, information area 706A includes the name of the first restaurant (e.g., "Food King") and the address of the first restaurant.

[0230] In some implementations, the indication of 706B indicates (e.g., including text describing the type of activity associated with the first restaurant) the type of activity associated with the first restaurant (e.g., ordering menu items, such as food and / or beverages).

[0231] In some implementations, the form user interface 706 includes an image 706C indicating the first restaurant (e.g., an image of the first restaurant; the logo of the first restaurant).

[0232] In some implementations, the form user interface 706 includes instructions 706D (e.g., text or images) from a developer (e.g., an entity; a company) that operates (e.g., creates and / or manages) a first-type application (e.g., a simplified / partial version of an application with a corresponding full / regular version available) that can be used to enable activities associated with the first restaurant (e.g., ordering menu items such as food and / or beverages). For ease of description, the first-type application is sometimes referred to as a simplified version application.

[0233] In some implementations, the developer is different from the supplier corresponding to the first restaurant (i.e., the supplier corresponding to the first restaurant is not the developer of the simplified version of the application). For example, in Figure 7B In this context, the application is operated by a first developer (e.g., "Food Review") that is different from the supplier corresponding to the first restaurant (e.g., "Food King"). In some implementations, the developer may offer its application platform for use by multiple different suppliers, and the application may be customized for each supplier. In some implementations, the developer is the supplier corresponding to the first restaurant (i.e., the supplier corresponding to the first restaurant is the application developer).

[0234] In some implementations, the form user interface 706 includes a power representation 706E (e.g., an optional user interface object; an activatable user interface object) for accessing an application store (e.g., an application store controlled and managed by the developer of the operating system of the computer system 700, such as computer applications or websites, where the application store can be used to download first-party and third-party applications to the computer system 700).

[0235] In some implementations, the form user interface 706 includes a power indication 706F (e.g., an optional user interface object; an activatable user interface object) for eliminating (e.g., causing the computer system 700 to stop displaying) the form user interface 706 without performing activities associated with the first restaurant (e.g., ordering menu items such as food and / or drinks).

[0236] exist Figure 7C In the process of displaying a form user interface 706 that can be used to initiate activities associated with the first restaurant (e.g., ordering menu items such as food and / or drinks), the computer system 700 detects the activation 701 of the power indicator 706B via the one or more input devices (e.g., via the touch-sensitive surface of the one or more input devices). (e.g., the user selects the power indicator; the user taps on the power indicator.)

[0237] exist Figure 7DIn response to the detection of activation 701 of the enable signal 706B, and based on the determination (indicated via instruction 706D) that a second type of application (e.g., a full version / regular version of the application) developed by the developer has been installed on the computer system 700 (and is therefore available on the computer system), the computer system 700 displays the user interface 708 of the second type of application installed on the computer system via the display generation component 702. In some embodiments, the second type of application can be downloaded to the computer system 700 from an application store. For ease of description, the second type of application is sometimes referred to as a full version application. In some embodiments, the corresponding full version application has a corresponding simplified version application (e.g., both created and / or managed by the same developer (e.g., the same entity; the same company)).

[0238] Figure 7E A computer system 700 is shown displaying (e.g., re-displaying) a form user interface 706 via a display generation component 702 (e.g., and overlaid on a portion of the user interface 704). Figure 7E In this case, the full version of the application corresponding to the developer is not available on computer system 700 (for example, it is not installed on this computer system).

[0239] exist Figure 7E In the process of displaying the form user interface 706, the computer system 700 (e.g., via the touch-sensitive surface of the one or more input devices) detects activation 703 of the power indicator 706E for accessing the application store (e.g., the user selects the power indicator; the user taps on the power indicator). In some embodiments, only the full version of the application corresponding to the developer is not installed on the computer system 700 (e.g., such as...). Figure 7E In some implementations, the computer system 700 includes the power display 706E in the form user interface 706 even when the full version of the application corresponding to the developer is already installed on the computer system 700.

[0240] exist Figure 7F In response to the detection of activation 703 of the power indicator 706E, the computer system 700 displays the user interface 710 of the application store via the display generation component 702, wherein the application store displays an application page 712 in the user interface 710 that corresponds to the full version of the application and is used to download the full version of the application to the computer system 700.

[0241] Figures 7G to 7NA method (e.g., a location-based method) is shown for initiating a process to enable activity on computer system 700 when the corresponding full version of the application is not used on computer system 700 (e.g., because the full version of the application is not installed on computer system 700). Figure 7G The computer system 700 displays a message in response to (e.g., via one or more position sensors of the one or more input devices) detecting that the computer system 700 is at the first restaurant (e.g., because the user of the computer system 700 walks into / arrives at the first restaurant). Figure 7B The form user interface was first depicted in the 706. Figure 7G In, such as in Figure 7E In this case, the developer's full version of the application (e.g., "Food Review") is not available on computer system 700 (e.g., it is not installed on that computer system).

[0242] exist Figure 7G In the process of displaying the form user interface 706, the computer system 700 (e.g., via the touch-sensitive surface of the one or more input devices) detects the activation 705 of the power indicator 706B for initiating a process related to the activity (e.g., ordering) of the first restaurant on the computer system 700.

[0243] In some implementation schemes, such as Figures 7H to 7J As shown, in response to detecting activation 705 of the enablement indicator 706B in the form user interface 706, the computer system 700 displays a user interface 714 (e.g., a loading screen) via a display generation component 702. This user interface includes an indication 714A of the name of the first restaurant (e.g., “Food King”) and an indication 714B of the developer (e.g., an entity; company) (e.g., “Food Review”). The developer operates a simplified version of the application (e.g., creating and / or managing templates for the simplified application) that can enable activities associated with the first restaurant (e.g., ordering menu items such as food and / or drinks). In some embodiments, the computer system 700 displays visual animations via indications 714A and / or 714B when displaying the user interface 714 (e.g., displaying the loading screen animated).

[0244] exist Figure 7KIn response to the detection of activation 705 of the enable display 706B in the form user interface 706 (e.g., after the user interface 714 (e.g., loading screen) has been displayed for a predetermined period of time) (e.g., or after the detection), the computer system 700A displays a simplified user interface 716 of a simplified version of the application via the display generation component 702, wherein the simplified user interface 716 corresponds to a first restaurant version (e.g., "Food King" version) of the simplified application (e.g., "Food Review"). In some embodiments, the simplified user interface 716 corresponds to a simplified version of the full version application (e.g., "Food Review"), wherein... Figure 7D The corresponding full version user interface is depicted. In some implementations, based on the determination that the simplified version application is not installed on the computer system 700, the computer system 700 responds to detecting the activation 705 of the enablement representation 706B in the form user interface 706 (e.g., in the display) Figures 7H to 7J When the user interface 714 shown (e.g., the loading screen) appears, a simplified version of the application corresponding to the simplified user interface 716 is automatically downloaded and installed (e.g., without user input). In some embodiments, the computer system 700 automatically downloads and installs the simplified version of the application without requesting user authorization (e.g., authorization by providing authentication information such as biometric authentication and / or password authentication).

[0245] like Figure 7K As shown, in some embodiments, the simplified user interface 716 includes location information 718 (e.g., address) of the first restaurant. In some embodiments, the simplified user interface 716 includes a menu area 720 that includes multiple optional menu items that can be ordered at the first restaurant. In some embodiments, the simplified user interface 716 includes a power indicator 722 (e.g., an optional user interface object; an activatable user interface object) for ordering / checkout of the selected menu item.

[0246] like Figure 7KAs shown, in some embodiments, the simplified user interface 716 includes a user interface object 724 (e.g., a banner advertisement; a disc) that is displayed simultaneously with the simplified user interface 716 (e.g., overlaid on a portion of the simplified user interface 716). In some embodiments, the user interface object 724 is displayed together with the simplified user interface 716 and for a predetermined time period (e.g., 10 seconds; 30 seconds; 1 minute). In some embodiments, the user interface object 724 includes instructions 724A (e.g., text messages) from a developer (e.g., an entity; a company) that operates a simplified version of the application corresponding to the simplified user interface 716 (e.g., creating and / or managing templates for the simplified version of the application). In some embodiments, the user interface object 724 includes a shared display 724B for initiating a process for sharing the simplified version of the application corresponding to the simplified user interface 716 with different users (e.g., transmitting electronic communications to different computer systems including the simplified version of the application and / or instructions for downloading the simplified version of the application).

[0247] exist Figure 7L In the process of displaying the simplified user interface 716, the computer system 700 (e.g., via the touch-sensitive surface of the one or more input devices) detects user selection 707 for a first menu item 720A and user selection 709 for a second menu item 720B from the menu area 720 of the simplified user interface 716.

[0248] exist Figure 7M In response to the detection of user selections 709 and 711 for the first menu item 720A and the second menu item 720B, respectively, the computer system 700 displays an indication in the simplified user interface 716 (e.g., via a power indicator 722) that the selected menu item has been added to the current order (e.g., added to cart). When the selected menu item has been added to the current order, the computer system 700 detects activation 711 of the power indicator 722 (e.g., user selection for the power indicator; user tap input on the power indicator) via the touch-sensitive surface of the one or more input devices.

[0249] exist Figure 7NIn response to the detection of activation 711 of the enable indicator 722, the computer system 700 displays an authorization user interface 726 via a display generation component 702 (e.g., overlaid on a portion of the simplified user interface 716 such that a portion, but not all, of the simplified user interface 716 remains visible on the display generation component 702) for authorizing a transfer (e.g., a transaction) to complete the process of ordering a selected menu item. In some embodiments, the authorization user interface 726 corresponds to a secure first-party application developed and managed by the same entity (e.g., the same company) that develops and manages the operating system of the computer system 700.

[0250] Figures 70 to 7U A method (e.g., a point-of-interest-based method) is shown for initiating a process to enable activity on computer system 700 when the corresponding full version of the application is not used on computer system 700 (e.g., because the full version of the application is not installed on computer system 700). Figure 7O The computer system 700 is shown displaying a user interface 728 of a map application including a map 730 via a display generation component 702, wherein the map 730 includes a plurality of location points 730A-730D corresponding to points of interest (e.g., saved locations; favorite locations; suggested locations).

[0251] exist Figure 7O In the process of displaying a map 730 in the user interface 728 of a map application, a computer system 700 (e.g., via a touch-sensitive surface of the one or more input devices) detects a user selection 713 for a first location point 730A (e.g., a first point of interest) in the map 730, wherein the first location point 730A corresponds to a first bicycle rental location.

[0252] exist Figure 7P In response to detecting a user selection 713 for a first location point 730A in map 730, computer system 700 displays a user interface 732 (e.g., a pop-up user interface) via display generation component 702 (e.g., overlaid on a portion of user interface 728) that includes information (e.g., name; address; rating; reviews; photos; directions) about the selected location (first bicycle rental location). The user interface 732 includes an enablement representation 732A (e.g., an optional user interface object; an activatable user interface object) associated with a process initiated on computer system 700 for enabling activities associated with the selected first bicycle rental location (e.g., renting a bicycle).

[0253] exist Figure 7PIn the process of displaying the user interface 732, the computer system 700 (e.g., via the touch-sensitive surface of the one or more input devices) detects the activation 715 of the power indicator 732A (e.g., user selection for the power indicator; user tap input on the power indicator).

[0254] exist Figure 7Q In response to the detection of activation 715 of the indicator 732A, the computer system 700 displays a form user interface 734 corresponding to the selected location (e.g., the first bicycle rental location) via a display generation component 702 (e.g., and overlaid on a portion of the user interface 728 of the map application), wherein the form user interface 734 is similar to the one referenced above. Figure 7B The form user interface 706, described for the first time, (e.g., has the same layout / structure as the form user interface; provides a consistent experience with the form user interface). In Figure 7B In this context, the form user interface 706 is associated with an activity (e.g., ordering) enabled based on the detected corresponding location (e.g., detecting that computer system 700 is in the first restaurant). Figure 7Q In this context, the form user interface 734 is associated with detected (e.g., received) selection enablement activities (e.g., rentals) based on the corresponding location from the map application.

[0255] exist Figures 70 to 7U In the exemplary user interface depicted, the selected corresponding location is a first bicycle rental location (e.g., a bicycle rental shop; a bicycle rental port). In some embodiments, the form user interface 734 includes an information area 734A that includes the name of the first bicycle rental location (e.g., "bicycle rental 3") and address and / or branch information about the bicycle rental location (e.g., "location 42"), and a power indication 734B (e.g., an optional user interface object; an activatable user interface object) that, when activated, initiates a process for enabling activities related to the first bicycle rental location (e.g., reserving a bicycle).

[0256] In some implementations, the form user interface 734 includes an image 734C indicating the first bicycle rental location (e.g., an image of the first bicycle rental location; the logo of the supplier (e.g., an entity / company) operating the first bicycle rental location).

[0257] In some embodiments, the form user interface 734 includes instructions 734D from a developer (e.g., an entity; a company) that operates a simplified version of the application (e.g., creating and / or managing templates for the simplified application) that can be used to enable activities associated with the first bicycle rental location (e.g., reserving a bicycle) on the computer system 700. In some embodiments, such as in Figure 7Q In this context, the developers of the simplified version of the application (and the corresponding full version of the application) are the same as the providers (e.g., entities / companies) operating the first bicycle rental location.

[0258] In some implementations, the form user interface 734 includes a power representation 734E (e.g., an optional user interface object; an activatable user interface object) for accessing an application store (e.g., an application store controlled and managed by the developer of the operating system of computer system 700, where the application store can be used to download first-party and third-party applications to computer system 700).

[0259] In some implementations, the form user interface 734 includes a power indication 734F (e.g., an optional user interface object; an activatable user interface object) for eliminating (e.g., causing the computer system 700 to stop displaying) the form user interface 734 without performing any activity associated with the first bicycle rental location (e.g., reserving a bicycle).

[0260] exist Figure 7R In the process of displaying a form user interface 734 that can be used to initiate an activity associated with the first bicycle rental location (e.g., reserving a bicycle), the computer system 700 (e.g., via a touch-sensitive surface of the one or more input devices) detects activation 717 of the power indicator 734B (e.g., user selection for the power indicator; user tap input on the power indicator).

[0261] exist Figure 7SIn response to the detection of activation 717 of the power indicator 734B, based on the determination that the full version of the application for enabling the activity (e.g., reserving a bicycle) is unavailable on the computer system 700 (e.g., not installed on the computer system), the computer system 700 displays a simplified user interface 736 for a simplified version of the application for enabling the activity (e.g., reserving a bicycle) via the display generation component 702. In some embodiments, the full version of the application corresponding to the simplified version of the application for enabling the activity (e.g., reserving a bicycle) may be downloaded to the computer system 700 from an application store (e.g., via the power indicator 734E of the user interface 734). In some embodiments, if the simplified version of the application is not installed on the computer system 700 (e.g., because this is the first time the simplified version of the "bicycle rental" application has been accessed), the computer system 700 (e.g., in response to the detection of activation 717 of the power indicator 734B) automatically (e.g., without user input; without user authorization) (e.g., before and / or simultaneously with the display of the simplified user interface 736) downloads and installs the simplified version of the application.

[0262] like Figure 7S As shown, in some embodiments, the simplified user interface 736 includes a first area 738, which includes a map (e.g., a map indicating one or more nearby locations corresponding to different bicycle rental locations; a map provided by a simplified application tailored for the purpose of the activity, and...) Figure 7O (The map application shown is the opposite). In some embodiments, the simplified user interface 736 includes an indication 740 (e.g., displayed as an optional user interface object; displayed as a disc) that indicates the corresponding bicycle rental location (e.g., the first bicycle rental location) closest to the current location of the computer system 700 (e.g., and includes the time required to reach (e.g., walk to) the corresponding bicycle rental location).

[0263] In some implementations, the simplified user interface 736 includes a second area 742 that includes information about an object (e.g., a specific bicycle) that can be reserved at the first bicycle rental location, including the object's identifier / identification number (e.g., the specific bicycle's identification number). In some implementations, the second area 742 includes an indication 744 for reserving the object (e.g., a specific bicycle) and an indication 746 for initiating the rental of the object once the user has arrived at it (e.g., by scanning the bicycle's code / identification).

[0264] In some implementations, although a simplified version of an application corresponding to the simplified user interface 736 has recently been used or is in use (e.g., active on the computer system; currently displayed and / or running in the background), the computer system 700 (e.g., via one or more position sensors) detects that the computer system 700 is moving closer to the first bicycle rental location. In some implementations, the computer system 700 indicates the updated location of the computer system 700 relative to the first bicycle rental location in the simplified user interface 736 (e.g., via indication 740), such as... Figure 7T As shown in the image.

[0265] Figure 7U The computer system 700 displays a user interface 704 corresponding to the wake-up screen (e.g., lock screen) of the computer system 700 via a display generation component 702, as shown above. Figure 7A As described initially. In some implementations, a simplified version of the application is enabled to (e.g., authorized to; authorized to access) cause a notification on computer system 700.

[0266] exist Figure 7U In the process, based on the determination of the location of the computer system 700 at (e.g., having arrived at) the first bicycle rental location, the computer system 700 displays a notification 748 indicating that it has arrived at the location via the display generation component 702.

[0267] Figures 7V to 7AA A method (e.g., an NFC-based method; a QR code-based method) is shown for initiating a process to enable activity on computer system 700 when the corresponding full version of the application is not used on computer system 700 (e.g., because the full version of the application is not installed on computer system 700).

[0268] Figure 7V The computer system 700 displays a user interface 704 corresponding to the wake-up screen (e.g., lock screen) of the computer system 700 via a display generation component 702, as shown above. Figure 7A First described. In Figure 7V In this context, computer system 700 is positioned at the first location (e.g., the first restaurant; the first coffee shop; the first bakery) with the first identifier (e.g., the first table). Figures 7V to 7AA In the exemplary user interface depicted, the location of the first identifier is the first table (e.g., table number 5) at the first coffee shop.

[0269] Figure 7WA computer system 700 is shown communicating (e.g., via NFC) with a contactless wireless terminal 750 (e.g., an NFC terminal), wherein terminal 750 corresponds to a terminal at the first table (e.g., table 5) in a first coffee shop. In some embodiments, such as Figure 7W As shown, when the computer system (e.g., via NFC) receives a corresponding communication from the terminal 750 (e.g., or alternatively, the computer system 700 detects a QR code scanned from a QR code terminal (e.g., using one or more image sensors)), the display generation component 702 of the computer system 700 is in an on state (e.g., displaying the user interface 704). In some embodiments, when the computer system 700 (e.g., via NFC) receives a corresponding communication from the terminal 750, the display generation component 702 of the computer system 700 is in an off state.

[0270] exist Figure 7W In this process, computer system 700 (e.g., via NFC) detects (e.g., receives) identification information (e.g., an identifier) ​​from terminal 750 (e.g., or alternatively detects a QR code scanned via a QR code terminal at the first table (e.g., using one or more image sensors), wherein the identification information includes information about the first coffee shop (e.g., information identifying the first coffee shop) and / or information about the first table (e.g., information identifying that terminal 750 corresponds to table number 5 in the first coffee shop).

[0271] exist Figure 7X In response to the detection (e.g., receipt) of identification information from terminal 750 (e.g., via NFC; via QR code scanning), computer system 700 displays a form user interface 752 based on the identification information from terminal 750 via display generation component 702 (e.g., overlaid on a portion of user interface 704), wherein the form user interface 752 is similar to the above reference. Figure 7B The form user interface 706 described for the first time and the above reference Figure 7Q The form user interface 734 described for the first time (e.g., having the same layout / structure as the two form user interfaces; providing a consistent experience with the two form user interfaces). In Figure 7B In this context, the form user interface 706 is associated with an activity (e.g., ordering) enabled based on the detected corresponding location (e.g., detecting that the computer system 700 is in the first restaurant). Figure 7Q In this context, the form user interface 734 is associated with detected (e.g., received) selection-enabled activities (e.g., rentals) based on the corresponding location from a map application. Figure 7XIn this form, the form user interface 752 is associated with an activity (e.g., ordering) enabled based on detected (e.g., received) identification information (e.g., via NFC; via QR code scanning) from an external device (e.g., a contactless wireless terminal).

[0272] exist Figures 7V to 7AA In the exemplary user interface depicted, the detected (e.g., received) identification information includes information about the first coffee shop and identifies the first table (e.g., table 5) within the first coffee shop. In some embodiments, the form user interface 752 includes an information area 752A that includes the name of the first coffee shop (e.g., "coffee shop") and address and / or branch information about the first coffee shop, and a power representation 752B (e.g., an optional user interface object; an activatable user interface object) that, when activated, initiates a process for enabling activities related to the first coffee shop and specifically to the first table (e.g., table 5) at the first coffee shop.

[0273] In some implementations, the form user interface 752 includes an image 752C indicating the first coffee shop (e.g., "coffee shop") (e.g., an image of the first coffee shop; a logo of the supplier (e.g., an entity / company) operating the first coffee shop).

[0274] In some implementations, the form user interface 752 includes instructions 752D from a developer (e.g., an entity; a company) that operates a simplified version of the application (e.g., creating and / or managing templates for the simplified application) that can enable activities associated with the first coffee shop (e.g., the "coffee shop") (e.g., ordering one or more menu items, such as food or beverages). In some implementations, such as in Figure 7X In this context, the developers of the simplified version of the application (and the corresponding full version of the application) (e.g., “Food Review”) are different from the suppliers (e.g., First Coffee Shop (e.g., “Coffee Shop”)).

[0275] In some embodiments, the form user interface 752 includes a power representation 752E (e.g., an optional user interface object; an activatable user interface object) for accessing an application store (e.g., an application store controlled and managed by the developer of the operating system of computer system 700, where the application store can be used to download first-party and third-party applications to computer system 700). In some embodiments, a full version of an application corresponding to a simplified version of the application, used to enable activities (e.g., reserving a bicycle), can be downloaded to computer system 700 from the application store (e.g., via the power representation 752E of the form user interface 752).

[0276] In some implementations, the form user interface 752 includes a power representation 752F (e.g., an optional user interface object; an activatable user interface object) for eliminating (e.g., causing the computer system 700 to stop displaying) the form user interface 752 without performing activities associated with the first coffee shop (e.g., ordering one or more menu items for the first table).

[0277] exist Figure 7Y In the process of displaying a form user interface 752 that can be used to initiate an activity associated with the first coffee shop (e.g., ordering one or more menu items for the first table), the computer system 700 (e.g., via a touch-sensitive surface of the one or more input devices) detects activation 719 of the power indicator 752B (e.g., user selection for the power indicator; user tap input on the power indicator).

[0278] exist Figure 7Z In response to the detection of activation 719 of the power indicator 752B, based on the determination that the full version of the application (e.g., the full version of the "Food Review" application) used to enable the activity (e.g., ordering one or more menu items for the first table) is unavailable on the computer system 700 (e.g., not installed on the computer system), the computer system 700 displays a simplified user interface 754 via the display generation component 702 corresponding to a simplified version of the application (e.g., "Food Review") used to enable the activity (e.g., ordering one or more menu items for the first table). In some embodiments, if the simplified version of the application is not installed on the computer system 700 (e.g., because this is the first time the simplified version of the "Food Review" application has been accessed), the computer system 700 (e.g., in response to the detection of activation 719 of the power indicator 752B) automatically (e.g., without user input; without user authorization) (e.g., before and / or simultaneously with the display of the simplified user interface 754) downloads and installs the simplified version of the application.

[0279] In some implementations, the simplified user interface 754 is similar to the reference above. Figure 7K The simplified user interface 716 described (e.g., sharing a similar layout with the simplified user interface) is used because both simplified user interfaces are operated by the same developer (e.g., the same entity; the same company) (e.g., "Food Review"). Figure 7ZAs shown, in some embodiments, the simplified user interface 754 includes location information 756 (e.g., address) of the first coffee shop. In some embodiments, the simplified user interface 754 includes (e.g., together with the location information 756) identification information (e.g., the table number of the first table (e.g., table 5)). In some embodiments, the simplified user interface 754 includes a menu area 758 that includes multiple optional menu items that can be ordered at the first coffee shop. In some embodiments, the simplified user interface 754 includes a power indicator 760 (e.g., an optional user interface object; an activatable user interface object) for ordering / checkout of the selected menu item.

[0280] In some implementations, the simplified user interface 754 includes a user interface object 762 (e.g., a banner ad; a disc) that is displayed simultaneously with the simplified user interface 754 (e.g., overlaid on a portion of the simplified user interface 754) (e.g., similar to the reference above). Figure 7K The user interface object 724 is described. In some embodiments, the user interface object 762 is displayed together with the simplified user interface 754 and for a predetermined time period (e.g., 10 seconds; 30 seconds; 1 minute; after which the computer system 700 stops displaying the user interface object 762). In some embodiments, the user interface object 762 includes instructions 762A (e.g., text information) from a developer (e.g., an entity; a company) who operates a simplified version of the application corresponding to the simplified user interface 754 (e.g., creating and / or managing templates for the simplified version of the application). In some embodiments, the user interface object 762 includes a shared capability representation 762B for initiating a process for sharing the simplified version of the application corresponding to the simplified user interface 716 with different users (e.g., transmitting electronic communications to different users including the simplified version of the application and / or methods for initiating the download of the simplified version of the application).

[0281] Figure 7AA The computer system 700 is shown displaying a simplified user interface 754 via display generation component 702 after a predetermined time period (e.g., 10 seconds; 30 seconds; 1 minute). In some embodiments, based on the determination of the predetermined time period, the computer system 700 automatically (e.g., in the absence of user input) stops the display of user interface object 762 (e.g., while maintaining the display of simplified user interface 754).

[0282] Figures 7AB to 7AFA method (e.g., a link-based method) is shown for initiating a process to enable activity on computer system 700 when the corresponding full version of the application is not used on computer system 700 (e.g., because the full version of the application is not installed on computer system 700). Figure 7AB A computer system 700 is shown displaying a browser application's user interface 756 via a display generation component 702, wherein the browser application's user interface 756 is displaying a webpage 758. Figure 7AB In the exemplary user interface depicted, webpage 758 is a first car sales / leasing webpage, and webpage 758 includes optional links 760 (e.g., hyperlinks).

[0283] exist Figure 7AC In the process of displaying a webpage 758 in a user interface 756, a computer system 700 (e.g., via a touch-sensitive surface of the one or more input devices) detects the activation 721 of an optional link 760 (e.g., a user selection for the optional link; a user tap input on the optional link).

[0284] exist Figure 7AD In response to detecting activation 721 of the optional link 760, the computer system 700 displays a form user interface 762 corresponding to the selected link (e.g., from a car sales / leasing webpage) via a display generation component 702 (e.g., overlaid on a user interface 756 displaying a webpage 758). In some embodiments, the form user interface 762 is similar to that described above. Figure 7B The form user interface described for the first time 706, referenced above. Figure 7Q The form user interface described for the first time 734 and the above reference Figure 7X The form user interface 752 described for the first time (e.g., having the same layout / structure as these form user interfaces; providing an experience consistent with these form user interfaces). In Figure 7B In this context, the form user interface 706 is associated with an activity (e.g., ordering) enabled based on the detected corresponding location (e.g., detecting that computer system 700 is in the first restaurant). Figure 7Q In this context, the form user interface 734 is associated with detected (e.g., received) selection-enabled activities (e.g., rentals) based on the corresponding location from a map application. Figure 7X In this context, the form user interface 752 is associated with an activity (e.g., ordering) enabled based on detected (e.g., received) identification information (e.g., via NFC; via QR code scanning) from an external device (e.g., a contactless wireless terminal). Figure 7ADIn this context, the form user interface 762 is associated with an activity (e.g., purchase; lease) enabled based on a selected link (e.g., from a webpage), where the activity relates to content associated with the link.

[0285] exist Figures 7AB to 7AF In the exemplary user interface depicted, the selected link 760 is associated with purchasing and / or leasing a vehicle from the First Auto Shop. In some embodiments, the form user interface 762 includes an information area 762A that includes the name of the First Auto Shop (e.g., “Shining Cars”) and address and / or branch information about the First Auto Shop, and a power representation 762B (e.g., an optional user interface object; an activatable user interface object) that, when activated, initiates a process for enabling activities related to the First Auto Shop (e.g., purchasing; leasing).

[0286] In some implementations, the form user interface 762 includes an image 762C indicating the First Auto Shop (e.g., “Shiny Auto”) (e.g., an image of the First Auto Shop; the logo of the supplier (e.g., an entity / company) operating the First Auto Shop).

[0287] In some implementations, the form user interface 762 includes instructions 762D from a developer (e.g., an entity; a company) that operates a simplified version of the application (e.g., creating and / or managing templates for the simplified application) that can enable activities associated with the first car dealership (e.g., purchasing and / or leasing a car). In some implementations, such as in Figure 7AD In this context, developers (e.g., entities / companies) who operate simplified versions of applications (and their corresponding full versions) also operate First Auto Shops (e.g., "Shining Auto").

[0288] In some embodiments, the form user interface 762 includes a power representation 762E (e.g., an optional user interface object; an activatable user interface object) for accessing an application store (e.g., an application store controlled and managed by the developer of the operating system of computer system 700, where the application store can be used to download first-party and third-party applications to computer system 700). In some embodiments, a full version of an application corresponding to a simplified version of the application, used to enable activities (e.g., purchasing and / or renting a car), can be downloaded to computer system 700 from the application store (e.g., via the power representation 762E of the form user interface 762).

[0289] In some implementations, the form user interface 762 includes a power representation 762F (e.g., an optional user interface object; an activatable user interface object) for eliminating (e.g., causing the computer system 700 to stop displaying) the form user interface 762 without performing activities associated with the first car shop (e.g., “shiny car”) (e.g., ordering one or more menu items for the first table).

[0290] exist Figure 7AE In the process of displaying a form user interface 762 that can be used to initiate activities associated with the first car store (e.g., “Sparkling Cars”) such as purchasing and / or leasing a car, the computer system 700 (e.g., via a touch-sensitive surface of the one or more input devices) detects activation 723 of the power indicator 762B (e.g., user selection for the power indicator; user tap input on the power indicator).

[0291] exist Figure 7AF In response to the detection of activation 723 of power indicator 762B, based on the determination that the full version of the application (e.g., the full version of the "Shining Cars" application) for enabling activities (e.g., purchasing and / or renting cars) is unavailable on computer system 700 (e.g., not installed on the computer system), computer system 700 displays a simplified user interface 764 of a simplified version of the application (e.g., a simplified version of the "Car Shop" application) for enabling activities (e.g., purchasing and / or renting cars) via display generation component 702. In some embodiments, if the simplified version of the application is not installed on computer system 700 (e.g., because this is the first time accessing the simplified version of the "Shining Cars" application), computer system 700 (e.g., in response to the detection of activation 723 of power indicator 762B) automatically (e.g., without user input; without user authorization) (e.g., before and / or simultaneously with the display of simplified user interface 764) downloads and installs the simplified version of the application.

[0292] In some implementations, the simplified user interface 764 differs from the reference above. Figure 7S The simplified user interface 736 described (e.g., having a layout different from the simplified user interface) is used because simplified user interface 764 and simplified user interface 736 are operated by different developers (e.g., different entities; different companies). In some implementations, the layout and / or structure of the corresponding simplified version of the application may be configured by the respective developer (e.g., the respective entity; the respective company) for the respective application.

[0293] like Figure 7AFAs shown, in some embodiments, the simplified user interface 764 includes a search area 766 for initiating a search (e.g., searching for a car to buy or lease) on a simplified version of the application corresponding to the simplified user interface 764. In some embodiments, the simplified user interface 764 includes a map area 768 that includes a map indicating the location of car dealerships and / or the location of the car being searched. In some embodiments, the simplified user interface 764 includes a filtering area 770 that includes multiple filters that can be applied to a given search.

[0294] Figures 7AG to 7AL A method (e.g., a search-based method) is shown for initiating a process to enable activity on computer system 700 when the corresponding full version of the application is not used on computer system 700 (e.g., because the full version of the application is not installed on computer system 700).

[0295] Figure 7AG A computer system 700 is shown displaying a search user interface 772, including a search area 774, via a display generation component 702. In some embodiments, the computer system 700 displays an input area 776 (e.g., a keyboard) in the search user interface 772.

[0296] In some implementations, when the search user interface 772 is displayed, the computer system 700 (e.g., via input area 776; via microphone) detects (e.g., receives) input 778. In the exemplary user interface shown in Figure AH, input 778 corresponds to a search for a coffee shop.

[0297] exist Figure 7AH In response to detecting (e.g., receiving) input 778 corresponding to a search for a coffee shop, computer system 700 displays a first results area 780 in search user interface 772, which includes multiple search results 780A-780C relating to input 778, each corresponding to a different simplified version of an application. In some embodiments, at least some of the multiple search results 780A-780C correspond to simplified versions of applications that are already installed on computer system 700 (e.g., recently used on the computer system; already accessed on the computer system). In some embodiments, at least some of the multiple search results 780A-780C correspond to different simplified versions of applications that are not installed on computer system 700 (e.g., not yet accessed on the computer system).

[0298] exist Figure 7AIIn the process of displaying the search user interface 772 showing the first results area 780, the computer system 700 (e.g., via the touch-sensitive surface of the one or more input devices) detects the user selection 725 for the first search result 780A corresponding to the second coffee shop (e.g., or for the display of the first search result 780A).

[0299] In Figure AJ, in response to detecting a user selection 725 for a first search result 780A corresponding to the second coffee shop, the computer system 700 displays a form user interface 784 corresponding to the second coffee shop via a display generation component 702 (e.g., overlaid on a portion of the search user interface 772). In some embodiments, the form user interface 784 is similar to the above reference. Figure 7B The form user interface described for the first time 706, referenced above. Figure 7Q The form user interface described for the first time 734, referenced above. Figure 7X The form user interface 752 described for the first time and the above reference Figure 7AE The form user interface 762 described for the first time (e.g., having the same layout / structure as these form user interfaces; providing an experience consistent with these form user interfaces). In Figure 7B In this context, the form user interface 706 is associated with an activity (e.g., ordering) enabled based on the detected corresponding location (e.g., detecting that computer system 700 is in the first restaurant). Figure 7Q In this context, the form user interface 734 is associated with detected (e.g., received) selection-enabled activities (e.g., rentals) based on the corresponding location from a map application. Figure 7X In this context, the form user interface 752 is associated with an activity (e.g., ordering) enabled based on detected (e.g., received) identification information (e.g., via NFC; via QR code scanning) from an external device (e.g., a contactless wireless terminal). Figure 7AD In this context, the form user interface 762 is associated with an activity (e.g., purchase; rental) enabled based on a selected link (e.g., from a webpage), where the activity relates to content associated with that link. Figure 7AJ In this context, the form user interface 784 is associated with an activity enabled based on selections from the search results (e.g., ordering).

[0300] In some implementations, the form user interface 784 includes an information area 784A that includes the name of the second coffee shop (e.g., "Mocha Coffee") and address and / or branch information about the second coffee shop, and a power representation 784B (e.g., an optional user interface object; an activatable user interface object) that, when activated, initiates a process related to enabling activities (e.g., purchase; lease) associated with the second coffee shop.

[0301] In some implementations, the form user interface 784 includes an image 784C indicating the second coffee shop (e.g., "Mocha Coffee") (e.g., an image of the second coffee shop; a logo of the supplier (e.g., an entity / company) operating the second coffee shop).

[0302] In some implementations, the form user interface 784 includes instructions 784D from a developer (e.g., an entity; a company) that operates a simplified version of the application (e.g., creating and / or managing templates for the simplified application) that can be used to enable activities associated with the second coffee shop (e.g., ordering one or more menu items). In some implementations, such as in Figure 7AJ In this context, the developer (e.g., entity / company) of the simplified version of the application (and the corresponding full version of the application) (e.g., "Mocha Coffee") is the supplier associated with the second coffee shop (e.g., "Mocha Coffee") (e.g., the same entity as the supplier; the same company as the supplier).

[0303] In some embodiments, the form user interface 784 includes a power representation 784E (e.g., an optional user interface object; an activatable user interface object) for accessing an application store (e.g., an application store controlled and managed by the developer of the operating system of computer system 700, where the application store can be used to download first-party and third-party applications to computer system 700). In some embodiments, a full version of an application corresponding to a simplified version of an application used to enable activities (e.g., ordering one or more menu items) can be downloaded to computer system 700 from the application store (e.g., via the power representation 784E of user interface 784).

[0304] In some implementations, the form user interface 784 includes a power representation 784F (e.g., an optional user interface object; an activatable user interface object) for eliminating (e.g., causing the computer system 700 to stop displaying) the form user interface 784 without performing activities associated with the second coffee shop (e.g., "Mocha Coffee") (e.g., ordering one or more menu items).

[0305] exist Figure 7AK In the process of displaying a form user interface 784 that can be used to initiate an activity associated with a second coffee shop (e.g., "Mocha Coffee") (e.g., ordering one or more menu items), the computer system 700 (e.g., via a touch-sensitive surface of the one or more input devices) detects activation 727 of the power indicator 784B (e.g., user selection for the power indicator; user tap input on the power indicator).

[0306] exist Figure 7AL In response to the detection of activation 727 of power indicator 784B, based on the determination that the full version of the application (e.g., the full version of the "Mocha Coffee" application) for enabling activities (e.g., ordering one or more menu items) is unavailable on computer system 700 (e.g., not installed on the computer system), computer system 700 displays a simplified user interface 786 for enabling activities (e.g., ordering one or more menu items) via display generation component 702. In some embodiments, if the simplified version of the application is not installed on computer system 700 (e.g., because this is the first time accessing the simplified version of the "Mocha Coffee" application), computer system 700 (e.g., in response to the detection of activation 727 of power indicator 784B) automatically (e.g., without user input; without user authorization) (e.g., before and / or simultaneously with the display of simplified user interface 786) downloads and installs the simplified version of the application.

[0307] In some implementations, the simplified user interface 786 differs from the reference above. Figure 7K The simplified user interface 716 described for the first time and the above reference Figure 7Z The simplified user interface 754, described for the first time (e.g., structurally different from the two simplified user interfaces; having a different layout than the two simplified user interfaces), is used because the simplified user interface 786 is operated by different developers. Figure 7AL As shown, in some embodiments, the simplified user interface 784 includes location information 788 (e.g., address) of the second coffee shop. In some embodiments, the simplified user interface 786 includes a menu area 790 that includes multiple optional menu items that can be ordered at the second coffee shop. In some embodiments, the simplified user interface 786 includes a power indicator 792 (e.g., an optional user interface object; an activatable user interface object) for ordering / checkout of the selected menu item.

[0308] like Figure 7AL As shown, in some embodiments, the simplified user interface 786 includes a user interface object 794 (e.g., a banner advertisement; a disc) that is displayed simultaneously with the simplified user interface 786 (e.g., overlaid on a portion of the simplified user interface 786) (e.g., similar to the reference above). Figure 7KThe user interface object 724 is described. In some embodiments, the user interface object 794 is displayed together with the simplified user interface 786 and for a predetermined time period (e.g., 10 seconds; 30 seconds; 1 minute). In some embodiments, the user interface object 794 includes instructions 794A (e.g., text information) from a developer (e.g., an entity; a company) who operates a simplified version of the application corresponding to the simplified user interface 786 (e.g., creating and / or managing templates for the simplified version of the application). In some embodiments, the user interface object 794 includes a shared capability representation 794B for initiating a process for sharing the simplified version of the application corresponding to the simplified user interface 786 with different users (e.g., transmitting electronic communications to different computer systems including the simplified version of the application and / or methods for initiating the download of the simplified version of the application).

[0309] Figure 7AM The computer system 700 is shown displaying a main user interface 796 via a display generation component 702 (e.g., a user interface including one or more application icons corresponding to applications installed on the computer system 700; a user interface controlled by the operating system of the computer system 700). Figure 7AM In this context, the main user interface 796 includes multiple application icons 798A-798I corresponding to the corresponding full version applications available on the computer system 700 (e.g., installed on the computer system).

[0310] Figure 7AN A computer system 700 is shown displaying a main user interface 796 via a display generation component 702. This main user interface includes multiple application icons 798A-798I corresponding to corresponding full-version applications available on the computer system 700 (e.g., installed on the computer system) and simplified application icons corresponding to simplified versions of the applications. Figure 7AN In the exemplary user interface depicted, the main user interface 796 includes a first simplified application icon 799A corresponding to a first simplified version application (e.g., "Mocha Coffee"), a second simplified application icon 799B corresponding to a second simplified version application (e.g., a simplified version application of "Food Review" for "Coffee Shop"), a third simplified application icon 799C corresponding to a third simplified version application (e.g., "Bicycle Rental"), a fourth simplified application icon 799D for a fourth simplified version application (e.g., "Shiny Cars"), and a fifth simplified application icon 799E for a fifth simplified version application (e.g., a simplified version application of "Food Review" for "Burger Queen"). Figure 7ANAs shown, in some implementations, simplified application icons 799A-799E corresponding to the installed simplified version of the application and application icons corresponding to the full version (regular) application installed on the computer system 700 are displayed in the same user interface (e.g., main user interface 796) and can be accessed from the same user interface.

[0311] In some implementation schemes, such as Figure 7AN The document also shows that the simplified application icon includes a first visual indicator (e.g., 799AA of simplified application icon 799A) (e.g., a first mark (e.g., with a graphic and / or text indicator)) that indicates the corresponding simplified application icon corresponds to a simplified version of the application (rather than the full version). In some embodiments, the first visual indicator (e.g., a first mark) is included in a first predefined location (e.g., the lower left corner) of the corresponding simplified application icon. In some embodiments, such as... Figure 7AN As shown, the simplified application icon includes a second visual indicator (e.g., 799AB of simplified application icon 799A) (e.g., a second marker (e.g., indicating a number)) that indicates the number of notifications (e.g., unchecked notifications) that have been generated by the corresponding simplified version of the application and / or are currently available to the corresponding simplified version of the application. In some embodiments, the second visual indicator (e.g., the second marker) is included in a second predefined location (e.g., the upper right corner) of the corresponding simplified application icon.

[0312] Figure 7AO A computer system 700 is shown displaying a main user interface 796, including application icons 798A-798I, via a display generation component 702. The main user interface 796 also includes folder icons 797 for simplifying the application icons. In some embodiments, the application icons are simplified (e.g., ...). Figure 7AN The simplified application icons 799A-799E are included in the folder corresponding to the folder icon 797 displayed on the main user interface 796 (for example, instead of being directly included in the main user interface 796). Figure 7AO In the document, folder icon 797 includes a simplified representation of application icons 799A-799E (e.g., thumbnails).

[0313] In some embodiments, similar to a simplified application icon, a folder icon 797 includes a first visual indicator 797B including a first visual indicator 797A (e.g., a first marker (e.g., having a graphic and / or text indicator)) indicating that the folder icon corresponds to a folder for a simplified version of the application (rather than for the full version of the application). In some embodiments, the first visual indicator 797A (e.g., a first marker) is included in a first predefined location (e.g., the lower left corner) of the corresponding simplified application icon. In some embodiments, the folder icon 797 includes a second visual indicator 797B (e.g., a second marker (e.g., showing a number)) indicating the (total) number of notifications (e.g., unchecked notifications) generated by the corresponding simplified application included in the folder corresponding to the folder icon 797 and / or currently available to the corresponding simplified application. In some embodiments, the second visual indicator 797B (e.g., a second marker) is included in a second predefined location (e.g., the upper right corner) of the folder icon 797.

[0314] Figure 7AP The computer system 700 is shown displaying a user selection 729 for a folder icon 797 displayed in the main user interface 796 via a display generation component 702.

[0315] exist Figure 7AQ In response to detecting a user selection 729 for folder icon 797, computer system 700 displays, via display generation component 702 (e.g., overlaid on a portion of main user interface 796), a list including the above references. Figure 7AN The first described simplified application icons 799A-799E are folder user interfaces 795 (e.g., pop-up user interfaces).

[0316] like Figure 7AQAs shown, in some embodiments, similar to simplified application icons, the folder user interface 795 includes a first visual indicator 795A (e.g., a first marker (e.g., with a graphic and / or text indicator)) indicating that the folder user interface 795 corresponds to a folder for a simplified version of the application (rather than for the full version of the application). In some embodiments, the first visual indicator 795A (e.g., the first marker) is included in a first predefined location (e.g., the lower left corner) of the corresponding simplified application icon. In some embodiments, the folder user interface 795 includes a second visual indicator 795B (e.g., a second marker (e.g., displaying a number)) indicating the (total) number of notifications (e.g., unchecked notifications) generated and / or currently available to the corresponding simplified application by the corresponding simplified application displayed in the folder user interface 795 via simplified application icons 799A-799E. In some embodiments, the second visual indicator 795B (e.g., the second marker) is included in a second predefined location (e.g., the upper right corner) of the folder user interface 795.

[0317] Figure 7AR The computer system 700 is shown via display generation component 702 (e.g., and after displaying folder user interface 795 including simplified application icons 799A-799E) (e.g., in response to detection). Figure 7AQ The activation of the simplified application 799E (e.g., user selection for the simplified application icon; user tap input on the simplified application icon) is displayed with the input from... Figure 7AQ The simplified application icon 799E corresponds to (for example, to the simplified version of the "Food Review" application corresponding to "Burger Queen") the simplified user interface 793.

[0318] Figure 7AS This is shown in the display (e.g., access). Figure 7AR After the simplified version of the "Hamburger Queen" application is displayed, the computer system 700 displays the folder user interface 795 via the display generation component 702. Figure 7AS In, with Figure 7AQ Instead, the simplified application icon 799E (for example, the one corresponding to the simplified version of the application for "Burger Queen") is moved to the first simplified application icon listed in the folder user interface 795 (for example, because the corresponding simplified version of the application was recently accessed / displayed by the computer system 700).

[0319] Figure 7AT This illustrates that after displaying the folder user interface 795, the computer system 700 (e.g., in response to detecting in) Figure 7ASThe activation of the simplified application icon 799E (e.g., user selection for the simplified application icon; tap input on the simplified application icon) is displayed via the display generation component 702 and from Figure 7AS The simplified application icon 799E corresponds to the simplified user interface 793.

[0320] exist Figure 7AT In the process of displaying the simplified user interface 793, the computer system 700 (e.g., via the touch-sensitive surface of the one or more input devices) detects input 731 (e.g., swipe input; upward swipe input on the bottom area of ​​the display generation component 702).

[0321] exist Figure 7AV In response to the detection of input 731 (in Figure 7AU As shown in the figure, the computer system 700 displays a multitasking user interface 791 via a display generation unit 702, the multitasking user interface including a plurality of user interface cards corresponding to a portion of the most recently displayed user interface.

[0322] exist Figure 7AV In the middle, the computer system 700 displays and interacts with data from the multitasking user interface 791. Figure 7AU The simplified user interface 793 (the recently displayed (e.g., accessed) user interface) corresponds to a user interface card 789 (e.g., a user interface preview image, a view of the application), the user interface card 787 corresponds to an application store (the second recently displayed (e.g., accessed) user interface), and the user interface card 785 corresponds to a simplified version of the application (the third recently displayed (e.g., accessed) user interface), the type of which is different from the simplified version of the application corresponding to user interface 793 (e.g., a "bike rental" simplified version application) (e.g., developed by different developers (e.g., different entities; different companies)). The user interface card 789 is the first user interface card shown (e.g., the user interface card is displayed on top) because it corresponds to the recently displayed (e.g., accessed) user interface.

[0323] Figure 7AW A computer system 700 is shown (e.g., in the display). Figure 7AV After the multitasking user interface 791, a simplified user interface 783 corresponding to the simplified version application is displayed via the display generation component 702. The type of the simplified version application corresponds to... Figure 7AV The simplified user interface 793 is the same as the simplified version of the application (e.g., the simplified version of the "Food Review" application) (e.g., developed by the same developer (e.g., the same entity; the same company)). Figure 7AWThe simplified user interface 783 corresponds to a simplified user interface for a first supplier (e.g., a coffee shop named "Mocha Coffee"), where the first supplier is using a corresponding simplified version of the application developed by a first developer (e.g., a first entity or company named "Food Review"). Figure 7AU The simplified user interface 793 corresponds to a simplified user interface for a second supplier (e.g., a restaurant named "Burger Queen"), where the second supplier is using a corresponding simplified version of the application developed by the same first developer.

[0324] Figure 7AX A computer system 700 is shown displaying a multitasking user interface 791 via a display generation component 702 (e.g., immediately after displaying a simplified user interface 783 and without displaying different user interfaces for different applications). Figure 7AX As shown, because Figure 7AW The simplified user interface 783 is the most recently displayed user interface, so the multitasking user interface 791 now includes... Figure 7AW The simplified user interface 783 corresponds to the user interface card 781 as the most recently displayed (e.g., accessed) user interface. In some implementations, such as Figure 7AX As shown, the multitasking user interface 791 includes a user interface card 789 corresponding to a simplified user interface 793, which is a previously recently displayed (e.g., accessed) user interface, serving as a second recently displayed (e.g., accessed) user interface. In some embodiments, the computer system 700 maintains the display of two different user interface cards from different vendors, both corresponding to simplified versions of the same type of application in the multitasking user interface 791 (e.g., both corresponding to a simplified version of the "Food Review" application). Figure 7AX As shown, the multitasking user interface 791 includes a user interface card 787 as a third recently displayed (e.g., accessed) user interface.

[0325] Figure 7AY A computer system 700 is shown displaying a multitasking user interface 791 via a display generation component 702 (e.g., immediately after displaying a simplified user interface 783 and without displaying different user interfaces for different applications). Figure 7AY As shown, because Figure 7AW The simplified user interface 783 is the most recently displayed user interface, so the multitasking user interface 791 includes... Figure 7AWThe simplified user interface 783 corresponds to the user interface card 781 as the most recently displayed user interface. In some embodiments, if a simplified version of the same type of application is displayed (e.g., accessed), even for different vendors (e.g., "Mocha Coffee" and "Burger Queen"), the computer system 700 removes the display of the user interface card corresponding to the same simplified version of the application but for a different vendor, which has been included in the multitasking user interface 791. For example, in Figure 7AY In this context, the multitasking user interface 791 does not include a user interface card 789 corresponding to the simplified user interface 793 because the simplified user interface 783 corresponding to the same simplified version of the application (e.g., the "Food Review" simplified version application) has been accessed recently. Instead, in... Figure 7AQ In the multitasking user interface 791, following the user interface card 781 corresponding to the simplified user interface 783, there are a user interface 787 corresponding to the previously second most recently displayed (e.g., accessed) application and a user interface card 785 corresponding to the previously third most recently displayed (e.g., accessed) application.

[0326] exist Figure 7AY In the process of displaying the multitasking user interface 791, the computer system 700 (e.g., via the touch-sensitive surface of the one or more input devices) detects a user selection 733 (e.g., a tap on the user interface card) for the user interface card 787 corresponding to the application store.

[0327] exist Figure 7AZ In response to detecting a user selection 733 for user interface card 787, computer system 700 displays a user interface 779 corresponding to the application store via display generation component 702. In some embodiments, computer system 700 displays a first page 777 (e.g., a search page; search tab) in the application store's user interface 779, which includes one or more suggested (e.g., recommended) applications. In some embodiments, the application store suggests (e.g., recommends) downloading the full version of an application corresponding to a simplified version of an application installed on and / or already displayed / accessed via the computer system. For example, in Figure 7AZ In the application store's user interface 779, the first page 777 includes content corresponding to... Figure 7AW The simplified user interface 783 corresponds to the full version of the simplified application, which is the first application suggestion 775A of the application (e.g., the full version of the "Food Review" application corresponding to the simplified version of the "Food Review" application). In some implementations, such as Figure 7AZAs shown, the first application suggestion 775A includes a power indication 775B (e.g., an optional user interface object; an activatable user interface object), which, when activated, initiates a process on computer system 700 for downloading and installing the corresponding full version of the application.

[0328] Figures 8A to 8B This is a flowchart illustrating a method for using computer system calls associated with an application, according to some embodiments. Method 800 is executed at a computer system (e.g., 100, 300, 500, 700) (e.g., an electronic device, a smart device such as a smartphone or smartwatch, a mobile device, a wearable device), which communicates with a display generating component (e.g., 702) and one or more input devices (e.g., a touch-sensitive surface integrated with the display generating component). Some operations in method 800 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0329] As described below, method 800 provides an intuitive way to enable activities using a computer system. This method reduces the cognitive burden on users when enabling activities using a computer system, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to enable activities more quickly and efficiently saves power and increases the time interval between battery charging sessions.

[0330] The computer system (e.g., 700) (e.g., via one or more location sensors, such as GPS sensors, communicating with the computer system) detects (802) the occurrence of triggering conditions (e.g., scanning a QR code, detecting an NFC signal, detecting the selection of a hyperlink, detecting / determining the presence of a computer system near a location beacon, detecting / determining the presence of a computer system at / in a specific geographic location) for initiating an activity (e.g., reservation, placing an order, booking, making a payment, making a request) associated with the first application (e.g., an application corresponding to a merchant, store, restaurant, and / or service provider).

[0331] In response to the detection of a trigger condition (804), the computer system (e.g., 700) displays (806) a first user interface (e.g., 706, 734, 752, 762, 784) via a display generation component (e.g., 702) (e.g., overlaid on a wake-up screen user interface (e.g., 704), overlaid on a desktop or home screen user interface, overlaid on another application user interface) (e.g., overlaid on another application user interface). This could be an interstitial user interface, a form user interface, a mini-user interface that covers a portion but not all of a previously displayed user interface so that the previous user interface remains visible on the display, or a pop-up user interface. In some embodiments, the home screen is the main user interface of the computer system provided by the computer system's operating system. In some embodiments, the home screen is a graphical user interface (e.g., having one or more pages or screens) provided by the computer system's operating system and includes links to applications, settings, and / or notifications (e.g., display options for launching or accessing applications, settings, and / or notifications).

[0332] In some implementations, in response to the detection of a triggering condition, based on the determination that the first application is unavailable on the computer system (e.g., 700) (e.g., not downloaded to the computer system, not installed on the computer system, not stored on the computer system, or cannot be started or accessed on the computer system), the computer system (e.g., 700) displays or causes to display a first user interface without obtaining (e.g., downloading, installing) the first application.

[0333] Displaying a first user interface (e.g., 706, 734, 752, 762, 784) includes simultaneously displaying a description of the activity (e.g., 706A, 734A, 752A, 762A, 784A) (e.g., text information about the activity, an image associated with the activity, an indication or logo associated with the company providing or enabling the activity) (808) and a first optional user interface object (e.g., 706B, 734B, 752B, 762B, 784B) for taking actions associated with the activity (e.g., reservation, booking, purchase) (e.g., a first indicator, a first optional button) (810). In some embodiments, the first optional user interface object includes an indication of the type of activity available (e.g., text information about the type of activity, such as "reservation," "booking," "payment"). Displaying the first user interface in response to detecting a trigger condition allows the user to know that the computer system is available to perform the activity and to quickly and easily access the activity on the computer system. Performing optimal actions when a set of conditions have been met and no further user input is required enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the computer system). This, in turn, reduces power consumption and extends the battery life of the computer system by enabling users to use it more quickly and efficiently.

[0334] When displaying the first user interface (e.g., 706, 734, 752, 762, 784) (814), the computer system (e.g., 700) detects (816) the activation of the first optional user interface object (e.g., 701, 717, 719, 723, 727) (e.g., user selection for the first optional user interface object) via the one or more input devices.

[0335] In response to the detection of activation of a first optional user interface object (e.g., 706B, 734B, 752B, 762B, 784B) (e.g., 701, 717, 719, 723, 727) (818), based on the determination (820) that the first application is unavailable on the computer system (e.g., 700) (e.g., not downloaded to the computer system, not installed on the computer system, not stored on the computer system, or cannot be started or accessed on the computer system), the computer system displays (822) via a display generation component (e.g., 702) a second user interface (e.g., 716, 736, 754, 764, 786) configured to perform activities without downloading at least a portion of the first application (e.g., without obtaining the first application, without downloading the full version of the application) (e.g., a user interface of a simplified version of an application associated with or related to the full version of the application). In some implementations, the second user interface is configured to perform activities using (e.g., by downloading) a simplified version of the first application (e.g., instead of downloading the full version of the first application). In some implementations, the simplified version of the first application is smaller than the corresponding full version of the first application (e.g., requires less memory). In some implementations, the simplified version of the first application is faster to download and access, and requires less memory resources to store and access (e.g., therefore loads and starts faster on the corresponding computer system) compared to the corresponding full version of the application. In some implementations, the simplified version of the first application enables a subset (e.g., but not all) of the features (e.g., capabilities) of the corresponding full version of the application. Even when at least that part of the first application is unavailable on the computer system and without the need to download the first application (e.g., the full version) to the computer system, displaying the second user interface, configured to perform activities without downloading at least that part of the first application, provides the user with quick and easy access to the features of the first application used to perform the activities, based on the determination that the first application is unavailable on the computer system. Performing optimal actions when a set of conditions have been met and no further user input is required enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the computer system). This, in turn, reduces power consumption and extends the battery life of the computer system by enabling users to use it more quickly and efficiently.

[0336] In some embodiments, displaying a second user interface (e.g., 716, 736, 754, 764, 786) includes displaying the second user interface (824) without requesting authentication information (e.g., biometric authentication information (e.g., fingerprint authentication information, facial recognition authentication information, retinal / iris recognition information), password or password authentication information) to authorize the display of the second user interface. In some embodiments, in response to detecting activation of a first optional user interface object (e.g., even if the first optional user interface object is already displayed (e.g., overlaid on) the lock screen or wake screen of the computer system (e.g., 700), the computer system may display (or cause to display) the second user interface without authorization (e.g., via biometric authentication, via password / password authentication). Displaying the second user interface without requesting authentication information to authorize the display of the second user interface provides the feature of quick access to the second user interface without requiring additional input. Reducing the amount of input required to perform operations enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the computer system). This, in turn, reduces power consumption and extends the battery life of the computer system by enabling users to use it more quickly and efficiently.

[0337] In some implementations, based on a determination that the first application is unavailable on the computer system (e.g., 700) (e.g., not downloaded to the computer system, not installed on the computer system, not stored on the computer system, or cannot be started or accessed on the computer system), the computer system initiates (826) a process for (e.g., automatically, without requesting user permissions) to download (e.g., and install) software configured to perform activities on the computer system, the software (e.g., a simplified version of the first application instead of the full version of the first application, a version of the first application configured to perform activities without at least a portion of the first application) not including at least that portion of the first application. In some implementations, if this is the first time the first application is invoked on the computer system (e.g., based on a detected triggering condition), the computer system initiates a process for (e.g., automatically, without requesting user permissions) to download the software, and thus the first application is unavailable on the computer system. In some implementations, the computer system downloads software configured to perform activities on the computer system when a first user interface is displayed, the software (e.g., a simplified version of the first application) not including at least that portion of the first application. In some implementations, the computer system, in response to detecting activation of a first optional user interface object, downloads software configured to perform an activity onto the computer system. This software (e.g., a simplified version of the first application) does not include at least that portion of the first application. Based on a determination that the first application is unavailable on the computer system, (e.g., automatically, without user input) a process is initiated to download (e.g., install) the software configured to perform an activity onto the computer system, which does not include at least that portion of the first application. This allows the user to access the first application without manually downloading it to the computer system. Reducing the amount of input required to perform an operation enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate input and reducing user errors when operating / interacting with the computer system). This, in turn, reduces power consumption and extends the battery life of the computer system by enabling the user to use it more quickly and efficiently.

[0338] In some implementations, in response to the detection of activation (e.g., 701, 717, 719, 723, 727) (818) of a first optional user interface object (e.g., 706B, 734B, 752B, 762B, 784B), the computer system displays (830) a third user interface (e.g., a user interface of a full version of the first application) via a display generation component (e.g., 702), based on a determination (828) that the first application is available on the computer system (e.g., 700) (e.g., downloaded to the computer system, installed on the computer system, stored in the computer system, or available to be launched or accessed on the computer system). The third user interface is the user interface of the first application configured to perform active operations. Displaying the third user interface based on the determination that the first application is available on the computer system, where the third user interface is the user interface of the first application configured to perform active operations, allows the user to quickly and easily access (e.g., all) features of the first application. Performing an operation when a set of conditions has been met and no further user input is required enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the computer system). This, in turn, reduces power consumption and extends the battery life of the computer system by enabling users to use it more quickly and efficiently.

[0339] In some implementations, a second user interface (e.g., 716, 736, 754, 764, 786) corresponds to software configured to perform activities (e.g., a simplified version of the first application; a version of the first application configured to perform activities without at least a portion of the first application), the software excluding at least that portion of the first application, and a third user interface corresponds to the first application (e.g., a full version of the first application), wherein both the software configured to perform activities, excluding at least that portion of the first application, and the first application correspond to a common application source (e.g., the same developer (e.g., the developer of the first application); the same company (the company that developed / is developing the first application)).

[0340] In some implementations, displaying a first user interface (e.g., 706, 734, 752, 762, 784) includes displaying the first user interface on (e.g., overlaid on) a background user interface (e.g., a portion, but not all) (e.g., overlaid on a previously displayed user interface, overlaid on a wake-up screen user interface (e.g., 704), overlaid on a desktop or home screen user interface) (812). Displaying the first user interface on (e.g., overlaid on) a background user interface allows the user to simultaneously view at least a portion of both the first user interface and the background user interface that has already been displayed. Providing additional control over the computer system without cluttering the UI due to additional displayed controls enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the computer system), which in turn reduces power consumption and extends the battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.

[0341] In some implementations, the first user interface (e.g., 706, 734, 752, 762, 784) or the second user interface (e.g., 716, 736, 754, 764, 786) includes activity-related information (e.g., identifying the activity; indicating an identifier for the activity; describing the activity) (e.g., call-based information (e.g., a specific branch of a store or restaurant; a table number within the restaurant; an object identifier (e.g., an object number, such as a bicycle number); supplier-specific information), wherein this information is determined based on detected trigger conditions (832). In some implementations, the determination of a first type of trigger condition is based on detected trigger conditions (e.g., scanning a QR code; detecting an NFC signal; detecting a selection of a hyperlink; detecting / determining the presence of a computer system near a location beacon; detecting / determining the presence of a computer system at / in a specific geographic location), and the computer system displays or causes to display first information (e.g., supplier-specific information) via a display generation component based on the detected trigger conditions. In some implementations, based on detected trigger conditions... The determination of a second type of trigger condition, different from the first type of trigger condition (e.g., scanning a QR code; detecting an NFC signal; detecting a selection of a hyperlink; detecting / determining the presence of a computer system near a location beacon; detecting / determining the presence of a computer system at / in a specific geographic location), is based on the detected trigger condition. The computer system (e.g., 700) displays or causes to display second information (e.g., vendor-specific information) that differs from the first information. Providing activity-related information in a first or second user interface, where this information is determined based on the detected trigger condition, allows the user to quickly and easily view activity-related information and thus effectively perform activities using the computer system. Providing improved feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the computer system), which in turn reduces power consumption and extends the battery life of the computer system by enabling the user to use the computer system more quickly and effectively.

[0342] In some implementations, the detected trigger conditions include the activation (user selection) of a link (e.g., a displayed hyperlink; a link displayed in a message, an application, or a webpage / website). A first user interface (e.g., 706, 734, 752, 762, 784) is displayed in response to the detection of a trigger condition, where the detected trigger condition includes the activation of a link, allowing the user to quickly and easily view information about how the computer system can be used to perform activities and to efficiently access activities using the computer system. Performing optimal operation when a set of conditions has been met without requiring additional user input enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the computer system), which in turn reduces power consumption and extends the battery life of the computer system by enabling the user to use it more quickly and efficiently.

[0343] In some implementations, the detected trigger conditions include the detection of physical objects (e.g., objects detectable via NFC connection; QR or barcodes detectable / scanned by a computer system (e.g., 700)) via NFC or other wireless communications; or scanning QR or barcodes with a camera or other sensors for detecting visual information. A first user interface (e.g., 706, 734, 752, 762, 784) is displayed in response to the detection of a trigger condition, where the detected trigger condition includes the detection of a physical object. This allows the user to quickly and easily view information about how the computer system can be used to perform activities and conveniently access activities using the computer system. Performing optimal operation when a set of conditions has been met without requiring additional user input enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the computer system). This, in turn, reduces power consumption and extends the battery life of the computer system by enabling the user to use it more quickly and efficiently.

[0344] In some implementations, the detected triggering conditions include detecting that the computer system (e.g., 700) is in (e.g., near, adjacent to) a corresponding location using geographic information about the computer system or broadcast beacons and / or other computer system location technologies such as WiFi triangulation (e.g., location from a point of interest in a map application; location-based determination that the computer system is in a specific location where an activity can be performed (e.g., at a particular restaurant; at a particular store)). A first user interface (e.g., 706, 734, 752, 762, 784) is displayed in response to the detection of the triggering conditions, wherein the detected triggering conditions include detecting that the computer system is in a corresponding location, which allows the user to recognize that the computer system is available to perform an activity and provides quick and easy access to activities on the computer system. Performing optimal operation when a set of conditions has been met without requiring additional user input enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the computer system), which in turn reduces power consumption and extends the battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.

[0345] In some embodiments, the detected trigger condition includes the initiation of a search performed on the computer system (e.g., 700) (e.g., using general search features of the computer system). In some embodiments, the computer system displays the search results (e.g., as shown in 772) of a search performed on the computer system (e.g., searching for restaurants, shops, bicycles, etc.) via a display generation component (e.g., 702). In some embodiments, the detected trigger condition includes detecting a user selection of a specific search result from the plurality of displayed search results. A first user interface (e.g., 706, 734, 752, 762, 784) is displayed in response to the detection of the trigger condition, wherein the detected trigger condition includes the initiation of a search performed on the computer system, which allows the user to quickly and easily view information about how the computer system can be used to perform activities and to effectively access activities using the computer system. Performing optimal actions when a set of conditions have been met and no further user input is required enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the computer system). This, in turn, reduces power consumption and extends the battery life of the computer system by enabling users to use it more quickly and efficiently.

[0346] In some implementations, after displaying a second user interface (e.g., 716, 736, 754, 764, 786), the computer system (e.g., 700) displays a main user interface (e.g., 796) (e.g., the main screen or one or more screens / pages of the main screen; the main user interface controlled by the operating system of the computer system) via a display generation component (e.g., 702). The main user interface includes multiple application user interface objects (e.g., application icons) corresponding to a respective application available on the computer system (e.g., downloaded to the computer system; installed on the computer system), wherein the main user interface does not include (e.g., not included in any of the one or more screens / pages of the main screen) the application user interface objects used to launch the second user interface.

[0347] In some implementations, the main user interface (e.g., 796) includes one or more screens or pages that include the plurality of application user interface objects (e.g., 798A-798I) (e.g., application icons). In some implementations, the application user interface objects used to launch a second user interface (e.g., 716, 736, 754, 764, 786) are not included in any of the one or more screens or pages of the main user interface.

[0348] In some implementations, in response to detecting the activation (e.g., selection) of an application user interface object (e.g., an application icon) for launching a second user interface (e.g., 716, 736, 754, 764, 786), the computer system (e.g., 700) displays or causes the second user interface (e.g., 716, 736, 754, 764, 786) to be displayed via a display generation component (e.g., 702).

[0349] In some implementations, the main user interface (e.g., 796) does not include application user interface objects (e.g., application icons) corresponding to the application, wherein a first version (e.g., a simplified version) of the corresponding application is available on the computer system (e.g., 700), but a second version (e.g., a full version) of the corresponding application is not available on the computer system. In some implementations, the main user interface only includes application user interface objects (e.g., 798A-798I) (e.g., application icons) corresponding to the application, wherein a second version (full version) of the corresponding application is available on the computer system.

[0350] In some embodiments, after displaying a second user interface (e.g., 716, 736, 754, 764, 786), the computer system (e.g., 700) displays a main user interface (e.g., 796) (e.g., the home screen; the main user interface controlled by the computer system's operating system) via a display generation component (e.g., 702), which includes a second optional user interface object (e.g., 797) (e.g., a folder; a menu). In some embodiments, when displaying the second optional user interface object (e.g., 797), the computer system (e.g., 700) detects the activation (e.g., 729) (e.g., a selection) of the second optional user interface object via one or more input devices. In some embodiments, in response to the detection of activation (e.g., 729) of a second optional user interface object (e.g., 797), the computer system (e.g., 700) displays an application user interface object (e.g., 799A-799E) (e.g., an application icon) for launching the second user interface (e.g., 716, 736, 754, 764, 786) via a display generation component (e.g., 702) (in a user interface corresponding to an application icon for a first version (e.g., a simplified version) of an application downloaded to the computer system). In some embodiments, in response to the detection of activation (e.g., selection) of an application user interface object (e.g., an application icon) for launching the second user interface (e.g., 716, 736, 754, 764, 786), the computer system (e.g., 700) displays or causes the second user interface to be displayed via the display generation component (e.g., 702). In some implementations, the application user interface object (e.g., 799A-799E) (e.g., an application icon) used to launch the second user interface includes an indication (e.g., a label) that the application user interface object corresponds to a first version (e.g., a simplified version) of the first application (as opposed to a second version (e.g., a full version) of the first application). In response to detecting activation of a second optional user interface object included in the main user interface, displaying the application user interface object (e.g., an application icon) used to launch the second user interface allows the user to quickly and easily launch the second user interface from the main user interface. Reducing the amount of input required to perform operations enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the computer system), which in turn reduces power consumption and extends the battery life of the computer system by enabling the user to use it more quickly and efficiently.

[0351] In some implementations, in response to detecting the activation of a second optional user interface object, the computer system abandons displaying the application user interface object (e.g., application icon) for launching the second user interface (e.g., 1 day, 1 week, 2 weeks, 1 month, 3 months, 6 months, 1 year) via the display generation component (e.g., 702) (in the user interface corresponding to the folder (e.g., temporary folder) for the application icon corresponding to the first version (e.g., simplified version) application downloaded to the computer system) for launching the second user interface (e.g., 716, 736, 754, 764, 786).

[0352] In some implementations, the application user interface object used to launch the second user interface (e.g., 716, 736, 754, 764, 786) is not displayed because the application user interface object has been removed (e.g., deleted) from the computer system (e.g., 700). In some implementations, in response to detecting activation of the second optional user interface object, based on a predetermined time period (e.g., 1 day, 1 week, 2 weeks, 1 month, 3 months, 6 months, 1 year) since the second user interface was accessed (e.g., launched; displayed) on the computer system, the computer system removes (e.g., deletes) the software used to launch the second user interface from the computer system (e.g., corresponding to; required for) the software. Removing the software used to launch the second user interface from the computer system based on a predetermined time period since the second user interface was accessed on the computer system (e.g., automatically, without user input) frees up storage space on the computer system previously used by software that the user may no longer access on the computer system. Performing an operation when a set of conditions has been met and no further user input is required enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the computer system). This, in turn, reduces power consumption and extends the battery life of the computer system by enabling users to use it more quickly and efficiently.

[0353] In some implementations, when a first application process corresponding to a second user interface (e.g., 716, 736, 754, 764, 786) has recently been used on a computer system (e.g., 700) (e.g., active in the background; currently running in the background), the computer system displays multiple user interface preview items (e.g., user interface objects indicating applications that have been launched, are currently active, and / or are running on the computer system) via a display generation component (e.g., 702) (e.g., in a multitasking user interface; in a multitasking screen). These preview items include images of the user interface (current instance) of the corresponding application used for an application that has recently been used on the computer system (e.g., active in the background; currently running in the background; launched and not yet closed). These multiple user interface preview items include the first user interface preview item corresponding to the second user interface. In some implementations, upon detecting that the first application process corresponding to the second user interface is no longer enabled (e.g., closed), the computer system no longer includes the first user interface preview item within the multiple user interface preview items. The inclusion of a first user interface preview project corresponding to the second user interface in the multiple user interface preview projects provides users with quick and easy access to the second user interface. Providing additional control options without cluttering the UI with additional displayed controls enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the computer system). This, in turn, reduces power consumption and extends the computer system's battery life by enabling users to use the computer system more quickly and efficiently.

[0354] In some implementations, when a first application process corresponding to a second user interface (e.g., 716, 736, 754, 764, 786) and a second application corresponding to the second user interface have recently been used on a computer system (e.g., 700) (e.g., both are active (e.g., in the background); both are currently running (e.g., in the background)), wherein the first application process corresponds to a first instance of the second user interface (e.g., at a first time, a first location, and / or with respect to a first object) and the second application process corresponds to a second instance of the second user interface (e.g., at a second time, a second location, and / or with respect to a second object), the computer system displays a plurality of user interface preview items via a display generation component (e.g., 702) (e.g., in a multitasking user interface; in a multitasking screen), wherein the plurality of user interface preview items includes a first user interface preview item corresponding to a first instance of the second user interface and a second user interface preview item corresponding to a second instance of the second user interface.

[0355] In some embodiments, after displaying a second user interface (e.g., 716, 736, 754, 764, 786) configured to perform activities without downloading at least that portion of the first application, the computer system (e.g., 700) displays an application store user interface (e.g., a user interface for an application store from which applications can be searched and where application downloads can be initiated) via a display generation component (e.g., 702). In some embodiments, the computer system simultaneously displays a third optional user interface object (e.g., a power indicator; an optional download button) in the application store user interface, which, when activated, initiates a process for downloading the first application to the computer system, and an indication (e.g., a description) of how (e.g., accessed; launched) the second user interface on the computer system (e.g., an indication (e.g., a description) of how, when, and / or where the second user interface was used on the computer system). A third optional user interface object is simultaneously displayed within the application store user interface. When activated, this third optional user interface object initiates the process of downloading the first application to the computer system, along with an indication that the second user interface has been used on the computer system. This allows the user to easily recognize that the second user interface has already been used on the computer system, while enabling the user to efficiently download the first application (e.g., one associated with the second user interface) to the computer system. Providing improved visual feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the computer system). This, in turn, reduces power consumption and extends the computer system's battery life by enabling users to use the computer system more quickly and efficiently.

[0356] In some embodiments, when displaying a second user interface (e.g., 716, 736, 754, 764, 786), the computer system (e.g., 700) displays user interface elements (e.g., banner ad areas or notification areas within the second user interface) that include an indication that a first application can be downloaded to the computer system (e.g., 700) (e.g., via an app store). In some embodiments, this indication includes a download user interface object (e.g., a download enablement), which, when activated (e.g., selected), initiates a process for downloading the first application to the computer system. Displaying user interface elements including an indication that the first application can be downloaded to the computer system when displaying the second user interface allows the user to quickly and easily recognize that the application corresponding to or associated with the displayed user interface—the first application—can be downloaded to the computer system. Providing improved visual feedback enhances the operability of computer systems and makes user-system interfaces more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with computer systems). This, in turn, reduces power consumption and extends the battery life of computer systems by enabling users to use them more quickly and effectively.

[0357] In some embodiments, the user interface elements (e.g., 724, 762, 784) (e.g., banner ad areas or notification areas within a second user interface) also include a fourth optional user interface object (e.g., a power indicator; an optional share button), which, when activated, initiates a process (e.g., a sharing process) to enable the second computer system (different from the first computer system) to access (e.g., display) a second user interface for performing activities without downloading at least that portion of the first application to the second computer system. In some embodiments, temporarily displaying a user interface element (e.g., a notification; a banner ad notification) causes the computer system to stop displaying the user interface element after a predetermined time period (e.g., 10 seconds, 30 seconds, one minute) has elapsed since the element was displayed. Including a fourth optional user interface object, when activated, to initiate a process (e.g., a sharing process) to enable the second computer system (different from the first computer system) to access a second user interface for performing activities without downloading at least that portion of the first application to the second computer system allows the user to effectively enable the second computer system to perform activities with less input. Reducing the amount of input required to perform operations enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the computer system). This, in turn, reduces power consumption and extends the battery life of the computer system by enabling users to use it more quickly and efficiently.

[0358] In some implementations, the application process corresponding to the second user interface (e.g., 716, 736, 754, 764, 786) is enabled (e.g., permitted) to display a notification including information related to the execution activity. In some implementations, when the application process corresponding to the second user interface is active on the computer system (e.g., 700) (e.g., running in the background; starting in the background), the computer system may display (or cause to display) a notification about the execution activity.

[0359] In some implementations, the second user interface (e.g., 716, 736, 754, 764, 786, 793) corresponds to software configured to perform activities (e.g., a simplified version of the first application; a version of the first application configured to perform activities without at least a portion of the first application). In some implementations, in response to detecting the activation of a first optional user interface object (e.g., 706B, 734B, 752B, 762B, 784B), a computer system (e.g., 700) sets one or more system permissions on the software to include the permission to generate notifications (e.g., 748, 1399) on the computer system within a predetermined time period (e.g., a limited duration) (e.g., 8 hours; 12 hours; until the end of the day). (For example, automatically, without additional user input) setting one or more system permissions for the software to include the permission to generate notifications on the computer system for a predetermined period of time. This enables the software to provide features (providing notifications related to the performance of activities) on the computer system for a period of time during which the software's notifications are most useful and relevant to the user of the computer system, thereby enabling the user to utilize the software more effectively. At the same time, preventing the software from providing notifications after the period of time has passed prevents the computer system from unnecessarily consuming power, which in turn extends the battery life of the computer system.

[0360] In some implementations, activation of a first optional user interface object is detected at a first time. In some implementations, at a second time after the first time, the computer system (e.g., 700) detects (e.g., determines) the occurrence of a notification event (e.g., an event that meets the criteria for generating a notification; an event related to an activity performed by the software; the presence of a computer system near a location beacon is detected / determined; the presence of a computer system at / in a specific geographic location is detected / determined), which corresponds to the occurrence of a second application (e.g., applications corresponding to the simplified user interfaces 716, 736, 754, 764, 786, 793, respectively) (e.g., a simplified version of the first application; a version of the first application configured to perform activities without at least a portion of the first application). In some implementations, in response to the detection of a notification event, based on a second time within a predetermined time period from a first time (e.g., within 8 hours of the first time; within 12 hours of the first time; on the same day as the first time), the computer system displays a notification (e.g., 748, 1399) corresponding to the detected notification event via a display generation component (e.g., 702) (e.g., push notification; alert). In some implementations, in response to the detection of a notification event, based on a second time not within a predetermined time period from the first time (e.g., as via...), the computer system displays a notification (e.g., 748, 1399) corresponding to the detected notification event via a display generation component (e.g., 702). Figure 13V (As shown in the right-hand depiction of computer system 700) (e.g., more than 8 hours since the first time; more than 12 hours since the first time; after the day the first time occurred), the computer system, via the display generation component, abandons the display of the notification corresponding to the detected notification event. Based on whether the second time is displayed or abandoned within a predetermined time period from the first time, it avoids unnecessarily extending the access of applications that are not full versions of the application and are designed for temporary use (unlike full versions of the application) to the ability to generate notifications. This, in turn, improves system security by avoiding unnecessary access to system permissions and reducing software power consumption, which in turn reduces power consumption and extends the battery life of the computer system.

[0361] In some implementations, the predetermined time period is based on the amount of time elapsed since a predetermined type of user interaction was detected with respect to the second application (e.g., applications corresponding to simplified user interfaces 716, 736, 754, 764, 786, 793, respectively) (e.g., a predetermined amount of time elapsed since the second application was last displayed via the display generation component of the computer system). Automatically setting the predetermined time period for allowing notifications based on the detected user interaction with the second application enables the computer system to generate relevant notifications corresponding to the second application that are useful to the user, while also enabling the computer system to stop generating notifications corresponding to the second application after the user has stopped using the second application (e.g., after a predetermined time period has elapsed since the user last interacted with the second application). In response to detecting user interaction with a second application (e.g., via notification), automatically providing useful information within a predetermined time period reduces the amount of input required to perform operations, enhancing the operability of the computer system and making the user-system interface more efficient (e.g., by assisting the user in providing appropriate input and reducing user errors when operating / interacting with the computer system). This, in turn, reduces power consumption and extends the battery life of the computer system by enabling users to use it more quickly and efficiently. Furthermore, refusing to generate additional notifications from the second application after the user has stopped using it improves system security by avoiding unnecessary access to system permissions and reducing software power consumption, which again reduces power consumption and extends the battery life of the computer system.

[0362] In some implementations, when a first application (e.g., the application corresponding to user interface 708, the application corresponding to user interface 1348, the application corresponding to user interface 1394) is installed on a computer system (e.g., 700), the computer system detects the occurrence of a second notification event (e.g., a notification event corresponding to software (e.g., a simplified version of the application); an event related to an activity performed by the software; detecting / determining the presence of a computer system near a location beacon; detecting / determining the presence of a computer system at / in a specific geographical location). In some implementations, in response to detecting the occurrence of the second notification event, the system, based on one or more system permissions of the first application including the permission to generate a notification (e.g., such as...). Figures 13I to 13J Upon determination of the second notification event, the computer system displays a notification (e.g., 748, 1399) corresponding to the detected second notification event via a display generation component (e.g., 702). In some embodiments, the one or more system permissions of the first application do not include the permission to generate notifications (e.g., such as...). Figure 13SUpon determining that (for example, because the permission has been denied by the user), the computer system, via the display generation component, abandons the display of the notification corresponding to the detected second notification event. When a notification event is detected, allowing the first application to generate a notification when its one or more system permissions include the permission to generate a notification, and preventing the first application from generating a notification when its one or more system permissions do not include the permission to generate a notification, improves security. Therefore, by allowing the first application to perform tasks consistent with its system permissions while preventing the first application from performing tasks inconsistent with its system permissions, the computer system is used more securely.

[0363] It should be noted that the above description is relative to the process described in method 800 (e.g., Figures 8A to 8B The details of the above-described methods also apply in a similar manner to the methods described below. For example, method 1000 optionally includes one or more features of the various methods described above with reference to method 800. For example, via reference... Figures 7A to 7AZ One or more of the described methods may initiate a process for enabling activity on a corresponding computer system. The corresponding simplified user interface displayed on the corresponding computer may include customized content based on information received or detected from the initiating process. For another example, method 1200 may optionally include one or more features of the various methods described above with reference to method 800. For example, this may be achieved via reference to... Figures 11A to 11S The described methods access and / or manage, on the corresponding computer system (e.g., again), via reference-based... Figures 7A to 7AZ The procedures initiated by one or more of the described methods display a corresponding simplified user interface on the respective computer system, which is used to enable an activity on the respective computer system. For another example, method 1400 optionally includes one or more features of the various methods described above with reference to method 800. For example, features for setting references... Figures 13A to 13V The process of granting one or more system permissions to the described application can be applied to applications configured to not download, as referenced. Figures 7A to 7AZ The software that performs the activity of the user interface in at least a portion of the described application. For the sake of brevity, these details will not be repeated below.

[0364] Figures 9A to 9T Exemplary user interfaces are shown, according to some implementation schemes, for customizing content displayed based on a context (e.g., the situation) of the content being invoked. The user interfaces in these figures are used to illustrate the processes described below, including... Figures 10A to 10C The process in.

[0365] Figures 9A to 9EAn exemplary user interface is shown for location-based customization of displayed content (e.g., using an application from the same developer to customize content for different vendors).

[0366] Figure 9A A user interface 904 corresponding to a wake-up screen (e.g., a lock screen) of a computer system 700 is shown displayed via a display generation component 702. In some embodiments, the wake-up screen is a user interface displayed when the display generation component of the computer system transitions from an inactive (e.g., off) state to an active (e.g., on) state. In some embodiments, the lock screen is a user interface displayed when the computer system is operating in a locked state, in which at least some functions of the computer system are restricted (e.g., until the computer system is unlocked).

[0367] Computer system 700 (e.g., via one or more location sensors (e.g., GPS sensors)) (e.g., when displaying user interface 904, when displaying a different user interface, or when display generation component 702 is in a closed state) detects that the computer system is in (e.g., has entered) a location corresponding to the first supplier (e.g., the first restaurant).

[0368] exist Figure 9B In response to detecting that the computer system 700 is in a location corresponding to the first supplier (e.g., the first restaurant named "Food King"), the computer system 700 displays a form user interface 906. In some embodiments, the form user interface 906 is similar to that described in the reference above. Figure 7B The form user interface described for the first time 706, referenced above. Figure 7Q The form user interface described for the first time 734, referenced above. Figure 7X The form user interface described for the first time 752, referenced above. Figure 7AE The form user interface described for the first time 762 and the above reference Figure 7AJ The first described form user interface 784 (e.g., having the same layout / structure as these form user interfaces; providing an experience consistent with these form user interfaces).

[0369] like Figure 9B As shown, in some embodiments, the form user interface 906 includes an information area 908, wherein the information area 908 includes the name information 908A of the first supplier (e.g., “Food King”) and the location information 908B of the first supplier (e.g., the address of the first supplier).

[0370] In some embodiments, the form user interface 906 includes a capability representation 910 (e.g., an optional user interface object; an activatable user interface object) that, when activated, initiates a process on computer system 700 to enable an activity associated with a first supplier (e.g., "Food King") (e.g., ordering one or more menu items, such as food or beverages, from the first supplier). In some embodiments, the capability representation 910 indicates the type of activity associated with the first supplier (e.g., "Food King") (e.g., ordering one or more menu items, such as food or beverages, from the first supplier) (e.g., including text information).

[0371] In some implementations, the form user interface 906 includes an image 912 indicating the first supplier (e.g., “Food King”) (e.g., an image of the first supplier’s store; the logo of the first supplier).

[0372] In some implementations, the form user interface 906 includes instructions 914 from a first developer (e.g., an entity; a company) that operates an application (e.g., a simplified / partial version of the application with a corresponding full / regular version available) that can enable activities associated with a first supplier (e.g., ordering menu items such as food or beverages) (e.g., developing, creating, and / or managing templates for the application), wherein the application (hereinafter referred to as the "simplified version application") is based on a portion (but not all) of the first developer's corresponding full version application. In some implementations, such as Figure 9B In some implementations, the application (e.g., "Food Review") is operated by a first developer that is different from the first supplier (e.g., "Food King") (e.g., a different entity from the first supplier). In some implementations, the developer may offer its application platform for use by multiple different suppliers, and the application may be customized for the respective supplier using the application platform. In some implementations, the application is operated by a second developer (e.g., the first supplier itself) that is the same as the first supplier (e.g., "Food King") (e.g., the same entity).

[0373] In some implementations, the form user interface 906 includes a power representation 916 (e.g., an optional user interface object; an activatable user interface object) for accessing an application store (e.g., an application store controlled and managed by the developer of the operating system of computer system 700, where the application store can be used to download first-party and third-party applications to computer system 700).

[0374] In some implementations, the form user interface 906 includes a power indicator 918 (e.g., an optional user interface object; an activatable user interface object) for eliminating (e.g., causing the computer system 700 to stop displaying) the form user interface 906 without performing an activity associated with the first supplier (e.g., “Food King”) (e.g., ordering menu items, such as food or beverages).

[0375] exist Figure 9B In the process of displaying the form user interface 906, the computer system 700 (e.g., via a touch-sensitive surface of one or more input devices) detects the activation 901 of the power indicator 910 (e.g., a user selection for the power indicator; a user tap input on the power indicator).

[0376] exist Figure 9C In response to detecting activation 901 of the indicator 910 (e.g., and in response to displaying as referenced above), Figures 7H to 7J The loading screen described indicates that, based on the determination that the corresponding full version of the simplified application of the first developer (e.g., "Food Review") is not installed (e.g., not installed) on computer system 700, computer system 700 displays a simplified user interface 920 of the first supplier (e.g., "Food King") via display generation component 702, wherein the simplified application is operated by the first developer (e.g., "Food Review"). In some embodiments, if the simplified application of the first developer (e.g., "Food Review") is unavailable (e.g., not installed) on computer system 700 when activation 901 of power indicator 910 is detected, computer system 700 automatically (e.g., without user input) downloads and installs the simplified application corresponding to the first developer (e.g., "Food Review") in response to the detection of activation 901 of power indicator 910.

[0377] like Figure 9C As shown, in some embodiments, the simplified user interface 920 includes information 922 of the first supplier (e.g., “Food King”) (e.g., including the address of the first supplier), which corresponds to the location information 908B of the first supplier (e.g., the address of the first supplier) included in the form user interface 906.

[0378] In some implementations, the simplified user interface 920 includes a supplier-customized menu area 924 that includes one or more menu items (e.g., food and / or beverages) provided by a first supplier (e.g., “Food King”).

[0379] In some implementations, the simplified user interface 920 includes a power indicator 926 (e.g., an optional user interface object; an activatable user interface object) for ordering / checkout of selected menu items.

[0380] In some embodiments, the simplified user interface 920 includes a user interface object 928 (e.g., a banner advertisement; a disc) that is displayed simultaneously with the simplified user interface 920 (e.g., overlaid on a portion of the simplified user interface 920). In some embodiments, the user interface object 928 is displayed together with the simplified user interface 928 and for a predetermined time period (e.g., 10 seconds; 30 seconds; 1 minute; after which the computer system 700 stops displaying the user interface object 920). In some embodiments, the user interface object 928 includes an instruction 928A (e.g., a text message) corresponding to a first developer of the application (e.g., "food review"). In some embodiments, the user interface object 928 includes a shared power representation 928B for initiating a process for sharing a simplified version of the application corresponding to the simplified user interface 920 with different users (e.g., transmitting electronic communications to different users' computer systems including portions of the application (e.g., the simplified application) and / or instructions for downloading portions of the application (e.g., the simplified application)).

[0381] Figure 9D A user interface 904 is shown in which the computer system 700 displays its wake-up screen (e.g., lock screen) via a display generation component 702. Figure 9D In response to detecting that the computer system 700 is in a location corresponding to the second supplier (e.g., a second restaurant named "Burger Queen"), the computer system 700 displays a form user interface 930 that is also operated by the first developer (e.g., "Food Review") (e.g., and therefore shares the same layout / structure as the form user interface 906).

[0382] like Figure 9D As shown, in some embodiments, similar to the form user interface 906 corresponding to the first supplier, the form user interface 930 includes an information area 932, wherein the information area 932 includes the name information 932A of the second supplier (e.g., "Hamburger Queen") and the location information 932B of the second supplier (e.g., the address of the second supplier).

[0383] In some embodiments, similar to the form user interface 906 corresponding to the first supplier, the form user interface 930 includes a capability representation 934 (e.g., an optional user interface object; an activatable user interface object) that, when activated, initiates a process on computer system 700 to enable an activity related to the second supplier (e.g., "Burger Queen") (e.g., ordering one or more menu items, such as food or beverages, from the second supplier). In some embodiments, the capability representation 934 indicates the type of activity related to the second supplier (e.g., "Burger Queen") (e.g., ordering one or more menu items, such as food or beverages, from the second supplier) (e.g., including text information).

[0384] In some implementations, similar to the form user interface 906 corresponding to the first supplier, the form user interface 930 includes an image 936 indicating the second supplier (e.g., "Burger Queen"); an image of the second supplier's store; the logo of the second supplier.

[0385] In some implementations, similar to the form user interface 906 corresponding to the first supplier, the form user interface 930 includes instructions 938 from a first developer (e.g., “Food Review”) that operates an application that enables activities related to the second supplier (e.g., “Burger Queen”) (e.g., ordering one or more menu items, such as food or beverages) (e.g., developing, creating and / or managing templates for the application).

[0386] In some implementations, similar to the form user interface 906 corresponding to the first vendor, the form user interface 930 includes a power representation 940 (e.g., an optional user interface object; an activatable user interface object) for accessing an application store (e.g., an application store controlled and managed by the developer of the operating system of computer system 700, where the application store can be used to download first-party and third-party applications to computer system 700).

[0387] In some implementations, similar to the form user interface 906 corresponding to the first supplier, the form user interface 930 includes a power indicator 942 (e.g., an optional user interface object; an activatable user interface object) for eliminating (e.g., causing the computer system 700 to stop displaying) the form user interface 930 without performing an activity associated with the second supplier (e.g., "Burger Queen") (e.g., ordering one or more menu items, such as food or drinks).

[0388] exist Figure 9DIn the process of displaying the form user interface 930, the computer system 700 (e.g., via the touch-sensitive surface of the one or more input devices) detects the activation 903 of the power indicator 934 (e.g., user selection for the power indicator; user tap input on the power indicator).

[0389] exist Figure 9E In response to detecting activation 903 of the enable indicator 934 (e.g., and in response to displaying as referenced above) Figures 7H to 7J The computer system 700 displays a simplified user interface 944 of a second supplier (e.g., "Burger Queen") via a display generation component 702 on a loading screen described above. The simplified user interface 944 is used by a first developer (e.g., "Food Review") for operational reference. Figure 9C The simplified version of the application, described in the simplified user interface 920, operates the same way.

[0390] In some implementations, since both the simplified user interface 920 of the first supplier (e.g., "Food King") and the simplified user interface 944 of the second supplier ("Burger Queen") are operated by the same simplified version of the application corresponding to the first developer (e.g., "Food Review"), the simplified user interface 944 shares a similar layout / structure as the simplified user interface 920. However, the simplified user interface 920 includes information customized for the first supplier (e.g., "Food King"), and the simplified user interface 944 includes information customized for the second supplier (e.g., "Burger Queen").

[0391] like Figure 9E As shown, in some embodiments, the simplified user interface 944 includes information 946 of the second supplier (e.g., "Burger Queen") (e.g., the address of the second supplier), which corresponds to the location information 932B of the second supplier (e.g., the address of the second supplier) included in the form user interface 930.

[0392] In some implementations, the simplified user interface 944 includes a supplier-customized menu area 948 that includes one or more menu items (e.g., food and / or beverages) provided by a second supplier (e.g., "Burger Queen").

[0393] In some implementations, the simplified user interface 944 includes a power indicator 950 (e.g., an optional user interface object; an activatable user interface object) for ordering / checkout of selected menu items.

[0394] In some embodiments, the simplified user interface 944 includes a user interface object 952 (e.g., a banner advertisement; a disc) that is displayed simultaneously with the simplified user interface 944 (e.g., overlaid on a portion of the simplified user interface 944). In some embodiments, the user interface object 952 is displayed together with the simplified user interface 944 and for a predetermined time period (e.g., 10 seconds; 30 seconds; 1 minute; the computer system 700 stops displaying the user interface object 952 after a predetermined non-zero time period). In some embodiments, the user interface object 952 includes an instruction 952A (e.g., a text message) corresponding to a first developer of the application (e.g., "food review"). In some embodiments, the user interface object 952 includes a shared power representation 952B for initiating a process for sharing a simplified version of the application corresponding to the simplified user interface 944 with different users (e.g., transmitting electronic communications to different users' computer systems including portions of the application (e.g., the simplified application) and / or instructions for downloading portions of the application (e.g., the simplified application)).

[0395] Figures 9F to 9M An exemplary user interface is shown for customizing the displayed content based on object identification information (e.g., table number; object number), wherein the object identification information is obtained by computer system 700 via NFC connection (e.g., or alternatively via QR code), and wherein different object identification information (e.g., different table numbers; different object numbers) belong to the same supplier (e.g., the same restaurant; the same store; the same company).

[0396] Figure 9F A computer system 700 is shown communicating with a wireless communication terminal 954 (e.g., an NFC terminal) (e.g., simultaneously displaying a wake-up screen user interface 904 via a display generation component 904), wherein the terminal 954 corresponds to the first table (e.g., table number 8) at a third supplier (e.g., "Mocha Coffee").

[0397] exist Figure 9J In this process, computer system 700 receives (e.g., detects) (e.g., via NFC) identification information from terminal 954 corresponding to the first table (e.g., table number 8) of a third supplier (e.g., "Mocha Coffee").

[0398] exist Figure 9GIn response to receiving identification information from terminal 954, computer system 700 displays a form user interface 956 operated by a second developer (e.g., "Mocha Coffee") via display generation component 702 (e.g., overlaid on user interface 904), wherein the second developer is the same as the third supplier (e.g., "Mocha Coffee") (e.g., the same entity; the same company). In some embodiments, form user interface 956 is similar to Figure 9B Forms user interface 920 and Figure 9D The form user interface 944 (e.g., sharing the same layout / structure).

[0399] like Figure 9G As shown, in some embodiments, the form user interface 956 includes an information area 958, wherein the information area 958 includes the name information 958A of the third supplier (e.g., "Mocha Coffee") and the location information 958B of the third supplier (e.g., the address of the third supplier). In some embodiments, the form user interface 956 includes in the information area 958 identification information 958C (e.g., first table number (e.g., table number; object number) received from the terminal 954) corresponding to identification information (e.g., table number; object number).

[0400] In some embodiments, the form user interface 956 includes a capability representation 960 (e.g., an optional user interface object; an activatable user interface object) that, when activated, initiates a process on computer system 700 to enable an activity related to a third supplier (e.g., “Mocha Coffee”) (e.g., ordering one or more menu items, such as coffee or other beverages, from the third supplier). In some embodiments, the capability representation 960 indicates the type of activity related to the third supplier (e.g., “Mocha Coffee”) (e.g., ordering one or more menu items, such as coffee or other beverages, from the third supplier) (e.g., including text information).

[0401] In some implementations, the form user interface 956 includes an image 962 indicating a third supplier (e.g., an image of the third supplier's store; the logo of the third supplier).

[0402] In some implementations, the form user interface 956 includes instructions 964 from a second developer (e.g., "Mocha Coffee") who operates an application that enables activities related to a third supplier (e.g., "Mocha Coffee") (e.g., ordering one or more menu items, such as coffee or other beverages) (e.g., developing, creating, and / or managing templates for the application). Figure 9G In this context, the second developer and the third supplier (e.g., "Mocha Coffee") are the same entity (e.g., they are the same company).

[0403] In some implementations, the form user interface 956 includes a power representation 966 (e.g., an optional user interface object; an activatable user interface object) for accessing an application store (e.g., an application store controlled and managed by the developer of the operating system of computer system 700, where the application store can be used to download first-party and third-party applications to computer system 700).

[0404] In some implementations, the form user interface 956 includes a power indication 968 (e.g., an optional user interface object; an activatable user interface object) for eliminating (e.g., causing the computer system 700 to stop displaying) the form user interface 956 without performing an activity associated with a third supplier (e.g., “Mocha Coffee”) (e.g., ordering one or more menu items, such as coffee or other beverages).

[0405] exist Figure 9H In the process of displaying the form user interface 956, the computer system 700 (e.g., via the touch-sensitive surface of the one or more input devices) detects the activation 905 of the power indicator 960 (e.g., user selection for the power indicator; user tap input on the power indicator).

[0406] exist Figure 9I In response to detecting activation 905 of the indicator 960 (e.g., and in response to displaying as referenced above) Figures 7H to 7J (As described in the loading screen), the computer system 700 displays a simplified user interface 970 corresponding to a third vendor (e.g., "Mocha Coffee") via a display generation component 702. This simplified user interface is operated by a simplified version of an application from a second developer (e.g., "Mocha Coffee"), which is the same entity as the third vendor (e.g., the same company). In some embodiments, the respective developer may (e.g., is free to) create and / or customize the respective simplified version of the application to provide a unique experience via the respective simplified user interface.

[0407] like Figure 9I As shown, in some embodiments, the simplified user interface 970 includes an information area 972 that includes location information 972A (e.g., the address of the third supplier) corresponding to location information 958B included in the form user interface 956 (e.g., "Mocha Coffee") and identification information 972B (e.g., the first table number (e.g., table number 8)) corresponding to identification information 958C included in the form user interface 956.

[0408] In some implementations, the simplified user interface 970 includes a supplier-customized menu area 974 that includes one or more menu items (e.g., coffee or other beverages) provided by a third supplier (e.g., "Mocha Coffee").

[0409] In some implementations, the simplified user interface 970 includes a power indicator 976 (e.g., an optional user interface object; an activatable user interface object) for ordering / checkout of selected menu items.

[0410] In some embodiments, the simplified user interface 970 includes a user interface object 978 (e.g., a banner advertisement; a disc) that is displayed simultaneously with the simplified user interface 970 (e.g., overlaid on a portion of the simplified user interface 970). In some embodiments, the user interface object 978 is displayed together with the simplified user interface 970 and for a predetermined time period (e.g., 10 seconds; 30 seconds; 1 minute; the computer system 700 stops displaying the user interface object 978 after a predetermined non-zero time period). In some embodiments, the user interface object 978 includes an instruction 978A (e.g., a text message) from a second developer (e.g., "Mocha Coffee") corresponding to the application. In some embodiments, the user interface object 978 includes a shared power representation 978B for initiating a process for sharing a simplified version of the application corresponding to the simplified user interface 970 with different users (e.g., transmitting electronic communications to different users' computer systems including portions of the application (e.g., the simplified application) and / or instructions for downloading portions of the application (e.g., the simplified application)).

[0411] Figure 9J A computer system 700 is shown communicating with a wireless communication terminal 980 (e.g., an NFC terminal), (e.g., simultaneously displaying a wake-up screen user interface 904 via a display generation component 702), wherein terminal 980 corresponds to a second table (e.g., table 5) at a third supplier (e.g., "Mocha Coffee") and is different from terminal 954 at the third supplier. Figure 9J In this process, computer system 700 receives (e.g., detects) (e.g., via NFC) identification information from terminal 980 corresponding to a second table (e.g., table 5) of a third supplier (e.g., "Mocha Coffee").

[0412] exist Figure 9K In response to receiving identification information from terminal 980, computer system 700 displays form user interface 956 via display generation component 702 (e.g., overlaid on user interface 904), as referenced above. Figure 9GIn its initial description, the form user interface was operated by a second developer (e.g., "Mocha Coffee").

[0413] exist Figure 9K In response to receiving identification information corresponding to a second table (e.g., table 5) at a third supplier (e.g., "Mocha Coffee"), instead of identification information corresponding to the first table (e.g., table 8), the form user interface 956 is displayed. Figure 9K As shown, the form user interface 956 includes, in the information area 958, elements related to... Figure 9G The same third supplier name information 958A (e.g., "Mocha Coffee") and related Figure 9G The same third supplier location information 958B (e.g., the address of the third supplier) is included in the information area 958 (e.g., because both terminals 954 and 980 belong to the same third supplier (e.g., "Mocha Coffee"), but identification information 958C is included in the information area 958, where identification information 958C displays the identification information corresponding to terminal 980 (e.g., the second table number (e.g., table 5)) instead of the identification information corresponding to terminal 954 (e.g., the first table number (e.g., table 8)).

[0414] exist Figure 9L In the process of displaying the form user interface 956, the computer system 700 (e.g., via the touch-sensitive surface of the one or more input devices) detects the activation 907 of the power indicator 960 (e.g., user selection for the power indicator; user tap input on the power indicator).

[0415] exist Figure 9M In response to detection Figure 9L The indicator in the middle represents the activation of 907 of 96...

Claims

1. A computer system, comprising: Display generated components; one or more input devices; one or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: accumulating, over a period of time, a plurality of automatically downloaded applications that are automatically downloaded to assist in performing a context-related task, wherein the plurality of applications includes a first application having first usage information and a second application having second usage information; receiving, via the one or more input devices, a request to display representations of automatically downloaded applications available on the computer system after the plurality of applications have been automatically downloaded; as well as In response to receiving the request, displaying, via the display generating component, a user interface for accessing the automatically downloaded applications, wherein the user interface provides access to a subset of the plurality of automatically downloaded applications, the subset excluding one or more applications that do not meet corresponding usage criteria, wherein: the subset of the plurality of automatically downloaded applications including the first application based on a determination that the first usage information satisfies the corresponding usage criteria, wherein the user interface includes a first icon representation corresponding to the first application, wherein the first icon representation includes a graphical indicator that the first application has been automatically downloaded and that the first application is to be removed from the computer system when the first usage information does not satisfy the corresponding usage criteria; the subset of the plurality of automatically downloaded applications excluding the first application based on determining that the first usage information does not satisfy the corresponding usage criteria; the subset of the plurality of automatically downloaded applications includes the second application based on a determination that the second usage information satisfies the corresponding usage criteria, wherein the user interface includes a second icon representation corresponding to the second application, wherein the second icon representation includes a graphical indicator that the second application has been automatically downloaded and that the second application is to be removed from the computer system when the second usage information does not satisfy the corresponding usage criteria; and Based on determining that the second usage information does not satisfy the corresponding usage criteria, the subset of the plurality of automatically downloaded applications excludes the second application.

2. The computer system of claim 1, wherein upon downloading, the plurality of automatically downloaded applications are stored on the computer system.

3. A computer system according to claim 1, wherein receiving the request to display the representation of the automatically downloaded application available on the computer system includes detecting activation of a first selectable user interface object via the one or more input devices, the first selectable user interface object causing display of the user interface for accessing the automatically downloaded application when activated.

4. The computer system of claim 3, wherein the one or more programs further comprise instructions for: displaying the first selectable user interface object in a second user interface; while the first selectable user interface object is displayed, detecting, via the one or more input devices, activation of the first selectable user interface object; and In response to detecting the activation of the first selectable user interface object, displaying, via the display generation component, the user interface for accessing the automatically downloaded application.

5. The computer system of claim 1, wherein the one or more programs further comprise instructions for: displaying, via the display generating component, a second selectable user interface object; while the second selectable user interface object is displayed, detecting, via the one or more input devices, activation of the second selectable user interface object; and In response to detecting the activation of the second selectable user interface object, the plurality of automatically downloaded applications accumulated over the time period are removed such that the user interface no longer provides access to the subset of the plurality of automatically downloaded applications.

6. The computer system of claim 1, wherein the one or more programs further comprise instructions for: displaying, via the display generating component, a third selectable user interface object, wherein the third selectable user interface object corresponds to a respective application that has been automatically downloaded; detecting activation of the third selectable user interface object via the one or more input devices; and In response to detecting the activation of the third selectable user interface object, the corresponding application is removed such that the user interface no longer provides access to the corresponding application.

7. The computer system of claim 1, wherein the one or more programs further comprise instructions for: displaying, via the display generation component, a first user interface corresponding to the first application; When displaying the first user interface corresponding to the first application, receiving a request to remove the first application; as well as In response to receiving the request to remove the first application, the first application is removed such that the user interface no longer provides access to the first application.

8. The computer system of claim 1, wherein the graphical indicator further indicates that the first application does not include at least a portion of the first application's corresponding application.

9. The computer system of claim 1, wherein the one or more programs further comprise instructions for: The user interface for accessing the automatically downloaded applications is displayed via the display generating component, wherein the user interface includes representations of the automatically downloaded applications corresponding to the subset of the multiple automatically downloaded applications, and wherein the representations are arranged within the user interface based on access times of the subset of the multiple automatically downloaded applications.

10. The computer system of claim 9, wherein the one or more programs further comprise instructions for: displaying, via the display generating component, the user interface for accessing the automatically downloaded application, wherein the first icon representation corresponding to the first application is not located at a first position in the user interface; detecting a request to invoke the first application after displaying the user interface with the first icon representation not in the first position in the user interface; as well as After detecting the request to invoke the first application, the user interface for accessing the automatically downloaded application is displayed via the display generation component, wherein the first icon representation corresponding to the first application is located at the first position in the user interface.

11. A computer system according to claim 9, wherein the representation of the automatically downloaded applications corresponding to the subset of the multiple automatically downloaded applications includes a corresponding icon representation corresponding to the first application, and does not include another corresponding icon representation corresponding to the first application.

12. The computer system of claim 9, wherein the one or more programs further comprise instructions for: displaying, in the user interface for accessing the automatically downloaded applications, a respective icon representation corresponding to the first application at a respective position within the user interface that is not a top position within the user interface relative to other icon representations in the user interface, wherein the respective icon representation corresponds to a previous invocation of the first application with respect to a first provider associated with the first application; detecting a request to invoke the first application by a second provider associated with the first application that is different from the first provider after displaying the respective icon representation corresponding to the first application in the user interface at the respective position within the user interface that is not the top position; and After detecting the request to invoke the first application by the second supplier different from the first supplier, the user interface for accessing the automatically downloaded application is displayed via the display generating component, wherein the user interface includes the corresponding icon representation corresponding to the first application at the top position within the user interface.

13. The computer system of claim 1, wherein the one or more programs further comprise instructions for: After the first application has been automatically downloaded on the computer system, detecting that the computer system is operating in a first context; and In response to detecting that the computer system is operating in the first context: Based on determining that the first context relates to a first context-related task that the first application is configured to perform, a first indication that the first application is available on the computer system to perform the first context-related task is displayed via the display generation component.

14. The computer system of claim 1, wherein the one or more programs further comprise instructions for: detecting that the computer system is operating in a first context when the first application is not downloaded on the computer system; and In response to detecting that the computer system is operating in the first context: Based on determining that the first context relates to a first context-related task that the first application is configured to perform, displaying, via the display generating component, a second indication that a third application is usable on the computer system for performing a third context-related task.

15. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: accumulating, over a period of time, a plurality of automatically downloaded applications that are automatically downloaded to assist in performing a context-related task, wherein the plurality of applications includes a first application having first usage information and a second application having second usage information; receiving, via the one or more input devices, a request to display representations of automatically downloaded applications available on the computer system after the plurality of applications have been automatically downloaded; as well as In response to receiving the request, displaying, via the display generating component, a user interface for accessing the automatically downloaded applications, wherein the user interface provides access to a subset of the plurality of automatically downloaded applications, the subset excluding one or more applications that do not meet corresponding usage criteria, wherein: the subset of the plurality of automatically downloaded applications including the first application based on a determination that the first usage information satisfies the corresponding usage criteria, wherein the user interface includes a first icon representation corresponding to the first application, wherein the first icon representation includes a graphical indicator that the first application has been automatically downloaded and that the first application is to be removed from the computer system when the first usage information does not satisfy the corresponding usage criteria; the subset of the plurality of automatically downloaded applications excluding the first application based on determining that the first usage information does not satisfy the corresponding usage criteria; the subset of the plurality of automatically downloaded applications includes the second application based on a determination that the second usage information satisfies the corresponding usage criteria, wherein the user interface includes a second icon representation corresponding to the second application, wherein the second icon representation includes a graphical indicator that the second application has been automatically downloaded and that the second application is to be removed from the computer system when the second usage information does not satisfy the corresponding usage criteria; and Based on determining that the second usage information does not satisfy the corresponding usage criteria, the subset of the plurality of automatically downloaded applications excludes the second application.

16. The non-transitory computer-readable storage medium of claim 15, wherein upon downloading, the plurality of automatically downloaded applications are stored on the computer system.

17. A non-transitory computer-readable storage medium according to claim 15, wherein receiving the request to display the representation of the automatically downloaded application available on the computer system includes detecting activation of a first selectable user interface object via the one or more input devices, the first selectable user interface object causing display of the user interface for accessing the automatically downloaded application when activated.

18. The non-transitory computer readable storage medium of claim 17, wherein the one or more programs further comprise instructions for: displaying the first selectable user interface object in a second user interface; while displaying the first selectable user interface object, detecting, via the one or more input devices, activation of the first selectable user interface object; as well as In response to detecting the activation of the first selectable user interface object, displaying, via the display generation component, the user interface for accessing the automatically downloaded application.

19. The non-transitory computer readable storage medium of claim 15, wherein the one or more programs further comprise instructions for: displaying, via the display generating component, a second selectable user interface object; while the second selectable user interface object is displayed, detecting, via the one or more input devices, activation of the second selectable user interface object; and In response to detecting the activation of the second selectable user interface object, the plurality of automatically downloaded applications accumulated over the time period are removed such that the user interface no longer provides access to the subset of the plurality of automatically downloaded applications.

20. The non-transitory computer readable storage medium of claim 15, the one or more programs further comprising instructions for: displaying, via the display generating component, a third selectable user interface object, wherein the third selectable user interface object corresponds to a respective application that has been automatically downloaded; detecting activation of the third selectable user interface object via the one or more input devices; and In response to detecting the activation of the third selectable user interface object, the corresponding application is removed such that the user interface no longer provides access to the corresponding application.

21. The non-transitory computer readable storage medium of claim 15, wherein the one or more programs further comprise instructions for: displaying, via the display generation component, a first user interface corresponding to the first application; When displaying the first user interface corresponding to the first application, receiving a request to remove the first application; as well as In response to receiving the request to remove the first application, the first application is removed such that the user interface no longer provides access to the first application.

22. The non-transitory computer-readable storage medium of claim 15, wherein the graphical indicator further indicates that the first application does not include at least a portion of the first application's corresponding application.

23. The non-transitory computer readable storage medium of claim 15, the one or more programs further comprising instructions for: The user interface for accessing the automatically downloaded applications is displayed via the display generating component, wherein the user interface includes representations of the automatically downloaded applications corresponding to the subset of the multiple automatically downloaded applications, and wherein the representations are arranged within the user interface based on access times of the subset of the multiple automatically downloaded applications.

24. The non-transitory computer readable storage medium of claim 23, the one or more programs further comprising instructions for: displaying, via the display generating component, the user interface for accessing the automatically downloaded application, wherein a first representation corresponding to the first iconic application is not in a first position in the user interface; detecting a request to invoke the first application after displaying the user interface with the first icon representation not in the first position in the user interface; as well as After detecting the request to invoke the first application, the user interface for accessing the automatically downloaded application is displayed via the display generation component, wherein the first icon representation corresponding to the first application is located at the first position in the user interface.

25. A non-transitory computer-readable storage medium according to claim 23, wherein the representation of the automatically downloaded applications corresponding to the subset of the multiple automatically downloaded applications includes a corresponding icon representation corresponding to the first application, and does not include another corresponding icon representation corresponding to the first application.

26. The non-transitory computer readable storage medium of claim 23, the one or more programs further comprising instructions for: displaying, in the user interface for accessing the automatically downloaded applications, a respective icon representation corresponding to the first application at a respective position within the user interface that is not a top position within the user interface relative to other icon representations in the user interface, wherein the respective icon representation corresponds to a previous invocation of the first application with respect to a first provider associated with the first application; detecting a request to invoke the first application by a second provider associated with the first application that is different from the first provider after displaying the respective icon representation corresponding to the first application in the user interface at the respective position within the user interface that is not the top position; and After detecting the request to invoke the first application by the second supplier different from the first supplier, the user interface for accessing the automatically downloaded application is displayed via the display generating component, wherein the user interface includes the corresponding icon representation corresponding to the first application at the top position within the user interface.

27. The non-transitory computer readable storage medium of claim 15, the one or more programs further comprising instructions for: After the first application has been automatically downloaded on the computer system, detecting that the computer system is operating in a first context; and In response to detecting that the computer system is operating in the first context: Based on determining that the first context relates to a first context-related task that the first application is configured to perform, a first indication that the first application is available on the computer system to perform the first context-related task is displayed via the display generation component.

28. The non-transitory computer readable storage medium of claim 15, the one or more programs further comprising instructions for: detecting that the computer system is operating in a first context when the first application is not downloaded on the computer system; and In response to detecting that the computer system is operating in the first context: Based on determining that the first context relates to a first context-related task that the first application is configured to perform, displaying, via the display generating component, a second indication that a third application is usable on the computer system for performing a third context-related task.

29. A method for managing an application, comprising: At a computer system in communication with a display generating component and one or more input devices: accumulating, over a period of time, a plurality of automatically downloaded applications that are automatically downloaded to assist in performing a context-related task, wherein the plurality of applications includes a first application having first usage information and a second application having second usage information; receiving, via the one or more input devices, a request to display representations of automatically downloaded applications available on the computer system after the plurality of applications have been automatically downloaded; as well as In response to receiving the request, displaying, via the display generating component, a user interface for accessing the automatically downloaded applications, wherein the user interface provides access to a subset of the plurality of automatically downloaded applications, the subset excluding one or more applications that do not meet corresponding usage criteria, wherein: the subset of the plurality of automatically downloaded applications including the first application based on a determination that the first usage information satisfies the corresponding usage criteria, wherein the user interface includes a first icon representation corresponding to the first application, wherein the first icon representation includes a graphical indicator that the first application has been automatically downloaded and that the first application is to be removed from the computer system when the first usage information does not satisfy the corresponding usage criteria; the subset of the plurality of automatically downloaded applications excluding the first application based on determining that the first usage information does not satisfy the corresponding usage criteria; the subset of the plurality of automatically downloaded applications includes the second application based on a determination that the second usage information satisfies the corresponding usage criteria, wherein the user interface includes a second icon representation corresponding to the second application, wherein the second icon representation includes a graphical indicator that the second application has been automatically downloaded and that the second application is to be removed from the computer system when the second usage information does not satisfy the corresponding usage criteria; and Based on determining that the second usage information does not satisfy the corresponding usage criteria, the subset of the plurality of automatically downloaded applications excludes the second application.

30. The method of claim 29, wherein upon downloading, the plurality of automatically downloaded applications are stored on the computer system.

31. A method according to claim 29, wherein receiving the request to display the representation of the automatically downloaded application available on the computer system includes detecting activation of a first selectable user interface object via the one or more input devices, the first selectable user interface object causing display of the user interface for accessing the automatically downloaded application when activated.

32. The method of claim 31 further comprising: displaying the first selectable user interface object in a second user interface; while displaying the first selectable user interface object, detecting, via the one or more input devices, activation of the first selectable user interface object; as well as In response to detecting the activation of the first selectable user interface object, displaying, via the display generation component, the user interface for accessing the automatically downloaded application.

33. The method of claim 29, further comprising: displaying, via the display generating component, a second selectable user interface object; while displaying the second selectable user interface object, detecting, via the one or more input devices, activation of the second selectable user interface object; as well as In response to detecting the activation of the second selectable user interface object, the plurality of automatically downloaded applications accumulated over the time period are removed such that the user interface no longer provides access to the subset of the plurality of automatically downloaded applications.

34. The method of claim 29, further comprising: displaying, via the display generating component, a third selectable user interface object, wherein the third selectable user interface object corresponds to a respective application that has been automatically downloaded; detecting, via the one or more input devices, activation of the third selectable user interface object; as well as In response to detecting the activation of the third selectable user interface object, the corresponding application is removed such that the user interface no longer provides access to the corresponding application.

35. The method of claim 29, further comprising: displaying, via the display generation component, a first user interface corresponding to the first application; When displaying the first user interface corresponding to the first application, receiving a request to remove the first application; as well as In response to receiving the request to remove the first application, the first application is removed such that the user interface no longer provides access to the first application.

36. The method of claim 29, wherein the graphical indicator further indicates that the first application does not include at least a portion of the first application's corresponding application.

37. The method of claim 29, further comprising: The user interface for accessing the automatically downloaded applications is displayed via the display generating component, wherein the user interface includes representations of the automatically downloaded applications corresponding to the subset of the multiple automatically downloaded applications, and wherein the representations are arranged within the user interface based on access times of the subset of the multiple automatically downloaded applications.

38. The method of claim 37, further comprising: displaying, via the display generating component, the user interface for accessing the automatically downloaded application, wherein the first icon representation corresponding to the first application is not located at a first position in the user interface; detecting a request to invoke the first application after displaying the user interface with the first icon representation not in the first position in the user interface; as well as After detecting the request to invoke the first application, the user interface for accessing the automatically downloaded application is displayed via the display generation component, wherein the first icon representation corresponding to the first application is located at the first position in the user interface.

39. A method according to claim 37, wherein the representation of the automatically downloaded applications corresponding to the subset of the multiple automatically downloaded applications includes a corresponding icon representation corresponding to the first application, and does not include another corresponding icon representation corresponding to the first application.

40. The method of claim 37, further comprising: displaying, in the user interface for accessing the automatically downloaded applications, a respective icon representation corresponding to the first application at a respective position within the user interface that is not a top position within the user interface relative to other icon representations in the user interface, wherein the respective icon representation corresponds to a previous invocation of the first application with respect to a first provider associated with the first application; detecting a request to invoke the first application by a second provider associated with the first application that is different from the first provider after displaying the respective icon representation corresponding to the first application in the user interface at the respective position within the user interface that is not the top position; as well as After detecting the request to invoke the first application by the second supplier different from the first supplier, the user interface for accessing the automatically downloaded application is displayed via the display generating component, wherein the user interface includes the corresponding icon representation corresponding to the first application at the top position within the user interface.

41. The method of claim 29, further comprising: After the first application has been automatically downloaded on the computer system, detecting that the computer system is operating in a first context; as well as In response to detecting that the computer system is operating in the first context: Based on determining that the first context relates to a first context-related task that the first application is configured to perform, a first indication that the first application is available on the computer system to perform the first context-related task is displayed via the display generation component.

42. The method of claim 29, further comprising: detecting that the computer system is operating in a first context when the first application is not downloaded on the computer system; as well as In response to detecting that the computer system is operating in the first context: Based on determining that the first context relates to a first context-related task that the first application is configured to perform, displaying, via the display generating component, a second indication that a third application is usable on the computer system for performing a third context-related task.

Images