Patent Grant
12242707
The present disclosure relates generally to computer user interfaces, and more specifically to techniques for displaying application views.
Many modern electronic devices provide the capability to select and open applications for accessing the content and functionality of the applications. Some techniques for selecting and opening applications are based on scrolling through many applications. These techniques can be cumbersome and inefficient.
Some techniques for selecting and opening applications using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for selecting and opening applications. Such methods and interfaces optionally complement or replace other methods for selecting and opening applications. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
In some embodiments, a method is performed at an electronic device with a display, one or more processors, memory, and a rotatable input mechanism, where the rotatable input mechanism is rotatable around a rotation axis substantially perpendicular to a normal axis that is normal to a face of the display. The method includes detecting a first user input, and, in response to detecting the first user input, displaying a first subset of application views of a set of application views, where the first subset of application views is displayed along a first dimension of the display that is substantially perpendicular to both the rotation axis and the normal axis. A rotation of the rotatable input mechanism is detected, and, in response to detecting the rotation of the rotatable input mechanism, a second subset of application views of the set of application views is displayed. Displaying the second subset of application views includes moving the set of application views on the display along the first dimension of the display.
In some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display and a rotatable input mechanism, where the rotatable input mechanism is rotatable around a rotation axis substantially perpendicular to a normal axis that is normal to a face of the display. The one or more programs include instructions for detecting a first user input, and, in response to detecting the first user input, displaying a first subset of application views of a set of application views, where the first subset of application views is displayed along a first dimension of the display that is substantially perpendicular to both the rotation axis and the normal axis. The one or more programs further include detecting a rotation of the rotatable input mechanism, and, in response to detecting the rotation of the rotatable input mechanism, displaying a second subset of application views of the set of application views, where displaying the second subset of application views includes moving the set of application views on the display along the first dimension of the display.
In some embodiments, a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display and a rotatable input mechanism, where the rotatable input mechanism is rotatable around a rotation axis substantially perpendicular to a normal axis that is normal to a face of the display. The one or more programs include instructions for detecting a first user input, and, in response to detecting the first user input, displaying a first subset of application views of a set of application views, where the first subset of application views is displayed along a first dimension of the display that is substantially perpendicular to both the rotation axis and the normal axis. The one or more programs further include detecting a rotation of the rotatable input mechanism, and, in response to detecting the rotation of the rotatable input mechanism, displaying a second subset of application views of the set of application views, where displaying the second subset of application views includes moving the set of application views on the display along the first dimension of the display.
In some embodiments, an electronic device includes a display, a rotatable input mechanism rotatable around a rotation axis substantially perpendicular to a normal axis that is normal to a face of the display, one or more processors, and memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for detecting a first user input, and, in response to detecting the first user input, displaying a first subset of application views of a set of application views, where the first subset of application views is displayed along a first dimension of the display that is substantially perpendicular to both the rotation axis and the normal axis. The one or more programs further include instructions for detecting a rotation of the rotatable input mechanism, and, in response to detecting the rotation of the rotatable input mechanism, displaying a second subset of application views of the set of application views, where displaying the second subset of application views includes moving the set of application views on the display along the first dimension of the display.
In some embodiments, an electronic device includes a display, a rotatable input mechanism rotatable around a rotation axis substantially perpendicular to a normal axis that is normal to a face of the display. The electronic device further includes means for detecting a first user input and means for, in response to detecting the first user input, displaying a first subset of application views of a set of application views, where the first subset of application views is displayed along a first dimension of the display that is substantially perpendicular to both the rotation axis and the normal axis. The electronic device further includes means for detecting a rotation of the rotatable input mechanism and means for, in response to detecting the rotation of the rotatable input mechanism, displaying a second subset of application views of the set of application views, where displaying the second subset of application views includes moving the set of application views on the display along the first dimension of the display.
Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
Thus, devices are provided with faster, more efficient methods and interfaces for selecting and opening applications, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for selecting and opening applications.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
There is a need for electronic devices that provide efficient methods and interfaces for selecting and opening applications. In one example, a device displays a plurality of application views that can be selected to open corresponding applications. The application views are navigated by rotating an input mechanism, which moves the application views on the display of the device. The arrangement and movement of the application views are intuitively aligned with the rotation of the input mechanism based on the physical configuration of the device. Such techniques can reduce the cognitive burden on a user who accesses applications on an electronic device, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
Below,
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “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 “includes,” “including,” “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.
The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the 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 a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that 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
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.
Peripherals interface 118 can 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 memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals 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.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoW), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), 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, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 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 embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over 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, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, 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 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.
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 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications 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 telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with 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, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with 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, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
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 workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
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 to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still 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 to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
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, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
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, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
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 for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, 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, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with 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 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this 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 as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, 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-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a 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 actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, 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 button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples that follow 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 that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Ser. No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Ser. No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including process 700 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments 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 the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
In some embodiments, the display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed in proximity of application icon 572B, as shown in
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to 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 hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
As used herein, the terms “open application” or “executing application” refer to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application is, optionally, any one of the following types of applications:
As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
Device 600 includes various input mechanisms that receive user input, such as, rotatable input mechanism 610, that is able to receive a rotatable input (and may also receive a push input), and input mechanism 612 that is able to receive a push user input. Rotatable input mechanism 610, as illustrated in
In response to detecting user input 620 at input mechanism 612, a plurality of application views of a set of application views 630 are displayed. In some embodiments, the plurality of application views are displayed in response to other types of user inputs, such as a tap or a swipe (e.g., a vertical swipe up or down) on touch-sensitive display 602. The set of application views 630 are a sequential list of application views that correspond to respective applications. The set of application views 630 can include any number of application views (e.g., ten application views) that correspond to a respective number of applications. In some embodiments, the number of application views in the set of application views is predefined.
As shown in
In some embodiments, in response to user input 620, device 600 displays a subset of the set of application views. The subset of application views are displayed along the first dimension of display 602 (e.g., substantially perpendicular to both rotation axis 614 and normal axis 615). According to the configuration of device 600 shown in
Referring now to
In some embodiments, as shown in
In some embodiments, in response to a user input (e.g., press of input mechanism 612) while displaying the set of application views, device 600 returns to the display that was displayed at the time the input that caused display of the set of application views was detected. In one example, in response to a press of input mechanism 612 while displaying the set of application views in
In some embodiments, each of the application views in the set of application views 630 is an affordance that, when selected, displays the application that corresponds to the application view (e.g., launches the corresponding application or, if the corresponding application is open and running in the background or suspended, switches the display to the application). For example, the selection (e.g., a touch input on the affordance) of application view 631 that corresponds with a workout application launches the workout application. Similarly, the selection of application view 634 that corresponds to a messages application launches the messages application. In some embodiments, the applications respectively corresponding to the set of application views 630 are stored in memory (e.g., volatile memory). As such, the applications corresponding to the respective application views in the set of application views 630 are quickly and easily accessed (e.g., launch instantaneously) in response to selection of the respective application view.
Referring again to
Alternatively, or in addition, to scrolling the application views using the rotatable input mechanism 610, in some embodiments, the set of application views are moved along the first dimension of the display in response to detecting a gesture (e.g., a swipe along the first dimension) on display 602. Optionally, device 600 displays scroll indicator 649 that indicates the position of the sequence of the set of application views that is displayed. The scroll indicator allows the user to quickly and easily determine what portion of the sequence of application views is being displayed. In
Scroll indicator 649 is updated in
In some embodiments, once an application view reaches the top edge of the display, it is no longer translated in response to further upward scrolling toward the end of the sequence of the set of application views. Instead, it remains at the top of the display and is covered by the adjacent application view below it. In some embodiments, after an application view reaches the top edge of the display, it continues to be reduced in size (e.g., appears to move back into the display, without translating) in response to further scrolling toward the end of the sequence of the set of application views. Conversely, in response to scrolling toward the beginning of the sequence of the set of application views, previously hidden application views towards the beginning of the sequence of the set of application views are revealed at the top of the display as adjacent application views move downward. In other embodiments, the application views continue to translate up off the display after reaching the top edge of the display. Conversely, in response to downward scrolling, previously hidden application views towards the beginning of the sequence of the set of application views translate downward onto the display from the top edge of the display.
Referring now to
In some embodiments, in response to receiving a rotation of rotatable input mechanism 610 or a vertical swipe gesture on the display, device 600 scrolls the application views based on the velocity of the rotation or swipe gesture, respectively (e.g., a faster rotation or swipe will result in faster scrolling). In some embodiments, scrolling continues after user input has ceased (e.g., if the velocity of the rotation or swipe gesture exceeds a predetermined velocity). In some embodiments, scrolling the application views includes a decrease in velocity after input has ceased. For example, the speed of the scrolling slows down over time, where the slowing down of the scrolling is based on a coefficient of friction.
Referring now to
In other embodiments, in response to user input 625, device 600 displays an application view removal user interface, as shown in
Referring now to
In some embodiments, the transition from displaying the set of application views 630 to displaying the menu of applications 642 includes an animation. In one example, illustrated by the sequence shown in
Referring now to
In some embodiments, the affordance 641 for displaying the menu of applications indicates the style of the menu of applications that will be displayed upon selection of the affordance. Optionally, the appearance of affordance 641 for displaying the menu of applications is changed to reflect the currently selected menu style.
In some embodiments, device 600 is configured to operate in what may be referred to as a “Favorites” mode in which the set of application views 630 includes preselected application views. The preselected application views are application views corresponding to respective applications, where the respective applications have been preselected such that their corresponding application views are displayed in response to user input (e.g., user input 614). As a result, the set of application views 630 provides quick and easy access to the applications that have been preselected. In one example, application views 631-635 described above are preselected application views because they have been affirmatively selected to be in the set of application views 630. In some embodiments, a user of device 600 affirmatively selects the applications (or application views) that are a part of the set of application views 630 (e.g., the user designates “favorite” applications). In some embodiments, a user selects the applications using a user interface provided on device 600 or an external device (e.g., via an application on a companion device in communication with device 600).
In other embodiments, a party (other than the user) selects one or more applications (or application views) (e.g., “default” preselected applications) prior to shipping of the device for commercial sale or initial use by the user. In some embodiments, a user of device 600 selects an order (e.g., sequence) of the application views in the set of application views. In other embodiments, a party (other than the user) selects an order of the application views in the set of application views (e.g., a “default” sequence) prior to shipping of the device for commercial sale or initial use by the user. In some embodiments, a user of device 600 can select and/or change the order of the application views in the set of application views using device 600 or an external device.
In some embodiments, the preselected application views remain in the set of application views regardless of the operational state of the respective application. The various operational states of the application can be a launched (e.g., to become opened) application, an open or executing application, or a closed application. In particular, an open or executing application can be, but is not limited to (1) an active application, which is currently displayed on a display screen of the device on which the application is being used, (2) a background application (or background process(es)), which is not currently displayed, but for which one or more processes are being processed by one or more processors, and (3) a suspended or hibernated application, which is not running, but has state information that is stored in memory (volatile and non-volatile, respectively) and that can be used to resume execution of the application. As a result, in some embodiments, the preselected application views are able to be displayed regardless of the operational state of the application.
In some embodiments, the techniques described above are applied when application views 631-635 are preselected application views. In one example, referring to
In another example, referring to
In some embodiments, the preselected application views remain in the set of application views until affirmatively removed by the user. In some embodiments, a preselected application view is removed from the preselected application views by applying the process of removing an application view described above with reference to
In some embodiments, as seen in
In
In some embodiments, the calendar application is an open application on the device and is not a view in the set of application views. While the calendar application is open and displayed as shown in
In some embodiments, device 600 displays the adaptive application view at a terminus (e.g., beginning or end) of the sequence of the set of application views. Alternatively, the adaptive application view is not displayed at the terminus of the sequence of application views. In some embodiments, the set of application views includes more than one adaptive application view that respectively correspond to the most recently opened applications. In some embodiments, the adaptive application view is displayed even when user input to display the set of application views is detected while an application is not open. In some embodiments, the adaptive application view is displayed only when user input to display the set of application views is detected while an application is open, or only while an application is displayed.
In some embodiments, as shown in
Furthermore, a subsequent new application, which is also not associated with the preselected application views, may be launched (or opened). In response to detecting the launch of the new application, which is also not associated with the preselected application views, the adaptive application view is updated to correspond with the new most recently opened application. For example, when a weather application is the most recently opened application (and not associated with the preselected application views) then device 600 updates adaptive application view 636 such that it corresponds with the weather application (rather than the previous recently opened application, such as the calendar application). In some embodiments, the adaptive application view permits a user to quickly access a recently used application, without having to perform the steps necessary to add the application to the set of preselected application views.
Referring now to
Affordance 647 corresponds to adding the adaptive application view 636 to the preselected application views of the set of application views. In response to receiving user input (e.g., tap gesture) for selecting the affordance 647, the adaptive application view (e.g., application view 636) that corresponds to the most recently opened application (e.g., calendar application) is added to the preselected application views. For example, referring to
In some embodiments, an open application corresponds to one of the preselected application views 631-635, and in response to a user input for displaying the set of application views, device 600 displays an adaptive application view corresponding to the open application at the top of the display of the set of application views while also maintaining the preselected application view corresponding to the open application.
Referring now to
As mentioned, an opened application refers to an application that was a launched or open application at some point in time, regardless of whether the application is still open or the application is closed. In some embodiments, the plurality of adaptive application views correspond to a predetermined number (e.g., ten) of most recently opened applications. Optionally, the adaptive application views are arranged in a sequence in order of how recently their corresponding applications have been opened.
In some embodiments, in
Next, a music application corresponding to adaptive application view 633 is opened and displayed, as shown in
Next, as shown in
As described below, method 700 provides an intuitive way for selecting and launching applications. The method reduces the cognitive burden on a user for selecting and launching applications, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to select and launch applications faster and more efficiently conserves power and increases the time between battery charges.
At block 702, the device detects a first user input (e.g., user input 620 in
At block 704, in response to detecting the first user input, the device displays a first subset of application views (e.g., 631 and 632) of a set of application views (e.g., 630). According to block 706, the first subset of application views is displayed along a first dimension (e.g., 616) of the display that is substantially perpendicular to both the rotation axis (e.g., 614) of the rotatable input mechanism and the normal axis (e.g., 618) to the display. Displaying the subset of application views along a dimension of the display that is substantially perpendicular to both the rotation axis of the rotatable input mechanism and the normal axis to the display arranges the application views substantially parallel to the plane of rotation of the rotatable input mechanism, which provides an intuitive alignment between the display of the set of application views and the rotatable input mechanism. This alignment provides visual feedback to the user that there is a relationship between the set of application views and the rotatable input mechanism and that the rotatable input mechanism can be used (e.g., rotated) to navigate (e.g., scroll) the set of application views. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
Optionally, at blocks 708 and 710, displaying the first subset of application views includes displaying at least a partial view of a first application view (e.g., 632 in
In some embodiments, the set of application views includes a plurality of preselected application views and an adaptive application view (e.g., 636) corresponding to a most recently opened application that does not correspond to a preselected application view. Optionally, displaying the first subset of application views includes displaying the adaptive application view and at least one of the preselected application views (e.g.,
In some embodiments, the set of application views includes a plurality of adaptive application views corresponding to a plurality of opened applications (e.g.,
Optionally, at block 714, the device displays an animation of a screenshot of an open application moving along the first dimension of the display and/or reducing in size (e.g., as at least part of displaying an adaptive application view that corresponds to the open application, such as when the first user input is detected while displaying the open application, as shown for example in
At block 716, the device detects a rotation (e.g., user input 621) of the rotatable input mechanism.
At block 718, in response to detecting the rotation of the rotatable input mechanism, the device displays a second subset of application views (e.g., 631, 632, and 633) of the set of application views. At block 720, displaying the second subset of application views includes moving the set of application views on the display along the first dimension of the display (e.g.,
Displaying the second subset of application views by moving the set of application views on the display along the first dimension of the display provides improved visual feedback to the user when scrolling the set of application views. Since the first dimension is substantially parallel to the plane of rotation of the rotatable input mechanism, moving the set of application views on the display along the first dimension of the display provides an intuitive response to the rotation of the rotatable input mechanism. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
Optionally, at block 722, moving the set of application views on the display along the first dimension of the display includes translating the set of application views along the first dimension of the display and changing the size of the application views as the application views translate along the first dimension of the display (e.g.,
In some embodiments, translating the set of application views along the first dimension of the display and changing the size of the application views as the application views translate along the first dimension of the display provides the user with improved visual feedback and reduces the amount of user input by allowing a greater number of application views on the display at one time and reducing the movement of the application views while scrolling. This allows quicker and more efficient navigation of the set of application views and reduces the possibility of a user being disoriented. Providing improved visual feedback to the user and reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the set of application views includes preselected application views. In some embodiments, the set of application views includes an adaptive application view (e.g., 636) that corresponds to a most recently opened application that is not one of the preselected application views. Optionally in such embodiments, at block 724, displaying the second subset of application views includes displaying the adaptive application view and an affordance (e.g., 647) for adding the adaptive application view to the preselected application views. Optionally, at blocks 726 and 728, the device detects a second user input (e.g., 654) corresponding to selection of the affordance for adding the adaptive application view to the preselected application views, and in response to detecting the second user input corresponding to selection of the affordance for adding the adaptive application view to the preselected application views, adds the adaptive application view that corresponds to the most recently opened application to the preselected application views. Adding the adaptive application view corresponding to the most recently opened application to the preselected application views in the manner described in blocks 724, 726, and 728 reduces the number of inputs required to add an application view to the preselected application views while displaying the set of application views. The benefits of reducing the number of inputs required to perform an operation are described above.
In some embodiments, the display includes a touch-sensitive display. Optionally, at blocks 730 and 732, the device detects a gesture (e.g., 625) on the touch-sensitive display corresponding to selection of a first application view of the set of application views (e.g., a swipe on the first application view in a direction perpendicular to the first dimension), and in response to detecting the gesture, deletes the first application view from the set of application views. Deleting the first application view from the set of application views in the manner described in blocks 730 and 732 reduces the number of inputs required to delete an application view from the set of application views while displaying the set of application views. The benefits of reducing the number of inputs required to perform an operation are described above.
Optionally, at blocks 734 and 736, the device detects a third user input (e.g., 623) corresponding to selection of an application view of the set of application views, and in response to detecting the third user input corresponding to selection of the application view, displays the application associated with the selected application view (e.g.,
Optionally, at blocks 738 and 740, in embodiments in which the display includes a touch-sensitive display, the device detects a second gesture (e.g., 622) on the touch-sensitive display, and in response to detecting the second gesture on the display, displays a third subset of application views (e.g., 632, 633, and 634 in
Optionally, at blocks 744, 746, 748, 750, and 752, the device displays an affordance (e.g., 641) for displaying a menu of applications (e.g., 642), detects a fourth user input (e.g., 628) corresponding to selection of the affordance for displaying the menu of applications, and in response to detecting the fourth user input corresponding to selection of the affordance for displaying the menu of applications: (i) ceases to display the set of application views and (ii) displays the menu of applications (e.g.,
Optionally, at blocks 754, 756, and 758, in embodiments in which the display includes a touch-sensitive display, while displaying the menu of applications, the device detects a contact (e.g., 629) on the touch-sensitive display and determines a characteristic intensity of the contact. Optionally, at block 760, in accordance with a determination that the characteristic intensity exceeds a predetermined intensity threshold, the device displays a second menu of applications (e.g., 645). The method of displaying a second menu of applications as described at blocks 754, 756, 758, and 760 provides an easy way to switch the display from a first menu of application to the second menu of applications and reduces the number of inputs to switch the menu of applications while displaying the first menu of applications. The benefits of reducing the number of inputs required to perform an operation are described above. Optionally, at block 762, in accordance with a determination that the characteristic intensity does not exceed the predetermined threshold, the device launches an application.
The foregoing description, for purpose 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 view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
This application claims priority to U.S. Provisional Patent Application No. 62/506,548, filed May 15, 2017, titled “DISPLAYING A SET OF APPLICATION VIEWS,” the content of which is hereby incorporated by reference in its entirety. This application relates to U.S. Provisional Patent Application No. 62/348,849, entitled “DISPLAYING AND UPDATING A SET OF APPLICATION VIEWS,” filed on Jun. 10, 2016, the content of which is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 102663 | Dillen | May 1870 | A |
| 4761642 | Huntzinger | Aug 1988 | A |
| 4885704 | Takagi et al. | Dec 1989 | A |
| 4896291 | Gest et al. | Jan 1990 | A |
| 5140678 | Torres | Aug 1992 | A |
| 5146556 | Hullot et al. | Sep 1992 | A |
| 5202961 | Mills et al. | Apr 1993 | A |
| 5227771 | Kerr et al. | Jul 1993 | A |
| 5229852 | Maietta et al. | Jul 1993 | A |
| 5237653 | Noguchi et al. | Aug 1993 | A |
| 5287447 | Miller et al. | Feb 1994 | A |
| 5333256 | Green et al. | Jul 1994 | A |
| 5347295 | Agulnick et al. | Sep 1994 | A |
| 5384911 | Bloomfield | Jan 1995 | A |
| 5412776 | Bloomfield et al. | May 1995 | A |
| 5416895 | Anderson et al. | May 1995 | A |
| 5428730 | Baker et al. | Jun 1995 | A |
| 5463725 | Henckel et al. | Oct 1995 | A |
| 5487143 | Southgate | Jan 1996 | A |
| 5499334 | Staab | Mar 1996 | A |
| 5500936 | Allen et al. | Mar 1996 | A |
| 5557724 | Sampat et al. | Sep 1996 | A |
| 5560022 | Dunstan et al. | Sep 1996 | A |
| 5561811 | Bier | Oct 1996 | A |
| 5581670 | Bier et al. | Dec 1996 | A |
| 5583984 | Conrad et al. | Dec 1996 | A |
| 5657049 | Ludolph et al. | Aug 1997 | A |
| 5659693 | Hansen et al. | Aug 1997 | A |
| 5721850 | Farry et al. | Feb 1998 | A |
| 5793365 | Tang et al. | Aug 1998 | A |
| 5825357 | Malamud et al. | Oct 1998 | A |
| 6025871 | Kantor et al. | Feb 2000 | A |
| 6166736 | Hugh | Dec 2000 | A |
| 6215490 | Kaply | Apr 2001 | B1 |
| 6230170 | Zellweger et al. | May 2001 | B1 |
| 6300951 | Filetto et al. | Oct 2001 | B1 |
| 6346962 | Goodridge | Feb 2002 | B1 |
| 6486895 | Robertson et al. | Nov 2002 | B1 |
| 6493002 | Christensen | Dec 2002 | B1 |
| 6661437 | Miller et al. | Dec 2003 | B1 |
| 6768497 | Baar et al. | Jul 2004 | B2 |
| 7007241 | Boeuf | Feb 2006 | B2 |
| 7102663 | Crook | Sep 2006 | B2 |
| 7148911 | Mitsui et al. | Dec 2006 | B1 |
| 7444645 | St-Michel et al. | Oct 2008 | B1 |
| 7458014 | Rubin et al. | Nov 2008 | B1 |
| 7469381 | Ording | Dec 2008 | B2 |
| 7506260 | Wada et al. | Mar 2009 | B2 |
| 7676767 | Hofmeister et al. | Mar 2010 | B2 |
| 7707514 | Forstall et al. | Apr 2010 | B2 |
| 7739622 | DeLine et al. | Jun 2010 | B2 |
| 7814112 | Gupta et al. | Oct 2010 | B2 |
| 7840907 | Kikuchi et al. | Nov 2010 | B2 |
| 7876996 | Herz | Jan 2011 | B1 |
| 7954056 | Graham | May 2011 | B2 |
| 7982762 | Chatting et al. | Jul 2011 | B2 |
| 8077157 | Sengupta et al. | Dec 2011 | B2 |
| 8171137 | Parks et al. | May 2012 | B1 |
| 8181119 | Ording | May 2012 | B1 |
| RE43462 | Washino et al. | Jun 2012 | E |
| 8196061 | Bhojan | Jun 2012 | B1 |
| 8224894 | Parks et al. | Jul 2012 | B1 |
| 8250071 | Killalea et al. | Aug 2012 | B1 |
| 8259153 | Campbell, III et al. | Sep 2012 | B1 |
| 8260879 | Chan | Sep 2012 | B2 |
| 8269739 | Hillis et al. | Sep 2012 | B2 |
| 8290777 | Nguyen et al. | Oct 2012 | B1 |
| 8291341 | Tseng et al. | Oct 2012 | B2 |
| 8294105 | Alameh et al. | Oct 2012 | B2 |
| 8370448 | Galchev | Feb 2013 | B2 |
| 8427303 | Brady et al. | Apr 2013 | B1 |
| 8438504 | Cranfill et al. | May 2013 | B2 |
| 8443280 | Noyes | May 2013 | B2 |
| 8478363 | Levien et al. | Jul 2013 | B2 |
| 8478816 | Parks et al. | Jul 2013 | B2 |
| 8499236 | Keljo | Jul 2013 | B1 |
| 8502856 | Jeong et al. | Aug 2013 | B2 |
| 8566700 | Ueda | Oct 2013 | B2 |
| 8613070 | Borzycki et al. | Dec 2013 | B1 |
| 8624952 | Currivan et al. | Jan 2014 | B2 |
| 8656040 | Bajaj et al. | Feb 2014 | B1 |
| 8718556 | Lee et al. | May 2014 | B2 |
| 8725880 | Santamaria et al. | May 2014 | B2 |
| 8762844 | Kim et al. | Jun 2014 | B2 |
| 8782513 | Migos et al. | Jul 2014 | B2 |
| 8806369 | Khoe et al. | Aug 2014 | B2 |
| 8839122 | Anzures et al. | Sep 2014 | B2 |
| 8856105 | Gargi | Oct 2014 | B2 |
| 8949250 | Garg | Feb 2015 | B1 |
| 9095779 | Chan et al. | Aug 2015 | B2 |
| 9253531 | Relyea et al. | Feb 2016 | B2 |
| 9253631 | White et al. | Feb 2016 | B1 |
| 9417781 | Lee | Aug 2016 | B2 |
| 9442516 | Migos et al. | Sep 2016 | B2 |
| 9462017 | Siracusano, Jr. | Oct 2016 | B1 |
| 9483175 | Wagner | Nov 2016 | B2 |
| 9552015 | Migos et al. | Jan 2017 | B2 |
| 9639252 | Jin | May 2017 | B2 |
| 9781540 | Jagannathan | Oct 2017 | B2 |
| 9787938 | Cranfill et al. | Oct 2017 | B2 |
| 9819877 | Faulkner et al. | Nov 2017 | B1 |
| 9830056 | Keely | Nov 2017 | B1 |
| 10025496 | Park | Jul 2018 | B2 |
| 10198144 | Munoz | Feb 2019 | B2 |
| 10284812 | Van Os et al. | May 2019 | B1 |
| 10386994 | Singal et al. | Aug 2019 | B2 |
| 10534535 | Lee | Jan 2020 | B2 |
| 10909586 | Avedissian et al. | Feb 2021 | B2 |
| 11064256 | Voss et al. | Jul 2021 | B1 |
| 11164113 | Howard | Nov 2021 | B2 |
| 11258619 | Libin | Feb 2022 | B2 |
| 11360634 | Chang et al. | Jun 2022 | B1 |
| 11449188 | Chang et al. | Sep 2022 | B1 |
| 11671697 | O'Leary et al. | Jun 2023 | B2 |
| 11726647 | Kim | Aug 2023 | B2 |
| 11770600 | O'Leary et al. | Sep 2023 | B2 |
| 20020010707 | Chang et al. | Jan 2002 | A1 |
| 20020075334 | Yfantis | Jun 2002 | A1 |
| 20020083101 | Card et al. | Jun 2002 | A1 |
| 20020093531 | Barile | Jul 2002 | A1 |
| 20020105537 | Orbanes et al. | Aug 2002 | A1 |
| 20020113802 | Card et al. | Aug 2002 | A1 |
| 20020118230 | Card et al. | Aug 2002 | A1 |
| 20020120651 | Pustejovsky et al. | Aug 2002 | A1 |
| 20030013493 | Irimajiri et al. | Jan 2003 | A1 |
| 20030030673 | Ho | Feb 2003 | A1 |
| 20030055977 | Miller | Mar 2003 | A1 |
| 20030076352 | Uhlig et al. | Apr 2003 | A1 |
| 20030098884 | Christensen | May 2003 | A1 |
| 20030158886 | Walls et al. | Aug 2003 | A1 |
| 20030184598 | Graham | Oct 2003 | A1 |
| 20030218619 | Ben-Tovim | Nov 2003 | A1 |
| 20030225836 | Lee et al. | Dec 2003 | A1 |
| 20040017404 | Schileru-Key | Jan 2004 | A1 |
| 20040048601 | Lee et al. | Mar 2004 | A1 |
| 20040048612 | Virtanen et al. | Mar 2004 | A1 |
| 20040080531 | Berstis | Apr 2004 | A1 |
| 20040102225 | Furuta et al. | May 2004 | A1 |
| 20040125081 | Hayakawa | Jul 2004 | A1 |
| 20040141016 | Fukatsu et al. | Jul 2004 | A1 |
| 20040174398 | Luke et al. | Sep 2004 | A1 |
| 20040205514 | Sommerer et al. | Oct 2004 | A1 |
| 20040218035 | Crook | Nov 2004 | A1 |
| 20050132281 | Pan et al. | Jun 2005 | A1 |
| 20050223068 | Shohfi et al. | Oct 2005 | A1 |
| 20050233780 | Jani et al. | Oct 2005 | A1 |
| 20050239512 | Hasegawa et al. | Oct 2005 | A1 |
| 20050289482 | Anthony et al. | Dec 2005 | A1 |
| 20060002315 | Theurer et al. | Jan 2006 | A1 |
| 20060031776 | Glein et al. | Feb 2006 | A1 |
| 20060033724 | Chaudhri et al. | Feb 2006 | A1 |
| 20060055789 | Jin et al. | Mar 2006 | A1 |
| 20060056837 | Vapaakoski | Mar 2006 | A1 |
| 20060071947 | Ubillos et al. | Apr 2006 | A1 |
| 20060101122 | Ishii | May 2006 | A1 |
| 20060107226 | Matthews et al. | May 2006 | A1 |
| 20060149399 | Norhammar et al. | Jul 2006 | A1 |
| 20060150215 | Wroblewski | Jul 2006 | A1 |
| 20060184894 | Daniels et al. | Aug 2006 | A1 |
| 20060185005 | Graves et al. | Aug 2006 | A1 |
| 20060230346 | Bhogal et al. | Oct 2006 | A1 |
| 20060256188 | Mock et al. | Nov 2006 | A1 |
| 20070015519 | Casey | Jan 2007 | A1 |
| 20070040898 | Lee et al. | Feb 2007 | A1 |
| 20070064112 | Chatting et al. | Mar 2007 | A1 |
| 20070083828 | Toriyama et al. | Apr 2007 | A1 |
| 20070115349 | Currivan et al. | May 2007 | A1 |
| 20070115933 | Muhamed et al. | May 2007 | A1 |
| 20070160345 | Sakai et al. | Jul 2007 | A1 |
| 20070174761 | Lin et al. | Jul 2007 | A1 |
| 20070177025 | Kopet et al. | Aug 2007 | A1 |
| 20070177804 | Elias et al. | Aug 2007 | A1 |
| 20070233736 | Xiong et al. | Oct 2007 | A1 |
| 20070236476 | Suzuki | Oct 2007 | A1 |
| 20070239831 | Basu | Oct 2007 | A1 |
| 20070264977 | Zinn et al. | Nov 2007 | A1 |
| 20070277121 | Beckman | Nov 2007 | A1 |
| 20070279482 | Oswald et al. | Dec 2007 | A1 |
| 20070291736 | Furlong et al. | Dec 2007 | A1 |
| 20080032704 | Oneil et al. | Feb 2008 | A1 |
| 20080034307 | Cisler et al. | Feb 2008 | A1 |
| 20080036849 | Oh et al. | Feb 2008 | A1 |
| 20080063389 | Fang et al. | Mar 2008 | A1 |
| 20080068447 | Mattila et al. | Mar 2008 | A1 |
| 20080074049 | Kitai et al. | Mar 2008 | A1 |
| 20080074550 | Park | Mar 2008 | A1 |
| 20080084482 | Hansson et al. | Apr 2008 | A1 |
| 20080094368 | Ording et al. | Apr 2008 | A1 |
| 20080094370 | Ording et al. | Apr 2008 | A1 |
| 20080117876 | Hidaka et al. | May 2008 | A1 |
| 20080129816 | Mattila et al. | Jun 2008 | A1 |
| 20080134033 | Burns et al. | Jun 2008 | A1 |
| 20080141182 | Barsness et al. | Jun 2008 | A1 |
| 20080160974 | Vartiainen et al. | Jul 2008 | A1 |
| 20080165388 | Serlet | Jul 2008 | A1 |
| 20080168073 | Siegel et al. | Jul 2008 | A1 |
| 20080174570 | Jobs et al. | Jul 2008 | A1 |
| 20080218535 | Forstall et al. | Sep 2008 | A1 |
| 20080246778 | Ham et al. | Oct 2008 | A1 |
| 20080282202 | Sunday | Nov 2008 | A1 |
| 20080307345 | Hart et al. | Dec 2008 | A1 |
| 20080313257 | Allen et al. | Dec 2008 | A1 |
| 20080316295 | King et al. | Dec 2008 | A1 |
| 20080319856 | Zito et al. | Dec 2008 | A1 |
| 20080319944 | Venolia et al. | Dec 2008 | A1 |
| 20090005011 | Christie et al. | Jan 2009 | A1 |
| 20090007017 | Anzures et al. | Jan 2009 | A1 |
| 20090046075 | Kim et al. | Feb 2009 | A1 |
| 20090049446 | Merten et al. | Feb 2009 | A1 |
| 20090089712 | Sato | Apr 2009 | A1 |
| 20090100383 | Sunday et al. | Apr 2009 | A1 |
| 20090103780 | Nishihara et al. | Apr 2009 | A1 |
| 20090106687 | De et al. | Apr 2009 | A1 |
| 20090109276 | Kim | Apr 2009 | A1 |
| 20090113347 | Hess et al. | Apr 2009 | A1 |
| 20090140960 | Mahowald | Jun 2009 | A1 |
| 20090158217 | Stuart | Jun 2009 | A1 |
| 20090164322 | Khan et al. | Jun 2009 | A1 |
| 20090179867 | Shim et al. | Jul 2009 | A1 |
| 20090187825 | Sandquist et al. | Jul 2009 | A1 |
| 20090213086 | Chae et al. | Aug 2009 | A1 |
| 20090228126 | Spielberg et al. | Sep 2009 | A1 |
| 20090228820 | Kim et al. | Sep 2009 | A1 |
| 20090228825 | Van Os et al. | Sep 2009 | A1 |
| 20090228938 | White et al. | Sep 2009 | A1 |
| 20090232129 | Wong et al. | Sep 2009 | A1 |
| 20090235155 | Ueda | Sep 2009 | A1 |
| 20090235162 | Nuccio et al. | Sep 2009 | A1 |
| 20090241054 | Hendricks | Sep 2009 | A1 |
| 20090249244 | Robinson et al. | Oct 2009 | A1 |
| 20090254867 | Farouki et al. | Oct 2009 | A1 |
| 20090259939 | Lockett et al. | Oct 2009 | A1 |
| 20090271381 | Beezer et al. | Oct 2009 | A1 |
| 20090305679 | Kim | Dec 2009 | A1 |
| 20090315841 | Cheng et al. | Dec 2009 | A1 |
| 20090319888 | Oygard | Dec 2009 | A1 |
| 20100009719 | Oh et al. | Jan 2010 | A1 |
| 20100011065 | Scherpa et al. | Jan 2010 | A1 |
| 20100023878 | Douris et al. | Jan 2010 | A1 |
| 20100023883 | Khazaka et al. | Jan 2010 | A1 |
| 20100029255 | Kim et al. | Feb 2010 | A1 |
| 20100044121 | Simon et al. | Feb 2010 | A1 |
| 20100045616 | Li et al. | Feb 2010 | A1 |
| 20100053212 | Kang et al. | Mar 2010 | A1 |
| 20100066763 | Macdougall et al. | Mar 2010 | A1 |
| 20100073454 | Lovhaugen et al. | Mar 2010 | A1 |
| 20100073455 | Iwabuchi et al. | Mar 2010 | A1 |
| 20100087230 | Peh et al. | Apr 2010 | A1 |
| 20100095240 | Shiplacoff et al. | Apr 2010 | A1 |
| 20100107078 | Hayashi | Apr 2010 | A1 |
| 20100109864 | Haartsen et al. | May 2010 | A1 |
| 20100115388 | Nguyen | May 2010 | A1 |
| 20100125807 | Easterday et al. | May 2010 | A1 |
| 20100159995 | Stallings et al. | Jun 2010 | A1 |
| 20100162108 | Stallings et al. | Jun 2010 | A1 |
| 20100174606 | Hoyle | Jul 2010 | A1 |
| 20100175018 | Petschnigg et al. | Jul 2010 | A1 |
| 20100177156 | Kim et al. | Jul 2010 | A1 |
| 20100189096 | Flynn et al. | Jul 2010 | A1 |
| 20100205563 | Haapsaari et al. | Aug 2010 | A1 |
| 20100211872 | Rolston | Aug 2010 | A1 |
| 20100241699 | Muthukumarasamy et al. | Sep 2010 | A1 |
| 20100242066 | Tseng | Sep 2010 | A1 |
| 20100247077 | Yamamoto et al. | Sep 2010 | A1 |
| 20100262714 | Hiie | Oct 2010 | A1 |
| 20100269039 | Pahlavan et al. | Oct 2010 | A1 |
| 20100281399 | Banker | Nov 2010 | A1 |
| 20100295789 | Shin et al. | Nov 2010 | A1 |
| 20100309284 | Samadani et al. | Dec 2010 | A1 |
| 20100311336 | Huotari et al. | Dec 2010 | A1 |
| 20100333045 | Guéziec et al. | Dec 2010 | A1 |
| 20110007029 | Ben-David | Jan 2011 | A1 |
| 20110010667 | Sakai et al. | Jan 2011 | A1 |
| 20110016417 | Shiplacoff et al. | Jan 2011 | A1 |
| 20110029864 | Stewart et al. | Feb 2011 | A1 |
| 20110029891 | Kim et al. | Feb 2011 | A1 |
| 20110030324 | Higgins | Feb 2011 | A1 |
| 20110032324 | George et al. | Feb 2011 | A1 |
| 20110041056 | Griffin et al. | Feb 2011 | A1 |
| 20110041096 | Larco et al. | Feb 2011 | A1 |
| 20110041102 | Kim | Feb 2011 | A1 |
| 20110065384 | Cader et al. | Mar 2011 | A1 |
| 20110074824 | Srinivasan et al. | Mar 2011 | A1 |
| 20110087431 | Gupta et al. | Apr 2011 | A1 |
| 20110087955 | Ho et al. | Apr 2011 | A1 |
| 20110088086 | Swink et al. | Apr 2011 | A1 |
| 20110091182 | Look et al. | Apr 2011 | A1 |
| 20110107241 | Moore | May 2011 | A1 |
| 20110117898 | Pereira et al. | May 2011 | A1 |
| 20110138295 | Momchilov et al. | Jun 2011 | A1 |
| 20110145691 | Noyes | Jun 2011 | A1 |
| 20110145692 | Noyes et al. | Jun 2011 | A1 |
| 20110178811 | Sheridan | Jul 2011 | A1 |
| 20110179386 | Shaffer et al. | Jul 2011 | A1 |
| 20110191710 | Jang et al. | Aug 2011 | A1 |
| 20110205333 | Wu et al. | Aug 2011 | A1 |
| 20110209099 | Hinckley et al. | Aug 2011 | A1 |
| 20110209104 | Hinckley et al. | Aug 2011 | A1 |
| 20110227810 | Mckinney et al. | Sep 2011 | A1 |
| 20110234746 | Saleh et al. | Sep 2011 | A1 |
| 20110235549 | Ahlers et al. | Sep 2011 | A1 |
| 20110242356 | Aleksic et al. | Oct 2011 | A1 |
| 20110246944 | Byrne | Oct 2011 | A1 |
| 20110249073 | Cranfill et al. | Oct 2011 | A1 |
| 20110249074 | Cranfill et al. | Oct 2011 | A1 |
| 20110252062 | Hanatani et al. | Oct 2011 | A1 |
| 20110252364 | Anzures et al. | Oct 2011 | A1 |
| 20110252368 | Anzures et al. | Oct 2011 | A1 |
| 20110252369 | Chaudhri | Oct 2011 | A1 |
| 20110252376 | Chaudhri et al. | Oct 2011 | A1 |
| 20110252377 | Anzures et al. | Oct 2011 | A1 |
| 20110252381 | Chaudhri | Oct 2011 | A1 |
| 20110261030 | Bullock | Oct 2011 | A1 |
| 20110275358 | Faenger | Nov 2011 | A1 |
| 20110281568 | Le Clech | Nov 2011 | A1 |
| 20110291945 | Ewing, Jr. et al. | Dec 2011 | A1 |
| 20110295879 | Logis et al. | Dec 2011 | A1 |
| 20110296333 | Bateman et al. | Dec 2011 | A1 |
| 20110296344 | Habib et al. | Dec 2011 | A1 |
| 20110296351 | Ewing, Jr. | Dec 2011 | A1 |
| 20110314398 | Yano | Dec 2011 | A1 |
| 20120023438 | Xia et al. | Jan 2012 | A1 |
| 20120023462 | Rosing et al. | Jan 2012 | A1 |
| 20120084644 | Robert et al. | Apr 2012 | A1 |
| 20120096069 | Chan | Apr 2012 | A1 |
| 20120096076 | Chan | Apr 2012 | A1 |
| 20120096344 | Ho et al. | Apr 2012 | A1 |
| 20120096386 | Baumann et al. | Apr 2012 | A1 |
| 20120102387 | Badoiu et al. | Apr 2012 | A1 |
| 20120105225 | Valtonen | May 2012 | A1 |
| 20120121185 | Zavesky | May 2012 | A1 |
| 20120129496 | Park et al. | May 2012 | A1 |
| 20120131470 | Wessling et al. | May 2012 | A1 |
| 20120136998 | Hough et al. | May 2012 | A1 |
| 20120143694 | Zargahi et al. | Jun 2012 | A1 |
| 20120159364 | Hyun | Jun 2012 | A1 |
| 20120159373 | Archer et al. | Jun 2012 | A1 |
| 20120159380 | Kocienda et al. | Jun 2012 | A1 |
| 20120166950 | Frumar et al. | Jun 2012 | A1 |
| 20120173383 | Badawiyeh et al. | Jul 2012 | A1 |
| 20120179970 | Hayes | Jul 2012 | A1 |
| 20120185355 | Kilroy | Jul 2012 | A1 |
| 20120185467 | Prager et al. | Jul 2012 | A1 |
| 20120192068 | Migos et al. | Jul 2012 | A1 |
| 20120192102 | Migos et al. | Jul 2012 | A1 |
| 20120192118 | Migos et al. | Jul 2012 | A1 |
| 20120201479 | Zhang et al. | Aug 2012 | A1 |
| 20120214552 | Sirpal et al. | Aug 2012 | A1 |
| 20120223890 | Borovsky et al. | Sep 2012 | A1 |
| 20120229591 | Lee | Sep 2012 | A1 |
| 20120240085 | Sim et al. | Sep 2012 | A1 |
| 20120266098 | Webber | Oct 2012 | A1 |
| 20120274550 | Campbell et al. | Nov 2012 | A1 |
| 20120284256 | Mahajan et al. | Nov 2012 | A1 |
| 20120284673 | Lamb et al. | Nov 2012 | A1 |
| 20120289217 | Riemer et al. | Nov 2012 | A1 |
| 20120290657 | Parks et al. | Nov 2012 | A1 |
| 20120290943 | Toney et al. | Nov 2012 | A1 |
| 20120293605 | Seferian et al. | Nov 2012 | A1 |
| 20120304111 | Queru | Nov 2012 | A1 |
| 20130005487 | Frazzini et al. | Jan 2013 | A1 |
| 20130014040 | Jagannathan | Jan 2013 | A1 |
| 20130019182 | Gil et al. | Jan 2013 | A1 |
| 20130041790 | Murugesan et al. | Feb 2013 | A1 |
| 20130046893 | Hauser et al. | Feb 2013 | A1 |
| 20130050263 | Khoe et al. | Feb 2013 | A1 |
| 20130054697 | Cha | Feb 2013 | A1 |
| 20130055113 | Chazin et al. | Feb 2013 | A1 |
| 20130061155 | Hon | Mar 2013 | A1 |
| 20130061175 | Matas et al. | Mar 2013 | A1 |
| 20130080525 | Aoki et al. | Mar 2013 | A1 |
| 20130102281 | Kanda et al. | Apr 2013 | A1 |
| 20130111342 | Alameh et al. | May 2013 | A1 |
| 20130111603 | Sakai et al. | May 2013 | A1 |
| 20130120254 | Mun et al. | May 2013 | A1 |
| 20130122961 | Choi et al. | May 2013 | A1 |
| 20130145303 | Prakash et al. | Jun 2013 | A1 |
| 20130151623 | Weiser et al. | Jun 2013 | A1 |
| 20130151959 | Flynn, III et al. | Jun 2013 | A1 |
| 20130166580 | Maharajh et al. | Jun 2013 | A1 |
| 20130173699 | Parks et al. | Jul 2013 | A1 |
| 20130185642 | Gammons | Jul 2013 | A1 |
| 20130191911 | Dellinger et al. | Jul 2013 | A1 |
| 20130212212 | Addepalli et al. | Aug 2013 | A1 |
| 20130283199 | Selig et al. | Oct 2013 | A1 |
| 20130283283 | Wang et al. | Oct 2013 | A1 |
| 20130298024 | Rhee et al. | Nov 2013 | A1 |
| 20130318158 | Teng et al. | Nov 2013 | A1 |
| 20130318249 | McDonough et al. | Nov 2013 | A1 |
| 20130321340 | Seo | Dec 2013 | A1 |
| 20130325949 | Virani et al. | Dec 2013 | A1 |
| 20130325967 | Parks et al. | Dec 2013 | A1 |
| 20130332856 | Sanders et al. | Dec 2013 | A1 |
| 20130332886 | Cranfill et al. | Dec 2013 | A1 |
| 20140013271 | Moore et al. | Jan 2014 | A1 |
| 20140018053 | Cho et al. | Jan 2014 | A1 |
| 20140024340 | Raleigh | Jan 2014 | A1 |
| 20140032706 | Kuscher et al. | Jan 2014 | A1 |
| 20140047020 | Matus et al. | Feb 2014 | A1 |
| 20140047382 | Kim | Feb 2014 | A1 |
| 20140058941 | Moon et al. | Feb 2014 | A1 |
| 20140068477 | Roh | Mar 2014 | A1 |
| 20140082136 | Garcia et al. | Mar 2014 | A1 |
| 20140101597 | Bamford et al. | Apr 2014 | A1 |
| 20140105372 | Nowack et al. | Apr 2014 | A1 |
| 20140108084 | Bargetzi et al. | Apr 2014 | A1 |
| 20140122730 | Burch et al. | May 2014 | A1 |
| 20140136481 | Quan et al. | May 2014 | A1 |
| 20140149884 | Flynn, III et al. | May 2014 | A1 |
| 20140165012 | Shen et al. | Jun 2014 | A1 |
| 20140168696 | Matsuhara et al. | Jun 2014 | A1 |
| 20140171064 | Das | Jun 2014 | A1 |
| 20140173447 | Das | Jun 2014 | A1 |
| 20140201126 | Zadeh et al. | Jul 2014 | A1 |
| 20140201632 | Kunigita et al. | Jul 2014 | A1 |
| 20140215356 | Brander et al. | Jul 2014 | A1 |
| 20140280812 | Bealkowski et al. | Sep 2014 | A1 |
| 20140282103 | Crandall | Sep 2014 | A1 |
| 20140282110 | Chaudhri | Sep 2014 | A1 |
| 20140282208 | Chaudhri | Sep 2014 | A1 |
| 20140282240 | Flynn, III | Sep 2014 | A1 |
| 20140298253 | Jin | Oct 2014 | A1 |
| 20140320387 | Eriksson et al. | Oct 2014 | A1 |
| 20140320425 | Jeong et al. | Oct 2014 | A1 |
| 20140325447 | Jin et al. | Oct 2014 | A1 |
| 20140337791 | Agnetta | Nov 2014 | A1 |
| 20140351722 | Frederickson et al. | Nov 2014 | A1 |
| 20140354759 | Cranfill et al. | Dec 2014 | A1 |
| 20140359637 | Yan | Dec 2014 | A1 |
| 20140365929 | Ding | Dec 2014 | A1 |
| 20140368547 | Elings | Dec 2014 | A1 |
| 20140375577 | Yeh et al. | Dec 2014 | A1 |
| 20140380187 | Gardenfors et al. | Dec 2014 | A1 |
| 20150033149 | Kuchoor | Jan 2015 | A1 |
| 20150049591 | Adams et al. | Feb 2015 | A1 |
| 20150062158 | Hildreth et al. | Mar 2015 | A1 |
| 20150085057 | Ouyang et al. | Mar 2015 | A1 |
| 20150098309 | Adams | Apr 2015 | A1 |
| 20150116363 | Monte et al. | Apr 2015 | A1 |
| 20150128042 | Churchill | May 2015 | A1 |
| 20150163188 | Faaborg et al. | Jun 2015 | A1 |
| 20150169146 | Lalwani | Jun 2015 | A1 |
| 20150169182 | Khoe et al. | Jun 2015 | A1 |
| 20150193069 | Di Censo et al. | Jul 2015 | A1 |
| 20150193392 | Greenblatt et al. | Jul 2015 | A1 |
| 20150199082 | Scholler | Jul 2015 | A1 |
| 20150205488 | Yi | Jul 2015 | A1 |
| 20150304366 | Bader-Natal et al. | Oct 2015 | A1 |
| 20150304413 | Park | Oct 2015 | A1 |
| 20150309689 | Jin | Oct 2015 | A1 |
| 20150319144 | Barton et al. | Nov 2015 | A1 |
| 20150324067 | Cabral | Nov 2015 | A1 |
| 20150332031 | Mistry et al. | Nov 2015 | A1 |
| 20150339007 | Yoshizawa et al. | Nov 2015 | A1 |
| 20150339466 | Gao et al. | Nov 2015 | A1 |
| 20150347010 | Yang et al. | Dec 2015 | A1 |
| 20150350296 | Yang et al. | Dec 2015 | A1 |
| 20150350297 | Yang et al. | Dec 2015 | A1 |
| 20150358484 | Permude | Dec 2015 | A1 |
| 20150365306 | Chaudhri et al. | Dec 2015 | A1 |
| 20150370529 | Zambetti et al. | Dec 2015 | A1 |
| 20150373065 | Holmquist et al. | Dec 2015 | A1 |
| 20160048296 | Gan et al. | Feb 2016 | A1 |
| 20160059864 | Feit et al. | Mar 2016 | A1 |
| 20160062567 | Yang et al. | Mar 2016 | A1 |
| 20160062589 | Wan et al. | Mar 2016 | A1 |
| 20160065708 | Yang et al. | Mar 2016 | A1 |
| 20160072861 | Woolsey et al. | Mar 2016 | A1 |
| 20160139785 | Griffin et al. | May 2016 | A1 |
| 20160142450 | Paul et al. | May 2016 | A1 |
| 20160170608 | Zambetti et al. | Jun 2016 | A1 |
| 20160180259 | Marianko et al. | Jun 2016 | A1 |
| 20160210602 | Siddique et al. | Jul 2016 | A1 |
| 20160299679 | Park | Oct 2016 | A1 |
| 20160306328 | Ko | Oct 2016 | A1 |
| 20160308920 | Brunsch et al. | Oct 2016 | A1 |
| 20160316038 | Jolfaei | Oct 2016 | A1 |
| 20160327911 | Eim et al. | Nov 2016 | A1 |
| 20160364106 | Koum et al. | Dec 2016 | A1 |
| 20170006162 | Bargetzi et al. | Jan 2017 | A1 |
| 20170024100 | Pieper et al. | Jan 2017 | A1 |
| 20170024226 | Yan | Jan 2017 | A1 |
| 20170034583 | Long et al. | Feb 2017 | A1 |
| 20170126592 | El | May 2017 | A1 |
| 20170212667 | Miyazaki | Jul 2017 | A1 |
| 20170357917 | Holmes et al. | Dec 2017 | A1 |
| 20170359285 | Weinig et al. | Dec 2017 | A1 |
| 20170359461 | De Vries et al. | Dec 2017 | A1 |
| 20170367484 | Salvoni et al. | Dec 2017 | A1 |
| 20170373868 | Deets, Jr. | Dec 2017 | A1 |
| 20180013799 | Davies | Jan 2018 | A1 |
| 20180081522 | Greenberg et al. | Mar 2018 | A1 |
| 20180081538 | Kim | Mar 2018 | A1 |
| 20180095616 | Valdivia et al. | Apr 2018 | A1 |
| 20180124128 | Faulkner et al. | May 2018 | A1 |
| 20180131732 | Aronoff et al. | May 2018 | A1 |
| 20180150433 | Sowden et al. | May 2018 | A1 |
| 20180160072 | Cranfill et al. | Jun 2018 | A1 |
| 20180191965 | Faulkner et al. | Jul 2018 | A1 |
| 20180204111 | Zadeh et al. | Jul 2018 | A1 |
| 20180205797 | Faulkner | Jul 2018 | A1 |
| 20180309801 | Rathod | Oct 2018 | A1 |
| 20180321842 | Lee | Nov 2018 | A1 |
| 20180359293 | Faulkner et al. | Dec 2018 | A1 |
| 20180367484 | Rodriguez et al. | Dec 2018 | A1 |
| 20180375676 | Bader-Natal et al. | Dec 2018 | A1 |
| 20190005419 | Howard | Jan 2019 | A1 |
| 20190034849 | Romaine et al. | Jan 2019 | A1 |
| 20190102049 | Anzures et al. | Apr 2019 | A1 |
| 20190149887 | Williams et al. | May 2019 | A1 |
| 20190208028 | Larabie-Belanger | Jul 2019 | A1 |
| 20190236142 | Balakrishnan et al. | Aug 2019 | A1 |
| 20190297039 | Rodriguez et al. | Sep 2019 | A1 |
| 20190342519 | Van Os et al. | Nov 2019 | A1 |
| 20190347181 | Cranfill et al. | Nov 2019 | A1 |
| 20190361694 | Gordon et al. | Nov 2019 | A1 |
| 20190370805 | Van Os et al. | Dec 2019 | A1 |
| 20200034033 | Chaudhri et al. | Jan 2020 | A1 |
| 20200059628 | Cranfill et al. | Feb 2020 | A1 |
| 20200112690 | Harrison et al. | Apr 2020 | A1 |
| 20200183548 | Anzures et al. | Jun 2020 | A1 |
| 20200226896 | Robertson et al. | Jul 2020 | A1 |
| 20200274726 | Setteboun et al. | Aug 2020 | A1 |
| 20200296329 | Tang et al. | Sep 2020 | A1 |
| 20200322479 | De Vries et al. | Oct 2020 | A1 |
| 20200356063 | Guzman et al. | Nov 2020 | A1 |
| 20210136129 | Ponnusamy et al. | May 2021 | A1 |
| 20210152503 | Rodriguez et al. | May 2021 | A1 |
| 20210182169 | Mardente et al. | Jun 2021 | A1 |
| 20210217106 | Hauser et al. | Jul 2021 | A1 |
| 20210360192 | Cranfill et al. | Nov 2021 | A1 |
| 20210409359 | Eirinberg et al. | Dec 2021 | A1 |
| 20220050578 | Waldman et al. | Feb 2022 | A1 |
| 20220100362 | Kim | Mar 2022 | A1 |
| 20220100812 | Anvaripour et al. | Mar 2022 | A1 |
| 20220122089 | Bonilla Kuhlmann et al. | Apr 2022 | A1 |
| 20220163996 | Yang et al. | May 2022 | A1 |
| 20220207840 | Cansizoglu et al. | Jun 2022 | A1 |
| 20220253136 | Holder et al. | Aug 2022 | A1 |
| 20220254074 | Berliner et al. | Aug 2022 | A1 |
| 20220263940 | De Vries et al. | Aug 2022 | A1 |
| 20220278992 | Baker et al. | Sep 2022 | A1 |
| 20220365739 | Chang et al. | Nov 2022 | A1 |
| 20220365740 | Chang et al. | Nov 2022 | A1 |
| 20220368548 | Chang et al. | Nov 2022 | A1 |
| 20220368659 | Chang et al. | Nov 2022 | A1 |
| 20220368742 | Chang et al. | Nov 2022 | A1 |
| 20220374136 | Chang et al. | Nov 2022 | A1 |
| 20230246857 | Boucheron et al. | Aug 2023 | A1 |
| 20230262196 | Cranfill et al. | Aug 2023 | A1 |
| 20230370507 | Chang et al. | Nov 2023 | A1 |
| 20230393616 | Chao et al. | Dec 2023 | A1 |
| 20240036804 | Chang et al. | Feb 2024 | A1 |
| 20240103677 | Mckenzie et al. | Mar 2024 | A1 |
| 20240103678 | Dryer et al. | Mar 2024 | A1 |
| 20240111333 | Yang et al. | Apr 2024 | A1 |
| 20240163365 | De Vries et al. | May 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 2876587 | Feb 2014 | CA |
| 1473430 | Feb 2004 | CN |
| 1525723 | Sep 2004 | CN |
| 1801926 | Jul 2006 | CN |
| 1918533 | Feb 2007 | CN |
| 1985319 | Jun 2007 | CN |
| 101226444 | Jul 2008 | CN |
| 101296356 | Oct 2008 | CN |
| 101356493 | Jan 2009 | CN |
| 101409743 | Apr 2009 | CN |
| 101535938 | Sep 2009 | CN |
| 101828166 | Sep 2010 | CN |
| 102262506 | Nov 2011 | CN |
| 102439558 | May 2012 | CN |
| 102707994 | Oct 2012 | CN |
| 102750086 | Oct 2012 | CN |
| 103250138 | Aug 2013 | CN |
| 103336651 | Oct 2013 | CN |
| 103582873 | Feb 2014 | CN |
| 103765385 | Apr 2014 | CN |
| 104182123 | Dec 2014 | CN |
| 104834439 | Aug 2015 | CN |
| 105094551 | Nov 2015 | CN |
| 105308634 | Feb 2016 | CN |
| 105637451 | Jun 2016 | CN |
| 108933965 | Dec 2018 | CN |
| 110456971 | Nov 2019 | CN |
| 111108740 | May 2020 | CN |
| 112416223 | Feb 2021 | CN |
| 0483777 | May 1992 | EP |
| 0584392 | Mar 1994 | EP |
| 1215575 | Jun 2002 | EP |
| 1517228 | Mar 2005 | EP |
| 1760584 | Mar 2007 | EP |
| 1903791 | Mar 2008 | EP |
| 1986431 | Oct 2008 | EP |
| 2151745 | Feb 2010 | EP |
| 2600584 | Jun 2013 | EP |
| 2682850 | Jan 2014 | EP |
| 2703974 | Mar 2014 | EP |
| 2725473 | Apr 2014 | EP |
| 2770708 | Aug 2014 | EP |
| 2446619 | Oct 2015 | EP |
| 3091421 | Nov 2016 | EP |
| 3163866 | May 2020 | EP |
| 6-110881 | Apr 1994 | JP |
| 6-113297 | Apr 1994 | JP |
| 6-276335 | Sep 1994 | JP |
| 6-276515 | Sep 1994 | JP |
| 7-135594 | May 1995 | JP |
| 7-325700 | Dec 1995 | JP |
| 8-76926 | Mar 1996 | JP |
| 9-182046 | Jul 1997 | JP |
| 9-247655 | Sep 1997 | JP |
| 10-240488 | Sep 1998 | JP |
| 2000-40158 | Feb 2000 | JP |
| 2000-200092 | Jul 2000 | JP |
| 2000-242390 | Sep 2000 | JP |
| 2000-283772 | Oct 2000 | JP |
| 2001-101202 | Apr 2001 | JP |
| 2001-169166 | Jun 2001 | JP |
| 2002-251365 | Sep 2002 | JP |
| 2002-288125 | Oct 2002 | JP |
| 2002-320140 | Oct 2002 | JP |
| 2002-351802 | Dec 2002 | JP |
| 2003-134382 | May 2003 | JP |
| 2003-189168 | Jul 2003 | JP |
| 2003-195998 | Jul 2003 | JP |
| 2003-274376 | Sep 2003 | JP |
| 2003-526820 | Sep 2003 | JP |
| 2003-299050 | Oct 2003 | JP |
| 2003-348444 | Dec 2003 | JP |
| 2004-187273 | Jul 2004 | JP |
| 2004-193860 | Jul 2004 | JP |
| 2004-221738 | Aug 2004 | JP |
| 2005-45744 | Feb 2005 | JP |
| 2005-159567 | Jun 2005 | JP |
| 2005-260289 | Sep 2005 | JP |
| 2005-286445 | Oct 2005 | JP |
| 2005-332368 | Dec 2005 | JP |
| 2006-135495 | May 2006 | JP |
| 2006-166414 | Jun 2006 | JP |
| 2006-222822 | Aug 2006 | JP |
| 2006-245732 | Sep 2006 | JP |
| 2006-246019 | Sep 2006 | JP |
| 2006-254350 | Sep 2006 | JP |
| 2006-319742 | Nov 2006 | JP |
| 2007-88630 | Apr 2007 | JP |
| 2007-140060 | Jun 2007 | JP |
| 2007-200329 | Aug 2007 | JP |
| 2007-201727 | Aug 2007 | JP |
| 2007-274034 | Oct 2007 | JP |
| 2007-282263 | Oct 2007 | JP |
| 2007-300452 | Nov 2007 | JP |
| 2008-28586 | Feb 2008 | JP |
| 2008-125105 | May 2008 | JP |
| 2008-136119 | Jun 2008 | JP |
| 2008-533838 | Aug 2008 | JP |
| 2008-276801 | Nov 2008 | JP |
| 2008-289014 | Nov 2008 | JP |
| 2009-80710 | Apr 2009 | JP |
| 2009-159253 | Jul 2009 | JP |
| 2009-188975 | Aug 2009 | JP |
| 2009-232290 | Oct 2009 | JP |
| 2009-296577 | Dec 2009 | JP |
| 2009-296583 | Dec 2009 | JP |
| 2010-15239 | Jan 2010 | JP |
| 2010-97353 | Apr 2010 | JP |
| 2010-511939 | Apr 2010 | JP |
| 2010-109789 | May 2010 | JP |
| 2010-522935 | Jul 2010 | JP |
| 2010-245940 | Oct 2010 | JP |
| 2011-118662 | Jun 2011 | JP |
| 2012-168966 | Sep 2012 | JP |
| 2012-215938 | Nov 2012 | JP |
| 2012-244340 | Dec 2012 | JP |
| 2013-25357 | Feb 2013 | JP |
| 2013-74499 | Apr 2013 | JP |
| 2013-93699 | May 2013 | JP |
| 2013-105468 | May 2013 | JP |
| 2013-530433 | Jul 2013 | JP |
| 2013-191065 | Sep 2013 | JP |
| 2014-503861 | Feb 2014 | JP |
| 2014-44724 | Mar 2014 | JP |
| 2015-520456 | Jul 2015 | JP |
| 2016-53929 | Apr 2016 | JP |
| 2017-532645 | Nov 2017 | JP |
| 2018-136828 | Aug 2018 | JP |
| 2019-114282 | Jul 2019 | JP |
| 2020-510929 | Apr 2020 | JP |
| 1997-0031883 | Jun 1997 | KR |
| 1999-0044201 | Jun 1999 | KR |
| 10-2004-0016688 | Feb 2004 | KR |
| 10-2004-0045338 | Jun 2004 | KR |
| 10-2005-0054684 | Jun 2005 | KR |
| 10-2006-0031959 | Apr 2006 | KR |
| 10-2006-0116902 | Nov 2006 | KR |
| 10-2007-0111270 | Nov 2007 | KR |
| 10-2008-0057326 | Jun 2008 | KR |
| 10-2008-0096042 | Oct 2008 | KR |
| 10-2009-0002641 | Jan 2009 | KR |
| 10-2009-0004176 | Jan 2009 | KR |
| 10-2009-0017901 | Feb 2009 | KR |
| 10-2009-0017906 | Feb 2009 | KR |
| 10-2009-0036226 | Apr 2009 | KR |
| 10-2009-0042499 | Apr 2009 | KR |
| 10-2009-0122805 | Dec 2009 | KR |
| 10-2009-0126516 | Dec 2009 | KR |
| 10-2012-0003323 | Jan 2012 | KR |
| 10-2012-0088746 | Aug 2012 | KR |
| 10-2012-0100433 | Sep 2012 | KR |
| 10-2013-0063019 | Jun 2013 | KR |
| 10-2013-0075783 | Jul 2013 | KR |
| 10-2013-0082190 | Jul 2013 | KR |
| 10-2013-0141688 | Dec 2013 | KR |
| 10-2014-0016244 | Feb 2014 | KR |
| 10-2014-0026263 | Mar 2014 | KR |
| 10-2014-0043370 | Apr 2014 | KR |
| 10-1989433 | Jun 2019 | KR |
| 1321955 | Mar 2010 | TW |
| 201415345 | Apr 2014 | TW |
| 201416959 | May 2014 | TW |
| 0211022 | Feb 2002 | WO |
| 2003077553 | Sep 2003 | WO |
| 2005086159 | Sep 2005 | WO |
| 2005109829 | Nov 2005 | WO |
| 2006048028 | May 2006 | WO |
| 2006063343 | Jun 2006 | WO |
| 2007002621 | Jan 2007 | WO |
| 2007102110 | Sep 2007 | WO |
| 2008030779 | Mar 2008 | WO |
| 2008030879 | Mar 2008 | WO |
| 2008040566 | Apr 2008 | WO |
| 2008067498 | Jun 2008 | WO |
| 2008090902 | Jul 2008 | WO |
| 2009143076 | Nov 2009 | WO |
| 2010001672 | Jan 2010 | WO |
| 2010134729 | Nov 2010 | WO |
| 2011126502 | Oct 2011 | WO |
| 2012028773 | Mar 2012 | WO |
| 2012051052 | Apr 2012 | WO |
| 2012079530 | Jun 2012 | WO |
| 2012087939 | Jun 2012 | WO |
| 2012103117 | Aug 2012 | WO |
| 2012126078 | Sep 2012 | WO |
| 2012154748 | Nov 2012 | WO |
| 2012170446 | Dec 2012 | WO |
| 2013097896 | Jul 2013 | WO |
| 2013132144 | Sep 2013 | WO |
| 2013173838 | Nov 2013 | WO |
| 2014197279 | Dec 2014 | WO |
| 2014200730 | Dec 2014 | WO |
| 2015192085 | Dec 2015 | WO |
| 2016022204 | Feb 2016 | WO |
| 2019067131 | Apr 2019 | WO |
| 2019217009 | Nov 2019 | WO |
| 2021112983 | Jun 2021 | WO |
| Entry |
|---|
| Screen captures from YouTube clip entitled “Samsung Gear S3 App launcher widget—App review” 5 pages, published on Dec. 26, 2016 by Mr Analytical. Retrieved from Internet <https://www.youtube.com/watch?v=HEfTv17peik> (Year: 2016). |
| Screen captures from YouTube clip entitled “Samsung Gear S3 Apps Launcher” 1 page, published on Feb. 5, 2017 by Trish's World. Retrieved from Internet <https://www.youtube.com/watch?v=zlamYA-4XSQ> (Year: 2017). |
| Screen captures from YouTube clip entitled “Samsung Gear S3 App launcher widget—App review” 11 pages, published on Dec. 26, 2016 by Mr Analytical. Retrieved from Internet (Year: 2016). |
| Office Action received for Australian Patent Application No. 2016266010, mailed on May 4, 2018, 4 pages. |
| Extended European Search Report received for European Patent Application No. 18185408.4, mailed on Oct. 17, 2018, 10 Pages. |
| Esther, Instructions for Kobo Books: How to change to scrolling mode and do table of contents navigation—Google Groups, XP055513050, Retrieved from the Internet: URL:https://groups.google.com/forum/print/msg/viphone/-dkqODh_31A/8acJK2dGPe8J?ctz=4607561_48_52_123900_48_436380 [retrieved on Oct. 5, 2018], Aug. 28, 2010, 3 Pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2018/032396, mailed on Jul. 30, 2018, 13 pages. |
| Office Action received for Australian Patent Application No. 2016266010, mailed on Aug. 23, 2018, 4 pages. |
| Decision to Grant received for European Patent Application No. 12704175.4, mailed on Jul. 19, 2018, 2 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,304, mailed on Jul. 24, 2018, 19 pages. |
| Notice of Allowance received for Taiwanese Patent Application No. 106144804, mailed on Jun. 27, 2018, 6 pages (2 pages of English Translation and 4 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2018-0035949, mailed on Jun. 20, 2018, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| “Q Pair, Posting Of A Blog”, Online Available at: <“http://www.leaderyou.co.kr/2595”>, Dec. 7, 2013, 24 pages (Official Copy Only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Intention to Grant received for European Patent Application No. 15713062.6, mailed on Oct. 8, 2018, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,298, mailed on Sep. 19, 2018, 41 pages. |
| Office Action received for Japanese Patent Application No. 2017-101107, mailed on Sep. 7, 2018, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/035326, mailed on Oct. 5, 2017, 22 pages. |
| Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US2017/035326, mailed on Aug. 7, 2017, 2 pages. |
| Notice of Allowance received for Taiwanese Patent Application No. 104117042, mailed on Nov. 17, 2017, 5 pages (2 Pages of English Translation and 3 Pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 14/641,289, mailed on Dec. 12, 2017, 5 pages. |
| Office Action received for Australian Patent Application No. 2016266010, mailed on Nov. 30, 2017, 5 pages. |
| Office Action received for European Patent Application No. 15713062.6, mailed on Dec. 6, 2017, 7 pages. |
| Office Action received for Chinese Patent Application No. 201510288981.9, mailed on Jul. 3, 2018, 19 pages (8 pages of English Translation and 11 pages of Official Copy). |
| Hanley, Ryan, “Aero Effects”, Windows 7 Editions, 2010, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/608,866, mailed on Nov. 2, 2018, 46 pages. |
| Intention to Grant received for European Patent Application No. 12704175.4, mailed on Mar. 22, 2018, 8 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2015-0072162, mailed on Dec. 27, 2017, 4 pages (2 pages of English Translation and 2 pages of Official copy). |
| Advisory Action received for U.S. Appl. No. 10/179,775, mailed on Oct. 13, 2015, 4 pages. |
| Advisory Action received for U.S. Appl. No. 10/179,775, mailed on Oct. 14, 2010, 2 pages. |
| Advisory Action received for U.S. Appl. No. 10/179,775, mailed on Sep. 15, 2009, 2 pages. |
| Advisory Action received for U.S. Appl. No. 12/890,499, mailed on Jan. 11, 2016, 3 pages. |
| Advisory Action received for U.S. Appl. No. 13/077,850, mailed on Apr. 24, 2014, 3 pages. |
| Advisory Action received for U.S. Appl. No. 13/077,855, mailed on Jun. 15, 2016, 4 pages. |
| Advisory Action received for U.S. Appl. No. 13/077,862, mailed on Apr. 7, 2016, 3 pages. |
| Advisory Action received for U.S. Appl. No. 13/077,874, mailed on Aug. 19, 2016, 3 pages. |
| Apple, “iPhone User's Guide”, Available at: <http://mesnotices.20minutes.fr/manuel-notice-mode-emploi/APPLE/IPHONE%2D%5FE#>, 2007, 137 pages. |
| Baig, ED, “Palm Pre: The Missing Manual”, Safari Books Online, Available at <http://my.safaribooksonline.com/book/operating-systems/0596528264>, Aug. 27, 2009, 16 pages. |
| Benge et al., “Designing Custom Controls”, IBM OS/2 Developer, The Magazine for Advanced Software Development, vol. 5, No. 2, 1993, pp. 72-85. |
| Chan, Christine, “Handoff Your Browser to Your iPhone or iPad! Plus A Chance To Win A Copy!”, Apr. 12, 2011, 2 pages. |
| “Chapter 13: Menus”, Apple Human Interface Guidelines, Available at: <https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/OSXHIGuidelines/index.html>, Aug. 20, 2009, pp. 165-190. |
| Cuyamaca LRC Computer Labs, “Topics in CommonSpace Application”, Available at: <http://www.cuyamaca.net/librarylab/Technical%20Help/cmspace.asp>, Retrieved on May 19, 2014, 16 pages. |
| Decision to Grant received for European Patent Application No. 10799259.6, mailed on Aug. 31, 2017, 2 pages. |
| Evaluation Report for Utility Model Patent received for Chinese Patent Application No. 201620051290.7, completed on Sep. 19, 2016, 11 pages (6 pages of English translation and 5 pages of Official Copy). |
| Fahey, M., “The iPad Blows Up iPhone Apps Real Good”, Available at <www.kotaku.com.au/2010/01/the-ipad-blows-up-iphone-apps-real-good/>, Jan. 28, 2010, 3 pages. |
| Fehily, C., “Visual QuickStart Guide: Microsoft Windows 7”, Peachpit Press, Sep. 8, 2009, 9 pages. |
| Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Apr. 5, 2006, 14 pages. |
| Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Aug. 16, 2013, 12 pages. |
| Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Jul. 8, 2009, 11 pages. |
| Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Jun. 22, 2010, 13 pages. |
| Final Office Action received for U.S. Appl. No. 10/179,775, mailed on May 22, 2015, 15 pages. |
| Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Oct. 8, 2008, 12 pages. |
| Final Office Action received for U.S. Appl. No. 12/843,814, mailed on Apr. 23, 2015, 28 pages. |
| Final Office Action received for U.S. Appl. No. 12/843,814, mailed on Jan. 31, 2014, 20 pages. |
| Final Office Action received for U.S. Appl. No. 12/843,814, mailed on Nov. 14, 2012, 13 pages. |
| Final Office Action received for U.S. Appl. No. 12/890,472, mailed on Feb. 6, 2013, 10 pages. |
| Final Office Action received for U.S. Appl. No. 12/890,482, mailed on Sep. 12, 2013, 10 pages. |
| Final Office Action received for U.S. Appl. No. 12/890,489, mailed on Aug. 14, 2013, 9 pages. |
| Final Office Action received for U.S. Appl. No. 12/890,499, mailed on May 22, 2017, 17 pages. |
| Final Office Action received for U.S. Appl. No. 12/890,499, mailed on Jul. 8, 2013, 17 pages. |
| Final Office Action received for U.S. Appl. No. 12/890,499, mailed on Oct. 19, 2015, 14 pages. |
| Final Office Action received for U.S. Appl. No. 13/077,850, mailed on Nov. 7, 2013, 14 pages. |
| Final Office Action received for U.S. Appl. No. 13/077,855, mailed on Mar. 17, 2014, 11 pages. |
| Final Office Action received for U.S. Appl. No. 13/077,855, mailed on Nov. 7, 2013, 14 pages. |
| Final Office Action received for U.S. Appl. No. 13/077,855, mailed on Mar. 24, 2016, 19 pages. |
| Final Office Action received for U.S. Appl. No. 13/077,862, mailed on Nov. 8, 2013, 15 pages. |
| Final Office Action received for U.S. Appl. No. 13/077,862, mailed on Oct. 22, 2015, 16 pages. |
| Final Office Action received for U.S. Appl. No. 13/077,867, mailed on May 23, 2013, 10 pages. |
| Final Office Action received for U.S. Appl. No. 13/077,874, mailed on Dec. 3, 2014, 23 pages. |
| Final Office Action received for U.S. Appl. No. 13/077,874, mailed on May 5, 2016, 26 pages. |
| Final Office Action received for U.S. Appl. No. 13/333,909, mailed on Dec. 5, 2013, 24 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,289, mailed on Jul. 1, 2016, 32 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,298, mailed on Oct. 4, 2017, 30 pages. |
| G Pad, “LG's Latest Uls That Shine More Lightly On The G-Pad”, Online Available at: <http://bungq.com/1014>, Nov. 11, 2013, 38 pages (2 pages of English Translation and 36 pages of Official Copy). |
| Harris et al., “Inside WordPerfect 6 for Windows”, New Riders Publishing, 1994, pp. 1104-1108. |
| Intention to Grant received for European Patent Application No. 10799259.6, mailed on Apr. 20, 2017, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2010/062314, issued on Jul. 10, 2012, 14 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2012/022401, mailed on Aug. 8, 2013, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/019306, mailed on Dec. 15, 2016, 10 pages. |
| International Preliminary Report on Patentability Received for PCT Patent Application No. PCT/US2015/019309, mailed on Dec. 15, 2016, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2010/062314, mailed on Jun. 22, 2011, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2012/022401, Jul. 6, 2012, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/019306, mailed on Jun. 17, 2015, 15 pages. |
| International Search Report and Written Opinion received for PCT Application No. PCT/US2015/019309, mailed on Jun. 25, 2015, 15 pages. |
| International Search Report received for PCT Patent Application No. PCT/US95/11025, mailed on Jan. 3, 1996, 3 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2012/022401, May 4, 2012, 8 pages. |
| Kimura, Ryoji, “Keynote presentation practice guide for iPad & iPhone”, K.K. Rutles, first edition, Feb. 29, 2012, 4 pages. {See Communication under 37 CFR § 1.98(a) (3)}. |
| King, Adrian, “Inside Windows 95”, Microsoft Press, Aug. 1994, pp. 176-182. |
| “Microsoft Windows 3.1”, Available at: <http://www.guidebookgallery.org/screenshots/win31>, 1992, pp. 1-31. |
| Non-Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Aug. 14, 2014, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Dec. 23, 2009, 13 Pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Dec. 23, 2015, 14 Pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Jan. 22, 2009, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Jul. 2, 2007, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Mar. 14, 2008, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Mar. 28, 2013, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/179,775, mailed on Oct. 12, 2005, 16 Pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/789,436, mailed on Jun. 25, 2012, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/843,814, mailed on Apr. 27, 2012, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/843,814, mailed on May 28, 2013, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/843,814, mailed on Oct. 8, 2014, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/890,472, mailed on Jul. 5, 2012, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/890,482, mailed on Sep. 27, 2012, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/890,489, mailed on Nov. 6, 2014, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/890,489, mailed on Nov. 30, 2012, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/890,499, mailed on Apr. 6, 2015, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/890,499, mailed on Nov. 1, 2016, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/890,499, mailed on Nov. 26, 2012, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/890,499, mailed on Sep. 11, 2014, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,850, mailed on Mar. 28, 2013, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,850, mailed on Sep. 10, 2015, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,855, mailed on Aug. 13, 2015, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,855, mailed on Mar. 28, 2013, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,862, mailed on Dec. 29, 2014, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,862, mailed on Mar. 15, 2013, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,867, mailed on Dec. 21, 2012, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,867, mailed on Jul. 20, 2012, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,874, mailed on Jun. 19, 2014, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,874, mailed on Dec. 3, 2015, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/333,909, mailed on Mar. 19, 2013, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/456,852, mailed on Jul. 1, 2015, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,298, mailed on Mar. 6, 2017, 26 pages. |
| Non Final Office Action received for U.S. Appl. No. 14/641,289, mailed on Mar. 11, 2016, 26 pages. |
| Non Final Office Action received for U.S. Appl. No. 14/641,289, mailed on Jul. 16, 2015, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,304, mailed on Sep. 11, 2017, 18 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2010339636, mailed on Jul. 3, 2014, 2 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2012209199, mailed on Jan. 27, 2016, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015201884, mailed on Oct. 4, 2016, 3 pages. |
| Notice of Allowance received for Australian Patent Application No. 2016202837, mailed on Apr. 21, 2017, 3 Pages. |
| Notice of Allowance received for Chinese Patent Application No. 201080064125.0, mailed on Sep. 8, 2015, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice Of Allowance received for Chinese Patent Application No. 201280006317.5, mailed on Feb. 17, 2017, 2 pages (1 pages of English Translation and 1 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201520364847.8, mailed on Nov. 5, 2015, 9 pages (7 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201620051290.7, mailed on Jun. 22, 2016, 2 Pages (Official Copy only) {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Japanese Patent Application No. 2015-095183, mailed on Apr. 21, 2017, 3 pages. (Official Copy Only) {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Japanese Patent Application No. 2016-130565, mailed on Aug. 28, 2017, 3 pages (Official Copy Only) {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Korean Patent Application No. 10-2013-7022057, mailed on Apr. 27, 2015, 2 pages (Official Copy only) {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Korean Patent Application No. 10-2014-7033660, mailed on Sep. 25, 2015, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2015-7013849, mailed on Mar. 28, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7017508, issued on Apr. 27, 2017, 3 pages (1 page of English translation and 2 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 104117041, mailed on Feb. 24, 2017, 3 pages (Official Copy Only) {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for U.S. Appl. No. 10/179,775, mailed on Aug. 24, 2017, 3 Pages. |
| Notice of Allowance received for U.S. Appl. No. 10/179,775, mailed on Jul. 13, 2017, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/789,436, mailed on Jan. 7, 2013, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/843,814, mailed on Jun. 22, 2016, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/890,482, mailed on May 8, 2014, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/890,489, mailed on Jul. 27, 2015, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/077,850, mailed on May 5, 2016, 15 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/077,855, mailed on Jan. 30, 2017, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/077,867, mailed on Mar. 12, 2014, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/077,867, mailed on Sep. 18, 2013, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/077,874, mailed on Dec. 9, 2016, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/077,874, mailed on Nov. 22, 2016, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/333,909, mailed on Mar. 31, 2014, 20 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/456,852, mailed on Jul. 31, 2015, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,289, mailed on Aug. 24, 2017, 6 pages. |
| Office Action received for Australian Patent Application No. 2010339636, mailed on Jun. 19, 2013, 3 pages. |
| Office Action received for Australian Patent Application No. 2012209199, mailed on Dec. 17, 2015, 3 pages. |
| Office Action received for Australian Patent Application No. 2012209199, mailed on Jan. 15, 2015, 3 pages. |
| Office Action received for Australian Patent Application No. 2015100490, mailed on Dec. 15, 2016, 2 pages. |
| Office Action received for Australian Patent Application No. 2015100490, mailed on Jun. 9, 2015, 6 pages. |
| Office Action received for Australian Patent Application No. 2015201884, mailed on Oct. 12, 2015, 4 pages. |
| Office Action received for Australian Patent Application No. 2016202837, mailed on Jan. 10, 2017, 2 pages. |
| Office Action received for Chinese Patent Application No. 201080064125.0, mailed on Jun. 10, 2014, 8 pages (Official Copy only) {See Communication under 37 CFR § 1.98(a) (3)}. |
| Office Action received for Chinese Patent Application No. 201080064125.0, mailed on Mar. 11, 2015, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201280006317.5, mailed on Jan. 11, 2016, 10 pages (5 pages of English Translation and 5 pages of official Copy). |
| Office Action received for Chinese Patent Application No. 201280006317.5, mailed on Jul. 11, 2016, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA201570256, mailed on Jul. 7, 2015, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570256, mailed on Mar. 17, 2016, 5 pages. |
| Office Action received for Danish Patent Application No. PA201570256, mailed on May 23, 2017, 3 pages. |
| Office Action received for Danish Patent Application PA201570256, mailed on Oct. 10, 2016, 3 pages. |
| Office Action received for European Patent Application No. 10799259.6, mailed on Jun. 1, 2015, 9 pages. |
| Office Action received for Hong Kong Patent Application No. 151051633, mailed on Jun. 5, 2015, 11 pages (Official Copy Only) {See Communication under 37 CFR § 1.98(a) (3)}. |
| Office Action received for Japanese Patent Application No. 2013-550664, mailed on Aug. 24, 2015, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2013-550664, mailed on Jun. 10, 2016, 3 pages (Official Copy only) {See Communication under 37 CFR § 1.98(a) (3)}. |
| Office Action received for Japanese Patent Application No. 2013-550664, mailed on Sep. 12, 2014, 10 pages (6 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2015-095183, mailed on Jun. 3, 2016, 13 pages (6 pages of English Translation and 7 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2012-7020548, mailed on Oct. 10, 2013, 5 pages (Official Copy only) {See Communication under 37 CFR § 1.98(a) (3)}. |
| Office Action received for Korean Patent Application No. 10-2013-7022057, mailed on May 28, 2014, 7 pages (3 pages of English Translation and 4 copies of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2014-7033660, mailed on Feb. 23, 2015, 3 pages (Official Copy only) {See Communication under 37 CFR § 1.98(a) (3)}. |
| Office Action received for Korean Patent Application No. 10-2015-0072162, mailed on Apr. 20, 2016, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2015-0072162, mailed on Feb. 27, 2017, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2015-7013849, mailed on Aug. 20, 2015, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7017508, mailed on Oct. 20, 2016, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104117041, mailed on Aug. 22, 2016, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104117042, mailed on Apr. 20, 2017, 18 pages (7 pages of English Translation and 11 pages of Official Copy). |
| Pogue, David, “Windows Vista for Starters: The Missing Manual”, Available at: <http://academic.safaribooksonline.com/book/operating-systems/0596528264>, Jan. 25, 2007, 18 pages. |
| “QPair”, Available at: <http://mongri.net/entry/G-Pad-83-0pair>, Dec. 20, 2013, 22 pages (10 pages of English translation and 12 pages of Official Copy). |
| Search Report received For Netherlands Patent Application No. 2014737, mailed on Oct. 29, 2015, 9 pages. |
| Summons to Attend Oral Proceedings received for European Application No. 10799259.6, mailed on Aug. 2, 2016, 16 pages. |
| Wolfe, Joanna, “Annotation Technologies: A Software and Research Review”, Computers and Composition, vol. 19, No. 4, 2002, pp. 471-497. |
| Written Opinion received for PCT Patent Application No. PCT/US95/11025, mailed on Oct. 4, 1996, 6 pages. |
| Ziegler, Chris, “Palm® Pre.™. for Dummies®”, For Dummies, Oct. 19, 2009, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/035326, mailed on Dec. 20, 2018, 19 pages. |
| Appeal Decision received for U.S. Appl. No. 13/077,862, mailed on Mar. 22, 2019, 10 pages. |
| Decision to Grant received for European Patent Application No. 15713062.6, mailed on Apr. 11, 2019, 2 pages. |
| Intention to Grant received for European Patent Application No. 15713062.6, mailed on Mar. 25, 2019, 7 pages. |
| Office Action received for Chinese Patent Application No. 201510288981.9, mailed on Mar. 6, 2019, 20 pages (10 pages of English Translation and 10 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 15/608,866, mailed on Mar. 8, 2019, 36 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,304, mailed on Feb. 27, 2019, 18 pages. |
| Office Action received for Australian Patent Application No. 2016266010, mailed on Nov. 28, 2018, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2018-0035949, mailed on Dec. 24, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for German Patent Application No. 102015208532.5, mailed on Apr. 1, 2019, 20 pages (10 pages of English Translation and 10 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-0035949, mailed on Apr. 24, 2019, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Extended European Search Report received for European Patent Application No. 17810737.1, mailed on Oct. 28, 2019, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/608,866, mailed on Dec. 18, 2019, 9 pages. |
| Minutes of Oral Hearing received for German Patent Application No. 102015208532.5, mailed on Dec. 13, 2019, 21 pages (3 pages of English Translation and 18 pages of Official Copy). |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/641,304, mailed on Dec. 2, 2019, 5 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2018/032396, mailed on Nov. 28, 2019, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,862, mailed on Nov. 21, 2019, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,298, mailed on Nov. 29, 2019, 47 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201710240907.9, mailed on Nov. 25, 2019, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2018-0035949, mailed on Nov. 28, 2019, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 14/641,298, mailed on May 16, 2019, 50 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,304, mailed on Oct. 15, 2019, 21 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-101107, mailed on Jun. 3, 2019, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 13/077,862, mailed on Jun. 20, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/077,862, mailed on Sep. 20, 2019, 2 pages. |
| Office Action received for Chinese Patent Application No. 201510288981.9, mailed on Jul. 1, 2019, 16 pages (8 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201710240907.9, mailed on Jun. 5, 2019, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for German Patent Application No. 102015208532.5, mailed on Aug. 21, 2019, 15 pages (5 pages of English Translation and 10 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 14/641,298, mailed on Jun. 26, 2020, 50 pages. |
| Office Action received for German Patent Application No. 102015208532.5, mailed on Apr. 21, 2020, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-0024632, mailed on May 18, 2020, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Examiner's Initiated Interview Summary received for U.S. Appl. No. 14/641,298, mailed on Mar. 10, 2020, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,304, mailed on Mar. 4, 2020, 21 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/608,866, mailed on Feb. 28, 2020, 2 pages. |
| Office Action received for Australian Patent Application No. 2018271366, mailed on Feb. 25, 2020, 5 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 15/608,866, mailed on Feb. 20, 2020, 2 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/641,304, mailed on Jul. 28, 2020, 5 pages. |
| Decision to Grant received for German Patent Application No. 102015208532.5, mailed on Sep. 22, 2020, 10 pages (1 page of English Translation and 9 pages of Official Copy). |
| Groom, Gyeong-A, “LG G pad 8.3 reviews-Q pair connecting smartphone and tablet PC”, Online Available at: https://m.blog.naver.com/PostView.nhn?blogId=feena74&logNo=140203710954&proxyReferer=https:%2F%2Fwww.google.com%2F, Dec. 30, 2013, 56 pages (28 pages of English Translation and 28 pages of Official Copy). |
| lazion.com, “G Pad 8.3, Q Pair to become one with your smartphone”, Online available at: https://lazion.com/2512682, Dec. 30, 2013, 24 pages (11 pages of English Translation and 13 pages of Official Copy). |
| Non-Final Office Action received for U.S. Appl. No. 13/077,862, mailed on Jul. 17, 2020, 20 pages. |
| Notice of Allowance Action received for U.S. Appl. No. 14/641,304, mailed on Sep. 9, 2020, 15 pages. |
| Office Action received for Australian Patent Application No. 2018271366, mailed on Oct. 26, 2020, 5 pages. |
| Office Action received for Chinese Patent Application No. 201780033771.2, mailed on Jul. 15, 2020, 18 pages (9 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2019-124728, mailed on Sep. 18, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Q Pair, Posting of a blog, Online Available at: <http://www.leaderyou.co.kr/2595>, Dec. 7, 2013, 41 pages (23 page of English Translation and 18 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-0024632, mailed on Dec. 29, 2020, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Board Opinion received for Chinese Patent Application No. 201510288981.9, mailed on Jan. 4, 2021, 21 pages (9 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2018271366, mailed on Jan. 19, 2021, 5 pages. |
| Office Action received for European Patent Application No. 17810737.1, mailed on Jan. 20, 2021, 6 pages. |
| Office Action received for Japanese Patent Application No. 2019-124728, mailed on Dec. 14, 2020, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| “LG G Pad 8.3 Tablet Q Remote User”, Available at:—<https://mushroomprincess.tistory.com/1320>, Dec. 26, 2013, 37 pages (20 pages of English Translation and 17 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201780033771.2, mailed on Feb. 3, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Board Decision received for Chinese Patent Application No. 201510288981.9, mailed on May 6, 2021, 31 pages (3 pages of English Translation and 28 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0024632, mailed on Jul. 26, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Decision to Grant received for Japanese Patent Application No. 2019-124728, mailed on Apr. 2, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Intention to Grant received for European Patent Application No. 17810737.1, mailed on Jul. 5, 2021, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/859,101, mailed on Aug. 5, 2021, 19 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/641,298, mailed on Mar. 22, 2021, 19 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, mailed on Aug. 23, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/483,549, mailed on Aug. 24, 2022, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202110409273.1, mailed on Aug. 2, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201910055588.3, mailed on Mar. 2, 2022, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for Australian Patent Application No. 2021201243, mailed on Feb. 17, 2022, 4 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/859,101, mailed on Feb. 25, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/859,101, mailed on Mar. 25, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,564, mailed on Mar. 14, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, mailed on Apr. 29, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,899, mailed on Apr. 27, 2022, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/483,582, mailed on Feb. 15, 2022, 2 pages. |
| Final Office Action received for U.S. Appl. No. 17/483,564, mailed on Apr. 18, 2022, 23 pages. |
| Final Office Action received for U.S. Appl. No. 17/483,679, mailed on May 24, 2022, 21 pages. |
| Final Office Action received for U.S. Appl. No. 17/484,899, mailed on May 12, 2022, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,549, mailed on Jan. 11, 2022, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,564, mailed on Jan. 6, 2022, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,679, mailed on Feb. 1, 2022, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/484,899, mailed on Jan. 24, 2022, 24 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,549, mailed on Apr. 15, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,582, mailed on Apr. 19, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,582, mailed on Jan. 20, 2022, 10 pages. |
| Office Action received for Australian Patent Application No. 2021201243, mailed on Jun. 1, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,564, mailed on Jul. 21, 2022, 5 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2021-074395, mailed on Jun. 27, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/859,101, mailed on Nov. 30, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/641,298, mailed on Dec. 9, 2021, 5 pages. |
| Decision on Appeal received for U.S. Appl. No. 14/641,298, mailed on Nov. 1, 2021, 9 pages. |
| Decision to Grant received for European Patent Application No. 17810737.1, mailed on Nov. 11, 2021, 2 pages. |
| Examiner-Initiated Interview Summary received for U.S. Appl. No. 16/859,101, mailed on Dec. 1, 2021, 2 pages. |
| Extended European Search Report received for European Patent Application No. 21206800.1, mailed on Jan. 24, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,298, mailed on Nov. 29, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/859,101, mailed on Jan. 18, 2022, 10 pages. |
| Office Action received for Chinese Patent Application No. 201910055588.3, mailed on Nov. 24, 2021, 24 pages (14 pages of English Translation and 10 pages of Official Copy). |
| Office Action received for European Patent Application No. 15714698.6, mailed on Oct. 13, 2021, 2 pages. |
| Record of Oral Hearing received for U.S. Appl. No. 14/641,298, mailed on Oct. 8, 2021, 17 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-0143923, mailed on Jan. 27, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110409273.1, mailed on Jan. 11, 2022, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/859,101, mailed on Feb. 7, 2022, 2 pages. |
| Office Action received for Australian Patent Application No. 2018271366, mailed on May 17, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,899, mailed on Sep. 1, 2022, 5 pages. |
| Advisory Action received for U.S. Appl. No. 17/483,679, mailed on Sep. 20, 2022, 8 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/029261, mailed on Aug. 29, 2022, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,542, mailed on Sep. 22, 2022, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/029261, mailed on Oct. 20, 2022, 18 pages. |
| Advisory Action received for U.S. Appl. No. 14/263,889, mailed on May 26, 2016, 4 pages. |
| Advisory Action received for U.S. Appl. No. 15/725,868, mailed on Dec. 10, 2018, 5 pages. |
| Advisory Action received for U.S. Appl. No. 16/666,073, mailed on Jul. 7, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/666,971, mailed on Jun. 9, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/666,971, mailed on Apr. 15, 2016, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/725,868, mailed on Jul. 25, 2018, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/725,868, mailed on May 13, 2019, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/725,868, mailed on Nov. 20, 2018, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,542, mailed on May 22, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,542, mailed on Nov. 23, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,542, mailed on Apr. 21, 2023, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,542, mailed on Jun. 21, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, mailed on Aug. 18, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, mailed on Dec. 18, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, mailed on May 19, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,899, mailed on Feb. 14, 2024, 8 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,899, mailed on Jun. 24, 2024, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,899, mailed on Sep. 12, 2023, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/732,355, mailed on Sep. 20, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/067,350, mailed on Jul. 29, 2024, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/067,350, mailed on Mar. 13, 2024, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/067,350, mailed on Sep. 11, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/140,449, mailed on Aug. 27, 2024, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/165,144, mailed on Feb. 27, 2024, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/165,144, mailed on Jul. 15, 2024, 4 pages. |
| Baudisch et al., “Back-of-device interaction allows creating very small touch devices”, Chi 2009—Digital Life, New World: Conference Proceedings and Extended Abstracts; The 27th Annual Chi Conference on Human Factors in Computing Systems, Available online at <http://dx.doi.org/10.1145/1518701.1518995>, Apr. 9, 2009, pp. 1923-1932. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/725,868, mailed on Aug. 23, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/725,868, mailed on Sep. 30, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/666,073, mailed on Apr. 6, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/666,073, mailed on Apr. 26, 2021, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/666,073, mailed on Feb. 22, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/666,073, mailed on Mar. 11, 2021, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,542, mailed on Aug. 25, 2023, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,542, mailed on Feb. 5, 2024, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/666,971, mailed on Jan. 16, 2024, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/666,971, mailed on Sep. 29, 2023, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/732,204, mailed on Dec. 4, 2023, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/732,204, mailed on Jan. 18, 2024, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/732,204, mailed on Nov. 16, 2023, 6 pages. |
| On Appeal received for Korean Patent Application No. 10-2020-7034959, mailed on Jul. 25, 2022, 28 pages (5 pages of English Translation and 23 pages of Official Copy). |
| On Opposition received for Australian Patent Application No. 2018271366, mailed on Mar. 3, 2023, 3 pages. |
| To Grant received for European Patent Application No. 10763539.3, mailed on Jul. 19, 2018, 3 pages. |
| To Grant received for European Patent Application No. 15714698.6, mailed on Apr. 5, 2024, 2 pages. |
| To Grant received for European Patent Application No. 18188433.9, mailed on Aug. 13, 2020, 3 pages. |
| To Grant received for Japanese Patent Application No. 2023-571312, mailed on Aug. 29, 2024, 3 pages (1 page of English Translation and 2 pages of Official Copy). Decision to Grant received for Japanese Patent Application No. 2024-003876, mailed on. |
| Sep. 2, 2024, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| To Refuse received for Japanese Patent Application No. 2013-503731, mailed on Jun. 23, 2014, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| To Refuse received for Japanese Patent Application No. 2022-116534, mailed on Jan. 29, 2024, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Pre-Review Report received for Japanese Patent Application No. 2014-212867, mailed on Nov. 4, 2016, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Extended European Search Report received for European Patent Application No. 18188433.9, mailed on Oct. 29, 2018, 8 pages. |
| Extended European Search Report received for European Patent Application No. 23172038.4, mailed on Oct. 11, 2023, 10 pages. |
| Extended European Search Report received for European Patent Application No. 24160234.1, mailed on May 28, 2024, 6 pages. |
| Extended European Search Report received for European Patent Application No. 24164409.5, mailed on Jun. 14, 2024, 5 pages. |
| Final Office Action received for U.S. Appl. No. 12/794,766, mailed on Nov. 26, 2012, 23 pages. |
| Final Office Action received for U.S. Appl. No. 14/263,889, mailed on Jan. 4, 2016, 9 pages. |
| Final Office Action received for U.S. Appl. No. 15/725,868, mailed on Sep. 27, 2018, 25 pages. |
| Final Office Action received for U.S. Appl. No. 16/666,073, mailed on Apr. 17, 2020, 18 pages. |
| Final Office Action received for U.S. Appl. No. 17/332,829, mailed on Feb. 6, 2023, 19 pages. |
| Final Office Action received for U.S. Appl. No. 17/483,564, mailed on May 25, 2023, 26 pages. |
| Final Office Action received for U.S. Appl. No. 17/483,679, mailed on Feb. 6, 2024, 45 pages. |
| Final Office Action received for U.S. Appl. No. 17/483,679, mailed on Jun. 13, 2023, 33 pages. |
| Final Office Action received for U.S. Appl. No. 17/484,899, mailed on Nov. 6, 2023, 39 pages. |
| Final Office Action received for U.S. Appl. No. 17/666,971, mailed on May 12, 2023, 29 pages. |
| Final Office Action received for U.S. Appl. No. 17/732,355, mailed on Nov. 3, 2023, 21 pages. |
| Final Office Action received for U.S. Appl. No. 18/067,350, mailed on Dec. 13, 2023, 44 pages. |
| Final Office Action received for U.S. Appl. No. 18/067,350, mailed on Oct. 31, 2024, 44 pages. |
| Final Office Action received for U.S. Appl. No. 18/140,449, mailed on Oct. 18, 2024, 11 pages. |
| Final Office Action received for U.S. Appl. No. 18/165,144, mailed on Jun. 11, 2024, 32 pages. |
| Intention to Grant received for European Patent Application No. 10763539.3, mailed on Mar. 15, 2018, 6 pages. |
| Intention to Grant received for European Patent Application No. 15714698.6, mailed on Dec. 8, 2023, 9 pages. |
| Intention to Grant received for European Patent Application No. 18188433.9, mailed on Apr. 6, 2020, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2010/050311, mailed on Oct. 18, 2012, 11 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/029261, mailed on Nov. 30, 2023, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/029580, mailed on Nov. 30, 2023, 14 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2010/050311, mailed on Aug. 24, 2011, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/029580, mailed on Nov. 7, 2022, 20 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/020569, mailed on Nov. 13, 2023, 23 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/032911, mailed on Jan. 4, 2024, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/033372, mailed on Jan. 12, 2024, 21 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2010/050311, mailed on Dec. 21, 2010, 6 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/029580, mailed on Sep. 5, 2022, 13 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2023/020569, mailed on Sep. 21, 2023, 14 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2023/033372, mailed on Nov. 22, 2023, 13 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 15714698.6, mailed on Dec. 16, 2022, 4 pages. |
| Koyama Kaori, “Mac Fan Macintosh Master Book Mac Os X v10.4 ”Tiger“ & iLife”, '06 version, Mainichi Communications Inc. Nobuyuki Nakagawa, Jul. 9, 2007, 4 pages (Official Copy Only). {See Communication Under Rule 37 CFR § 1.98(a) (3)}. |
| Non-Final Office Action received for U.S. Appl. No. 12/794,766, mailed on Aug. 5, 2013, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/794,766, mailed on Jun. 25, 2012, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/794,768, mailed on Oct. 10, 2012, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/263,889, mailed on Jul. 2, 2015, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/263,889, mailed on Jul. 26, 2016, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/725,868, mailed on Apr. 27, 2018, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/725,868, mailed on Feb. 12, 2019, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/666,073, mailed on Dec. 10, 2019, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/332,829, mailed on Aug. 1, 2022, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,542, mailed on Jan. 31, 2023, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,564, mailed on Nov. 28, 2022, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,679, mailed on Dec. 9, 2022, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,679, mailed on Sep. 13, 2023, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/484,899, mailed on Jun. 14, 2023, 41 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/484,899, mailed on Mar. 21, 2024, 42 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/666,971, mailed on Dec. 8, 2022, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/732,204, mailed on Aug. 4, 2023, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/732,355, mailed on Aug. 4, 2023, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/067,350, mailed on Aug. 3, 2023, 41 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/067,350, mailed on May 28, 2024, 43 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/140,449, mailed on May 24, 2024, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/165,144, mailed on Dec. 27, 2023, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/165,144, mailed on Sep. 11, 2024, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/380,116, mailed on Jul. 18, 2024, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/422,571, mailed on Sep. 26, 2024, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/535,820, mailed on Sep. 25, 2024, 27 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2010350749, mailed on Jan. 13, 2015, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015201127, mailed on Feb. 14, 2017, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018271366, mailed on Mar. 31, 2023, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021201243, mailed on Feb. 23, 2023, 3 pages. |
| Notice of Allowance received for Brazilian Patent Application No. BR112012025746-3, mailed on Jul. 6, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201010602653.9, mailed on Nov. 15, 2014, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 2010106600623.4, mailed on Aug. 11, 2014, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201410575145.4, mailed on May 10, 2018, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2014-212867, mailed on Mar. 30, 2018, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2016-151497, mailed on Jun. 4, 2018, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2019-182484, mailed on Aug. 30, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-154573, mailed on Nov. 11, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2022-116534, mailed on Jun. 24, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2022-197327, mailed on May 31, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2023-571161, mailed on Jul. 30, 2024, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2012-7028535, mailed on Jul. 16, 2014, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2014-7005164, mailed on Dec. 21, 2014, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2014-7029838, mailed on Jul. 28, 2015, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2015-7007050, mailed on Feb. 26, 2016, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7014580, mailed on Dec. 17, 2019, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7036975, mailed on Sep. 18, 2019, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7002845, mailed on Sep. 24, 2020, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-0053111, mailed on Jun. 25, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-7005442, mailed on Jan. 22, 2024, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-7039382, mailed on Feb. 13, 2024, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2024-7000870, mailed on Feb. 13, 2024, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011623, mailed on Jan. 16, 2014, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Mexican Patent Application No. MX/a/2014/004295, mailed on May 21, 2015, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Mexican Patent Application No. MX/a/2015/010523, mailed on May 25, 2016, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Mexican Patent Application No. MX/a/2016/012174, mailed on Jan. 17, 2020, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Mexican Patent Application No. MX/a/2020/003290, mailed on Feb. 9, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 099132253, mailed on Apr. 27, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 099132254, mailed on Feb. 18, 2014, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 12/794,766, mailed on Jan. 17, 2014, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/794,768, mailed on Mar. 22, 2013, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/263,889, mailed on Feb. 1, 2017, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/263,889, mailed on Jun. 16, 2017, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/725,868, mailed on Jun. 12, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/666,073, mailed on Jan. 21, 2021, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,542, mailed on Aug. 11, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,542, mailed on Dec. 20, 2023, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,564, mailed on Jul. 17, 2023, 46 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/484,899, mailed on Aug. 26, 2024, 21 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/666,971, mailed on Aug. 16, 2023, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/666,971, mailed on Dec. 15, 2023, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/732,204, mailed on Oct. 12, 2023, 8 pages. |
| Office Action received for Australian Patent Application No. 2010350749, mailed on Oct. 16, 2013, 3 pages. |
| Office Action received for Australian Patent Application No. 2015201127, mailed on Mar. 21, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2021201243, mailed on Dec. 12, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2023201057, mailed on Jan. 25, 2024, 6 pages. |
| Office Action received for Australian Patent Application No. 2023201057, mailed on Jun. 19, 2024, 5 pages. |
| Office Action received for Australian Patent Application No. 2023201057, mailed on Oct. 24, 2024, 3 pages. |
| Office Action received for Brazilian Patent Application No. BR112012025746-3, mailed on Jun. 2, 2020, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201010602653.9, mailed on Apr. 1, 2013, 21 pages (13 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201010602653.9, mailed on Dec. 9, 2013, 10 pages (6 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201010602653.9, mailed on May 15, 2014, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 2010106600623.4, mailed on Apr. 28, 2014, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 2010106600623.4, mailed on Jan. 24, 2014, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 2010106600623.4, mailed on May 2, 2013, 27 pages (15 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201410575145.4, mailed on Feb. 13, 2017, 18 pages (11 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201410575145.4, mailed on Nov. 30, 2017, 17 pages (11 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110894284.3, mailed on Jun. 27, 2024, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202311835200.4, mailed on Aug. 29, 2024, 16 pages (7 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202410030102.1, mailed on Jul. 23, 2024, 18 pages (9 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for European Patent Application No. 10763539.3, mailed on Jun. 13, 2016, 5 pages. |
| Office Action received for European Patent Application No. 15714698.6, mailed on Apr. 18, 2023, 14 pages. |
| Office Action received for European Patent Application No. 21206800.1, mailed on Jun. 30, 2023, 6 pages. |
| Office Action received for European Patent Application No. 22733778.9, mailed on Oct. 22, 2024, 6 pages. |
| Office Action received for Japanese Patent Application No. 2013-503731, mailed on Mar. 3, 2014, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2013-503731, mailed on Sep. 24, 2013, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2014-212867, mailed on Aug. 18, 2017, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2014-212867, mailed on Jun. 29, 2015, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-151497, mailed on Sep. 25, 2017, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-127760, mailed on Feb. 22, 2019, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-127760, mailed on Jul. 5, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2019-182484, mailed on Dec. 4, 2020, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2022-116534, mailed on Aug. 28, 2023, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2022-197327, mailed on Mar. 1, 2024, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2023-571161, mailed on May 28, 2024, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2023-571312, mailed on Jul. 16, 2024, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2024-003876, mailed on Jul. 2, 2024, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2012-7028535, mailed on Nov. 26, 2013, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2014-7005164, mailed on May 23, 2014, 15 pages (6 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2014-7029838, mailed on Dec. 20, 2014, 13 pages (5 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2015-7007050, mailed on Apr. 16, 2015, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2015-7007050, mailed on Oct. 23, 2015, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014580, mailed on Jan. 30, 2018, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014580, mailed on Jul. 30, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014580, mailed on Jun. 29, 2017, 7 pages (1 page of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014580, mailed on Sep. 19, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014580, mailed on Sep. 27, 2016, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7002774, mailed on Apr. 18, 2017, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7002774, mailed on Jul. 30, 2018, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7002774, mailed on Sep. 20, 2018, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7036975, mailed on Mar. 22, 2019, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7002845, mailed on Feb. 17, 2020, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7034959, mailed on Jan. 27, 2022, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7034959, mailed on Mar. 2, 2021, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7034959, mailed on Oct. 27, 2021, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-0053111, mailed on Dec. 12, 2022, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-0053111, mailed on Jun. 29, 2023, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-0053111, mailed on Oct. 23, 2023, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7006973, mailed on May 19, 2022, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7006973, mailed on Nov. 24, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2023-7005442, mailed on Jul. 25, 2023, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2014/004295, mailed on Aug. 21, 2014, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2014/004295, mailed on Jan. 20, 2015, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2015/010523, mailed on Jan. 26, 2016, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2016/012174, mailed on Apr. 10, 2019, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2016/012174, mailed on Aug. 8, 2019, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2020/003290, mailed on Nov. 11, 2022, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2020/003290, mailed on Oct. 26, 2022, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2023/005388, mailed on Dec. 15, 2023, 18 pages (9 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2023/005388, mailed on Jun. 2, 2023, 24 pages (12 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 099132253, mailed on Jun. 24, 2013, 16 pages (8 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 099132253, mailed on Mar. 27, 2014, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 099132254, mailed on May 27, 2013, 24 pages (12 pages of English Translation and 12 pages of Official Copy). |
| Sharf et al., “SnapPaste: an interactive technique for easy mesh composition”, The Visual Computer; International Journal of Computer Graphics, Springer, Berlin, De, vol. 22, No. 9-11, Available Online at <http://dx.doi.org/10.1007/s00371-006-0068-5>, Aug. 25, 2006, pp. 835-844. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/484,899, mailed on Oct. 29, 2024, 5 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/484,899, mailed on Sep. 30, 2024, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/165,144, mailed on Dec. 23, 2024, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/745,680, mailed on Dec. 12, 2024, 2 pages. |
| Office Action received for Australian Patent Application No. 2023201057, mailed on Dec. 19, 2024, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/067,350, mailed on Nov. 26, 2024, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/140,449, mailed on Nov. 26, 2024, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/745,680, mailed on Nov. 20, 2024, 2 pages. |
| Intention to Grant received for European Patent Application No. 24160234.1, mailed on Nov. 4, 2024, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2023/020569, mailed on Nov. 21, 2024, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,679, mailed on Nov. 21, 2024, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/745,680, mailed on Nov. 12, 2024, 8 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20180329586 A1 | Nov 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62506548 | May 2017 | US |
