CN110554880B

CN110554880B - Setup program for electronic device

Info

Publication number: CN110554880B
Application number: CN201811143102.3A
Authority: CN
Inventors: T·L·巴尔萨莫
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2018-06-03
Filing date: 2018-09-28
Publication date: 2024-03-15
Anticipated expiration: 2038-09-28
Also published as: WO2019236412A1; CN110554880A

Abstract

The invention provides a setup program for an electronic device. In some embodiments, an electronic device may guide a user to first set the device or set the device after a factory reset. In some embodiments, an electronic device facilitates suggesting and installing applications on the electronic device during device setup. In some embodiments, the electronic device facilitates the transmission of settings and information from another electronic device during device settings.

Description

Setup program for electronic device

Technical Field

This document relates generally to setup procedures for electronic devices, and interactions with such devices by a user during this period.

Background

In recent years, user interaction with electronic devices has been significantly enhanced. These devices may be devices such as computers, tablets, televisions, multimedia devices, mobile devices, etc.

In some cases, such devices may guide a user to first set up the device or set up the device after a factory reset. Enhancing these programs and user interactions with the device improves the user's use experience with the device and reduces user interaction time, which is particularly important where the input device is battery powered.

Disclosure of Invention

Some embodiments described in this disclosure relate to one or more electronic devices that suggest and install applications on an electronic device and transmit settings and information from another electronic device during device setup. A full description of the embodiments is provided in the accompanying drawings and detailed description, and it is to be understood that the summary of the invention provided above is not in any way limiting the scope of the disclosure.

Drawings

For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the accompanying drawings in which like reference numerals designate corresponding parts throughout the figures thereof.

Fig. 1A is a block diagram illustrating a multifunction device with a touch-sensitive display in accordance with some embodiments of the present disclosure.

Fig. 1B is a block diagram illustrating exemplary components for event processing according to some embodiments of the present disclosure.

Fig. 2 illustrates a multi-function device with a touch screen according to some embodiments of the present disclosure.

Fig. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments of the present disclosure.

Fig. 4 illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface separate from a display in accordance with some embodiments of the present disclosure.

Fig. 5A-5B illustrate block diagrams of exemplary architectures for devices according to some embodiments of the present disclosure.

Fig. 6A-6 GG illustrate an exemplary manner in which an electronic device facilitates suggesting and installing applications on the electronic device during device setup according to some embodiments of the present disclosure.

Fig. 7A-7J are flowcharts illustrating methods of facilitating suggestion and installation of applications on an electronic device during device setup according to some embodiments of the present disclosure.

Fig. 8A-8 DD illustrate an exemplary manner in which an electronic device facilitates transmitting settings and information from another electronic device during device setup according to some embodiments of the present disclosure.

Fig. 9A-9F are flowcharts illustrating methods of facilitating transmission of settings and information from another electronic device during device settings, according to some embodiments of the present disclosure.

Detailed Description

In the following description of the embodiments, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific embodiments which may be optionally practiced. It is to be understood that other embodiments may be optionally employed and structural changes may be optionally made without departing from the scope of the disclosed embodiments. Furthermore, although the following description uses the terms "first," "second," etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another element. For example, a first touch may be named a second touch and similarly a second touch may be named a first touch without departing from the scope of the various described embodiments. Both the first touch and the second touch are touches, but they are not the same touch.

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

Depending on the context, the term "if" is optionally interpreted to mean "when …", "at …" or "in response to a determination" or "in response to detection". Similarly, the phrase "if determined …" or "if detected [ stated condition or event ]" is optionally interpreted to mean "upon determining …" or "in response to determining …" or "upon detecting [ stated condition or event ]" or "in response to detecting [ stated condition or event ]" depending on the context.

Exemplary apparatus

Herein describeEmbodiments of electronic devices, user interfaces for such devices, and related processes for using such devices. 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 the portable multifunction device include, but are not limited to, those from Apple inc (Cupertino, california)Device, iPod->Device, and->An apparatus. Other portable electronic devices, such as a laptop or tablet computer having a touch-sensitive surface (e.g., a touch screen display and/or a touchpad), are optionally used. It should also be appreciated that in some embodiments, the device is not a portable communication device, but rather a desktop computer or television having a touch-sensitive surface (e.g., a touch screen display and/or a touch pad). In some embodiments, the device does not have a touch screen display and/or a touch pad, but is capable of outputting display information (such as the user interface of the present disclosure) for display on a separate display device and is capable of receiving input information from a separate input device having one or more input mechanisms (such as one or more buttons, a touch screen display, and/or a touch pad). In some embodiments, the device has a display, but is capable of receiving input information from a separate input device having one or more input mechanisms, such as one or more buttons, a touch screen display, and/or a touch pad.

In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and/or joystick. Additionally, as noted above, it should be understood that the described electronic devices, displays, and touch-sensitive surfaces are optionally distributed among two or more devices. Thus, as used in this disclosure, information displayed on or by an electronic device is optionally used to describe information output by the electronic device for display on a separate display device (touch-sensitive or non-touch-sensitive). Similarly, as used in this disclosure, input received on an electronic device (e.g., touch input received on a touch-sensitive surface of the electronic device) is optionally used to describe input received on a separate input device from which the electronic device receives input information.

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

The various applications executing on the device optionally use at least one generic physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and/or changed for different applications and/or within the respective applications. In this way, the common physical architecture of the devices (such as the touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and transparent to the user.

Attention is now directed to embodiments of portable or non-portable devices having touch sensitive displays, but the device need not include a touch sensitive display or a general display, as described above. Fig. 1A is a block diagram illustrating a portable or non-portable multifunction device 100 with a touch-sensitive display 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience and is sometimes referred to as or called a touch-sensitive display system. Device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripheral interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input or control devices 116, and external ports 124. The apparatus 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

As used in the present specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of the contact on the touch-sensitive surface (e.g., finger contact), or to an alternative to the force or pressure of the contact on the touch-sensitive surface (surrogate). The intensity of the contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of the contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure forces at different 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 contact force. Similarly, the pressure-sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area and/or its variation detected on the touch-sensitive surface, the capacitance of the touch-sensitive surface in the vicinity of the contact and/or its variation and/or the resistance of the touch-sensitive surface in the vicinity of the contact and/or its variation are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, surrogate measurements of contact force or pressure are directly used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to surrogate measurements). In some implementations, an alternative measurement of 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). The intensity of the contact is used as an attribute of the user input, allowing the user to access additional device functions that are not otherwise accessible to the user on a smaller sized device of limited real estate for displaying affordances and/or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical/mechanical control, such as a knob or button).

As used in this specification and in the claims, the term "haptic 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 a centroid of the device, to be detected by a user with a user's feel. For example, in the case where the device or component of the device is in contact with a surface that is sensitive to touch by a user (e.g., a finger, palm, or other portion of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a haptic sensation that corresponds to a perceived change in a physical characteristic of the device or component of the device. For example, a touch-sensitive surface (e.g., a touch-sensitive display or touch pad) is optionally interpreted by a user as a "press click" or "click-down" of a physically actuated button. In some cases, the user will feel a tactile sensation, such as "press click" or "click down", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement is not moved. As another example, movement of the touch-sensitive surface may optionally be interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when the smoothness of the touch-sensitive surface is unchanged. While such interpretation of touches by a user will be limited by the user's individualized sensory perception, many sensory perceptions of touches are common to most users. Thus, when a haptic output is described as corresponding to a particular sensory perception of a user (e.g., "click down", "roughness"), unless stated otherwise, the haptic output generated corresponds to a physical displacement of the device or component thereof that would generate the described sensory perception of a typical (or ordinary) user.

It should be understood that the device 100 is only one example of a portable or non-portable multifunction device, and that the device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in fig. 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application specific integrated circuits. Furthermore, the various components shown in fig. 1A are optionally implemented on two or more devices; such as a display and audio circuitry on the display device, a touch-sensitive surface on the input device, and the rest of the components on the device 100. In such embodiments, the device 100 optionally communicates with a display device and/or an input device to facilitate operation of the system, as described in this disclosure, and various components described herein relating to display and/or input remain in the device 100, or are optionally included in the display and/or input device as appropriate.

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

Peripheral interface 118 may be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in the memory 102 to perform various functions of the device 100 and process data.

In some embodiments, peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

The RF (radio frequency) circuit 108 receives and transmits RF signals, also referred to as electromagnetic signals. The RF circuitry 108 converts/converts electrical signals to/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, and the like. RF circuitry 108 optionally communicates via wireless communication with networks such as the internet (also known as the World Wide Web (WWW)), intranets, and/or wireless networks such as cellular telephone networks, wireless Local Area Networks (LANs), and/or Metropolitan Area Networks (MANs), and other devices. The RF circuitry 108 optionally includes well-known circuitry for detecting Near Field Communication (NFC) fields, such as by short range communication radios. Wireless communications optionally use any of a variety of communication standards, protocols, and technologies including, but not limited to, global system for mobile communications (GSM), enhanced Data GSM Environment (EDGE), high Speed Downlink Packet Access (HSDPA), high Speed Uplink Packet Access (HSUPA), evolution, pure data (EV-DO), HSPA, hspa+, dual cell HSPA (DC-HSPDA), long Term Evolution (LTE), near Field Communications (NFC), wideband code division multiple access (W-CDMA), code Division Multiple Access (CDMA), time Division Multiple Access (TDMA), 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.11 ac), voice over internet protocol (VoIP), wi-MAX, email protocols (e.g., internet Message Access Protocol (IMAP) and/or Post Office Protocol (POP)), messages (e.g., extensible message handling and presence protocol (XMPP), protocols for instant messaging and presence using extended session initiation protocol (sime), messages and presence (IMPS), instant messaging and/or SMS (SMS) protocols, or any other suitable communications protocol not yet developed herein.

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

I/O subsystem 106 couples input/output peripheral devices on device 100, such as touch screen 112 and other input control devices 116, to peripheral interface 118. The I/O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from/transmit electrical signals to other input or control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click-type dials, and the like. In some alternative implementations, one or more input controllers 160 are optionally coupled to (or not coupled to) any of the following: a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g., 208 in fig. 2) optionally include an up/down button 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).

The rapid pressing of the push button optionally unlocks the touch screen 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. patent application Ser. No. 11/322,549 (i.e., U.S. patent No.7,657,849) entitled "Unlocking a Device by Performing Gestures on an Unlock Image," filed 12-23-2005, which is hereby incorporated by reference in its entirety. Long presses of a button (e.g., 206) optionally cause the device 100 to power on or off. The function of the one or more buttons is optionally customizable by the user. Touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

The touch sensitive display 112 provides an input interface and an output interface between the device and the user. As described above, the touch-sensitive and display operations of the touch-sensitive display 112 are optionally separated from each other such that the display device is used for display purposes, while the touch-sensitive surface (whether or not the display) is used for input detection purposes, and the components and functions described are modified accordingly. However, for brevity, the following description is provided with reference to a touch sensitive display. The display controller 156 receives electrical signals from and/or transmits electrical signals to the touch screen 112. Touch screen 112 displays visual output to a user. Visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively, "graphics"). In some embodiments, some or all of the visual output corresponds to a user interface object.

Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that receives input from a user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or interruption of the contact) on touch screen 112 and translate the detected contact into interactions with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touch screen 112. In one exemplary embodiment, the point of contact between touch screen 112 and the user corresponds to the user's finger.

Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, but in other embodiments other display technologies are used. Touch screen 112 and display controller 156 optionally detect contact and any movement or interruption thereof using any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In one exemplary embodiment, a projected mutual capacitance sensing technique is used, such as that from Apple inc (Cupertino, california) iPod/>And->Techniques for discovery.

The touch sensitive display in some implementations of touch screen 112 is optionally similar to the multi-touch sensitive touch pad described in the following U.S. patents: 6,323,846 (Westerman et al), 6,570,557 (Westerman et al) and/or 6,677,932 (Westerman et al) and/or U.S. patent publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, while touch sensitive touchpads do not provide visual output.

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

Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some implementations, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or appendage, such as a stylus, finger, or the like, to make contact with touch screen 112. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which may not be as accurate as stylus-based input due to the large contact area of the finger on the touch screen. In some embodiments, the device translates the finger-based coarse input into a precise pointer/cursor position or command for performing the action desired by the user.

In some embodiments, the device 100 optionally includes a touch pad (not shown) for activating or deactivating particular functions in addition to the touch screen. In some embodiments, the touch pad is a touch sensitive area of the device that, unlike the touch screen, does not display visual output. The touch pad is optionally a touch sensitive surface separate from the touch screen 112 or an extension of the touch sensitive surface formed by the touch screen.

The apparatus 100 also includes a power system 162 for powering the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating Current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., light Emitting Diode (LED)), and any other components associated with the generation, management, and distribution of power in portable or non-portable devices.

The apparatus 100 optionally further comprises one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to an optical sensor controller 158 in the I/O subsystem 106. The optical sensor 164 optionally includes a Charge Coupled Device (CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for still image and/or video image acquisition. In some embodiments, the optical sensor is located on the front of the device such that the user's image is optionally acquired for video conferencing while viewing other video conference participants on the touch screen display. In some implementations, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensors in the device housing) such that a single optical sensor 164 is used with the touch screen display for both video conferencing and still image and/or video image acquisition.

The apparatus 100 optionally further comprises one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 in the I/O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring force (or pressure) of a contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a surrogate for pressure information) from the environment. In some implementations, at least one contact intensity sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on a rear of the device 100 opposite a touch screen display 112 located on a front of the device 100.

The device 100 optionally further includes one or more proximity sensors 166. Fig. 1A shows a proximity sensor 166 coupled to the peripheral interface 118. Alternatively, the proximity sensor 166 is optionally coupled to the input controller 160 in the I/O subsystem 106. The proximity sensor 166 optionally performs as described in the following U.S. patent applications: 11/241,839, entitled "Proximity Detector In Handheld Device";11/240,788, entitled "Proximity Detector In Handheld Device";11/620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output";11/586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11/638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals," which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor is turned off and the touch screen 112 is disabled when the multifunction device is placed near the user's ear (e.g., when the user is making a telephone call).

The device 100 optionally further comprises one or more tactile output generators 167. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 in the I/O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components; and/or electromechanical devices 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 a device). The contact intensity sensor 165 receives haptic feedback generation instructions from the haptic feedback module 133 and generates a haptic output on the device 100 that can be perceived by a user of the device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112), and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., inward/outward of the surface of device 100) or laterally (e.g., backward and forward in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on a rear of the device 100 opposite a touch screen display 112 located on a front of the device 100.

The device 100 optionally further includes one or more accelerometers 168. Fig. 1A shows accelerometer 168 coupled to peripheral interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I/O subsystem 106. Accelerometer 168 optionally performs as described in the following U.S. patent publications: U.S. patent publication 20050190059, entitled "acception-based Theft Detection System for Portable Electronic Devices" and U.S. patent publication 20060017692, entitled "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer", both of which are incorporated herein by reference in their entirety. In some implementations, information is displayed in a portrait view or a landscape view on a touch screen display based on analysis of data received from one or more accelerometers. The device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to the accelerometer 168 for obtaining information about the position and orientation (e.g., longitudinal or lateral) of the device 100.

In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact/motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application program (or instruction set) 136. Furthermore, in some embodiments, memory 102 (fig. 1A) or 370 (fig. 3) stores device/global internal state 157, as shown in fig. 1A and 3. The device/global internal state 157 includes one or more of the following: an active application state indicating which applications (if any) are currently active; a display state indicating what applications, views, or other information occupy various areas of the touch screen display 112; sensor status, including information obtained from the various sensors of the device and the input control device 116; and location information regarding the location and/or pose of the device.

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

The communication module 128 facilitates communication with other devices through one or more external ports 124 and also includes various software components for processing data received by the RF circuitry 108 and/or the external ports 124. External port 124 (e.g., universal Serial Bus (USB), firewire, etc.) is adapted to be coupled directly to other devices or indirectly through 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 or similar to and/or compatible with a 30-pin connector used on an iPod (trademark of Apple inc.) device.

The contact/motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). The contact/motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining the strength of the contact (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has ceased (e.g., detecting a finger lift event or a contact break). The contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact optionally includes determining a velocity (magnitude), a speed (magnitude and direction), and/or an acceleration (change in magnitude and/or direction) of the point of contact, the movement of the point of contact being represented by a series of contact data. These operations are optionally applied to a single contact (e.g., one finger contact) or multiple simultaneous contacts (e.g., "multi-touch"/multiple finger contacts). In some embodiments, the contact/motion module 130 and the display controller 156 detect contact on the touch pad.

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

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

Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other displays, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphic" includes any object that may be displayed to a user, including without limitation text, web pages, icons (such as user interface objects including soft keys), digital images, video, animation, and the like.

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

Haptic feedback module 133 includes various software components for generating instructions for use by haptic output generator 167 to generate haptic output at one or more locations on device 100 in response to user interaction with device 100.

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

The GPS module 135 determines the location of the device and provides such information for use in various applications (e.g., to the phone 138 for location-based dialing, to the camera 143 as picture/video metadata, and to applications that provide location-based services such as weather desktops, page-on-the-ground desktops, and map/navigation desktops).

The application 136 optionally includes the following modules (or sets of instructions) or a subset or superset thereof:

contact module 137 (sometimes referred to as an address book or contact list);

a telephone module 138;

video conferencing module 139;

email client module 140;

an Instant Messaging (IM) module 141;

a fitness support module 142;

a camera module 143 for still and/or video images;

an image management module 144;

a video player module;

a music player module;

Browser module 147;

calendar module 148;

a desktop applet module 149, optionally including one or more of: weather desktop applet 149-1, stock desktop applet 149-2, calculator desktop applet 149-3, alarm desktop applet 149-4, dictionary desktop applet 149-5 and other desktop applets obtained by the user, and user created desktop applet 149-6;

a desktop applet creator module 150 for forming a user-created desktop applet 149-6;

search module 151;

a video and music player module 152 that incorporates the video player module and the music player module;

notepad module 153;

map module 154; and/or

An online video module 155.

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 replication.

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 optionally used to manage an address book or contact list (e.g., in application internal state 192 of contacts module 137 stored in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating a telephone number, email address, physical address, or other information with the name; associating the image with the name; classifying and classifying names; providing a telephone number or email address to initiate and/or facilitate communication via telephone 138, video conferencing module 139, email 140, or instant message 141; etc.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to input a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contact module 137, modify the entered telephone number, dial the corresponding telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephony module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants according to user instructions.

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

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

In conjunction with RF circuitry 108, touch screen 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, workout support module 142 includes executable instructions to create a workout (e.g., with time, distance, and/or calorie burn targets); communicate with a fitness sensor (exercise device); receiving fitness sensor data; calibrating a sensor for monitoring fitness; selecting and playing music for exercise; and displaying, storing and transmitting the fitness data.

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

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 includes executable instructions for: arrange, modify (e.g., edit), or otherwise manipulate, tag, delete, present (e.g., in a digital slide show or album), and store still images and/or video images.

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 includes executable instructions for browsing the internet (including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages) according to user instructions.

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 includes executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (e.g., calendar entries, to-do items, etc.) according to user instructions.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, desktop applet module 149 is a mini-application (e.g., weather desktop applet 149-1, stock market desktop applet 149-2, calculator desktop applet 149-3, alarm clock desktop applet 149-4, and dictionary desktop applet 149-5) or a mini-application created by a user (e.g., user created desktop applet 149-6) that is optionally downloaded and used by a user. In some embodiments, the desktop applet includes an HTML (hypertext markup language) file, a CSS (cascading style sheet) file, and a JavaScript file. In some embodiments, the desktop applet includes an XML (extensible markup language) file and a JavaScript file (e.g., yahoo.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, a desktop applet creator module 150 is optionally used by a user to create a desktop applet (e.g., to transfer a user-specified portion of a web page into the desktop applet).

In conjunction 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 to search memory 102 for text, music, sounds, images, videos, and/or other files that match one or more search criteria (e.g., one or more user-specified search terms) according to user instructions.

In conjunction with the touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, the video and music player module 152 includes executable instructions that allow a user to download and playback recorded music and other sound files stored in one or more file formats (such as MP3 or AAC files), as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on the touch screen 112 or on an external display connected via the external port 124). In some embodiments, the device 100 optionally includes the functionality of an MP3 player such as an iPod (trademark of Apple inc.).

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notepad module 153 includes executable instructions to create and manage notepads, backlog, and the like, according to user instructions.

In conjunction with RF circuitry 108, touch screen 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 optionally configured to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data related to shops and other points of interest at or near a particular location, and other location-based data) according to user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions for: allowing a user to access, browse, receive (e.g., by streaming and/or downloading), play back (e.g., on a touch screen or on an external display connected via external port 124), send an email with a link to a particular online video, and otherwise manage online video in one or more file formats such as h.264. In some embodiments, the instant messaging module 141 is used to send links to particular online videos instead of the email client module 140. Additional description of online video applications may be found in U.S. provisional patent application 60/936,562 entitled "Portable Multifunction Device, method, and Graphical User Interface for Playing Online Videos," filed on even 20, 6, 2007, and U.S. patent application 11/968,067 entitled "Portable Multifunction Device, method, and Graphical User Interface for Playing Online Videos," filed on even 31, 12, 2007, the contents of both of which are hereby incorporated by reference in their entirety.

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

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

A predefined set of functions performed solely by the touch screen and/or touch pad optionally includes navigation between user interfaces. In some implementations, when the user touches the touchpad, the device 100 is navigated from any user interface displayed on the device 100 to a main menu, home menu, or root menu. In such implementations, a touch pad is used to implement a "menu button". In some other embodiments, the menu buttons are physical push buttons or other physical input control devices, rather than touch pads.

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

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

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

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

In some embodiments, event monitor 171 sends requests to peripheral interface 118 at predetermined intervals. In response, the peripheral interface 118 transmits event information. In other embodiments, the peripheral interface 118 transmits event information only if there is a significant event (e.g., an input above a predetermined noise threshold is received and/or an input exceeding a predetermined duration is received).

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

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

Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which the touch is detected optionally corresponds to a level of programming within the application's programming or view hierarchy. For example, the lowest horizontal view in which a touch is detected is optionally referred to as a hit view, and the set of events identified as being correctly entered is optionally determined based at least in part on the hit view of the initial touch that begins a touch-based gesture.

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

The activity event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some implementations, the active event identifier determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively engaged views and, thus, that all actively engaged views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely localized to an area associated with one particular view, the higher view in the hierarchy will remain the actively engaged view.

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

In some embodiments, the operating system 126 includes an event classifier 170. Alternatively, the application 136-1 includes an event classifier 170. In another embodiment, the event classifier 170 is a stand-alone module or part of another module stored in the memory 102, such as the contact/motion module 130.

In some implementations, the application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for processing touch events that occur within a respective view of the user interface of the application. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, the respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module that is a higher level object, such as a user interface toolkit (not shown) or application 136-1, from which to inherit methods and other properties. In some implementations, the respective event handlers 190 include one or more of the following: 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 the application internal state 192. Alternatively, one or more of application views 191 include one or more corresponding event handlers 190. Additionally, in some implementations, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in a respective application view 191.

The corresponding event identifier 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies events from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 further includes at least a subset of both: metadata 183 and event delivery instructions 188 (which optionally include sub-event delivery instructions).

The event receiver 182 receives event information from the event sorter 170. The event information includes information about sub-events such as touches or touch movements. The event information also includes additional information, such as the location of the sub-event, according to the sub-event. When a sub-event relates to movement of a touch, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes rotation of the device from one orientation to another orientation (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about a current orientation of the device (also referred to as a device pose).

The event comparator 184 compares the event information with predefined event or sub-event definitions and determines an event or sub-event or determines or updates the state of the event or sub-event based on the comparison. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 includes definitions of events (e.g., a predefined sequence of sub-events), such as event 1 (187-1), event 2 (187-2), and other events. In some implementations, sub-events in event 187 include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1 (187-1) is a double click on the displayed object. For example, the double click includes a first touch (touch start) for a predetermined period of time on the displayed object, a first lift-off (touch end) for a predetermined period of time, a second touch (touch start) for a predetermined period of time on the displayed object, and a second lift-off (touch end) for a predetermined period of time. In another example, the definition of event 2 (187-2) is a drag on the displayed object. For example, dragging includes touching (or contacting) on the displayed object for a predetermined period of time, movement of the touch on the touch-sensitive display 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

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

In some embodiments, the definition of the respective event 187 further includes a delay action that delays delivery of the event information until it has been determined that the sequence of sub-events does or does not correspond to an event type of the event recognizer.

When 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 impossible, event failed, or event end state after which subsequent sub-events of the touch-based gesture are ignored. In this case, the other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

In some embodiments, the respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to the actively engaged event recognizer. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate how event recognizers interact or are able to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

In some implementations, when one or more particular sub-events of an event are identified, the respective event identifier 180 activates an event handler 190 associated with the event. In some implementations, the respective event identifier 180 delivers event information associated with the event to the event handler 190. The activate event handler 190 is different from sending (and deferring) sub-events to the corresponding hit view. In some embodiments, event recognizer 180 throws a marker associated with the recognized event, and event handler 190 associated with the marker obtains the marker and performs a predefined process.

In some implementations, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about the sub-event without activating the event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with the sub-event sequence or to an actively engaged view. Event handlers associated with the sequence of sub-events or with the actively engaged views receive the event information and perform a predetermined process.

In some embodiments, the data updater 176 creates and updates data used in the application 136-1. For example, the data updater 176 updates a telephone number used in the contact module 137 or stores a video file used in the video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, the object updater 177 creates a new user interface object or updates the location of the user interface object. GUI updater 178 updates the GUI. For example, the GUI updater 178 prepares the display information and sends the display information to the graphics module 132 for display on a touch-sensitive display.

In some embodiments, one or more event handlers 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, the data updater 176, the object updater 177, and the 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.

It should be appreciated that the above discussion regarding event handling of user touches on a touch sensitive display also applies to other forms of user inputs that utilize an input device to operate the multifunction device 100, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; contact movement on the touchpad, such as tap, drag, scroll, etc.; stylus input; movement of the device; verbal instructions; detected eye movement; inputting biological characteristics; and/or any combination thereof is optionally used as input corresponding to sub-events defining the event to be identified.

Fig. 2 illustrates a portable or non-portable multifunction device 100 with a touch screen 112 in accordance with some embodiments. As described above, the multifunction device 100 is described as having various illustrated structures (such as touch screen 112, speaker 111, accelerometer 168, microphone 113, etc.); however, it should be understood that these structures optionally reside on separate devices. For example, display related structures (e.g., display, speaker, etc.) and/or functions optionally reside on a separate display device, input related structures (e.g., touch sensitive surface, microphone, accelerometer, etc.) and/or functions optionally reside on a separate input device, and the remaining structures and/or functions optionally reside on the multifunction device 100.

Touch screen 112 optionally displays one or more graphics within User Interface (UI) 200. In this and other embodiments described below, a user can select one or more of these graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figures) or one or more styluses 203 (not drawn to scale in the figures). In some embodiments, selection of one or more graphics will occur when a 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, up and/or down), and/or scrolling of a finger that has been in contact with the device 100 (right to left, left to right, up and/or down). In some implementations or in some cases, inadvertent contact with the graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that swipes over an application icon optionally does not select the corresponding application.

The device 100 optionally also includes one or more physical buttons, such as a "home" button, or a menu button 204. As previously described, menu button 204 is optionally used to navigate to any application 136 in a set of applications that are optionally executed on device 100. Alternatively, in some embodiments, the menu buttons are implemented as soft keys in a GUI displayed on touch screen 112.

In one embodiment, the device 100 includes a touch screen 112, menu buttons 204, a push button 206 for powering the device on and off and locking the device, one or more volume adjustment buttons 208, a Subscriber Identity Module (SIM) card slot 210, a headset jack 212, and a docking/charging external port 124. Pressing button 206 is optionally used to turn on/off the device by pressing the button and holding the button in the pressed state for a predefined time interval; locking the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input through the microphone 113 for activating or deactivating certain functions. The device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on the touch screen 112, and/or one or more haptic output generators 167 for generating haptic outputs for a user of the device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. As described above, the device 300 need not include a display and touch-sensitive surface, but rather, in some embodiments, is in optional communication with displays and touch-sensitive surfaces on other devices. In addition, the device 300 need not be portable. In some embodiments, the device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device (such as a television or set-top box), a navigation device, an educational device (such as a child learning toy), a gaming system, or a control device (e.g., a home or industrial controller). The device 300 generally includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communications between system components. The device 300 includes an input/output (I/O) interface 330 with a display 340, typically a touch screen display. The I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 (e.g., similar to the tactile output generator 167 described above with reference to fig. 1A), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch sensitive sensors, and/or contact intensity sensors (similar to the contact intensity sensor 165 described above with reference to fig. 1A)) for generating tactile outputs on the device 300. Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU 310. In some embodiments, memory 370 stores programs, modules, and data structures, or a subset thereof, similar to those stored in memory 102 of portable or non-portable multifunction device 100 (fig. 1A). Further, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable or non-portable multifunction device 100. For example, the memory 370 of the device 300 optionally stores the drawing module 380, the presentation module 382, the word processing module 384, the website creation module 386, the disk editing module 388, and/or the spreadsheet module 390, while the memory 102 of the portable or non-portable multifunction device 100 (fig. 1A) optionally does not store these modules.

Each of the above elements in fig. 3 is optionally stored in one or more of the previously mentioned memory devices. Each of the identified modules corresponds to a set of instructions for performing the functions described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures described above. Further, memory 370 optionally stores additional modules and data structures not described above.

Fig. 4 illustrates an exemplary user interface on a device (e.g., device 300 of fig. 3) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of fig. 3) separate from a display 450 (e.g., touch screen display 112). The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 357) for detecting the intensity of contacts on the touch-sensitive surface 451 and/or one or more tactile output generators 359 for generating tactile outputs for a user of the device 300.

While some of the examples below will be given with reference to inputs on touch screen display 112 (where the touch sensitive surface and the display are combined), in some embodiments the device detects inputs on a touch sensitive surface separate from the display, as shown in fig. 4. In some embodiments, the touch-sensitive surface (e.g., 451 in fig. 4) has a primary axis (e.g., 452 in fig. 4) that corresponds to the primary axis (e.g., 453 in fig. 4) on the display (e.g., 450). According to these embodiments, the device detects contact (e.g., 460 and 462 in fig. 4) with the touch-sensitive surface 451, the location of which corresponds to a corresponding location on the display (e.g., 460 corresponds to 468 and 462 corresponds to 470 in fig. 4). Thus, when the touch-sensitive surface (e.g., 451 in FIG. 4) is separated from the display (450 in FIG. 4) of the multifunction device, user inputs (e.g., contacts 460 and 462 and movement thereof) detected by the device on the touch-sensitive surface are used by the device to operate the user interface on the display. It should be appreciated that similar approaches are optionally used for other user interfaces described herein.

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

As used herein, the term "focus selector" refers to an input element for indicating the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is hovering over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input in the event that an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touch pad 355 in fig. 3 or touch-sensitive surface 451 in fig. 4). In some implementations including a touch screen display (e.g., touch sensitive display system 112 in fig. 1A) that enables direct interaction with user interface elements on the touch screen display, the contact detected on the touch screen acts as a "focus selector" such that when an input (e.g., a press input by contact) is detected on the touch screen display at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations, the focus is moved from one area of the user interface to another area of the user interface without a corresponding movement of the cursor or movement of contact on the touch screen display (e.g., by moving the focus from one button to another using a tab key or arrow key); in these implementations, the focus selector moves in accordance with movement of the focus between different areas of the user interface. Regardless of the particular form that the focus selector takes, the focus selector is typically controlled by the user to communicate user interface elements (or contacts on the touch screen display) of the user interface with which the user is expecting to interact (e.g., by indicating to the device the elements of the user interface with which the user desires to interact). For example, upon detection of a press input on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a respective button will indicate that the user desires to activate the respective button (rather than other user interface elements shown on the device display).

As used in the specification and claims, the term "characteristic intensity" of a contact refers to the characteristic of a 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 predefined number of intensity samples or a set of intensity samples acquired during a predetermined period of time (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after detection of contact, before or after detection of lift-off of contact, before or after detection of start of movement of contact, before or after detection of end of contact, and/or before or after detection of decrease in intensity of contact). The characteristic intensity of the contact is optionally based on one or more of: maximum value of intensity of contact, average value of intensity of contact, value at first 10% of intensity of contact, half maximum value of intensity of contact, 90% maximum value of intensity of 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 the user has performed an operation. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, contact of the feature strength that does not exceed the first threshold results in a first operation, contact of the feature strength that exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and contact of the feature strength that exceeds the second threshold results in a third operation. In some implementations, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform or forgo performing the respective operations) rather than for determining whether to perform the first or second operations.

In some implementations described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting a respective press input performed with a respective contact (or contacts), wherein a respective press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some implementations, the respective operation is performed in response to detecting that the intensity of the respective contact increases above a press input intensity threshold (e.g., a "downstroke" of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below the press input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press input threshold (e.g., an "upstroke" of the respective press input).

In some implementations, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter," in which the device defines or selects a hysteresis intensity threshold that has a predefined relationship to the compression input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the compression input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the compression input intensity threshold). Thus, in some embodiments, the press input includes an increase in the intensity of the respective contact above a press input intensity threshold and a subsequent decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and the respective operation is performed in response to detecting that the intensity of the respective contact subsequently decreases below the hysteresis intensity threshold (e.g., an "upstroke" of the respective press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold and optionally a subsequent decrease in contact intensity to an intensity at or below the hysteresis intensity, and a corresponding operation is performed in response to detecting a press input (e.g., an increase in contact intensity or a decrease in contact intensity depending on the circumstances).

For ease of explanation, optionally, a description of operations performed in response to a press input associated with a press input intensity threshold or in response to a gesture comprising a press input is triggered in response to detecting any of the following: the contact strength increases above the compression input strength threshold, the contact strength increases from an intensity below the hysteresis strength threshold to an intensity above the compression input strength threshold, the contact strength decreases below the compression input strength threshold, and/or the contact strength decreases below the hysteresis strength threshold corresponding to the compression input strength threshold. In addition, in examples where the operation is described as being performed in response to the intensity of the detected contact decreasing below a press input intensity threshold, the operation is optionally performed in response to the intensity of the detected contact decreasing below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

Fig. 5A illustrates a block diagram of an exemplary architecture for a device 500, according to some embodiments of the present disclosure. In the embodiment of fig. 5A, media content or other content is optionally received by device 500 via a network interface 502, which is optionally a wireless connection or a wired connection. The one or more processors 504 optionally execute any number of programs stored in the memory 506 or storage device, optionally including instructions to perform one or more of the methods and/or processes described herein (e.g., methods 700 and 900).

In some implementations, the display controller 508 causes various user interfaces of the present disclosure to be displayed on the display 514. In addition, input to the device 500 is optionally provided by a remote control 510 via a remote control interface 512, which is optionally a wireless or wired connection. In some embodiments, the input to the device 500 is provided by a multifunction device 511 (e.g., a smart phone) on which a remote control application is running that configures the multifunction device to simulate remote control functionality, as will be described in more detail below. In some embodiments, the multifunction device 511 corresponds to one or more of the devices 100 in fig. 1A and 2 and the device 300 in fig. 3. It should be understood that the embodiment of fig. 5A is not meant to limit features of the apparatus of the present disclosure, and that other components that facilitate other features described in the present disclosure are also optionally included in the architecture of fig. 5A. In some embodiments, device 500 optionally corresponds to one or more of multifunction device 100 in fig. 1A and 2 and device 300 in fig. 3; network interface 502 optionally corresponds to one or more of RF circuitry 108, external port 124, and peripheral interface 118 in fig. 1A and 2, and network communication interface 360 in fig. 3; the processor 504 optionally corresponds to one or more of the following: one or more processors 120 in fig. 1A and one or more CPUs 310 in fig. 3; the display controller 508 optionally corresponds to one or more of: the display controller 156 in FIG. 1A and the I/O interface 330 in FIG. 3; the memory 506 optionally corresponds to one or more of: memory 102 in fig. 1A and memory 370 in fig. 3; the remote control interface 512 optionally corresponds to one or more of the following: peripheral interface 118 and I/O subsystem 106 (and/or components thereof) in FIG. 1A and I/O interface 330 in FIG. 3; remote control 512 optionally corresponds to and/or includes one or more of the following: speaker 111, touch sensitive display system 112, microphone 113, one or more optical sensors 164, one or more contact intensity sensors 165, one or more tactile output generators 167, other input control devices 116, one or more accelerometers 168, proximity sensors 166, and I/O subsystem 106 in fig. 1A, and keyboard/mouse 350, touchpad 355, one or more tactile output generators 357, and one or more contact intensity sensors 359 in fig. 3, and touch sensitive surface 451 in fig. 4; and display 514 optionally corresponds to one or more of: one or more of the touch sensitive display systems 112 of fig. 1A and 2, and the display 340 of fig. 3.

Fig. 5B illustrates an exemplary structure of a remote control 510 according to some embodiments of the present disclosure. In some embodiments, remote control 510 optionally corresponds to one or more of multifunction device 100 in fig. 1A and 2 and device 300 in fig. 3. Remote control 510 optionally includes a touch-sensitive surface 451. In some implementations, the touch-sensitive surface 451 is edge-to-edge (e.g., it extends to an edge of the remote control 510 such that little or no surface of the remote control 510 is present between the touch-sensitive surface 451 and one or more edges of the remote control 510, as shown in fig. 5B). As previously described in this disclosure, the touch-sensitive surface 451 is optionally capable of sensing contact as well as contact intensity (e.g., clicking on the touch-sensitive surface 451). Further, the touch-sensitive surface 451 optionally includes mechanical actuators for providing physical button click functionality (e.g., the touch-sensitive surface 451 is "clickable" to provide corresponding input to the device 500). Remote control 510 also optionally includes buttons 516, 518, 520, 522, 524, and 526. Buttons 516, 518, 520, 522, 524, and 526 are optionally mechanical buttons or mechanical button alternatives that are capable of sensing contact or depression with such buttons to initiate a corresponding action on, for example, device 500. In some embodiments, user selection of the "menu" button 516 navigates the device 500 back in the currently executing application or currently displayed user interface (e.g., back to the user interface displayed prior to the currently displayed user interface) or navigates the device 500 to a user interface that is one level higher than the currently displayed user interface. In some embodiments, user selection of the "home" button 518 navigates the device 500 from any user interface displayed on the device 500 to a main menu, home menu, or root menu user interface (e.g., to a main screen of the device 500, which optionally includes one or more applications accessible on the device 500). In some implementations, user selection of the "play/pause" button 520 toggles between playing and pausing a currently playing content item on the device 500 (e.g., if the content item is playing on the device 500 when the "play/pause" button 520 is selected, the content item is optionally paused, and if the content item is paused on the device 500 when the "play/pause" button 520 is selected, the content item is optionally played). In some implementations, user selection of the "+"522 or "-"524 buttons increases or decreases, respectively, the volume of audio reproduced by the device 500 (e.g., the volume of a content item currently being played on the device 500). In some implementations, selection of the "audio input" button 526 by the user allows the user to provide audio input (e.g., voice input) to the device 500, optionally to a voice assistant on the device. In some implementations, the remote control 510 includes a microphone via which the user provides audio input to the device 500 when selecting the "audio in" button 526. In some embodiments, remote control 510 includes one or more accelerometers for detecting information regarding the motion of the remote control.

User interface and associated process

Set-top box provider based settings

Users interact with electronic devices in a number of different ways, including interacting with media (e.g., music, movies, etc.) available (e.g., stored, or otherwise accessible) on the electronic device. For example, a user may browse and play media that is accessible on an electronic device. In some cases, the electronic device is capable of hosting many applications for consuming media. The application may be a native application of the electronic device or may need to be installed by a user. In some cases, the electronic device may guide the user to set the device for the first time or after a factory reset. In these cases, the user may wish to quickly set up the electronic device by installing an application that is related to and recommended by the user for a particular subscription to the content. The embodiments described below provide a way for an electronic device to facilitate the suggestion and installation of applications on the electronic device during device setup, thereby enhancing user interaction with the electronic device. Enhancing interaction with the device reduces the amount of time required for the user to perform an operation, thereby reducing the power consumption of the device and extending the battery life of the battery-powered device. It will be appreciated that people use the device. When a person uses a device, the person is optionally referred to as a user of the device.

Fig. 6A-6 GG illustrate an exemplary manner in which an electronic device facilitates suggesting and installing applications on the electronic device during device setup according to some embodiments of the present disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to fig. 7A-7J.

Fig. 6A-6C illustrate one exemplary setup process for an electronic device (e.g., electronic device 500 of fig. 5A). In fig. 6A, an exemplary display 514 optionally displays one or more user interfaces including various content. In the example shown in fig. 6A, the display 514 displays a setup interface 601 of an electronic device (e.g., the electronic device 500 of fig. 5A), which the display 514 is part of or to which the display 514 is connected. In some embodiments, the device 500 enters the device setup process and the display 514 displays the setup interface 601 (e.g., in response to the device being first powered on or booted or after a factory reset). In fig. 6A, an initial setting start screen is displayed in the setting interface 601. The initial setup start screen optionally includes a header 610 that communicates to the user that the device is entering the device setup program. In some embodiments, title 610 is a text title or artwork (e.g., logo, picture, illustration, etc.).

In some implementations, the device 500 is pre-associated with a primary content provider (e.g., provider 1). The primary content provider is optionally a content provider (e.g., a cable television provider, a satellite provider, etc.) that provides users with access to content from multiple secondary content providers (e.g., CBS, fox, HBO, etc., or any other content provider) as part of a bundled service provided to the users (e.g., via subscriptions to the primary content provider). In some embodiments, when the serial number of the device is registered with the primary content provider (e.g., if the device is purchased from the primary content provider), there is a pre-association with the primary content provider. The pre-association is optionally set before the end-user or consumer of the electronic device receives the electronic device. In other words, pre-association is independent of any user input of the electronic device, and is optionally a setting set by the vendor or manufacturer of the electronic device. The user optionally purchases the electronic device from the primary content provider (e.g., unlike purchasing the device directly from the manufacturer, the manufacturer optionally is not associated with the primary content provider), and the primary content provider associates the serial number with the primary content provider and with the user's account credentials.

In some implementations, the unified media browsing application is installed on the device 500 (e.g., a default pre-installation on the device 500 or during a setup process). The unified media browsing application optionally provides a centralized location for browsing, viewing, or otherwise accessing content on the electronic device. The unified media browsing application optionally receives content viewing information from multiple content providers and/or applications to view content from those content providers installed on the electronic device (e.g., content providers that have enabled sharing of content viewing information with the unified media browsing application, such as a separate CBS application, a separate Fox application, a separate ESPN application, etc.). In some embodiments, the unified media browsing application aggregates all shared information to provide better and more cohesive interfaces and data sets for the user. In some embodiments, the unified media browsing application allows a user to browse content available on an electronic device via a content provider (e.g., CBS, fox, HBO, etc. or any other content provider), via a unified media browsing application's own services (e.g., iTunes Store maintained by Apple, inc. of Cupertino, california), or via the user's own account (e.g., previously purchased, currently rented, or otherwise owned content, which may be accessed from a server or stored locally on the electronic device). In some implementations, the unified media browsing application provides the user with an interface to select the content item that the user desires to view. Upon selection of a content item, the electronic device optionally determines a respective application from which the content item may be provided, launches the respective application, and causes playback of the selected content item.

In some embodiments, device 500 is located in a geographic location where a Unified Media Browsing (UMB) application is eligible. The location or geographic location of the device 500 may optionally not support the functionality of the unified media browsing application (e.g., a server supporting the application may optionally not have been set up for a particular country or region). In some embodiments, the user of device 500 has a unified media browsing application account. The unified media browsing application account is optionally a content access account. The content access account is optionally an account or subscription with a respective entity corresponding to the unified media browsing application (e.g., an account allowing a user to log in and use the unified media browsing application, which is optionally created and/or controlled by the respective entity), wherein the respective entity is different from the primary content provider and/or the secondary content provider. Examples of content access accounts are the iboud account and/or iTunes account and/or Apple ID maintained by Apple inc. Of Cupertino, california. In some embodiments, the setup process includes a setup interface for requesting the user to provide content access account information (e.g., login to a content access account or registration of a new content access account).

After the device 500 displays the initial setup launch screen, the device 500 automatically determines the primary content provider as provider 1 (e.g., using the serial number of the device 500 to look up a database without user input indicating or selecting the primary content provider 1), optionally using pre-association of the device with provider 1. The device 500 also optionally verifies that the device 500 resides in a geographic location where the unified media browsing application is eligible (e.g., the user optionally selects his or her location, or the device 500 optionally determines the location of the device and determines that the geographic location supports the unified media browsing application) and whether the user's unified media browsing application account is valid (e.g., the user optionally enters his or her unified media browsing application account credentials and successfully logs in). After successfully logging in to the primary content provider and determining eligibility for the unified media browsing application, the device 500 optionally displays a primary content provider welcome page. For example, in fig. 6B, display 514 displays a settings interface 601 with a title 610 indicating to the user that device 500 is to be set to take provider 1 as the primary content provider. The settings interface 601 optionally includes a representation 612 (e.g., logo, picture, video clip, etc.) of provider 1 and a settings description 614. The settings description 614 optionally informs the user of the steps that the settings will perform. For example, in FIG. 6B, setting description 614 indicates that the setting is agreed to install provider 1 applications and log device 500 into a single sign-on (described below) using the user's credentials at the primary content provider.

The setup interface 601 optionally includes two buttons: a continue button 620 and a cancel button 622. In fig. 6B, the continue button 620 has a current focus, as indicated by the dashed box within the icon 620. Clicking on cancel button 622 optionally exits the setup process and no further setup steps are performed. Clicking on the continue button 620 optionally continues the setup and performs the setup step. For example, in fig. 6B, because device 500 has successfully logged into provider 1 and is entitled to use the unified media browsing application, continuing to set up the provider 1 application (e.g., the user's cable company's application through which the user can access content from the user's cable company), setting up a single sign-on device 500 (e.g., authorizing device 500 to use provider 1), authorizing provider 1 application to use a single sign-on (e.g., granting access to a single sign-on authorization for provider 1 application to use provider 1 for the electronic device, and configuring provider 1 application to share viewing data with the unified media browsing application (e.g., content catalogs available from provider 1, content that the user previously viewed, content that the user is viewing, viewing preference data for the user, etc.).

In some embodiments, single sign-on is a feature in which a user's login credentials for a particular service are authenticated and authorized. As a result of the successful authorization, the device 500 optionally creates an authentication token and stores the authentication token on the device 500 itself or optionally on an external server. In some embodiments, the authorization is performed independent of any application and specific to a particular service. For example, device 500 optionally authorizes provider 1 as the primary content provider, and the authorization is optionally agnostic to provider 1 applications that are being installed or not installed on device 500. In some embodiments, the device 500 is capable of granting access to single sign-on authentication tokens for different applications or services on the device 500. Granting access to the identity authentication token optionally allows the corresponding application or service to access the identity authentication token to authenticate itself using the stored authentication credentials without separately authenticating the corresponding application to the primary content provider. Authenticating the respective application using the authentication token optionally provides respective application verification that the user has valid credentials of the primary content provider, and optionally enables the respective application to use the credentials of the primary content provider to access its respective content.

In some implementations, configuring the content provider application to share viewing data with the unified media browsing application will share a catalog of content available from the content provider (e.g., included in a user's subscription, or capable of being purchased or rented), content that the user has previously viewed (e.g., user viewing history), content that the user is currently viewing (e.g., content that the user has started viewing and paused or is currently viewing on the electronic device or another device), and viewing preference data for the user on the unified media browsing application (e.g., user-selected content ratings, or preferences determined by the user's viewing mode).

Returning to FIG. 6B, in some embodiments, the device 500 detects a click input of the contact 608 on the touch-sensitive surface 604 while the setup interface 601 is displayed, the input indicating selection of the continue button 620. As a result of detecting the click input, device 500 optionally performs the setup steps described above (e.g., installing provider 1 application (indicated by icon 618-2), setting up single sign-on, authorizing provider 1 application to use single sign-on credentials, and configuring provider 1 application to share viewing data with the unified media browsing application), and completing the setup process. In some embodiments, after completing the setup process, device 500 replaces the display of setup interface 601 with the display of home screen user interface 602, as shown in fig. 6C. In fig. 6C, the user interface 602 is an application browsing user interface of the operating system of the electronic device, which includes icons for different applications installed on the electronic device, which icons may be selected to launch their corresponding applications on the electronic device. For example, the user interface 602 includes icons 618-1 through 618-3 that can be selected to launch different applications on the electronic device. Icon 618-1 may be selected to launch the unified media browsing application, icon 618-2 may be selected to launch the media application corresponding to media provider 1, and icon 618-3 may be selected to launch the setup application. In some implementations, icons 618-1 through 618-3 are arranged in a scrollable grid pattern, and user interface 602 may be scrolled to display more rows of icons than 618-3. In some implementations, the provider 1 application icon 618-2 is placed in a preferential location on the user interface 602. For example, in FIG. 6C, icon 618-2 is placed in a second position on user interface 602 after unified media browsing application icon 618-1.

The user interface 602 optionally also includes an area (e.g., a "top-level" area) above the icon 618 that optionally displays one or more user interface elements corresponding to applications whose icons 618 have current focus (in some embodiments, only those icons that are top-line icons in the user interface 602). For example, in FIG. 6C, icon 618-2, corresponding to media provider 1, has the current focus. As a result, the electronic device displays representations 623-1 through 623-4 of media items accessible from media provider 1 in the "top-level" region of user interface 602. The representation 623 optionally includes information identifying each media item (e.g., text information) and/or information about the content of each media item (e.g., a video preview of the media item, a still image of the media item, etc.). In some embodiments, the "top-level" area is a scrollable area that includes representations of suggested media items for applications currently highlighted in the home screen, and swipes up so that the current focus moves to a representation of one of the suggested media items, upon selection of which representation (e.g., by a tap or click input on a remote control), will cause the device to begin playing a media item corresponding to the representation of the suggested media item with the current focus.

In some embodiments, as shown in fig. 6C, device 500 installs the provider 1 application, enables single sign-on (e.g., authorizes device 500 to use provider 1), logs in single sign-on (e.g., grants access to single sign-on authentication of the provider 1 application), and enables sharing of viewing data with the unified media browsing application as a result of the setup process. While fig. 6A-6C illustrate certain setup interfaces and steps as one-by-one, this is illustrative and not limiting. For example, the device setup process may optionally include other setup interfaces and steps before, after, or between any of the setup interfaces and steps described above without departing from the scope of the present disclosure.

Fig. 6D-6F illustrate another exemplary setup process for device 500. In the example shown in fig. 6D, the display 514 displays a setup interface 601 of an electronic device (e.g., the electronic device 500 of fig. 5A) of which the display 514 is a part or to which the display 514 is connected. In some embodiments, the device 500 enters the device setup process and the display 514 displays the setup interface 601 (e.g., in response to the device being first powered on or started or after a factory reset), similar to that described in fig. 6A. In some embodiments, as shown in fig. 6D, the device 500 is pre-associated with the primary content provider (e.g., the serial number of the device 500 is pre-associated with provider 1), the device 500 is not located in a geographic location where the unified media browsing application is eligible (e.g., the device 500 is located in a location where use of the unified media browsing application is not supported), and the user of the device 500 has a valid unified media browsing application account.

After the device 500 displays the initial setup launch screen, the device 500 automatically determines the primary content provider as provider 1 (e.g., using the serial number of the device 500 to look up a database without user input indicating or selecting the primary content provider 1), optionally using pre-association of the device with provider 1. The device 500 also optionally attempts to verify that the device 500 resides in a geographic location where the unified media browsing application is eligible (e.g., the user optionally selects his or her location, or the device 500 optionally determines the location of the device and determines that the geographic location supports the unified media browsing application) and whether the user's unified media browsing application account is valid (e.g., the user optionally enters his or her unified media browsing application account credentials and successfully logs in). Because the device 500 is not resident in a geographic location that supports the unified media browsing application, the device 500 determines that it is not eligible to use the unified media browsing application. After successfully logging in to the primary content provider and determining disqualification of the unified media browsing application, the device 500 optionally displays a primary content provider welcome page, similar to the page shown in FIG. 6B. For example, in FIG. 6E, display 514 displays a settings interface 601 with a title 610 indicating to the user that device 500 is to be set to have provider 1 as the primary content provider, and a settings description 614 indicating agreement that the setting is to install the provider 1 application and log device 500 into a single sign-on.

In fig. 6E, because device 500 has successfully logged into provider 1, but is not entitled to use the unified media browsing application, continuing to set (e.g., clicking on continue button 620) will install the provider 1 application (e.g., the user's cable company application through which the user can access content from the user's cable company), setting single sign-on device 500 (e.g., authorizing device 500 to use provider 1), and authorizing provider 1 application to use single sign-on (e.g., granting access to a single sign-on authorization for provider 1 application to use provider 1 for the electronic device), but not configuring provider 1 application to share viewing data with the unified media browsing application.

In fig. 6E, the device 500 detects a click input of a contact 608 on the touch-sensitive surface 604 while the setup interface 601 is displayed, the input indicating selection of a continue button 620. As a result of detecting the click input, device 500 optionally performs the setup steps described above (e.g., installing the provider 1 application, setting up a single sign-on, and authorizing the provider 1 application to use single sign-on credentials, but not configuring the provider 1 application to share viewing data with the unified media browsing application) and completes the setup process. In some embodiments, after completing the setup process, device 500 replaces the display of setup interface 601 with the display of home screen user interface 602, as shown in fig. 6F.

In some embodiments, as shown in fig. 6F, as a result of the setup process, device 500 installs the provider 1 application, enables single sign-on (e.g., authorizes device 500 to use provider 1), logs in single sign-on (e.g., grants access to single sign-on authentication of the provider 1 application), and does not enable sharing of viewing data with the unified media browsing application. While fig. 6D-6F illustrate certain setup interfaces and steps as one-by-one, this is illustrative and not limiting. For example, the device setup process may optionally include other setup interfaces and steps before, after, or between any of the setup interfaces and steps described above without departing from the scope of the present disclosure.

Fig. 6G-6I illustrate another exemplary setup process for the device 500 that is similar to the setup process described in fig. 6A-6C, but in which the user of the device 500 does not have an active unified media browsing application account. After the device 500 displays the initial setup launch screen, the device 500 automatically determines the primary content provider as provider 1 (e.g., using the serial number of the device 500 to look up a database without user input indicating or selecting the primary content provider 1), optionally using pre-association of the device with provider 1. Device 500 optionally verifies that device 500 resides in a geographic location where the unified media browsing application is eligible (e.g., the user optionally selects his or her location, or device 500 optionally determines the location of the device and determines that the geographic location supports the unified media browsing application) and attempts to verify that the user has a valid unified media browsing application account. In fig. 6G-6I, because the user of device 500 does have a valid unified media browsing application account, device 500 determines that it is not eligible to use the unified media browsing application. After successfully logging in to the primary content provider and determining disqualification of the unified media browsing application, the device 500 optionally displays a primary content provider welcome page, similar to the page shown in FIG. 6B. For example, in FIG. 6H, display 514 displays a settings interface 601 with a title 610 indicating to the user that device 500 is to be set to have provider 1 as the primary content provider, and a settings description 614 indicating agreement that the setting is to install the provider 1 application and log device 500 into a single sign-on.

In fig. 6H, because device 500 has successfully logged into provider 1, but is not entitled to use the unified media browsing application, continuing to set (e.g., clicking on continue button 620) will install the provider 1 application (e.g., the user's cable company application through which the user can access content from the user's cable company), setting single sign-on device 500 (e.g., authorizing device 500 to use provider 1), and authorizing provider 1 application to use single sign-on (e.g., granting access to a single sign-on authorization for provider 1 application to use provider 1 for the electronic device), but not configuring provider 1 application to share viewing data with the unified media browsing application.

In fig. 6H, the device 500 detects a click input of the contact 608 on the touch-sensitive surface 604 while the setup interface 601 is displayed, the input indicating selection of the continue button 620. As a result of detecting the click input, device 500 optionally performs the setup steps described above (e.g., installing the provider 1 application, setting up a single sign-on, and authorizing the provider 1 application to use single sign-on credentials, but not configuring the provider 1 application to share viewing data with the unified media browsing application) and completes the setup process. In some embodiments, after completing the setup process, device 500 replaces the display of setup interface 601 with the display of home screen user interface 602, as shown in fig. 6I.

In some embodiments, as shown in fig. 6I, as a result of the setup process, device 500 installs the provider 1 application, enables single sign-on (e.g., authorizes device 500 to use provider 1), logs in single sign-on (e.g., grants access to single sign-on authentication of the provider 1 application), and does not enable sharing of viewing data with the unified media browsing application. While fig. 6G-6I show certain setup interfaces and steps as one after the other, this is illustrative and not limiting. For example, the device setup process may optionally include other setup interfaces and steps before, after, or between any of the setup interfaces and steps described above without departing from the scope of the present disclosure.

Fig. 6J-6M illustrate another exemplary setup process for the device 500 that is similar to the setup process described in fig. 6A-6C, but in which the device 500 is not successfully logged into the primary content provider. In some embodiments, the device 500 does not successfully log into the primary content provider because the device's serial number is optionally associated with the wrong primary content provider, the user no longer has a valid primary content provider account, or any other scenario that would result in unsuccessful authentication, such as the electronic device being unable to communicate with the primary content provider at this time due to a connection problem.

After unsuccessful login to the primary content provider, the device 500 optionally displays a primary content provider login page. For example, in fig. 6K, display 514 displays setup interface 601 with login fields, login confirmation button 624, and login cancellation button 626 for user provider 1 login credentials (e.g., username field 630 and password field 632). In fig. 6K, the device 500 detects a click input of the contact 608 on the touch-sensitive surface 604 while displaying the setup interface 601 with login fields 630 and 632 and while the login confirmation button 624 is highlighted. As a result, the device 500 logs into provider 1 and verifies the user's login credentials (if correct). The device 500 also optionally verifies that the device 500 resides in a geographic location where the unified media browsing application is eligible (e.g., the user optionally selects his or her location, or the device 500 optionally determines the location of the device and determines that the geographic location supports the unified media browsing application) and verifies that the user has a valid unified media browsing application account.

After successfully logging into the primary content provider using the user-provided credentials (e.g., not pre-associated) and determining eligibility of the unified media browsing application, the device 500 optionally continues the setup process as if the device were successfully logged into the primary content provider using pre-association. For example, in fig. 6L, the display 514 displays a setup interface 601 similar to that in fig. 6B. After detecting a click input of contact 608, device 500 optionally performs the following setup steps: installing the provider 1 application (indicated by icon 618-2), setting up a single sign-on, authorizing the provider 1 application to use the single sign-on credentials, and configuring the provider 1 application to share viewing data with the unified media browsing application, thereby completing the setup process. In some embodiments, after completing the setup process, device 500 replaces the display of setup interface 601 with the display of home screen user interface 602, as shown in fig. 6M.

In some embodiments, as shown in fig. 6M, device 500 installs the provider 1 application, enables single sign-on (e.g., authorizes device 500 to use provider 1), logs in single sign-on (e.g., grants access to single sign-on authentication of the provider 1 application), and enables sharing of viewing data with the unified media browsing application as a result of the setup process. While fig. 6J-6M illustrate certain setup interfaces and steps as one-by-one, this is illustrative and not limiting. For example, the device setup process may optionally include other setup interfaces and steps before, after, or between any of the setup interfaces and steps described above without departing from the scope of the present disclosure.

Fig. 6N-6P illustrate another exemplary setup process for device 500 that is similar to the setup process described in fig. 6A-6C, but in which device 500 is not successfully logged into the primary content provider and device 500 is not eligible for use with the unified media browsing application (e.g., either because device 500 is located in a geographic location where the unified media application is not eligible, or because the user does not have a valid unified media application account). In such cases, the device 500 optionally displays the primary content provider application installation page. For example, in FIG. 6O, display 514 displays a settings interface 601 with a title 610 indicating to the user that device 500 is to install a provider 1 application. The settings interface 601 optionally includes a representation 612 (e.g., logo, picture, video clip, etc.) of provider 1 and a settings description 614. The settings description 614 optionally informs the user of the steps that the settings will perform. For example, in FIG. 6O, the settings description 614 indicates that the settings are agreed to install the provider 1 application.

In fig. 6O, because the device 500 did not successfully log into the provider 1 and also did not qualify for use of the unified media browsing application, the settings continue to be set up to install the provider 1 application (e.g., the user's cable company's application through which the user can access content from the user's cable company), but single sign-on will not be set up on the device 500 (e.g., the device 500 is authorized to use the provider 1), the provider 1 application will not be authorized to use single sign-on (e.g., access to single sign-on authorization of the electronic device for use of the provider 1 by the provider 1 application is granted), nor will the provider 1 application be configured to share viewing data with the unified media browsing application (e.g., content catalogs available from the provider 1, content previously viewed by the user, content being viewed by the user, viewing preference data for the user, etc.).

In fig. 6O, the device 500 detects a click input of a contact 608 on the touch-sensitive surface 604 while displaying the setup interface 601, the input indicating selection of a continue button 620. As a result of detecting the click input, the device 500 optionally performs the setup steps described above (e.g., installs the provider 1 application, but does not set single sign-on, does not authorize the provider 1 application to use single sign-on credentials, and does not configure the provider 1 application to share viewing data with the unified media browsing application) and completes the setup process. In some embodiments, after completing the setup process, device 500 replaces the display of setup interface 601 with the display of home screen user interface 602, as shown in fig. 6P.

In some embodiments, as shown in fig. 6P, device 500 installs the provider 1 application as a result of the setup process, but does not enable single sign-on (e.g., authorizing device 500 to use provider 1), does not log-in single sign-on (e.g., granting access to single sign-on authentication of provider 1 application), and does not enable sharing of viewing data with the unified media browsing application. While fig. 6N-6P illustrate certain setup interfaces and steps as one-by-one, this is illustrative and not limiting. For example, the device setup process may optionally include other setup interfaces and steps before, after, or between any of the setup interfaces and steps described above without departing from the scope of the present disclosure.

In some implementations, the device 500 is not pre-associated with the primary content provider. The device 500 is optionally not pre-associated with the primary content provider because the device 500 was purchased from the manufacturer of the device rather than through the primary content provider, or alternatively because the user has skipped the setup steps for automatically determining the primary content provider based on the predefined association (e.g., if the user wishes to set up the device using a different primary content provider than the primary content provider that has been pre-associated, such as if the user selects "now unused" 622 in fig. 6B or similar figures). For example, fig. 6Q-6V illustrate one exemplary setup process for the device 500, wherein the device 500 is not pre-associated with a primary content provider.

After the device 500 displays the initial setup launch screen, the device 500 optionally displays a provider selection interface, as shown in fig. 6Q. For example, in fig. 6R, the setup interface 601 includes a provider search field 634. The user can optionally search for and select an appropriate primary content provider by entering the name of the user's primary content provider in a search field 634 via an input device. The setup interface 601 optionally includes a plurality of quick access provider buttons 636, 638, and 639 corresponding to provider 1, provider 2, and provider 3, respectively. Quick access provider buttons 636, 638, and 639 optionally list the most popular primary search providers, available for the geographic location of device 500, or the top results of the provider search (e.g., options updated as the user enters letters in search field 634). In FIG. 6R, a click input of contact 608 is detected on touch-sensitive surface 604, which indicates that the user selected provider 1 as the primary content provider. As a result of detecting this click input, device 500 optionally updates display 514 to display the primary content provider landing page. For example, in fig. 6S, display 514 displays setup interface 601 with login fields, login confirmation button 624, and login cancellation button 626 for login credentials (e.g., username field 630 and password field 632) of user provider 1. In fig. 6S, the device 500 detects a click input of the contact 608 on the touch-sensitive surface 604 while displaying the setup interface 601 with login fields 630 and 632 and while the login confirmation button 624 is highlighted. As a result, device 500 logs into provider 1 and verifies the user's login credentials (if correct) at provider 1. The device 500 also optionally determines whether the device 500 is eligible for use with a unified media browsing application (e.g., the device 500 resides in a geographic location where the unified media browsing application is eligible, and the user has a valid unified media browsing application account).

After successfully logging into the primary content provider using the credentials provided by the user and determining eligibility for the unified media browsing application, the device 500 optionally continues the setup process and recommends multiple applications to the user for installation. For example, in FIG. 6T, the setup interface 601 includes an iconic grid 616 that suggests applications for installation. In some embodiments, the suggested applications include a provider 1 application and optionally 8 other suggested applications. In some embodiments, the suggested applications are the most commonly used or popular secondary content provider applications (e.g., CBS content applications, HBO content applications) that correspond to secondary content providers (e.g., CBS and HBO) included in the user's subscription to the primary content provider. For example, if a user's subscription to a primary content provider enables the user to access a first set of secondary content provider applications to be installed, the device 500 optionally suggests a first set of secondary content provider applications to be installed, and if a user's subscription to a primary content provider enables the user to access a second set of secondary content provider applications different from the first set (e.g., more or less channels or different channels), the device 500 optionally suggests a second set of secondary content provider applications different from the first set (e.g., more or less applications or different applications) to be installed. In some embodiments, the suggested application to be installed is not based on a user's subscription to the primary content provider. For example, the suggested application may alternatively be the most popular content application in iTunes store (maintained by Apple inc. Of Cupertino, california) regardless of the user's subscription to the primary content provider.

In fig. 6T, after detecting a click input of the contact 608, the device optionally performs the following setup steps: installing the listed application, setting a single sign-on the device, and authorizing the provider 1 application to use the single sign-on credentials. In some embodiments, if the suggested application is included in the user's subscription to the primary content provider, the device 500 also authorizes the suggested application to use single sign-on credentials. In some embodiments, if the device 500 determines that it is eligible to use the unified media browsing application (e.g., the device 500 is located in a geographic location where the unified media application is not eligible and the user has a valid unified media application account), the device 500 configures the provider 1 application (and optionally other suggested applications) to share viewing data with the unified media browsing application. In some embodiments, if device 500 determines that it does not qualify for use with the unified media browsing application (e.g., either because device 500 is located in a geographic location where the unified media application is not compliant or because the user does not have a valid unified media application account), device 500 does not configure provider 1 applications or suggested applications to share viewing data with the unified media browsing application. In some embodiments, after completing the setup process, device 500 replaces the display of setup interface 601 with the display of home screen user interface 602, as shown in fig. 6U.

In some embodiments, as shown in fig. 6U, as a result of the setup process, device 500 installs the provider 1 application, installs the suggested application, enables single sign-on (e.g., authorizes device 500 to use provider 1), logs in single sign-on (e.g., grants access to single sign-on authentication of provider 1 application), and enables sharing view data with the unified media browsing application. In some embodiments, device 500 creates an entertainment folder (represented by icon 618-4) and installs the suggested application within the folder. For example, the user can display the content of the entertainment folder by clicking on the input selection icon 618-4, as shown in FIG. 6V. The content of the entertainment folder is optionally displayed in a pop-up window overlaid on home screen interface 602. In FIG. 6V, the entertainment folder displays six applications, represented by icons 618-5 through 618-10. In some implementations, the pop-up window is a scrollable list that is optionally capable of scrolling to display more application icons. In FIG. 6U, the provider 1 application (represented by icon 618-2) is installed in a preferred location on the user interface 602 rather than in the entertainment folder. While fig. 6Q-6U illustrate certain setup interfaces and steps as one-by-one, this is illustrative and not limiting. For example, the device setup process may optionally include other setup interfaces and steps before, after, or between any of the setup interfaces and steps described above without departing from the scope of the present disclosure.

Fig. 6W-6 AA illustrate another exemplary setup process for the device 500 that is similar to the setup process described in fig. 6O-6V, but where the geographic location of the device 500 has only one primary content provider. In such cases, the device 500 optionally determines the current location of the device (e.g., querying an internet service provider, querying an IP address geolocation service, receiving GPS data, or other suitable location determination mechanism), and determines that only one primary content provider serves the device location (e.g., optionally querying a server or through a lookup table). In some embodiments, this determination occurs before all setup steps occur (e.g., before or during the initial setup launch screen, or before the device 500 automatically displays the primary content provider login page). After displaying the initial settings launch screen, the device 500 optionally automatically displays a primary content provider login page for the unique primary content provider in that location (e.g., without user input identifying the selected primary content provider). For example, as shown in fig. 6X, the only provider is provider 1. Thus, the device 500 optionally displays a prompt in the setting interface 601 for setting the device to provider 1. Upon detecting a click input of contact 608 on touch-sensitive surface 604 while continue button 620 is highlighted, display 514 changes to display the primary content provider landing page in FIG. 6Y, similar to the page shown in FIG. 6K. In fig. 6Y, display 514 displays setup interface 601 with login fields, login confirmation button 624, and login cancellation button 626 for login credentials (e.g., username field 630 and password field 632) of user provider 1. In fig. 6Y, the device 500 detects a click input of the contact 608 on the touch-sensitive surface 604 while displaying the setup interface 601 with login fields 630 and 632 and while the login confirmation button 624 is highlighted. As a result, the device 500 logs into provider 1 and verifies the user's login credentials (if correct). The device 500 also optionally determines whether the device 500 is eligible for use with a unified media browsing application (e.g., the device 500 resides in a geographic location where the unified media browsing application is eligible, and the user has a valid unified media browsing application account).

After successfully logging into the primary content provider using the credentials provided by the user and determining eligibility for the unified media browsing application, the device 500 optionally continues the setup process and recommends multiple applications to the user for installation. For example, in FIG. 6Z, the setup interface 601 includes an iconic grid 616 that suggests applications for installation. In some embodiments, the suggested applications include a provider 1 application and optionally 8 other suggested applications. In some embodiments, the suggested applications are the most commonly used or popular secondary content provider applications (e.g., CBS content applications, HBO content applications) that correspond to secondary content providers (e.g., CBS and HBO) included in the user's subscription to the primary content provider. For example, if a user's subscription to a primary content provider enables the user to access a first set of secondary content provider applications to be installed, the device 500 optionally suggests a first set of secondary content provider applications to be installed, and if a user's subscription to a primary content provider enables the user to access a second set of secondary content provider applications different from the first set (e.g., more or less channels or different channels), the device 500 optionally suggests a second set of secondary content provider applications different from the first set (e.g., more or less applications or different applications) to be installed. In some embodiments, the suggested application to be installed is not based on a user's subscription to the primary content provider. For example, the suggested application may alternatively be the most popular content application in iTunes store (maintained by Apple inc. Of Cupertino, california) regardless of the user's subscription to the primary content provider.

In fig. 6Z, after detecting a click input of contact 608, the device optionally performs the following setup steps: installing the listed application, setting a single sign-on the device, and authorizing the provider 1 application to use the single sign-on credentials. In some embodiments, if the suggested application is included in the user's subscription to the primary content provider, the device 500 also authorizes the suggested application to use single sign-on credentials. In some embodiments, if the device 500 determines that it is eligible to use the unified media browsing application (e.g., the device 500 is located in a geographic location where the unified media application is not eligible and the user has a valid unified media application account), the device 500 configures the provider 1 application (and optionally other suggested applications) to share viewing data with the unified media browsing application. In some embodiments, if device 500 determines that it does not qualify for use with the unified media browsing application (e.g., either because device 500 is located in a geographic location where the unified media application is not compliant or because the user does not have a valid unified media application account), device 500 does not configure provider 1 applications or suggested applications to share viewing data with the unified media browsing application. In some embodiments, after the setup process is completed, device 500 replaces the display of setup interface 601 with the display of home screen user interface 602, as shown in fig. 6 AA.

In some embodiments, as shown in fig. 6AA, as a result of the setup process, device 500 installs the provider 1 application, installs the suggested application, enables single sign-on (e.g., authorizes device 500 to use provider 1), logs in single sign-on (e.g., grants access to single sign-on authentication of provider 1 application), and enables sharing of viewing data with the unified media browsing application. In some embodiments, device 500 creates an entertainment folder (represented by icon 618-4) and installs the suggested application within the folder. For example, the user can display the content of the entertainment folder by clicking on the input selection icon 618-4, similar to the content described in FIG. 6V. In FIG. 6AA, the provider 1 application (represented by icon 618-2) is installed in a preferred location on the user interface 602 rather than in the entertainment folder. While fig. 6W-6 AA show certain setup interfaces and steps as one after the other, this is illustrative and not limiting. For example, the device setup process may optionally include other setup interfaces and steps before, after, or between any of the setup interfaces and steps described above without departing from the scope of the present disclosure.

In some embodiments, device 500, after completing its setup process (e.g., as described above), displays home screen interface 602 on display 514, as shown in fig. 6 BB. The user optionally installs a new application associated with the secondary content provider to which the user's subscription to the primary content provider (e.g., provider 1) provides the user with access (e.g., the user's cable package includes the secondary content provider). For example, in FIG. 6CC, device 500 installs a new application 9, represented by icons 618-11. At device setup, the application 9 is optionally included in the user's primary content provider (e.g., provider 1) account package. In some embodiments, if the application 9 is included in a user's subscription to a primary content provider when the device 500 enables single sign-on (e.g., when the device 500 creates an authentication token for the provider 1), the single sign-on authorization of the device includes the authentication privileges of the application 9 (e.g., the authentication token for the provider 1 includes the access privileges of the secondary content source corresponding to the application 9). In FIG. 6CC, device 500 detects a click input of contact 608 on touch-sensitive surface 604 while display interface 602 and icons 618-11 are highlighted, the input indicating a desire to launch application 9.

In some embodiments, because the application 9 is included in the user's subscription to the primary content provider when single sign-on for the primary content provider occurs, the device 500 is able to launch and display the application 9 as a result of detecting the click input. The application 9 is optionally able to use the authorization of the device and to launch without further input from the user, as shown in fig. 6 DD.

In some embodiments, the user optionally installs another new application associated with the secondary content provider, and the user's subscription to the primary content provider (e.g., provider 1) provides the user with access to the secondary content provider (e.g., the user's cable package includes the secondary content provider). For example, in FIG. 6EE, device 500 installs a new application 10, represented by icons 618-12. The application 10 is optionally included in the user's primary content provider (e.g., provider 1) account package at device setup, but is optionally currently included in the user's primary content provider account package. For example, the user's subscription to the primary content provider may optionally be changed to now include the secondary content provider associated with the application 10 (e.g., the user's cable package now includes more channels). In some embodiments, if the application 10 is not included in the user's subscription to the primary content provider when the device 500 enables single sign-on (e.g., when the device 500 creates an authentication token for provider 1), the single sign-on authorization of the device does not include the authentication privileges of the application 10 (e.g., the authentication token for provider 1 does not include the access privileges of the secondary content source corresponding to the application 10). In FIG. 6EE, device 500 detects a click input of contact 608 on touch-sensitive surface 604 while display interface 602 and icons 618-12 are highlighted, the input indicating a desire to launch application 10.

In some embodiments, the device 500 optionally displays an authentication pop-up window prior to launching and displaying the application 10 because the application 10 is not included in the user's subscription to the primary content provider when single sign-on to the primary content provider occurs. The authentication popup window requests permission from the user to allow the application 10 to use authentication of the device 500 to the provider 1 (e.g., grant or deny access to the application 10, authorize the device 500 to the provider 1 (single sign-on)). The authentication popup window includes a "yes" button 628 and a "no" button 629. In fig. 6FF, when the yes button 628 is highlighted, the device 500 detects a click input of the contact 608. Thus, the device 500 optionally authorizes the application 10 to use single sign-on (e.g., grants access to single sign-on authorization for the application 10 to have the electronic device use the provider 1). After the application 10 is granted access to the single sign-on, the device 500 can optionally use the authorization of the device and launch the application 10, as shown in fig. 6 GG. In some embodiments, in response to the user selecting the "no" button 629, the device 500 does not grant the application 10 access rights for single sign-on authorization. In some embodiments, the user must individually authorize the use of the primary content provider's application 10 to access content on the application 10 that is included in the user's subscription to the primary content provider, as there is no access right to the single sign-on authorization.

Fig. 7A-7J are flowcharts illustrating a method 700 of facilitating suggesting and installing applications on an electronic device during initial device setup according to some embodiments of the present disclosure. Method 700 is optionally performed on an electronic device (such as device 100, device 300, or device 500), as described above in connection with fig. 1A-1B, 2-3, and 5A-5B. Some operations in method 700 are optionally combined and/or the order of some operations is optionally changed.

As described below, method 700 provides a manner by which to facilitate suggesting and installing applications on an electronic device during initial device setup. The method reduces the cognitive burden on the user when interacting with the device user interface of the present disclosure, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, improving the efficiency of user interaction with the user interface saves power and increases the time between battery charges.

In some embodiments, an electronic device (e.g., a set top box, such as device 100, device 300, or device 500) in communication with a display (e.g., a television, such as display 514) and one or more input devices (e.g., a remote control device separate from the electronic device, such as remote control 510, or a smart phone separate from the electronic device, such as device 511) determines (702) a primary content provider (e.g., a cable television provider, satellite provider, etc.) for the electronic device that allows content associated with the primary content provider to be accessible on the electronic device, such as in fig. 6A (e.g., the electronic device is optionally associated with one or more primary content providers). In some embodiments, the electronic device is a tablet, smart phone, wearable device, etc., and the display and/or input device is a touch screen included in these devices. In some embodiments, the electronic device is optionally pre-associated with the primary content provider. For example, if the device is purchased from a primary content provider, the serial number of the device is optionally registered with the primary content provider. In some implementations, a user identifies a primary content provider associated with an electronic device. In some implementations, the electronic device is authorized to use the primary content provider (e.g., receive content from the primary content provider based on a subscription of the user). In some embodiments, authorizing the electronic device to use the primary content provider allows one or more secondary content provider (e.g., CBS, fox, HBO, etc., or any other content provider) applications that the user has access to through subscriptions to the primary content provider (e.g., cable television provider, satellite provider, etc.) to be installed on the electronic device to provide content on the electronic device through the primary content provider and corresponding respective secondary content provider that the user gives access to the user to the primary content provider through subscriptions to the primary content provider. In particular, if an application (e.g., a CBS content application) on an electronic device is permitted to authorize the electronic device to use a primary content provider (e.g., a cable television provider), and a user's subscription to the primary content provider gives the user access to a secondary content provider associated with the application (e.g., the user's cable package includes CBS), the application is optionally able to display content from the secondary content provider on the electronic device (e.g., the user is able to view CBS content on the electronic device using the CBS application). If the application is not permitted to authorize the electronic device, the application optionally must be individually authorized to use the primary content provider (e.g., the user must log in his cable provider from within the CBS application) to display content on the electronic device from the secondary content provider associated with the application.

In some embodiments, after determining a primary content provider for an electronic device, the electronic device displays (704), on a display, one or more representations of one or more suggested applications to be installed on the electronic device (e.g., displaying icons for content source-specific applications optionally included in a user's service package or bundled with the primary content provider) based on the determined primary content provider, including a first application associated with the primary content provider, such as shown in FIG. 6T (e.g., an application of the primary content provider, such as a user's cable television company's application through which the user can access content from the user's cable television company)

In some embodiments, the suggested application is the highest scoring or popular application of the determined subscribers of the primary content provider. In some embodiments, the suggested application is the highest scoring or popular application and is not associated with the primary content provider (e.g., the highest scoring or popular application within an application store accessible on the electronic device is independent of the popularity of the application among subscribers of the determined primary content provider). The number of suggested applications to be installed is optionally one, two, six, nine, ten or more. The primary content provider's application may alternatively be a content viewing application, a primary content provider account management application, or any other suitable application associated with the primary content provider. In some embodiments, if the primary content provider is a first primary content provider, the electronic device suggests a first application, and if the primary content provider is a second primary content provider, the electronic device suggests a second application that is different from the first application (e.g., the electronic device suggests which primary content provider application is based on which primary content provider is determined).

In some embodiments, upon displaying one or more representations for one or more suggested applications, the electronic device receives (706), via one or more input devices, an input corresponding to a request to install the one or more suggested applications on the electronic device, such as shown in fig. 6T (e.g., the user selects one or more of the one or more suggested applications to install, or the user agrees to install all of the one or more suggested applications). In some embodiments, in response to receiving the input, the electronic device installs (708) the one or more suggested applications on the electronic device, such as shown in fig. 6U (e.g., the installed one or more suggested applications are optionally authorized to use the primary content provider as part of the installation).

For example, the proposed application may optionally be entitled to use the primary content provider as a whole for the electronic device. In some embodiments, this installation authorizes the electronic device to use the primary content provider and allows the installed one or more suggested applications to provide content on the electronic device via the primary content provider and corresponding respective second content providers to which the user's subscription to the primary content provider gives the user access rights. In some embodiments, the one or more suggested applications installed are further configured to share their viewing history data with a unified media browser application installed on the electronic device as a result of the user requesting installation of the suggested application. In some implementations, the unified media browsing application provides a centralized location for browsing, viewing, or otherwise accessing content on an electronic device. The unified media browsing application optionally receives content viewing information from multiple content providers and/or applications to view content from those content providers installed on the electronic device (e.g., content providers that have enabled sharing of content viewing information with the unified media browsing application, such as a separate CBS application, a separate Fox application, a separate ESPN application, etc.). In some implementations, the shared content viewing information includes a catalog of content available from the respective content provider (e.g., included in a subscription of the user, or capable of being purchased or rented), content that the user has previously viewed (e.g., a user viewing history), content that the user is currently viewing (e.g., content that the user has started viewing and paused or is currently viewing on the electronic device or another device), and viewing preference data for the user (e.g., a user-selected content rating, or a preference determined by a viewing mode of the user). In some embodiments, the unified media browsing application aggregates all shared information to provide better and more cohesive interfaces and data sets for the user. In some embodiments, the unified media browsing application allows a user to browse content available on an electronic device via a content provider (e.g., CBS, fox, HBO, etc. or any other content provider), via a unified media browsing application's own services (e.g., iTunes Store maintained by Apple, inc. of Cupertino, california), or via the user's own account (e.g., previously purchased, currently rented, or otherwise owned content, which may be accessed from a server or stored locally on the electronic device). In some embodiments, the user is optionally able to scroll through or navigate within a list or grid of content that may be provided to the user, or otherwise search for such list or grid. The content list or grid is optionally ordered by recommendation based on aggregated user viewing preference data, the user's viewing history, or top-ranked or trending content items (e.g., based on how frequently the program was viewed, purchased, or discussed by other users). In some implementations, the unified media browsing application provides the user with an interface to select the content item that the user desires to view. Upon selection of a content item, the electronic device optionally determines a respective application from which the content item may be provided, launches the respective application, and causes playback of the selected content item. In some implementations, if multiple applications provide access to a content item, the electronic device automatically selects one of the applications to launch based on factors such as the user's preferences, the user's past usage history of the corresponding application, and the price of the content. In some implementations, the unified media browsing application does not launch the respective application, but rather causes playback within the unified media browsing application itself, without exiting the unified media browsing application or launching the respective application.

The manner in which applications are suggested and installed on an electronic device described above (e.g., automatically by determining a primary content provider for accessing content) allows the electronic device to provide a user with the ability to effectively install one or more suggested applications (e.g., using an interface without the user having to navigate to a separate application or interface and conduct research with respect to applications that are appropriate or popular with the user's primary content provider), which simplifies interactions between the user and the device and enhances the operability of the device, makes the user-device interface more efficient (e.g., by suggesting applications to be installed to the user and installing the suggested applications in response to a user's installation request for those applications), and, in addition, reduces power usage and extends the battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, determining the primary content provider for the electronic device includes automatically determining (710) the primary content provider, such as shown in fig. 6A, based on a predefined association of the electronic device with the primary content provider (e.g., a unique identifier that uniquely identifies the device using the primary content provider). For example, the serial number of the electronic device may optionally be linked or otherwise associated with the primary content provider. The association with the primary content provider optionally includes a primary content provider login credential of the client or user. In some embodiments, the association of the serial number of the electronic device with the primary content provider is stored on a server, and the electronic device determines the primary content provider by querying the server to retrieve the associated primary content provider. In some embodiments, the association is preprogrammed into the electronic device, and the electronic device determines the primary content provider by accessing the preprogrammed (e.g., stored in ROM, solid state storage, or any other suitable non-volatile memory). The predefined association is optionally set before an end user or consumer of the electronic device receives the electronic device. In other words, the predefined association is optionally independent of any user input of the electronic device, and is optionally a setting set by the vendor or manufacturer of the electronic device. The customer or user optionally purchases the electronic device from the primary content provider (e.g., unlike purchasing the device directly from the manufacturer, the manufacturer optionally is not associated with the primary content provider), and the primary content provider associates the unique identifier with the primary content provider and with the login credentials of the customer or user.

The above-described manner of determining the primary content provider of the electronic device (e.g., automatically based on a predetermined association with the primary content provider) allows the electronic device to be efficiently and automatically determined (e.g., by not requiring user input) while the electronic device is set up, which simplifies interactions between the user and the device, enhances operability of the device, and makes the user-device interface more efficient (e.g., by automatically determining the primary content provider without any user input, thereby avoiding user errors and misunderstanding, and ensuring a smooth and quick set-up procedure with less user input), and furthermore, by enabling the user to use the device more quickly and efficiently, reducing power usage, and extending battery life of the device.

In some embodiments, in response to receiving (712) an input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6B, the electronic device is authenticated to a primary content provider (e.g., the device successfully logs in to the primary content provider using user login credentials (or otherwise verifies that the user login credentials are valid for accessing content from the primary content provider)) in accordance with a determination (714) that the predefined association is successfully used and one or more unified media browsing application eligibility criteria, such as shown in fig. 6B (e.g., the unified media browsing application eligibility criteria include criteria requiring that the location or geographic location of the electronic device support for sharing content viewing information with the unified media browsing application and criteria requiring that the user of the electronic device possess a valid content access account (e.g., an itudes account and/or an Apple ID maintained by Cupertino, california)) are authorized (716) by the electronic device to use the primary content provider, such as shown in fig. 6B. Enabling single sign-on the electronic device optionally includes storing subscription data and/or login credentials of the user in a content access account setting of the user on the electronic device or on an external server. In some embodiments, authorizing the electronic device to use the primary content provider includes creating an authentication token after successfully authorizing use of the primary content provider. The authentication token is optionally stored on the electronic device or in a content access account setting of the user on an external server. In some embodiments, access to the authentication key can be granted to multiple applications or services. Granting access to the authentication key optionally allows the corresponding application or service to authenticate using credentials associated with the authentication token (e.g., if the authentication token has authenticated the device to the primary content provider, granting access allows other applications to access the same authentication to the primary content provider). In some embodiments, access to the authentication token may be granted if the corresponding application or service supports single sign-on authentication.

In some implementations, the credentials of the user are automatically determined when the electronic device determines the primary content provider. For example, the electronic device optionally queries the server using the serial number of the device and, in response to the query, receives login credentials of the primary content provider and the client or user at the primary content provider (e.g., via a lookup table). In some embodiments, the electronic device authenticates to the primary content provider using only the serial number of the electronic device (e.g., provides its serial number to the primary content provider, which authenticates (or does not authenticate) the serial number as an authenticated serial number) without using the user's account credentials at the primary content provider. In some embodiments, the content access account is an account or subscription with a respective entity to which the unified media browsing application corresponds (e.g., an account that allows a user to log in and use the unified media browsing application, which is optionally created and/or controlled by the respective entity), wherein the respective entity is different from the primary content provider and/or the secondary content provider. In some implementations, certain locations or geographic locations do not support sharing of content viewing information with unified media browsing applications. The location or geographic location of the electronic device may optionally be stored on the electronic device (e.g., an area code), or alternatively the electronic device may determine the current location of the device (e.g., query an internet service provider, query an IP address geolocation service, receive GPS data, or other suitable location determination mechanism). The content access account is optionally one account (e.g., apple ID) or a combination of two accounts (e.g., itudes and iTunes accounts). For example, if the geographic location of the device supports sharing viewing content information with the unified media browsing application and the user has a valid Apple ID, then the unified media browsing application eligibility criteria are met. In some embodiments, the unified media browsing application eligibility criteria is met if the geographic location of the device supports sharing viewing content information with the unified media browsing application and the user does not have a valid Apple ID but has a valid iTunes and ituud account.

In some embodiments, in response to receiving (712) an input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6B, authenticating the electronic device to a primary content provider (e.g., a standard that the device successfully logs in to the primary content provider using login credentials of a user (or otherwise verifies that the user's login credentials are valid for accessing content from the primary content provider)) in accordance with a determination (714) that the predefined association is successfully used and satisfying one or more unified media browsing application eligibility criteria, such as that shown in fig. 6B (e.g., the unified media browsing application eligibility criteria includes a criterion that requires the location or geographic location of the electronic device to support content viewing information with the unified media browsing application and a criterion that requires the user of the electronic device to possess a valid content access account (e.g., an itude account and/or itudes account and/or an app ID maintained by Cupertino, california) for the first application access to the electronic device user) and meeting one or more unified media browsing application eligibility criteria, such as that the electronic device (e.g., the token) can be authenticated to the primary content provider alone to the user's primary content provider without requiring the authorization of the respective application to access the primary content provider to the primary content provider (e.g., the user's authorization provider).

In some embodiments, in response to receiving (712) an input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6B, in accordance with a determination (714) that a predefined association was successfully used to authenticate the electronic device to a primary content provider (e.g., a standard that the device successfully logged in to the primary content provider using user login credentials (or otherwise verifies that user login credentials are valid for accessing content from the primary content provider)) and that one or more unified media browsing application eligibility criteria, such as shown in fig. 6B (e.g., the unified media browsing application eligibility criteria includes a standard that requires the location or geographic location of the electronic device to support sharing of content viewing information with a unified media browsing application and a standard that requires the user of the electronic device to have a valid content access account (e.g., an itudes account and/or an Apple ID maintained by cupertina, california) are met) and electronic device enablement (720) is met with a first application installed on the electronic device, such as shown in fig. 6B to share media viewing information with a first application, such as shown in the unified media browsing application is configured to share media viewing information with the primary application.

Sharing content viewing information with a unified media browsing application optionally includes sharing content catalogs available from respective content providers (e.g., included in a user's subscription, or capable of being purchased or rented), content that the user has previously viewed (e.g., user viewing history), content that the user is currently viewing (e.g., content that the user has started viewing and paused or is currently viewing on an electronic device or another device), and viewing preference data for the user (e.g., user-selected content ratings, or preferences determined by the user's viewing mode). In some embodiments, the unified media browsing application aggregates shared information from multiple content applications to provide a single aggregated interface for browsing content.

The manner in which the electronic device is set up (e.g., the device uses single sign-on, the primary content provider account uses single sign-on, and enabling sharing of information with a unified media browsing application is done in one step) described above allows the electronic device to provide the user with the ability to effectively set up the electronic device for optimal content viewing (e.g., enabling multiple features in one step without the user having to navigate to a separate application or interface to enable the same features), which simplifies interactions between the user and the device, enhances operability of the device, and makes the user-device interface more efficient (e.g., by setting up the device with multiple functions in response to a single user request), and which further reduces power usage and extends battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, in response to receiving (722) input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6E, in accordance with a determination (724) that the electronic device successfully uses the predefined association to authenticate to a primary content provider (e.g., the device successfully logs in to the primary content provider using a user's login credentials (or otherwise verifies that the user's login credentials are valid for accessing content from the primary content provider)) and does not satisfy one or more unified media browsing application eligibility criteria, such as shown in fig. 6E (e.g., optionally, a location or geographic location of the electronic device does not support sharing of content viewing information with the unified media browsing application), the electronic device authorizes (726) the electronic device to use the primary content provider, such as shown in fig. 6F (e.g., enables single sign-on to the primary content provider).

In some implementations, the credentials of the user are automatically determined when the electronic device determines the primary content provider. For example, the electronic device optionally queries the server using the serial number of the device and, in response to the query, receives login credentials of the primary content provider and the client or user at the primary content provider (e.g., via a lookup table). In some embodiments, the electronic device authenticates to the primary content provider using only the serial number of the electronic device (e.g., provides its serial number to the primary content provider, which authenticates (or does not authenticate) the serial number as an authenticated serial number) without using the user's account credentials at the primary content provider. In some embodiments, the unified media browsing application eligibility criteria are not met if the user of the electronic device does not have a valid content access account. In some embodiments, possession of a valid content access account includes possession of a valid Apple ID (maintained by Apple inc. Of Cupertino, california). In some embodiments, having a valid content access account includes having at least one or both of an ibud account and an iTunes account (both of Cupertino, apple inc. Of California). For example, if the geographic location of the device does not support sharing viewing content information with the unified media browsing application, the unified media browsing application eligibility criteria are not met whether or not a valid content access account exists. In some embodiments, the unified media browsing application eligibility criteria is not met if the geographic location of the device does not support sharing viewing content information with the unified media browsing application and the user does not have a valid Apple ID and/or does not have a valid itudes account. In some embodiments, authorizing the electronic device to use the primary content provider includes creating an authentication token after successfully authorizing use of the primary content provider.

In some embodiments, in response to receiving (722) input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6E, in accordance with a determination (724) that a predefined association was successfully used to authenticate the electronic device to a primary content provider (e.g., the device successfully logged in to the primary content provider using a user's login credentials (or otherwise verifying that the user's login credentials are valid for accessing content from the primary content provider)), and one or more unified media browsing application eligibility criteria are not met, such as shown in fig. 6E (e.g., optionally, the location or geographic location of the electronic device does not support sharing of content viewing information with the unified media browsing application), the electronic device grants (728) access to authorization for the first application to use the primary content provider to the electronic device, such as shown in fig. 6F (e.g., optionally enabling the primary content provider application to access its respective content using authorization for the electronic device to use the primary content provider (e.g., enabling the primary content provider application to use authentication), without requiring the user to authenticate the primary content provider to use the other user's credentials alone).

In some embodiments, in response to receiving (722) input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6E, in accordance with a determination (724) that the electronic device successfully uses the predefined association to authenticate to a primary content provider (e.g., the device successfully logs in to the primary content provider using a user's login credentials (or otherwise verifies that the user's login credentials are valid for accessing content from the primary content provider)) and does not satisfy one or more unified media browsing application eligibility criteria, such as shown in fig. 6E (e.g., optionally, a location or geographic location of the electronic device does not support sharing of content viewing information with the unified media browsing application), the electronic device foregoes (730) enabling sharing of content viewing information associated with the first application with the unified media browsing application installed on the electronic device, such as shown in fig. 6F (e.g., optionally, the primary content application does not configure sharing of data with the unified media browsing application).

In some implementations, the geographic location does not allow sharing of content viewing information with the unified media browsing application. In some embodiments, the user does not have a valid content access account. In some embodiments, sharing of content viewing information with the unified media browsing application can then be enabled if the geographic location later supports sharing of content viewing information with the unified media browsing application, and the user later obtains a valid content access account (e.g., meets one or more unified media browsing application eligibility criteria).

The manner in which the electronic device is set up (e.g., the device is set up using single sign-on and the primary content provider account is set up using single sign-on, done in one step) described above allows the electronic device to provide the user with the ability to effectively set up the electronic device for optimal content viewing (e.g., enabling multiple features in one step without the user having to navigate to a separate application or interface to enable the same features), which simplifies interaction between the user and the device, enhances operability of the device, and makes the user-device interface more efficient (e.g., by setting up the device with multiple functions in response to a single user request), and furthermore, reduces power usage and extends battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, in response to receiving (732) input corresponding to a request to install one or more suggested applications on the electronic device, such as shown in fig. 6J, the electronic device requests (734) manual authentication of the electronic device from the user of the electronic device to the primary content provider, such as shown in fig. 6K (e.g., providing a login screen or other mechanism for the user to provide login credentials to the electronic device to authenticate the electronic device to the primary content provider, such as shown in fig. 6K, in response to determining that the device did not successfully login to the primary content provider using the predefined association or the serial number of the electronic device), and meeting one or more unified media browsing application eligibility criteria, such as shown in fig. 6J (e.g., optionally, the location or geographic location of the electronic device supports sharing content viewing information with the unified media browsing application and the user owns a valid content access account).

For example, the serial number of the device may optionally be associated with the wrong primary content provider, the user no longer having a valid primary content provider account, or any other scenario that would result in unsuccessful authentication, such as the electronic device being unable to communicate with the primary content provider at this time due to a connection problem. For example, if the geographic location of the device supports sharing viewing content information with the unified media browsing application and the user has a valid Apple ID, then the unified media browsing application eligibility criteria are met. In some embodiments, the unified media browsing application eligibility criteria is met if the geographic location of the device supports sharing viewing content information with the unified media browsing application and the user does not have a valid Apple ID but has a valid iTunes and ituud account. In some embodiments, if the manual authentication is successful, the device is optionally capable of authorizing the device to use the primary content provider, granting access to authorization for the first application to use the primary content provider for the electronic device, and enabling sharing of content viewing information associated with the first application with the unified media browsing application (if one or more unified media browsing application eligibility criteria are met) (e.g., the device is optionally capable of performing all of the same functions as if authentication using the predefined association was successful). In some embodiments, the user can manually enable the single sign-on function after the manual authentication is successful.

The manner in which the electronic device is set (e.g., requesting manual authentication to the primary content provider if authentication using a predefined association is unsuccessful) described above allows the electronic device to provide the user with the ability to manually authenticate the device and effectively set the device for optimal content viewing (e.g., associating the device with the primary content provider without the user having to navigate to a separate application or interface to enable the same feature), which simplifies interaction between the user and the device, enhances operability of the device, and makes the user-device interface more efficient, and furthermore, by enabling the user to use the device more quickly and effectively, reduces power usage and extends battery life of the device.

In some embodiments, in response to receiving (736) an input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6O, in accordance with a determination (738) that the electronic device was not successfully authenticated to a primary content provider using a predefined association (e.g., the device was not successfully logged into the primary content provider using a login credential of a user or a serial number of the electronic device), and one or more unified media browsing application eligibility criteria are not met, such as shown in fig. 6O (e.g., optionally, a location or geographic location of the electronic device does not support sharing of content viewing information with the unified media browsing application and the user does not have a valid content access account), the electronic device installs (740) a first application associated with the primary content provider, such as shown in fig. 6P (e.g., an application of the primary content provider). In some embodiments, the electronic device discards installing other ones of the one or more suggested applications that are not applications of the primary content provider.

In some embodiments, in response to receiving (736) an input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6O, in accordance with a determination (738) that the electronic device was not successfully authenticated to a primary content provider using a predefined association (e.g., the device was not successfully logged into the primary content provider using a login credential of a user or a serial number of the electronic device), and one or more unified media browsing application eligibility criteria are not met, such as shown in fig. 6O (e.g., optionally, a location or geographic location of the electronic device does not support sharing of content viewing information with the unified media browsing application and the user does not have a valid content access account), the electronic device relinquishes (742) authorization for the device to use the primary content provider, such as shown in fig. 6P (e.g., single sign-on to the primary content provider is not enabled on the electronic device). In some implementations, the user can manually enable the single sign-on function in the future when one or more unified media browsing application eligibility criteria are met and the primary content provider is successfully authenticated (e.g., through manual authentication).

In some embodiments, in response to receiving (736) an input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6O, in accordance with a determination (738) that the predefined association was not successfully used to authenticate the electronic device to a primary content provider (e.g., the device was not successfully logged into the primary content provider using a login credential of a user or a serial number of the electronic device), and one or more unified media browsing application eligibility criteria are not met, such as shown in fig. 6O (e.g., optionally, a location or geographic location of the electronic device does not support sharing of content viewing information with the unified media browsing application and the user does not have a valid content access account), the electronic device relinquishes (744) access to authorization for the first application to use the primary content provider with the electronic device, such as shown in fig. 6P (e.g., the primary content provider application cannot use single sign-on authorization). In some embodiments, the user can later manually grant access to the single sign-on authorization after manually enabling the single sign-on function.

In some embodiments, in response to receiving (736) an input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6O, in accordance with a determination (738) that the electronic device was not successfully authenticated to the primary content provider using the predefined association (e.g., the device was not successfully logged into the primary content provider using a login credential of a user or a serial number of the electronic device), and one or more unified media browsing application eligibility criteria are not met, such as shown in fig. 6O (e.g., optionally, a location or geographic location of the electronic device does not support sharing of content viewing information with the unified media browsing application and the user does not have a valid content access account), the electronic device (746) enables sharing of content viewing information associated with the first application with the unified media browsing application installed on the electronic device, such as shown in fig. 6P (e.g., optionally, the primary content application is not configured to share data with the unified media browsing application). In some embodiments, sharing of content viewing information with the unified media browsing application can then be enabled if the geographic location later supports sharing of content viewing information with the unified media browsing application, and the user later obtains a valid content access account (e.g., meets one or more unified media browsing application eligibility criteria).

The manner in which the electronic device is configured (e.g., installing a primary provider application) described above allows the electronic device to provide a user with the ability to effectively configure the device for optimal content viewing (e.g., automatically installing the primary provider application for user use without the user having to navigate to a separate application or interface to download and install the application), which simplifies interactions between the user and the device, enhances operability of the device, and makes the user-device interface more efficient (e.g., requires less user input), and which, in addition, reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the predetermined association of the electronic device with the primary content provider includes an association (748) of a unique identifier of the electronic device with a user account for accessing content from the primary content provider, such as shown in fig. 6A (e.g., a serial number of the electronic device optionally linked or otherwise associated with the primary content provider). The association with the primary content provider optionally includes a primary content provider login credential of the client or user. For example, the user may optionally purchase the electronic device from the user's primary content provider (e.g., unlike purchasing the device directly from the manufacturer, which may optionally not be associated with the primary content provider), and the primary content provider associates the unique identifier with the user's login credentials or with the user's account only (e.g., on the primary content provider's server) before the electronic device is delivered to the user.

The above-described manner of associating an electronic device with a primary content provider (e.g., using a unique identifier to identify a user account for the primary content provider) allows the electronic device to be efficiently and automatically determined and authenticated to the primary content provider (e.g., without user input) while the electronic device is set up, which simplifies interactions between the user and the device, enhances operability of the device, and makes the user-device interface more efficient (e.g., by automatically determining the primary content provider, thereby avoiding user mistakes and misunderstandings, and ensuring a smooth and quick setup process with less user input), and furthermore, by enabling the user to use the device more quickly and efficiently, reducing power usage and extending battery life of the device.

In some embodiments, determining (750) a primary content provider for an electronic device includes receiving (752), via one or more input devices, user input selecting a primary content provider for the electronic device, such as shown in fig. 6R (e.g., providing a list of available primary content providers for user selection). The list of available primary content providers is optionally alphabetically or popularity ordered. In some embodiments, the user can search for the appropriate primary content provider by entering the primary content provider's name or partial name. In some embodiments, only primary content providers available at the geographic location or locations of the user can be selected. In some embodiments, if the geographic location contains only one primary content provider, the user is prompted to select only that one primary content provider. The user is prompted to select the primary content provider, optionally manually, because the electronic device has no predefined association (e.g., the user purchases the device from the manufacturer of the device instead of through the primary content provider) or, optionally, because the user has skipped a setup step for automatically determining the primary content provider based on the predefined association. For example, the device has a predefined association, but the user wants to set the device to use another primary content provider, such as if the device is purchased through the user's primary content provider, but is presented to the end user as a gift, with the end user subscribed to a different primary content provider.

The above-described manner of determining the primary content provider (e.g., manually selecting the primary content provider by the user) allows the electronic device to provide the user with the ability to accurately select which primary content provider is associated with the device (e.g., using the same setup interface, without the user having to complete automatic setup and navigate to a separate interface to change the primary content provider to the desired primary content provider, or without losing the benefit of setting up the device to use the associated primary content provider if there is no predefined association), which simplifies interactions between the user and the device, enhances operability of the device, and makes the user-device interface more efficient (e.g., by providing the user with the opportunity to select the primary content provider during initial device setup), and furthermore, which reduces power usage and prolongs battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, after receiving user input selecting a primary content provider, the electronic device receives (754), via one or more input devices, user input for using the user credentials to determine user input for authenticating the electronic device to the determined primary content provider, such as shown in fig. 6S (e.g., after the user selects the primary content provider, the electronic device provides a user name and password field to facilitate user input to log in or otherwise authenticate to the primary content provider, or in some embodiments, to facilitate a mechanism by which the user provides credentials for authenticating to the primary content provider).

In some embodiments, in accordance with a determination (756) that the user credentials were successfully used to authenticate the electronic device to the primary content provider (e.g., the electronic device successfully logged in to the primary content provider using the user-provided credentials for the primary content provider or authenticated to the primary content provider), the one or more suggested applications to be installed include a plurality of applications corresponding to a plurality of secondary content providers for accessing content from the plurality of secondary content providers that the user credentials were able to access at the primary content provider, such as shown in fig. 6T (e.g., each of the plurality of applications is associated with a respective secondary content provider). The application selected for inclusion in the plurality of applications optionally depends on content accessible within the user's subscription to the primary content provider. For example, the plurality of applications optionally include a CBS content application for accessing content from the CBS, an HBO content application for accessing content from the HBO, and the like. In some embodiments, the plurality of applications includes an application for a secondary content provider included in a user's bundle or subscription to the primary content provider. For example, if the user's primary content provider subscribes to include access to CBS and HBO, the plurality of applications optionally includes a CBS content application and an HBO content application. In some implementations, if the user's subscription to the primary content provider includes a first package of secondary content providers, the plurality of applications includes a first set of applications (e.g., for accessing the first package of secondary content providers). In some implementations, if the user's subscription to the primary content provider includes a second package secondary content provider (e.g., includes more channels or different channels than the first package), the plurality of applications includes a second set of applications that are different from the first set of applications (e.g., for accessing the second package secondary content provider).

The above-described method of suggesting applications to be installed on an electronic device (e.g., by suggesting applications for content sources included in a user's subscription to a primary content provider) allows the electronic device to provide a user with the ability to effectively install applications that are accessible due to the user's subscription (e.g., using one interface, without the user having to navigate to a separate application or interface, and conduct research as to which applications are included in the user's primary content provider), which simplifies interactions between the user and the device and enhances operability of the device, makes the user-device interface more efficient, and furthermore, reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the plurality of applications includes a predetermined number of most commonly used applications (758), such as those shown in fig. 6T (e.g., suggesting that the user install a most commonly used or popular secondary content provider application (e.g., CBS content application, HBO content application) corresponding to the primary content provider and the respective secondary content provider (e.g., CBS, HBO, fox, etc. or any other content provider) to which the user gives access to the primary content provider's subscription (e.g., the user's limited view package includes CBS and HBO)). The predetermined number of most commonly used applications is optionally 2, 4, 6, 9, 10 or any other number. In some embodiments, the suggested applications include applications where the user's subscription to the primary content provider does not provide the user with their access rights, and in some embodiments, the suggested applications include only applications where the user's subscription to the primary content provider does provide the user with their access rights.

The above-described manner of suggesting applications installed on an electronic device (e.g., by suggesting the most commonly or popular applications) allows the electronic device to provide a user with the ability to effectively install multiple popular applications (e.g., using an interface without the user having to navigate to a separate application or interface and study which applications are appropriate or popular with the user's primary content provider), which simplifies interactions between the user and the device and enhances the operability of the device, makes the user-device interface more efficient (e.g., by suggesting popular applications to be installed to the user), and, in addition, reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, in response to receiving (760) an input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6T, the electronic device authorizes (762) the electronic device to use a primary content provider, such as shown in fig. 6U (e.g., enables single sign-on to the primary content provider on the electronic device). In some embodiments, authorizing the electronic device to use the primary content provider includes creating an authentication token after successfully authorizing use of the primary content provider. In some embodiments, in response to receiving (760) input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6T, the electronic device grants (764) access to authorization of the electronic device to use a primary content provider for the installed plurality of applications, such as shown in fig. 6U (e.g., optionally enabling each of the installed plurality of applications to access its respective content using the authorization of the primary content provider by the electronic device (e.g., enabling the application to use an authentication token) without otherwise requiring the user to individually authenticate each application using the user's credentials at the primary content provider).

In some embodiments, in response to receiving (760) input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6T, in accordance with a determination that one or more unified media browsing application eligibility criteria are met, the electronic device enables (766) sharing content viewing information associated with the installed plurality of applications with the unified media browsing application installed on the electronic device, such as shown in fig. 6T (e.g., optionally configuring each of the plurality of applications to share data with the unified media browsing application). In some embodiments, the unified media browsing application eligibility criteria are met when the location or geographic location of the electronic device supports sharing of content viewing information with the unified media browsing application and the user of the electronic device has a valid content access account.

In some embodiments, in response to receiving (760) input corresponding to a request to install one or more suggested applications on an electronic device, such as shown in fig. 6T, in accordance with a determination that one or more unified media browsing application eligibility criteria are not met, the electronic device relinquishes (768) enabling sharing of content viewing information associated with the installed plurality of applications with the unified media browsing application installed on the electronic device, such as shown in fig. 6T (e.g., optionally, not configuring the content application to share data with the unified media browsing application). In some embodiments, sharing of content viewing information with the unified media browsing application can then be enabled if the geographic location later supports sharing of content viewing information with the unified media browsing application, and the user later obtains a valid content access account (e.g., meets one or more unified media browsing application eligibility criteria).

The manner in which the electronic device is set up (e.g., the device uses single sign-on, the primary content provider account uses single sign-on, and optionally enables sharing of information with a unified media browsing application, done in one step) described above allows the electronic device to provide the user with the ability to effectively set up the electronic device for optimal content viewing (e.g., enabling multiple features in one step without the user having to navigate to a separate application or interface to enable the same features), which simplifies interactions between the user and the device, enhances operability of the device, and makes the user-device interface more efficient (e.g., by setting up the device with multiple functions in response to a single user request), and furthermore, which reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the electronic device receives (770), via one or more input devices, input corresponding to a request to launch a corresponding application installed on the electronic device, such as described in fig. 6CC (e.g., a user selecting one of the applications to run). In some embodiments, the application is one of the suggested applications installed during device setup. In some embodiments, the application is installed manually by the user after initial device setup.

In some embodiments, in response to receiving (772) input corresponding to a request to launch a respective application, such as shown in fig. 6CC, in accordance with a determination that when input corresponding to a request to install one or more suggested applications on an electronic device is received, a user launches (774) the respective application without requesting user input to access or deny access to the determined primary content provider for use of the electronic device via the respective application (e.g., if the application is one of an application that was subscribed and installed during initial device setup and is authorized to access the determined primary content provider, or if the application corresponds to a secondary content provider whose subscription to the primary content provider provides its access rights at device setup (e.g., when the electronic device is authorized to use the primary content provider to enable single sign-on during setup, the secondary content provider is in a subscription package of the user to the primary content provider)), the electronic device launches (774) the respective application without requesting user input to grant or deny access to the respective application to the determined primary content provider for use of the electronic device, such as shown in fig. 6DD (e.g., the respective application may itself be authenticated and authorized to access the primary content provider). In this case, the application can optionally be launched without further input from the user.

In some embodiments, in response to receiving (772) input corresponding to a request to launch a respective application, such as shown in fig. 6EE, upon determining (776) that when input corresponding to a request to install one or more suggested applications on an electronic device is received, the user requests (778) user input to token or deny authorization of the respective application to use the determined primary content provider for single sign-on to the electronic device, such as shown in fig. 6EE, in response to receiving (778) input corresponding to the request to launch the respective application, such as shown in fig. 6EE, the user being unable to provide access to the secondary content provider for the primary content provider at the device set-up (e.g., when the electronic device is authorized to use the primary content provider to enable single sign-on during set-up), the secondary content provider being unable to be in the user's subscription package), the electronic device requests (778) user input to token or deny authorization of the respective application to use the determined primary content provider for single sign-on to the electronic device, such as shown in fig. 6 e.g., whether the user is queried for single sign-on to grant or denial of authentication of the FF.

In some embodiments, the corresponding application is included in the user's primary content provider package at the time of initial device setup, but is not otherwise suggested or otherwise installed during initial device setup. In some embodiments, the respective application is not included in the user's primary content provider package at the time of initial device setup, and thus the respective application is not suggested or installed during initial device setup, but is now included in the user's primary content provider package (e.g., the user has changed his or her subscription package or the bundle package has otherwise been changed to include the respective application). In some implementations, the respective application cannot access the authorization to use the primary content provider, or otherwise do not use the user's credentials at the primary content provider for separate authentication. In some embodiments, after receiving a user input indicating a desire to grant access to the respective application program for authorization of the electronic device to use the determined primary content provider, the electronic device grants access to the authorization for the electronic device and initiates the application program, which is then able to provide access to its corresponding content on the electronic device. If the user refuses to access the authorization of the device to use the primary content provider for the respective application, the user optionally must first manually authenticate the respective application to the primary content provider (e.g., use the user's primary content provider credentials), the respective application may only be able to provide access to its content, otherwise the respective application may not be able to provide access to its content.

The above-described manner of launching an application (e.g., launching an application without further user input if the application has access to single sign-on authentication, and requiring a user to authenticate the application if the application cannot access single sign-on) allows the electronic device to provide a convenient interface for the user to grant authorization (e.g., by requesting user input to grant or deny authorization when launching an application, without the user having to navigate to a separate application or interface to grant or deny authorization), which simplifies interactions between the user and the device, enhances operability of the device, and makes the user-device interface more efficient (e.g., by requesting user input when the user is likely to know what functions are required to be enabled or disabled), and, in addition, reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, determining (780) a primary content provider for the electronic device includes selecting (782) only one primary content provider as the determined primary content provider based on determining that the location of the electronic device is associated with the primary content provider, such as shown in fig. 6X (e.g., if the geographic location or location of the electronic device is only a single primary content provider, then optionally suggesting to the user whether the user wishes to authenticate to the primary content provider).

The above-described manner of setting up the electronic device (e.g., selecting the one of the primary content providers in the geographic location of the electronic device) allows the electronic device to provide a simple and convenient way for the user to select the appropriate primary content provider (e.g., without the user having to browse through a list of primary content providers that may not be relevant or otherwise search for the appropriate primary content provider), which simplifies interactions between the user and the device, enhances operability of the device, and makes the user-device interface more efficient (e.g., by suggesting the one primary content provider only when the user is likely to have a subscription to the one primary content provider), and furthermore, which reduces power usage and extends battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, after installing the one or more suggested applications, the electronic device displays (784) a representation of the first application associated with the primary content provider at a preferential location on a home screen of the electronic device, such as shown in fig. 6C (e.g., placing the primary content provider at a preferential location on the home screen relative to other applications installed on the electronic device). In some embodiments, the preferred location is a second location in the installed application grid. In some embodiments, the unified media browsing application is located at the first location in the installed application grid and the primary content provider application is placed next to the unified media browsing application on the home screen.

The above-described manner of organizing applications installed on an electronic device (e.g., by placing a primary content provider in a preferential location) allows the electronic device to provide a user with a simple and convenient way to find and access the primary content provider application (e.g., without the user having to browse or otherwise find the primary content provider application), which simplifies interactions between the user and the device, enhances operability of the device, and makes the user-device interface more efficient (e.g., places the application in a location that is easily found and accessed), and in addition, reduces power usage and extends battery life of the device by enabling the user to more quickly and efficiently use the device.

It should be understood that the particular order in which the operations in fig. 7A-7J are described is merely exemplary and is not intended to suggest that the described order is the only order in which the operations may be performed. Those of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. Additionally, it should be noted that the details of other processes described herein with reference to other methods described herein (e.g., method 900) are equally applicable in a similar manner to method 700 described above with reference to fig. 7A-7J. For example, the user interfaces, user interface elements, processes for suggesting and installing applications, processes for authorizing devices and applications to use primary content providers, sharing view data with unified media browsing applications, etc. described above with reference to method 700 have one or more features of the user interfaces, user interface elements, processes for suggesting and installing applications, processes for authorizing devices and applications to use primary content providers, sharing view data with unified media browsing applications, etc. described herein with reference to other methods (e.g., method 900). For the sake of brevity, these details are not repeated here.

The operations in the above-described information processing method are optionally implemented by running one or more functional modules in an information processing apparatus such as a general-purpose processor (e.g., as described in connection with fig. 1A-1B, 3, 5A-5B) or an application-specific chip. Furthermore, the operations described above with reference to fig. 7A to 7J are optionally implemented by the components depicted in fig. 1A to 1B. For example, determining operation 702, displaying operation 704, receiving operation 706, and installing operation 708 are optionally implemented by event sorter 170, event recognizer 180, and event handler 190. An event monitor 171 in the event sorter 170 detects a contact on the touch-sensitive surface 604 and an event dispatcher module 174 communicates the event information to the application 136-1. The respective event identifier 180 of the application 136-1 compares the event information to the respective event definition 186 and determines whether the first contact at the first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as a selection of an object on the user interface. When a respective predefined event or sub-event is detected, the event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update the application internal state 192. In some examples, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it will be apparent to one of ordinary skill in the art how other processes may be implemented based on the components depicted in fig. 1A-1B.

Quick set-up of set-top boxes

Users interact with electronic devices in a number of different ways, including interacting with media (e.g., music, movies, etc.) available (e.g., stored, or otherwise accessible) on the electronic device. For example, a user may browse and play media that is accessible on an electronic device. During device setup or after a factory reset, the electronic device provides an interface for guiding the user to complete the setup process. In some cases, the user of the electronic device has provided certain settings and information related to setting the electronic device to another electronic device. Accordingly, a user may wish to perform quick settings by transmitting settings and information from another electronic device to the electronic device being set. The embodiments described below provide a way for an electronic device to facilitate the transfer of settings and information from another electronic device during device settings, thereby enhancing user interaction with the electronic device. Enhancing interaction with the device reduces the amount of time required for the user to perform an operation, thereby reducing the power consumption of the device and extending the battery life of the battery-powered device. It will be appreciated that people use the device. When a person uses a device, the person is optionally referred to as a user of the device.

Fig. 8A-8 DD illustrate an exemplary manner in which an electronic device facilitates transmitting settings and information from another electronic device during device setup according to some embodiments of the present disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to fig. 9A-9F.

Fig. 8A illustrates an exemplary setup environment for an electronic device (e.g., electronic device 500 of fig. 5A) of which display 514 is a part or to which display 514 is connected. The device 500 optionally communicates (e.g., communicates unidirectionally or bidirectionally) with a remote control device (e.g., the remote controller 510 of fig. 5B) and a smart phone device (e.g., the multi-function device 511 of fig. 5A). In some embodiments, remote control 510 and multifunction device 511 are used as input devices for device 500. Display 514 optionally displays one or more user interfaces including various content. In the example shown in fig. 8A, the display 514 displays a setup interface 801. In some embodiments, the device 500 enters the device setup process and the display 514 displays a setup interface (e.g., in response to the device being first powered on or booted or after a factory reset). In some embodiments, display 514 displays an initial setup launch screen or other user interface, such as those described in fig. 6A, before proceeding to the quick setup procedure.

In some embodiments, the device 500 is capable of performing a quick setup procedure. The quick setup procedure optionally involves transmitting settings from a second device (e.g., multifunction device 511) to device 500 to facilitate, enhance, or otherwise accelerate the device setup process. In some embodiments, the user of device 500 has set a second device with applications and settings related to the settings of device 500. For example, device 511 optionally has installed application 1 (represented by icon 450 on smart phone display 804). In some implementations, the application 1 authenticates to a primary content provider (e.g., a cable television provider, a satellite provider, etc.). In some embodiments, the application 1 is a primary content provider application or an application for a secondary content provider that is included in a user's subscription to a primary content provider (e.g., CBS, fox, HBO, etc., or any other content provider) as part of a bundled service provided to the user. In some embodiments, the multifunction device 511 is authorized to use the primary content provider (e.g., single sign-on to the primary content provider is enabled on the multifunction device 511). In these scenarios, and optionally other scenarios, the quick setup program is optionally capable of retrieving primary content provider credentials or subscription information from the multifunction device 511 and transmitting data to the device 500 to facilitate setup of the device 500. In some embodiments, other data can be transmitted from the multifunction device 511 to the device 500, such as content access accounts (e.g., iCloud accounts and/or iTunes accounts and/or Apple IDs maintained by Apple Inc. of Cupertino, california) and installed applications (e.g., primary content provider applications, secondary content provider applications, or alternatively applications unrelated to the primary content provider).

Returning to fig. 8A, the device 500 optionally displays a quick setup interface 801. In some embodiments, the quick setup interface 801 includes a title 810 that conveys to the user the option to proceed to quick setup or manual setup. In some embodiments, title 810 is a text title or artwork (e.g., logo, picture, illustration, etc.). The quick setup interface 801 optionally includes a quick setup button 820 and a manual setup button 822. In some embodiments, the quick set button 820 is displayed more prominently (e.g., larger and/or contains text using a larger font) than the manual set button 822. In some embodiments, the quick settings interface 801 displays a settings representation 824, which represents a device for controlling settings. For example, in fig. 8A, the quick set button 820 has a current focus (as indicated by the dashed box within the quick set button 820), and thus the settings representation 824 displays a representation of the device 500 and the multifunction device 511 indicating that the multifunction device 511 is to be used to perform the settings of the device 500. In fig. 8A, the multifunction device 511 includes application 1 and the device has single sign-on enabled (e.g., the multifunction device 511 is authorized to use the primary content provider).

In fig. 8A-8B, a swipe of contact 808 from top to bottom has been detected on touch-sensitive surface 451 of remote control 510. In response, the device 500 moves the current focus from the quick set button 820 to the manual set button 822, as shown in fig. 8B. Thus, the device 500 modifies the settings representation 824 to display a representation of the remote control 510 that indicates that the remote control 510 is to be used to perform the settings of the device 500. In some embodiments, in response to detecting a swipe from top to bottom, display 514 updates title 810 to represent the manual settings option highlighted by the user. The display 514 optionally displays instructional text 823 that instructs the user how to make manual settings.

In fig. 8B-8C, a bottom-up swipe of contact 808 has been detected on touch-sensitive surface 451 of remote control 510. In response, the device 500 moves the current focus from the manual setup button 822 to the quick setup button 820, as shown in fig. 8C. Thus, device 500 modifies settings representation 824 to display representations of device 500 and multifunction device 511 that indicate that multifunction device 511 is to be used to perform settings for device 500. In some embodiments, in response to detecting a swipe from top to bottom, display 514 updates title 810 to represent the quick setup option highlighted by the user.

In fig. 8D, a click input of contact 808 has been detected on touch-sensitive surface 451 of remote control 510, while quick set button 820 is highlighted. In response, the device 500 optionally begins a quick setup procedure. The device 500 optionally displays on the display 514 an explanation for linking a second device (e.g., the multifunction device 511 for setting up the device 500) to the device 500, as shown in fig. 8E. For example, to make a quick setup, the device 500 optionally requests the user to unlock the multifunction device 511, enable a bluetooth connection on the multifunction device 511, and hold the multifunction device 511 in proximity to the device 500 (e.g., optionally establish a Near Field Communication (NFC) connection). In some embodiments, settings representation 824 is modified to include a preview of the pop-up settings card on the representation of multifunction device 511.

In some embodiments, the quick setup procedure will be performed when the user performs the requested steps (e.g., unlock the multifunction device 511, enable a bluetooth connection on the multifunction device 511, and place the multifunction device 511 in proximity to the device 500), as shown in fig. 8F. Thereby, a connection (e.g., device pairing) is optionally created between the multifunction device 511 and the device 500. In some embodiments, the device 500 updates the quick setup interface 801 to indicate that quick setup is in progress (e.g., updates the title 810). In some embodiments, in response to starting a quick setup of device 500 using multifunction device 511, multifunction device 511 displays setup card interface 807 overlaid on home screen interface 806 (or any other user interface displayed by device 511 at the beginning of the quick setup). The setup card interface 807 optionally includes a header 830 and a representation 840 of the device being setup. Representation 840 is optionally an image of device 500. In some embodiments, setup card interface 807 includes a setup button 850 and a cancel button 852. In some implementations, the cancel button 852 is not a button, but rather an exit icon (e.g., an "x" icon in the upper right hand corner of the setup card). In some embodiments, actuation of the cancel button 852 ends the quick setup procedure and the device 500 optionally displays an initial quick setup interface 801, similar to that described in fig. 8A, or the device 500 optionally makes a manual setup.

In fig. 8G, multifunction device 511 detects a tap of contact 808 on touch-sensitive surface 804, selects set button 850 and indicates that the user wishes to make a quick setting of device 1 (e.g., device 500) using device 2 (e.g., multifunction device 511). In response, the multifunction device 511 optionally updates the setup card interface 807 to display the content access account sharing card. In some embodiments, the multifunction device 511 determines whether the multifunction device 511 contains a content access account and what type of content access account. For example, the multifunction device 511 optionally includes an Apple ID account and/or an iTunes account and/or an iCloud account. In some embodiments, different content access accounts include different user settings and data. For example, the iTunes account optionally includes music or media settings and data, the itudes account optionally includes user settings such as contacts, calendars, mail, etc., and the Apple ID account optionally includes settings available on both iTunes and itudes accounts.

For example, in fig. 8H, the multifunction device 511 determines that the multifunction device 511 includes an Apple ID account, and the setup card interface 807 includes a switcher element 842 to enable or disable sharing of the Apple ID content access account with the device 500. The setup card interface 807 optionally includes descriptive text 844 (e.g., language settings, personal assistant data, location service data, device analysis, application analysis, wi-Fi information, etc.) of the content included in the share. In some embodiments, setup card interface 807 includes a continue button 854 and a cancel button 856. In some embodiments, the cancel button 856 is not a button, but rather an exit icon (e.g., the "x" icon in the upper right hand corner of the setup card). In some embodiments, actuation of the cancel button 856 ends the quick set up procedure and the device 500 optionally displays an initial quick set up interface 801, similar to that described in fig. 8A, or the device 500 optionally makes a manual setting.

In some embodiments, the multifunction device 511 determines that the multifunction device 511 does not include an Apple ID account, but includes an iCloud and iTunes account. Thus, the content access account sharing card optionally includes two switcher elements 842 to enable or disable sharing of the ibud and iTunes content access accounts with the device 500, respectively, independently. In some implementations, enabling or disabling sharing of the content access account (e.g., by a switcher element) results in modification of the descriptive text 844 to indicate which settings and data to share. For example, in FIG. 8I, the iCloud account switch element is switched to the "off" position, indicating that sharing of the iCloud account and its attendant settings with device 500 is not desired. In some embodiments, based on the switching selection of the switcher element 842, the corresponding content access account is transferred to the device 500 (e.g., if the iTunes account switcher element is enabled, the multifunction device 511 will transfer the iTunes account to the device 500, if the itudes account switcher element is enabled, the multifunction device 511 will transfer the itudes account to the device 500, and if both account switcher elements are enabled, the multifunction device 511 will transfer both accounts to the device 500), a procedure that will be described below.

Turning now to FIG. 8J, which illustrates the setup interface depicted in FIG. 8H, multifunction device 511 detects a tap of contact 808 on touch-sensitive surface 804. Thus, the multifunction device 511 will transmit content access account information to the device 511. In some implementations, transmitting the content access account information involves transmitting content access account login credentials (e.g., user name and password) and settings associated with the content access account (e.g., language settings, personal assistant data, location service data, device analysis, application analysis, wi-Fi settings, etc.). In some embodiments, the device 500 implements the same settings that are transmitted (e.g., the device 500 will use the same language settings or connect to the same Wi-Fi network).

In some embodiments, the multifunction device 511 next displays a setup card interface 807 for sharing primary content provider subscriptions and associated applications with the device 500, as shown in fig. 8K. In fig. 8K, setup card interface 807 includes switch buttons 846 for sharing provider 1 subscriptions and sharing associated applications, respectively. In some embodiments, setup card interface 807 also includes an application list 848 under the shared application switcher, which indicates which applications are to be shared with device 500. In some embodiments, the application list 848 includes a "View all" selectable link. FIG. 8L illustrates a tap of contact 808 detected on the "View all" link in application list 848. As a result, the setup card interface 807 displays a list of applications included to be shared with the associated switcher button of each application in fig. 8M. The user is optionally able to select which applications to share with the device 500 individually. Upon detection of a tap of contact 808 on the "done" button 860, the setup card interface 807 will return to displaying an interface for sharing primary content provider subscriptions and related applications, as shown in FIG. 8N.

In some embodiments, the suggested shared application is the most commonly used or popular secondary content provider application (e.g., CBS content application, HBO content application) corresponding to secondary content providers (e.g., CBS and HBO) included in the user's subscription to the primary content provider. For example, if a user's subscription to a primary content provider enables the user to access a first set of secondary content providers, the multifunction device 511 optionally suggests a first set of secondary content provider applications to be shared, and if a user's subscription to a primary content provider enables the user to access a second set of secondary content providers that are different from the first set (e.g., more or less channels or different channels), the multifunction device 511 optionally suggests a second set of secondary content provider applications that are different from the first set (e.g., more or less applications or different applications) to be shared.

In some embodiments, the multifunction device 511 determines to suggest the primary content provider in fig. 8N for sharing with the device 500 through a single sign-on feature enabled on the multifunction device 511. For example, the multifunction device 511 optionally enables single sign-on at the primary content provider (e.g., provider 1). Thus, the multifunction device 511 selects a primary content provider (e.g., provider 1) associated with the single sign-on feature for sharing with the device 500 on the setup card interface 807. In some implementations, the multifunction device 511 includes an authentication token associated with successful single sign-on authentication to the primary content provider. In some embodiments, transmitting the primary content provider subscription involves transmitting an authentication token from the multifunction device 511 to the device 500. In some embodiments, transmitting the primary content provider subscription involves transmitting user credentials (e.g., login and password) for the primary content provider to the device 500, and the device 500 performs its own authentication and authentication token creation.

In some embodiments, sharing an application with device 500 involves installing the application on device 500. In some embodiments, application packages are transmitted from multifunction device 511 to device 500 (e.g., if an application is installed on multifunction device 511), installation packages are transmitted from multifunction device 511 to device 500 (e.g., optionally installation packages stored on multifunction device 511 are transmitted, or multifunction device 511 downloads installation packages from an application store and transmits them to device 500), or alternatively multifunction device 511 sends commands to device 500 for device 500 to download and install an application from an application store (e.g., iTunes). In some embodiments, settings for the shared application and use are additionally transmitted to the device 500.

The quick set-up optionally ends after the multifunction device 511 has transmitted the provider 1 subscription and application to the device 500. At the end of the quick set-up, the device 500 optionally launches and displays the unified media browser application on the display 514, as shown in FIG. 8O. In some embodiments, as shown in fig. 8P, as a result of the setup process, device 500 installs the provider 1 application, installs the shared application, enables single sign-on (e.g., authorizes device 500 to use provider 1), logs one or more applications into single sign-on (e.g., grants access to single sign-on authentication of provider 1 applications), and enables sharing viewing data of provider 1 applications and the installed suggested applications with a unified media browsing application (as described in more detail in fig. 6T-6U and method 700). In some embodiments, device 500 creates an entertainment folder (represented by icon 818-4) and installs the shared application within the folder. For example, the user can display the content of the entertainment folder by clicking on the input selection icon 818-4, similar to the content described in FIG. 6V. In FIG. 8P, the provider 1 application (represented by icon 818-2) is installed in a preferred location on the user interface 802, rather than in the entertainment folder.

Fig. 8Q-8S illustrate another exemplary quick setup procedure in which single sign-on is not enabled on the multifunction device 511, but the multifunction device 511 includes an application (e.g., application 1) (shown by icon 450) that is authenticated separately using the user' S credentials at the primary content provider. In fig. 8Q, a click input of contact 808 is detected on touch-sensitive surface 451 of remote control 510 while quick set button 820 is highlighted. In response, the device 500 optionally begins a quick setup procedure. After the multifunction device 511 is paired with the device 500 (e.g., in a similar procedure as described in fig. 8E), the multifunction device 511 optionally displays the quick setup card 807 in fig. 8Q. In some embodiments, the quick setup card suggests a number of applications to be installed on the device 500, as shown in fig. 8Q. In some implementations, the suggested application is not associated with the primary content provider. The suggested application is optionally the most popular content application in iTunes store (maintained by Apple inc. Of Cupertino, california) regardless of the user's subscription to the primary content provider. In some implementations, the user can actuate the switch 872 to disable the installation of an application on the device 500. The user is optionally also able to select the "View all" link in the application list 874 to display an interface with a suggested application list to install, similar to that described in FIGS. 8L-8M. In fig. 8R, the multifunction device 511 detects a tap of contact 808 on the "continue" button 862, indicating that it is desired to install the suggested application and complete the setting.

In some embodiments, as shown in fig. 8S, as a result of the setup process, device 500 installs the shared application (but does not install the provider 1 application), but does not enable single sign-on (e.g., authorizing device 500 to use provider 1), does not sign-on one or more applications (e.g., grant access to single sign-on authentication of provider 1 application)), and does not enable sharing of viewing data of the installed shared application with the unified media browsing application. In some embodiments, device 500 creates an entertainment folder (represented by icon 818-4) and installs the shared application within the folder. For example, the user can display the content of the entertainment folder by clicking on the input selection icon 818-4, similar to the content described in FIG. 6V.

Fig. 8T-8Z illustrate another exemplary quick setup procedure in which single sign-on is not enabled on the multifunction device 511, but the multifunction device 511 includes an application (e.g., application 1) (shown by icon 450) that is authenticated separately using the user's credentials at the primary content provider. In fig. 8T, a click input of contact 808 is detected on touch-sensitive surface 451 of remote control 510, while quick set button 820 is highlighted. In response, the device 500 optionally begins a quick setup procedure. After the multifunction device 511 is paired with the device 500 (e.g., in a similar procedure as described in fig. 8E), the multifunction device 511 optionally displays the quick setup card 807 in fig. 8U. In fig. 8U, a quick setup card 807 provides a login interface to login to the primary content provider (e.g., provider 1). The login interface optionally includes a user name field 876 and a password field 878 for the user to enter credentials for the primary content provider. The login interface optionally includes a login button 864 and an exit button 866. When a tap of contact 808 is detected on "login" button 864, multifunction device 511 optionally verifies the credentials provided by the user at the primary content provider (if correct).

Responsive to verifying the user's credentials at the primary content provider (e.g., provider 1), the flash setup card 807 displays the subscription and application sharing interface in FIG. 8V. For example, in fig. 8V, the quick setup card 807 includes a switch for enabling setup of single sign-on for provider 1 on both device 500 and multifunction device 511, and a switch for installing the proposed application. With the switch enabled for setting single sign-on for both device 500 and multifunction device 511, multifunction device 511 will optionally authorize itself to use provider 1 (e.g., single sign-on enabled), and device 500 will optionally also authorize use of provider 1 (e.g., single sign-on enabled), resulting in both devices being authorized to use provider 1. In some embodiments, each device performs its own authorization independently of the other devices, or alternatively, one device performs the authorization and transmits the authorization to the other device (such as described above in fig. 8N). In some embodiments, as a result of enabling single sign-on, the multifunction device 511 and device 500 will grant access to single sign-on authentication for any application installed on the corresponding device included in the user's subscription to provider 1.

Fig. 8W illustrates an exemplary alternate quick setup card 807 for the subscription and application sharing interface. In FIG. 8W, the suggested application list includes an information icon 849 (e.g., instead of a "View all" link). Activating the information icon 849 will trigger the display of an application interface similar to that described in fig. 8M. Fig. 8X-8Y illustrate another exemplary alternate quick setup card 807 for subscription and application sharing interfaces. In fig. 8X, the suggested application list includes a scroll bar representing icons (e.g., logos, pictures, etc.) of suggested applications for installation. The icon scrollbar is optionally automatically moved from right to left (or alternatively left to right) as shown in fig. 8Y. In some embodiments, the user can perform a left-to-right swipe or a right-to-left swipe to scroll through a representation of the suggested application.

Returning to FIG. 8V, the multifunction device 511 detects a tap of contact 808 on the "continue" button 860 on the touch-sensitive surface 804, which indicates a desire to execute the selected option (e.g., set a single sign-on and/or install an application), and completes the setting. As a result of the setup process, as shown in fig. 8Z, device 500 installs the provider 1 application, installs the suggested application, enables single sign-on (e.g., authorizes device 500 and multifunction device 511 to use provider 1), logs one or more applications into single sign-on (e.g., grants access to single sign-on authentication of the provider 1 application and the suggested application), and enables sharing of viewing data of the provider 1 application and the installed suggested application with the unified media browsing application. In some embodiments, device 500 creates an entertainment folder (represented by icon 818-4) and installs the shared application within the folder. For example, the user can display the content of the entertainment folder by clicking on the input selection icon 818-4, similar to the content described in FIG. 6V. In FIG. 8Z, the provider 1 application (represented by icon 818-2) is installed in a preferred location on the user interface 802, rather than in the entertainment folder.

In some implementations, the device 500, after being set (e.g., as described above), displays the home screen interface 802 on the display 514, as shown in fig. 8 AA. For example, after a certain amount of time without user input, device 500 optionally enters a screen saver mode and replaces user interface 802 with a screen saver interface. In some embodiments, the device 500 enters the screen saver mode in response to a user request to enter the screen saver mode. For example, in fig. 8BB, display 514 displays screen saver a on screen saver interface 803. In fig. 8BB, device 500 detects a click of contact 808 on touch-sensitive surface 451 when in screen saver mode. In response to detecting the click, the device 500 optionally exits the screen saver mode. In some embodiments, if device 500 exits the screensaver mode after the device first displays the screensaver (e.g., device 500 has never previously displayed the screensaver), display 514 displays a screensaver download pop-up dialog box overlaid on home screen interface 802 (or any other user interface displayed by device 500 when the screensaver first displays), as shown in fig. 8 CC. In some embodiments, the screensaver download pop-up dialog includes a title 880 asking the user if he wishes to download the screensaver. In some embodiments, the screensaver download pop-up dialog includes a representation 882 of the screensaver just displayed (e.g., screensaver a). The representation is optionally a picture, snapshot or preview video of the screensaver. The screensaver download pop-up dialog optionally includes an "auto download" option button 884 and an "no download" option button 886. In some embodiments, selecting the "auto download" option results in an automatic periodic query and download of new screensavers (e.g., from an external server or from an application store). The automatic download of the screensaver may alternatively occur daily, weekly, monthly or at any other suitable frequency. In some embodiments, selecting the "not to download" option causes the device 500 to never automatically download a new screensaver. In some embodiments, when the device 500 is configured to never automatically download a new screensaver, the new screensaver is downloaded only upon manual request by the user. In fig. 8CC, while the "auto download" option button 884 is currently highlighted, the device 500 detects a click of contact 808 on the touch-sensitive surface 451, which indicates that the user wishes to automatically download the screen saver to the device 500. In some embodiments, after the user selects to download the screensaver automatically or not, the display 514 returns to the home screen interface 802 (or any other user interface displayed by the device 500 when the screensaver is first displayed), as shown in fig. 8 DD. By presenting the screensaver download dialog after the device 500 first displays the screensaver (e.g., as opposed to during the setup process of the device 500), the device 500 is better able to ensure that the user knows what the automatically downloadable screensaver is (e.g., because the device 500 only displays the screensaver A), thereby increasing the likelihood that the user makes a correct selection and increasing the efficiency of the human-machine interface.

Fig. 9A-9F are flowcharts illustrating methods 900 that facilitate transmitting settings and information from another electronic device during device setup according to some embodiments of the present disclosure. Method 900 is optionally performed on an electronic device (such as device 100, device 300, or device 500) as described above in connection with fig. 1A-1B, 2-3, and 5A-5B. Some operations in method 900 are optionally combined and/or the order of some operations is optionally changed.

As described below, method 900 provides a way to facilitate the transfer of settings and information from another electronic device during device setup. The method reduces the cognitive burden on the user when interacting with the device user interface of the present disclosure, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, improving the efficiency of user interaction with the user interface saves power and increases the time between battery charges.

In some embodiments, a first electronic device (e.g., a tablet, a smart phone, a wearable device, etc., such as device 511, and the display and/or the input device are touch screens included in those devices) in communication with a display and one or more input devices receives (902), via the one or more input devices, a request to share subscription information to a primary content provider with the second electronic device while performing a process for setting a second electronic device separate from the first electronic device (e.g., initializing or setting a set top box, such as device 100, device 300, or device 500 in communication with the first electronic device), via the one or more input devices, wherein subscription to the primary content provider allows access to content associated with the primary content provider on the second electronic device, such as shown in fig. 8K (e.g., a user requesting that a quick setting be performed via the first electronic device instead of a manual setting).

In some embodiments, the setting is a first power-on of the second electronic device. In some embodiments, the setting is performed after the second electronic device performs the factory reset. In some embodiments, the setup of the set-top box is initiated at the set-top box (e.g., via a remote control of the set-top box, or via another device that serves as a remote control of the set-top box, such as a smart phone (e.g., a first electronic device)), and then at some point after the start-up at the set-top box, at least a portion of the setup procedure for the set-top box is executed at the first electronic device (e.g., remotely from the set-top box). In some embodiments, the manual setting involves the user providing subscription information to the primary content provider to the second electronic device. The subscription information is optionally user account information associated with the primary content provider that allows the user to receive content (e.g., login information and/or content included in the user's bundle) from the primary content provider. In some implementations, subscription information can be used to log the device into the user's account with the primary content provider. The subscription information optionally enables a user to access one or more secondary content providers through subscriptions to the primary content provider. In some embodiments, the user has entered subscription information for the primary content provider on the first electronic device. For example, the first electronic device may optionally have one or more applications that access content using subscriptions with the primary content provider. If the user has provided the subscription information to the first electronic device, the quick setup of the second electronic device allows the user to share the subscription information stored on the first electronic device with the second electronic device and avoid redundancy.

In some embodiments, in response to receiving a request to share subscription information for a primary content provider with a second electronic device, the first electronic device transmits (904) the subscription information for the primary content provider to the second electronic device, wherein the subscription information for the primary content provider allows access to content associated with the primary content provider on the second electronic device, such as shown in fig. 8P (e.g., when a user requests to perform a quick setup of the second electronic device using the first electronic device, the first electronic device optionally determines whether the user has provided the subscription information for the primary content provider to the first electronic device). If the first electronic device has subscription information for the primary content provider, the first electronic device optionally transmits the subscription information to the first electronic device. The transmission is optionally performed using any suitable electronic communication protocol, such as Wi-Fi, bluetooth, or Near Field Communication (NFC) or any combination of protocols. In some implementations, determining whether the user has provided subscription information to the primary content provider includes determining whether the first electronic device is authorized to share subscription information with the secondary content provider (e.g., whether a single sign-on feature is enabled). If the devices are authorized to share subscription information, the first electronic device optionally retrieves subscription information from the single sign-on feature, shares the subscription information with the second electronic device, authorizes the second electronic device, and grants access to authorization to use the secondary content provider. In some embodiments, if the first electronic device is not authorized to share subscription information with the secondary content provider, the first electronic device determines whether the first electronic device has logged into a primary content provider account in an application (e.g., a primary content provider application or a secondary content provider application) installed on the first electronic device. In some embodiments, the first electronic device retrieves subscription information from the applications, shares the subscription information with the second electronic device, authorizes the second electronic device, and grants access to authorization to use the secondary content provider (e.g., enables a single sign-on feature on the second electronic device). In some embodiments, the quick setup process also communicates device settings and application-specific settings and suggests applications to be installed on the set-top box.

The above-described manner of performing settings for a set-top box (e.g., by requesting subscription information for a primary content provider from a first electronic device and transmitting the subscription information from the first electronic device to the set-top box) allows the first electronic device to perform faster settings for the set-top box (e.g., by transmitting settings that have been provided by a user to a second electronic device and without the user performing manual settings for the set-top box), which simplifies interactions between the user and the device, reduces setup time and effort for the set-top box, and makes the user-device interface more efficient (e.g., by eliminating redundant setup steps), and furthermore, which reduces power usage and extends battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, while performing a process for setting up a second electronic device using a first electronic device, the first electronic device receives (906), via one or more input devices, a request to share a plurality of content access accounts with the second electronic device (e.g., a user requesting the first electronic device to share a content access account stored on the first electronic device with the second electronic device, such as shown in fig. 8H (e.g., an ibud account and/or iTunes account and/or Apple ID maintained by Apple inc. Of Cupertino, california)), including a first content access account (908) using a respective content service, the first content access account enabling access to a first set of content from the respective content service, such as shown in fig. 8H (e.g., optionally an ibunes account or an iboudes account). In some embodiments, iTunes accounts enable access to media content such as movies, games, music, and the like. In some embodiments, the iboud account enables access to user settings and data, such as device settings, contacts, calendars, mail, and the like.

In some embodiments, the request is for one or more content access accounts. In some embodiments, during the setup process, the user can select which content access accounts to share with the second electronic device. In some embodiments, the content access account is an account or subscription with a respective entity to which the unified media browsing application corresponds (e.g., an account that allows a user to log in and use the unified media browsing application, which is optionally created and/or controlled by the respective entity), wherein the respective entity is different from the primary content provider and/or the secondary content provider. The content access account is optionally one account (e.g., apple ID) or a combination of two accounts (e.g., itudes and iTunes accounts).

In some embodiments, while performing a process for setting up a second electronic device using a first electronic device, the first electronic device receives (906), via one or more input devices, a request to share a plurality of content access accounts with the second electronic device, such as shown in fig. 8I (e.g., a user requesting the first electronic device to share a content access account stored on the first electronic device with the second electronic device (e.g., an itudes account and/or iTunes account and/or Apple ID maintained by Apple inc. Of Cupertino, california)), including a second content access account (910) using a respective content service that enables access to a second set of content from the respective content service that is different from the first set of content, such as shown in fig. 8H (e.g., in some embodiments, the other of the itudes account and itudes account).

In some embodiments, in response to receiving a request to share a plurality of content access accounts with a second electronic device, a first electronic device transfers (912) the plurality of content access accounts using the second electronic device to the second electronic device, wherein the plurality of content access accounts allow the second electronic device to access a first set of content and a second set of content from a respective content service, such as shown in fig. 8I (e.g., the transfer account provides the second electronic device with the ability to access the content on the second electronic device). In some embodiments, transferring accounts transfers information and data stored within those accounts. For example, transferring an iTunes account optionally provides a media purchase history to the second electronic device, and transferring an itudes account provides corresponding settings and data to the second electronic device. In some embodiments, the user can choose which account to transfer, and transferring only one of the one or more content access accounts will transfer only the corresponding content set. After transfer, the transferred account and the attendant account information and data may optionally be accessed on the second electronic device without any further data or input from the first electronic device (e.g., the account information is transferred entirely and the second electronic device may access the account and its settings independently of the first electronic device).

The manner in which the settings are performed for the set-top box described above (e.g., by transferring the content access account to the second electronic device) allows the first electronic device to perform faster settings for the set-top box (e.g., by transmitting content associated with the content access account), which simplifies interactions between the user and the device, reduces setup time and effort for the set-top box, and makes the user-device interface more efficient (e.g., by eliminating redundant setup steps), and furthermore, which reduces power usage and extends battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, one or more of the language preference setting, the personal assistant setting, the location sharing setting, the analysis sharing setting, and the network connection setting are transmitted 914 from the first electronic device to the second electronic device, such as shown in fig. 8H (e.g., transmitting the device and the user preference setting stored on the first electronic device), while the process for setting the second electronic device is performed using the first electronic device. In some embodiments, the language preference settings include a user's primary language, all user-selected languages, and user-preferred languages. In some embodiments, the personal assistant settings include personal assistant usage history (e.g., previous queries), personal assistant preferences, and other settings. In some implementations, the location sharing settings include device-level location service settings (e.g., whether device location information is collected and shared) and application-level location service settings (e.g., whether device location information is shared with an application). In some embodiments, the analysis sharing settings include preferences for sharing device or application usage, crashes, and errors or other useful analysis with a developer of the device or application. In some embodiments, the network connection settings include a preferred or saved Wi-Fi network ID and password.

The above-described manner of performing settings for a set-top box (e.g., by transmitting user settings to a second electronic device) allows a first electronic device to perform faster settings for the set-top box (e.g., by transmitting settings that have been set by a user to the second electronic device and without the user performing manual settings for the set-top box), which simplifies interactions between the user and the device, reduces setup time and effort for the set-top box, and makes the user-device interface more efficient (e.g., by eliminating redundant setup steps), and furthermore, which reduces power usage and extends battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, upon performing (916) a process for setting up a second electronic device using a first electronic device, such as shown in fig. 8F, in accordance with a determination that the first electronic device is authorized to use a primary content provider (e.g., single sign-on to the primary content provider is enabled on the first electronic device), the first electronic device provides (918) one or more suggested applications to be installed on the second electronic device based on the primary content provider, such as shown in fig. 8K (e.g., a suggestion content source-specific application, optionally included in a user's service package or bundled with the primary content provider).

Enabling single sign-on the electronic device optionally includes storing subscription data and/or login credentials of the user in a content access account setting of the user on the electronic device or on an external server. In some embodiments, authorizing the electronic device to use the primary content provider includes creating an authentication token after successfully authorizing use of the primary content provider. The authentication token is optionally stored on the electronic device or in a content access account setting of the user on an external server. In some embodiments, access to the authentication key can be granted to multiple applications or services. Granting access to the authentication key optionally allows the corresponding application or service to authenticate using credentials associated with the authentication token (e.g., if the authentication token has authenticated the device to the primary content provider, granting access allows other applications to access the same authentication to the primary content provider). In some embodiments, access to the authentication token may be granted if the corresponding application or service supports single sign-on authentication. In some embodiments, if the primary content provider is a first primary content provider, it is recommended to install the first set of applications. In some embodiments, if the primary content provider is a second primary content provider different from the first content provider, it is recommended to install a second set of applications (e.g., different applications or more or less applications) different from the first set of applications. In some embodiments, if the user's subscription to the primary content provider includes access to a first package of content sources, it is recommended to install the first set of applications. In some embodiments, if the user's subscription to the primary content provider includes access to a second package content source (e.g., a different channel or more or less channels) that is different from the first package content source, it is recommended to install a second set of applications (e.g., different applications or more or less applications) that is different from the first set of applications. In some embodiments, the suggested application is the highest scoring or popular application and is not associated with the primary content provider (e.g., the highest scoring or popular application within an application store accessible on the second electronic device is independent of the popularity of the application among subscribers of the determined primary content provider). The number of suggested applications to be installed is optionally one, two, six, nine, ten or more. In some embodiments, the recommended form of installing the applications is to display a representation of these applications to the user. For example, the user is optionally presented with an icon depicting the suggested application, or in some embodiments, a list of suggested applications. In some embodiments, the suggested application is the highest scoring or popular application of the determined subscribers of the primary content provider. In some embodiments, if the first electronic device is not authorized to use the primary content provider, it is not recommended to install any application.

In some embodiments, upon performing (916) a process for setting up a second electronic device using a first electronic device, such as shown in fig. 8F, the first electronic device installs (920) one or more suggested applications, such as shown in fig. 8P, on the second electronic device in response to receiving input corresponding to a request to install the one or more suggested applications on the second electronic device via one or more input devices (e.g., installing the one or more suggested applications optionally involves transmitting the application from the first electronic device to the second electronic device).

In some embodiments, installing an application involves downloading and installing an application from an external application server or provider (e.g., apple Store or iTunes maintained by Apple inc. Of Cupertino, california) without downloading and installing an application from the first electronic device (e.g., if the first electronic device does not have an application installed or if the proposed application is not compatible with the first electronic device). The installed one or more suggested applications are optionally authorized to use the primary content provider (e.g., as a whole, gaining access to the second electronic device's authorization to use the primary content provider) as part of the installation. In some embodiments, this installation authorizes the second electronic device to use the primary content provider and allows the installed one or more suggested applications to provide content on the second electronic device via the primary content provider and a corresponding respective second content provider to which the user gives access rights to the primary content provider's subscription. In some embodiments, the one or more suggested applications installed are further configured to share their viewing history data with a unified media browser application installed on the second electronic device as a result of the user requesting installation of the suggested application. In some embodiments, the user is able to select which suggested applications to install and which applications to not install.

The manner in which a set top box is provided described above (e.g., by suggesting and installing applications on a set top box) allows a first electronic device to provide a user with the ability to effectively install one or more suggested applications on a second electronic device (e.g., using an interface without the user having to navigate to a separate application or interface and conduct research on applications that are appropriate or popular with the user's primary content provider), which simplifies user-device interaction and enhances device operability, makes the user-device interface more efficient (e.g., by suggesting applications to be installed to the user and installing the suggested applications in response to a user's installation request for those applications), and, in addition, reduces power usage and extends device battery life by enabling the user to more quickly and efficiently use the device.

In some embodiments, upon performing (922) a process for provisioning a second electronic device using a first electronic device, such as shown in fig. 8F, in accordance with a determination that the first electronic device is not authorized to use the primary content provider (e.g., single sign-on to the primary content provider is not enabled on the first electronic device), the first electronic device provides (924) one or more suggested applications to be installed on the second electronic device that are not based on the primary content provider, such as shown in fig. 8R (e.g., the suggested applications are top scoring or popular applications and are not associated with the primary content provider (e.g., highest scoring or popular applications within an application store accessible on the electronic device, independent of popularity of the applications among subscribers of the determined primary content provider)).

In some embodiments, upon performing (922) a process for setting up a second electronic device using a first electronic device, such as shown in fig. 8F, the first electronic device installs (926) the one or more suggested applications, such as shown in fig. 8S, on the second electronic device (e.g., installing the one or more suggested applications optionally involves transmitting the applications from the first electronic device to the second electronic device) in response to receiving input corresponding to a request to install the one or more suggested applications on the second electronic device via the one or more input devices. In some embodiments, installing an application involves downloading and installing an application from an external application server or provider (e.g., apple Store or iTunes maintained by Apple inc. Of Cupertino, california) without downloading and installing an application from the first electronic device (e.g., if the first electronic device does not have an application installed or if the proposed application is not compatible with the first electronic device). In some embodiments, the installed one or more suggested applications are optionally unauthorized to use the primary content provider (e.g., do not gain authorized access to the secondary electronic device for use of the primary content provider). In some embodiments, the installed one or more suggested applications are optionally not configured to share their viewing history data with the unified media browser application.

The manner in which a set top box is set up described above (e.g., by suggesting and installing applications on the set top box) allows a first electronic device to provide a user with the ability to effectively install one or more suggested applications on a second electronic device when the first device is not authorized to use a primary content provider (e.g., using an interface without the user having to navigate to a separate application or interface and conduct research on applications that are appropriate or popular with the user's primary content provider), which simplifies interactions between the user and the device and enhances operability of the device, making the user-device interface more efficient (e.g., by suggesting applications to be installed to the user and installing the suggested applications in response to a user's installation request for those applications), and which, in addition, reduces power usage and extends battery life of the device by enabling the user to more quickly and effectively use the device.

In some embodiments, upon performing (928) a process for setting up a second electronic device using a first electronic device, such as shown in fig. 8F, in accordance with a determination (930) that the first electronic device is not authorized to use the primary content provider (e.g., single sign-on to the primary content provider is not enabled on the first electronic device) and an application authorized to use the primary content provider is installed on the first electronic device, such as shown in fig. 8T (e.g., a content application installed on the first electronic device that a user individually authenticates using credentials of the user at the primary content provider, rather than authenticating the content application using authorization to use the primary content provider for the device (because the authorization optionally does not exist)), in accordance with a determination that the primary content provider supports access to the primary content provider for one or more applications on the electronic device to allow the one or more applications to provide access to respective content on the electronic device (e.g., a primary content provider support single sign-on function), the first electronic device (e.g., a primary content provider support function), the first electronic device (e.g., a first electronic device) and the second electronic device, such as shown in fig. a suggested single sign-on function, are enabled for the first electronic device 932 and the second electronic device (e.g., a suggested V-on for the first device).

In some embodiments, if the primary content provider does not support granting authorized access to the first electronic device and/or the second electronic device to use the primary content provider (e.g., does not support a single sign-on function), then authorizing the first electronic device and/or the second electronic device to use the primary content provider is not suggested. In some embodiments, authorizing the first electronic device and the second electronic device to use the primary content provider is not suggested if the first electronic device does not install an application authorized to use the primary content provider or if an installed application authorized to use the primary content provider alone does not support a single sign-on function.

In some embodiments, upon performing (928) a process for setting up a second electronic device using a first electronic device, such as shown in fig. 8F, in accordance with a determination (930) that the first electronic device is not authorized to use the primary content provider (e.g., single sign-on to the primary content provider is not enabled on the first electronic device) and an application authorized to use the primary content provider is installed on the first electronic device, such as shown in fig. 8T (e.g., a content application installed on the first electronic device that a user individually authenticates using credentials of the user at the primary content provider, rather than authenticating the content application using authorization to use the primary content provider by the device (because the authorization optionally does not exist)), the first electronic device authorizes (934) the first electronic device and the second electronic device to use the primary content provider, such as shown in fig. 8Z (e.g., both the first electronic device and the second electronic device are suggested to be enabled for both single sign-on functions) in response to receiving input corresponding to a request to authorize the first electronic device and the primary content provider to use by the first electronic device via one or more input devices.

In some embodiments, one or more applications are installed on the second electronic device. In some embodiments, the installed one or more suggested applications are optionally authorized to use the primary content provider (e.g., as a whole, gaining authorized access to the secondary electronic device for use of the primary content provider) as part of the installation. In some implementations, this authorization allows the installed one or more applications to provide content on the second electronic device via the primary content provider and the corresponding respective second content provider for which the user is given access rights via the user's subscription to the primary content provider. In some embodiments, the installed one or more applications are further configured to share their viewing history data with a unified media browser application installed on the second electronic device.

The above-described manner of setting up a set-top box (e.g., by determining that a primary content provider uses an installed application that has been individually authorized to use the primary content provider and enabling single sign-on both electronic devices) allows the electronic device to provide the user with the ability to effectively initiate authorization of the electronic device (e.g., using one interface without the user having to navigate to a separate application or interface to perform the same function), which simplifies interactions between the user and the device, enhances operability of the device, and makes the user-device interface more efficient, and furthermore, reduces power usage and extends battery life of the device by enabling the user to more quickly and effectively use the device.

In some embodiments, in response to completion of the process for setting up the second electronic device, the second electronic device launches (936) a unified media browsing application, such as that shown in fig. 8O, installed on the second electronic device (e.g., upon completion of the setting, the set-top box will automatically launch and display the unified media browsing application). The above-described manner of launching the unified media browsing application (e.g., automatically upon completion of device settings) allows the electronic device to provide the user with the ability to effectively become familiar with the functionality of the device's new settings (e.g., by enabling the user to interact with the application immediately without the user having to navigate to a separate application or interface to search for and experience new functionality), which simplifies interactions between the user and the device, enhances the operability of the device, and makes the user-device interface more efficient, and furthermore, by enabling the user to use the device more quickly and effectively, reduces power usage and extends the battery life of the device.

In some embodiments, in response to (938) the second electronic device exiting the screen saver mode, in accordance with a determination that the electronic device has not previously exited the screen saver mode until the process for setting up the second electronic device is completed (e.g., exited the screen saver after the device first displayed the screen saver), the second electronic device requests (940) user input for defining one or more settings related to downloading the screen saver to the second electronic device, such as shown in fig. 8CC (e.g., the user is provided with an option to select how to download other screen savers to the second electronic device). In some embodiments, the user is able to select to automatically download the screensaver. In some embodiments, if the second electronic device previously exited the screensaver mode (e.g., rather than first activating the screensaver on the device), the user is not provided with an option to automatically download the screensaver.

The above-described manner of requesting user settings to further download the screensaver (e.g., immediately after the device first enters a screensaver mode and exits the screensaver) allows the second electronic device to provide the user with the ability to effectively define settings for downloading the screensaver (e.g., by requiring the user to define settings that are immediately after exiting the screensaver, thereby increasing the likelihood that the user knows the settings and making informed decisions without having to navigate to a separate application or interface to perform the same function), which simplifies interactions between the user and the device, enhances the operability of the device, and makes the user-device interface more efficient (e.g., by requesting to define the screensaver download settings), and furthermore, which reduces power usage and extends the battery life of the device by enabling the user to more quickly and effectively use the device.

It should be understood that the particular order in which the operations in fig. 9A-9F are described is merely exemplary and is not intended to suggest that the described order is the only order in which the operations may be performed. Those of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein with reference to other methods described herein (e.g., method 700) are equally applicable in a similar manner to method 900 described above with reference to fig. 9A-9F. For example, the user interfaces, user interface elements, processes for suggesting and installing applications, processes for authorizing devices and applications to use primary content providers, sharing view data with unified media browsing applications, etc. described above with reference to method 900 have one or more features of the user interfaces, user interface elements, processes for suggesting and installing applications, processes for authorizing devices and applications to use primary content providers, sharing view data with unified media browsing applications, etc. described herein with reference to other methods (e.g., method 700). For the sake of brevity, these details are not repeated here.

The operations in the above-described information processing method are optionally implemented by running one or more functional modules in an information processing apparatus such as a general-purpose processor (e.g., as described in connection with fig. 1A-1B, 3, 5A-5B) or an application-specific chip. Furthermore, the operations described above with reference to fig. 9A to 9F are optionally implemented by the components depicted in fig. 1A to 1B. For example, receive operation 902 and transmit operation 904 are optionally implemented by event sorter 170, event recognizer 180, and event handler 190. The event monitor 171 in the event sorter 170 detects a contact on the touch screen 804 and/or the touch-sensitive surface 451 and the event dispatcher module 174 communicates the event information to the application 136-1. The respective event identifier 180 of the application 136-1 compares the event information to the respective event definition 186 and determines whether the first contact at the first location on the touch screen and/or touch sensitive surface corresponds to a predefined event or sub-event, such as a selection of an object on the user interface. When a respective predefined event or sub-event is detected, the event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update the application internal state 192. In some examples, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it will be apparent to one of ordinary skill in the art how other processes may be implemented based on the components depicted in fig. 1A-1B.

As described above, one aspect of the present technology is to collect and use data from various sources to improve delivery of content to a user that may be of interest to the user. The present disclosure contemplates that in some examples, such collected data may include personal information data that uniquely identifies or may be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records related to the health or wellness level of the user (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying information or personal information.

The present disclosure recognizes that the use of such personal information data in the present technology may be used to benefit users. For example, the personal information data may be used to deliver targeted content of greater interest to the user. Thus, the use of such personal information data enables a user to have programmatic control over the delivered content. In addition, the present disclosure contemplates other uses for personal information data that are beneficial to the user. For example, health and fitness data may be used to provide insight into the overall health of a user, or may be used as positive feedback to individuals using technology to pursue health goals.

The present disclosure contemplates that entities responsible for gathering, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and/or privacy practices. In particular, such entities should exercise and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies may be readily accessed by a user and should be updated as the collection and/or use of data changes. The personal information of the user should be collected as legal and rational use of the entity and should not be shared or sold outside these legal uses. In addition, such collection/sharing should be performed after informed consent is received from the user. In addition, such entities should consider taking any necessary steps to defend and secure access to such personal information data and to ensure that other persons having access to personal information data adhere to their privacy policies and procedures. In addition, such entities may subject themselves to third party evaluations to prove compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to collect and/or access particular types of personal information data and to suit applicable laws and standards including specific considerations of jurisdiction. For example, in the united states, the collection or access of certain health data may be subject to federal and/or state law restrictions, such as the health insurance portability and liability act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be treated accordingly. Thus, different privacy practices should be maintained for different personal data types for each country.

In spite of the foregoing, the present disclosure also contemplates embodiments in which a user selectively prevents use or access to personal information data. That is, the present disclosure contemplates that hardware elements and/or software elements may be provided to prevent or block access to such personal information data. For example, with respect to content delivery services, the techniques of the present invention may be configured to allow a user to choose to "join" or "leave" to participate in the collection of personal information data during or at any time after registration with the service. As another example, the user may choose not to provide the targeted content delivery service with data associated with friends or content taste data. In addition to providing the "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to accessing or using personal information. For example, the user may be notified when the application is downloaded that his personal information data will be accessed and then be reminded again before the personal information data is accessed by the application.

Further, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use. Once the data is no longer needed, risk can be minimized by limiting data collection and deleting the data. Further, and when applicable, including in certain health-related applications, data de-identification may be used to protect the privacy of the user. De-identification may be facilitated by removing a particular identifier (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data at the city level instead of at the address level), controlling the manner in which data is stored (e.g., aggregating data across users), and/or other methods, where appropriate.

Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that the various embodiments may be implemented without accessing such personal information data. That is, various embodiments of the present technology do not fail to function properly due to the lack of all or a portion of such personal information data. For example, the content may be selected and delivered to the user by inferring preferences based on non-personal information data or absolute minimum amount of personal information such as content requested by a device associated with the user, other non-personal information available to the content delivery service, or publicly available information.

The foregoing description, for purposes of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application to thereby enable others skilled in the art to best utilize the invention and various described embodiments with various modifications as are suited to the particular use contemplated.

Claims

1. A method for installing one or more applications, the method comprising:

at an electronic device in communication with a display and one or more input devices:

determining a primary content provider for the electronic device, the primary content provider allowing access to content associated with the primary content provider on the electronic device;

after determining the primary content provider for the electronic device, displaying, on the display, one or more representations of one or more suggested applications to be installed on the electronic device, including a first application associated with the primary content provider, based on the determined primary content provider;

upon displaying the one or more representations of the one or more suggested applications, receiving, via the one or more input devices, a single input corresponding to a request to install the one or more suggested applications on the electronic device; and

in response to receiving the single input:

installing the one or more suggested applications on the electronic device; and

based on a determination that one or more criteria are met:

Authorizing the electronic device to use the primary content provider;

granting access to the authorization of the electronic device to use the primary content provider for the one or more suggested applications, wherein granting access to the authorization of the electronic device to use the primary content provider for the one or more suggested applications provides access to media content to the electronic device via the one or more suggested applications; and

enabling sharing of content viewing information associated with the one or more suggested applications with a unified media browsing application installed on the electronic device; and

after receiving the single input:

receiving the media content using the authorization for the electronic device to use the primary content provider via the one or more suggested applications at the electronic device; and

one or more representations of media content are displayed in the unified media browsing application based on the content viewing information associated with the one or more suggested applications.

2. The method of claim 1, wherein determining the primary content provider for the electronic device comprises automatically determining the primary content provider based on a predefined association of the electronic device with the primary content provider.

3. The method of claim 2, further comprising:

in response to receiving the single input corresponding to the request to install the one or more suggested applications on the electronic device:

in accordance with a determination that the predefined association was successfully used to authenticate the electronic device to the primary content provider and one or more unified media browsing application eligibility criteria were not met:

authorizing the device to use the primary content provider;

granting the first application access to the authorization for the electronic device to use the primary content provider; and

the method further includes relinquishing enabling sharing of content viewing information associated with the first application with a unified media browsing application installed on the electronic device.

4. The method of claim 2, further comprising:

in accordance with a determination that the predefined association was not successfully used to authenticate the electronic device to the primary content provider and one or more unified media browsing application eligibility criteria were met, a manual authentication of the electronic device to the primary content provider from a user of the electronic device is requested.

5. The method of claim 2, further comprising:

in accordance with a determination that the predefined association was not successfully used to authenticate the electronic device to the primary content provider and one or more unified media browsing application eligibility criteria were not met:

relinquishing authorization of the device to use the primary content provider;

relinquishing the authorization granting the first application access to the electronic device to use the primary content provider; and

6. The method of claim 2, wherein the predefined association of the electronic device with the primary content provider comprises an association of a unique identifier of the electronic device with a user account for accessing content from the primary content provider.

7. The method of claim 1, wherein determining a primary content provider for the electronic device comprises:

User input is received via the one or more input devices, the user input selecting the primary content provider for the electronic device.

8. The method of claim 7, further comprising:

upon receiving the user input selecting the primary content provider, receiving, via the one or more input devices, user input for authenticating the electronic device to the determined primary content provider using user credentials;

wherein in accordance with a determination that the user credentials were successfully used to authenticate the electronic device to the primary content provider, the one or more suggested applications to be installed include a plurality of applications corresponding to a plurality of secondary content providers for accessing content from the plurality of secondary content providers that the user credentials are capable of accessing at the primary content provider.

9. The method of claim 8, the plurality of applications comprising a predetermined number of most commonly used applications.

10. The method of claim 8, further comprising:

Authorizing the electronic device to use the primary content provider;

granting access to the installed plurality of applications to authorization of the electronic device to use the primary content provider;

in accordance with a determination that one or more unified media browsing application eligibility criteria are met, enabling sharing of content viewing information associated with the installed plurality of applications with a unified media browsing application installed on the electronic device; and is also provided with

In accordance with a determination that one or more unified media browsing application eligibility criteria are not met, enabling sharing of content viewing information associated with the installed plurality of applications with the unified media browsing application installed on the electronic device is abandoned.

11. The method of claim 10, further comprising:

receiving, via the one or more input devices, an input corresponding to a request to launch a respective application installed on the electronic device; and

in response to receiving the input corresponding to the request to launch the respective application:

in accordance with a determination that, upon receiving the single input corresponding to the request to install the one or more suggested applications on the electronic device, the user enables the user to access content via the respective application at credentials of the determined primary content provider, launch the respective application without requesting user input for granting or denying the respective application access to the authorization to use the determined primary content provider for the electronic device; and is also provided with

In accordance with a determination that, when the single input corresponding to the request to install the one or more suggested applications on the electronic device is received, the user does not enable the user to access content via the respective application at the determined credentials of the primary content provider:

user input is requested for granting or denying the respective application access to the authorization to use the determined primary content provider for the electronic device.

12. The method of claim 1, wherein determining the primary content provider for the electronic device comprises:

in accordance with a determination that the location of the electronic device is associated with only one primary content provider, the only one primary content provider is selected as the determined primary content provider.

13. The method of claim 1, further comprising displaying a representation of a first application associated with the primary content provider at a preferential location on a home screen of the electronic device after installing the one or more suggested applications.

14. The method of claim 1, wherein the one or more criteria comprise: criteria for successfully authenticating the electronic device to the primary content provider using a predefined association, and criteria for one or more unified media browsing application eligibility criteria being met.

15. The method of claim 1, wherein the content viewing information comprises user viewing activities associated with respective suggested applications.

16. An electronic device, comprising:

one or more processors;

a memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for:

after determining the primary content provider for the electronic device, displaying, on a display, one or more representations of one or more suggested applications to be installed on the electronic device, including a first application associated with the primary content provider, based on the determined primary content provider;

upon displaying the one or more representations of the one or more suggested applications, receiving, via one or more input devices, a single input corresponding to a request to install the one or more suggested applications on the electronic device;

In response to receiving the single input:

installing the one or more suggested applications on the electronic device;

and

Based on a determination that one or more criteria are met:

authorizing the electronic device to use the primary content provider;

after receiving the single input:

17. The electronic device of claim 16, wherein determining the primary content provider for the electronic device comprises automatically determining the primary content provider based on a predefined association of the electronic device with the primary content provider.

18. The electronic device of claim 17, wherein the one or more programs further comprise instructions for:

authorizing the device to use the primary content provider;

19. The electronic device of claim 17, wherein the one or more programs further comprise instructions for:

20. The electronic device of claim 17, wherein the one or more programs further comprise instructions for:

relinquishing authorization of the device to use the primary content provider;

21. The electronic device of claim 17, wherein the predefined association of the electronic device with the primary content provider comprises an association of a unique identifier of the electronic device with a user account for accessing content from the primary content provider.

22. The electronic device of claim 16, wherein determining a primary content provider for the electronic device comprises:

23. The electronic device of claim 22, wherein the one or more programs further comprise instructions for:

24. The electronic device of claim 23, the plurality of applications comprising a predetermined number of most commonly used applications.

25. The electronic device of claim 23, wherein the one or more programs further comprise instructions for:

authorizing the electronic device to use the primary content provider;

26. The electronic device of claim 25, wherein the one or more programs further comprise instructions for:

27. The electronic device of claim 16, wherein determining the primary content provider for the electronic device comprises:

28. The electronic device of claim 16, wherein the one or more programs further comprise instructions for: after installing the one or more suggested applications, a representation of a first application associated with the primary content provider is displayed at a preferred location on a home screen of the electronic device.

29. The electronic device of claim 16, wherein the one or more criteria comprise: criteria for successfully authenticating the electronic device to the primary content provider using a predefined association, and criteria for one or more unified media browsing application eligibility criteria being met.

30. The electronic device of claim 16, wherein the content viewing information includes user viewing activities associated with respective suggested applications.

31. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device, cause the electronic device to perform a method comprising:

In response to receiving the single input:

installing the one or more suggested applications on the electronic device;

authorizing the electronic device to use the primary content provider;

after receiving the single input:

32. The non-transitory computer-readable storage medium of claim 31, wherein determining the primary content provider for the electronic device comprises automatically determining the primary content provider based on a predefined association of the electronic device with the primary content provider.

33. The non-transitory computer readable storage medium of claim 32, wherein the one or more programs further comprise instructions for:

authorizing the device to use the primary content provider;

34. The non-transitory computer readable storage medium of claim 32, wherein the one or more programs further comprise instructions for:

35. The non-transitory computer readable storage medium of claim 32, wherein the one or more programs further comprise instructions for:

Relinquishing authorization of the device to use the primary content provider;

36. The non-transitory computer-readable storage medium of claim 32, wherein the predefined association of the electronic device with the primary content provider comprises an association of a unique identifier of the electronic device with a user account for accessing content from the primary content provider.

37. The non-transitory computer-readable storage medium of claim 31, wherein determining a primary content provider for the electronic device comprises:

38. The non-transitory computer readable storage medium of claim 37, wherein the one or more programs further comprise instructions for:

39. The non-transitory computer-readable storage medium of claim 38, the plurality of applications comprising a predetermined number of most commonly used applications.

40. The non-transitory computer readable storage medium of claim 38, wherein the one or more programs further comprise instructions for:

Authorizing the electronic device to use the primary content provider;

41. The non-transitory computer readable storage medium of claim 40, wherein the one or more programs further comprise instructions for:

42. The non-transitory computer-readable storage medium of claim 31, wherein determining the primary content provider for the electronic device comprises:

43. The non-transitory computer readable storage medium of claim 31, wherein the one or more programs further comprise instructions for: after installing the one or more suggested applications, a representation of a first application associated with the primary content provider is displayed at a preferred location on a home screen of the electronic device.

44. The non-transitory computer-readable storage medium of claim 31, wherein the one or more criteria comprise: criteria for successfully authenticating the electronic device to the primary content provider using a predefined association, and criteria for one or more unified media browsing application eligibility criteria being met.

45. The non-transitory computer-readable storage medium of claim 31, wherein the content viewing information includes user viewing activities associated with respective suggested applications.