User interface for activating activities

Abstract

To provide methods and user interfaces for enabling an activity using a computer system.SOLUTION: A method includes: accumulating and storing a plurality of automatically downloaded applications that were downloaded automatically to assist in performing contextually relevant tasks over a period of time; after the plurality of applications have been downloaded automatically, receiving, via one or more input devices, a request to display representations of automatically downloaded applications that are available on the computer system; and in response to receiving the request, display, via a display generation component, a user interface for accessing the automatically downloaded applications, which provides access to a subset of the plurality of automatically downloaded applications that excludes one or more applications that do not meet respective usage criteria.SELECTED DRAWING: Figure 12A

Description

[Technical Field]

[0001] TECHNICAL FIELD This disclosure relates generally to computer user interfaces, and more particularly to techniques for enabling activities using computer systems. [Background technology]

[0002] A computer system may include applications that are installed on the computer system. The installed applications may be used by the computer system to perform operations on the computer system. Applications that are not available on the computer system may be downloaded and installed on the computer system, such as from an application store accessible by the computer system. Summary of the Invention

[0003] Some techniques for enabling activities using computer systems (e.g., electronic devices) are generally cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that may involve multiple key presses or strokes. Existing techniques take longer than necessary, wasting the user's time and the device's energy. The latter problem is particularly acute in battery-operated computer systems.

[0004] Thus, the present technology provides a computer system with faster, more efficient methods and interfaces for enabling activities. Such methods and interfaces optionally complement or replace other methods for enabling activities. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and extend the time between battery charges. Such methods and interfaces also provide quick, efficient, and easy access to perform activities using the computer system. Such methods and interfaces also notify the user that the computer system can be used to perform activities of which the user is not aware.

[0005] According to some embodiments, a method executed on a computer system in communication with a display generation component and one or more input devices is described. The method includes detecting an occurrence of a trigger condition for initiating an activity associated with a first application, displaying a first user interface via the display generation component in response to detecting the occurrence of the trigger condition, the displaying the first user interface simultaneously displaying a description of the activity and a first selectable user interface object for taking an action associated with the activity, detecting activation of the first selectable user interface object via the one or more input devices while displaying the first user interface, and in response to detecting the activation of the first selectable user interface object, 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 in accordance with determining that the first application is unavailable on the computer system.

[0006] In some embodiments, 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 is described. The one or more programs include instructions for detecting an occurrence of a trigger condition for initiating an activity associated with a first application, displaying a first user interface via the display generation component in response to detecting the occurrence of the trigger condition, wherein displaying the first user interface simultaneously displays a description of the activity and a first selectable user interface object for taking an action associated with the activity, detecting activation of the first selectable user interface object via the one or more input devices while displaying the first user interface, and in response to detecting the activation of the first selectable user interface object, 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 in accordance with determining that the first application is unavailable on the computer system.

[0007] In some embodiments, a transient 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 is described. The one or more programs include instructions for detecting an occurrence of a trigger condition for initiating an activity associated with a first application, displaying a first user interface via the display generation component in response to detecting the occurrence of the trigger condition, wherein displaying the first user interface simultaneously displays a description of the activity and a first selectable user interface object for taking an action associated with the activity, detecting activation of the first selectable user interface object via the one or more input devices while displaying the first user interface, and in response to detecting the activation of the first selectable user interface object, 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 in accordance with determining that the first application is unavailable on the computer system.

[0008] In some embodiments, a computer system is described that includes a display generation component, one or more input devices, one or more processors, and a memory that stores one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for detecting an occurrence of a trigger condition for initiating an activity associated with a first application, displaying a first user interface via the display generation component in response to detecting the occurrence of the trigger condition, where displaying the first user interface includes simultaneously displaying a description of the activity and a first selectable user interface object for taking an action associated with the activity, detecting activation of the first selectable user interface object via the one or more input devices while displaying the first user interface, and in response to detecting the activation of the first selectable user interface object, 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 in accordance with determining that the first application is unavailable on the computer system.

[0009] According to some embodiments, a computer system is described that includes a display generation component and one or more input devices, and the method includes: means for detecting an occurrence of a trigger condition for initiating an activity associated with a first application; means for displaying, via the display generation component, a first user interface in response to detecting the occurrence of the trigger condition, the means for displaying the first user interface simultaneously displaying a description of the activity and a first selectable user interface object for taking an action associated with the activity; means for detecting, via the one or more input devices, activation of the first selectable user interface object while displaying the first user interface; and means for 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 in response to detecting the activation of the first selectable user interface object in accordance with a determination that the first application is unavailable on the computer system.

[0010] According to some embodiments, a method is described that is executed on a computer system in communication with a display generation component and one or more input devices. The method includes detecting, via the one or more input devices, a request to invoke a first application; and, in response to detecting the request to invoke the first application, displaying, via the display generation component, a first user interface corresponding to the first application, wherein, in response to determining that the request to invoke the first application occurred in a first context, displaying the first user interface includes displaying, in the first user interface, first content within a respective region of the first user interface; and, in response to determining that the request to invoke the first application occurred in a second context different from the first context, displaying, in the first user interface, second content within a respective region of the first user interface, the second content being different from the first content.

[0011] In some embodiments, 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 is described, the one or more programs including instructions for 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, in accordance with determining that the request to invoke the first application occurred in a first context, displaying the first user interface includes displaying, in the first user interface, first content within a respective region of the first user interface, and, in accordance with determining that the request to invoke the first application occurred in a second context different from the first context, displaying, in the first user interface, second content within a respective region of the first user interface, the second content being different from the first content.

[0012] In some embodiments, a transient 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 is described, the one or more programs including instructions for detecting a request to invoke a first application via the one or more input devices, and displaying a first user interface corresponding to the first application via the display generation component in response to detecting the request to invoke the first application, wherein displaying the first user interface in accordance with determining that the request to invoke the first application occurred in a first context includes displaying, in the first user interface, first content within respective regions of the first user interface, and wherein displaying the first user interface in accordance with determining that the request to invoke the first application occurred in a second context different from the first context includes displaying, in the first user interface, second content within respective regions of the first user interface, the second content being different from the first content.

[0013] In some embodiments, a computer system is described that includes a display generation component, one or more input devices, one or more processors, and a memory that stores one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for 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, in accordance with determining that the request to invoke the first application occurred in a first context, displaying the first user interface includes displaying, in the first user interface, first content within respective regions of the first user interface, and, in accordance with determining that the request to invoke the first application occurred in a second context different from the first context, displaying, in the first user interface, second content within respective regions of the first user interface, the second content being different from the first content.

[0014] According to some embodiments, a computer system is described that includes a display generation component, one or more input devices, means for detecting a request to invoke a first application via the one or more input devices, and means for displaying a first user interface corresponding to the first application via the display generation component in response to detecting the request to invoke the first application, wherein displaying the first user interface in accordance with a determination that the request to invoke the first application occurred in a first context includes displaying, in the first user interface, first content within a respective region of the first user interface, and wherein displaying, in accordance with a determination that the request to invoke the first application occurred in a second context different from the first context, second content within a respective region of the first user interface, the second content being different from the first content.

[0015] According to some embodiments, a method is described that is executed on a computer system in communication 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 that are automatically downloaded to assist in the performance of a contextually relevant task, the plurality of applications including a first application with first usage information and a second application with second usage information; receiving, via the one or more input devices, a request to display a representation of the automatically downloaded applications available on the computer system after the plurality of applications have been automatically downloaded; and, in response to receiving the request, displaying, via the display generation component, a user interface for accessing the automatically downloaded applications, the user interface displaying a user interface for accessing the automatically downloaded applications that meet respective usage criteria. and providing access to a subset of a plurality of automatically downloaded applications, excluding one or more applications that do not meet the respective usage criteria, wherein in accordance with a determination that the first usage information meets a respective usage criterion, the subset of a plurality of automatically downloaded applications includes a first application, and in accordance with a determination that the first usage information does not meet the respective usage criterion, the subset of a plurality of automatically downloaded applications includes a second application, and in accordance with a determination that the second usage information does not meet the respective usage criterion, the subset of a plurality of automatically downloaded applications excludes the second application.

[0016] In some embodiments, 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 generating component and one or more input devices is described. The one or more programs include instructions for accumulating, over a period of time, a plurality of automatically downloaded applications that are automatically downloaded to assist in the performance of contextually relevant tasks, the plurality of applications including a first application with first usage information and a second application with second usage information; receiving, via one or more input devices, a request to display a representation of the automatically downloaded applications available on the computer system after the plurality of applications have been automatically downloaded; and displaying, via a display generation component in response to receiving the request, a user interface for accessing the automatically downloaded applications, the user interface providing access to a subset of the plurality of automatically downloaded applications that excludes one or more applications that do not meet respective usage criteria; and, in accordance with a determination that the first usage information satisfies the respective usage criteria, the subset of the plurality of automatically downloaded applications includes the first application, and in accordance with a determination that the first usage information does not meet the respective usage criteria, the subset of the plurality of automatically downloaded applications excludes the first application, and in accordance with a determination that the second usage information meets the respective usage criteria, the subset of the plurality of automatically downloaded applications includes the second application, and in accordance with a determination that the second usage information does not meet the respective usage criteria.

[0017] In some embodiments, a transient 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 generating component and one or more input devices is described. The one or more programs include instructions for accumulating, over a period of time, a plurality of automatically downloaded applications that are automatically downloaded to assist in the performance of contextually relevant tasks, the plurality of applications including a first application with first usage information and a second application with second usage information; receiving, via one or more input devices, a request to display a representation of the automatically downloaded applications available on the computer system after the plurality of applications have been automatically downloaded; and displaying, via a display generation component in response to receiving the request, a user interface for accessing the automatically downloaded applications, the user interface providing access to a subset of the plurality of automatically downloaded applications that excludes one or more applications that do not meet respective usage criteria; and, in accordance with a determination that the first usage information satisfies the respective usage criteria, the subset of the plurality of automatically downloaded applications includes the first application, and in accordance with a determination that the first usage information does not meet the respective usage criteria, the subset of the plurality of automatically downloaded applications excludes the first application, and in accordance with a determination that the second usage information meets the respective usage criteria, the subset of the plurality of automatically downloaded applications includes the second application, and in accordance with a determination that the second usage information does not meet the respective usage criteria.

[0018] In some embodiments, a computer system is described that includes a display generation component, one or more input devices, one or more processors, and a memory that stores one or more programs configured to be executed by the one or more processors. The one or more programs accumulate, over a period of time, a plurality of automatically downloaded applications that are automatically downloaded to assist in the performance of a contextually relevant task, the plurality of applications including a first application with first usage information and a second application with second usage information. After the plurality of applications have been automatically downloaded, receive, 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, display, via the display generation component, a user interface for accessing the automatically downloaded applications, the user interface displaying a user interface for accessing the automatically downloaded applications that does not meet a respective usage criterion. The method includes providing access to a subset of a plurality of automatically downloaded applications that excludes the above applications, wherein the subset of a plurality of automatically downloaded applications includes a first application in accordance with a determination that the first usage information meets a respective usage criterion, the subset of a plurality of automatically downloaded applications excludes the first application in accordance with a determination that the first usage information does not meet the respective usage criterion, the subset of a plurality of automatically downloaded applications includes a second application in accordance with a determination that the second usage information meets the respective usage criterion, and the subset of a plurality of automatically downloaded applications excludes the second application in accordance with a determination that the second usage information does not meet the respective usage criterion at the current time.

[0019] According to some embodiments, a computer system is described, the computer system including a display generation component, one or more input devices, means for accumulating, over a period of time, a plurality of automatically downloaded applications that are automatically downloaded to assist in the performance of a contextually relevant task, the plurality of applications including a first application with first usage information and a second application with second usage information, means for receiving, via the one or more input devices, a request to display a representation of the automatically downloaded applications available on the computer system after the plurality of applications have been automatically downloaded, and means for displaying, via the display generation component, a user interface for accessing the automatically downloaded applications in response to receiving the request, the user interface The system provides access to a subset of a plurality of automatically downloaded applications, filtering out one or more applications that do not meet a respective usage criterion, wherein the subset of a plurality of automatically downloaded applications includes a first application in accordance with a determination that the first usage information meets the respective usage criterion; wherein the subset of a plurality of automatically downloaded applications includes a second application in accordance with a determination that the second usage information meets the respective usage criterion; and wherein the subset of a plurality of automatically downloaded applications filters out the second application in accordance with a determination that the second usage information does not meet the respective usage criterion at the current time.

[0020] According to some embodiments, a method is described that is executed on a computer system in communication with one or more input devices, the method including detecting an occurrence of a trigger condition for initiating an activity associated with a first application, installing a second application on the computer system while the first application is not installed on the computer system based on the detected trigger condition, the second application being configured to perform the activity without downloading at least a portion of the first application, setting one or more system privileges for the second application, installing the first application on the computer system after setting the one or more system privileges for the second application, setting the one or more system privileges for the first application based on the one or more system privileges for the second application in accordance with a determination that the second application was installed on the computer system when the installation of the first application occurred, and setting the one or more system privileges for the first application based on default system privileges in accordance with a determination that the second application was not installed on the computer system when the installation of the first application occurred.

[0021] In some embodiments, 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 one or more input devices is described, wherein the one or more programs include instructions for detecting an occurrence of a trigger condition for initiating an activity associated with a first application, installing a second application on the computer system while the first application is not installed on the computer system based on the detected trigger condition, the second application configured to perform the activity without downloading at least a portion of the first application, setting one or more system privileges for the second application, installing the first application on the computer system after setting the one or more system privileges for the second application, setting the one or more system privileges for the first application based on the one or more system privileges for the second application in accordance with a determination that the second application was installed on the computer system when the installation of the first application occurred after the installation of the first application on the computer system, and setting the one or more system privileges for the first application based on default system privileges in accordance with a determination that the second application was not installed on the computer system when the installation of the first application occurred.

[0022] In some embodiments, a transient 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 one or more input devices is described, wherein the one or more programs include instructions for detecting an occurrence of a trigger condition for initiating an activity associated with a first application, installing a second application on the computer system while the first application is not installed on the computer system based on the detected trigger condition, the second application configured to perform the activity without downloading at least a portion of the first application, setting one or more system privileges for the second application, installing the first application on the computer system after setting the one or more system privileges for the second application, setting the one or more system privileges for the first application based on the one or more system privileges for the second application in accordance with a determination that the second application was installed on the computer system when the installation of the first application occurred after the installation of the first application on the computer system, and setting the one or more system privileges for the first application based on default system privileges in accordance with a determination that the second application was not installed on the computer system when the installation of the first application occurred.

[0023] In some embodiments, a computer system is described that includes one or more input devices, one or more processors, and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for detecting an occurrence of a trigger condition for initiating an activity associated with a first application, installing a second application on the computer system while the first application is not installed on the computer system based on the detected trigger condition, the second application configured to perform the activity without downloading at least a portion of the first application, setting one or more system privileges for the second application, installing the first application on the computer system after setting the one or more system privileges for the second application, setting the one or more system privileges for the first application based on the one or more system privileges for the second application in accordance with a determination that the second application was installed on the computer system when installation of the first application occurred after installation of the first application on the computer system, and setting the one or more system privileges for the first application based on default system privileges in accordance with a determination that the second application was not installed on the computer system when installation of the first application occurred.

[0024] According to some embodiments, a computer system is described that includes means for detecting an occurrence of a trigger condition for initiating an activity associated with a first application, means for installing a second application on the computer system based on the detected trigger condition while the first application is not installed on the computer system, the second application configured to perform the activity without downloading at least a portion of the first application, means for setting one or more system privileges for the second application, means for installing the first application on the computer system after setting the one or more system privileges for the second application, means for setting the one or more system privileges for the first application based on the one or more system privileges for the second application in accordance with a determination that the second application was installed on the computer system when installation of the first application occurred after installation of the first application on the computer system, and means for setting the one or more system privileges for the first application based on default system privileges in accordance with a determination that the second application was not installed on the computer system when installation of the first application occurred.

[0025] Executable instructions to perform these functions are optionally contained in a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. Executable instructions to perform these functions are optionally contained in a transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0026] Thus, devices are provided with faster, more efficient methods and interfaces for enabling activities, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for enabling activities. [Brief explanation of the drawings]

[0027] For a better understanding of the various described embodiments, reference should be made to the following Detailed Description of the Invention in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:

[0028] [Figure 1A] FIG. 1 is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.

[0029] [Figure 1B] FIG. 2 is a block diagram illustrating exemplary components for event processing in accordance with some embodiments.

[0030] [Figure 2] 1 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

[0031] [Figure 3] FIG. 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments.

[0032] [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

[0033] [Figure 4B] 1 illustrates an exemplary user interface of a multifunction device having a touch-sensitive surface separate from a display in accordance with some embodiments.

[0034] [Figure 5A] 1 illustrates a personal electronic device according to some embodiments.

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

[0036] [Figure 6] 1 illustrates exemplary devices connected via one or more communication channels in accordance with some embodiments.

[0037] [Figure 7A] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7B] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7C] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7D] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7E] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7F] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7G] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7H]1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7I] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7J] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7K] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7L] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7M] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7N] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7O] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7P] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7Q] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7R] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7S]1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7T] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7U] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7V] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7W] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7X] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7Y] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7Z] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AA] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AB] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AC] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AD]1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AE] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AF] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AG] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AH] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AI] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AJ] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AK] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AL] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AM] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AN] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AO]1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AP] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AQ] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AR] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AS] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AT] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AU] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AV] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AW] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AX] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AY] 1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments. [Figure 7AZ]1 illustrates an exemplary user interface for invoking an activity associated with an application, according to some embodiments.

[0038] [Figure 8A] FIG. 1 is a flow diagram illustrating a method for invoking an activity associated with a camera application using a computer system, according to some embodiments. [Figure 8B] FIG. 1 is a flow diagram illustrating a method for invoking an activity associated with a camera application using a computer system, according to some embodiments.

[0039] [Figure 9A] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9B] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9C] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9D] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9E] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9F] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9G]1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9H] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9I] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9J] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9K] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9L] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9M] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9N] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9O] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9P] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9Q]1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9R] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9S] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments. [Figure 9T] 1 illustrates an exemplary user interface for customizing displayed content based on the context in which the content is invoked, according to some embodiments.

[0040] [Figure 10A] FIG. 1 is a flow diagram illustrating a method for customizing displayed content based on the context in which the content is invoked using a computer system, according to some embodiments. [Figure 10B] FIG. 1 is a flow diagram illustrating a method for customizing displayed content based on the context in which the content is invoked using a computer system, according to some embodiments. [Figure 10C] FIG. 1 is a flow diagram illustrating a method for customizing displayed content based on the context in which the content is invoked using a computer system, according to some embodiments.

[0041] [Figure 11A] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11B] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11C]1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11D] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11E] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11F] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11G] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11H] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11I] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11J] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11K] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11L] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11M]1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11N] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11O] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11P] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11Q] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11R] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments. [Figure 11S] 1 illustrates an exemplary user interface for managing applications used to enable an activity, according to some embodiments.

[0042] [Figure 12A] FIG. 1 is a flow diagram illustrating a method for managing applications used to enable activities using a computer system, according to some embodiments. [Figure 12B] FIG. 1 is a flow diagram illustrating a method for managing applications used to enable activities using a computer system, according to some embodiments. [Figure 12C] FIG. 1 is a flow diagram illustrating a method for managing applications used to enable activities using a computer system, according to some embodiments. [Figure 12D]FIG. 1 is a flow diagram illustrating a method for managing applications used to enable activities using a computer system, according to some embodiments.

[0043] [Figure 13A] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13B] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13C] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13D] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13E] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13F] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13G] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13H]1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13I] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13J] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13K] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13L] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13M] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13N] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13O] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13P] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13Q] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13R] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13S] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13T] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13U] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments. [Figure 13V] 1 illustrates an exemplary user interface for managing settings for an application used to enable an activity using a computer system, according to some embodiments.

[0044] [Figure 14A] FIG. 1 is a flow diagram illustrating a method for managing settings of an application used to enable an activity using a computer system, according to some embodiments. [Figure 14B] FIG. 1 is a flow diagram illustrating a method for managing settings of an application used to enable an activity using a computer system, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0045] The following description describes example methods, parameters, etc. However, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but is instead provided as a description of example embodiments.

[0046] There is a need for an electronic device that provides an efficient method and interface for enabling activities. For example, there is a need for an electronic device that can suggest or enable activities corresponding to applications that are not installed or available on the electronic device. In another example, there is a need for an electronic device that can start an activity corresponding to an application that is not installed or available on the electronic device without installing the application on the electronic device. In another example, there is a need for an electronic device that can quickly and easily enable access to download and install an application for an activity, where the application is not installed or available on the electronic device. Such techniques can reduce the cognitive burden on users who use electronic devices to access activities, thereby increasing productivity. Furthermore, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0047] 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of an exemplary device for performing a technique for enabling an activity. FIG. 6 illustrates exemplary devices connected via one or more communication channels according to some embodiments. FIGS. 7A-7AZ illustrate exemplary user interfaces for invoking an activity associated with an application according to some embodiments. FIGS. 8A-8B are flow diagrams illustrating a method for invoking an activity associated with a camera application using a computer system according to some embodiments. The user interfaces of FIGS. 7A-7AZ are used to illustrate processes described below, including the processes of FIGS. 8A-8B. FIGS. 9A-9T illustrate exemplary user interfaces for customizing displayed content based on the context in which the content is invoked according to some embodiments. FIGS. 10A-10C are flow diagrams illustrating a method for customizing displayed content based on the context in which the content is invoked using a computer system according to some embodiments. The user interfaces of FIGS. 9A-9T are used to illustrate processes described below, including the processes of FIGS. 10A-10C. 11A-11S show exemplary user interfaces for managing applications used to enable activities, according to some embodiments. 12A-12D are flow diagrams illustrating a method for managing applications used to enable activities using a computer system, according to some embodiments. The user interfaces of FIGS. 11A-11S are used to illustrate processes described below, including the processes of FIGS. 12A-12D. 13A-13V show exemplary user interfaces for managing settings for applications used to enable activities using a computer system. 14A-14B are flow diagrams illustrating a method for managing settings for applications used to enable activities using a computer system, according to some embodiments.The user interfaces of FIGS. 13A-13V are used to illustrate the processes described below, including the processes of FIGS. 14A-14B.

[0048] In the following description, terms such as "first" and "second" are used to describe various elements, but these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first touch can be referred to as a second touch, and similarly, a second touch can be referred to as a first touch, without departing from the scope of the various embodiments described. Although a first touch and a second touch are both touches, they are not the same touch.

[0049] The terminology used in the description of the various embodiments set forth herein is for the purpose of describing particular embodiments only and is not intended to be limiting. In the description of the various embodiments set forth and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. Also, as used herein, the term "and / or" should be understood to refer to and include any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," as used herein, specify the presence of 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.

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

[0051] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Optionally, other portable electronic devices, such as a laptop or tablet computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad). In some embodiments, the electronic device is a computer system that communicates (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide a visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, "displaying" content includes causing the content (e.g., video data rendered or decoded by display controller 156) to be displayed by transmitting data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component to visually generate the content.

[0052] In the following discussion, electronic devices are described that include a display and a touch-sensitive surface, however, it should be understood that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and / or a joystick.

[0053] The device typically supports a variety of applications such as any one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music playback application, and / or a digital video playback application.

[0054] 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 features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within each application. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications with user interfaces that are intuitive and transparent to the user.

[0055] Attention now turns to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 having touch-sensitive display system 112 according to some embodiments. Touch-sensitive display 112 may conveniently be referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 that detect the intensity of a contact on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 that generate tactile output on device 100 (e.g., generate tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0056] As used herein and in the claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four distinct values ​​and more typically includes hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure for the force or pressure of the contact is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is stated in units corresponding to the surrogate measure). In some implementations, the surrogate measure for the contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using contact intensity as an attribute of user input allows a user to access additional device functionality that may not otherwise be accessible by a user on devices of reduced size that have limited area for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0057] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a “downclick” or “upclick” of a physical actuator button. In some cases, a user feels a tactile sensation such as a “downclick” or “upclick” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

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

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

[0060] Peripheral interface 118 may be used to couple input and output peripherals of the device to CPU 120 and memory 102. One or more processors 120 operate or execute various software programs and / or instruction sets stored in memory 102 to perform various functions and process data for device 100. 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.

[0061] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to or from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. RF circuitry 108 optionally communicates wirelessly with networks, such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by short-range radios. Wireless communication is optionally supported by, but is not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), Long Term Evolution (LTE), and other standards.Wireless technology includes, but is not limited to, technology such as: LTE evolution (LTE), near field communications (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth®, Bluetooth Low Energy (BTLE®), Wireless Fidelity (Wi-Fi®) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX®, e-mail protocols (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol), and the like. The present invention may use any of a number of communication standards, protocols, and technologies, including the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (XMPP), the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), the Instant Messaging and Presence Service (IMPS), and / or the Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this application.

[0062] Audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuit 110 receives audio data from peripherals 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 audible to humans. Audio circuit 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuit 110 converts the electrical signals into audio data and transmits the audio data to peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to memory 102 and / or RF circuit 108 by peripherals interface 118. In some embodiments, audio circuit 110 also includes a headset jack (e.g., 212 in FIG. 2 ). The headset jack provides an interface between audio circuitry 110 and a detachable audio input / output peripheral, such as an output-only headphone or a headset with both an output (e.g., mono or binaural headphones) and an input (e.g., a microphone).

[0063] 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, light 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. One or more input controllers 160 receive / send electrical signals from / to other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some embodiments, input controller(s) 160 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2 ) optionally include up and down buttons for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in FIG. 2 ). In some embodiments, the electronic device is a computer system in communication (e.g., via wireless communication, via wired communication) with one or more input devices. In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a trackpad 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.

[0064] As described in U.S. Patent Application No. 11 / 322,549, filed December 23, 2005, "Unlocking a Device by Performing Gestures on an Unlock Image," U.S. Patent No. 7,657,849, which is incorporated herein by reference in its entirety, a quick press of the push button optionally disengages a lock on the touchscreen 112 or, optionally, initiates a process to unlock the device using a gesture on the touchscreen. A longer press of a push button (e.g., 206) optionally turns power on or off to the device 100. The functionality of one or more of the buttons is optionally customizable by the user. The touchscreen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0065] Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or sends electrical signals to touchscreen 112. Touchscreen 112 displays visual output to the user. This 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.

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

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

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

[0069] The touch-sensitive display in some embodiments of touch screen 112 may be any of the touch-sensitive displays described in U.S. patent application Ser. No. 11 / 381,313, filed May 2, 2006, entitled "Multipoint Touch Surface Controller," (2) U.S. patent application Ser. No. 10 / 840,862, filed May 6, 2004, entitled "Multipoint Touchscreen," (3) U.S. patent application Ser. No. 10 / 903,964, filed July 30, 2004, entitled "Gestures For Touch Sensitive Input Devices," (4) U.S. patent application Ser. No. 11 / 048,264, filed January 31, 2005, entitled "Gestures For Touch Sensitive Input Devices," and (5) U.S. patent application Ser. No. 11 / 038,590, filed January 18, 2005, entitled "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices." No. 11 / 228,758, filed September 16, 2005, entitled "Virtual Input Device Placement On A Touch Screen User Interface," (7) U.S. Patent Application No. 11 / 228,700, filed September 16, 2005, entitled "Operation Of A Computer With A Touch Screen Interface," (8) U.S. Patent Application No. 11 / 228,737, filed September 16, 2005, entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard," and (9) U.S. Patent Application No. 11 / 367,749, filed March 3, 2006, entitled "Multi-Functional Hand-Held Device," all of which are incorporated herein by reference in their entirety.

[0070] Touchscreen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. A user optionally contacts touchscreen 112 using any suitable object or accessory, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to primarily handle finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates the coarse finger input into precise pointer / cursor positions or commands to perform the action desired by the user.

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

[0072] Device 100 also includes a power system 162 that provides power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of electrical power within a portable device.

[0073] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Light sensor 164 optionally works in conjunction with imaging module 143 (also called a camera module) to capture still images or video. In some embodiments, the light sensor is located on the back of device 100, as opposed to touchscreen display 112, which is on the front of the device, so that the touchscreen display is effectively used as a viewfinder for capturing still and / or video images. In some embodiments, the light sensor is located on the front of the device so that an image of the user is obtained, optionally for video conferencing, and the user sees other video conference participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that a single light sensor 164 is used for both video conferencing and capturing still and / or video images, along with the touchscreen display.

[0074] Device 100 also optionally includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment and creates a three-dimensional model of an object (e.g., a face) in a 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 is optionally used to determine a depth map of various portions of an image captured by imaging module 143. In some embodiments, a depth camera sensor is located on the front of device 100 so that images of the user with depth information are optionally obtained for videoconferences and to capture selfie images with depth map data while the user views other videoconference participants on a touchscreen display. In some embodiments, depth camera sensor 175 is located on the back of the device or on both the back and front of device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that the depth camera sensor 175 is used for both video conferencing and capturing still and / or video images, along with a touchscreen display.

[0075] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information, or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with or proximate to the touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

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

[0077] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows tactile output generators coupled to haptic feedback controller 161 in I / O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

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

[0079] In some embodiments, software components stored in memory 102 include operating system 126, communications module (or instruction set) 128, touch / motion module (or instruction set) 130, graphics module (or instruction set) 132, text input module (or instruction set) 134, Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction set) 136. Additionally, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device / global internal state 157, as shown in FIGS. 1A and 3. Device / global internal state 157 includes one or more of: active application state indicating which applications, if any, are currently active; display state indicating which applications, views, or other information occupy various regions of touchscreen display 112; sensor state including information obtained from the device's various sensors and input control devices 116; and location information regarding the device's position and / or orientation.

[0080] Operating system 126 (e.g., Darwin®, RTXC®, LINUX®, UNIX®, OS X®, iOS®, WINDOWS®, or an embedded operating system such as VxWorks®) includes various software components and / or drivers that control and manage common system tasks (e.g., memory management, storage device control, power management, etc.) and facilitate communication between various hardware and software components.

[0081] Communications module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by RF circuitry 108 and / or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) is adapted to couple to other devices directly or indirectly via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, similar to, and / or compatible with the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

[0082] Contact / motion module 130, optionally in conjunction with display controller 156, detects contact with touchscreen 112 and other touch-sensing devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact occurs (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is contact movement and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-drag events), and determining whether contact has ceased (e.g., detecting a finger-up event or an interruption of contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact, as represented by the series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact. These actions are optionally applied to a single contact (e.g., a single finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on the touchpad.

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

[0084] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or intensities of detected contacts). Thus, gestures are optionally detected by detecting particular contact patterns. For example, detecting a finger tap gesture includes detecting a finger down event, followed by detecting a finger up (lift off) event at the same location (or substantially the same location) as the finger down event (e.g., the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger down event, followed by one or more finger drag events, followed by detecting a finger up (lift off) event.

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

[0086] In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. Graphics module 132 receives one or more codes specifying the graphics to be displayed, including coordinate data and other graphic characteristic data, as needed, from an application or the like, and then generates screen image data to output to display controller 156.

[0087] The tactile feedback module 133 includes various software components for generating instructions used by the tactile output generator(s) 167 to generate tactile outputs at one or more locations on the device 100 in response to user interaction with the device 100.

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

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

[0090] Application 136 optionally includes the following modules (or instruction sets), or a subset or superset thereof: • a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ●Videoconferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141; ●Training support module 142, a camera module 143 for still and / or video images, ● Image management module 144; ●Video player module, ●Music player module, ● Browser module 147, ● Calendar module 148, a widget module 149, optionally including any one or more of a weather widget 149-1, a stock price widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6; a widget creation module 150 for creating user-created widgets 149-6; ● Search module 151, A video and music player module 152 that integrates a video player module and a music player module; ● Memo module 153, Map module 154, and / or ●Online video module 155.

[0091] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

[0092] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, contacts module 137 is used to manage an address book or contact list (e.g., stored in memory 102 or in the application internal state 192 of contacts module 137 in memory 370), optionally including adding name(s) to the address book, deleting name(s) from the address book, associating phone number(s), email address(es), physical address(es), or other information with names, associating images with names, categorizing and sorting names, providing phone numbers or email addresses to initiate and / or facilitate communication by phone 138, videoconferencing module 139, email 140, or IM 141, etc.

[0093] Telephone module 138, in conjunction with 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, is optionally used to enter character sequences corresponding to telephone numbers, access one or more telephone numbers in contacts module 137, modify entered telephone numbers, dial respective telephone numbers, conduct conversations, and terminate or hang up when the conversation is completed. As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0094] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, touch / motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, videoconferencing module 139 includes executable instructions for initiating, conducting, and terminating a videoconference between a user and one or more other participants in accordance with user commands.

[0095] In cooperation with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 contains executable instructions for composing, sending, receiving, and managing emails in response to user commands. In cooperation with image management module 144, email client module 140 greatly facilitates the creation and sending of emails with still or video images captured by camera module 143.

[0096] In cooperation with RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for entering character sequences corresponding to instant messages, modifying previously entered characters, sending respective instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephony-based instant messaging, or XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0097] In conjunction with the RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, the training support module 142 includes executable instructions for creating workouts (e.g., with time, distance, and / or calorie burn goals), communicating with training sensors (sports devices), receiving training sensor data, calibrating sensors used to monitor workouts, selecting and playing music for workouts, and displaying, storing, and transmitting workout data.

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

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

[0100] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, browser module 147 contains executable instructions for browsing the Internet according to user commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

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

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

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

[0104] In cooperation with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions for searching for text, music, sound, images, video, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user commands.

[0105] In conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 contains executable instructions that enable a user to download and play pre-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 videos (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.).

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

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

[0108] In cooperation with touchscreen 112, display controller 156, contact / 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, online video module 155 contains instructions that enable a user to access, browse for, receive (e.g., by streaming and / or downloading), and play (e.g., on the touchscreen or on an external display connected via external port 124) particular online videos, send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140. Additional description of online video applications 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 entireties.

[0109] Each of the above-identified modules and applications corresponds to a set of executable instructions that perform one or more of the functions described above and methods described herein (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules; thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. For example, a video player module is optionally combined with a music player module into a single module (e.g., video and music player module 152 of FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

[0110] In some embodiments, device 100 is a device in which operation of a predetermined set of functions on the device is performed solely via a touchscreen and / or touchpad. Using the touchscreen and / or touchpad as the primary input control device for operation of device 100 optionally reduces the number of physical input control devices (push buttons, dials, etc.) on device 100.

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

[0112] 1B is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., within operating system 126) and a respective application 136-1 (e.g., any of applications 137-151, 155, 380-390 described above).

[0113] Event sorter 170 receives the event information and determines which application 136-1 to deliver the event information to and application view 191 for application 136-1. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192 that indicates the current application view(s) that are displayed on touch-sensitive display 112 when the application is active or running. In some embodiments, device / global internal state 157 is used by event sorter 170 to determine which application(s) are currently active, and application internal state 192 is used by event sorter 170 to determine which application(s) are currently active, and application internal state 192 is used by event sorter 170 to determine which application(s) to deliver the event information to.

[0114] In some embodiments, application internal state 192 includes additional information such as any one or more of resume information to be used when application 136-1 resumes execution, user interface state information indicating or ready to display information being displayed by application 136-1, state cues that allow the user to return to a previous state or view of application 136-1, and redo / undo cues of previous actions taken by the user.

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

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

[0117] In some embodiments, event sorter 170 also includes a hit view determination module 172 and / or an active event recognizer determination module 173 .

[0118] Hit view determination module 172 provides software procedures that determine where a sub-event occurred within one or more views when touch-sensitive display 112 displays more than one view. A view consists of the controls and other elements that a user can see on the display.

[0119] Another aspect of a user interface associated with an application is the 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 respective application) in which the touch is detected optionally corresponds to a programmatic level within the application's programmatic or view hierarchy. For example, the lowest-level view in which the touch is detected is optionally referred to as the hit view, and the set of events that are recognized as suitable inputs is optionally determined based at least in part on the hit view of the initial touch that initiates the touch gesture.

[0120] Hit view determination module 172 accepts information related to sub-events of a touch-based gesture. When an application has multiple views organized hierarchically, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest-level view in which an initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source as the hit view.

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

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

[0123] In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In still other embodiments, event sorter 170 is a stand-alone module or is part of another module stored in memory 102, such as contact / motion module 130.

[0124] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher-level object from which application 136-1 inherits methods and other attributes. In some embodiments, each event handler 190 includes one or more of data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or invokes data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of the data updater 176, object updater 177, and GUI updater 178 are included in each application view 191.

[0125] Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (optionally including sub-event delivery instructions).

[0126] Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, e.g., a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information, such as the position of the sub-event. When the sub-event involves a movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the current orientation of the device (also called the device's attitude).

[0127] The event comparator 184 compares the event information with predefined event or sub-event definitions and determines the event or sub-event, or determines or updates the state of the event or sub-event, based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a predefined sequence of sub-events), such as Event 1 (187-1) and Event 2 (187-2). In some embodiments, sub-events within Event 1 (187) include, for example, touch start, touch end, touch movement, touch cancellation, and multiple touches. In one example, the definition for Event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch on a displayed object relative to a predefined stage (touch start), a first lift-off (touch end) relative to the predefined stage, a second touch on a displayed object relative to the predefined stage (touch start), and a second lift-off (touch end) relative to the predefined stage. In another example, a definition of event 2 (187-2) is a drag on a displayed object. Drag includes, for example, a touch (or contact) on the displayed object to a predetermined stage, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (touch end). In some embodiments, the event also includes information about one or more associated event handlers 190.

[0128] In some embodiments, event definitions 187 include a definition of the event for each user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, when a touch is detected on touch-sensitive display 112 in an application view in which three user interface objects are displayed 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 respective event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggers the hit test.

[0129] In some embodiments, each event 187 definition also includes a delay action that delays delivery of the event information until it is determined whether the sequence of sub-events corresponds to the event type of the event recognizer.

[0130] If the respective event recognizer 180 determines that the sequence of sub-events does not match any of the events in the event definition 186, the respective event recognizer 180 enters an event-disabled, event-failed, or event-ended state and thereafter ignores the next sub-event of the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

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

[0132] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and deferring sending) the sub-events to the respective hit view. In some embodiments, the event recognizer 180 pops a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs a predetermined process.

[0133] In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with a set of sub-events or to an actively participating view. The event handler associated with the set of sub-events or the actively participating view receives the event information and performs predetermined processing.

[0134] In some embodiments, data updater 176 creates and updates data used by application 136-1. For example, data updater 176 updates phone numbers used in contacts module 137 or stores video files used in a video player module. In some embodiments, object updater 177 creates and updates objects used by application 136-1. For example, object updater 177 creates new user interface objects or updates the positions 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 the touch-sensitive display.

[0135] In some embodiments, event handler(s) 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0136] It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 using input devices, not all of which are initiated on the touchscreen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple keyboard presses or holds, pen stylus input, device movement, verbal commands, detected eye movement, biometric input, and / or any combination thereof, optionally utilize as inputs corresponding to sub-events that define the recognized event.

[0137] FIG. 2 illustrates portable multifunction device 100 having touchscreen 112, according to some embodiments. The touchscreen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user may select one or more of the graphics by performing a gesture on the graphics, for example, using one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upward and / or downward), and / or rolling of a finger in contact with device 100 (right to left, left to right, upward and / or downward). In some implementations or situations, accidental contact with a graphic does not select the graphic, for example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon optionally does not select the corresponding application.

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

[0139] In some embodiments, device 100 includes touchscreen 112, menu button 204, pushbuttons 206 for powering the device on / off and locking the device, volume control buttons 208, recipient identification module (SIM) card slot 210, headset jack 212, and external docking / charging port 124. Pushbutton 206 is optionally used to power the device on / off by pressing and holding the button down for a predetermined period of time, to lock the device by pressing and releasing the button before the predetermined time has elapsed, and / or to unlock the device or initiate the unlocking process. In alternative embodiments, device 100 also accepts verbal input via microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touchscreen 112 and / or one or more tactile output generators 167 for generating a tactile output for a user of device 100.

[0140] FIG. 3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or commercial 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 interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interface 330, including display 340, which is typically a touchscreen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, a touchpad 355, a tactile output generator 357 (e.g., similar to tactile output generator 167 described above with reference to FIG. 1A ) that generates tactile output on device 300, and sensors 359 (e.g., light, acceleration, proximity, touch-sensing, and / or contact intensity sensors similar to contact intensity sensor 165 described above with reference to FIG. 1A ). Memory 370 includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices, and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, ​​word processing module 384, website creation module 386, disc authoring module 388, and / or spreadsheet module 390, whereas memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

[0141] Each of the above-identified elements of FIG. 3 is optionally stored in any one or more of the memory devices mentioned above. Each of the above-identified modules corresponds to an instruction set that performs the function described above. The above-identified modules or programs (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. In some embodiments, memory 370 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.

[0142] Attention is now directed to embodiments of user interfaces, optionally implemented on portable multifunction device 100, for example.

[0143] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100 according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof: signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals; ●Time 404, ●Bluetooth® indicator 405, ● Battery status indicator 406, A tray 408 containing icons for frequently used applications, such as: an icon 416 for the phone module 138 labeled "Phone," optionally including an indicator 414 of the number of missed calls or voicemail messages; an icon 418 for the email client module 140, labeled "Mail," optionally including an indicator 410 of the number of unread emails; ○ An icon 420 for the browser module 147, labeled "Browser", and ○ An icon 422 labeled "iPod" for the video and music player module 152, also known as the iPod (registered trademark of Apple Inc.) module 152; and ●Icons for other applications, such as: ○ Icon 424 for IM module 141, labeled "Messages" ○ An icon 426 for the calendar module 148, labeled "Calendar"; ○ Icon 428 for the image management module 144, labeled "Photos" ○ An icon 430 for the camera module 143, labeled "camera"; ○ Icon 432 for the online video module 155, labeled "Online Video" Icon 434 for stock price widget 149-2, labeled "Stock Prices" ○ Icon 436 for map module 154, labeled "Map" ○ Icon 438 for weather widget 149-1, labeled "Weather" ○ Icon 440 for alarm clock widget 149-4, labeled "Clock" ○ Icon 442 for Training Support Module 142, labeled "Training Support"; ○ An icon 444 for the notes module 153, labeled "Notes," and An icon 446 for a settings application or module, labeled "Settings," that provides access to settings for the device 100 and its various applications 136.

[0144] 4A are merely exemplary. For example, icon 422 for video and music player module 152 may be labeled "Music" or "Music Player," although other labels are optionally used for the various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.

[0145] 4B shows an example user interface on a device (e.g., device 300 of FIG. 3 ) that has touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3 ) that is separate from display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) that detect the intensity of a contact on touch-sensitive surface 451, and / or one or more tactile output generators 357 that generate a tactile output for a user of device 300.

[0146] Although some of the following examples are given with reference to input on touchscreen display 112 (which combines a touch-sensitive surface and a display), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display shown in FIG. 4B . In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B ) has a primary axis (e.g., 452 in FIG. 4B ) that corresponds to a primary axis (e.g., 453 in FIG. 4B ) on the display (e.g., 450). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B ) at locations that correspond to respective locations on the display (e.g., in FIG. 4B , 460 corresponds to 468 and 462 corresponds to 470). In this way, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are optionally used for the other user interfaces described herein.

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

[0148] FIG. 5A shows an exemplary personal electronic device 500. Device 500 includes a main body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter referred to as touchscreen 504. Alternatively, or in addition 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 the touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of contact (e.g., touch) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data representing the intensity of the touch. A user interface of device 500 can respond to a touch based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface actions on device 500.

[0149] Exemplary techniques for detecting and processing touch intensity can be found, for example, in International Patent Application 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 International Patent Application No. WO / 2013 / 169849, and related applications, including International Patent Application 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 International Patent Application No. WO / 2014 / 105276, each of which is incorporated herein by reference in its entirety.

[0150] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical mechanisms. 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, can allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

[0151] FIG. 5B illustrates an exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has a bus 512 operably coupling an I / O section 514 to one or more computer processors 516 and memory 518. I / O section 514 can be connected to a display 504, which can have touch-sensing components 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, I / O section 514 can be connected to a communication unit 530 that receives application and operating system data using Wi-Fi, Bluetooth, near-field communication (NFC), cellular, and / or other wireless communication techniques. Device 500 can include input mechanisms 506 and / or 508. Input mechanism 506 is optionally a rotatable input device or a depressible and rotatable input device, for example. In some examples, input mechanism 508 is optionally a button.

[0152] 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 may be operably connected to the I / O section 514.

[0153] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, can cause the computer processors to perform the techniques described below, for example. A computer-readable storage medium may 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 embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, 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, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and resident solid-state memory such as flash and solid-state drives. The personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in multiple configurations.

[0154] As used herein, the term "affordance" refers to a user-interactive graphical user interface object that is optionally displayed on the display screen of device 100, 300, and / or 500 (FIGS. 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each optionally constitute an affordance.

[0155] As used herein, the term “focus selector” refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations involving a cursor or other location marker, the cursor acts as the “focus selector,” such that when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 of FIG. 3 or touch-sensitive surface 451 of FIG. 4B) while the cursor is positioned over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 of FIG. 1A or touchscreen 112 of FIG. 4A) that enables direct interaction with user interface elements on the touchscreen display, a detected contact on the touchscreen acts as the “focus selector,” such that when input (e.g., a press input by contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface without a corresponding cursor movement or contact movement on the touchscreen display (e.g., by using the tab key or arrow keys to move focus from one button to another), and in these implementations, the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the particular form the focus selector takes, the focus selector is generally a user interface element (or contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device which element of the user interface the user intends to interact with).For example, while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, touch, or selection box) over a corresponding button indicates that the user intends to activate that corresponding button (rather than other user interface elements shown on the device's display).

[0156] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples, i.e., a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the start of contact movement, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the maximum intensity of the contact, the mean intensity of the contact, the average intensity of the contact, the top 10 percentile intensity of the contact, half the maximum intensity of the contact, 90 percent of the maximum intensity of the contact, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold results in a first action, a contact having a characteristic intensity that exceeds the first intensity threshold but not the second intensity threshold results in a second action, and a contact having a characteristic intensity that exceeds the second threshold results in a third action. In some embodiments, the comparison between the characteristic intensity and the one or more thresholds is not used to determine whether the first action or the second action should be performed, but rather is used to determine whether one or more actions should be performed (e.g., whether to perform the respective action or to refrain from performing the respective action).

[0157] 6 illustrates exemplary devices connected via one or more communication channels to engage in a transaction according to some embodiments. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are optionally configured to detect input (e.g., specific user input, NFC field) and optionally transmit payment information (e.g., using NFC). One or more electronic devices optionally include NFC hardware and are configured to be NFC-enabled.

[0158] An electronic device (e.g., devices 100, 300, and 500) is optionally configured to store payment account information associated with each of one or more payment accounts. The payment account information includes, for example, any one or more of a personal or company name, a billing address, a login, a password, an account number, an expiration 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, the payment account information includes an image, such as a photograph of a payment card (e.g., taken and / or received by the device). In some embodiments, the electronic device receives user input including at least some payment account information (e.g., receives a credit, debit, account, or gift card number and expiration date entered by a user). In some embodiments, the electronic device detects at least some payment account information from an image (e.g., a payment card captured by a camera sensor of the device). In some embodiments, the electronic device receives at least some payment account information from another device (e.g., another user device or a server). In some embodiments, the electronic device receives payment account information from a server associated with another service (e.g., an app for renting or selling audio and / or video files) to which the user or user device or account for the identified payment account data previously made a purchase.

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

[0160] In some embodiments, communication between electronic devices 100, 300, and 500 facilitates a transaction (e.g., a general or specific transaction). For example, a first electronic device (e.g., 100) can act as a provisioning or management device and send notifications of new or updated payment account data (e.g., information for a new account, updated information for an existing account, and / or alerts regarding an existing account) to a second electronic device (e.g., 500). In another example, a first electronic device (e.g., 100) can send data to a second electronic device, the data reflecting information regarding a payment transaction facilitated at the first electronic device. The information optionally includes any one or more of the payment amount, the account used, the time of purchase, and whether the default account has changed. The second device (e.g., 500) optionally uses such information to update the default payment account (e.g., based on a learning algorithm or explicit user input).

[0161] The electronic devices (e.g., 100, 300, 500) are configured to communicate with each other over any of a variety of networks. For example, the devices communicate using a Bluetooth connection 608 (e.g., including a conventional Bluetooth connection or a Bluetooth low energy connection) or a WiFi network 606. Communications between user devices are optionally coordinated to reduce the likelihood of inappropriate sharing of information between devices. For example, communications related to payment information require the communicating devices to be paired (e.g., associated with each other through explicit user interaction) or associated with the same user account.

[0162] In some embodiments, the electronic device (e.g., 100, 300, 500) is used to communicate with a point-of-sale (POS) payment terminal 600, which is optionally NFC-enabled. This communication optionally occurs using various communication channels and / or technologies. In some embodiments, the electronic device (e.g., 100, 300, 500) communicates with the payment terminal 600 using an NFC channel 610. In some embodiments, the payment terminal 600 communicates with the electronic device (e.g., 100, 300, 500) using a peer-to-peer NFC mode. The electronic device (e.g., 100, 300, 500) is optionally configured to transmit a signal to the payment terminal 600 that includes payment information for a payment account (e.g., a default account or an account selected for a particular transaction).

[0163] In some embodiments, proceeding with the transaction includes transmitting a signal including payment information for an account, such as a payment account. In some embodiments, proceeding with the transaction includes reconfiguring the electronic device (e.g., 100, 300, 500) to respond as a contactless payment card, such as an NFC-enabled contactless payment card, and then transmitting account credentials via NFC to the payment terminal 600, etc. In some embodiments, after transmitting the account credentials via NFC, the electronic device reconfigures to not respond as a contactless payment card (e.g., requiring authentication before again being reconfigured to respond as a contactless payment card via NFC).

[0164] In some embodiments, signal generation and / or transmission is controlled by a secure element within the electronic device (e.g., 100, 300, 500). The secure element optionally requires a specific user input before disclosing the payment information. For example, the secure element optionally requires detecting that the electronic device is being worn, detecting a button press, detecting the entry of a passcode, detecting a touch, detecting one or more option selections (e.g., received during interaction with an application), detecting a fingerprint signature, detecting a voice or voice command, and / or detecting a gesture or movement (e.g., rotation or acceleration). In some embodiments, if a communication channel (e.g., an NFC communication channel) with another device (e.g., payment terminal 600) is established within a defined period of time from detecting the input, the secure element discloses the payment information to be sent to the other device (e.g., payment terminal 600). In some embodiments, the secure element is a hardware component that controls the disclosure of the secure information. In some embodiments, the secure element is a software component that controls the disclosure of the secure information.

[0165] In some embodiments, the protocol associated with engaging in a transaction depends, for example, on the device type. For example, the states for generating and / or transmitting payment information may be different for a wearable device (e.g., device 500) and a phone (e.g., device 100). For example, the generating and / or transmitting state for a wearable device may include detecting a button press (e.g., after security verification), while the corresponding state for a phone may not require a button press but instead detection of a specific interaction with an application. In some embodiments, the states for transmitting and / or publishing payment information may include receiving specific inputs on each of multiple devices. For example, publishing payment information optionally requires detection of a fingerprint and / or passcode on a device (e.g., device 100) and detection of a mechanical input (e.g., a button press) on another device (e.g., device 500).

[0166] The payment terminal 600 optionally uses the payment information to generate a signal that it sends to a payment server 604 to determine whether the payment is authorized. The 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, the payment server 604 includes an issuing bank's server. The payment terminal 600 communicates with the payment server 604 directly or indirectly via one or more other devices or systems (e.g., an acquiring bank's server and / or a card network's server).

[0167] The payment server 604 optionally uses at least some of the payment information to identify a user account in a database of user accounts (e.g., 602). For example, each user account includes payment information. The account is optionally located by locating an account with specific payment information that matches the payment information from the POS communication. In some embodiments, the payment is denied when the provided payment information does not match (e.g., the expiration date does not correspond to a credit, debit, or gift card number) or when there is no account with payment information that matches the payment information from the POS communication.

[0168] In some embodiments, the data for the user account further identifies one or more limits (e.g., credit limit), current or previous balance, previous transaction date, location, and / or amount, account status (e.g., active or frozen), and / or authorization instructions. In some embodiments, the payment server (e.g., 604) uses such data to determine whether to authorize a payment. For example, the payment server denies a payment when adding the purchase amount to the current balance would exceed an account limit, when the account is frozen, when the previous transaction amount exceeds a threshold, or when the number or frequency of previous transactions exceeds a threshold.

[0169] In some embodiments, the payment server 604 responds to the POS payment terminal 600 with an indication as to whether the proposed purchase was authorized or denied. In some embodiments, the POS payment terminal 600 sends a signal to the electronic device (e.g., 100, 300, 500) to identify the outcome. For example, the POS payment terminal 600 sends a receipt to the electronic device (e.g., 100, 300, 500) when the purchase is authorized (e.g., via a transaction coordination server that manages the transaction app on the user device). In some cases, the POS payment terminal 600 presents an output (e.g., a visual or audio output) indicating the outcome. The payment can be sent to the merchant as part of the authentication process or can be sent at a later time.

[0170] In some embodiments, the electronic device (e.g., 100, 300, 500) participates in a transaction that is completed without the intervention of the POS payment terminal 600. For example, upon detecting that machine input has been received, a secure element within the electronic device (e.g., 100, 300, 500) exposes payment information and allows an application on the electronic device to access the information (e.g., transmit the information to a server associated with the application).

[0171] In some embodiments, 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 operational, but is prevented from performing a predetermined set of operations in response to user input. The predetermined set of operations may include navigation between user interfaces, activation or deactivation of a predetermined set of functions, and activation or deactivation of specific applications. The locked state may be used to prevent unintended or unauthorized use of some functionality of the electronic device or activation or deactivation of some functions on the electronic device. In the unlocked state, the electronic device 100 is powered on and operational, and is not prevented from performing at least a portion of the predetermined set of operations that cannot be performed in the locked state.

[0172] When a device is in the locked state, the device is considered locked. In some embodiments, a device in the locked state may respond to a limited set of user inputs, including inputs corresponding to an attempt to transition the device from the unlocked state or inputs corresponding to powering off the device.

[0173] In some embodiments, the secure element is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or algorithms. In some embodiments, the secure element provides (or reveals) payment information (e.g., an account number and / or a transaction-specific dynamic security code). In some embodiments, the secure element provides (or reveals) payment information in response to the device receiving an authorization such as user authentication (e.g., fingerprint authentication, passcode authentication, detecting a double press of a hardware button when the device is in an unlocked state, and optionally, when the device is continuously on the user's wrist since being unlocked by providing authentication credentials to the device; the continuous presence of the device on the user's wrist is determined by periodically testing that the device is in contact with the user's skin). For example, the device detects a fingerprint with a fingerprint sensor (e.g., a fingerprint sensor integrated into a button) on the device. The device determines whether the fingerprint matches a registered fingerprint. Following a determination that the fingerprint matches a registered fingerprint, the secure element provides (or reveals) the payment information. Pursuant to a determination that the fingerprint does not match the enrolled fingerprint, the secure element refrains from providing (or releasing) the payment information.

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

[0175] As used herein, the terms "open application" or "running application" refer to a software application that has retained 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 one of the following types of application: ● the active application currently displayed on the display screen of the device on which the application is being used; background applications (or background processes) that are not currently displayed, but for which one or more processes for the application are being processed by one or more processors; and • A suspended or hibernated application that is not running but has state information stored in memory (volatile and non-volatile respectively) that can be used to resume execution of the application.

[0176] As used herein, the term "closed application" refers to a software application that does not have retained state information (e.g., state information for a closed application is not stored in the device's memory). Thus, closing an application includes stopping and / or removing the application process for the application and removing state information for the application from the device's memory. Generally, opening a second application during a first application does not close the first application. When a second application is displayed and the first application is no longer displayed, the first application becomes a background application.

[0177] Attention is now directed to embodiments of user interfaces (“UIs”) and related processes implemented on an electronic device such as portable multifunction device 100, device 300, or device 500.

[0178] 7A-7AZ show exemplary user interfaces for invoking an activity associated with an application, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 8A-8B.

[0179] FIG. 7A illustrates a computer system 700 (e.g., an electronic device, smartphone, smartwatch, tablet, mobile device) that communicates with (e.g., includes) 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., GPS sensors), one or more image sensors (e.g., cameras, mechanical input devices). In FIG. 7A , the computer system 700 displays a wake screen (e.g., lock screen) user interface 704 of the computer system 700 via the display generating component 702A. In some embodiments, a wake screen is a user interface that is displayed when the display generating component of the computer system transitions from an inactive (e.g., off) state to an active (e.g., on) state. In some embodiments, a lock screen is a user interface that is displayed when the computer system is operating in a locked state, where at least some functionality of the computer system is limited (e.g., until the computer system is unlocked).

[0180] In some embodiments, computer system 700 detects (e.g., determines) (via one or more location sensors (e.g., GPS sensors) in communication with computer system 700) that the system is at (e.g., has entered) a first respective location (e.g., a store, a restaurant, a cafe, a bakery). In some embodiments, computer system 700 detects that the system is at the first respective location while displaying a wake screen user interface 704. In some embodiments, computer system 700 detects that the system is at the first respective location while displaying a different user interface (e.g., of a different application). In some embodiments, computer system 700 detects that the system is at the first respective location while display generation component 702 is in an off state.

[0181] In FIG. 7B , in response to detecting (e.g., determining) that computer system 700 is at a first respective location, computer system 700 displays, via display generation component 702 (e.g., overlaid on a portion of user interface 704), a seat user interface 706 corresponding to the first respective location, where seat user interface 706 includes an information region 706A containing information about the first respective location (e.g., the name of the first respective location, the address of the first respective location, an identifier / identification number (e.g., object number, branch number, table number) associated with an activity that can be performed at the first respective location (e.g., reserving an object (e.g., a motorcycle, a car) to rent, ordering a menu item such as food and / or drinks)), and an affordance 706B (e.g., a selectable user interface object, an activatable user interface object) that, when activated, initiates a process (e.g., ordering, reserving, purchasing) that enables an activity on computer system 700 associated with the first respective location. In some embodiments, the seat user interface has the appearance of a seat that is displayed (e.g., pops up) over the current user interface and includes a graphical element that has a similar appearance to the graphical elements (e.g., seats) that are displayed (e.g., pops up) when other predetermined events occur, such as pairing headphones, controlling music on a home audio device, etc.

[0182] 7B-7N, the first respective location is a first restaurant (e.g., a restaurant called "Food King"). In some embodiments, information region 706A includes the name of the first restaurant (e.g., "Food King") and the address of the first restaurant.

[0183] In some embodiments, affordance 706B indicates (e.g., includes text describing) a type of activity (e.g., ordering menu items such as food and / or drinks) associated with the first restaurant.

[0184] In some embodiments, the seat user interface 706 includes an image 706C that depicts the first restaurant (eg, of the first restaurant, eg, a logo of the first restaurant).

[0185] In some embodiments, the seat user interface 706 includes an indication 706D (e.g., text or images) of a developer (e.g., an entity, company) that provides (e.g., creates and / or manages) an application (e.g., an application platform) of a first type (e.g., a simplified / partial version of an application with a corresponding available full / regular version) that can be used to enable an activity associated with the first restaurant (e.g., ordering menu items such as food and / or drinks). For ease of explanation, the first type of application may also be referred to as a simplified version application.

[0186] In some embodiments, the developer is different from the vendor corresponding to the first restaurant (i.e., the vendor corresponding to the first restaurant is not the developer of the simplified version application). For example, in FIG. 7B , the application is provided by a first developer (e.g., "Food Reviews") that is different from the vendor corresponding to the first restaurant (e.g., "Food King"). In some embodiments, the developer can provide an application platform for use by multiple different vendors, and the application can be customized for each vendor. In some embodiments, the developer is the same as the vendor corresponding to the first restaurant (i.e., the vendor corresponding to the first restaurant is the developer of the simplified version application).

[0187] In some embodiments, the sheet user interface 706 includes affordances 706E (e.g., selectable user interface objects, activatable user interface objects) for accessing an application store (e.g., an application store, such as a computer application or website, controlled and managed by the developer of the operating system of the computer system 700, which can be used to download first-party and third-party applications to the computer system 700).

[0188] In some embodiments, the seat user interface 706 includes an affordance 706F (e.g., a selectable user interface object, an activatable user interface object) for hiding the seat user interface 706 (e.g., causing the computer system 700 to terminate the display) without performing an activity associated with the first restaurant (e.g., ordering a menu item such as food and / or beverages).

[0189] In FIG. 7C , while displaying seat user interface 706 that may be used to initiate an activity associated with a first restaurant (e.g., ordering a menu item such as food and / or beverages), computer system 700 detects activation (e.g., user selection, user tap input) of affordance 706B via one or more input devices (e.g., via a touch-sensitive surface of one or more input devices).

[0190] 7D , in response to detecting activation 701 of affordance 706B, and pursuant to a determination that a second type (e.g., full / regular version of the application) application of the developer (indicated via suggestion 706D) is already installed (and therefore already available) on computer system 700, computer system 700, via display generation component 702, displays user interface 708 of the second type application already installed on computer system 700. In some embodiments, the second type application can be downloaded onto computer system 700 from an application store. For ease of explanation, the second type application may also be referred to as a full version application. In some embodiments, each full version application has a corresponding simplified version application (e.g., created and / or managed by the same developer (e.g., the same entity, the same company)).

[0191] 7E shows computer system 700 (e.g., again) displaying sheet user interface 706 via display generation component 702 (e.g., overlaid on a portion of user interface 704). In FIG. 7E, the full version application corresponding to the developer is not available (e.g., not installed) on computer system 700.

[0192] 7E , while displaying sheet user interface 706, computer system 700 detects activation 703 (e.g., user selection, user tap input) of affordance 706E for accessing an application store (e.g., via the touch-sensitive surface of one or more input devices). In some embodiments, computer system 700 includes affordance 706E in sheet user interface 706 only if a full version application corresponding to the developer is not installed on computer system 700 (e.g., as in FIG. 7E ). In some embodiments, computer system 700 includes affordance 706E in sheet user interface 706 even if a full version application corresponding to the developer is already installed on computer system 700.

[0193] In FIG. 7F , in response to detecting activation 703 of affordance 706E, computer system 700, via display generation component 702, displays application store user interface 710, and the application store displays application page 712 in user interface 710 that corresponds to the full version application and for downloading the full version application to computer system 700.

[0194] 7G-7N illustrate a method (e.g., a location-based method) for initiating a process to enable an activity on computer system 700 without using a corresponding full version application on computer system 700 (e.g., because the full version application is not installed on computer system 700). FIG. 7G illustrates computer system 700 displaying seat user interface 706 as initially shown in FIG. 7B in response to detecting (e.g., via one or more location sensors of one or more input devices) that computer system 700 is at a first restaurant (e.g., because a user of computer system 700 has entered / arrived at the first restaurant). In FIG. 7G, similar to FIG. 7E, a full version application of a developer (e.g., "Food Reviews") is not available (e.g., not installed) on computer system 700.

[0195] In FIG. 7G , while displaying seat user interface 706, computer system 700 detects (e.g., via a touch-sensitive surface of one or more input devices) activation 705 (e.g., user selection, user tap input) of affordance 706B to initiate a process of enabling an activity (e.g., ordering) related to a first restaurant on computer system 700.

[0196] 7H-7J , in response to detecting activation 705 of affordance 706B in seat user interface 706, computer system 700, via display generation component 702, displays user interface 714 (e.g., a loading screen) including a suggestion 714A of the name of the first restaurant (e.g., "Food King") and a suggestion 714B of a developer (e.g., entity, company) (e.g., "Food Reviews") that provides a simplified version of an application (e.g., creating and / or managing templates) that can be used to enable an activity associated with the first restaurant (e.g., ordering menu items such as food and / or drinks). In some embodiments, computer system 700, via suggestion 714A and / or suggestion 714B, displays a visual animation (e.g., the loading screen is animated) while displaying user interface 714.

[0197] 7K, in response to (e.g., following) detecting activation 705 of affordance 706B in seat user interface 706 (e.g., after displaying user interface 714 (e.g., a loading screen) for a predetermined period of time), computer system 700A, via display generation component 702, displays simplified user interface 716 of a simplified version application, where simplified user interface 716 corresponds to a first restaurant version (e.g., the "Food King" version) of the simplified version application (e.g., "Food Reviews"). In some embodiments, simplified user interface 716 corresponds to a simplified version application of the full version application (e.g., "Food Reviews"), the corresponding full version user interface being shown in FIG. 7D. In some embodiments, in accordance with determining that the light version application has not been automatically installed on computer system 700, computer system 700, in response to detecting activation 705 of affordance 706B in seat user interface 706, automatically (e.g., without user input) downloads and installs the light version application corresponding to light user interface 716 (e.g., while displaying user interface 714 (e.g., a loading screen) shown in FIGS. 7H-7J). In some embodiments, computer system 700 does not require user authentication (e.g., by providing authentication information such as biometric authentication and / or password / passcode authentication) to automatically download and install the light version application.

[0198] 7K, in some embodiments, simplified user interface 716 includes location information 718 (e.g., address) of the first restaurant. In some embodiments, simplified user interface 716 includes a menu area 720 including multiple selectable menu items available to order at the first restaurant. In some embodiments, simplified user interface 716 includes affordances 722 (e.g., selectable user interface objects, activatable user interface objects) for ordering / checking the selected menu items.

[0199] 7K , in some embodiments, simplified user interface 716 includes a user interface object 724 (e.g., a banner, a platter) that is displayed concurrently with simplified user interface 716 (e.g., overlaid on a portion of simplified user interface 716). In some embodiments, user interface object 724 is displayed concurrently with the display of simplified user interface 716 and is displayed for a predetermined period of time (e.g., 10 seconds, 30 seconds, 1 minute). In some embodiments, user interface object 724 includes a suggestion 724A (e.g., text information) of a developer (e.g., an entity, a company) that provides a simplified version application corresponding to simplified user interface 716 (e.g., creating and / or managing templates). In some embodiments, user interface object 724 includes a sharing affordance 724B for initiating a process for sharing the simplified version application corresponding to simplified user interface 716 with a different user (e.g., sending an electronic communication to a different computer system of a different user that includes the simplified version application and / or instructions for downloading the simplified version application).

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

[0201] 7M , in response to detecting user selection 709 and user selection 711 of first menu item 720A and second menu item 720B, respectively, computer system 700 displays (e.g., via affordance 722) within simplified user interface 716 an indication that the selected menu items have been added to the current order (e.g., added to checkout cart). While the selected menu items are being added to the current order, computer system 700 detects activation 711 (e.g., user selection, user tap input) of affordance 722 (e.g., via the touch-sensitive surface of one or more input devices).

[0202] 7N , in response to detecting activation 711 of affordance 722, computer system 700, via display generating component 702 (e.g., superimposed over a portion of simplified user interface 716 such that a portion, but not all, of simplified user interface 716 remains visible on display generating component 702), displays authentication user interface 726 for authenticating a transmission (e.g., a transaction) to complete the process of ordering the selected menu item. In some embodiments, authentication 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 computer system 700.

[0203] 7O-7U illustrate a method (e.g., a point-of-interest-based method) for initiating a process to enable an activity on computer system 700 without using a corresponding full version application on computer system 700 (e.g., because a full version application is not installed on computer system 700). FIG. 7O illustrates computer system 700 displaying, via display generation component 702, a user interface 728 of a map application that includes a map 730, the map 730 including a plurality of location points 730A-730D that correspond to points of interest (e.g., saved locations, favorite locations, suggested locations).

[0204] In FIG. 7O, while displaying a map 730 within a map application user interface 728, computer system 700 detects (e.g., via the touch-sensitive surface of one or more input devices) a user selection 713 of a first location point 730A (e.g., a first point of interest) within map 730, where first location point 730A corresponds to a first bike rental location.

[0205] In FIG. 7P , in response to detecting a user selection 713 of a first location point 730A on map 730, computer system 700, via display generation component 702 (e.g., overlaid on a portion of user interface 728), displays (e.g., pops up) a user interface 732 including information (e.g., name, address, rating, reviews, photos, directions) about the selected location (e.g., first bike rental location), and user interface 732 includes an affordance 732A (e.g., selectable user interface object, activatable user interface object) associated with initiating a process to enable an activity (e.g., rent a bike) associated with the selected first bike rental location on computer system 700.

[0206] In FIG. 7P, while displaying sheet user interface 732, computer system 700 detects activation 715 (e.g., user selection, user tap input) of affordance 732A (e.g., via the touch-sensitive surface of one or more input devices).

[0207] In FIG. 7Q, in response to detecting activation 715 of affordance 732A, computer system 700, via display generation component 702 (e.g., overlaid on a portion of map application user interface 728), displays seat user interface 734 corresponding to the selected respective location (e.g., first bike rental location), which is similar to (e.g., has the same layout / structure, provides a consistent experience) seat user interface 706 first described with reference to FIG. 7B. In FIG. 7B, seat user interface 706 is associated with enabling an activity (e.g., ordering) based on the detected respective location (e.g., detecting that computer system 700 is at a first restaurant). In FIG. 7Q, seat user interface 734 is associated with enabling an activity (e.g., rental) based on the detected (e.g., received) selection of the respective location from the map application.

[0208] 7O-7U, each selected location is a first bike rental location (e.g., bike rental store, bike rental port). In some embodiments, seat user interface 734 includes an information region 734A that includes the name of the first bike rental location (e.g., "Bike Rental 3"), address and / or branch information for the bike rental location (e.g., "Location 42"), and an affordance 734B (e.g., a selectable user interface object, an activatable user interface object) that, when activated, initiates a process (e.g., ordering, reserving, purchasing) to enable an activity (e.g., reserving a bike) related to the first bike rental location.

[0209] In some embodiments, the seat user interface 734 includes an image 734C showing the first bike rental location (e.g., the first bike rental location, a logo of the vendor (e.g., entity / company) operating the first bike rental location).

[0210] In some embodiments, seat user interface 734 includes a suggestion 734D of a developer (e.g., entity, company) that provides a simplified version application (e.g., creates and / or manages templates) that can be used to enable an activity (e.g., reserving a bike) associated with the first remaining first bike rental location on computer system 700. In some embodiments, similar to FIG. 7Q, the developer that provides the simplified version application (and the corresponding full version application) is the same as the vendor (e.g., entity / company) that operates the first bike rental location.

[0211] In some embodiments, the sheet user interface 734 includes affordances 734E (e.g., selectable user interface objects, activatable user interface objects) 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, which application store can be used to download first-party and third-party applications to the computer system 700).

[0212] In some embodiments, the seat user interface 734 includes an affordance 734F (e.g., a selectable user interface object, an activatable user interface object) for hiding the seat user interface 734 (e.g., causing the computer system 700 to terminate the display) without performing an activity associated with the first bike rental location (e.g., reserving a bike).

[0213] In FIG. 7R, while displaying a seat user interface 734 that can be used to initiate an activity associated with a first bike rental location (e.g., reserving a bike), computer system 700 detects (e.g., via the touch-sensitive surface of one or more input devices) activation 717 (e.g., user selection, user tap input) of affordance 734B.

[0214] 7S, in response to detecting activation 717 of affordance 734B, and pursuant to determining that a full version application for enabling an activity (e.g., reserving a bike) is not available (e.g., not installed) on computer system 700, computer system 700 displays simplified user interface 736 of a simplified version application for enabling an activity (e.g., reserving a bike) via display generation component 702. In some embodiments, a counterpart full version application for the simplified version application for enabling an activity (e.g., reserving a bike) can be downloaded onto computer system 700 from an application store (e.g., via affordance 734E of user interface 734). In some embodiments, if the simplified version application is not installed on computer system 700 (e.g., because this is the first time the simplified version “Bike Rental” application is accessed), computer system 700 (e.g., in response to detecting activation 717 of affordance 734B) automatically (e.g., without user input, without user authentication) and installs the simplified version application (e.g., before and / or while displaying simplified user interface 736).

[0215] As shown in FIG. 7S, in some embodiments, simplified user interface 736 includes a first region 738 that includes a map (e.g., a map provided by a simplified application customized for the activity, as opposed to the map application shown in FIG. 7O, which shows one or more nearby locations corresponding to different bike rental locations). In some embodiments, simplified user interface 736 includes suggestions 740 (e.g., displayed as a user interface object, such as a platter) that show each bike rental location (e.g., a first bike rental location) that is closest to the current location of computer system 700 (e.g., including the time required to reach (e.g., walking) each bike rental location).

[0216] In some embodiments, simplified user interface 736 includes a second area 742 that includes information about an object (e.g., a particular bike) that can be reserved at the first bike rental location, including an identifier / identification number for the object (e.g., the identification number for that particular bike). In some embodiments, second area 742 includes an affordance 744 for reserving the object (e.g., a particular bike) and an affordance 746 for initiating the object rental process (e.g., by scanning the bike's code / identifier) ​​once the user reaches the object.

[0217] In some embodiments, while a simplified version application corresponding to simplified user interface 736 is currently being used or is being used (e.g., active, currently displayed, and / or running in the background on the computer system), computer system 700 detects (e.g., via one or more location sensors) that computer system 700 is being moved in proximity to a first bike rental location. In some embodiments, computer system 700 indicates (e.g., via suggestion 740) within simplified user interface 736 an updated location of computer system 700 relative to the first bike rental location, as shown in FIG. 7T.

[0218] 7U illustrates computer system 700 displaying, via display generation component 702, a user interface 704 corresponding to a wake screen (e.g., a lock screen) of computer system 700, as first described with reference to FIG. 7A. In some embodiments, the simplified version application is enabled (e.g., authenticated and has access) and triggers a notification to computer system 700.

[0219] In FIG. 7U, pursuant to determining that computer system 700 is at (e.g., has reached) the first bike rental location, computer system 700, via display generation component 702, displays notification 748 indicating that the location has been reached.

[0220] 7V-7AA illustrate methods (e.g., NFC-based methods, QR code-based methods) for initiating the process of enabling an activity on computer system 700 without using a corresponding full version application on computer system 700 (e.g., because a full version application is not installed on computer system 700).

[0221] 7V illustrates computer system 700 displaying, via display generation component 702, a user interface 704 corresponding to a wake screen (e.g., a lock screen) of computer system 700, as first described with reference to FIG. 7A. In FIG. 7V, computer system 700 is at a first identified location (e.g., a first table) in a first location (e.g., a first restaurant, a first cafe, a first bakery). In the example user interfaces illustrated in FIGS. 7V-7AA, the first identified location is at a first table (e.g., table 5) in the first cafe.

[0222] 7W illustrates a computer system 700 communicating (e.g., via NFC) with a contactless wireless terminal 750 (e.g., an NFC terminal), where terminal 750 corresponds to a terminal at a first table (table 5) in a first cafe. In some embodiments, as shown in FIG. 7W , display generation component 702 of computer system 700 is in an on state (e.g., displaying user interface 704) when the computer system receives a respective communication from terminal 750 (e.g., via NFC) (e.g., or alternatively, computer system 700 detects a QR code from a scan (e.g., using one or more image sensors) of a QR code terminal). In some embodiments, display generation component 702 of computer system 700 is in an off state when computer system 700 receives a respective communication from terminal 750 (e.g., via NFC).

[0223] In FIG. 7W , computer system 700 detects (e.g., receives) identification information (e.g., identifier) ​​from terminal 750 (e.g., via NFC) (e.g., or alternatively, detects a QR code via scanning a QR code at a first table (e.g., using one or more image sensors)), where the identification information includes information about the first cafe (e.g., information identifying the first cafe) and / or information about the first table (e.g., information identifying that terminal 750 corresponds to table 5 within the first cafe).

[0224] In FIG. 7X, in response to detecting (e.g., receiving) identification information from terminal 750 (e.g., via NFC, by scanning a QR code), computer system 700, via display generation component 702 (e.g., overlaid on a portion of user interface 704), displays seat user interface 752 based on the identification information from terminal 750, which is similar to (e.g., has the same layout / structure, provides a consistent experience with) seat user interface 706 first described with reference to FIG. 7B and seat user interface 734 first described with reference to FIG. 7Q. In FIG. 7B, seat user interface 706 is associated with enabling an activity (e.g., ordering) based on the detected respective location (e.g., detecting that computer system 700 is at a first restaurant). In FIG. 7Q, seat user interface 734 is associated with enabling an activity (e.g., rental) based on the detected (e.g., received) selection of the respective location from a map application. In FIG. 7X, the seat user interface 752 is associated with enabling an activity (e.g., an order) based on identification information detected (e.g., received) from an external device (e.g., a contactless wireless terminal) (e.g., via NFC, by scanning a QR code).

[0225] 7V-7AA, the detected (e.g., received) identification information includes information about a first cafe and identifies a first table (e.g., table 5) within the first cafe. In some embodiments, the seat user interface 752 includes an information region 752A that includes the name of the first cafe (e.g., "Coffee Shop"), address and / or branch information for the first cafe, and an affordance 752B (e.g., a selectable user interface object, an activatable user interface object) that, when activated, initiates a process to enable an activity (e.g., ordering one or more menu items for the first table) related to the first cafe and, specifically, the first table (e.g., table 5) at the first cafe.

[0226] In some embodiments, the seat user interface 752 includes an image 752C showing the first cafe (e.g., "Coffee Shop") (e.g., a logo of the first cafe and of the vendor (e.g., entity / company) operating the first cafe).

[0227] In some embodiments, the sheet user interface 752 displays a suggestion 752D of a developer (e.g., entity, company) that provides a simplified version application (e.g., creates and / or manages templates) that can be used to enable an activity (e.g., ordering one or more menu items, such as food or drinks) associated with the first cafe (e.g., "Coffee Shop"). In some embodiments, as in FIG. 7X, the developer (e.g., "Food Reviews") that provides the simplified version application (and the corresponding full version application) is different from the vendor (e.g., the first cafe (e.g., "Coffee Shop")).

[0228] In some embodiments, the seat user interface 752 includes affordances 752E (e.g., selectable user interface objects, activatable user interface objects) 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, which application store can be used to download first-party and third-party applications to the computer system 700). In some embodiments, a full-version application counterpart to a simplified version application for enabling an activity (e.g., reserving a bike) can be downloaded onto the computer system 700 from the application store (e.g., via affordances 752E of the seat user interface 752).

[0229] In some embodiments, the seat user interface 752 includes an affordance 752F (e.g., a selectable user interface object, an activatable user interface object) for hiding the seat user interface 752 (e.g., causing the computer system 700 to terminate the display) without performing an activity associated with the first cafe (e.g., ordering one or more menu items for the first table).

[0230] In FIG. 7Y, while displaying a seat user interface 752 that can be used to initiate an activity associated with a first cafe (e.g., ordering one or more menu items for a first table), computer system 700 detects (e.g., via the touch-sensitive surfaces of one or more input devices) activation 719 (e.g., user selection, user tap input) of affordance 752B.

[0231] 7Z , in response to detecting activation 719 of affordance 752B, and pursuant to determining that a full version application (e.g., the full version of the “Food Reviews” application) for enabling the activity (e.g., ordering one or more menu items for the first table) is not available (e.g., not installed), computer system 700, via display generation component 702, displays simplified user interface 754 corresponding to a simplified version application (e.g., “Food Reviews”) for enabling the activity (e.g., ordering one or more menu items for the first table). In some embodiments, if the simplified version application is not installed on computer system 700 (e.g., because this is the first time the simplified version “Food Reviews” application is accessed), computer system 700 (e.g., in response to detecting activation 719 of affordance 752B) automatically (e.g., without user input, without user authentication) and installs the simplified version application (e.g., before and / or while displaying simplified user interface 754).

[0232] In some embodiments, simplified user interface 754 is similar to (e.g., shares a similar layout with) simplified user interface 716 described above with reference to FIG. 7K because both simplified user interfaces are provided by the same developer (e.g., same entity, same company) (e.g., “Food Reviews”). As shown in FIG. 7Z , in some embodiments, simplified user interface 754 includes location information 756 (e.g., address) of the first cafe. In some embodiments, simplified user interface 754 includes identification information (e.g., table number for the first table (e.g., table 5)) (e.g., along with location information 756). In some embodiments, simplified user interface 754 includes menu area 758 including multiple selectable menu items available for ordering at the first cafe. In some embodiments, simplified user interface 754 includes affordance 760 (e.g., selectable user interface object, activatable user interface object) for ordering / checking the selected menu item.

[0233] In some embodiments, simplified user interface 754 includes a user interface object 762 (e.g., a banner, a platter) (e.g., similar to user interface object 724 described above with reference to FIG. 7K ) that is displayed concurrently with (e.g., overlaid on) a portion of simplified user interface 754. In some embodiments, user interface object 762 is displayed concurrently with the display of simplified user interface 754 and is displayed for a predetermined period of time (e.g., 10 seconds, 30 seconds, 1 minute; computer system 700 ceases displaying user interface object 762 after the predetermined period of time). In some embodiments, user interface object 762 includes a suggestion 762A (e.g., text information) of a developer (e.g., entity, company) to provide a simplified version application (e.g., create and / or manage templates) that corresponds to simplified user interface 754. In some embodiments, user interface object 762 includes a sharing affordance 762B for initiating a process for sharing a simplified version application corresponding to simplified user interface 716 with a different user (e.g., sending an electronic communication to a different computer system of a different user that includes the simplified version application and / or a method for initiating the download of the simplified version application).

[0234] 7AA illustrates computer system 700 displaying simplified user interface 754 via display generation component 702 after a predetermined period of time (e.g., 10 seconds, 30 seconds, 1 minute) has elapsed. In some embodiments, pursuant to determining that the predetermined period of time has elapsed, computer system 700 automatically (e.g., without user input) ceases displaying user interface object 762 (e.g., while maintaining display of simplified user interface 654).

[0235] 7AB-7AF illustrate a method (e.g., a link-based (e.g., hyperlink-based) method) for initiating a process to enable an activity on computer system 700 without using a corresponding full version application on computer system 700 (e.g., because a full version application is not installed on computer system 700). FIG. 7AB illustrates computer system 700 displaying, via display generation component 702, a browser application user interface 756, which shows web page 758. In the example user interface shown in FIG. 7AB, web page 758 is a first car sales / rental web page, and web page 758 includes a selectable link 760 (e.g., a hyperlink).

[0236] In FIG. 7AC, while displaying web page 758 within seat user interface 756, computer system 700 detects activation 721 (e.g., user selection, user tap input) of selectable link 760 (e.g., via the touch-sensitive surface of one or more input devices).

[0237] In FIG. 7AD, in response to detecting activation 721 of selectable link 760, computer system 700, via display generation component 702 (e.g., overlaid over a portion of user interface 756), displays seat user interface 762 corresponding to the selected link (e.g., from car sales / rental web page 758). In some embodiments, seat user interface 762 is similar to (e.g., has the same layout / structure, provides a consistent experience) seat user interface 706 first described with reference to FIG. 7B, seat user interface 734 first described with reference to FIG. 7Q, and seat user interface 752 first described with reference to FIG. 7X. In FIG. 7B, seat user interface 706 is associated with enabling an activity (e.g., ordering) based on a detected respective location (e.g., detecting that computer system 700 is at a first restaurant). In FIG. 7Q, seat user interface 734 is associated with enabling an activity (e.g., renting) based on a detected (e.g., received) selection of a respective location from a map application. In Figure 7X, the seat user interface 752 is associated with enabling an activity (e.g., ordering) based on identification information detected (e.g., received) from an external device (e.g., a contactless wireless terminal) (e.g., via NFC, by scanning a QR code). In Figure 7AD, the seat user interface 762 is associated with enabling an activity (e.g., purchasing, renting) based on a link selected (e.g., from a web page), where the activity is related to content associated with the link.

[0238] 7AB-7AF, the selected link 760 relates to purchasing and / or renting a car from a first car store. In some embodiments, the seat user interface 762 includes an information region 762A that includes the name of the first car store (e.g., "Shiny Cars"), address and / or branch information for the first car store, and an affordance 762B (e.g., a selectable user interface object, an activatable user interface object) that, when activated, initiates a process (e.g., purchase, rental) that enables an activity related to the first car store.

[0239] In some embodiments, the seat user interface 762 includes an image 762C showing a first car store (e.g., “Shiny Cars”) (e.g., a logo of the first car store's vendor (e.g., entity / company) that operates the first car store).

[0240] In some embodiments, seat user interface 762 includes a suggestion 762D of a developer (e.g., entity, company) that provides a simplified version application (e.g., creates and / or manages templates) that can be used to enable activities (e.g., buying and / or renting cars) associated with the first car store on computer system 700. In some embodiments, similar to FIG. 7AD, the developer (e.g., entity / company) that provides the simplified version application (and the corresponding full version application) also operates the first car store (e.g., “Shiny Cars”).

[0241] In some embodiments, the seat user interface 762 includes affordances 762E (e.g., selectable user interface objects, activatable user interface objects) 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, which application store can be used to download first-party and third-party applications to the computer system 700). In some embodiments, a full-version application equivalent to a simplified version application for enabling an activity (e.g., buying / renting a car) can be downloaded onto the computer system 700 from the application store (e.g., via affordances 762E of the seat user interface 762).

[0242] In some embodiments, the seat user interface 762 includes an affordance 762F (e.g., a selectable user interface object, an activatable user interface object) for hiding the seat user interface 762 (e.g., causing the computer system 700 to terminate the display) without performing an activity (e.g., ordering one or more menu items to the first table) associated with the first automobile store (e.g., “Shiny Cars”).

[0243] In FIG. 7AE, while displaying a seat user interface 762 that can be used to initiate an activity (e.g., buying / renting a car) associated with a first car store (e.g., “Shiny Cars”), computer system 700 detects (e.g., via the touch-sensitive surfaces of one or more input devices) activation 723 (e.g., user selection, user tap input) of affordance 762B.

[0244] 7AF, in response to detecting activation 723 of affordance 762B, pursuant to determining that a full version application (e.g., the full version of the “Shiny Cars” application) for enabling an activity (e.g., buying / renting a car) is not available (e.g., not installed), computer system 700 displays, via display generation component 702, a simplified user interface 764 corresponding to a simplified version application (e.g., the simplified version “Car Store” application) for enabling an activity (e.g., buying / renting a car). In some embodiments, if the simplified version application was not installed on computer system 700 (e.g., because this is the first time the simplified version “Shiny Cars” application is accessed), computer system 700 (e.g., in response to detecting activation 723 of affordance 762B) automatically (e.g., without user input, without user authentication) and installs the simplified version application (e.g., before and / or while displaying simplified user interface 764).

[0245] In some embodiments, simplified user interface 764 differs (e.g., has a different layout) from simplified user interface 736 first described with reference to Figure 7S because simplified user interface 764 and simplified user interface 736 are operated by different developers (e.g., different entities, different companies). In some embodiments, the layout and / or structure of each simplified version application is configurable (e.g., freely) by the respective developers (e.g., respective entities, respective companies) for each application.

[0246] 7AF, in some embodiments, simplified user interface 764 includes a search area 766 for initiating a search on a simplified version application corresponding to simplified user interface 764 (e.g., to search for a car to purchase or rent). In some embodiments, simplified user interface 764 includes a map area 768 that includes a map showing the location of car stores and / or the location of the car being searched for. In some embodiments, simplified user interface 764 includes a filter area 770 that includes multiple filters that can be applied to a given search.

[0247] 7AG-7AL illustrate a method (e.g., a search-based method) for initiating the process of enabling an activity on computer system 700 without using a corresponding full version application on computer system 700 (e.g., because the full version application is not installed on computer system 700).

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

[0249] In some embodiments, while displaying search user interface 772, computer system 700 detects (e.g., receives) input 778 (e.g., via input area 776, e.g., via a microphone). In the example user interface shown in Figure AH, input 778 corresponds to a search for coffee shops.

[0250] 7AH , in response to detecting (e.g., receiving) an input 778 corresponding to a search for coffee shops, computer system 700 displays, within search user interface 772, a first results region 780 including a plurality of search results 780A-780C corresponding to different light-weight version applications associated with input 778. In some embodiments, at least a portion of the plurality of search results 780A-780C correspond to light-weight version applications that are already installed (e.g., (currently) in use, accessed) on computer system 700. In some embodiments, at least a portion of the plurality of search results 780A-780C correspond to different light-weight version applications that are not installed (e.g., not accessed) on computer system 700.

[0251] In FIG. 7AI, while displaying search user interface 772 showing first results region 780, computer system 700 detects (e.g., via the touch-sensitive surface of one or more input devices) user selection 725 of first search result 780A corresponding to a second cafe (or user selection of an affordance corresponding to first search result 780A, etc.).

[0252] In FIG. 7AJ, in response to detecting a user selection 725 of a first search result 780A corresponding to a second cafe, the computer system 700 displays, via the display generation component 702 (e.g., overlaid on a portion of the search user interface 772), a seating user interface 784 corresponding to the second cafe. In some embodiments, the seating user interface 784 is similar to (e.g., has the same layout / structure, provides a consistent experience with) the seating user interface 706 first described with reference to FIG. 7B, the seating user interface 734 first described with reference to FIG. 7Q, the seating user interface 752 first described with reference to FIG. 7X, and the seating user interface 762 first described with reference to FIG. 7AE. In FIG. 7B, the seating user interface 706 is associated with enabling an activity (e.g., ordering) based on a detected respective location (e.g., detecting that the computer system 700 is at the first restaurant). In FIG. 7Q, the seating user interface 734 is associated with enabling an activity (e.g., renting) based on a detected (e.g., received) selection of a respective location from a map application. In Figure 7X, seat user interface 752 is associated with enabling an activity (e.g., ordering) based on identification information detected (e.g., received) from an external device (e.g., a contactless wireless terminal) (e.g., via NFC, by scanning a QR code). In Figure 7AD, seat user interface 762 is associated with enabling an activity (e.g., purchasing, renting) based on a link selected (e.g., from a web page), where the activity is related to content associated with the link. In Figure 7AJ, seat user interface 784 is associated with enabling an activity (e.g., ordering) based on a selection from search results.

[0253] In some embodiments, the seat user interface 784 includes an information area 784A that includes the name of the second cafe (e.g., "Cafe Mocha"), address and / or branch information for the second cafe, and an affordance 784B (e.g., a selectable user interface object, an activatable user interface object) that, when activated, initiates a process (e.g., purchase, rental) that enables an activity related to the second cafe.

[0254] In some embodiments, the seat user interface 784 includes an image 784C showing a second cafe (e.g., "Cafe Mocha") (e.g., a logo of the second cafe and of the vendor (e.g., entity / company) operating the second cafe).

[0255] In some embodiments, the seat user interface 784 displays a suggestion 784D of a developer (e.g., entity, company) that provides a simplified version application (e.g., creates and / or manages templates) that can be used to enable an activity associated with the second cafe (e.g., ordering one or more menu items). In some embodiments, similar to FIG. 7AJ, the developer (e.g., entity / company) that provides the simplified version application (and the corresponding full version application) is the same (e.g., same entity, same company) as the vendor associated with the second cafe (e.g., "Cafe Mocha").

[0256] In some embodiments, seat user interface 784 includes affordances 784E (e.g., selectable user interface objects, activatable user interface objects) for accessing an application store (e.g., an application store controlled and managed by the developer of the operating system of computer system 700, which application store can be used to download first-party and third-party applications to computer system 700). In some embodiments, a full version application corresponding to a simplified version application for enabling an activity (e.g., ordering one or more menu items) can be downloaded onto computer system 700 from the application store (e.g., via affordances 784E of user interface 784).

[0257] In some embodiments, the seat user interface 784 includes an affordance 784F (e.g., a selectable user interface object, an activatable user interface object) for hiding the seat user interface 784 (e.g., causing the computer system 700 to terminate the display) without performing an activity (e.g., ordering one or more menu items) associated with the second cafe (e.g., “Cafe Mocha”).

[0258] In FIG. 7AK, while displaying a seat user interface 784 that can be used to initiate an activity (e.g., ordering one or more menu items) associated with a second cafe (e.g., “Cafe Mocha”), computer system 700 detects (e.g., via the touch-sensitive surface of one or more input devices) activation 727 (e.g., user selection, user tap input) of affordance 784B.

[0259] 7AL , in response to detecting activation 727 of affordance 784B, in accordance with a determination that a full version application (e.g., the full version of the “Cafe Mocha” application) for enabling an activity (e.g., ordering one or more menu items) is not available (e.g., not installed) on computer system 700, computer system 700 displays, via display generation component 702, simplified user interface 786 of a simplified version application (e.g., the simplified version of the “Cafe Mocha” application) for enabling an activity (e.g., ordering one or more menu items). In some embodiments, if the simplified version application is not installed on computer system 700 (e.g., because this is the first time the simplified version “Cafe Mocha” application is accessed), computer system 700 (e.g., in response to detecting activation 727 of affordance 784B) automatically (e.g., without user input, without user authentication) and installs the simplified version application (e.g., before and / or while displaying simplified user interface 786).

[0260] In some embodiments, simplified user interface 786 is provided by a different developer, and therefore simplified user interface 786 differs (e.g., is structurally different, has a different layout) from simplified user interface 716 first described with reference to FIG. 7K and simplified user interface 754 first described with reference to FIG. 7Z. As shown in FIG. 7AL, in some embodiments, simplified user interface 784 includes location information 788 (e.g., an address) of the second cafe. In some embodiments, simplified user interface 786 includes a menu area 790 that includes multiple selectable menu items that can be ordered at the second cafe. In some embodiments, simplified user interface 786 includes affordances 792 (e.g., selectable user interface objects, activatable user interface objects) for ordering / checking the selected menu items.

[0261] 7AL, in some embodiments, simplified user interface 786 includes a user interface object 794 (e.g., a banner, a platter) (e.g., similar to user interface object 724 described above with reference to FIG. 7K) that is displayed concurrently with (e.g., overlaid on) a portion of simplified user interface 786. In some embodiments, user interface object 794 is displayed along with the display of simplified user interface 786 and is displayed for a predetermined period of time (e.g., 10 seconds, 30 seconds, 1 minute). In some embodiments, user interface object 794 includes a suggestion 794A (e.g., text information) of a developer (e.g., an entity, a company) that provides a simplified version application corresponding to simplified user interface 786 (e.g., creating and / or managing templates). In some embodiments, user interface object 794 includes a sharing affordance 794B for initiating a process for sharing the simplified version application corresponding to simplified user interface 786 with a different user (e.g., sending an electronic communication to a different user's different computer system that includes the simplified version application and / or a method for initiating download of the simplified version application).

[0262] 7AM illustrates computer system 700 displaying home user interface 796 (a user interface including one or more application icons corresponding to applications installed on computer system 700, a user interface controlled by the operating system of computer system 700) via display generation component 702. In FIG. 7AM, home user interface 796 includes multiple application icons 798A-798I corresponding to full-version applications available (e.g., installed) on computer system 700.

[0263] 7AN illustrates a computer system 700 that displays, via a display generation component 702, a home user interface 796 that includes a plurality of application icons 798A-798I corresponding to respective full version applications and simplified application icons corresponding to simplified version applications available (e.g., installed) on the computer system 700. In the example user interface illustrated in FIG. 7AN, the home user interface 796 includes a first simplified application icon 799A corresponding to a first simplified version application (e.g., "Cafe Mocha"), a second simplified application icon 799B corresponding to a second simplified version application (e.g., the "Food Review" simplified version application for "Coffee Shop"), a third simplified application icon 799C corresponding to a third simplified version application (e.g., "Bike 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., the "Food Review" simplified version application for "Burger Queen"). As shown in FIG. 7AN, in some embodiments, simplified application icons 799A-799E corresponding to installed simplified version applications are displayed within and accessible from the same user interface (e.g., home user interface 796) as application icons corresponding to full version (regular) applications installed on computer system 700.

[0264] In some embodiments, as also shown in FIG. 7AN, the simplified application icons include a first visual indicator (e.g., 799AA of simplified application icon 799A) indicating that the respective simplified application icon corresponds to a simplified version application (e.g., a first indicia (e.g., having an image and / or text indicator) indicating that the respective simplified application icon corresponds to a simplified version application (instead of a full version application). In some embodiments, the first visual indicator (e.g., the first indicia) is included in a first predetermined location (e.g., the lower left corner) of the respective simplified application icon. In some embodiments, as shown in FIG. 7AN, the simplified application icons include a second visual indicator (e.g., 799AB of simplified application icon 799A) (e.g., a second indicia (e.g., showing a number)) indicating the number of notifications generated by and / or currently available for the respective simplified version application (e.g., unchecked notifications). In some embodiments, the second visual indicator (e.g., the second indicia) is included in a second predetermined location (e.g., the upper right corner) of the respective simplified application icon.

[0265] 7AO illustrates a computer system 700 displaying, via display generation component 702, a home user interface 796 including application icons 798A-798I, where home user interface 796 also includes a folder icon 797 for the simple application icons. In some embodiments, the simple application icons (e.g., simple application icons 799A-799E of FIG. 7AN) are included within a folder corresponding to folder icon 797 displayed on home user interface 796 (e.g., instead of being included directly in home user interface 796). In FIG. 7AO, folder icon 797 includes representations (e.g., thumbnail images) of the simple application icons 799A-799E.

[0266] In some embodiments, similar to the simplified application icons, folder icon 797 includes a first visual indicator 797A (e.g., a first indicia (e.g., having an image and / or a text indicator)) that indicates that the folder icon corresponds to a folder for a simplified version application (instead of a full version application). In some embodiments, first visual indicator 797A (e.g., the first indicia) is included in a first predetermined location (e.g., the lower left corner) of the respective simplified application icon. In some embodiments, folder icon 797 includes a second visual indicator 797B (e.g., a second indicia (e.g., showing a number)) that indicates the (e.g., total) number of notifications (e.g., unchecked notifications) generated by and / or currently available for each simplified version application included in the folder corresponding to folder icon 797. In some embodiments, second visual indicator 797B (e.g., the second indicia) is included in a second predetermined location (e.g., the upper right corner) of folder icon 797.

[0267] FIG. 7AP illustrates a computer system 700 displaying, via a display generation component 702, a user selection 729 of a folder icon 797 displayed within a home user interface 796.

[0268] In FIG. 7AQ, in response to detecting a user selection 729 of a folder icon 797, the computer system 700 displays, via a display generation component 702 (e.g., overlaid on a portion of the home user interface 796), a folder user interface 795 (e.g., a popup) including simplified application icons 799A-799E first described with reference to FIG. 7AN.

[0269] As shown in FIG. 7AQ, in some embodiments, similar to simplified application icons, folder user interface 795 includes a first visual indicator 795A (e.g., a first indicia (e.g., having an image and / or text indicator)) indicating that folder user interface 795 corresponds to a folder for simplified version applications (instead of full version applications). In some embodiments, first visual indicator 795A (e.g., a first indicia) is included in a first predetermined location (e.g., the lower left corner) of each simplified application icon. In some embodiments, folder user interface 795 includes a second visual indicator 795B (e.g., a second indicia (e.g., showing a number)) that indicates the (e.g., total) number of notifications (e.g., unchecked notifications) generated by and / or currently available for each simplified version application displayed in folder user interface 795 via simplified application icons 799A-799E. In some embodiments, a second visual indicator 795B (eg, a second indicia) is included in a second predefined location (eg, the upper right corner) of the folder user interface 795.

[0270] FIG. 7AR shows computer system 700 displaying, via display generation component 702 (e.g., after displaying folder user interface 795 including simplified application icons 799A-799E), a simplified user interface 793 corresponding to simplified application icon 799E from FIG. 7AQ (e.g., corresponding to a simplified version of the "Food Review" application for "Burger Queen") (e.g., in response to detecting activation (e.g., user selection, user tap input) of simplified application icon 799E of FIG. 7AQ).

[0271] 7AS illustrates computer system 700 displaying folder user interface 795 after displaying (e.g., accessing) the stripped-down version application for “Burger Queen” of FIG. 7AR via display generation component 702. In FIG. 7AS, in contrast to FIG. 7AQ, stripped-down application icon 799E (e.g., corresponding to the stripped-down version application for “Burger Queen”) is moved to be the first stripped-down application icon listed in folder user interface 795 (e.g., because the corresponding stripped-down version application was most recently accessed / displayed by computer system 700).

[0272] FIG. 7AT shows a computer system 700 displaying, via a display generation component 702, a simplified user interface 793 corresponding to the simplified application icon 799E from FIG. 7AS after displaying a folder user interface 795 (e.g., in response to detecting activation (e.g., user selection, user tap input) of the simplified application icon 799E of FIG. 7AS).

[0273] In FIG. 7AT, while displaying simplified user interface 793, computer system 700 detects input 731 (e.g., a swipe input, a swipe up input on the bottom region of display generating component 702) (e.g., via the touch-sensitive surface of one or more input devices).

[0274] In FIG. 7AV, in response to detecting input 731 (shown in FIG. 7AU), computer system 700, via display generation component 702, displays a multitasking user interface 791 that includes multiple user interface cards corresponding to portions of the most recently displayed user interface.

[0275] In FIG. 7AV, computer system 700 displays, in multitasking user interface 791, user interface card 789 (e.g., user interface preview image, view of application) corresponding to simplified user interface 793 from FIG. 7AU (the most recently displayed (e.g., accessed) user interface), user interface card 787 corresponding to an application store (the second most recently displayed (e.g., accessed) user interface), and user interface card 785 corresponding to a simplified user interface of a simplified version application of a different type (e.g., developed by a different developer (e.g., a different entity, a different company)) than the simplified version application (e.g., a “Bike Rental” simplified version application) (the third most recently displayed (e.g., accessed) user interface) corresponding to user interface 793; and because user interface card 789 corresponds to the most recently displayed (e.g., accessed) user interface, user interface card 789 is the first user interface card shown (e.g., the topmost displayed user interface card).

[0276] 7AW illustrates computer system 700 displaying, via display generation component 702 (e.g., after displaying multitasking user interface 791 of FIG. 7AV), simplified user interface 783 corresponding to a simplified version application of the same type (e.g., developed by the same developer (e.g., the same entity)) as a simplified version application (e.g., the “Food Review” simplified version application) corresponding to simplified user interface 793 of FIG. 7AV. Simplified user interface 783 of FIG. 7AW corresponds to a simplified user interface of a first vendor (e.g., a coffee shop called “Cafe Mocha”), which is using a corresponding simplified version application developed by a first developer (e.g., a first entity or first company called “Food Review”), and simplified user interface 793 of FIG. 7AU corresponds to a simplified user interface of a second vendor (e.g., a restaurant called “Burger Queen”), which is using a corresponding simplified version application developed by the same first developer.

[0277] 7AX illustrates computer system 700 displaying multitasking user interface 791 via display generation component 702 (e.g., (shortly after) displaying simplified user interface 783, and without displaying a different user interface for a different application). As shown in FIG. 7AX, because simplified user interface 783 of FIG. 7AW was the most recently displayed user interface, multitasking user interface 791 includes user interface card 781 corresponding to simplified user interface 783 of FIG. 7AW as the most recently displayed (e.g., accessed) user interface. In some embodiments, as shown in FIG. 7AX, multitasking user interface 791 includes user interface card 789 corresponding to simplified user interface 793, the previous most recently displayed (e.g., accessed) user interface, as the second most recently displayed (e.g., accessed) user interface. In some embodiments, computer system 700 maintains within multitasking user interface 791 the display of two different user interface cards from different vendors, both corresponding to the same type of simplified version application (e.g., both corresponding to the “Food Review” simplified version application). As shown in FIG. 7AX, multitasking user interface 791 includes user interface card 787 as the third most recently displayed (eg, accessed) user interface.

[0278] 7AY illustrates computer system 700 displaying multitasking user interface 791 via display generation component 702 (e.g., (shortly after) displaying simplified user interface 783, and without displaying different user interfaces for different applications). As shown in FIG. 7AY, because simplified user interface 783 of FIG. 7AW was the most recently displayed user interface, multitasking user interface 791 includes user interface card 781 corresponding to simplified user interface 783 of FIG. 7AW as the most recently displayed user interface. In some embodiments, when simplified version applications of the same type are displayed (e.g., accessed), even if for different vendors (e.g., "Cafe Mocha" vs. "Burger Queen"), computer system 700 removes the display of user interface cards for each user interface corresponding to the same simplified version application, but excludes the display of the different vendors that were included in multitasking user interface 791. For example, in Figure 7AY, because simplified user interface 783 corresponding to the same simplified version application (e.g., the "Food Reviews" simplified version application) was accessed more recently, multitasking user interface 791 does not include user interface card 789 corresponding to simplified user interface 793. Instead, in Figure 7AQ, multitasking user interface 791 includes, after user interface card 781 corresponding to simplified user interface 783, user interface 787 corresponding to the second most recently displayed (e.g., accessed) application and user interface card 785 corresponding to the third most recently displayed (e.g., accessed) application.

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

[0280] In FIG. 7AZ, in response to detecting a user selection 733 of a user interface card 787, computer system 700, via display generation component 702, displays a user interface 779 corresponding to an application store. In some embodiments, computer system 700 displays a first page 777 (e.g., a search page, a search tab) within application store user interface 779 that includes one or more suggested (e.g., recommended) applications. In some embodiments, full version applications that correspond to simplified version applications installed on and / or displayed / accessed via computer system 700 are suggested (e.g., recommended) for download via the application store. For example, in FIG. 7AZ, first page 777 of application store user interface 779 includes a first app suggestion 775A that corresponds to a full version application equivalent of the simplified version application corresponding to simplified user interface 783 of FIG. 7AW (e.g., the “Food Reviews” full version application equivalent to the “Food Reviews” simplified version application). In some embodiments, as shown in FIG. 7AZ, the first app suggestion 775A includes an affordance 775B (e.g., a selectable user interface object, an activatable user interface object) that, when activated, initiates a process for downloading and installing the respective full version application on the computer system 700.

[0281] 8A-8B are flow diagrams illustrating a method for invoking an activity associated with a camera application using a computer system, according to some embodiments. Method 800 is performed in 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) in communication 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 of method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0282] As described below, method 800 provides an intuitive way to enable activities using a computer system. This method reduces the cognitive burden on a user of enabling activities using a computer system, thereby creating a more efficient human-machine interface. For battery-powered computing devices, allowing a user to enable activities more quickly and efficiently conserves power and increases the time between battery charges.

[0283] A computer system (e.g., 700) detects (802) (e.g., via one or more location sensors in communication with the computer system, such as a GPS sensor) the occurrence of a trigger condition (e.g., scanning a QR code, detecting an NFC signal, detecting a hyperlink selection, detecting / determining the presence of the computer system near a location beacon, detecting / determining the presence of the computer system at a particular geographic location) to initiate an activity (e.g., making a reservation, placing an order, booking, making a payment, making a request) associated with a first application (e.g., an application corresponding to a retailer, store, restaurant, and / or service provider).

[0284] In response to detecting (804) the occurrence of a trigger condition, the computer system (e.g., 700) displays (806) via a display generating component (e.g., 702) (e.g., overlaid on a wake screen user interface (e.g., 704), overlaid on a desktop or home screen user interface, overlaid on another application user interface) a first user interface (e.g., 706, 734, 752, 762, 784) (e.g., an intermediate user interface, a sheet 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 is still visible on the display, a pop-up user interface). In some embodiments, the home user interface 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 that includes links (e.g., affordances for launching or accessing) to applications, settings, and / or notifications.

[0285] In some embodiments, in response to detecting the occurrence of a trigger condition, and pursuant to determining that the first application is not available (e.g., not downloaded, not installed, not stored, cannot be launched or accessed) on the computer system (e.g., 700), the computer system (e.g., 700) displays or causes the display of the first user interface without obtaining (e.g., downloading, installing) the first application.

[0286] 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, and an indication or logo associated with a company offering or enabling the activity) (808) and a first selectable user interface object (e.g., 706B, 734B, 752B, 762B, 784B) (e.g., a first affordance, a first selectable button) for taking an action associated with the activity (e.g., making a reservation, making an appointment, booking, making a purchase) (810). In some embodiments, the first selectable user interface object includes an indication of a type of activity available (e.g., text information such as “reservation,” “booking,” “payment,” etc.). Displaying the first user interface in response to detecting a trigger condition allows a user to recognize that a computer system will be used to perform the activity and to quickly and easily access the activity on the computer system. By performing an optimized action when a set of conditions is met without requiring further user input, the operability of the computer system is improved, the user-system interface is made more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and, in addition, by allowing the user to use the device more quickly and efficiently, power usage is reduced and battery life of the computer system is improved.

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

[0288] In response to detecting 818 the activation (e.g., 701, 717, 719, 723, 727) of a first selectable user interface object (e.g., 706B, 734B, 752B, 762B, 784B) and following a determination 820 that the first application is unavailable (e.g., not downloaded, not installed, not stored, unable to be launched, or not accessible) on the computer system (e.g., 700), the computer system, via the display generation component (e.g., 702), displays 822 a second user interface (e.g., 716, 736, 754, 764, 786) (e.g., a user interface of a simplified version application associated or related to the full version application) configured to perform an activity without downloading at least a portion of the first application (e.g., without obtaining the first application, without downloading a full version of the application). In some embodiments, the second user interface is configured to perform an activity of downloading a simplified version of the first application (e.g., instead of downloading the full version of the first application). In some embodiments, the simplified version of the first application is smaller (e.g., requires less memory) than a comparable full version application of the first application. In some embodiments, the simplified version of the first application is faster to download and access, and requires fewer memory resources for storage and access (e.g., therefore, is faster to load and launch on a respective computer system) than the comparable full version application. In some embodiments, the simplified version of the first application enables a subset (e.g., not all) of the features (e.g., functionality) of the comparable full version application.In accordance with determining that the first application is not available on the computer, displaying a second user interface configured to perform an activity without downloading at least a portion of the first application provides a user with quick and easy access to features of the first application for performing an activity, even when at least a portion of the first application is not available on the computer system and there is no need to download the first application (e.g., a full version) to the computer system. Performing an optimized operation when a set of conditions is met without requiring further user input improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0289] In some embodiments, displaying the second user interface (e.g., 716, 736, 754, 764, 786) includes displaying the second user interface without requiring authentication information (e.g., biometric authentication information (e.g., fingerprint authentication information, facial authentication information, retina / iris recognition information), passcode or password authentication information) to authenticate display of the second user interface (824). In some embodiments, authentication (e.g., via biometric authentication, via passcode / password authentication) is not required for the computer system to display (e.g., cause display of) the second user interface in response to detecting activation of the first selectable user interface object (e.g., even if the first selectable user interface object is displayed within a (e.g., superimposed) lock screen or wake screen of the computer system (e.g., 700). Displaying the second user interface without requiring authentication information to authenticate display of the second user interface provides quick access to features of the second user interface without requiring additional input. Improves the operability of the computer system by reducing the number of inputs required to perform operations, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0290] In some embodiments, pursuant to determining that the first application is unavailable (e.g., not downloaded, not installed, not stored, unable to be launched, or not accessible) on the computer system (e.g., 700), the computer system initiates (e.g., automatically, without requesting user permission) a process for downloading (e.g., and installing) on ​​the computer system software configured to perform an activity that does not include at least a portion of the first application (e.g., a simplified version application of the first application instead of a full version application of the first application, the version of the first application configured to perform the activity without at least a portion of the first application) (826). In some embodiments, the computer system initiates (e.g., automatically, without requesting user permission) the process for downloading the software when this is the first time the first application has been invoked on the computer system (e.g., based on a detected trigger condition) and therefore the first application is unavailable on the computer system. In some embodiments, the computer system, while displaying the first user interface, downloads software onto the computer system configured to perform an activity that does not include at least a portion of the first application (e.g., a simplified version of the first application). In some embodiments, the computer system, in response to detecting activation of the first selectable user interface object, downloads software onto the computer system configured to perform an activity that does not include at least a portion of the first application (e.g., a simplified version of the first application). In accordance with determining that the first application is not available on the computer system, initiating (e.g., automatically, without user input) a process of downloading (e.g., and installing) software onto the computer system configured to perform an activity that does not include at least a portion of the first application allows a user to access the first application without having to manually download the first application onto the computer system. Reducing the number of inputs required to perform operations improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0291] In some embodiments, in response to detecting 818 the activation (e.g., 701, 717, 719, 723, 727) of a first selectable user interface object (e.g., 706B, 734B, 752B, 762B, 784B) and in accordance with determining 828 that the first application is available (e.g., downloaded, installed, stored, launched, or accessible) on the computer system (e.g., 700), the computer system, via the display generation component (e.g., 702), displays 830 a third user interface, the third user interface (e.g., a user interface of a full version of the first application) being a user interface of the first application configured to perform an activity. Displaying the third user interface, the third user interface being a user interface of the first application configured to perform an activity in accordance with determining that the first application is available on the computer system, allows a user to quickly and easily access (e.g., all) of the features of the first application. Performing an action when a set of conditions is met without requiring further user input improves the operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by allowing the user to use the device more quickly and efficiently.

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

[0293] In some embodiments, displaying the first user interface (e.g., 706, 734, 752, 762, 784) includes displaying the first user interface over (e.g., overlaid on) (e.g., a portion, but not all, of) a background user interface (e.g., overlaid on) the first user interface (e.g., overlaid on a previously displayed user interface, overlaid on a wake screen user interface (e.g., 704), overlaid on a desktop or home screen user interface) (812). Displaying the first user interface over (e.g., overlaid on) the background user interface allows a user to simultaneously view the first user interface and at least a portion of the displayed background user interface. Providing additional control of the computer system without cluttering the UI with additional displayed controls improves usability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0294] In some embodiments, the first user interface (e.g., 706, 734, 752, 762, 784) or the second user interface (e.g., 716, 736, 754, 764, 786) includes information related to (e.g., identifying, identifying, describing) the activity (e.g., call-based information (e.g., a particular branch of a store or restaurant, a table number within a restaurant, an object identifier (e.g., an object number such as a bicycle number), vendor-specific information)), which is determined based on the detected trigger condition (832). In some embodiments, pursuant to a determination that the detected 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 a particular geographic location) is a first type of trigger condition, the computer system, via a display generation component, displays or causes a display of first information (e.g., vendor-specific information) based on the detected trigger condition. In some embodiments, pursuant to determining that the detected 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 a particular geographic location) is a second type of trigger condition that is different from the first type of trigger condition, the computer system (e.g., 700) displays or causes the display of second information (e.g., vendor-specific information) based on the detected trigger condition that is different from the first information. By providing information related to the activity in the first user interface or the second user interface, where the information is determined based on the detected trigger condition, a user can quickly and easily view information related to the activity and thus efficiently perform the activity using the computer system.By providing improved feedback, the computer system's operability is improved, the user-system interface is made more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and, in addition, the user can use the computer system more quickly and efficiently, thereby reducing power usage and improving the computer system's battery life.

[0295] In some embodiments, the method of any one of items 1 to 7, wherein the detected trigger condition includes activation (e.g., user selection) of a link (e.g., a displayed hyperlink, a message, an app, or a link displayed on a webpage / website). Displaying a first user interface (e.g., 706, 734, 752, 762, 784) in response to detecting the trigger condition, wherein the detected trigger condition includes activation of a link, allows the user to quickly and easily view information about how the user can perform and efficiently access activities using the computer system. Performing an optimized action when a set of conditions is met without requiring further user input improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0296] In some embodiments, the detected trigger condition includes the detection of a physical object (e.g., an object detectable via an NFC connection, a QR code or barcode detectable / scannable using the computer system (e.g., 700)) (e.g., via NFC or other wireless communication, via scanning a QR or barcode using a camera or other sensor to detect visual information). Displaying a first user interface (e.g., 706, 734, 752, 762, 784) in response to detecting the trigger condition, where the detected trigger condition includes the detection of a physical object, allows a user to quickly and easily view information about how the computer system can be used to perform and conveniently access activities. Performing optimized actions when a set of conditions is met without requiring further user input improves the operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves the battery life of the computer system by allowing users to use the device more quickly and efficiently.

[0297] In some embodiments, the detected trigger condition includes detecting that a computer system (e.g., 700) is at a respective (e.g., nearby, proximate) location (e.g., a location-based determination that the computer system is at a particular location where an activity may be performed (e.g., at a particular restaurant, at a particular store) using location from a point of interest in a map application, geographic information about the computer system or broadcast beacons, and / or other computer system location techniques such as WiFi triangulation). In response to detecting the trigger condition, a first user interface (e.g., 706, 734, 752, 762, 784) is displayed, and the detected trigger condition, by detecting that the computer system is at the respective location, enables a user to recognize that the computer system may be used to perform an activity and may provide quick and easy access to the activity on the computer system. By performing an optimized action when a set of conditions is met without requiring further user input, the operability of the computer system is improved, the user-system interface is made more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and, in addition, by allowing the user to use the device more quickly and efficiently, power usage is reduced and battery life of the computer system is improved.

[0298] In some embodiments, the detected trigger condition includes initiating a search (e.g., using a general-purpose search function of the computer system) performed on the computer system (e.g., 700). In some embodiments, the computer system, via a display generation component (e.g., 702), displays search results (as shown at 772) of a search (e.g., a search for restaurants, stores, vehicles, etc.) performed on the computer system. In some embodiments, the detected trigger condition includes detecting a user selection of a particular search result from multiple displayed search results. By displaying a first user interface (e.g., 706, 734, 752, 762, 784) in response to detecting the trigger condition, where the detected trigger condition includes initiating a search performed on the computer system, the user can quickly and easily view information about how they can perform activities and efficiently access activities using the computer system. By performing an optimized action when a set of conditions is met without requiring further user input, the operability of the computer system is improved, the user-system interface is made more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and, in addition, by allowing the user to use the device more quickly and efficiently, power usage is reduced and battery life of the computer system is improved.

[0299] In some embodiments, following displaying the second user interface (e.g., 716, 736, 754, 764, 786), the computer system (e.g., 700), via the display generation component (e.g., 702), displays a home user interface (e.g., 796) (e.g., a home screen or one or more screens / pages of the home screen, the operating system-controlled main user interface of the computer system) that includes a plurality of application user interface objects (app icons) corresponding to respective applications available (e.g., downloaded, installed) on the computer system, where the home user interface does not include an application user interface object for launching the second user interface (e.g., does not include any of the one or more screens / pages of the home screen).

[0300] In some embodiments, the home user interface (e.g., 796) includes one or more screens or pages that include multiple application user interface objects (e.g., 798A-798I) (e.g., app icons). In some embodiments, no application user interface object for launching a second user interface (e.g., 716, 736, 754, 764, 786) is included in any of the one or more screens or pages of the home user interface.

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

[0302] In some embodiments, the home user interface (e.g., 796) does not include application user interface objects (e.g., app icons) corresponding to applications for which a first version (e.g., a simplified version) of the respective application is available on the computer system (e.g., 700), but a second version (e.g., a full version) of the respective application is not available on the computer system. In some embodiments, the home user interface only includes application user interface objects (e.g., 798A-798I) (e.g., app icons) corresponding to applications for which a second version (e.g., a full version) of the respective application is available on the computer system.

[0303] In some embodiments, following displaying the second user interface (e.g., 716, 736, 754, 764, 786), the computer system (e.g., 700), via the display generation component (e.g., 702), displays a home user interface (e.g., 796) (e.g., a home screen, an operating system-controlled main user interface of the computer system) that includes a second selectable user interface object (e.g., 797) (e.g., a folder, a menu). In some embodiments, while displaying the second selectable user interface object (e.g., 797), the computer system (e.g., 700) detects activation (e.g., 729) (e.g., selection) of the second selectable user interface object via one or more input devices. In some embodiments, in response to detecting activation (e.g., 729) of a second selectable user interface object (e.g., 797), the computer system (e.g., 700), via the display generation component (e.g., 702), displays (e.g., in a user interface corresponding to a folder (e.g., a temporary folder) for an app icon corresponding to a first version (e.g., a simplified version) of the application to be downloaded onto the computer system) an application user interface object (e.g., 799A-799E) (e.g., an app icon) for launching a second user interface (e.g., 716, 736, 754, 764, 786). In some embodiments, in response to detecting activation (e.g., selection) of an application user interface object (e.g., an app icon) for launching a second user interface (e.g., 716, 736, 754, 764, 786), the computer system (e.g., 700), via the display generation component (e.g., 702), displays or causes to be displayed the second user interface.In some embodiments, the application user interface object (e.g., 799A-799E) (e.g., app icon) for launching the second user interface includes an indication (e.g., indicia) that the application user interface object corresponds to a first version (e.g., a lite version) of the first application (e.g., as opposed to a second version (e.g., a full version) of the first application). Displaying the application user interface object (e.g., an app icon) for launching the second user interface in response to detecting activation of a second selectable user interface object included within the home user interface allows a user to quickly and easily launch the second user interface from the home user interface. Reducing the number of inputs required to perform operations improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and additionally reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0304] In response to detecting activation of the second selectable user interface object, in accordance with a determination that a predetermined period of time (e.g., one day, one week, two weeks, one month, three months, six months, one year) has elapsed since the second user interface was accessed (e.g., launched and displayed) on the computer system, the computer system (e.g., 700), via the display generation component (e.g., 702), ceases displaying the application user interface object (e.g., app icon) for launching the second user interface (e.g., 716, 736, 754, 764, 786) (e.g., in a user interface corresponding to a folder (e.g., a temporary folder) for the app icon corresponding to the first version (e.g., simplified version) of the application downloaded onto the computer system).

[0305] In some embodiments, the application user interface object for launching 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 response to detecting activation of the second selectable user interface object, the computer system removes (e.g., deletes) the (e.g., corresponding, necessary) software for launching the second user interface in accordance with a determination that a predetermined period of time (e.g., one day, one week, two weeks, one month, three months, six months, one year) has elapsed since the second user interface was accessed (e.g., activated and displayed) on the computer system. Removing the software for launching the second user interface from the computer system (e.g., automatically, without user input) in accordance with a determination that a predetermined period of time has elapsed since the second user interface was accessed on the computer system frees up storage on the computer system that was used by software that may no longer be accessed by a user on the computer system. Performing an action when a set of conditions is met without requiring further user input improves the operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0306] In some embodiments, while a first application process corresponding to a second user interface (e.g., 716, 736, 754, 764, 786) is currently being used on the computer system (e.g., 700) (e.g., active (e.g., in the background), e.g., currently running (e.g., in the background)), the computer system, via the display generation component (e.g., 702) (e.g., within a multitasking user interface, within a multitasking screen), displays a plurality of user interface preview items corresponding to the application currently being used on the computer system (e.g., user interface objects representing launched applications currently active and / or running (e.g., in the background) on the computer system, one preview item including an image of the (current instance of) the user interface for the corresponding application), wherein the plurality of user interface preview items includes the first user interface preview item corresponding to the second user interface. In some embodiments, in response to detecting that the first application process corresponding to the second user interface is no longer active (e.g., closed), the computer system no longer includes the first user interface preview item in the plurality of user interface preview items. Including a first user interface preview item corresponding to a second user interface within the plurality of user interface preview items provides the user with quick and easy access to the second user interface, improving usability of the computer system by providing additional control options for the computer system without cluttering the UI with additional displayed controls, making the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reducing power usage and improving battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0307] In some embodiments, a first application process corresponding to a second user interface (e.g., 716, 736, 754, 764, 786) and a second application process corresponding to a second user interface may be in use on a computer system (e.g., 700) while both are currently in use (e.g., both are active (e.g., in the background), both are currently running (e.g., in the background)), where the first application process corresponds to a first instance of the second user interface (e.g., a second user interface launched at a first time, at a first location, and / or in association with a first object), and the second application process The instance corresponds to a second instance of a second user interface (e.g., a second user interface launched at a second time, at a second location, and / or in association with a second object), and the computer system displays (e.g., within a multitasking user interface, within a multitasking screen) via a display generation component (e.g., 702) a plurality of user interface preview items, the plurality of user interface preview items including a first user interface preview item corresponding to the first instance of the second user interface and a second user interface preview item corresponding to the second instance of the second user interface.

[0308] In some embodiments, following displaying the second user interface (e.g., 716, 736, 754, 764, 786) configured to perform an activity without downloading at least a portion of the first application, the computer system (e.g., 700), via the display generation component (e.g., 702), displays an application store user interface (e.g., a user interface for an application store in which applications can be searched for and application downloads can be initiated). In some embodiments, the computer system simultaneously displays within the application store user interface a third selectable user interface object (e.g., an affordance, a selectable download button) that, when activated, initiates a process for downloading the first application to the computer system, and an indication (e.g., description) of how, when, and / or where the second user interface was used (e.g., accessed, launched) on the computer system. In the application store user interface, by simultaneously displaying a third selectable user interface object that, when activated, initiates a process for downloading a first application onto a computer system and an indication that a second user interface has been used on the computer system, the application store user interface allows a user to easily recognize that a second user interface has been used on the computer system while still allowing the first application (e.g., associated with the second user interface) to be efficiently downloaded.Providing improved visual feedback improves the operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and also reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0309] In some embodiments, while displaying the second user interface (e.g., 716, 736, 754, 764, 786), the computer system (e.g., 700) displays a user interface element (e.g., a banner area or notification area within the second user interface) within the second user interface that includes a suggestion that the first application can be downloaded to the computer system (e.g., via an application store). In some embodiments, the suggestion includes a download user interface object (e.g., a download affordance) that, when activated (e.g., selected), initiates a process of downloading the first application onto the computer system. Displaying a user interface element while displaying the second user interface that includes a suggestion that the first application can be downloaded onto the computer system allows a user to quickly and easily recognize that an application corresponding to or associated with the displayed user interface, i.e., the first application, can be downloaded onto the computer system. Providing improved visual feedback improves the operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and also reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0310] In some embodiments, the user interface element (e.g., 724, 762, 784) (e.g., a banner area or notification area in the second user interface) further includes a fourth selectable user interface object (e.g., an affordance, a selectable share button) that, when activated, initiates a process (e.g., a share process) that enables a second computer system (different from the computer system) to access (e.g., display) the second user interface to perform an activity without downloading at least a portion of the first application to the second computer system. In some embodiments, the user interface element (e.g., a notification, a banner-style notification) is temporarily displayed such that the computer system ceases displaying the user interface element after a predetermined period of time (e.g., 10 seconds, 30 seconds, 1 minute) has elapsed since the user interface element was displayed. The inclusion of a fourth selectable user interface object (e.g., an affordance, a selectable shareable button) that, when activated, initiates a process (e.g., a shareable process) that enables a second computer system (different from the computer system) to access a second user interface to perform an activity without downloading at least a portion of the first application to the second computer system effectively allows a user to cause the second computer system to perform an activity with less input, improving usability of the computer system by reducing the number of inputs required to perform an action, making the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and, in addition, reducing power usage and improving battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0311] In some embodiments, an application process corresponding to a second user interface (e.g., 716, 736, 754, 764, 786) is enabled (e.g., permitted) to cause the display of a notification that includes information related to performing an activity. In some embodiments, while an application process corresponding to a second user interface is active (e.g., running (e.g., in the background), launched (e.g., in the background)) on a computer system (e.g., 700), the computer system can display (or cause the display of) a notification related to performing an activity using the computer system.

[0312] In some embodiments, the second user interface (e.g., 716, 736, 754, 764, 786, 793) corresponds to software configured to perform an activity (e.g., a simplified version of the first application, a version of the first application configured to perform an activity without at least a portion of the first application). In some embodiments, in response to detecting activation of the first selectable user interface object (e.g., 706B, 734B, 752B, 762B, 784B), the computer system (e.g., 700) sets one or more system privileges for the software to include permission to generate a notification (e.g., 748, 1399) on the computer system for a predetermined period (e.g., limited duration) (e.g., 8 hours, 12 hours, until the end of the current day). Setting one or more system privileges for software to include permission to generate notifications on a computer system for a predetermined period of time (e.g., automatically, without further user input) allows the software to provide functionality (provide notifications related to performing activities) on the computer system for a reasonable period of time when the notifications by the software are most useful to the user of the computer system, thereby enabling the user to utilize the software in a more efficient manner, while disabling the software from providing notifications after the period has elapsed prevents the computer system from unnecessarily consuming power and further improves the battery life of the computer system.

[0313] In some embodiments, detecting activation of the first selectable user interface object occurs at a first time. In some embodiments, 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 criteria for generating a notification, detecting / determining the presence of a computer system near a location beacon, detecting / determining the presence of a computer system near a location beacon, detecting / determining the presence of a computer system at a particular geographic location) corresponding to a second application (e.g., an application corresponding to 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 an activity without at least a portion of the first application). In some embodiments, in response to detecting the occurrence of the notification event, the computer system displays, via the display generation component (e.g., 702), a notification (e.g., 748, 1399) (e.g., a push notification, a prompt) corresponding to the detected notification event in accordance with a determination that the second time is within a predetermined period of time from the first time (e.g., within 8 hours of the first time, within 12 hours of the first time, within the same day as the first time). In some embodiments, in response to detecting the occurrence of the notification event, in accordance with a determination that the second time is not within a predetermined period of time from the first time (e.g., more than 8 hours from the first time, more than 12 hours from the first time, after the day on which the first time occurred) (e.g., as shown via the right depiction of computer system 700 in FIG. 13V), the computer system ceases displaying, via the display generation component, the notification corresponding to the detected notification event.Displaying or canceling the display of a notification corresponding to the detected notification event based on whether the second time is within a predetermined period of time from the first time is designed to avoid allowing applications that are not full version applications and (unlike full version applications) to temporarily use unnecessarily extended access to functionality that generates notifications, which improves system security by avoiding granting unnecessary access to system privileges and reduces power consumption by software, which in turn reduces power usage and improves battery life of the computer system.

[0314] In some embodiments, the predetermined period of time is based on the amount of time that has elapsed since a predetermined type of user interaction was detected for the second application (e.g., an application corresponding to simplified user interface 716, 736, 754, 764, 786, 793) (e.g., a predetermined amount of time since the second application was last displayed via a display generation component of the computer system). By automatically setting the predetermined period of time during which notifications are allowed based on the detected user interaction with the second application, the computer system can generate relevant notifications corresponding to the second application that are useful to the user, while still allowing the computer system to cease generating notifications corresponding to the second application after the user has stopped using the second application (e.g., a predetermined period of time has elapsed since the user last interacted with the second application). Automatically providing useful information (via notifications) for a predetermined period of time in response to detecting user interaction with the second application reduces the number of inputs required to perform an action, improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and allows the user to use the computer system more quickly and efficiently, thereby reducing power usage and improving battery life of the computer system. Furthermore, refusing the second application to generate further notifications after the user has stopped using the second application avoids granting unnecessary access to system privileges, improving system security by reducing power consumption by the software, thereby reducing power usage and improving battery life of the computer system.

[0315] In some embodiments, while a first application (e.g., an application corresponding to user interface 708, an application corresponding to user interface 1348, an 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 application), an event related to an activity performed by the software, detecting / determining the presence of the computer system near a location beacon, detecting / determining the presence of the computer system at a particular geographic location). In some embodiments, in response to detecting the occurrence of the second notification event, pursuant to a determination that one or more system privileges for the first application include permission to generate notifications (e.g., as in FIGS. 13I-13J), the computer system, via a display generation component (e.g., 702), generates a notification for the detected notification event. 13S) (e.g., because permission has been denied by the user), the computer system, via the display generation component, ceases displaying the notification corresponding to the detected second notification event. Detecting the notification event increases security by allowing the first application to generate a notification if the one or more system privileges for the first application include permission to generate a notification, and by preventing the first application from generating a notification if the one or more system privileges for the first application do not include permission to generate a notification, thus making use of the computer system safer by allowing the first application to perform tasks consistent with its system privileges while preventing the first application from performing tasks inconsistent with its system privileges.

[0316] It should be noted that the process details described above with respect to method 800 (e.g., FIGS. 8A-8B) equally apply to the methods described below. For example, method 1000 optionally includes any one or more of the characteristics of the various methods described above with reference to method 800. For example, the respective simplified user interfaces displayed on the respective computers via processes for enabling activity on the respective computer systems initiated based on any one or more of the methods described with reference to FIGS. 7A-7AZ may include customized content based on information received or detected from the initiation process. In another example, method 1200 optionally includes any one or more of the characteristics of the various methods described above with reference to method 800. For example, the respective simplified user interfaces displayed on the respective computer systems via processes for enabling activity on the respective computer systems initiated based on any one or more of the methods described with reference to FIGS. 7A-7AZ may be accessed and / or managed (e.g., again) on the respective computer systems via the methods described with reference to FIGS. 11A-11S. In another example, method 1400 optionally includes any one or more of the characteristics of the various methods described above with respect to method 800. For example, the process for setting one or more system privileges for an application described with reference to Figures 13A-13V may be applied to software corresponding to a user interface configured to perform an activity without downloading at least a portion of the application, as described with reference to Figures 7A-7AZ. For the sake of brevity, these details will not be repeated below.

[0317] 9A-9T show exemplary user interfaces for customizing displayed content based on the situation (e.g., context) in which the content is invoked, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 10A-10C.

[0318] 9A-9E show exemplary user interfaces for customizing displayed content based on location (e.g., customizing content for different vendors using applications from the same developer).

[0319] 9A illustrates computer system 700 displaying, via display generating component 702, a user interface 904 corresponding to a wake screen (e.g., a lock screen) for computer system 700. In some embodiments, the wake screen is a user interface that is displayed when the display generating 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 that is displayed when the computer system is operating in a locked state, where at least some functionality of the computer system is limited (e.g., until the computer system is unlocked).

[0320] The computer system 700 detects (e.g., via one or more location sensors (e.g., GPS sensors)) that the computer system is at (e.g., has entered) a location corresponding to a first vendor (e.g., a first restaurant) (e.g., while displaying the user interface 904, while displaying a different user interface, or while the display generation component 702 is in an off state).

[0321] 9B , in response to computer system 700 detecting that it is in a location corresponding to a first vendor (e.g., a first restaurant called "Food King"), computer system 700 displays seating user interface 906. In some embodiments, seating user interface 906 is similar to (e.g., has the same layout / structure, provides a consistent experience with) seating user interface 706 first described with reference to FIG. 7B , seating user interface 734 first described with reference to FIG. 7Q , seating user interface 752 first described with reference to FIG. 7X , seating user interface 762 first described with reference to FIG. 7AE , and seating user interface 784 first described with reference to FIG. 7AJ .

[0322] As shown in FIG. 9B , in some embodiments, the seat user interface 906 includes an information area 908, which includes name information 908A of a first vendor (e.g., “Food King”) and location information 908B of the first vendor (e.g., the address of the first vendor).

[0323] In some embodiments, seat user interface 906 includes affordance 910 (e.g., a selectable, activatable user interface object) that, when activated, initiates a process to enable an activity on computer system 700 associated with a first vendor (e.g., "Food King") (e.g., ordering one or more menu items, such as food or drinks, from the first vendor). In some embodiments, affordance 910 indicates (e.g., includes text information) a type of activity (e.g., ordering one or more menu items, such as food or drinks, from the first vendor) associated with the first vendor (e.g., "Food King").

[0324] In some embodiments, the sheet user interface 906 includes an image 912 depicting a first vendor (eg, "Food King") (eg, the first vendor's logo for the first vendor's store).

[0325] In some embodiments, the seat user interface 906 includes a suggestion 914 of a first developer (e.g., an entity, company) providing (e.g., developing, creating, and / or managing templates) an application (e.g., a simplified / partial version of an application for which a corresponding full / regular version is available) that can be used to enable an activity (e.g., ordering a menu item such as food or drink) associated with a first vendor, where the application (hereinafter referred to as the “simplified version application”) is based on a portion (but not all) of the first developer’s equivalent full version application. In some embodiments, as in FIG. 9B , the application is provided by a first developer (e.g., “Food Reviews”) that is different (e.g., a different entity) from the first vendor (e.g., “Food King”). In some embodiments, a developer can provide an application platform for use by multiple different vendors, and the application can be customized for each vendor for which the application platform is used. In some embodiments, the application is developed by a second developer (e.g., the first vendor itself) that is the same (e.g., the same entity) as the first vendor (e.g., “Food King”).

[0326] In some embodiments, the sheet user interface 906 includes affordances 916 (e.g., selectable user interface objects, activatable user interface objects) 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, which application store can be used to download first-party and third-party applications to the computer system 700).

[0327] In some embodiments, the seat user interface 906 includes an affordance 918 (e.g., a selectable user interface object, an activatable user interface object) for hiding the seat user interface 906 (e.g., causing the computer system 700 to terminate the display) without performing an activity (e.g., ordering a menu item such as food or drink) associated with the first vendor (e.g., “Food King”).

[0328] In FIG. 9B, while displaying sheet user interface 906, computer system 700 detects activation 901 (e.g., user selection, user tap input) of affordance 910 (e.g., via the touch-sensitive surface of one or more input devices).

[0329] 9C , in response to detecting activation 901 of affordance 910 (e.g., in response to displaying a loading screen as described above with reference to FIGS. 7H-7J ), in accordance with determining that a corresponding full version application of the first developer's (e.g., “Food Reviews”) simplified version application is not installed (e.g., not installed) on computer system 700, computer system 700, via display generation component 702, displays simplified user interface 920 of the first vendor (e.g., “Food King”), the simplified application being provided by the first developer (e.g., “Food Reviews”). In some embodiments, if the first developer's (e.g., “Food Reviews”) simplified version application is not available (e.g., not installed) on computer system 700 when activation 901 of affordance 910 is detected, computer system 700 automatically (e.g., without user input) downloads and installs the simplified version application corresponding to the first developer (e.g., “Food Reviews”) in response to detecting activation 901 of affordance 910.

[0330] As shown in FIG. 9C , in some embodiments, simplified user interface 920 includes information 922 (e.g., including the address of the first vendor) of a first vendor (e.g., “Food King”) that corresponds to first vendor location information 908B (e.g., the address of the first vendor) included in seat user interface 906.

[0331] In some embodiments, simplified user interface 920 includes a vendor-customized menu area 924 that includes one or more menu items (e.g., food and / or drinks) offered by a first vendor (e.g., “Food King”).

[0332] In some embodiments, simplified user interface 920 includes affordances 926 (eg, selectable user interface objects, activatable user interface objects) for ordering / checking selected menu items.

[0333] In some embodiments, simplified user interface 920 includes a user interface object 928 (e.g., a banner, a platter) that is displayed simultaneously with simplified user interface 920 (e.g., overlaid on a portion of simplified user interface 920). In some embodiments, user interface object 928 is displayed along with the display of simplified user interface 928 and is displayed for a predetermined period of time (e.g., 10 seconds, 30 seconds, 1 minute; computer system 700 ceases displaying user interface object 920 after a non-zero predetermined period of time). In some embodiments, user interface object 928 includes suggestions 928A (e.g., text information) of a first developer (e.g., "Food Reviews") corresponding to the application. In some embodiments, user interface object 928 includes a sharing affordance 928B for initiating a process for sharing a simplified version application corresponding to simplified user interface 920 with a different user (e.g., sending an electronic communication to a different user's different computer system that includes a portion of the application (e.g., the simplified version application) and / or instructions for downloading a portion of the application (e.g., the simplified version application)).

[0334] 9D shows computer system 700 displaying, via display generation component 702, user interface 904 on a wake screen (e.g., lock screen) of computer system 700. In FIG. 9D, in response to computer system 700 detecting that it is in a location corresponding to a second vendor (e.g., a second restaurant called "Burger Queen"), computer system 700 displays sheet user interface 930 provided by the same first developer (e.g., "Food Reviews") (e.g., and therefore shares the same layout / structure as sheet user interface 906).

[0335] As shown in FIG. 9D , in some embodiments, similar to the seat user interface 906 corresponding to the first vendor, the seat user interface 930 includes an information area 932, which includes name information 932A of the second vendor (e.g., “Burger Queen”) and location information 932B of the second vendor (e.g., the address of the second vendor).

[0336] In some embodiments, similar to seat user interface 906 corresponding to a first vendor, in some embodiments seat user interface 930 includes an affordance 934 (e.g., a selectable user interface object, an activatable user interface object) that, when activated, initiates a process to enable an activity on computer system 700 associated with a second vendor (e.g., "Burger Queen") (e.g., ordering one or more menu items, such as food or drinks, from the second vendor). In some embodiments, affordance 934 indicates (e.g., includes text information) a type of activity (e.g., ordering one or more menu items, such as food or drinks, from the second vendor) associated with the second vendor (e.g., "Burger Queen").

[0337] In some embodiments, similar to the seat user interface 906 corresponding to the first vendor, in some embodiments, the seat user interface 930 includes an image 936 representing the second vendor (e.g., "Burger Queen") (e.g., the second vendor's logo for the second vendor's store).

[0338] In some embodiments, similar to the seat user interface 906 corresponding to the first vendor, the seat user interface 930 includes a suggestion 938 of a first developer (e.g., “Food Reviews”) providing an application (e.g., developing, creating, and / or managing templates) that enables an activity (e.g., ordering one or more menu items, such as food or beverages) related to a second vendor (e.g., “Burger Queen”).

[0339] In some embodiments, similar to the sheet user interface 906 corresponding to the first vendor, in some embodiments the sheet user interface 930 includes affordances 940 (e.g., selectable user interface objects, activatable user interface objects) 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, which application store can be used to download first-party and third-party applications to the computer system 700).

[0340] In some embodiments, similar to the seat user interface 906 corresponding to the first vendor, in some embodiments, the seat user interface 930 includes an affordance 942 (e.g., a selectable user interface object, an activatable user interface object) for hiding the seat user interface 930 (e.g., causing the computer system 700 to terminate the display) without performing an activity (e.g., ordering one or more menu items, such as food or drinks) associated with the second vendor (e.g., "Burger Queen").

[0341] In FIG. 9D , while displaying seat user interface 930, computer system 700 detects activation 903 (e.g., user selection, user tap input) of affordance 934 (e.g., via the touch-sensitive surface of one or more input devices).

[0342] In FIG. 9E, in response to detecting activation 903 of affordance 934 (e.g., in response to displaying a loading screen as described above with reference to FIGS. 7H-7J), computer system 700, via display generation component 702, displays simplified user interface 944 of a second vendor (e.g., "Burger Queen"), where simplified user interface 944 is provided by the same simplified version application of the first developer (e.g., "Food Reviews") that provided simplified user interface 920 described above with reference to FIG. 9C.

[0343] In some embodiments, both simplified user interface 920 for a first vendor (e.g., "Food King") and simplified user interface 944 for a second vendor (e.g., "Burger Queen") are provided by the same simplified version application corresponding to a first developer (e.g., "Food Reviews"), so that simplified user interface 944 shares a similar layout / structure as simplified user interface 920, but simplified user interface 920 includes information customized for the first vendor (e.g., "Food King") and simplified user interface 944 includes information customized for the second vendor (e.g., "Burger Queen").

[0344] As shown in FIG. 9E , in some embodiments, simplified user interface 944 includes information 946 (e.g., including the address of the second vendor) of a second vendor (e.g., “Burger Queen”) that corresponds to second vendor location information 932B (e.g., the address of the second vendor) included in seat user interface 930.

[0345] In some embodiments, simplified user interface 944 includes a vendor-customized menu area 948 that includes one or more menu items (e.g., food and / or drinks) offered by a second vendor (e.g., "Burger Queen").

[0346] In some embodiments, simplified user interface 944 includes affordances 950 (eg, selectable user interface objects, activatable user interface objects) for ordering / checking selected menu items.

[0347] In some embodiments, simplified user interface 944 includes a user interface object 952 (e.g., a banner, a platter) that is displayed simultaneously with simplified user interface 944 (e.g., overlaid on a portion of simplified user interface 944). In some embodiments, user interface object 952 is displayed along with the display of simplified user interface 944 and is displayed for a predetermined period of time (e.g., 10 seconds, 30 seconds, 1 minute; computer system 700 ceases displaying user interface object 952 after the non-zero predetermined period of time). In some embodiments, user interface object 952 includes suggestions 952A (e.g., text information) of a first developer (e.g., "Food Reviews") that correspond to the application. In some embodiments, user interface object 952 includes a sharing affordance 952B for initiating a process for sharing a simplified version application corresponding to simplified user interface 944 with a different user (e.g., sending an electronic communication to a different user's different computer system that includes a portion of the application (e.g., the simplified version application) and / or instructions for downloading the portion of the application (e.g., the simplified version application)).

[0348] 9F-9M show exemplary user interfaces for customizing displayed content based on object identification (e.g., table number, object number) information, where the object identification information is obtained by computer system 700 via an NFC connection (or alternatively, via a QR code, etc.), and where different object identification information (e.g., different table numbers, different object numbers) are from the same vendor (e.g., the same restaurant, the same store, the same company).

[0349] FIG. 9F illustrates computer system 700 in communication with a wireless communication terminal 954 (e.g., an NFC terminal) (e.g., while displaying a wake screen user interface 904 via display generation component 904), where terminal 954 corresponds to a first table (e.g., table 8) at a third vendor (e.g., “Cafe Mocha”).

[0350] In FIG. 9J, computer system 700 receives (eg, detects) from terminal 954 identification information corresponding to a first table (eg, table 8) at a third vendor (eg, "Cafe Mocha").

[0351] 9G, in response to receiving the identification information from terminal 954, computer system 700 displays (e.g., overlaid on user interface 904) via display generation component 702 a seat user interface 956 provided by a second developer (e.g., "Cafe Mocha"), which is the same (e.g., same entity, same company) as a third vendor (e.g., "Cafe Mocha"). In some embodiments, seat user interface 956 is similar to (e.g., shares the same layout / structure with) seat user interface 920 of FIG. 9B and seat user interface 944 of FIG. 9D.

[0352] 9G , in some embodiments, seat user interface 956 includes information area 958, which includes name information 958A of a third vendor (e.g., "Cafe Mocha") and location information 958B of the third vendor (e.g., the address of the third vendor). In some embodiments, seat user interface 956 includes in information area 958 identification information 958C (e.g., a first table number (e.g., table 8)) that corresponds to identification information (e.g., a table number, an object number) received from terminal 954.

[0353] In some embodiments, seat user interface 956 includes affordance 960 (e.g., a selectable, activatable user interface object) that, when activated, initiates a process to enable an activity on computer system 700 associated with a third vendor (e.g., "Cafe Mocha") (e.g., ordering one or more menu items, such as coffee or other beverages, from the third vendor). In some embodiments, affordance 960 indicates (e.g., includes text information) a type of activity (e.g., ordering one or more menu items, such as coffee or other beverages, from the third vendor) associated with the third vendor (e.g., "Cafe Mocha").

[0354] In some embodiments, the seat user interface 956 includes an image 962 showing a third vendor (eg, "Cafe Mocha") (eg, the third vendor's logo for the third vendor's store).

[0355] In some embodiments, the seat user interface 956 includes a suggestion 964 of a second developer (e.g., "Cafe Mocha") that provides an application (e.g., develops, creates, and / or manages templates) that enables an activity (e.g., ordering one or more menu items, such as coffee or other beverages) associated with the third vendor (e.g., "Cafe Mocha"). In FIG. 9G, the second developer is the same (e.g., same entity, same company) as the third vendor (e.g., "Cafe Mocha").

[0356] In some embodiments, the sheet user interface 956 includes affordances 966 (e.g., selectable user interface objects, activatable user interface objects) 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, which application store can be used to download first-party and third-party applications to the computer system 700).

[0357] In some embodiments, the seat user interface 956 includes an affordance 968 (e.g., a selectable user interface object, an activatable user interface object) for hiding the seat user interface 956 (e.g., causing the computer system 700 to terminate the display) without performing an activity (e.g., ordering one or more menu items such as coffee or other beverages) associated with the third vendor (e.g., “Cafe Mocha”).

[0358] In FIG. 9H, while displaying seat user interface 956, computer system 700 detects activation 905 (e.g., user selection, user tap input) of affordance 960 (e.g., via the touch-sensitive surface of one or more input devices).

[0359] 9I , in response to detecting activation 905 of affordance 960 (e.g., in response to displaying a loading screen as described above wi...

Claims

1. 1. A method comprising:

1. A computer system in communication with one or more input devices, comprising: Detecting an occurrence of a trigger condition for initiating an activity associated with the first application; While the first application is not installed on the computer system, installing on the computer system a second application configured to perform the activity based on the detected trigger condition without downloading at least a portion of the first application; setting one or more system privileges for the second application; installing the first application on the computer system after setting the one or more system privileges of the second application; After installing the first application on the computer system, setting one or more system privileges for the first application based on the one or more system privileges for the second application pursuant to a determination that the second application was installed on the computer system when installation of the first application occurred; setting the one or more system privileges for the first application based on default system privileges in accordance with a determination that the second application was not installed on the computer system when installation of the first application occurred; A method comprising:

2. The method of claim 1 , wherein the one or more system privileges for the second application exclude allowing permanent access to location information.

3. 3. The method of claim 1, wherein the one or more system privileges for the second application include a first type of permission and exclude a second type of permission that is different from the first type of permission.

4. the one or more system privileges for the second application Allowing access to the camera, Allowing access to the microphone, Bluetooth access permission, or Allow location access The method of claim 1 , further comprising one or more of the following:

5. setting the one or more system privileges for the first application based on the default system privileges; setting the one or more system privileges for the first application to include a denial of permission to access location information in accordance with a determination that the one or more system privileges for the second application include an indication that permission to access location information is denied; deactivating permission to access location information for the first application in response to a determination that the one or more system privileges for the second application include an indication that permission to access location information has been granted; and The method of any one of claims 1 to 4, comprising:

6. After the first application is installed and the second application is given permission to access location information, Detecting an occurrence of a condition in which the first application has use of location information; in response to the first application detecting the occurrence of the condition having use of location information; displaying a request for permission to access location information by the first application in accordance with a determination that the one or more system privileges for the second application do not include the indication that permission to access location information is denied; and The method of claim 5 , comprising:

7. A computer program product causing a computer to carry out the method according to any one of claims 1 to 6.

8. 1. A computer system comprising:

8. A computer system comprising: a memory having stored thereon a computer program according to claim 7; and one or more processors capable of executing the computer program stored in said memory, said computer system being configured to communicate with one or more input devices. Computer system.

9. 1. A computer system configured to communicate with one or more input devices, comprising: Means for carrying out the method according to any one of claims 1 to 6 A computer system comprising:

Images