Patent Grant
12131007
The disclosed embodiments relate generally to portable electronic devices, and more particularly, to animating user interface transitions on portable multifunction devices with touch-sensitive displays.
As portable electronic devices become more compact, and the number of functions performed by a given device increases, it has become a significant challenge to design a user interface that allows users to easily interact with a multifunction device. This challenge is particularly significant for handheld portable devices, which have much smaller screens than desktop or laptop computers. This situation is unfortunate because the user interface is the gateway through which users receive not only content but also responses to user actions or behaviors, including user attempts to access a device's features, tools, and functions. Some portable communication devices (e.g., mobile telephones, sometimes called mobile phones, cell phones, cellular telephones, and the like) have resorted to adding more pushbuttons, increasing the density of pushbuttons, overloading the functions of pushbuttons, or using complex menu systems to allow a user to access, store and manipulate data. These conventional user interfaces often result in complicated key sequences and menu hierarchies that must be memorized by the user.
Many conventional user interfaces, such as those that include physical pushbuttons, are also inflexible. This may prevent a user interface from being configured and/or adapted by either an application running on the portable device or by users. When coupled with the time consuming requirement to memorize multiple key sequences and menu hierarchies, and the difficulty in activating a desired pushbutton, such inflexibility is frustrating to most users.
In addition, a user may get lost in the myriad of user interfaces that are displayed on a multifunction device. It may be difficult for a user to follow the changes between the various interfaces, both changes between applications and changes within a particular application. Abrupt changes between user interfaces may be particularly jarring and confusing to a user, there by making the device difficult to use and frustrating the user.
Accordingly, there is a need for more transparent and intuitive user interfaces for portable devices that enable a user to easily navigate the user interfaces that are displayed on a multifunction device.
The above deficiencies and other problems associated with user interfaces for portable devices are reduced or eliminated by the disclosed portable multifunction device. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen”) with a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through finger contacts and gestures on the touch-sensitive display. In some embodiments, the functions may include telephoning, video conferencing, e-mailing, instant messaging, blogging, digital photographing, digital videoing, web browsing, digital music playing, and/or digital video playing. Instructions for performing these functions may be included in, a computer readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, a computer-implemented method is performed at a computing device with a touch screen display. The computer-implemented method includes: displaying a first set of a first plurality of application launch icons in a first area on the touch screen display, wherein the first plurality of application launch icons includes a plurality of sets of application launch icons that are separately displayed in the first area of the touch screen display; displaying a second plurality of application launch icons in a second area on the touch screen display, wherein the second area is different from the first area; in response to detecting a first finger gesture on the touch screen display in the first area, replacing display of the first set of the first plurality of application launch icons with display of a second set of the first plurality of application launch icons in the first area on the touch screen display while maintaining the display of the second plurality of application launch icons in the second area on the touch screen display; and, in response to detecting activation of any respective application launch icon in the plurality of application launch icons, displaying a first animation of a transition from display of application launch icons to display of an application that corresponds to the activated application launch icon. The first animation comprises expanding an image of the application.
In accordance with some embodiments, a graphical user interface on a computing device with a touch screen display includes: a first set of a first plurality of application launch icons displayed in a first area on the touch screen display, wherein the first plurality of application launch icons includes a plurality of sets of application launch icons that are separately displayed in the first area of the touch screen display; and a second plurality of application launch icons displayed in a second area on the touch screen display, wherein the second area is different from the first area. In response to detecting a first finger gesture on the touch screen display in the first area, display of the first set of the first plurality of application launch icons is replaced with display of a second set of the first plurality of application launch icons in the first area on the touch screen display while maintaining the display of the second plurality of application launch icons in the second area on the touch screen display. In response to detecting activation of any respective application launch icon in the plurality of application launch icons, a first animation is displayed of a transition from display of application launch icons to display of an application that corresponds to the activated application launch icon. The first animation comprises expanding an image of the application.
In accordance with some embodiments, a computing device includes: a touch screen display; one or more processors; memory; and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for: displaying a first set of a first plurality of application launch icons in a first area on the touch screen display, wherein the first plurality of application launch icons includes a plurality of sets of application launch icons that are separately displayed in the first area of the touch screen display; displaying a second plurality of application launch icons in a second area on the touch screen display, wherein the second area is different from the first area; replacing, in response to detecting a first finger gesture on the touch screen display in the first area, display of the first set of the first plurality of application launch icons with display of a second set of the first plurality of application launch icons in the first area on the touch screen display while maintaining the display of the second plurality of application launch icons in the second area on the touch screen display; and displaying, in response to detecting activation of any respective application launch icon in the plurality of application launch icons, a first animation of a transition from display of application launch icons to display of an application that corresponds to the activated application launch icon. The first animation comprises expanding an image of the application.
In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which when executed by a device with a touch screen display, cause the device to: display a first set of a first plurality of application launch icons in a first area on the touch screen display, wherein the first plurality of application launch icons includes a plurality of sets of application launch icons that are separately displayed in the first area of the touch screen display; display a second plurality of application launch icons in a second area on the touch screen display, wherein the second area is different from the first area; replace, in response to detecting a first finger gesture on the touch screen display in the first area, display of the first set of the first plurality of application launch icons with display of a second set of the first plurality of application launch icons in the first area on the touch screen display while maintaining the display of the second plurality of application launch icons in the second area on the touch screen display; and display, in response to detecting activation of any respective application launch icon in the plurality of application launch icons, a first animation of a transition from display of application launch icons to display of an application that corresponds to the activated application launch icon. The first animation comprises expanding an image of the application.
In accordance with some embodiments, a computing device includes: a touch screen display; means for displaying a first set of a first plurality of application launch icons in a first area on the touch screen display, wherein the first plurality of application launch icons includes a plurality of sets of application launch icons that are separately displayed in the first area of the touch screen display; means for displaying a second plurality of application launch icons in a second area on the touch screen display, wherein the second area is different from the first area; means for replacing, in response to detecting a first finger gesture on the touch screen display in the first area, display of the first set of the first plurality of application launch icons with display of a second set of the first plurality of application launch icons in the first area on the touch screen display while maintaining the display of the second plurality of application launch icons in the second area on the touch screen display; and means for displaying, in response to detecting activation of any respective application launch icon in the plurality of application launch icons, a first animation of a transition from display of application launch icons to display of an application that corresponds to the activated application launch icon. The first animation comprises expanding an image of the application.
In accordance with some embodiments, a computer-implemented method is performed at a portable multifunction device with a touch screen display. The computer-implemented method includes: displaying a home menu comprising a plurality of application launch icons; detecting activation of any respective application launch icon; and, in response to detecting the activation, displaying a first animation of a transition from display of the home menu to display of an application that corresponds to the activated application launch icon. The first animation comprises expanding an image of the application.
In accordance with some embodiments, a graphical user interface on a portable multifunction device with a touch screen display includes a home menu comprising a plurality of application launch icons; and applications that correspond to the application launch icons. In response to detecting activation of any respective application launch icon, a first animation is displayed of a transition from display of the home menu to display of an application that corresponds to the activated application launch icon, wherein the first animation comprises expanding an image of the application.
In accordance with some embodiments, a portable multifunction device includes: a touch screen display; one or more processors; memory; and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for: displaying a home menu comprising a plurality of application launch icons; detecting activation of any respective application launch icon; and displaying, in response to detecting the activation, a first animation of a transition from display of the home menu to display of an application that corresponds to the activated application launch icon. The first animation comprises expanding an image of the application.
In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which when executed by a portable multifunction device with a touch screen display, cause the portable multifunction device to: display a home menu comprising a plurality of application launch icons; detect activation of any respective application launch icon; and display, in response to detecting the activation, a first animation of a transition from display of the home menu to display of an application that corresponds to the activated application launch icon. The first animation comprises expanding an image of the application.
In accordance with some embodiments, a portable multifunction device includes: a touch screen display; means for displaying a home menu comprising a plurality of application launch icons; means for detecting activation of any respective application launch icon; and means for displaying, in response to detecting the activation, a first animation of a transition from display of the home menu to display of an application that corresponds to the activated application launch icon, wherein the first animation comprises expanding an image of the application.
In accordance with some embodiments, a computer-implemented method is performed at a portable multifunction device with a touch screen display. The computer-implemented method includes: displaying a first user interface comprising a group of items; detecting a gesture to select an item in the group; and, in response to detecting the gesture, displaying a first animation of a transition from display of the first user interface to display of a second user interface corresponding to the selected item. The first animation comprises sliding the second user interface onto the touch screen display from a first side of the display.
In accordance with some embodiments, a graphical user interface on a portable multifunction device with a touch screen display includes a first user interface comprising a group of items; and a second user interface corresponding to a selected item in the group. In response to detecting a gesture to select an item in the group while the first user interface is displayed, a first animation is displayed of a transition from display of the first user interface to display of the second user interface corresponding to the selected item. The first animation comprises sliding the second user interface onto the touch screen display from a first side of the display.
In accordance with some embodiments, a portable multifunction device includes: a touch screen display; one or more processors; memory; and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for: displaying a first user interface comprising a group of items; detecting a gesture to select an item in the group; and displaying, in response to detecting the gesture, a first animation of a transition from display of the first user interface to display of a second user interface corresponding to the selected item. The first animation comprises sliding the second user interface onto the touch screen display from a first side of the display.
In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which when executed by a portable multifunction device with a touch screen display, cause the portable multifunction device to: display a first user interface comprising a group of items; detect a gesture to select an item in the group; and display, in response to detecting the gesture, a first animation of a transition from display of the first user interface to display of a second user interface corresponding to the selected item. The first animation comprises sliding the second user interface onto the touch screen display from a first side of the display.
In accordance with some embodiments, a portable multifunction device includes: a touch screen display; means for displaying a first user interface comprising a group of items; means for detecting a gesture to select an item in the group; and means for displaying, in response to detecting the gesture, a first animation of a transition from display of the first user interface to display of a second user interface corresponding to the selected item. The first animation comprises sliding the second user interface onto the touch screen display from a first side of the display.
In accordance with some embodiments, a computer-implemented method is performed at a portable multifunction device with a touch screen display. The computer-implemented method includes: displaying a first user interface; detecting a gesture on the touch screen display to select a second user interface; and, in response to detecting the gesture, displaying an animation of a transition from display of the first user interface to display of the second user interface. The animation comprises sliding a first element of the second user interface onto the display from a first side of the display while simultaneously sliding a second element of the second user interface across the top of the first element.
In accordance with some embodiments, a graphical user interface on a portable multifunction device with a touch screen display includes first and second user interfaces. In response to detecting a gesture on the touch screen display to select the second user interface while the first user interface is displayed, an animation is displayed of a transition from display of the first user interface to display of the second user interface. The animation comprises sliding a first element of the second user interface onto the display from a first side of the display while simultaneously sliding a second element of the second user interface across the top of the first element.
In accordance with some embodiments, a portable multifunction device includes: a touch screen display; one or more processors; memory; and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for: displaying a first user interface; detecting a gesture on the touch screen display to select a second user interface; and displaying, in response to detecting the gesture, an animation of a transition from display of the first user interface to display of the second user interface. The animation comprises sliding a first element of the second user interface onto the display from a first side of the display while simultaneously sliding a second element of the second user interface across the top of the first element.
In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which when executed by a portable multifunction device with a touch screen display, cause the portable multifunction device to: display a first user interface; detect a gesture on the touch screen display to select a second user interface; and display, in response to detecting the gesture, an animation of a transition from display of the first user interface to display of the second user interface. The animation comprises sliding a first element of the second user interface onto the display from a first side of the display while simultaneously sliding a second element of the second user interface across the top of the first element.
In accordance with some embodiments, a portable multifunction device includes: a touch screen display; means for displaying a first user interface; means for detecting a gesture on the touch screen display to select a second user interface; and means for displaying, in response to detecting the gesture, an animation of a transition from display of the first user interface to display of the second user interface, the animation comprising sliding a first element of the second user interface onto the display from a first side of the display while simultaneously sliding a second element of the second user interface across the top of the first element.
In accordance with some embodiments, a computer-implemented method is performed at a portable multifunction device with a touch screen display. The computer-implemented method includes: displaying a first user interface; detecting a gesture on the touch screen display to select a second user interface; and, in response to detecting the gesture, displaying an animation of flipping the first user interface to reveal the second user interface.
In accordance with some embodiments, a graphical user interface on a portable multifunction device with a touch screen display includes first and second user interfaces. In response to detecting a gesture on the touch screen display to select the second user interface while the first user interface is displayed, an animation is displayed of flipping the first user interface to reveal the second user interface.
In accordance with some embodiments, a portable multifunction device includes: a touch screen display; one or more processors; memory; and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for: displaying a first user interface; detecting a gesture on the touch screen display to select a second user interface; and displaying an animation of flipping the first user interface to reveal the second user interface, in response to detecting the gesture.
In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which when executed by a portable multifunction device with a touch screen display, cause the portable multifunction device to: display a first user interface; detect a gesture on the touch screen display to select a second user interface; and display an animation of flipping the first user interface to reveal the second user interface, in response to detecting the gesture.
In accordance with some embodiments, a portable multifunction device includes: a touch screen display; means for displaying a first user interface; means for detecting a gesture on the touch screen display to select a second user interface; and means for displaying an animation of flipping the first user interface to reveal the second user interface, in response to detecting the gesture.
In accordance with some embodiments, a computer-implemented method is performed at a portable multifunction device with a touch screen display. The computer-implemented method includes: playing music with a music player application while the device is in a user-interface lock state; detecting contact with the touch screen display while the device is playing music in the user-interface lock state; moving an unlock image across the touch screen display in accordance with the contact, wherein the unlock image is a graphical, interactive user-interface object with which a user interacts in order to unlock the device; transitioning the device to the user-interface unlock state and displaying a user interface in the music player application if the detected contact corresponds to a predefined gesture; and maintaining the device in the user-interface lock state and continuing to play music with the music player application if the detected contact does not correspond to the predefined gesture.
In accordance with some embodiments, a graphical user interface on a portable multifunction device with a touch screen display includes an unlock image. The unlock image is a graphical, interactive user-interface object with which a user interacts in order to unlock the device. Music is played with a music player application while the device is in a user-interface lock state. Contact with the touch screen display is detected while the device is playing music in the user-interface lock state. The unlock image is moved across the touch screen display in accordance with the contact. The device is transitioned to the user-interface unlock state and a user interface in the music player application is displayed if the detected contact corresponds to a predefined gesture. The device is maintained in the user-interface lock state and music play is continued with the music player application if the detected contact does not correspond to the predefined gesture.
In accordance with some embodiments, a portable multifunction device includes: a touch screen display; one or more processors; memory; and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for: playing music with a music player application while the device is in a user-interface lock state; detecting contact with the touch screen display while the device is playing music in the user-interface lock state; moving an unlock image across the touch screen display in accordance with the contact, wherein the unlock image is a graphical, interactive user-interface object with which a user interacts in order to unlock the device; transitioning the device to the user-interface unlock state and displaying a user interface in the music player application if the detected contact corresponds to a predefined gesture; and maintaining the device in the user-interface lock state and continuing to play music with the music player application if the detected contact does not correspond to the predefined gesture.
In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which when executed by a portable multifunction device with a touch screen display, cause the portable multifunction device to: play music with a music player application while the device is in a user-interface lock state; detect contact with the touch screen display while the device is playing music in the user-interface lock state; move an unlock image across the touch screen display in accordance with the contact, wherein the unlock image is a graphical, interactive user-interface object with which a user interacts in order to unlock the device; transition the device to the user-interface unlock state and displaying a user interface in the music player application if the detected contact corresponds to a predefined gesture; and maintain the device in the user-interface lock state and continuing to play music with the music player application if the detected contact does not correspond to the predefined gesture.
In accordance with some embodiments, a portable multifunction device includes: a touch screen display; means for playing music with a music player application while the device is in a user-interface lock state; means for detecting contact with the touch screen display while the device is playing music in the user-interface lock state; means for moving an unlock image across the touch screen display in accordance with the contact, wherein the unlock image is a graphical, interactive user-interface object with which a user interacts in order to unlock the device; means for transitioning the device to the user-interface unlock state and displaying a user interface in the music player application if the detected contact corresponds to a predefined gesture; and means for maintaining the device in the user-interface lock state and continuing to play music with the music player application if the detected contact does not correspond to the predefined gesture.
Animated transitions in accordance with the disclosed embodiments allow a user to navigate within and between applications in a multifunction device in a simple, intuitive manner.
For a better understanding of the aforementioned embodiments of the invention as welt as additional embodiments thereof, 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.
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first gesture could be termed a second gesture, and, similarly, a second gesture could be termed a first gesture, without departing from the scope of the present invention.
The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the description of the invention 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 “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.
As used herein, the term “if” may be 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” may be 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 a portable multifunction device, 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.
The user interface may include a physical click wheel in addition to a touch screen or a virtual click wheel displayed on the touch screen. A click wheel is a user-interface device that may provide navigation commands based on an angular displacement of the wheel or a point of contact with the wheel by a user of the device. A click wheel may also be used to provide a user command corresponding to selection of one or more items, for example, when the user of the device presses down on at least a portion of the wheel or the center of the wheel. Alternatively, breaking contact with a click wheel image on a touch screen surface may indicate a user command corresponding to selection. For simplicity, in the discussion that follows, a portable multifunction device that includes a touch screen is used as an exemplary embodiment. It should be understood, however, that some of the user interfaces and associated processes may be applied to other devices, such as personal computers and laptop computers, which may include one or more other physical user-interface devices, such as a physical click wheel, a physical keyboard, a mouse and/or a joystick.
The device supports a variety of applications, such as one or more of the following: a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a blogging 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 may be executed on the device may use at least one common physical user-interface device, such as the touch screen. One or more functions of the touch screen as well as corresponding information displayed on the device may be 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 screen) of the device may support the variety of applications with user interfaces that are intuitive and transparent.
The user interfaces may include one or more soft keyboard embodiments. The soft keyboard embodiments may include standard (QWERTY) and/or non-standard configurations of symbols on the displayed icons of the keyboard, such as those described in U.S. patent application Ser. No. 11/459,606, “Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, and Ser. No. 11/459,615, “Touch Screen Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, the contents of which are hereby incorporated by reference in their entirety. The keyboard embodiments may include a reduced number of icons (or soft keys) relative to the number of keys in existing physical keyboards, such as that for a typewriter. This may make it easier for users to select one or more icons in the keyboard, and thus, one or more corresponding symbols. The keyboard embodiments may be adaptive. For example, displayed icons may be modified in accordance with user actions, such as selecting one or more icons and/or one or more corresponding symbols. One or more applications on the portable device may utilize common and/or different keyboard embodiments. Thus, the keyboard embodiment used may be tailored to at least some of the applications. In some embodiments, one or more keyboard embodiments may be tailored to a respective user. For example, one or more keyboard embodiments may be tailored to a respective user based on a word usage history (lexicography, slang, individual usage) of the respective user. Some of the keyboard embodiments may be adjusted to reduce a probability of a user error when selecting one or more icons, and thus one or more symbols, when using the soft keyboard embodiments.
Attention is now directed towards embodiments of the device.
It should be appreciated that the device 100 is only one example of a portable multifunction device 100, and that the device 100 may have more or fewer components than shown, may combine two or more components, or a may have a different configuration or arrangement of the components. The various components shown in
Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of the device 100, such as the CPU 120 and the peripherals interface 118, may be controlled by the memory controller 122.
The peripherals interface 118 couples the input and output peripherals of the device to the 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 the device 100 and to process data.
In some embodiments, the peripherals interface 118, the CPU 120, and the memory controller 122 may be implemented on a single chip, such as a chip 104. In some other embodiments, they may be implemented on separate chips.
The RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. The RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. The RF circuitry 108 may include 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. The RF circuitry 108 may communicate 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 wireless communication may use 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), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email (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), and/or 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.
The audio circuitry 110, the speaker 111, and the microphone 113 provide an audio interface between a user and the device 100. The audio circuitry 110 receives audio data from the peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal to human-audible sound waves. The audio circuitry 110 also receives electrical signals converted by the microphone 113 from sound waves. The audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to the peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or the RF circuitry 108 by the peripherals interface 118. In some embodiments, the audio circuitry 110 also includes a headset jack (e.g. 212,
The I/O subsystem 106 couples input/output peripherals on the device 100, such as the touch screen 112 and other input/control devices 116, to the peripherals interface 118. The I/O subsystem 106 may include a display controller 156 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 or control devices 116. The other input/control devices 116 may 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 may be coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
The touch-sensitive touch screen 112 provides an input interface and an output interface between the device and a user. The display controller 156 receives and/or sends electrical signals from/to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects, further details of which are described below.
A 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. The touch screen 112 and the 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 the touch screen 112 and converts 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 the touch screen. In an exemplary embodiment, a point of contact between a touch screen 112 and the user corresponds to a finger of the user.
The touch screen 112 may use LCD (liquid crystal display) technology, or LPD (light emitting polymer display) technology, although other display technologies may be used in other embodiments. The touch screen 112 and the display controller 156 may 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 a touch screen 112.
A touch-sensitive display in some embodiments of the touch screen 112 may be analogous to the multi-touch sensitive tablets 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, a touch screen 112 displays visual output from the portable device 100, whereas touch sensitive tablets do not provide visual output.
A touch-sensitive display in some embodiments of the touch screen 112 may be as 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 in their entirety herein.
The touch screen 112 may have a resolution in excess of 100 dpi. In an exemplary embodiment, the touch screen has a resolution of approximately 160 dpi. The user may make contact with the 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 are much 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, the device 100 may include 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 may be a touch-sensitive surface that is separate from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
In some embodiments, the device 100 may include a physical or virtual click wheel as an input control device 116. A user may navigate among and interact with one or more graphical objects (henceforth referred to as icons) displayed in the touch screen 112 by rotating the click wheel or by moving a point of contact with the click wheel (e.g., where the amount of movement of the point of contact is measured by its angular displacement with respect to a center point of the click wheel). The click wheel may also be used to select one or more of the displayed icons. For example, the user may press down on at least a portion of the click wheel or an associated button. User commands and navigation commands provided by the user via the click wheel may be processed by an input controller 160 as well as one or more of the modules and/or sets of instructions in memory 102. For a virtual click wheel, the click wheel and click wheel controller may be part of the touch screen 112 and the display controller 156, respectively. For a virtual click wheel, the click wheel may be either an opaque or semitransparent object that appears and disappears on the touch screen display in response to user interaction with the device. In some embodiments, a virtual click wheel is displayed on the touch screen of a portable multifunction device and operated by user contact with the touch screen.
The device 100 also includes a power system 162 for powering the various components. The power system 162 may include 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.
The device 100 may also include one or more optical sensors 164.
The device 100 may also include one or more proximity sensors 166.
The device 100 may also include one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 may include an operating system 126, a communication module (or set of instructions) 128, a contact/motion module (or set of instructions) 130, a graphics module (or set or instructions) 132, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and applications (or set of instructions) 136.
The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, 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.
The 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 the RF circuitry 108 and/or the external port 124. The 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 Computer, Inc.) devices.
The contact/motion module 130 may detect contact with the touch screen 112 (in conjunction with the display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). The contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred, determining if there is movement of the contact and tracking the movement across the touch screen 112, and determining if the contact has been broken (i.e., if the contact has ceased). Determining movement of the point of contact may include 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 may be applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, the contact/motion module 130 and the display controller 156 also detects contact on a touchpad. In some embodiments, the contact/motion module 130 and the controller 160 detects contact on a click wheel.
The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112, including components for changing the intensity 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. An animation in this context is a display of a sequence of images that gives the appearance of movement, and informs the user of an action that has been performed (such as expanding a user-selected web-page portion to fill a browser window). In this context, a respective animation that executes an action, or confirms an action by the user of the device, typically takes a predefined, finite amount of time, typically between 0.2 and 1.0 seconds, and generally less than two seconds.
The text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, blogging 142, browser 147, and any other application that needs text input).
The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone module 138 for use in location-based dialing, to camera module 143 and/or blogger 142 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
The applications 136 may include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that may be stored in memory 102 include other word processing applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the contacts module 137 may be used to manage an address book or contact list, 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 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 module 130, graphics module 132, and text input module 134, the telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in the address book 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 may use 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 module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, the videoconferencing module 139 may be used to initiate, conduct, and terminate a video conference between a user and one or more other participants.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the e-mail client module 140 may be used to create, send, receive, and manage e-mail. In conjunction with image management module 144, the e-mail 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 module 130, graphics module 132, and text input module 134, the instant messaging module 141 may be used 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 may include graphics, photos, audio files, video files and/or other attachments as are supported in a 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 module 130, graphics module 132, text input module 134, image management module 144, and browsing module 147, the blogging module 142 may be used to send text, still images, video, and/or other graphics to a blog (e.g., the user's blog).
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, the camera module 143 may be used 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 module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 may be used to arrange, modify 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 touch screen 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, and speaker 111, the video player module 145 may be used to display, present or otherwise play back videos (e.g., on the touch screen or on an external, connected display via external port 124).
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, the music player module 146 allows 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. In some embodiments, the device 100 may include the functionality of an MP3 player, such as an iPod (trademark of Apple Computer, Inc.).
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, the browser module 147 may be used to browse the Internet, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages. Embodiments of user interfaces and associated processes using browser module 147 are described further below.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail module 140, and browser module 147, the calendar module 148 may be used to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.).
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget modules 149 are mini-applications that may be 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). Embodiments of user interfaces and associated processes using widget modules 149 are described further below.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a web-clip widget). In some embodiments, a web-clip widget comprises a file containing an XML property list that includes a URL for the web page and data indicating the user-specified portion of the web page. In some embodiments, the data indicating the user-specified portion of the web page includes a reference point and a scale factor. In some embodiments, the data indicating the user-specified portion of the web page includes a set of coordinates within the web page or an identification of a structural element within the web page. Alternatively, in some embodiments a web-clip widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. Alternatively, in some embodiments a web-clip widget includes an XML (Extensible Markup Language) file and a JavaScript file.
In some embodiments a web-clip widget includes an image file (e.g., a png file) of an icon corresponding to the widget. In some embodiments, a web-clip widget corresponds to a folder containing the image file and a file that includes the URL for the web page and data indicating the user-specified portion of the web page. In some embodiments, a web-clip widget corresponds to a folder containing the image file and an executable script.
Embodiments of user interfaces and associated processes using widget creator module 150 are described further below.
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, the search module 151 may be used 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 conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the notes module 153 may be used to create and manage notes, to do lists, and the like.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, the map module 154 may be 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 conjunction with touch screen 112, display system controller 156, contact 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, the online video module 155 allows 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, the content of which is hereby incorporated by reference in its entirety.
Each of the above identified modules and applications correspond to a set of instructions for performing one or more functions described above. These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. For example, video player module 145 may be combined with music player module 146 into a single module (e.g., video and music player module 152,
In some embodiments, the device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen 112 and/or a touchpad. By using a touch screen and/or a touchpad as the primary input/control device for operation of the device 100, the number of physical input/control devices (such as push buttons, dials, and the like) on the device 100 may be reduced.
The predefined set of functions that may be performed exclusively through a touch screen and/or a touchpad include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main, home, or root menu from any user interface that may be displayed on the device 100. In such embodiments, the touchpad may be referred to as a “menu button.” In some other embodiments, the menu button may be a physical push button or other physical input/control device instead of a touchpad.
The device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, the menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI in touch screen 112.
In one embodiment, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, a Subscriber Identity Module (SIM) card slot 210, a head set jack 212, and a docking/charging external port 124. The push button 206 may be 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, the device 100 also may accept verbal input for activation or deactivation of some functions through the microphone 113.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on a portable multifunction device 100.
In some embodiments, the device detects contact with the touch-sensitive display (e.g., a user's finger making contact on or near the unlock image 302) while the device is in a user-interface lock state. The device moves the unlock image 302 in accordance with the contact. The device transitions to a user-interface unlock state if the detected contact corresponds to a predefined gesture, such as moving the unlock image across channel 306. Conversely, the device maintains the user-interface lock state if the detected contact does not correspond to the predefined gesture. This process saves battery power by ensuring that the device is not accidentally awakened. This process is easy for users to perform, in part because of the visual cue(s) provided on the touch screen.
As noted above, processes that use gestures on the touch screen to unlock the device are 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, and Ser. No. 11/322,550, “Indication Of Progress Towards Satisfaction Of A User Input Condition,” filed Dec. 23, 2005, which are hereby incorporated by reference in their entirety.
In some embodiments, UI 400A displays all of the available applications 136 on one screen so that there is no need to scroll through a list of applications (e.g., via a scroll bar). In some embodiments, as the number of applications increase, the icons corresponding to the applications may decrease in size so that all applications may be displayed on a single screen without scrolling. In some embodiments, having all applications on one screen and a menu button enables a user to access any desired application with at most two inputs, such as activating the menu button 204 and then activating the desired application (e.g., by a tap or other finger gesture on the icon corresponding to the application).
In some embodiments, UI 400A provides integrated access to both widget-based applications and non-widget-based applications. In some embodiments, all of the widgets, whether user-created or not, are displayed in UI 400A. In other embodiments, activating the icon for user-created widget 149-6 may lead to another UI that displays the user-created widgets or icons corresponding to the user-created widgets. For example, UI 400B (
In some embodiments, a user may rearrange the icons in UI 400A, UI 400B, or UI 400C, e.g., using processes described in U.S. patent application Ser. No. 11/459,602, “Portable Electronic Device With Interface Reconfiguration Mode,” filed Jul. 24, 2006, which is hereby incorporated by reference in its entirety. For example, a user may move application icons in and out of tray 408 using finger gestures.
In some embodiments, UI 400A includes a gauge (not shown) that displays an updated account usage metric for an account associated with usage of the device (e.g., a cellular phone account), as described in U.S. patent application Ser. No. 11/322,552, “Account Information Display For Portable Communication Device,” filed Dec. 23, 2005, which is hereby incorporated by reference in its entirety.
In some embodiments, user interface 3900A (
In some embodiments, in response to a predefined gesture by the user on a block 3914 (e.g., a single tap gesture or a double tap gesture), the block is enlarged and centered (or substantially centered) in the web page display. For example, in response to a single tap gesture 3923 on block 3914-5, the user-selected block 3914-5 may be enlarged and centered in the display, as shown in UI 3900C (
In some embodiments, the device analyzes the render tree of the web page 3912 to determine the blocks 3914 in the web page. In some embodiments, a block 3914 corresponds to a render node that is: replaced; a block; an inline block; or an inline table.
In some embodiments, in response to the same predefined gesture by the user on a block 3914 (e.g., a single tap gesture or a double tap gesture) that is already enlarged and centered, the enlargement and/or centering is substantially or completely reversed. For example, in response to a single tap gesture 3929 on block 3914-5 (
In some embodiments, in response to a predefined gesture (e.g., a single tap gesture or a double tap gesture) by the user on a block 3914 that is already enlarged but not centered, the block is centered (or substantially centered) in the web page display. For example, in response to a single tap gesture 3927 on block 3914-4 (
In some embodiments, in response to a multi-touch (3931 and 3933) de-pinching gesture by the user (
In some embodiments, in response to a substantially vertical upward (or downward) swipe gesture by the user, the web page (or, more generally, other electronic documents) may scroll one-dimensionally upward (or downward) in the vertical direction. For example, in response to an upward swipe gesture 3937 by the user that is within a predetermined angle (e.g., 27°) of being perfectly vertical, the web page may scroll one-dimensionally upward in the vertical direction.
Conversely, in some embodiments, in response to a swipe gesture that is not within a predetermined angle (e.g., 27°) of being perfectly vertical, the web page may scroll two-dimensionally (i.e., with simultaneous movement in both the vertical and horizontal directions). For example, in response to an upward or diagonal swipe gesture 3939 by the user that is not within a predetermined angle (e.g., 27°) of being perfectly vertical, the web page may scroll two-dimensionally along the direction of the swipe 3939.
In some embodiments, in response to a multi-touch (3941 and 3943) rotation gesture by the user, the web page may be rotated exactly 90° (UI 3900D,
Thus, in response to imprecise gestures by the user, precise movements of graphics occur. The device behaves in the manner desired by the user despite inaccurate input by the user. Also, note that the gestures described for UI 3900C, which has a portrait view, are also applicable to UIs with a landscape view (e.g., UI 3900D,
In some embodiments, in response to a tap or other predefined user gesture on URL entry box 3908 (UI 3900A,
Thus, the same entry box 3926 may be used for inputting both search terms and URLs. In some embodiments, whether or not clear icon 3928 is displayed depends on the context.
UI 3900G (
In response to detecting a gesture on the touch screen display, a displayed window in the application is moved off the display and a hidden window is moved onto the display. For example, in response to detecting a tap gesture 3949 on the left side of the screen, the window with web page 3912-2 is moved partially or fully off-screen to the right, the window with web page 3912-3 is moved completely off-screen, partially hidden window with web page 3912-1 is moved to the center of the display, and another completely hidden window (not shown in
Conversely, in response to detecting a tap gesture 3953 on the right side of the screen, the window with web page 3912-2 is moved partially or fully off-screen to the left, the window with web page 3912-1 is moved completely off-screen, partially hidden window with web page 3912-3 is moved to the center of the display, and another completely hidden window (not shown in
In some embodiments, in response to a tap or other predefined gesture on a delete icon 3934 (e.g., 3934-2 or 3934-3), the corresponding window 3912 is deleted. In some embodiments, in response to a tap or other predefined gesture on Done icon 3938, the window in the center of the display (e.g., 3912-2) is enlarged to fill the screen.
A user may create a web-clip widget in accordance with some embodiments. Activation of the user-created web-clip widget displays a previously specified area in a web page (having a specified URL) at a specified display size or scale factor. In some embodiments, the area in the web page is specified by scaling and/or translating the display of the web page. For example, a specified area in the web page is enlarged and centered. The specified area may be displayed in a browser application (e.g., the browser 147) or other application. For example, activation of the web-clip widget may display a particular block that is of interest to the user within the web page; furthermore, the block may be enlarged. Activation of the web-clip widget thus enables the user to view the particular block of interest without having to enlarge and center the web page area that is of interest each time the user visits the web page. In some embodiments, after activation of the web-clip widget, the user may manipulate the display to view other portions of the web page by scaling and/or translating the display. Alternatively, in some embodiments, the user may not be permitted to manipulate the display.
Web-clip widgets provide more functionality than mere bookmarks: activation of a bookmark only displays a specified web page, while activation of a web-clip widget displays a specified area of a web page at a specified display size or scale factor in accordance with some embodiments. Similarly, a web-clip widget is distinguishable from a hyperlink. To view a web page or portion thereof specified by a hyperlink, the user must activate the browser application, navigate to a web page containing the hyperlink, activate the hyperlink, and then potentially scroll and/or scale the resulting web page. In contrast, to view an area of a web page specified by a web-clip widget, the user merely activates the widget.
In some embodiments, the web-clip widget corresponds to a block or other structural element of the web page. As described in U.S. patent application Ser. No. 11/620,492, “Selecting and Manipulating Web Content,” filed on Jan. 5, 2007, which application is incorporated by reference herein in its entirety, structural elements that are displayed in a web page may be identified during the web-clip widget creation process. In some embodiments, if the dimensions of a selected structural element change after creation of a web-clip widget, the area that is displayed upon activation of the web-clip widget is changed accordingly.
In some embodiments, a web-clip widget comprises a URL for the web page and data (e.g., metadata) indicating the user-specified portion of the web page. For example, in some embodiments the web-clip widget comprises a file containing an XML property list that includes the URL and the data indicating the user-specified portion of the web page. In some embodiments, the data indicating the user-specified portion of the web page includes a reference point (e.g., a corner point or center point for the widget) and a scale factor. In some embodiments, the data indicating the user-specified portion of the web page includes a set of coordinates within the web page (e.g., a user-defined rectangle) or an identification of a structural element within the web page. The application for viewing the web-clip widget (e.g., the browser 147) is configured to process the data indicating the user-specified portion of the web page and to display the corresponding portion.
In some embodiments a web-clip widget comprises an executable script. In some embodiments, the widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
To the extent that any application incorporated by reference herein includes a definition of web-clip widgets that contradicts the definition in the preceding five paragraphs, the definition in the preceding five paragraphs is to be considered controlling for purposes of interpreting the specification and claims of the present application.
Referring to
As a result of activating the options icon 3920, a user interface such as UI 3900F (
In some embodiments, in response to user activation of the “create web-clip widget” icon 3973 (
In some embodiments, as a result of activating the “create web-clip widget” icon 3973, a web-clip widget corresponding to the centered and/or enlarged area of the web page will be created and assigned a name without any further actions by a user. In some embodiments, instead of displaying a user interface such as UI 3900H (
An icon corresponding to the newly created widget may be created and displayed on a menu in a UI such as UI 400A or UI 4008 (
For example, as described above, a user viewing web page 3912 (
In some embodiments, instead of or in addition to performing a tap gesture 3923 (
In some embodiments, instead of first defining the area of the web page to be associated with the web-clip widget and then activating the options icon 3920 (e.g.,
In some embodiments, in response to the user activating the “create web-clip widget” icon 3973 (
In some embodiments, in response to the user activating the “create web-clip widget” icon 3973 (
In some embodiments, creating and displaying an icon corresponding to the newly created web-clip widget includes displaying an animation, as illustrated in
In some embodiments, instead of displaying an animation, the icon corresponding to the newly created web-clip widget is simply displayed in a first available vacancy in a menu of icons or in another available vacancy in the menu, or is appended to the menu.
Activation of the icon corresponding to the newly created web-clip widget 149-6-7 (e.g., by a gesture 606 (
UI 3900L (
UI 3900M (
In some embodiments, selection of a web page or portion thereof for display is detected (702). For example, one or more finger gestures are detected on the touch screen display to select the web page or portion thereof. In some embodiments, the one or more finger gestures include one or more finger gestures to scale an area in the web page. In some embodiments, the one or more finger gestures include one or more finger gestures to center an area in the web page. Examples of finger gestures used to select, center, and/or scale an area in the web page include a tap gesture 3923 or 3925 to center and enlarge a block (
The web page or portion thereof is displayed (704) on the touch screen display. In the example of
An activation of an options icon (e.g., icon 3920) is detected (706). In some embodiments, detecting activation of the options icon includes detecting a finger gesture (e.g., a tap gesture) on the options icon.
In response to detecting activation of the options icon, a plurality of icons (e.g., 3972,
An activation of the web-clip widget creation icon (e.g., 3973) is detected (710). In some embodiments, detecting activation of the web-clip widget creation icon includes detecting a finger gesture (e.g., a tap gesture) on the web-clip widget creation icon.
In response to detecting activation of the web-clip widget creation icon, a web-clip widget is created (712) corresponding to the displayed web page or portion thereof.
In some embodiments, the web-clip widget corresponds to a structural element of the web page, such as a particular block within the web page. In some embodiments, the web-clip widget corresponds to a user-specified rectangle in the web page.
In some embodiments, creating the web-clip widget includes (714) requesting a name for the web-clip widget, receiving the name, and storing the name. In some embodiments, requesting the name includes displaying a keyboard to receive input for the name. For example, in UI 3900H (
In some embodiments, creating the web-clip widget includes creating (716) an icon corresponding to the web-clip widget and displaying (718) the icon corresponding to the web-clip widget in a menu (e.g., UI 400A or 400B,
In some embodiments, the menu or list of icons comprises a menu or list of applications and widgets (e.g., UI 400A,
In some embodiments, the icon corresponding to the web-clip widget is displayed in a previously vacant area in the menu of icons. In some embodiments, the previously vacant area is a first available vacancy (e.g., 604-1,
In some embodiments, the web-clip widget is stored (720) as a bookmark in a browser application. In some embodiments, as described in U.S. patent application Ser. No. 11/469,838, “Presenting and Managing Clipped Content,” filed on Sep. 1, 2006, which application is incorporated by reference herein in its entirety, the web-clip widget is encoded as a URL associated with the bookmark.
In some embodiments, the web-clip widget is sent (722) to a web server for storage. In some embodiments, the web-clip widget stored on the web server is publicly accessible. Storing a user-created web-clip widget on a publicly accessible server allows the user to share the web-clip widget with other users.
In some embodiments, as illustrated in
In some embodiments, as illustrated in
In some embodiments, as illustrated in
In some embodiments, each operation of process 700 is performed by a portable multifunction device. In some embodiments, however, one or more operations of process 700 are performed by a server system in communication with a portable multifunction device via a network connection. The portable multifunction device may transmit data associated with the widget creation process to the server system and may receive information corresponding to the widget in return. For example, code (e.g., an HTML file, a CSS file, and/or a JavaScript file, in accordance with some embodiments, or an XML file and/or a JavaScript file, in accordance with some other embodiments) associated with the widget may be generated by the server system and then transmitted to the portable multifunction device. In general, operations in the widget creation process may be performed by the portable multifunction device, by the server system, or by a combination thereof.
Process 700 creates a widget that allows a user to view a specified area in a web page upon activation of the widget. The user thus is spared from having to enlarge and center the area of the web page that is of interest, such as a particular block of interest, each time the user visits the web page.
On a touch screen display of a portable multifunction device, an activation of an options icon (e.g., icon 3920,
An activation of a web-clip widget creation icon (e.g., icon 3973,
An area in a web page or portion thereof displayed on the touch screen display is selected (758). In some embodiments, selecting the area includes toggling (760) between frames that are successively overlaid on the displayed web page or portion thereof. For example, in UI 3900J (
In some embodiments, selecting the area includes detecting (762) one or more finger gestures to select an area in the web page or portion thereof for use by the web-clip widget. In some embodiments, selecting the area includes detecting (764) one or more finger gestures to scale an area in the web page or portion thereof for display by the web-clip widget. Examples of finger gestures used to select and/or scale an area in the web page or portion thereof include a single tap gesture 3923 or 3925 to center and enlarge a block (
A finishing gesture is detected (766). In some embodiments, a finger gesture (e.g., a tap gesture) on an icon (e.g., add widget icon 3954,
In some embodiments, creating the web-clip widget includes requesting a name for the web-clip widget, receiving the name, and storing the name, in accordance with operation 714 of process 700 (
In some embodiments, creating the web-clip widget includes creating an icon corresponding to the web-clip widget, in accordance with operation 716 of process 700. In some embodiments, the icon corresponding to the web-clip widget is displayed in a menu or list of icons, in accordance with operation 718 of process 700. En some embodiments, the menu or list of icons comprises a menu or list of applications and widgets on the multifunction device. In some embodiments, the menu or list of icons comprises a menu or list of widgets on the multifunction device. In some embodiments, the menu or list of icons comprises a menu or list of user-created widgets on the multifunction device.
In some embodiments, an activation of the icon corresponding to the web-clip widget is detected and the web-clip widget is displayed, in accordance with operations 724 and 726 (
In some embodiments, settings associated with the web-clip widget are edited, in accordance with operations 736-748 (
In some embodiments, the web-clip widget is stored as a bookmark in a browser application, in accordance with operation 720 of process 700 (
In some embodiments, the web-clip widget is sent to a web server for storage, in accordance with operation 722 of process 700. In some embodiments, the web-clip widget is sent to an external electronic device, in accordance with operations 728-734 (
In some embodiments, each operation of process 750 is performed by a portable multifunction device. In some embodiments, however, one or more operations of process 750 are performed by a server system in communication with a portable multifunction device via a network connection. The portable multifunction device may transmit data associated with the widget creation process to the server system and may receive information corresponding to the widget in return. For example, code (e.g., an HTML file, a CSS file, and/or a JavaScript file, in accordance with some embodiments, or an XML file and/or a JavaScript file, in accordance with some other embodiments) associated with the widget may be generated by the server system and then transmitted to the portable multifunction device. In general, operations in the widget creation process may be performed by the portable multifunction device, by the server system, or by a combination thereof.
Process 750, like process 700, creates a widget that allows a user to view a specified area in a web page upon activation of the widget, thus sparing the user from having to enlarge and center the area of the web page that is of interest each time the user visits the web page.
An activation of the icon is detected (782). For example, a finger gesture (e.g., a tap gesture) on the icon is detected.
In response to detecting the activation, a first portion of the two or more web-clip widgets is displayed (783). For example, UI 3900L (
A gesture is detected (784) on the touch screen display. In some embodiments, the gesture is a scrolling gesture. For example, a swipe gesture 3962 (
In response to detecting the gesture, a second portion of the two or more web-clip widgets is displayed (785). In some embodiments, in response to detecting the gesture, a displayed portion of the two or more web-clip widgets is scrolled from the first portion to the second portion. For example, in response to detecting an upward scroll gesture 3962 in UI 3900L (
In some embodiments, the gesture is a de-pinching gesture (e.g., gestures 3931 and 3933,
In some embodiments, the gesture is a finger tap on an area within the first portion (e.g., a finger tap analogous to gesture 3923,
An activation of the icon is detected (792). For example, a finger gesture (e.g., a tap gesture) on the icon is detected.
In response to detecting the activation of the icon, a plurality of icons corresponding to respective widgets in the plurality of widgets is displayed (793). In some embodiments, the plurality of icons is displayed in a menu, or in a list. For example, UI 400B (
An activation is detected (794) of a respective icon in the plurality of icons corresponding to a respective web-clip widget. In response to detecting the activation of the respective icon, the respective web-clip widget is displayed (795). For example, in response to detecting an activation of an icon corresponding to user-created widget 149-6-2 in UI 400B or UI 400C, user-created widget 149-6-2 is displayed in UI 3900M (
A gesture is detected (796) on the touch screen display. For example, a swipe gesture 3962 or 3963 (
In response to detecting the gesture, display of the respective web-clip widget is ceased and another web-clip widget is displayed (797). For example, in response to detecting a downward swipe 3962, a substantially horizontal left-to-right swipe 3963, a tap gesture 3967 at the left side of the displayed widget 149-6-2, or a tap gesture 3964 at the top of the displayed widget 149-6-2, a previous user-created widget 149-6-1 is displayed. In response to detecting an upward swipe 3962, a substantially horizontal right-to-left swipe 3963, a tap gesture 3965 at the right side of the displayed widget 149-6-2, or a tap gesture 3966 at the bottom of the displayed widget 149-6-2, a next user-created widget 149-6-3 is displayed.
Processes 780 and 790 thus provide user-friendly ways to view multiple specified areas in web pages without having to surf between successive web pages and without having to enlarge and center an area of interest in each web page.
In some embodiments, the icon is displayed (7004) in a menu or list of icons. In some embodiments, the menu or list of icons comprises a menu or list of applications and widgets (e.g., UI 400A,
In some embodiments, the user-specified area was previously selected by translating and scaling (7006) a displayed portion of the web page. In some embodiments, the user-specified area was previously selected by centering and enlarging (7008) a displayed portion of the web page. Examples of finger gestures used to translate, scale, center, and/or enlarge an area in the web page include a tap gesture 3923 or 3925 to center and enlarge a block (
An activation of the icon is detected (7010). In some embodiments, a linger gesture (e.g., a tap gesture 606,
In response to detecting activation of the icon, the user-specified area of the web page is displayed (7014). For example, in response to activation of the icon for the web-clip widget 149-6-7 (
The process 7000 allows a user to view a specified area in a web page upon activation of the corresponding icon. The user thus is spared from having to enlarge and center the area of the web page that is of interest, such as a particular block of interest, each time the user visits the web page.
The computing device displays (902) a first set of a first plurality of icons in a first area of the touch screen display (e.g., area 802,
In some embodiments, the first plurality of icons includes a plurality of application launch icons, wherein in response to detecting activation of an application launch icon in the plurality of application icons, an application that corresponds to the activated application icon is launched and displayed. In some embodiments, the applications include a default set of applications, third-party applications, and/or web-clip widget applications. The application launch icons are not for issuing commands or subcommands with an application. Rather, they are for launching applications. If an application is already launched, then activation of the corresponding application launch icon results in display of the application.
In some embodiments, the first plurality of icons includes one or more web-clip widget icons (e.g., widget icon 149-6,
The computing device displays (904) a second plurality of icons in a second area (e.g., tray 408,
In some embodiments, the second plurality of icons includes a plurality of application launch icons, wherein in response to detecting activation of an application icon in the plurality of application icons, an application that corresponds to the activated application icon is launched and/or displayed, as explained above. In some embodiments, the applications include a default set of applications, third-party applications, and/or web-clip widget applications.
The computing device detects (906) a first finger gesture on the touch screen display in the first area. In some embodiments, the first finger gesture is a swipe gesture (e.g., swipe 808,
In response to detecting the first finger gesture on the touch screen display in the first area, the computing device replaces (908) display of the first set of the first plurality of icons with display of a second set of the first plurality of icons in the first area on the touch screen display while maintaining the display of the second plurality of icons in the second area on the touch screen display. For example, in response to swipe 808, UI 800A (
In some embodiments, replacing display of the first set of the first plurality of icons with display of a second set of the first plurality of icons in the first area on the touch screen display comprises an animation that moves the first set out of the first area and the second set into the first area.
In some embodiments, the plurality of sets of icons includes a number of sets of icons that are configured to be separately displayed as a sequence of sets of icons in the first area of the touch screen display. In some embodiments, the computing device displays two or more set-sequence-indicia icons (e.g., icons 804-1, 804-2, and 804-3 in
In some embodiments, the computing device detects (912) a second finger gesture on an icon in the second set of the first plurality of icons. In response to detecting the second finger gesture, the computing device displays (914) an application that corresponds to the icon in the second set upon which the second finger gesture was detected. For example, in response to a finger tap gesture 814 (
In some embodiments, the computing device detects (916) a third finger gesture on the touch screen display while the second set of the first plurality of icons are displayed. In response to detecting the third finger gesture, the computing device replaces (918) display of the second set of the first plurality of icons with display of a third set of the first plurality of icons in the first area on the touch screen display while maintaining the display of the second plurality of icons in the second area on the touch screen display. For example, in response to detecting swipe 812 (
In some embodiments, the computing device detects (920) a fourth finger gesture on an icon in the third set of the first plurality of icons. In response to detecting the fourth finger gesture, the computing device displays (922) an application that corresponds to the icon in the third set upon which the fourth finger gesture was detected. For example, in response to a finger tap gesture 816 (
In some embodiments, the first finger gesture is a swipe gesture in a first direction and the computing device detects (924) a second finger swipe gesture on the touch screen display in a direction that is opposite (or substantially opposite) the first direction. In response to detecting the second finger swipe gesture, the computing device replaces (926) display of the first set of the first plurality of icons with a display of information, other than a set in the plurality of sets of icons, customized to a user of the device. In some embodiments, the customized information includes: local time, location, weather, stocks, calendar entries, and/or recent messages for the user. For example, in response to detecting finger swipe gesture 810 (
In some embodiments, the first finger gesture is a swipe gesture (e.g., swipe 808,
In some embodiments, while the image 1004 expands, icons in the first user interface 1000A appear to slide off of the touch screen 112 via respective corners, as illustrated in
In some embodiments, while the image 1004 shrinks, icons in the first user interface 1000A appear to slide onto the touch screen 112 from respective corners For example, in UI 1000G (
As shown in
In some embodiments, the name 504 associated with an instant message conversation is determined by finding an entry in the user's contact list 137 that contains the phone number used by the instant message conversation. If no such entry is found, then just the phone number is displayed (e.g., 504-3). In some embodiments, if the other person sends messages from two or more different phone numbers, the messages may appear in the same conversation including the person's name if all the phone numbers used are found in the same entry (i.e., the entry for the other person) in the user's contact list 137. In some embodiments, the conversation includes messages sent from phone numbers and/or email addresses associated with the other person. In some embodiments, the messages sent by the other person include a first message sent from a first address associated with the other person and a second message sent from a second address associated with the other person that is different from the first address. In some embodiments, the first address is a telephone number and the second address is an email address. In some embodiments, the first and second addresses are two distinct telephone numbers. In some embodiments, the first and second addresses are two distinct email addresses.
In some other embodiments, if the other person sends messages from two or more different phone numbers, the messages may appear in different conversations corresponding to different numbers. The phone numbers or other identifiers are displayed next to the person's name to distinguish these conversations from each other.
In some embodiments, the name field of an instant message conversation includes names or other identifiers of multiple parties that participate in the conversation as message recipients and/or senders. If there is no room for displaying all the names, a selected subset of names is displayed with a symbol like “ . . . ” at the end, indicating that there are more parties in the conversation. By default, a message by the user of the portable electronic device is sent to all the parties of the conversation. For simplicity, the subsequent embodiments of IM conversations described here involve only two parties, the user and another person. But one skilled in the art will appreciate that the methodologies described in the present invention are also applicable to an IM conversation involving more than two parties.
Automatically binning the instant messages into “conversations” (instant messages exchanged between the user of the device and a respective person or phone number) makes it easier for the user to carry on and keep track of instant message exchanges with multiple parties.
As noted above, the portable device monitors user contact with the conversation list. When the user swipes his finger or a stylus on the touch screen in a substantially vertical direction, this user contact may be interpreted as a scrolling gesture. In some embodiments, the scrolling gesture is independent of the horizontal position of the user contact with the touch screen display. In some embodiments, the scrolling gesture is substantially independent of the horizontal position of the user contact with the touch screen display (e.g., one or more side regions of the touch screen display may be reserved for other functions, such as functions corresponding to icons, soft keys or application navigation functions, and not available for the scroll gesture). The portable electronic device, accordingly, scrolls the conversation list and displays a different portion of the conversation list.
The conversation list moves in a direction consistent with the scrolling gesture 516. If the scrolling gesture is downward (or upward), the conversation list also moves downward (or upward). Scrolling the conversation list downward will typically scroll the list to earlier entries in the list, until the first entry is reached (e.g., Jane Doe 504-1). But if the user does not have too many IM conversations, the portable electronic device may display the entire conversation list and the scrolling gesture has no effect.
If the user taps on the edit icon 512 using his finger or stylus, the portable electronic device replaces the conversation list UI with a new UI that allows the user to edit the conversations (not shown). Similarly, if the user taps on the message creation icon 514, the portable electronic device replaces the conversation list UI with a new UI that allows the user to create a new instant message and therefore a new conversation (not shown).
If the user selects a particular conversation in the list (e.g., by a tap gesture 518 on the row listing the conversation, or by a gesture on a corresponding selection icon 510), the portable electronic device interprets the gesture as indicating that the user intends to check the messages associated with the user selected conversation. Accordingly, the portable electronic device replaces the conversation list UI 1100A (
In some embodiments, the portable electronic device replaces the conversation list UI 1100A (
In some embodiments, a header including a title (e.g., “Jane Doc” 504-1, corresponding to a name of a party in the instant message conversation) appears to slide onto the screen, as shown in
In some embodiments, user interface 1100E (
As shown in
In some embodiments, the device highlights certain portions of incoming and outgoing messages using, e.g., underlines, distinct font sizes or styles, and/or colors. Typically, the highlighted portions are deemed to have special connotations such as phone numbers, URLs, stock tickers, or contacts' names. These highlighted message portions may be user-selectable. For example, a user finger gesture on the highlighted portion “apple.com” of the message 604-2 causes the activation of the browser 147, which then brings up the home page of the website www.apple.com. Similarly, a user finger gesture on a telephone number activates the phone 138 and initiates a call to the telephone number.
In some embodiments, a vertically downward scrolling gesture scrolls the conversation downward, thereby showing older messages in the conversation. In some embodiments, a vertically upward scrolling gesture scrolls the conversation upward, thereby showing newer, more recent messages in the conversation. In some embodiments, as noted above, the last message in the conversation (e.g., 606-2) is displayed in the list of instant message conversations 500 (e.g., 506-1,
In some embodiments, in response to detecting activation of the instant messages icon 602 (e.g., detecting a gesture 1106,
In the UI 1200E, if a gesture 1224 is detected on the icon 1202, a reverse animation is displayed illustrating a transition back to UI 1200A. If a gesture 1226 is detected on a thumbnail 1210-11, an animation (not shown) is displayed of a transition to UI 1200F (
In response to detecting a gesture 5284 (
In response to detecting a gesture 1310 on the selection icon 1312 (
A second plurality of application launch icons is displayed (1604) in a second area (e.g., tray 408,
In response to detecting a first finger gesture (e.g., swipe 808,
In response to detecting activation of any respective application launch icon in the plurality of application launch icons, a first animation is displayed (1608) of a transition from display of application launch icons to display of an application that corresponds to the activated application launch icon. For example, in response to detecting gesture 1002 on the icon for the stocks application 149-2, an animation is displayed as illustrated in
In some embodiments, the first animation expands (1610) the image of the application from a point on the display screen. In some embodiments, the point is at or near the center of the touch screen display.
In some embodiments, the first animation further comprises fading out at least some of the application launch icons. In some embodiments, fading out at least some of the application launch icons comprises fading out at least some of the application launch icons with an ease-out transition.
In some embodiments, the first animation slides (1612) respective application launch icons off of the touch screen display via respective corners of the touch screen display, as illustrated in
In some embodiments, sliding respective application launch icons off of the touch screen display via respective corners of the touch screen display comprises fading out at least some the respective applications launch icons as the respective application launch icons slide towards respective corners of the touch screen display. In some embodiments, fading out at least some of the application launch icons occurs via an ease-out transition. For example, the four application launch icons closest to the center of area 802 (i.e., icons 149-2, 154, 149-3, and 153,
In some embodiments, a finishing gesture is detected (1614). In some embodiments, the finishing gesture is a gesture (e.g., 1006,
In some embodiments, in response to detecting the finishing gesture, a second animation is displayed (1616) of a transition from display of the application to display of application launch icons. For example, in response to detecting gesture 1006 on the home button 204, an animation is displayed as illustrated in
In some embodiments, the second animation shrinks (1618) the image of the application to a point on the display screen. In some embodiments, the point is at or near the center of the touch screen display.
In some embodiments, the second animation further comprises fading in at least some of the application launch icons. In some embodiments, fading in at least some of the application launch icons comprises fading in at least some of the application launch icons with an case-in transition.
In some embodiments, the second animation slides (1620) respective application launch icons onto the touch screen display from respective corners of the touch screen display, as illustrated in
In some embodiments, sliding respective application launch icons onto the touch screen display from respective corners of the touch screen display comprises fading in at least some the respective applications launch icons as the respective application launch icons slide from respective corners of the touch screen display. In some embodiments, fading in at least some of the application launch icons occurs via an ease-in transition. For example, the four application launch icons that end up closest to the center of area 802 (i.e., icons 149-2, 154, 149-3, and 153,
Activation of any respective application launch icon is detected (1626). In some embodiments, a finger gesture (e.g., a tap gesture 1002,
In response to detecting the activation, a first animation is displayed (1630) of a transition from display of the home menu to display of an application that corresponds to the activated application launch icon. For example, in response to detecting gesture 1002 on the icon for the stocks application 149-2, an animation is displayed as illustrated in
In some embodiments, the first animation further comprises fading out at least some of the application launch icons in the home menu. In some embodiments, fading out at least some of the application launch icons comprises fading out at least some of the application launch icons with an case-out transition.
In some embodiments, the first animation slides (1632) respective application launch icons off of the touch screen display via respective corners of the touch screen display, as illustrated in
In some embodiments, sliding respective application launch icons off of the touch screen display via respective corners of the touch screen display comprises fading out at least some the respective applications launch icons as the respective application launch icons slide towards respective corners of the touch screen display. In some embodiments, fading out at least some of the application launch icons occurs via an ease-out transition. For example, the four application launch icons closest to the center of area 802 (i.e., icons 149-2, 154, 149-3, and 153,
In some embodiments, a finishing gesture is detected (1634). In some embodiments, the finishing gesture (e.g., 1006,
In some embodiments, in response to detecting the finishing gesture, a second animation is displayed (1640) of a transition from display of the application to display of the home menu. For example, in response to detecting gesture 1006 on the home button 204, an animation is displayed as illustrated in
In some embodiments, the second animation further comprises fading in at least some of the application launch icons in the home menu. In some embodiments, fading in at least some of the application launch icons comprises fading in at least some of the application launch icons with an ease-in transition.
In some embodiments, the second animation slides (1642) respective application launch icons onto the touch screen display from respective corners of the touch screen display, as illustrated in
In some embodiments, sliding respective application launch icons onto the touch screen display from respective corners of the touch screen display comprises fading in at least some the respective applications launch icons as the respective application launch icons slide from respective corners of the touch screen display. In some embodiments, fading in at least some of the application launch icons occurs via an ease-in transition. For example, the four application launch icons that end up closest to the center of area 802 (i.e., icons 149-2, 154, 149-3, and 153,
A gesture (e.g., 518,
In response to detecting the gesture, a first animation is displayed (1654) of a transition from display of the first user interface to display of a second user interface corresponding to the selected item. The first animation slides the second user interface onto the touch screen display from a first side of the display. Examples of first animations are illustrated respectively in
In some embodiments, the first animation slides (1656) the first user interface off of a second side of the touch screen display. In some embodiments, the second side is opposite (1658) to the first side.
In some embodiments, the first animation slides (1660) a header including the title (e.g., name 504-1,
In some embodiments, a finishing gesture (e.g., 1106,
In some embodiments, in response to detecting the finishing gesture, a second animation is displayed (1666) of a transition from display of the second user interface to display of the first user interface. The second animation slides the first user interface onto the touch screen display. Examples of second animations are illustrated respectively in
In some embodiments, the second animation slides (1668) the first user interface onto the touch screen display from a second side opposite to the first side. In some embodiments, the second animation slides the second user interface off of the touch screen display via the first side. In some embodiments, the second animation slides the first user interface onto the touch screen display from the first side.
A gesture to select a second user interface (e.g., UI 1500E,
In response to detecting the gesture, an animation is displayed (1678) of a transition from display of the first user interface to display of the second user interface. The animation slides a first element (e.g., the block of numeric soft keys 1504,
In some embodiments, the animation slides the first element onto the display from the bottom of the display while simultaneously sliding (1680) the second element across the top of the first element from a side of the display. The second element (e.g., the block of user input fields 1502-1 through 1502-4) appears to rise while sliding.
A gesture to select a second user interface (e.g., gesture 1306,
In response to detecting the gesture, an animation is displayed (1690) of flipping the first user interface to reveal the second user interface. For example,
In some embodiments, the animation slides (1692) an element of the second user interface onto the touch screen display from a side or corner of the display.
In some embodiments, UIs 1700A-1700E (
The user interfaces in
The device plays (1802) music with a music player application (e.g., music player 146,
In some embodiments, prior to detecting contact with the touch screen display 112 while the device is playing music in the user-interface lock state, the device detects (1804) activation of a physical button on the portable multifunction device (e.g., home button 204 or push button 206). In response to detecting activation of the physical button, the device turns on the touch screen display; displays information on the touch screen display that is associated with the music playing on the music player application (e.g., title 1706, artist 1712, album 1714, and/or cover art 1708 corresponding to the album for the music playing on the music player application); and displays an unlock image 302 (1806) (e.g.,
The device detects (1808) contact with the touch screen display 112 while the device is playing music in the user-interface lock state.
The device moves (1810) the unlock image 302 across the touch screen display in accordance with the contact. In some embodiments, the unlock image is moved (1812) along a predefined displayed path on the touch screen display in accordance with the contact (e.g., across channel 306, as shown in
The device transitions (1814) to the user-interface unlock state and displays a user interface in the music player application if the detected contact corresponds to a predefined gesture (e.g., UI 1700E,
In some embodiments, the user interface in the music player application includes information that is associated with the music playing on the music player application (e.g., content title 1706, cover art 1708, artist 1712, and/or album title 1714,
In some embodiments, transitioning the device to the user-interface unlock state and displaying a user interface in the music player application includes: maintaining display of at least some of the information on the touch screen display that is associated with the music playing on the music player application (e.g., cover art 1708,
In some embodiments, transitioning the device to the user-interface unlock state and displaying a user interface in the music player application includes: maintaining display of at least some of the information on the touch screen display that is associated with the music playing on the music player application (e.g., cover art 1708,
The device is maintained in the user-interface lock state and continues to play music with the music player application if the detected contact does not correspond to the predefined gesture (1824).
In some embodiments, the device detects (1826) a finger gesture on one of the music player controls. In response to detecting the finger gesture on one of the music player controls, the device performs (I 828) a corresponding control function in the music player application.
A graphical user interface on a portable multifunction device with a touch screen display includes an unlock image 302. The unlock image is a graphical, interactive user-interface object with which a user interacts in order to unlock the device. Music is played with a music player application 146 while the device is in a user-interface lock state. Contact with the touch screen display is detected while the device is playing music in the user-interface lock state. The unlock image 302 is moved across the touch screen display in accordance with the contact. The device is transitioned to the user-interface unlock state and a user interface (e.g., UI 1700E,
Processes 1600, 1622, 1644, 1670, 1682, and 1800 help a user to navigate between user interfaces in a multifunction device in a simple, intuitive manner.
In some embodiments, the aforementioned processes for transitioning between user interfaces are enabled when one or more proximity sensors and/or a proximity determination module or a set of proximity determination instructions of the device determine that the portable electronic device is not currently being held up against (or in very close proximity to) the user's ear or face.
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 invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated.
This application is a continuation of U.S. patent application Ser. No. 16/987,255, “PORTABLE MULTIFUNCTION DEVICE WITH ANIMATED SLIDING USER INTERFACE TRANSITIONS,” filed Aug. 6, 2020, now Patent No. U.S. Pat. No. 11,507,255, which is a continuation of U.S. patent application Ser. No. 15/493,672, “Portable Multifunction Device with Animated User Interface Transitions,” filed Apr. 21, 2017, now Patent No. U.S. Pat. No. 10,761,691, which is a continuation of U.S. patent application Ser. No. 12/217,029, “Using Gestures to Slide Between User Interfaces,” filed Jun. 30, 2008, now Patent No. U.S. Pat. No. 9,772,751, which claims priority to U.S. Provisional Patent Application Nos.: 61/019,841, “Portable Multifunction Device with Animated User Interface Transitions,” filed Jan. 8, 2008; 61/010,208, “Portable Multifunction Device with Interface Recognition Mode,” filed Jan. 6, 2008; and 60/937,993, “Portable Multifunction Device,” filed Jun. 29, 2007. All of these applications are incorporated by reference herein in their entirety. This application is related to the following applications: (1) U.S. patent application Ser. No. 10/188,182, “Touch Pad For Handheld Device,” filed on Jul. 1, 2002; (2) U.S. patent application Ser. No. 10/722,948, “Touch Pad For Handheld Device,” filed on Nov. 25, 2003; (3) U.S. patent application Ser. No. 10/643,256, “Movable Touch Pad With Added Functionality,” filed on Aug. 18, 2003; (4) U.S. patent application Ser. No. 10/654,108, “Ambidextrous Mouse,” filed on Sep. 2, 2003; (5) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed on May 6, 2004; (6) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed on Jul. 30, 2004; (7) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices” filed on Jan. 18, 2005; (8) U.S. patent application Ser. No. 11/057,050, “Display Actuator,” filed on Feb. 11, 2005; (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006; (10) U.S. patent application Ser. No. 11/850,011, “Web Clip Widgets on a Portable Multifunction Device,” filed Sep. 4, 2007; (11) U.S. patent application Ser. No. 11/969,912, “Web-Clip Widgets on a Portable Multifunction Device,” filed Jan. 6, 2008; (12) U.S. patent application Ser. No. 11/459,602, “Portable Electronic Device with Interface Reconfiguration Mode,” filed Jul. 24, 2006; and (13) U.S. patent application Ser. No. 12/101,832, “Touch Screen Device, Method, and Graphical User Interface for Determining Commands by Applying Heuristics,” filed Apr. 11, 2008. All of these applications are incorporated by reference herein in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5051736 | Bennett et al. | Sep 1991 | A |
| 5146556 | Hullot et al. | Sep 1992 | A |
| 5196838 | Meier et al. | Mar 1993 | A |
| 5359712 | Cohen et al. | Oct 1994 | A |
| 5463725 | Henckel | Oct 1995 | A |
| 5491778 | Gordon et al. | Feb 1996 | A |
| 5598524 | Johnston et al. | Jan 1997 | A |
| 5610653 | Abecassis | Mar 1997 | A |
| 5612719 | Beernink et al. | Mar 1997 | A |
| 5621878 | Owens et al. | Apr 1997 | A |
| 5642490 | Morgan et al. | Jun 1997 | A |
| 5644739 | Moursund | Jul 1997 | A |
| 5657049 | Ludolph et al. | Aug 1997 | A |
| 5659694 | Bibayan et al. | Aug 1997 | A |
| 5706458 | Koppolu | Jan 1998 | A |
| 5724492 | Matthews et al. | Mar 1998 | A |
| 5726687 | Belfiore et al. | Mar 1998 | A |
| 5745096 | Ludolph et al. | Apr 1998 | A |
| 5745116 | Pisutha-Arnond | Apr 1998 | A |
| 5745710 | Clanton et al. | Apr 1998 | A |
| 5745910 | Piersol et al. | Apr 1998 | A |
| 5754179 | Hocker et al. | May 1998 | A |
| 5757371 | Oran et al. | May 1998 | A |
| 5760773 | Berman et al. | Jun 1998 | A |
| 5774119 | Alimpich et al. | Jun 1998 | A |
| 5796401 | Winer | Aug 1998 | A |
| 5812862 | Smith et al. | Sep 1998 | A |
| 5825349 | Meier et al. | Oct 1998 | A |
| 5825357 | Malamud et al. | Oct 1998 | A |
| 5870683 | Wells et al. | Feb 1999 | A |
| 5877765 | Dickman et al. | Mar 1999 | A |
| 5883626 | Glaser et al. | Mar 1999 | A |
| 5914716 | Rubin et al. | Jun 1999 | A |
| 5914717 | Kleewein et al. | Jun 1999 | A |
| 5923327 | Smith et al. | Jul 1999 | A |
| 5923908 | Schrock et al. | Jul 1999 | A |
| 5934707 | Johnson | Aug 1999 | A |
| 5963204 | Ikeda et al. | Oct 1999 | A |
| 5995106 | Naughton et al. | Nov 1999 | A |
| 5999173 | Ubillos | Dec 1999 | A |
| 6025842 | Filetto et al. | Feb 2000 | A |
| 6043818 | Nakano et al. | Mar 2000 | A |
| 6049336 | Liu et al. | Apr 2000 | A |
| 6069626 | Cline et al. | May 2000 | A |
| 6072486 | Sheldon et al. | Jun 2000 | A |
| 6073036 | Heikkinen et al. | Jun 2000 | A |
| 6111573 | Mccomb et al. | Aug 2000 | A |
| 6133914 | Rogers et al. | Oct 2000 | A |
| 6144863 | Charron | Nov 2000 | A |
| 6145083 | Shaffer et al. | Nov 2000 | A |
| 6177936 | Cragun | Jan 2001 | B1 |
| 6188407 | Smith et al. | Feb 2001 | B1 |
| 6195094 | Celebiler | Feb 2001 | B1 |
| 6199082 | Ferrel et al. | Mar 2001 | B1 |
| 6211858 | Moon et al. | Apr 2001 | B1 |
| 6229542 | Miller | May 2001 | B1 |
| 6243080 | Molne | Jun 2001 | B1 |
| 6256008 | Sparks et al. | Jul 2001 | B1 |
| 6262732 | Coleman et al. | Jul 2001 | B1 |
| 6262735 | Eteläperä | Jul 2001 | B1 |
| 6271841 | Tsujimoto | Aug 2001 | B1 |
| 6275935 | Barlow et al. | Aug 2001 | B1 |
| 6278454 | Krishnan | Aug 2001 | B1 |
| 6297795 | Kato et al. | Oct 2001 | B1 |
| 6297819 | Furst et al. | Oct 2001 | B1 |
| 6313853 | Lamontagne et al. | Nov 2001 | B1 |
| 6313855 | Shuping et al. | Nov 2001 | B1 |
| 6317140 | Livingston | Nov 2001 | B1 |
| 6323846 | Westerman et al. | Nov 2001 | B1 |
| 6326970 | Mott et al. | Dec 2001 | B1 |
| 6349410 | Lortz | Feb 2002 | B1 |
| 6353451 | Teibel et al. | Mar 2002 | B1 |
| 6359615 | Singh | Mar 2002 | B1 |
| 6377698 | Cumoli et al. | Apr 2002 | B1 |
| 6396520 | Ording | May 2002 | B1 |
| 6407757 | Ho et al. | Jun 2002 | B1 |
| 6411283 | Murphy | Jun 2002 | B1 |
| 6433801 | Moon et al. | Aug 2002 | B1 |
| 6466198 | Feinstein | Oct 2002 | B1 |
| 6466203 | Van Ee | Oct 2002 | B2 |
| 6469689 | Dow et al. | Oct 2002 | B1 |
| 6486895 | Robertson et al. | Nov 2002 | B1 |
| 6489975 | Patil et al. | Dec 2002 | B1 |
| 6496182 | Wong et al. | Dec 2002 | B1 |
| 6545669 | Kinawi et al. | Apr 2003 | B1 |
| 6570557 | Westerman et al. | May 2003 | B1 |
| 6570583 | Kung et al. | May 2003 | B1 |
| 6590568 | Astala et al. | Jul 2003 | B1 |
| 6597391 | Hudson | Jul 2003 | B2 |
| 6613100 | Miller | Sep 2003 | B2 |
| 6621768 | Keller et al. | Sep 2003 | B1 |
| 6628309 | Dodson et al. | Sep 2003 | B1 |
| 6628310 | Hiura et al. | Sep 2003 | B1 |
| 6629793 | Miller | Oct 2003 | B1 |
| 6636246 | Gallo et al. | Oct 2003 | B1 |
| 6639584 | Li | Oct 2003 | B1 |
| 6677932 | Westerman | Jan 2004 | B1 |
| 6683628 | Nakagawa et al. | Jan 2004 | B1 |
| 6700612 | Anderson et al. | Mar 2004 | B1 |
| 6710788 | Freach et al. | Mar 2004 | B1 |
| 6714222 | Björn et al. | Mar 2004 | B1 |
| 6727916 | Ballard | Apr 2004 | B1 |
| 6763388 | Tsimelzon | Jul 2004 | B1 |
| 6771250 | Oh | Aug 2004 | B1 |
| 6781575 | Hawkins et al. | Aug 2004 | B1 |
| 6820111 | Rubin et al. | Nov 2004 | B1 |
| 6909443 | Risden et al. | Jun 2005 | B1 |
| 6915294 | Singh et al. | Jul 2005 | B1 |
| 6915490 | Ewing | Jul 2005 | B1 |
| 6928461 | Tuli | Aug 2005 | B2 |
| 6931601 | Vronay et al. | Aug 2005 | B2 |
| 6934911 | Salmimaa et al. | Aug 2005 | B2 |
| 6940494 | Hoshino et al. | Sep 2005 | B2 |
| 6950949 | Gilchrist | Sep 2005 | B1 |
| 6956564 | Williams | Oct 2005 | B1 |
| 6957395 | Jobs et al. | Oct 2005 | B1 |
| 6970749 | Chinn et al. | Nov 2005 | B1 |
| 6976210 | Silva et al. | Dec 2005 | B1 |
| 6978127 | Bulthuis et al. | Dec 2005 | B1 |
| 6987991 | Nelson | Jan 2006 | B2 |
| 6990452 | Ostermann et al. | Jan 2006 | B1 |
| 7003495 | Burger et al. | Feb 2006 | B1 |
| 7007239 | Hawkins et al. | Feb 2006 | B1 |
| 7010755 | Anderson et al. | Mar 2006 | B2 |
| 7017118 | Carroll | Mar 2006 | B1 |
| 7030861 | Westerman et al. | Apr 2006 | B1 |
| 7054965 | Bell et al. | May 2006 | B2 |
| 7071943 | Adler | Jul 2006 | B2 |
| 7075512 | Fabre et al. | Jul 2006 | B1 |
| 7085590 | Kennedy et al. | Aug 2006 | B2 |
| 7093201 | Duarte | Aug 2006 | B2 |
| 7133859 | Wong | Nov 2006 | B1 |
| 7134095 | Smith et al. | Nov 2006 | B1 |
| 7149549 | Ortiz et al. | Dec 2006 | B1 |
| 7166791 | Robbin et al. | Jan 2007 | B2 |
| 7167731 | Nelson | Jan 2007 | B2 |
| 7171625 | Sacchi | Jan 2007 | B1 |
| 7221933 | Sauer et al. | May 2007 | B2 |
| 7231229 | Hawkins et al. | Jun 2007 | B1 |
| 7283845 | De Bast | Oct 2007 | B2 |
| 7310636 | Bodin et al. | Dec 2007 | B2 |
| 7346855 | Hellyar et al. | Mar 2008 | B2 |
| 7355593 | Hill et al. | Apr 2008 | B2 |
| 7360166 | Krzanowski | Apr 2008 | B1 |
| 7362331 | Ording | Apr 2008 | B2 |
| 7403910 | Hastings et al. | Jul 2008 | B1 |
| 7432928 | Shaw et al. | Oct 2008 | B2 |
| 7434177 | Ording et al. | Oct 2008 | B1 |
| 7437005 | Drucker et al. | Oct 2008 | B2 |
| 7461353 | Rohrabaugh et al. | Dec 2008 | B2 |
| 7480870 | Anzures et al. | Jan 2009 | B2 |
| 7487467 | Kawahara et al. | Feb 2009 | B1 |
| 7490295 | Chaudhri et al. | Feb 2009 | B2 |
| 7493573 | Wagner | Feb 2009 | B2 |
| 7506268 | Jennings et al. | Mar 2009 | B2 |
| 7509588 | Van Os et al. | Mar 2009 | B2 |
| 7512898 | Jennings et al. | Mar 2009 | B2 |
| 7526738 | Ording et al. | Apr 2009 | B2 |
| 7546548 | Chew et al. | Jun 2009 | B2 |
| 7546554 | Chiu et al. | Jun 2009 | B2 |
| 7561874 | Wang et al. | Jul 2009 | B2 |
| 7587671 | Saft et al. | Sep 2009 | B2 |
| 7587683 | Ito et al. | Sep 2009 | B2 |
| 7603105 | Bocking et al. | Oct 2009 | B2 |
| 7614008 | Ording | Nov 2009 | B2 |
| 7620894 | Kahn | Nov 2009 | B1 |
| 7624357 | De Bast | Nov 2009 | B2 |
| 7633076 | Huppi et al. | Dec 2009 | B2 |
| 7642934 | Scott | Jan 2010 | B2 |
| 7650137 | Jobs et al. | Jan 2010 | B2 |
| 7653883 | Hotelling et al. | Jan 2010 | B2 |
| 7657252 | Futami | Feb 2010 | B2 |
| 7657849 | Chaudhri et al. | Feb 2010 | B2 |
| 7663607 | Hotelling et al. | Feb 2010 | B2 |
| 7669135 | Cunningham et al. | Feb 2010 | B2 |
| 7683889 | Rimas Ribikauskas et al. | Mar 2010 | B2 |
| 7694231 | Kocienda et al. | Apr 2010 | B2 |
| 7719542 | Gough et al. | May 2010 | B1 |
| 7720893 | Boudreau et al. | May 2010 | B2 |
| 7730401 | Gillespie et al. | Jun 2010 | B2 |
| 7735021 | Padawer et al. | Jun 2010 | B2 |
| 7739271 | Cook et al. | Jun 2010 | B2 |
| 7739604 | Lyons et al. | Jun 2010 | B1 |
| 7747289 | Wang et al. | Jun 2010 | B2 |
| 7783583 | Sendhoff et al. | Aug 2010 | B2 |
| 7783990 | Amadio et al. | Aug 2010 | B2 |
| 7788583 | Amzallag et al. | Aug 2010 | B1 |
| 7805684 | Arvilommi | Sep 2010 | B2 |
| 7810038 | Matsa et al. | Oct 2010 | B2 |
| 7831926 | Rohrabaugh et al. | Nov 2010 | B2 |
| 7835729 | Hyon | Nov 2010 | B2 |
| 7840901 | Lacey et al. | Nov 2010 | B2 |
| 7844889 | Rohrabaugh et al. | Nov 2010 | B2 |
| 7844914 | Andre et al. | Nov 2010 | B2 |
| 7853972 | Brodersen et al. | Dec 2010 | B2 |
| 7856602 | Armstrong | Dec 2010 | B2 |
| 7917846 | Decker et al. | Mar 2011 | B2 |
| 7934152 | Krishnamurthy et al. | Apr 2011 | B2 |
| 7940250 | Forstall | May 2011 | B2 |
| 7957762 | Herz et al. | Jun 2011 | B2 |
| 7958457 | Brandenberg et al. | Jun 2011 | B1 |
| 7996789 | Louch et al. | Aug 2011 | B2 |
| 8006002 | Kalayjian et al. | Aug 2011 | B2 |
| 8099441 | Surasinghe | Jan 2012 | B2 |
| 8127239 | Louch et al. | Feb 2012 | B2 |
| 8205172 | Wong et al. | Jun 2012 | B2 |
| 8239784 | Hotelling et al. | Aug 2012 | B2 |
| 8279180 | Hotelling et al. | Oct 2012 | B2 |
| 8291344 | Chaudhri | Oct 2012 | B2 |
| 8306515 | Ryu et al. | Nov 2012 | B2 |
| 8365084 | Lin et al. | Jan 2013 | B1 |
| 8381135 | Hotelling et al. | Feb 2013 | B2 |
| 8446371 | Fyke et al. | May 2013 | B2 |
| 8479122 | Hotelling et al. | Jul 2013 | B2 |
| 8519964 | Platzer et al. | Aug 2013 | B2 |
| 8519972 | Forstall | Aug 2013 | B2 |
| 8558808 | Forstall | Oct 2013 | B2 |
| 8564544 | Jobs et al. | Oct 2013 | B2 |
| 8587613 | Wang | Nov 2013 | B2 |
| 8601370 | Chiang et al. | Dec 2013 | B2 |
| 8619038 | Chaudhri et al. | Dec 2013 | B2 |
| 8713469 | Park et al. | Apr 2014 | B2 |
| 8788954 | Lemay et al. | Jul 2014 | B2 |
| 8972890 | Ording | Mar 2015 | B2 |
| 9052925 | Chaudhri | Jun 2015 | B2 |
| 9052926 | Chaudhri | Jun 2015 | B2 |
| 9058186 | Chaudhri | Jun 2015 | B2 |
| 9244606 | Chaudhri et al. | Jan 2016 | B2 |
| 9256627 | Surasinghe | Feb 2016 | B2 |
| 9367232 | Platzer et al. | Jun 2016 | B2 |
| 9386432 | Chu et al. | Jul 2016 | B2 |
| 9619143 | Christie et al. | Apr 2017 | B2 |
| 9927970 | Ording et al. | Mar 2018 | B2 |
| 10007400 | Kocienda et al. | Jun 2018 | B2 |
| 10261668 | Kocienda et al. | Apr 2019 | B2 |
| 10852914 | Kocienda et al. | Dec 2020 | B2 |
| 11487404 | Kocienda et al. | Nov 2022 | B2 |
| 20010024195 | Hayakawa | Sep 2001 | A1 |
| 20010024212 | Ohnishi | Sep 2001 | A1 |
| 20020008691 | Hanajima et al. | Jan 2002 | A1 |
| 20020015024 | Westerman et al. | Feb 2002 | A1 |
| 20020015042 | Robotham et al. | Feb 2002 | A1 |
| 20020015064 | Robotham et al. | Feb 2002 | A1 |
| 20020018051 | Singh | Feb 2002 | A1 |
| 20020024540 | McCarthy | Feb 2002 | A1 |
| 20020038299 | Zernik et al. | Mar 2002 | A1 |
| 20020054090 | Silva et al. | May 2002 | A1 |
| 20020067376 | Martin et al. | Jun 2002 | A1 |
| 20020085037 | Leavitt et al. | Jul 2002 | A1 |
| 20020093531 | Barile | Jul 2002 | A1 |
| 20020104096 | Cramer et al. | Aug 2002 | A1 |
| 20020109721 | Konaka et al. | Aug 2002 | A1 |
| 20020113802 | Card et al. | Aug 2002 | A1 |
| 20020123368 | Yamadera et al. | Sep 2002 | A1 |
| 20020149561 | Fukumoto et al. | Oct 2002 | A1 |
| 20020152283 | Dutta et al. | Oct 2002 | A1 |
| 20020188948 | Florence | Dec 2002 | A1 |
| 20020191029 | Gillespie et al. | Dec 2002 | A1 |
| 20020196238 | Tsukada et al. | Dec 2002 | A1 |
| 20030007012 | Bate | Jan 2003 | A1 |
| 20030013483 | Ausems et al. | Jan 2003 | A1 |
| 20030014415 | Weiss et al. | Jan 2003 | A1 |
| 20030016241 | Burke | Jan 2003 | A1 |
| 20030025676 | Cappendijk | Feb 2003 | A1 |
| 20030030664 | Parry | Feb 2003 | A1 |
| 20030033331 | Sena et al. | Feb 2003 | A1 |
| 20030048295 | Lilleness et al. | Mar 2003 | A1 |
| 20030063072 | Brandenberg et al. | Apr 2003 | A1 |
| 20030063125 | Miyajima et al. | Apr 2003 | A1 |
| 20030081135 | Boll | May 2003 | A1 |
| 20030090572 | Belz et al. | May 2003 | A1 |
| 20030095135 | Kaasila et al. | May 2003 | A1 |
| 20030095155 | Johnson | May 2003 | A1 |
| 20030117427 | Haughawout et al. | Jun 2003 | A1 |
| 20030117440 | Hellyar et al. | Jun 2003 | A1 |
| 20030122787 | Zimmerman et al. | Jul 2003 | A1 |
| 20030132938 | Shibao | Jul 2003 | A1 |
| 20030164861 | Barbanson et al. | Sep 2003 | A1 |
| 20030169298 | Ording | Sep 2003 | A1 |
| 20030174172 | Conrad et al. | Sep 2003 | A1 |
| 20030179240 | Gest | Sep 2003 | A1 |
| 20030184552 | Chadha | Oct 2003 | A1 |
| 20030184587 | Ording et al. | Oct 2003 | A1 |
| 20030193524 | Bates et al. | Oct 2003 | A1 |
| 20030200289 | Kemp et al. | Oct 2003 | A1 |
| 20030206195 | Matsa et al. | Nov 2003 | A1 |
| 20030206197 | McInerney | Nov 2003 | A1 |
| 20030210280 | Baker et al. | Nov 2003 | A1 |
| 20030225811 | Ali et al. | Dec 2003 | A1 |
| 20040021643 | Hoshino et al. | Feb 2004 | A1 |
| 20040041849 | Mock et al. | Mar 2004 | A1 |
| 20040056839 | Yoshihara | Mar 2004 | A1 |
| 20040093582 | Segura | May 2004 | A1 |
| 20040103156 | Quillen et al. | May 2004 | A1 |
| 20040103371 | Chen et al. | May 2004 | A1 |
| 20040109013 | Goertz | Jun 2004 | A1 |
| 20040109025 | Hullot et al. | Jun 2004 | A1 |
| 20040117727 | Wada | Jun 2004 | A1 |
| 20040121823 | Noesgaard et al. | Jun 2004 | A1 |
| 20040125088 | Zimmerman et al. | Jul 2004 | A1 |
| 20040138569 | Grunwald et al. | Jul 2004 | A1 |
| 20040141011 | Smethers et al. | Jul 2004 | A1 |
| 20040143796 | Lerner et al. | Jul 2004 | A1 |
| 20040155909 | Wagner | Aug 2004 | A1 |
| 20040169674 | Linjama | Sep 2004 | A1 |
| 20040177148 | Tsimelzon, Jr. | Sep 2004 | A1 |
| 20040201595 | Manchester | Oct 2004 | A1 |
| 20040205492 | Newsome | Oct 2004 | A1 |
| 20040205496 | Dutta et al. | Oct 2004 | A1 |
| 20040215719 | Altshuler | Oct 2004 | A1 |
| 20040221006 | Gopalan et al. | Nov 2004 | A1 |
| 20040222975 | Nakano et al. | Nov 2004 | A1 |
| 20040268400 | Barde et al. | Dec 2004 | A1 |
| 20050005246 | Card et al. | Jan 2005 | A1 |
| 20050005248 | Rockey et al. | Jan 2005 | A1 |
| 20050010955 | Elia et al. | Jan 2005 | A1 |
| 20050020317 | Koyama | Jan 2005 | A1 |
| 20050024341 | Gillespie et al. | Feb 2005 | A1 |
| 20050026644 | Lien | Feb 2005 | A1 |
| 20050039134 | Wiggeshoff et al. | Feb 2005 | A1 |
| 20050044509 | Hunleth et al. | Feb 2005 | A1 |
| 20050057524 | Hill et al. | Mar 2005 | A1 |
| 20050057548 | Kim | Mar 2005 | A1 |
| 20050060653 | Fukase et al. | Mar 2005 | A1 |
| 20050060664 | Rogers | Mar 2005 | A1 |
| 20050060665 | Rekimoto | Mar 2005 | A1 |
| 20050066286 | Makela | Mar 2005 | A1 |
| 20050071364 | Xie et al. | Mar 2005 | A1 |
| 20050071736 | Schneider et al. | Mar 2005 | A1 |
| 20050071778 | Tokkonen | Mar 2005 | A1 |
| 20050078804 | Yomoda | Apr 2005 | A1 |
| 20050079896 | Kokko et al. | Apr 2005 | A1 |
| 20050088423 | Keely et al. | Apr 2005 | A1 |
| 20050091609 | Matthews et al. | Apr 2005 | A1 |
| 20050093826 | Huh | May 2005 | A1 |
| 20050097089 | Nielsen et al. | May 2005 | A1 |
| 20050108657 | Han | May 2005 | A1 |
| 20050114788 | Fabritius | May 2005 | A1 |
| 20050116026 | Burger et al. | Jun 2005 | A1 |
| 20050120142 | Hall | Jun 2005 | A1 |
| 20050134578 | Chambers et al. | Jun 2005 | A1 |
| 20050138569 | Baxter et al. | Jun 2005 | A1 |
| 20050154798 | Nurmi | Jul 2005 | A1 |
| 20050156873 | Walter et al. | Jul 2005 | A1 |
| 20050166232 | Lamkin et al. | Jul 2005 | A1 |
| 20050169527 | Longe et al. | Aug 2005 | A1 |
| 20050177783 | Agrawala et al. | Aug 2005 | A1 |
| 20050183017 | Cain | Aug 2005 | A1 |
| 20050190059 | Wehrenberg | Sep 2005 | A1 |
| 20050192924 | Drucker et al. | Sep 2005 | A1 |
| 20050204385 | Sull et al. | Sep 2005 | A1 |
| 20050210018 | Singh et al. | Sep 2005 | A1 |
| 20050210369 | Damm | Sep 2005 | A1 |
| 20050210403 | Satanek | Sep 2005 | A1 |
| 20050216913 | Gemmell et al. | Sep 2005 | A1 |
| 20050229102 | Watson et al. | Oct 2005 | A1 |
| 20050229118 | Chiu et al. | Oct 2005 | A1 |
| 20050250438 | Makipaa et al. | Nov 2005 | A1 |
| 20050251755 | Mullins et al. | Nov 2005 | A1 |
| 20050253817 | Rytivaara et al. | Nov 2005 | A1 |
| 20050259087 | Hoshino et al. | Nov 2005 | A1 |
| 20050262448 | Vronay et al. | Nov 2005 | A1 |
| 20050267869 | Horvitz et al. | Dec 2005 | A1 |
| 20050275636 | Dehlin et al. | Dec 2005 | A1 |
| 20050283734 | Santoro et al. | Dec 2005 | A1 |
| 20050285880 | Lai et al. | Dec 2005 | A1 |
| 20050289458 | Kylmanen | Dec 2005 | A1 |
| 20050289476 | Tokkonen | Dec 2005 | A1 |
| 20060005207 | Louch et al. | Jan 2006 | A1 |
| 20060007182 | Sato et al. | Jan 2006 | A1 |
| 20060017692 | Wehrenberg et al. | Jan 2006 | A1 |
| 20060025110 | Liu | Feb 2006 | A1 |
| 20060026170 | Kreitler et al. | Feb 2006 | A1 |
| 20060026521 | Hotelling et al. | Feb 2006 | A1 |
| 20060026536 | Hotelling et al. | Feb 2006 | A1 |
| 20060033724 | Chaudhri et al. | Feb 2006 | A1 |
| 20060033751 | Keely et al. | Feb 2006 | A1 |
| 20060033761 | Suen et al. | Feb 2006 | A1 |
| 20060035628 | Miller et al. | Feb 2006 | A1 |
| 20060036944 | Wilson | Feb 2006 | A1 |
| 20060048069 | Igeta | Mar 2006 | A1 |
| 20060051073 | Jung et al. | Mar 2006 | A1 |
| 20060053386 | Kuhl et al. | Mar 2006 | A1 |
| 20060053387 | Ording | Mar 2006 | A1 |
| 20060055662 | Rimas-Rbikauskas et al. | Mar 2006 | A1 |
| 20060055700 | Niles et al. | Mar 2006 | A1 |
| 20060064647 | Tapuska et al. | Mar 2006 | A1 |
| 20060075355 | Shiono et al. | Apr 2006 | A1 |
| 20060075396 | Surasinghe | Apr 2006 | A1 |
| 20060080616 | Vogel et al. | Apr 2006 | A1 |
| 20060085743 | Baudisch et al. | Apr 2006 | A1 |
| 20060085763 | Leavitt et al. | Apr 2006 | A1 |
| 20060097991 | Hotelling et al. | May 2006 | A1 |
| 20060101354 | Hashimoto et al. | May 2006 | A1 |
| 20060105814 | Monden et al. | May 2006 | A1 |
| 20060112335 | Hofmeister et al. | May 2006 | A1 |
| 20060116578 | Grunwald et al. | Jun 2006 | A1 |
| 20060117197 | Nurmi | Jun 2006 | A1 |
| 20060123360 | Anwar et al. | Jun 2006 | A1 |
| 20060125799 | Hillis et al. | Jun 2006 | A1 |
| 20060129647 | Kaghazian | Jun 2006 | A1 |
| 20060133664 | Hong | Jun 2006 | A1 |
| 20060139328 | Maki et al. | Jun 2006 | A1 |
| 20060143574 | Ito et al. | Jun 2006 | A1 |
| 20060146016 | Chan et al. | Jul 2006 | A1 |
| 20060146038 | Park et al. | Jul 2006 | A1 |
| 20060148526 | Kamiya et al. | Jul 2006 | A1 |
| 20060153531 | Kanegae et al. | Jul 2006 | A1 |
| 20060161871 | Hotelling et al. | Jul 2006 | A1 |
| 20060168510 | Bryar et al. | Jul 2006 | A1 |
| 20060174211 | Hoellerer et al. | Aug 2006 | A1 |
| 20060179415 | Cadiz et al. | Aug 2006 | A1 |
| 20060187212 | Park et al. | Aug 2006 | A1 |
| 20060190833 | Sangiovanni et al. | Aug 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060209035 | Jenkins et al. | Sep 2006 | A1 |
| 20060210958 | Rimas-Ribikauskas et al. | Sep 2006 | A1 |
| 20060224997 | Wong et al. | Oct 2006 | A1 |
| 20060236266 | Majava | Oct 2006 | A1 |
| 20060238625 | Sasaki et al. | Oct 2006 | A1 |
| 20060242145 | Krishnamurthy et al. | Oct 2006 | A1 |
| 20060242596 | Armstrong | Oct 2006 | A1 |
| 20060242604 | Wong et al. | Oct 2006 | A1 |
| 20060242607 | Hudson | Oct 2006 | A1 |
| 20060253771 | Baschy | Nov 2006 | A1 |
| 20060265643 | Saft et al. | Nov 2006 | A1 |
| 20060265653 | Paasonen et al. | Nov 2006 | A1 |
| 20060268100 | Karukka et al. | Nov 2006 | A1 |
| 20060271864 | Satterfield et al. | Nov 2006 | A1 |
| 20060271867 | Wang et al. | Nov 2006 | A1 |
| 20060271874 | Raiz et al. | Nov 2006 | A1 |
| 20060277460 | Forstall et al. | Dec 2006 | A1 |
| 20060277481 | Forstall et al. | Dec 2006 | A1 |
| 20060277588 | Harrington et al. | Dec 2006 | A1 |
| 20060278692 | Matsumoto et al. | Dec 2006 | A1 |
| 20060282786 | Shaw et al. | Dec 2006 | A1 |
| 20060282790 | Matthews et al. | Dec 2006 | A1 |
| 20060284852 | Hofmeister et al. | Dec 2006 | A1 |
| 20060290661 | Innanen et al. | Dec 2006 | A1 |
| 20070004451 | C. Anderson | Jan 2007 | A1 |
| 20070013665 | Vetelainen et al. | Jan 2007 | A1 |
| 20070022386 | Boss et al. | Jan 2007 | A1 |
| 20070024646 | Saarinen et al. | Feb 2007 | A1 |
| 20070028269 | Nezu et al. | Feb 2007 | A1 |
| 20070030362 | Ota et al. | Feb 2007 | A1 |
| 20070038612 | Sull et al. | Feb 2007 | A1 |
| 20070055947 | Ostojic et al. | Mar 2007 | A1 |
| 20070067272 | Flynt et al. | Mar 2007 | A1 |
| 20070067738 | Flynt et al. | Mar 2007 | A1 |
| 20070083827 | Scott et al. | Apr 2007 | A1 |
| 20070083911 | Madden et al. | Apr 2007 | A1 |
| 20070101292 | Kupka | May 2007 | A1 |
| 20070101297 | Forstall et al. | May 2007 | A1 |
| 20070106950 | Hutchinson et al. | May 2007 | A1 |
| 20070106952 | Matas et al. | May 2007 | A1 |
| 20070124677 | De Los Reyes et al. | May 2007 | A1 |
| 20070132789 | Ording et al. | Jun 2007 | A1 |
| 20070150810 | Katz et al. | Jun 2007 | A1 |
| 20070150830 | Ording et al. | Jun 2007 | A1 |
| 20070152980 | Kocienda et al. | Jul 2007 | A1 |
| 20070152984 | Ording et al. | Jul 2007 | A1 |
| 20070155434 | Jobs et al. | Jul 2007 | A1 |
| 20070156697 | Tsarkova | Jul 2007 | A1 |
| 20070157089 | Van Os et al. | Jul 2007 | A1 |
| 20070157228 | Bayer et al. | Jul 2007 | A1 |
| 20070177803 | Elias et al. | Aug 2007 | A1 |
| 20070177804 | Elias et al. | Aug 2007 | A1 |
| 20070180395 | Yamashita et al. | Aug 2007 | A1 |
| 20070189737 | Chaudhri et al. | Aug 2007 | A1 |
| 20070192741 | Yoritate et al. | Aug 2007 | A1 |
| 20070200713 | Weber et al. | Aug 2007 | A1 |
| 20070204218 | Weber et al. | Aug 2007 | A1 |
| 20070233695 | Boudreau et al. | Oct 2007 | A1 |
| 20070234235 | Scott | Oct 2007 | A1 |
| 20070240079 | Flynt et al. | Oct 2007 | A1 |
| 20070243862 | Coskun et al. | Oct 2007 | A1 |
| 20070245250 | Schechter et al. | Oct 2007 | A1 |
| 20070250768 | Funakami et al. | Oct 2007 | A1 |
| 20070254722 | Kim et al. | Nov 2007 | A1 |
| 20070260999 | Amadio et al. | Nov 2007 | A1 |
| 20070263176 | Nozaki et al. | Nov 2007 | A1 |
| 20070266011 | Rohrs et al. | Nov 2007 | A1 |
| 20070266342 | Chang et al. | Nov 2007 | A1 |
| 20070288860 | Ording et al. | Dec 2007 | A1 |
| 20070288862 | Ording | Dec 2007 | A1 |
| 20070288868 | Rhee et al. | Dec 2007 | A1 |
| 20070296333 | Kim et al. | Dec 2007 | A1 |
| 20070300160 | Ferrel et al. | Dec 2007 | A1 |
| 20080001924 | De Los Reyes et al. | Jan 2008 | A1 |
| 20080005703 | Radivojevic et al. | Jan 2008 | A1 |
| 20080034309 | Louch et al. | Feb 2008 | A1 |
| 20080042984 | Lim et al. | Feb 2008 | A1 |
| 20080059906 | Toki | Mar 2008 | A1 |
| 20080062137 | Brodersen et al. | Mar 2008 | A1 |
| 20080062141 | Chaudhri | Mar 2008 | A1 |
| 20080082930 | Omernick et al. | Apr 2008 | A1 |
| 20080104515 | Dumitru et al. | May 2008 | A1 |
| 20080122796 | Jobs et al. | May 2008 | A1 |
| 20080125180 | Hoffman et al. | May 2008 | A1 |
| 20080132252 | Altman et al. | Jun 2008 | A1 |
| 20080139176 | Kim | Jun 2008 | A1 |
| 20080155617 | Angiolillo et al. | Jun 2008 | A1 |
| 20080161045 | Vuorenmaa | Jul 2008 | A1 |
| 20080168075 | Kamiyabu | Jul 2008 | A1 |
| 20080168365 | Chaudhri | Jul 2008 | A1 |
| 20080168367 | Chaudhri et al. | Jul 2008 | A1 |
| 20080168369 | Tadman et al. | Jul 2008 | A1 |
| 20080168387 | Brownrigg | Jul 2008 | A1 |
| 20080168401 | Boule et al. | Jul 2008 | A1 |
| 20080168478 | Platzer et al. | Jul 2008 | A1 |
| 20080171555 | Oh et al. | Jul 2008 | A1 |
| 20080174562 | Kim | Jul 2008 | A1 |
| 20080182598 | Bowman | Jul 2008 | A1 |
| 20080182628 | Lee et al. | Jul 2008 | A1 |
| 20080184052 | Itoh et al. | Jul 2008 | A1 |
| 20080184112 | Chiang et al. | Jul 2008 | A1 |
| 20080189108 | Atar | Aug 2008 | A1 |
| 20080201452 | Athas et al. | Aug 2008 | A1 |
| 20080216017 | Kurtenbach et al. | Sep 2008 | A1 |
| 20080218523 | Zuverink | Sep 2008 | A1 |
| 20080225013 | Muylkens et al. | Sep 2008 | A1 |
| 20080231610 | Hotelling et al. | Sep 2008 | A1 |
| 20080259045 | Kim et al. | Oct 2008 | A1 |
| 20080259057 | Brons | Oct 2008 | A1 |
| 20080268882 | Moloney | Oct 2008 | A1 |
| 20080276280 | Nashida et al. | Nov 2008 | A1 |
| 20080297483 | Kim et al. | Dec 2008 | A1 |
| 20080300055 | Lutnick et al. | Dec 2008 | A1 |
| 20080300572 | Rankers et al. | Dec 2008 | A1 |
| 20080310602 | Bhupati | Dec 2008 | A1 |
| 20080313110 | Kreamer et al. | Dec 2008 | A1 |
| 20080313596 | Kreamer et al. | Dec 2008 | A1 |
| 20090002324 | Harbeson et al. | Jan 2009 | A1 |
| 20090002335 | Chaudhri | Jan 2009 | A1 |
| 20090006991 | Lindberg et al. | Jan 2009 | A1 |
| 20090007017 | Anzures et al. | Jan 2009 | A1 |
| 20090036108 | Cho | Feb 2009 | A1 |
| 20090058821 | Chaudhri et al. | Mar 2009 | A1 |
| 20090064055 | Chaudhri et al. | Mar 2009 | A1 |
| 20090070708 | Finkelstein | Mar 2009 | A1 |
| 20090128581 | Brid et al. | May 2009 | A1 |
| 20090138827 | Van Os et al. | May 2009 | A1 |
| 20090154082 | Nurmi et al. | Jun 2009 | A1 |
| 20090163193 | Fyke et al. | Jun 2009 | A1 |
| 20090164951 | Kumar | Jun 2009 | A1 |
| 20090178008 | Herz et al. | Jul 2009 | A1 |
| 20090199128 | Matthews et al. | Aug 2009 | A1 |
| 20090217187 | Kendall et al. | Aug 2009 | A1 |
| 20090222765 | Ekstrand | Sep 2009 | A1 |
| 20090249252 | Lundy et al. | Oct 2009 | A1 |
| 20090254799 | Unger | Oct 2009 | A1 |
| 20090262091 | Ikeda et al. | Oct 2009 | A1 |
| 20090288032 | Chang et al. | Nov 2009 | A1 |
| 20090293007 | Duarte et al. | Nov 2009 | A1 |
| 20090295753 | King et al. | Dec 2009 | A1 |
| 20100088628 | Flygh et al. | Apr 2010 | A1 |
| 20100095238 | Baudet | Apr 2010 | A1 |
| 20100105454 | Weber et al. | Apr 2010 | A1 |
| 20100169357 | Ingrassia et al. | Jul 2010 | A1 |
| 20100179991 | Lorch et al. | Jul 2010 | A1 |
| 20100283743 | Coddington | Nov 2010 | A1 |
| 20100299597 | Shin et al. | Nov 2010 | A1 |
| 20100315345 | Laitinen | Dec 2010 | A1 |
| 20100318709 | Bell et al. | Dec 2010 | A1 |
| 20110007009 | Ishihara et al. | Jan 2011 | A1 |
| 20110202872 | Park | Aug 2011 | A1 |
| 20110252357 | Chaudhri | Oct 2011 | A1 |
| 20110252373 | Chaudhri | Oct 2011 | A1 |
| 20110296333 | Bateman et al. | Dec 2011 | A1 |
| 20120081277 | De | Apr 2012 | A1 |
| 20120163574 | Gundotra et al. | Jun 2012 | A1 |
| 20130019193 | Rhee et al. | Jan 2013 | A1 |
| 20130069885 | Davidson | Mar 2013 | A1 |
| 20130097556 | Louch et al. | Apr 2013 | A1 |
| 20140068483 | Platzer et al. | Mar 2014 | A1 |
| 20140237360 | Chaudhri et al. | Aug 2014 | A1 |
| 20140340316 | Gu et al. | Nov 2014 | A1 |
| 20150012853 | Chaudhri et al. | Jan 2015 | A1 |
| 20150160832 | Walkin et al. | Jun 2015 | A1 |
| 20150242092 | Van et al. | Aug 2015 | A1 |
| 20160139747 | Kocienda et al. | May 2016 | A1 |
| 20160182805 | Emmett et al. | Jun 2016 | A1 |
| 20160253065 | Platzer et al. | Sep 2016 | A1 |
| 20170147198 | Herz et al. | May 2017 | A1 |
| 20170168651 | Ikeda et al. | Jun 2017 | A1 |
| 20170223176 | Anzures et al. | Aug 2017 | A1 |
| 20170374205 | Panda | Dec 2017 | A1 |
| 20180275839 | Kocienda et al. | Sep 2018 | A1 |
| 20190302971 | Kocienda et al. | Oct 2019 | A1 |
| 20200326834 | Lemmens et al. | Oct 2020 | A1 |
| 20200363919 | Anzures et al. | Nov 2020 | A1 |
| 20210255743 | Kocienda et al. | Aug 2021 | A1 |
| 20210278942 | Jung | Sep 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 2006338183 | Aug 2007 | AU |
| 2010304098 | Apr 2012 | AU |
| 2012202140 | May 2012 | AU |
| 2349649 | Jan 2002 | CA |
| 1257247 | Jun 2000 | CN |
| 1392977 | Jan 2003 | CN |
| 1464719 | Dec 2003 | CN |
| 1695105 | Nov 2005 | CN |
| 1773875 | May 2006 | CN |
| 1818843 | Aug 2006 | CN |
| 1940833 | Apr 2007 | CN |
| 101072410 | Nov 2007 | CN |
| 106471459 | Jun 2022 | CN |
| 102009058145 | Jun 2011 | DE |
| 163032 | Dec 1985 | EP |
| 322332 | Jun 1989 | EP |
| 404373 | Dec 1990 | EP |
| 476972 | Mar 1992 | EP |
| 626635 | Nov 1994 | EP |
| 651544 | May 1995 | EP |
| 689134 | Dec 1995 | EP |
| 0701220 | Mar 1996 | EP |
| 844553 | May 1998 | EP |
| 880090 | Nov 1998 | EP |
| 1049305 | Nov 2000 | EP |
| 1143334 | Oct 2001 | EP |
| 1231763 | Aug 2002 | EP |
| 1517228 | Mar 2005 | EP |
| 1632874 | Mar 2006 | EP |
| 1674976 | Jun 2006 | EP |
| 1744242 | Jan 2007 | EP |
| 1752880 | Feb 2007 | EP |
| 1964022 | Mar 2010 | EP |
| 2819675 | Jul 2002 | FR |
| 2301217 | Nov 1996 | GB |
| 2329813 | Mar 1999 | GB |
| 2407900 | May 2005 | GB |
| 5-225302 | Sep 1993 | JP |
| 6-51930 | Feb 1994 | JP |
| 6-208446 | Jul 1994 | JP |
| 7-225829 | Aug 1995 | JP |
| 8-221203 | Aug 1996 | JP |
| 9-73381 | Mar 1997 | JP |
| 9-97162 | Apr 1997 | JP |
| 9-101874 | Apr 1997 | JP |
| 9-138745 | May 1997 | JP |
| 9-258971 | Oct 1997 | JP |
| 9-297750 | Nov 1997 | JP |
| 10-40067 | Feb 1998 | JP |
| 10-96648 | Apr 1998 | JP |
| 10-214350 | Aug 1998 | JP |
| 11-143604 | May 1999 | JP |
| 11-508116 | Jul 1999 | JP |
| 11-242539 | Sep 1999 | JP |
| 11-327433 | Nov 1999 | JP |
| 2000-010702 | Jan 2000 | JP |
| 2000-105772 | Apr 2000 | JP |
| 2000-163031 | Jun 2000 | JP |
| 2000-163193 | Jun 2000 | JP |
| 2000-163444 | Jun 2000 | JP |
| 2000-181436 | Jun 2000 | JP |
| 2000-242390 | Sep 2000 | JP |
| 2001-92430 | Apr 2001 | JP |
| 2001-142604 | May 2001 | JP |
| 2001-175386 | Jun 2001 | JP |
| 2001-265481 | Sep 2001 | JP |
| 2001-312347 | Nov 2001 | JP |
| 2002-41197 | Feb 2002 | JP |
| 2002-41206 | Feb 2002 | JP |
| 2002-62966 | Feb 2002 | JP |
| 2002-99370 | Apr 2002 | JP |
| 2002-132412 | May 2002 | JP |
| 2002-149312 | May 2002 | JP |
| 2002-149616 | May 2002 | JP |
| 2002-189567 | Jul 2002 | JP |
| 2002-244635 | Aug 2002 | JP |
| 2002-525705 | Aug 2002 | JP |
| 2002-297514 | Oct 2002 | JP |
| 2002-312105 | Oct 2002 | JP |
| 2002-323850 | Nov 2002 | JP |
| 2003-66941 | Mar 2003 | JP |
| 2003-139546 | May 2003 | JP |
| 2003-162356 | Jun 2003 | JP |
| 2003-248538 | Sep 2003 | JP |
| 2003-256142 | Sep 2003 | JP |
| 2003-271310 | Sep 2003 | JP |
| 2003-536125 | Dec 2003 | JP |
| 2004-38260 | Feb 2004 | JP |
| 2004-38310 | Feb 2004 | JP |
| 2004-62645 | Feb 2004 | JP |
| 2004-70492 | Mar 2004 | JP |
| 2004-118478 | Apr 2004 | JP |
| 2004-132741 | Apr 2004 | JP |
| 2004-152075 | May 2004 | JP |
| 2004-159028 | Jun 2004 | JP |
| 2004-164242 | Jun 2004 | JP |
| 2004-206230 | Jul 2004 | JP |
| 2004-227393 | Aug 2004 | JP |
| 2004-288208 | Oct 2004 | JP |
| 2004-318505 | Nov 2004 | JP |
| 2004-341886 | Dec 2004 | JP |
| 2004-341892 | Dec 2004 | JP |
| 2004-343662 | Dec 2004 | JP |
| 2005-4396 | Jan 2005 | JP |
| 2005-18229 | Jan 2005 | JP |
| 2005-115896 | Apr 2005 | JP |
| 2005-515530 | May 2005 | JP |
| 2005-228088 | Aug 2005 | JP |
| 2005-234291 | Sep 2005 | JP |
| 2005-242669 | Sep 2005 | JP |
| 2005-267049 | Sep 2005 | JP |
| 2005-309933 | Nov 2005 | JP |
| 2005-321915 | Nov 2005 | JP |
| 2005-327064 | Nov 2005 | JP |
| 2005-352924 | Dec 2005 | JP |
| 2005-352943 | Dec 2005 | JP |
| 2006-18645 | Jan 2006 | JP |
| 2006-99733 | Apr 2006 | JP |
| 2006-155232 | Jun 2006 | JP |
| 2006-259376 | Sep 2006 | JP |
| 2007-132676 | May 2007 | JP |
| 2008-123553 | May 2008 | JP |
| 2008-518330 | May 2008 | JP |
| 2009-51921 | Mar 2009 | JP |
| 2009-522666 | Jun 2009 | JP |
| 2009-151821 | Jul 2009 | JP |
| 2010-538394 | Dec 2010 | JP |
| 2013-211055 | Oct 2013 | JP |
| 10-2002-0010863 | Feb 2002 | KR |
| 10-2006-0085850 | Jul 2006 | KR |
| 199928815 | Jun 1999 | WO |
| 199938149 | Jul 1999 | WO |
| 199954807 | Oct 1999 | WO |
| 200008757 | Feb 2000 | WO |
| 200016186 | Mar 2000 | WO |
| 200116690 | Mar 2001 | WO |
| 200157716 | Aug 2001 | WO |
| 200208881 | Jan 2002 | WO |
| 200213176 | Feb 2002 | WO |
| 200246903 | Jun 2002 | WO |
| 2002082418 | Oct 2002 | WO |
| 2002093542 | Nov 2002 | WO |
| 2003052626 | Jun 2003 | WO |
| 2003060622 | Jul 2003 | WO |
| 2003107168 | Dec 2003 | WO |
| 2004021166 | Mar 2004 | WO |
| 2004040481 | May 2004 | WO |
| 2004063862 | Jul 2004 | WO |
| 2005036416 | Apr 2005 | WO |
| 2005041020 | May 2005 | WO |
| 2005074268 | Aug 2005 | WO |
| 2005106684 | Nov 2005 | WO |
| 2006003591 | Jan 2006 | WO |
| 2006019639 | Feb 2006 | WO |
| 2006020304 | Feb 2006 | WO |
| 2006020305 | Feb 2006 | WO |
| 2006036069 | Apr 2006 | WO |
| 2006037545 | Apr 2006 | WO |
| 2006117438 | Nov 2006 | WO |
| 2007031816 | Mar 2007 | WO |
| 2007032972 | Mar 2007 | WO |
| 2007069835 | Jun 2007 | WO |
| 2007080559 | Jul 2007 | WO |
| 2007094894 | Aug 2007 | WO |
| 2008030874 | Mar 2008 | WO |
| 2008030976 | Mar 2008 | WO |
| 2008086303 | Jul 2008 | WO |
| 2009032638 | Mar 2009 | WO |
| 2009089222 | Jul 2009 | WO |
| 2011043575 | Apr 2011 | WO |
| Entry |
|---|
| Advisory Action received for U.S. Appl. No. 10/090,627, mailed on Aug. 19, 2014, 3 pages. |
| Advisory Action received for U.S. Appl. No. 10/090,627, mailed on Feb. 5, 2007, 3 pages. |
| Advisory Action received for U.S. Appl. No. 10/090,627, mailed on Jan. 29, 2009, 3 pages. |
| Advisory Action received for U.S. Appl. No. 10/090,627, mailed on Oct. 13, 2005, 3 pages. |
| Advisory Action received for U.S. Appl. No. 12/217,029, mailed on Dec. 12, 2014, 3 pages. |
| Advisory Action received for U.S. Appl. No. 12/217,029, mailed on Dec. 14, 2016, 3 pages. |
| Advisory Action received for U.S. Appl. No. 12/242,851, mailed on Nov. 15, 2013, 4 pages. |
| Advisory Action received for U.S. Appl. No. 13/077,524, mailed on May 16, 2014, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/261,112, mailed on Apr. 23, 2015, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/261,112, mailed on Nov. 30, 2017, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/710,125, mailed on Mar. 14, 2017, 3 pages. |
| Advisory Action received for U.S. Appl. No. 15/493,672, mailed on Aug. 12, 2019, 7 pages. |
| Advisory Action received for U.S. Appl. No. 16/987,255, mailed on May 3, 2022, 7 pages. |
| Agarawala et al., “Database Compendex/EI”, Engineering Information, Inc., Apr. 27, 2006, 1 page. |
| Agarawala et al., “Keepin' It Real: Pushing the Desktop Metaphor with Physics, Piles and the Pen”, CHI 2006 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Montreal, Quebec, Canada, Apr. 22-27, 2006, pp. 1283-1292. |
| Agarwal, Amit, “iTunesInlineVideo”, Digital Inspiration—The Tech Guide, available online at <http://labnol.blogspot.com/2006_09_17_labnol_archive.html>, 2006, 27 pages. |
| Ahmad et al., “Content-Based Image Retrieval on Mobile Devices”, Proceedings of SPIE-IS&T Electronic Imaging, vol. 5684, 2005, pp. 255-264. |
| Alam et al., “Web Document Manipulation for Small Screen Devices: A Review”, BCL Technologies Inc., Proceedings of the 2nd International Workshop on Web Document Analysis, 2003, pp. 33-36. |
| Alejandre, Suzanne, “Graphing Linear Equations”, Available at <http://mathforum.org/alejandre/palm/times.palm.html>, retrieved on Jun. 12, 2006, 3 pages. |
| Andrew's Widgets, “Developing Dashboard Widgets—A Brief Introduction to Building Widgets for Apple's Dashboard Environment”, Available online at <http://andrew.hedges.name/widgets/dev/>, Retrieved on Mar. 13, 2015, 6 pages. |
| Apparao et al., “Level 1 Document Object Model Specification (Version 1.0)”, W3C Working Draft, Available online at <http://www.w3.org/TR/WD-DOM/>, Jul. 20, 1998, 3 pages. |
| Apple Computer, Inc., “Dashboard Tutorial”, Apple Computer, Inc. © 2004, 2006, Jan. 10, 2006, 24 pages. |
| Apple Computer, Inc., “Welcome to Tiger”, available at <http://www.maths.dundee.ac.uk/software/Welcome_to_Mac_OS_X_v10.4_Tiger.pdf>, 2005, pp. 1-32. |
| Apple Iphone School, “Customize 1.19 Update for the iPhone”, 4:02 minutes video, available at <http://www.youtube.com/watch?v=5ogDzOM89oc>, uploaded on Dec. 8, 2007, 2 pages. |
| Apple Iphone School, “SummerBoard 3.0a9 for iPhone”, 4:50 minutes video, available at <http://www.youtube.com/watch?v=s_P_9mrZTKs>, uploaded on Oct. 21, 2007, 2 pages. |
| Apple, “iPhone User's Guide”, Available at <http://mesnotices.20minutes.fr/manuel-notice-mode-emploi/APPLE/IPHONE%2D%5FE#>, Retrieved on Mar. 27, 2008, Jun. 2007, 137 pages. |
| Apple, “Iphone User's Guide”, iPhone first generation, Available at: <http://pocketpccentral.net/iphone/products/1 g_iphone.htm>, Jun. 29, 2007, 124 pages. |
| apple.com, “Tiger Developer Overview Series—Developing Dashboard Widgets”, Available online at <http://developer.apple.com/macosx/dashboard.html>, Jun. 26, 2006, 9 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/378,990, mailed on Jun. 22, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/688,766, mailed on Feb. 1, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/688,766, mailed on Sep. 22, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/987,255, mailed on Nov. 29, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/107,321, mailed on Jun. 1, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/493,672, mailed on Jan. 31, 2020, 5 pages. |
| “Asus Eee News, Mods, and Hacks: Asus Eee PC Easy Mode Internet Tab Options Tour”, asuseeehacks.blogspot.com, Available online at <http://asuseeehacks.blogspot.com/2007/11/asus-eee-pc-user-interface-tour.html>, Nov. 10, 2007, 33 pages. |
| Autocomplete Plugin, Emesene Forum, available at: <http://emeseme.org/smf/index.olm?topic=1276.0>, Jun. 20, 2008, 5 pages. |
| Barsch, Bill, “3D Desktop! TouchScreen and XGL on Linux!”, 2:42 minutes video, available at <http://www.youtube.com/watch?v=Yx9FgLr90Tk>, uploaded on Aug. 15, 2006, 2 pages. |
| Baudisch et al., “Collapse-to-Zoom: Viewing Web Pages on Small Screen Devices by Interactively Removing Irrelevant Content”, Microsoft Research, Available at <http://www.patrickbaudisch.com/publications/2004-Baudisch-UIST04- CollapseToZoom.pdf>, Oct. 27, 2004, 4 pages. |
| Berka, “iFuntastic 3 Opens Up New iPhone Functionality”, ars technica, Availale at: <http://arstechnica.com/journals/apple.ars/2007/08/30/ifuntastic-3-opens-up-new-iphone-functionality>, Aug. 30, 2007, 2 pages. |
| BITSTREAM®, “ThunderHawk Pocket PC Edition for End Users”, Available at <http://www.bitstream.com/wireless/products/pocketpc/faq_using.html>, retrieved on Jun. 12, 2006, 2006, 4 pages. |
| Blickenstorfer, Conrad H. , “NeoNode N1 Can a Unique Interface Put this Compelling Smart Phone on the Map?”, available at <http://pencomputing.com/WinCE/neonode-n1-review.html>, retrieved on Sep. 1, 2014, 5 pages. |
| Board Opinion received for Chinese Patent Application No. 200780041309.3, mailed on Apr. 1, 2016, 16 pages. |
| Bos et al., “3 Conformance: Requirements and Recommendations”, Cascading Style Sheets, level 2 CSS2 Specification, W3C Recommendation, available at <http://www.w3.org/TR/CSS21/conform.html#doctree>, May 12, 1998, 6 pages. |
| Buyukkokten et al., “Power Browser: Efficient Web Browsing for PDAs”, Proceedings of the SIGCHI conference on Human Factors in Computing Systems, 2000, 8 pages. |
| Certificate of Examination received for Australian Patent Application No. 2011101190, mailed on Nov. 23, 2011, Nov. 23, 2011, 1 page. |
| Certification of Grant received for Australian Patent Application No. 2011101194, mailed on Mar. 2, 2012, Mar. 2, 2012, 2 pages. |
| Cerulean Studios, “Trillian Online User Manual”, available at <http://www.ceruleanstudios.com/support/manualphp?hchap=4&hsub=1&hsect=5>, 2006, 11 pages. |
| Cha, Bonnie, “HTC Touch Diamond (Sprint)”, CNET Reviews, available at <http://www.cnet.com/products/htc-touch/>, updated on Sep. 12, 2008, 8 pages. |
| Chang et al., “Animation: From Cartoons to the User Interface”, UIST '93 Proceedings of the 6th Annual ACM Symposium on User Interface Software and Technology, Nov. 1993, pp. 45-55. |
| Chartier, David, “iPhone 1.1.3 Video Brings the Proof”, ars TECHNICA, Available online at <http://arstechnica.com/journals/apple.are/2007/12/30/iphone-1-1-3-video-brings-the-proof>, Dec. 30, 2007, 3 pages. |
| Chen et al., “A Novel Navigation and Transmission Technique for Mobile Handheld Devices”, Technical Report CSE-2003-1, Department of Computer Science, University of California at Davis, 2003, 8 pages. |
| Chen et al., “Detecting Web Pages Structure for Adaptive Viewing on Small Form Factor Devices”, Proceedings of the 12th international conference on World Wide Web, 2003, 9 pages. |
| Chen et al., “Dress: A Slicing Tree Based Web Representation for Various Display Sizes”, Microsoft Research, Technical Report, Nov. 16, 2002, 9 pages. |
| Clifton, Marc, “Detect if Another Process is Running and Bring it to the Foreground”, Online Avialble at : https://www.codeproject.com/Articles/2976/Detect-if-another-process-is-running-andbring-it, Sep. 30, 2002, 6 pages. |
| CNET, “Bounding Box”, available at <http://www.cnet.com/Resources/Info/Glossary/Terms/boundingbox.html>, retrieved on Dec. 29, 2008, 1 page. |
| CNET, “Fujitsu LifeBook B6110D”, Reviews, Nov. 24, 2005, 2 pages. |
| CNET, “Video: Create Custom Widgets with Web Clip”, CNET News, Available at <http://news.cnet.com/1606-2-6103525.html>, Aug. 8, 2006, 3 pages. |
| cocoabuilder.com, “Single Instance of a Cocoa Application”, Available at: http://www.cocoabuilder.com/archive/cocoa/167892-single-instance-of-cocoa- application.html, Jul. 19, 2006, 4 pages. |
| Communication received for European Patent Application No. 08798713.7, mailed on Apr. 28, 2010, 2 pages. |
| Cooper, Alan, “The Inmates Are Running the Asylum”, Sams Publishing, Mar. 23, 1999, pp. 138-147. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/142,640, mailed on Feb. 5, 2020, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/378,990, mailed on Sep. 10, 2020, 5 pages. |
| Deanhill, “Run a Program or Switch to an Already Running Instance”, Available Online at <https://autohotkey.com/board/topic/7129-run-a-program-or-switch-to-an-already-running-instance/>, Feb. 1, 2006, 16 pages. |
| Dearman et al., “Rendezvousing with Location-Aware Devices: Enhancing Social Coordination”, Interacting with Computers, vol. 17, Issue 5, available at <http://www.dgp.toronto.edu/˜dearman/publications/dearman_IWC05.pdf>, Sep. 2005, pp. 542-566. |
| Decision of Board of Appeal received for European Patent Application No. 09170697.8 mailed on Oct. 24, 2016, 24 pages. |
| Decision on Acceptance received for Australian Patent Application No. 2017202587, mailed on Oct. 8, 2019, 19 pages. |
| Decision on Appeal received for U.S. Appl. No. 14/142,640, mailed on Oct. 7, 2019, 9 pages. |
| Decision on Appeal received for U.S. Appl. No. 14/710,125, mailed on Mar. 11, 2019, 7 pages. |
| Decision to Grant received for Chinese Patent Application No. 200780001140.9, mailed on Feb. 3, 2012, 4 pages. |
| Decision to Grant received for Chinese Patent Application No. 200880110709.X, mailed on Aug. 6, 2012, 2 pages. |
| Decision to Grant received for European Patent Application No. 09700333.9, mailed on Nov. 7, 2013, 2 pages. |
| Decision to Grant received for European Patent Application No. 12177813.8, mailed on Nov. 24, 2016, 3 pages. |
| Decision to Grant received for European Patent Application No. 12194312.0, mailed on Feb. 1, 2018, 2 pages. |
| Decision to Grant received for European Patent Application No. 12194315.3, mailed on Oct. 12, 2017, 2 pages. |
| Decision to Grant received for European Patent Application No. 13174706.5, mailed on Jul. 11, 2019, 2 pages. |
| Decision to Grant received for Japanese Patent Application No. 2010-524102, mailed on May 31, 2013, 3 pages. |
| Decision to Refusal received for European Patent Application No. 09171787.6, mailed on Dec. 14, 2011, 22 pages. |
| Decision to Refuse received for European Patent Application No. 09170697.8, mailed on Oct. 23, 2013, 12 pages. |
| Decision to Refuse received for European Patent Application No. 06846840.4, mailed on Mar. 4, 2010, 10 pages. |
| Decision to Refuse received for European Patent Application No. 07814689.1, mailed on May 11, 2012, 15 pages. |
| Decision to Refuse received for European Patent Application No. 09170697.8, mailed on Jul. 10, 2018, 31 pages. |
| Decision to Refuse received for European Patent Application No. 19190231.1, mailed on Jan. 14, 2020, 2 pages. |
| Delltech, “Windows XP: The Complete Reference: Working with Graphics”, http://web.archive.org/web/20050405151925/http:/delltech.150m.corn/XP/graphics/3.htm, Chapter 18, Apr. 5, 2005, 4 pages. |
| “Desktop Icon Toy-History”, Available online at <http://www.idesksoft.com/history.html>, retrieved on Jan. 2, 2010, 2 pages. |
| Dodge et al., “Microsoft Office Excel 2003 Office Manual”, Microsoft Press, vol. 1, Unable to Locate English Translation, Jul. 12, 2004, 5 pages. |
| Domshlak et al., “Preference-Based Configuration of Web Page Content”, Proceedings of the 17th Int'l Joint Conf. on Artificial Intelligence (IJCAI), Seattle, W A, Aug. 4-10, 2001, pp. 1451-1456. |
| Edwards, “iPhone 1.1.3 Firmware Feature Gallery”, Gear Live, Available at: <http://www.gearlive.com/news/article/q407-iphone-113-firmware-feature-gallery/>, Dec. 28, 2007, 7 pages. |
| Elo, “Touchscreen User Manual, Elo Projected Capacitance Driver Software Version 1.00 (Serial)”, Elo TouchSystems, Inc., Dec. 30, 2005, 37 pages. |
| Examiner's Answer for Appeal Brief received for U.S. Appl. No. 11/850,005, mailed on Apr. 10, 2018, 34 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/261,112, mailed on Oct. 29, 2019, 10 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/710,125, mailed on Jan. 26, 2018, 6 pages. |
| Examiner's Pre-review report received for Japanese Patent Application No. 2014-253365, mailed on Dec. 12, 2017, 7 pages. |
| Expansystv, “HTC Touch Dual Demonstration by eXpansys”, 5:26 minutes video, available at <http://www.youtube.com/watch?v=Tupk8MYLhMk>, uploaded on Oct. 1, 2007, 2 pages. |
| Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 09171787.6, Jan. 26, 2010, 6 pages. |
| Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 12169786.6, Jul. 11, 2012, 10 pages. |
| Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 13174706.5, mailed on Jan. 8, 2015, 8 pages. |
| Extended European Search Report received for European Patent Application No. 09170697.8, mailed on Apr. 28, 2010, 3 pages. |
| Extended European Search Report received for European Patent Application No. 12177813.8, mailed on Feb. 1, 2013, 6 pages. |
| Extended European Search Report received for European Patent Application No. 12189764.9, mailed on Jan. 4, 2013, 6 pages. |
| Extended European Search Report received for European Patent Application No. 12194312.0 mailed on Jan. 16, 2013, 7 pages. |
| Extended European Search Report received for European Patent Application No. 12194315.3, mailed on Jan. 16, 2013, 7 pages. |
| Extended European Search Report received for European Patent Application No. 17210062.0, mailed on Feb. 20, 2018, 12 pages. |
| Eyemodule Springboard Compatible, “Turn Your Handspring™ Visor™ Handheld into a Digital Camera”, User's Manual, 2000, 9 pages. |
| Fadhley, Mohd N., “LauncherX”, Online Available at <http://www.palmx.org/mambo/index2.php?option=com_content&task=view&id=65&1temid>, Nov. 21, 2002, 3 pages. |
| Farber, Dan, “Jobs: Today Apple is Going to Reinvent the Phone”, ZDNet, available at <http://www.zdnet.com/blog/btl/jobs-today-apple-is-going-to-reinvent-the-phone/4249>, Jan. 9, 2007, 3 pages. |
| Final Office Action received for U.S. Appl. No. 14/261,112, mailed on Mar. 3, 2016, 31 pages. |
| Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Dec. 1, 2010, 13 pages. |
| Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Feb. 16, 2012, 13 pages. |
| Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Jan. 13, 2014, 13 pages. |
| Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Jun. 15, 2005, 9 pages. |
| Final Office Action received for U.S. Appl. No. 10/090,627, mailed on May 14, 2012, 13 pages. |
| Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Oct. 7, 2008, 10 pages. |
| Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Oct. 19, 2006, 12 pages. |
| Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Sep. 25, 2007, 10 pages. |
| Final Office Action received for U.S. Appl. No. 11/620,647, mailed on Dec. 23, 2010, 21 pages. |
| Final Office Action received for U.S. Appl. No. 11/849,938, mailed on Jan. 30, 2013, 31 pages. |
| Final Office Action received for U.S. Appl. No. 11/849,938, mailed on May 27, 2011, 21 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,005, mailed on Jul. 8, 2011, 9 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,005, mailed on Jun. 6, 2019, 14 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,005, mailed on May 22, 2014, 13 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,005, mailed on Nov. 16, 2015, 13 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,005, mailed on Sep. 14, 2012, 9 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,008, mailed on Dec. 29, 2010, 14 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,010 mailed on Oct. 17, 2011, 11 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,010, mailed on Apr. 18, 2016, 16 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,010, mailed on Aug. 14, 2018, 21 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,010, mailed on Feb. 15, 2013, 12 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,010, mailed on May 8, 2014, 11 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,010, mailed on May 11, 2018, 24 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,011, mailed on Dec. 1, 2010, 15 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,638, mailed on Feb. 8, 2011, 14 pages. |
| Final Office Action received for U.S. Appl. No. 11/850,638, mailed on May 15, 2012, 16 pages. |
| Final Office Action received for U.S. Appl. No. 11/961,773, mailed on Nov. 2, 2011, 12 pages. |
| Final Office Action received for U.S. Appl. No. 11/961,773, mailed on Nov. 29, 2012, 15 pages. |
| Final Office Action received for U.S. Appl. No. 11/969,809, mailed on Jul. 14, 2011, 26 pages. |
| Final Office Action received for U.S. Appl. No. 11/969,912, mailed on Oct. 31, 2011, 11 pages. |
| Final Office Action received for U.S. Appl. No. 12/217,029, mailed on May 22, 2014, 12 pages. |
| Final Office Action received for U.S. Appl. No. 12/217,029, mailed on Oct. 5, 2012, 28 pages. |
| Final Office Action received for U.S. Appl. No. 12/242,851, mailed on Dec. 12, 2011,13 pages. |
| Final Office Action received for U.S. Appl. No. 12/242,851, mailed on Jul. 1, 2016, 90 pages. |
| Final Office Action received for U.S. Appl. No. 12/242,851, mailed on May 10, 2013, 20 pages. |
| Final Office Action received for U.S. Appl. No. 12/274,346, mailed on Mar. 14, 2012, 39 pages. |
| Final Office Action received for U.S. Appl. No. 12/364,470, mailed on May 5, 2010, 16 pages. |
| Final Office Action received for U.S. Appl. No. 12/364,470, mailed on Oct. 19, 2011, 20 pages. |
| Final Office Action received for U.S. Appl. No. 12/365,887, mailed on Feb. 29, 2012, 15 pages. |
| Final Office Action received for U.S. Appl. No. 13/077,524, mailed on Feb. 12, 2014, 13 pages. |
| Final Office Action received for U.S. Appl. No. 14/261,112, mailed on Aug. 10, 2017, 35 pages. |
| Final Office Action received for U.S. Appl. No. 14/261,112, mailed on Nov. 7, 2018, 34 pages. |
| Final Office Action received for U.S. Appl. No. 14/261,112, mailed on Oct. 9, 2014, 29 pages. |
| Final Office Action received for U.S. Appl. No. 14/710,125, mailed on Oct. 27, 2016, 13 pages. |
| Final Office Action received for U.S. Appl. No. 15/426,836, mailed on Mar. 29, 2019, 49 pages. |
| Final Office Action received for U.S. Appl. No. 15/493,672, mailed on May 31, 2019, 25 pages. |
| Final Office Action received for U.S. Appl. No. 16/688,766, mailed on Dec. 11, 2020, 23 pages. |
| Final Office Action received for U.S. Appl. No. 16/987,255, mailed on Jan. 19, 2022, 48 pages. |
| Final Office Action received for U.S. Appl. No. 14/142,640, mailed on Mar. 8, 2016, 35 pages. |
| Fingerworks Forums, “Is the Multitouch Lemur?”, Available at <http://64233.167.104/search?q=cache:sjVdtyFBvRMJ:forums.finger>, retrieved on Nov. 16, 2005, Dec. 24, 2004, 2 pages. |
| Fingerworks, Inc., “Installation and Operation Guide for the TouchStream and TouchStream LP”, available at <http://www.fingerworks.com>, 2002, pp. 1-25. |
| Fingerworks, Inc., “Quick Reference Guide for iGesture Products”, available at <http://www.fingerworks.com>, 1999-2002, 2 pages. |
| Fingerworks, Inc., “Quick Reference Guide for TouchStream ST/LP”, available at <http://www.fingerworks.com>, 2001-2003, 4 pages. |
| Fingerworks, Inc., “TouchStream LP Silver”, available at <http://www.fingerworks.com>, Apr. 27, 2005, 18 pages. |
| Fondantfancies, “Dash Clipping: Don't Wait for Mac OS X 10.5 Leopard”, fondantfancies.com, Available online at <http://www.fondantfancies.com/blog/3001239/>, retrieved on Sep. 3, 2009, 9 pages. |
| Forsberg et al., “Aperture Based Selection for Immersive Virtual Environments”, Proceedings of the ACM Symposium on User Interface Software and Technology, 1996, 2 pages. |
| Foxit, “Foxit Reader v. 1.3 Feature Description”, available at <http://www.foxitsoftware.com/pdf/reader 2/verhistory.htm>, 2008, 4 pages. |
| Gade, Lisa, “Sprint HTC Touch”, Smartphone Reviews by Mobile Tech Review, Available online at <http://www.mobiletechreview.com/phones/HTC-Touch.htm>, Nov. 2, 2007, 7 pages. |
| Gears, Leigh, “Orange SPV C600 Review”, Available at <http://www.coolsmartphone.com/article569.html>, retrieved on Apr. 14, 2006, 57 pages. |
| Getgreg, “Jeff Han's Multiple Touch Point Display, the Stuff Dreams are Made of”, Available at <http://www.theyshoulddothat.com/2006/08/jeff_hanns_multiple_touch_poin.html>, retrieved on Dec. 17, 2007, Aug. 16, 2006, 2 pages. |
| Grant for Invention Patent received in Chinese Patent Application No. 200680053441.1, Jan. 28, 2011, 1 page. |
| GSM Arena, “Neonode N2 User Interface”, 3:06 minutes video, available at <https://www.youtube.com/watch?v=MfDMHmIZRLc>, uploaded on Feb. 13, 2007, 2 pages. |
| Gsmarena Team, “HTC Touch Review: Smart to Touch the Spot”, available at <http://www.gsmarena.com/htc_touch-review-189.php>, Nov. 28, 2007, 18 pages. |
| Gsmarena Team, “HTC Touch review”, Online Available at: <twww.gsmarena.com/htc_touch-review-189p3.php>, Nov. 28, 2007, 5 pages. |
| Guan et al., “Zoom Selector: A Pen-based Interaction Technique for Small Target Selection”, Transactions of the Information Processing Society of Japan, vol. 45, No. 8, Aug. 2004, pp. 2087-2097. |
| Han Jeff, “Talks Jeff Han: Unveiling the Genius of Multi-touch Interface Design”, Ted Ideas Worth Spreading, available at <http://www.ted.com/index.php/talks/view/id/65> Retrieved on Dec. 17, 2007, Aug. 2006, 2 pages. |
| Hart Kim, “Rewriting the Web for Mobile Phones”, washingtonpost.com, available at <http://www.washingtonpost.com/wp-dyn/content/article/2006/07/25/AR2006072501517_pf.html>, Jul. 26, 2006, 2 pages. |
| Hesseldahl, Arik, “An App the Mac can Brag About”, Forbes.com, Available at <http://www.forbes.com/2003/12/15/cx_ah_1215tentech_print.html>, Dec. 15, 2003, 4 pages. |
| Higuchi, Tadahiro, “Try API!, Making a cool application with Visual Basic 6.0”, 1st edition, Japan, AI Publishing, AI Mook 221, Jul. 16, 1999, 23 pages. |
| Hinckley et al., “Input/Output Devices and Interaction Techniques”, CRC Press, Nov. 2004, pp. 1-79. |
| Holmquist, Larse, “The Zoom Browser Showing Simultaneous Detail and Overview in Large Documents”, Human IT, Available at: <http://www.hb.se/bhs/ith/3-98/leh.htm>, 1998, 12 pages. |
| Honeywell, “TH8000 Series Programmable Thermostats”, Retrieved from the Internet: URL:https://ia802507.us.archive.org/1/items/generalmanual_000075065/generalmanual_000075065.pdf, 2004, 44 pages. |
| Huang et al., “Effects of Visual Vibratory Perception by Cross-Modali Matching with Tactile Sensation”, Retrieved from the Internet:<URL: http://media.nuas.ac.jp/˜robin/Research/ADC99.html>, 1999, pp. 1-7. |
| ImageShack—Hosting, available at <http://img129.imageshack.us/mv.php?image=autocompleteemoticonprexw0.jpg>, Nov. 10, 2008, 1 page. |
| Infoworld Video, “Two Geeks and an iPhone: Part 3”, available at <http://web.archive.org/web/20080124065641/http:/www.infoworld.com/video/interviews/Mobile-Tech-Apple-iPhone/Two-Geeks-and-an-iPhone-Part-3/video_1966.html>, Dec. 18, 2007, 2 pages. |
| Intention to Grant received for Chinese Patent Application No. 200910173272.0, mailed on Oct. 23, 2012, 1 page. |
| Intention to Grant received for European Patent Application No. 09700333.9, mailed on Jun. 20, 2013, 7 pages. |
| Intention to Grant received for European Patent Application No. 12177813.8, mailed on Jul. 6, 2016, 8 pages. |
| Intention to Grant received for European Patent Application No. 12194312.0, mailed on Aug. 3, 2017, 8 pages. |
| Intention to Grant received for European Patent Application No. 12194315.3, mailed on May 31, 2017, 8 pages. |
| Intention to Grant received for European Patent Application No. 13174706.5, mailed on Apr. 30, 2019, 7 pages. |
| Intention to Grant received for European Patent Application No. 13174706.5, mailed on Nov. 22, 2018, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2006/062685, mailed on Jul. 1, 2008, 6 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2007/077639, issued on Mar. 10, 2009, 6 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2007/077643, issued on Mar. 10, 2009, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2008/050430, issued on Jul. 7, 2009, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2008/050431, issued on Jul. 7, 2009, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2008/074341, mailed on Mar. 9, 2010, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2008/074625, issued on Mar. 9, 2010, 6 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2009/030225, mailed on Jul. 15, 2010, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/077638, mailed on Feb. 19, 2008, 9 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/077639, mailed on Jul. 8, 2008, 7 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/077643, mailed on May 8, 2008, 9 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/077644, mailed on May 30, 2008, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/077773, mailed on Jan. 15, 2008, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/088879, mailed on Jun. 30, 2008, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/088893, mailed on Jul. 11, 2008, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2008/050430, mailed on Sep. 1, 2008, 13 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2008/050431, mailed on Jun. 17, 2008, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2008/074341, mailed on Nov. 27, 2009, 12 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2008/074625, mailed on Jan. 8, 2009, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2009/030225, mailed on Feb. 25, 2010, 15 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2007/077644, mailed on Jan. 23, 2008, 10 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2008/050430, mailed on Jun. 27, 2008, 7 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2009/030225, mailed on Nov. 16, 2009, 4 pages. |
| Iphone Dev Wiki, “IPhone Customization”, Available at: <http://iphone.fivefony.net/wiki/index.php/Iphone_Customization>, mailed on Dec. 13, 2007, 7 pages. |
| Iphone Hacks, “iPhone Firmware 1.1.1: Multi-Page SpringBoard Hack”, Available at: <http://www.iphonehacks.com/2007/10/springboardhack.html>, Oct. 9, 2007, 4 pages. |
| Iphone Hacks, “SummerBoard for iPhone OS v1.1.1: iPhone Hack Enables Scrolling of iPhone's Home Screen”, Available at: <http://www.iphonehacks.com/2007/10/summerboard-v3.html>, Dec. 2007, 3 pages. |
| Iphone Info, “ModifYing the iPhone SpringBoard”, Available at: <http://iphoneinfo.ca/modifying-the-iphone-springboard>, Dec. 2007, 6 pages. |
| ISO 9241-10:1996 Ergonomic Requirements for Office Work with Visual Display Terminals (VDTs)—Part 10, Dialogue Principles, International Standard—ISO, Zuerich, CH, vol. 9241-10, May 1, 1996, 17 pages. |
| ISO 9241-11:1998 Ergonomic requirements for office work with visual display terminals (VDTs)—Part 11, Guidance on usability, International Standard—ISO, Zuerich, CH, vol. 9241-11, Mar. 15, 1998, 27 pages. |
| ISO 9241-12:1998 Ergonomic requirements for office work with visual display terminals (VDTs)—Part 12, Presentation of Information, International Standard—ISO, Zuerich, CH, vol. 9241-12, Dec. 1, 1998, 52 pages. |
| Jazzmutant, “Jazzmutant Lemur”, Available at <http://64.233.167.104/search?a=cache:3g4wFSaZiXIJ:www.nuloop.c>, Nov. 16, 2005, 3 pages. |
| Jazzmutant, “The Lemur: Multitouch Control Surface”, Available at <http://64233.167.104/search?q=cache:j0_nFbNVzOcJ:www.cycling7>, retrieved on Nov. 16, 2005, 3 Pages. |
| Jobs, Steve, “iPhone Introduction in 2007 (Complete)”, available at <https://www.youtube.com/watch?v=9hUlxyE2Ns8>, Jan. 10, 2013, 3 pages. |
| Joire, Myriam, “Neonode N1m Review”, available at <http://www.youtube.com/watch?v=Tj-KS2kflr0>, Jun. 29, 2007, 3 pages. |
| Karlson et al., “AppLens and LaunchTile: Two Designs for One-Handed Thumb Use on Small Devices”, CHI 2005, Papers: Small Devices 1, Apr. 2-7, 2005, pp. 201-210. |
| Karlson et al., “AppLens and LaunchTile: Two Designs for One-Handed Thumb Use on Small Devices”, Powerpoint Presentation, CHI 2005, pp. 1-17. |
| Khella et al., “Pocket PhotoMesa: A Zoomable Image Browser for PDAs”, Proceedings of the 3rd International Conference on Mobile and Ubiquitous Multimedia, available at <http://delivery.acm.org/10.1145/1060000/1052384/p19-khella.pdf?key1=1052384&key2=2419987911&co11=GUIDE&d1=GUIDE&CFID=47073625&CFTOKEN=65767142>, Oct. 29, 2004, 2 pages. |
| Kinoma, “Kinoma Player 4 EX Documentation”, Available at <http://replay.waybackmachine.org/20061101175306/http://www.kinoma.com/index/pd-player-4>, Retrieved on Apr. 4, 2011, Nov. 1, 2006, 28 pages. |
| Kondo, Daisuke, “Windows XP Tablet PC Edition Quick Review Challenging by Microsoft”, PCfan No. 9, No. 28, Japan, Mainichi Communication., Oct. 15, 2002, pp. 12-17. |
| Laakko et al., “Adapting Web Content to Mobile User Agents”, IEEE Internet Computing, vol. 9, No. 2, Mar./Apr. 2005, pp. 46-53. |
| Landragin Frédéric, “The Role of Gesture in Multimodal Referring Actions”, Proceedings of the 4th IEEE International Conference on Multimodal Interfaces, available at <http://ieeexplore.iee.org/ie15/8346/26309/01166988pdf?arnumber=1166988>, 2002, 6 pages. |
| Lie Håkon W., “Cascading Style Sheets (chpt 8 CSS for small screens)”, Online Available at <http://people.opera.com/howcome/2006/phd/css.pdf> University of Osloensis, MDCCCXI, pp. 243-247, Retrieved on Dec. 14, 2007, 2005, 8 pages. |
| Macintosh Human Interface Guidelines (chapter 1), Online available at : http://interface.free.fr/Archives/Apple_HIGuidelines.pdf, 1995, 14 pages. |
| Macworld, “First Look: Leopard first looks: Dashboard”, Available at: <http://www.macworld.com/article/52297/2005/08/leodash.html>, Aug. 9, 2006, 3 pages. |
| Macworld, “Whip up a widget”, Available at: <http://www.macworld.com/article/46622/2005/09/octgeekfactor.html>, Sep. 23, 2005, 6 pages. |
| Mello, Jr J., “Tiger's Dashboard Brings Widgets to New Dimension”, MacNewsWorld, Available at: <http://www.macnewsworld.com/story/42630.html>, Retrieved on Jun. 23, 2006, 3 pages. |
| Microsoft Word, “Example of Scrolling Pages in Word 2003”, 2003, 3 pages. |
| Microsoft, “Working screenshot of Microsoft Office 2003”, Aug. 19, 2003, 14 Pages. |
| microsoft.com, “Right-Clicking with a Pen”, microsoft, Available at: http://www.microsoft.com/windowsxp/using/tabletpc/learnmore/rightclick.mspx, Nov. 7, 2002, 3 pages. |
| Milic-Frayling et al., “SmartView: Enhanced Document Viewer for Mobile Devices”, Microsoft Technical Report, available at <ftp://ftp.research.microsoft.com/pub/tr/tr-2002-114.pdf>, Retrieved on Dec. 17, 2007, Nov. 15, 2002, 10 pages. |
| Milic-Frayling et al., “SmartView: Flexible Viewing of Web Page Contents”, Proceedings of the Eleventh International World Wide Web Conference, available at <http://www2002.org/CDROM/poster/172/> Retrieved on May 5, 2008, May 11, 2002, 4 pages. |
| Miller Matthew, “HTC Touch and Touch FLO Interface”, 7:53 minutes video, available at <http://www.youtube.com/watch?v=60Up4wOcUc4>, uploaded on Jun. 6, 2007, 2 pages. |
| Minutes of Meeting received for European Patent Application No. 09170697.8, mailed on Jul. 10, 2018, 6 pages. |
| Minutes of the Oral Proceedings received for European Application No. 08798713.7, mailed on Aug. 6, 2018, 4 pages. |
| Mobilissimo.Ro, “HTC Touch—Touch FLO Demo”, Online Available at: <<https://www.youtube.com/watch?v=YQ8TQ9Rr_7E>, Jun. 5, 2007, 1 page. |
| Mountfocus Information Systems, “An Onscreen Virtual Keyboard: touchscreen, kiosk and Windows compatible”, Available at: http://www.virtual-kevboard.com, Dec. 19, 2007, 3 pages. |
| Multimedia Video Formats, Available online at <http://www.w3sschools.com/media/media_videoformats.asp?output=print>, 2006, 2 pages. |
| N1 Quick Start Guide, Version 0.5, Available at <http://www.instructionsmanuals.com/download/telefonos_movil/Neonode-N1-en.pdf>, Jul. 29, 2004, pp. 1-24. |
| Nakata Atsushi, “Tablet PC aiming at spread pen input by changing target user”, Nikkei Windows for IT Professionals, Nikkei Business Publications, Inc. No. 69., Dec. 1, 2002, pp. 14-16. |
| Neonode Inc., “Welcome to the N1 Guide”, available at <http://www.ebookspdf.com/gadget/2818/neonode-n1m-manual/>, Jul. 2004, pp. 1-42. |
| Nokia 7710, https://www.nokia.com/en_int/phones/sites/default/files/user-guides/Nokia_7710_UG_en.pdf, 2005, pp. 1-153. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,005, mailed on May 29, 2015, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,010, mailed on Dec. 17, 2014, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/142,640, mailed on Jun. 5, 2015, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/987,255, mailed on Jul. 23, 2021, 46 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/620,647 mailed on Jun. 24, 2010, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/620,647 mailed on Nov. 17, 2009, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/620,647, mailed on Oct. 13, 2011, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/849,938, mailed on Dec. 14, 2011, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/849,938, mailed on Oct. 12, 2010, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,005, mailed on Apr. 12, 2017, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,005, mailed on Dec. 31, 2018, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,005, mailed on Mar. 18, 2011, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,005, mailed on Nov. 10, 2011, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,005, mailed on Oct. 24, 2013, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,008, mailed on Aug. 2, 2010, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,010 mailed on May 16, 2012, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,010 mailed on May 2, 2011, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,010, mailed on Jul. 24, 2017, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,010, mailed on Jun. 25, 2015, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,010, mailed on Oct. 24, 2013,13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,011, mailed on Aug. 11, 2010,19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,013, mailed on Jun. 11, 2010, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,638, mailed on Jan. 17, 2012, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/850,638, mailed on Oct. 26, 2010, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/961,773, mailed on Apr. 15, 2011, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/961,773, mailed on May 10, 2012, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/969,809, mailed on Mar. 14, 2011, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/969,912, mailed on Apr. 13, 2011, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/969,912, mailed on Sep. 10, 2013, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/217,029, mailed on Apr. 18, 2011, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/217,029, mailed on Aug. 19, 2013, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/217,029, mailed on Jan. 25, 2012, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/217,029, mailed on Oct. 28, 2015, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/242,851, mailed on Apr. 15, 2011, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/242,851, mailed on Jun. 26, 2015, 33 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/242,851, mailed on Oct. 6, 2014, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/242,851, mailed on Sep. 20, 2012, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/274,346, mailed on Aug. 26, 2011, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/364,470, mailed on Mar. 4, 2011, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/364,470, mailed on Nov. 13, 2009, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/364,470, mailed on Sep. 2, 2010, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/365,887, mailed on Aug. 31, 2011, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/365,888, mailed on Nov. 10, 2011, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/981,433, mailed on Oct. 11, 2012, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/077,524, mailed on Jun. 28, 2013, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/104,903, mailed on Nov. 13, 2012, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/104,911, mailed on Feb. 20, 2013, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/155,304, mailed on Sep. 5, 2012, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/261,112, mailed on Apr. 5, 2018, 40 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/261,112, mailed on Jul. 8, 2015, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/261,112, mailed on Jun. 18, 2014, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/261,112, mailed on Nov. 29, 2016, 34 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/004,189, mailed on Dec. 21, 2017, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/153,617, mailed on Apr. 2, 2018, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/426,836, mailed on Oct. 18, 2018, 40 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/493,672, mailed on Dec. 12, 2019, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/493,672, mailed on Nov. 6, 2018, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/990,076, mailed on Aug. 13, 2018, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/688,766, mailed on May 22, 2020, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/107,321, mailed on Mar. 3, 2022, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Apr. 4, 2011, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Apr. 20, 2006, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Jun. 20, 2013, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Jun. 24, 2009, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Mar. 15, 2010, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Mar. 21, 2008, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Mar. 23, 2007, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/090,627, mailed on Oct. 6, 2004, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/710,125, mailed on Apr. 12, 2016, 12 pages. |
| Notice of Acceptance received for Australia Patent Application No. 2012261534, mailed on Jan. 6, 2015, 2 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2007292383, mailed on Jan. 4, 2012, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2008296445, mailed on Dec. 14, 2011, 4 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2010200763, mailed on Aug. 21, 2012, 1 page. |
| Notice of Acceptance received for Australian Patent Application No. 2012200475, mailed on Aug. 24, 2015, 2 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2012202140, mailed on May 28, 2014, 2 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2014204422, mailed on Apr. 28, 2016, 2 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2016213886, mailed on Feb. 9, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017201768, mailed on Nov. 21, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017202587, mailed on Nov. 6, 2019, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018200272, mailed on Apr. 23, 2019, 3 pages. |
| Notice of Allowance received for Australian Patent Application No. 2015202076, mailed on Apr. 5, 2017, 3 pages. |
| Notice of Allowance received for Canadian Patent Application No. 2,633,759, mailed on Sep. 9, 2013, 1 page. |
| Notice of Allowance received for Canadian Patent Application No. 2,845,297, mailed on Nov. 10, 2014, 1 page. |
| Notice of Allowance received for Canadian Patent Application No. 2,890,778, mailed on Apr. 24, 2017, 1 page. |
| Notice of Allowance received for Chinese Patent Application No. 200780041309.3, mailed on Jul. 31, 2017, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 200980000229.2, mailed on Oct. 24, 2014, 4 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201210399033.9, mailed on Jun. 20, 2016, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201310724733.5, mailed on Dec. 27, 2018, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201410250648.4, mailed on Aug. 20, 2018, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201410250688.9, mailed on May 21, 2018, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201410251370.2, mailed on Jul. 31, 2018, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201410251400.X, mailed on Aug. 20, 2018, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2009-051921, mailed on Jan. 20, 2014, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2011-537452, mailed on Jun. 14, 2013, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2013-127963, mailed on Oct. 9, 2015, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2013252338, mailed on Jun. 23, 2017, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2014-253365, mailed on Nov. 26, 2018, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-091460, mailed on Oct. 9, 2018, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-204561, mailed on Mar. 12, 2019, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2013-011209, mailed on Jun. 13, 2016, 2 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2009-7007064, mailed on Sep. 30, 2011, 2 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2009-7007067, mailed on Dec. 1, 2011, 2 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2010-7007258, mailed on Nov. 20, 2013, 2 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2011-7014104, mailed on Aug. 29, 2013, 2 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2011-7019633, mailed on May 18, 2012, 2 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2011-7026583, mailed on Apr. 29, 2015, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2014-7011273, mailed on Apr. 28, 2015, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/077,524, mailed on Sep. 15, 2015, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/011,639, mailed on Sep. 29, 2015, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 10/090,627, mailed on Oct. 22, 2014, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/620,647 mailed on Mar. 2, 2012, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/849,938, mailed on Nov. 27, 2013, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/849,938, mailed on Oct. 10, 2013, 28 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/850,008, mailed on Mar. 11, 2011, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/850,011, mailed on Feb. 11, 2011, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/850,011, mailed on Feb. 18, 2011, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/850,013, mailed on Oct. 20, 2010, 20 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/969,809, mailed on Apr. 26, 2013, 17 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/969,912, mailed on Jun. 11, 2014, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/969,912, mailed on Mar. 6, 2014, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/217,029, mailed on Jan. 17, 2017, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/242,851, mailed on Dec. 27, 2016, 20 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/274,346, mailed on Jul. 17, 2013, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/274,346, mailed on Mar. 12, 2013, 18 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/364,470, mailed on Nov. 24, 2017, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/365,887, mailed on May 23, 2012, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/077,524, mailed on May 27, 2015, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/104,903, mailed on Apr. 29, 2013, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/104,911, mailed on Jun. 10, 2013, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/011,639, mailed on Feb. 16, 2016, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/142,640, mailed on Dec. 11, 2019, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/710,125, mailed on Apr. 19, 2019, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/710,125, mailed on May 7, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/004,189, mailed on Feb. 26, 2018, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/153,617, mailed on Nov. 23, 2018, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/426,836, mailed on Dec. 16, 2019, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/493,672, mailed on Apr. 14, 2020, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/990,076, mailed on Dec. 12, 2018, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/990,076, mailed on Jan. 17, 2019, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/990,076, mailed on Nov. 8, 2018, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/378,990, mailed on Aug. 11, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/688,766, mailed on Mar. 23, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/987,255, mailed on Jul. 14, 2022, 18 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/107,321, mailed on Jun. 28, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/850,010, mailed on Feb. 6, 2019, 25 pages. |
| Notification of Acceptance received for Australian Patent Application No. 2009204252, mailed on Oct. 17, 2011, 3 pages. |
| NTT DOCOMO, “i-mode Compatible Pictograms”, available at <http://www.nttdocomo.co.jp/english/service/imode/make/content/pictograph/index.html>, 2008, 2 pages. |
| Office Action received for European Patent Application No. 13174706.5, mailed on Oct. 16, 2017, 8 pages. |
| Office Action received for Australian Patent Application No. 2007289019, mailed on Jul. 2, 2009, 3 pages. |
| Office Action received for Australian Patent Application No. 2007289019, mailed on Oct. 7, 2009, 2 pages. |
| Office Action received for Australian Patent Application No. 2007292383, mailed on Dec. 22, 2011, 2 pages. |
| Office Action received for Australian Patent Application No. 2007292383, mailed on Mar. 24, 2010, 2 pages. |
| Office Action received for Australian Patent Application No. 2007292383, mailed on May 12, 2011, 2 pages. |
| Office Action received for Australian Patent Application No. 2008296445, mailed on Oct. 29, 2010, 2 pages. |
| Office Action received for Australian Patent Application No. 2009100760, mailed on Sep. 28, 2009, 2 pages. |
| Office Action received for Australian Patent Application No. 2009100812, mailed on Sep. 14, 2009, 2 pages. |
| Office Action received for Australian Patent Application No. 2009100813, mailed on Sep. 14, 2009, 2 pages. |
| Office Action received for Australian Patent Application No. 2009204252, issued on Nov. 28, 2013, 2 pages. |
| Office Action received for Australian Patent Application No. 2009204252, issued on Sep. 16, 2014, 6 pages. |
| Office Action received for Australian Patent Application No. 2009204252, mailed on Apr. 20, 2010, 3 pages. |
| Office Action received for Australian Patent Application No. 2009204252, mailed on May 18, 2011, 2 pages. |
| Office Action received for Australian Patent Application No. 2010200763, mailed on Jul. 28, 2011, 2 pages. |
| Office Action received for Australian Patent Application No. 2011101194, mailed on Oct. 21, 2011, 2 pages. |
| Office Action received for Australian Patent Application No. 2012200475, issued on Aug. 4, 2015, 3 pages. |
| Office Action received for Australian Patent Application No. 2012200475, issued on Jun. 29, 2015, 3 pages. |
| Office Action received for Australian Patent Application No. 2012200475, issued on Nov. 19, 2013, 4 pages. |
| Office Action received for Australian Patent Application No. 2012202140, mailed on Aug. 12, 2013, 2 pages. |
| Office Action received for Australian Patent Application No. 2012261534, issued on Dec. 3, 2013, 3 pages. |
| Office Action received for Australian Patent Application No. 2014204422, issued on Aug. 7, 2015, 3 pages. |
| Office Action received for Australian Patent Application No. 2015202076, issued on May 5, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2015215876, mailed on Aug. 1, 2016, 4 pages. |
| Office Action received for Australian Patent Application No. 2015215876, mailed on Jul. 26, 2017, 6 pages. |
| Office Action received for Australian Patent Application No. 2015215876, mailed on Jun. 28, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2015215876, mailed on May 24, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2016213886, mailed on May 18, 2017, 2 pages. |
| Office Action received for Australian Patent Application No. 2017201768, mailed on Feb. 28, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2017202587, mailed on Apr. 26, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2017202587, mailed on Jul. 4, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2017202587, mailed on Jul. 4, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2018200272, mailed on Jan. 17, 2019, 2 pages. |
| Office Action received for Australian Patent Application No. 2019200692, mailed on Dec. 24, 2019, 2 pages. |
| Office Action received for Canadian Patent Application No. 2,633,759, mailed on Apr. 2, 2009, 5 pages. |
| Office Action received for Canadian Patent Application No. 2,633,759, mailed on Aug. 12, 2010, 8 pages. |
| Office Action received for Canadian Patent Application No. 2,633,759, mailed on Dec. 10, 2009, 6 pages. |
| Office Action received for Canadian Patent Application No. 2,845,297, mailed on Apr. 23, 2014, 2 pages. |
| Office Action received for Canadian Patent Application No. 2,890,778, mailed on May 19, 2016, 6 pages. |
| Office Action received for Canadian Patent Application No. 2,983,178, mailed on Aug. 16, 2018, 5 pages. |
| Office Action received for Canadian Patent Application No. 2,983,178, mailed on Jul. 22, 2019, 6 pages. |
| Office Action received for Chinese Patent Application No. 200980152822.9, mailed on Dec. 5, 2012, 10 pages. |
| Office Action received for Chinese Patent Application No. 200680053441.1, mailed on Nov. 12, 2010, 4 pages. |
| Office Action received for Chinese Patent Application No. 200780001140.9, mailed on Jan. 15, 2010, 5 pages. |
| Office Action received for Chinese Patent Application No. 200780001140.9, mailed on Jun. 10, 2011, 7 pages. |
| Office Action received for Chinese Patent Application No. 200780041222.6, mailed on Feb. 29, 2012, 6 pages. |
| Office Action received for Chinese Patent Application No. 200780041222.6, mailed on Jul. 25, 2012, 3 pages. |
| Office Action received for Chinese Patent Application No. 200780041222.6, mailed on Oct. 13, 2010, 10 pages. |
| Office Action received for Chinese Patent Application No. 200780041309.3, mailed on Feb. 8, 2017, 4 pages. |
| Office Action received for Chinese Patent Application No. 200780041309.3, mailed on Jan. 18, 2012, 15 pages. |
| Office Action received for Chinese Patent Application No. 200780041309.3, mailed on Nov. 1, 2012, 5 pages. |
| Office Action received for Chinese Patent Application No. 200780052019.9, mailed on Feb. 29, 2012, 6 pages. |
| Office Action received for Chinese Patent Application No. 200880110709.X, mailed on Nov. 24, 2011, 10 pages. |
| Office Action received for Chinese Patent Application No. 200880112570.2, mailed on Aug. 24, 2011, 6 pages. |
| Office Action received for Chinese Patent Application No. 200910175852.3, mailed on Apr. 24, 2012, 10 pages. |
| Office Action received for Chinese Patent Application No. 200910175852.3, mailed on Jun. 2, 2011, 6 pages. |
| Office Action received for Chinese Patent Application No. 200980000229.2, issued on Jan. 6, 2014, 6 pages. |
| Office Action received for Chinese Patent Application No. 200980000229.2, mailed on Jun. 27, 2014, 7 pages. |
| Office Action received for Chinese Patent Application No. 200980000229.2, mailed on Nov. 30, 2011, 24 pages. |
| Office Action received for Chinese Patent Application No. 200980000229.2, mailed on Oct. 26, 2012, 22 pages. |
| Office Action received for Chinese Patent Application No. 200980152822.9, mailed on Oct. 21, 2013, 2 pages. |
| Office Action received for Chinese Patent Application No. 201210399033.9, mailed on Nov. 27, 2014, 7 pages. |
| Office Action received for Chinese Patent Application No. 201210399033.9, mailed on Oct. 8, 2015, 8 pages. |
| Office Action received for Chinese Patent Application No. 201310724733.5, mailed on Apr. 9, 2018, 11 pages. |
| Office Action received for Chinese Patent Application No. 201310724733.5, mailed on Aug. 15, 2018, 2 pages. |
| Office Action received for Chinese Patent Application No. 201310724733.5, mailed on Aug. 28, 2018, 6 pages. |
| Office Action received for Chinese Patent Application No. 201310724733.5, mailed on Oct. 30, 2017, 14 pages. |
| Office Action received for Chinese Patent Application No. 2013107247335, mailed on Apr. 12, 2016, 14 pages. |
| Office Action received for Chinese Patent Application No. 2013107247335, mailed on Apr. 21, 2017, 18 pages. |
| Office Action received for Chinese Patent Application No. 2013107247335, mailed on Dec. 30, 2016, 13 pages. |
| Office action received for Chinese Patent Application No. 201410250648.4, mailed on Feb. 14, 2018, 6 pages. |
| Office Action received for Chinese Patent Application No. 2014102506484, mailed on Jun. 29, 2017, 13 pages. |
| Office Action received for Chinese Patent Application No. 2014102506484, mailed on Oct. 9, 2016, 6 pages. |
| Office Action received for Chinese Patent Application No. 201410250688.9, mailed on Nov. 16, 2017, 6 pages. |
| Office Action received for Chinese Patent Application No. 2014102506889, mailed on Jun. 1, 2017, 12 pages. |
| Office Action received for Chinese Patent Application No. 2014102506889, mailed on Sep. 28, 2016, 7 pages. |
| Office Action received for Chinese Patent Application No. 201410251370.2, mailed on Feb. 11, 2018, 14 pages. |
| Office Action received for Chinese Patent Application No. 2014102513702, mailed on May 12, 2017, 8 pages. |
| Office Action received for Chinese Patent Application No. 2014102513702, mailed on Sep. 5, 2016, 7 pages. |
| Office Action received for Chinese Patent Application No. 201410251400.X, mailed on Feb. 8, 2018, 6 pages. |
| Office Action received for Chinese Patent Application No. 201410251400.X, mailed on Jul. 4, 2016, 8 pages. |
| Office Action received for Chinese Patent Application No. 201410251400.X, mailed on May 26, 2017, 11 pages. |
| Office Action received for European Patent Application No. 07814689.1, mailed on Mar. 4, 2011, 6 pages. |
| Office Action received for European Patent Application No. 07814690.9, mailed on Jun. 21, 2010, 5 pages. |
| Office Action received for European Patent Application No. 07814690.9, mailed on Oct. 19, 2010, 8 pages. |
| Office Action received for European Patent Application No. 07841980.1, mailed on Feb. 23, 2012, 5 pages. |
| Office Action received for European Patent Application No. 07869929.5, mailed on Dec. 27, 2010, 6 pages. |
| Office Action received for European Patent Application No. 08798713.7, mailed on Feb. 9, 2012, 7 pages. |
| Office Action received for European Patent Application No. 08798713.7, mailed on Jul. 29, 2014, 18 pages. |
| Office Action received for European Patent Application No. 08798713.7, mailed on Jun. 22, 2011, 10 pages. |
| Office Action received for European Patent Application No. 08829660.3, mailed on Aug. 2, 2013, 7 pages. |
| Office Action received for European Patent Application No. 08829660.3, mailed on Jan. 3, 2020, 6 pages. |
| Office Action received for European Patent Application No. 08829660.3, mailed on Jan. 11, 2019, 7 pages. |
| Office Action received for European Patent Application No. 08829660.3, mailed on Jul. 5, 2016, 5 pages. |
| Office Action received for European Patent Application No. 08829660.3, mailed on Oct. 15, 2010, 8 pages. |
| Office Action received for European Patent Application No. 09170697.8 mailed on Dec. 13, 2011, 4 pages. |
| Office Action received for European Patent Application No. 09170697.8, mailed on Mar. 3, 2017, 8 pages. |
| Office Action received for European Patent Application No. 09171787.6, mailed on Jul. 12, 2011, 5 pages. |
| Office Action received for European Patent Application No. 09700333.9, mailed on Jun. 10, 2011, 5 pages. |
| Office Action received for European Patent Application No. 09700333.9, mailed on Nov. 26, 2010, 5 pages. |
| Office Action received for European Patent Application No. 12189764.9, mailed on Jan. 21, 2019, 7 pages. |
| Office Action received for European Patent Application No. 12189764.9, mailed on Mar. 1, 2016, 6 pages. |
| Office Action received for European Patent Application No. 12194312.0, mailed on Jan. 13, 2014, 4 pages. |
| Office Action received for European Patent Application No. 12194312.0, mailed on Oct. 8, 2013, 5 pages. |
| Office Action received for European Patent Application No. 12194315.3, mailed on Jan. 13, 2014, 4 pages. |
| Office Action received for European Patent Application No. 12194315.3, mailed on Oct. 8, 2013, 5 pages. |
| Office Action received for European Patent Application No. 17210062.0, mailed on Jan. 3, 2019, 6 pages. |
| Office Action received for German Patent Application No. 112007002107.1, mailed on Jun. 7, 2010, 3 pages. |
| Office Action received for Japanese Patent Application No. 2017-223021, mailed on Apr. 8, 2019, 7 pages. |
| Office Action received for Japanese Patent Application No. 2009-051921, mailed on May 31, 2013, 7 pages. |
| Office Action received for Japanese Patent Application No. 2009-527541, mailed on May 21, 2012, 3 pages. |
| Office Action received for Japanese Patent Application No. 2009-527541, mailed on Sep. 26, 2011, 3 pages. |
| Office Action received for Japanese Patent Application No. 2009-527566, mailed on Aug. 15, 2011, 3 pages. |
| Office Action received for Japanese Patent Application No. 2009-527566, mailed on Sep. 21, 2012, 3 pages. |
| Office Action received for Japanese Patent Application No. 2010-524102, mailed on Feb. 13, 2012, 2 pages. |
| Office Action received for Japanese Patent Application No. 2010-524102, mailed on Oct. 26, 2012, 4 pages. |
| Office Action received for Japanese Patent Application No. 2011-537452, mailed on Jan. 25, 2013, 7 pages. |
| Office Action received for Japanese Patent Application No. 2013-011209, mailed on Feb. 7, 2014, 3 pages. |
| Office Action received for Japanese Patent Application No. 2013-011209, mailed on Nov. 2, 2015, 9 pages. |
| Office Action received for Japanese Patent Application No. 2013-011209, mailed on Oct. 27, 2014, 3 pages. |
| Office Action received for Japanese Patent Application No. 2013-127963, mailed on Aug. 15, 2014, 8 pages. |
| Office Action received for Japanese Patent Application No. 2013-127963, mailed on Mar. 10, 2014, 7 pages. |
| Office Action received for Japanese Patent Application No. 2013-252338, mailed on Dec. 4, 2015, 4 pages. |
| Office Action received for Japanese Patent Application No. 2013-252338, mailed on Jan. 27, 2017, 10 pages. |
| Office Action received for Japanese Patent Application No. 2013-252338, mailed on Jan. 30, 2015, 4 pages. |
| Office Action received for Japanese Patent Application No. 2013-252338, mailed on Jun. 24, 2016, 4 pages. |
| Office Action received for Japanese Patent Application No. 2014-253365, mailed on Aug. 31, 2018, 6 pages. |
| Office Action received for Japanese Patent Application No. 2014-253365, mailed on Dec. 14, 2015, 6 pages. |
| Office Action received for Japanese Patent Application No. 2014-253365, mailed on Jul. 18, 2017, 9 pages. |
| Office Action received for Japanese Patent Application No. 2014-253365, mailed on Oct. 17, 2016, 11 pages. |
| Office Action received for Japanese Patent Application No. 2016-042767, mailed on Mar. 3, 2017, 10 pages. |
| Office Action received for Japanese Patent Application No. 2016-091460, mailed on Jun. 1, 2018, 3 pages. |
| Office Action received for Japanese Patent Application No. 2016-091460, mailed on Jun. 26, 2017, 6 pages. |
| Office Action received for Japanese Patent Application No. 2016-091460, mailed on Nov. 4, 2016, 6 pages. |
| Office Action received for Japanese Patent Application No. 2016-091460, mailed on Nov. 27, 2017, 7 pages. |
| Office Action received for Japanese Patent Application No. 2017-204561, mailed on Aug. 6, 2018, 7 pages. |
| Office Action received for Japanese Patent Application No. 2017-204561, mailed on Nov. 6, 2018, 8 pages. |
| Office Action received for Japanese Patent Application No. 2017-223021, mailed on Jul. 30, 2018, 12 pages. |
| Office Action received for Japanese Patent Application No. 2017-223021, mailed on Sep. 24, 2019, 6 pages. |
| Office Action received for Japanese Patent Application No. 2018-201088, mailed on Oct. 11, 2019, 9 pages. |
| Office Action received for Korean Patent Application No. 10-2009-7007067, mailed on Aug. 30, 2011, 2 pages. |
| Office Action received for Korean Patent Application No. 10-2009-7007067, mailed on Nov. 12, 2010, 3 pages. |
| Office Action received for Korean Patent Application No. 10-2010-7007258, mailed on Aug. 8, 2011, 2 pages. |
| Office Action received for Korean Patent Application No. 10-2010-7007258, mailed on Jan. 30, 2013, 8 pages. |
| Office Action received for Korean Patent Application No. 10-2011-7014104, mailed on Jan. 17, 2013, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2011-7026583, mailed on Aug. 14, 2014, 6 pages. |
| Office Action received for Korean Patent Application No. 10-2011-7026583, mailed on Oct. 25, 2013, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2014-7011273, mailed on Aug. 14, 2014, 5 pages. |
| Office Action received for Taiwan Patent Application No. 097100075, mailed on Dec. 29, 2011, 5 pages. |
| Office Action received for Canadian Patent Application No. 2,633,759, mailed on Apr. 18, 2013, 2 pages. |
| Office Action received for Chinese Patent Application No. 200680053441.1, mailed on Mar. 30, 2010, 5 pages. |
| Office Action received for Chinese Patent Application No. 200780041309.3, mailed on Jul. 2, 2013, 12 pages. |
| Office Action received for Chinese Patent Application No. 200880112570.2, mailed on Feb. 20, 2013, 7 pages. |
| Office Action received for Chinese Patent Application No. 200910173272.0, mailed on Nov. 30, 2011, 8 pages. |
| Office Action received for Chinese Patent Application No. 200980000229.2, mailed on Jul. 2, 2013, 4 pages. |
| Office Action received for European Patent Application No. 06846840.4, mailed on Oct. 13, 2008, 3 pages. |
| Office Action received for German Patent Application No. 112006003600.9, mailed on Aug. 9, 2011, 4 pages. |
| Office Action received for German Patent Application No. 112006003600.9, mailed on Oct. 27, 2009, 9 pages. |
| Office Action received for Japanese Patent Application No. 2008-548858 mailed on May 30, 2011, 3 pages. |
| Office Action received for Japanese Patent Application No. 2008-548858, mailed on Jan. 20, 2012, 5 pages. |
| Office Action received for Japanese Patent Application No. 2009-51921 mailed on Jan. 20, 2012, 5 pages. |
| Office Action received for Japanese Patent Application No. 2009-051921, mailed on Jun. 27, 2011, 6 pages. |
| Office Action received for Japanese Patent Application No. 2009-051921, mailed on Sep. 24, 2012, 3 pages. |
| O' Hara, “Absolute Beginner's Guide to Microsoft Window XP”, Que Publishing, 2003, 1 page. |
| Oliver, Dick, “Adding Multimedia to Your Web Site”, Chapter 22, Web Publishing Professional Reference Edition, Available online at <http://www.ssuet.edu.pk/taimoor/books/1-57521-198-X/index.htm>, 1997, 14 pages. |
| Online Learning @ College of the Canyons Create and Save a Document, Online available at:- http://psychology230.tripod.com/canyons_online/id11.html, attached as pdf, 2008, 2008, 1 page. |
| Opera Software, “Download the Opera Mobile™ Browser”, Available at <http://www.opera.com/products/mobile/products/>, retrieved on Oct. 19, 2006, 5 pages. |
| Opera Software, “Opera 7.60 for Series 60 Mobile”, Available at <http://jp.opera.com/support/tutorials/s60/760/O760manual.pdf>, 2009, 14 pages. |
| Opera Software, “Opera 8.5 Beta 2 for Windows Mobile, Pocket PC”, Available at <http://www.opera.com/products/mobile/products/winmobileppc>, retrieved on Apr. 5, 2006, 2 pages. |
| Opera Software, “Opera 8.5 for S60 Phones-Get the Full Internet Experience on Your Mobile Phone”, Available at <http://www.symbian-freak.com/news/1105/opera.htm>, Oct. 14, 2005, 3 pages. |
| Opera Software, “Opera for Mobile, The Full Web Anytime, Anywhere”, Available at <www.opera.com/mobile>, Jan. 2006, 7 pages. |
| Opera Software, “Opera for S60 Tutorial”, Available at <http://www.xmarks.com/site/www.opera.com/support/tutorials/s60/>, retrieved on Apr. 5, 2006, 5 pages. |
| Opera Software, “Opera for Windows Mobile Smartphone 2003 Tutorial”, Available at <http://www.opera.com/support/tutorials/winmobile>, retrieved on Apr. 5, 2005, 4 pages. |
| Opera Software, “The New Opera Browser for Series 60 Features Zoom and Password Manager”, Press Releases Database, Available at <http://pressreleases.techwhack.com/1334/1411-opera-browser-features-zoom-and- password>, Nov. 14, 2005, 3 pages. |
| Opera Software, “Welcome to Widgetize”, Copyright © 2006 Opera Software ASA, Available at: <http://widgets.opera.com/widgetize>, 2006, 1 page. |
| Palme et al., “MIME Encapsulation of Aggregate Documents, such as HTML”, Network Working Group, 1999, 24 pages. |
| Palmone, “Your Mobile Manager”, Chapter 2, LifeDrive™ User's Guide, available at <http://www.palm.com/us/support/handbooks/lifedrive/en/lifedrive_handbook.pdf>, 2005, 23 pages. |
| Park, Will, “Apple iPhone v1.1.1 SpringBoard Hacked to Display Multiple Pages”, available at <http://www.intomobile.com/2007/10/09/apple-iphone-v111-springboard- hacked-to-display-multiple-pages/>, Oct. 9, 2007, 5 pages. |
| Park, Will, “Neonode N2 Unboxing Pics!”, available at <http://www.intomobile.com/2007/07/18/neonode-n2-unboxing-pics/>, Jul. 18, 2007, 7 pages. |
| Patent Grant received for Japanese Patent Application No. 2008-548858, mailed on Sep. 24, 2012, 3 pages. |
| PCFAN, “Boot Camp Introduction/Data Transition/Operability/Ability Truth Derived from Gap Mac&Win Dual Boot Hard Verification”, Daily Communications, vol. 13, No. 14, Jun. 15, 2006, 4 pages. |
| “Playing QuickTime Movies”, Available online at <http://www.3schools.com/media/media_quicktime.asp?output=print>, 2006, 2 pages. |
| “Playing Videos on the Web”, Available online at <http://www.w3schools.com/media/media_browservideos.asp?out=print>, 2006, 3 pages. |
| pocketgear.com, “Software Keyboards: Efzy-Japanese (Eng/Jp) 4.0”, TimeSpacesystem Co. Ltd, available at <http://classic.pocketgear.com/software detail.asp?id=9115>, updated on Sep. 23, 2008, 9 pages. |
| Potter, “Graffiti Smilies”, PalmInfocenter Forums, available at <http://www.palminfocenter.com/forum/viewtopic.php?t=11307>, Feb. 9, 2003, 5 pages. |
| Pre-Interview First Office Action received for U.S. Appl. No. 16/378,990, mailed on Apr. 9, 2020, 5 pages. |
| Raman et al., “Application-Specific Workload Shaping in Multimedia-Enabled Personal Mobile Devices”, CODES+ISSS, Oct. 22-25, 2006, pp. 4-9. |
| Realnetworks, “Transition Effects”, RealNetworks Production Guide, Available at: <http://service.real.com/help/library/guides/productionguidepreview/HTML/htmflles/transit.htm>, 2001, 21 pages. |
| Record of Oral Hearing received for U.S. Appl. No. 14/142,640, mailed on Nov. 20, 2019, 15 pages. |
| Response to Notice of Opposition filed for Australian Patent Application No. 2009204252, on Apr. 28, 2014, Apr. 28, 2014, 4 pages. |
| Robie, Jonathan, “What is the Document Object Model?”, Texcel Research, available at <http://www.w3.org/TR-DOM/introduction.html>, 2006, 5 pages. |
| Rohrer, Tim, “Metaphors We Compute by: Bringing Magic into Interface Design”, Available online at <http://www.uoregon.edu/-uophil/metaphor/gui4web.htm>, retrieved on Jun. 13, 2006, 7 pages. |
| Roto et al., “Minimap—A Web Page Visualization Method for Mobile Phones”, Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 22-27, 2006, pp. 35-44. |
| Sadun, Erica, “1.1.1 iPhone Multipage Springboard Hack”, Available at: <http://www.tuaw.com/2007/10/09/1-1-1-iphone-multipage-springboard-hack/>, on Oct. 9, 2007, Oct. 9, 2007, 3 pages. |
| Sadun, Erica, “Found Footage: Scrolling iPhone Dock Smashes Through 16-icon Home Screen Limit”, The Unofficial Apple Weblog, available at <http://www.tuaw.com/2007/08/30/found-footage-scrolling-iphone-dock-smashes-through-16-icon-hom/>, Aug. 30, 2007, 3 pages. |
| Sadun, “Erica's Documentation: Applications and Utilities for the iPhone and iPod Touch”, Copyright 2007, Available at: <http://ericasadun.com/ftp/Deprecated/Documentation/Manual-0.04.pdf>, 2007, 22 pages. |
| Salmre I., “Characteristics of Mobile Applications”, Chapter 2, Salmre_02.fm, Dec. 20, 2004, pp. 19-36. |
| Schreiner, Tony, “High DPI in IE: Tip & Mystery Solved”, Tony Schreiner's Blog, available at <http://blogs.msdn.com/tonyschr/archive/2004/05/126305.aspx>, May 2004, 2 pages. |
| Sharewareconnection, “Handy Animated Emoticons”, available at <http://www.sharewareconnection.com/handy-animated-emoticons.htm>, Jul. 2007, 3 pages. |
| Shima et al., “Android Application-Development”, From basics of development to mashup/hardwareinteraction, a road to “takumi” of Android application-development, Section I, difference from prior platforms, things which can be done with Android, SoftwareDesign, Japan, Gijutsu-Hyohron Co., Ltd., Issue vol. 287 (No. 221), Mar. 18, 2009, pp. 58-65. |
| Shiota, Shinji, “Special Developer's Story”, DOS / V magazine, vol. 13, No. 10., Jun. 1, 2004, 12 pages. |
| “SilverScreen Theme Library”, Online Available at <https://web.archive.org/web/20061113121041/http://www.pocketsensei.com/ss_themes.htm>, Nov. 13, 2006, 3 pages. |
| “SilverScreen User Guide”, Online Available at <https://web.archive.org/web/20061113121032/http://www.pocketsensei.com/ss_guide.htm>, Nov. 13, 2006, 12 pages. |
| “Smiley Conversion Table”, available at <http://surf-style.us/manual3.htm>, Dec. 5, 2008, 8 pages. |
| snapfiles.com, “Dexpot”, Snapfiles, Oct. 10, 2007, 3 pages. |
| Stampfli, Tracy, “Exploring Full-Screen Mode in Flash Player 9”, Available online at <http://www.adobe.com/devnet/flashplayer/articles/full_screen_mode.html>, Nov. 14, 2006, 2 pages. |
| Stanek et al., “Video and Animation Plug-Ins”, Chapter 9, Web Publishing Professional Reference Edition, available online at <http://www.ssuet.edu.pk/taimoor/books/1-57521-198-X/index.htm>, 1997, 18 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 09170697.8 mailed on Apr. 22, 2013, 6 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 09170697.8, mailed on Jul. 29, 2016, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 09170697.8, mailed on Oct. 19, 2017, 12 pages. |
| Summons to Attend Oral proceedings received for European Patent Application No. 06846840.4, mailed on May 18, 2009, 7 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 07814689.1, mailed on Dec. 1, 2011, 11 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 07814690.9, mailed on Nov. 22, 2011, 4 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 07841980.1, mailed on Sep. 28, 2012, 8 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 07869929.5, Dec. 13, 2011, 6 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 07869929.5, mailed on Jan. 23, 2012, 1 page. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 08798713.7, mailed on Aug. 30, 2013, 15 pages. |
| Summons to Attend Oral proceedings received for European Patent Application No. 08798713.7, mailed on Mar. 26, 2018, 11 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 09700333.9, mailed on Sep. 21, 2012, 4 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 12189764.9, mailed on Mar. 12, 2020, 11 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17210062.0, mailed on Oct. 30, 2019, 7 pages. |
| Summons to Oral Proceedings received for European Patent Application No. 12194312.0, mailed on Dec. 8, 2016, 9 pages. |
| Summons to Oral Proceedings received for European Patent Application No. 12194315.3, mailed on Dec. 8, 2016, 9 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 11/850,011, mailed on Feb. 24, 2011, 6 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/987,255, mailed on Jul. 26, 2022, 2 pages. |
| Surfin'safari, “XUL”, Available online at <http://weblogs.mozillazine.org/hyatt.archives/2003_10.html>, Oct. 2003, 7 pages. |
| Synergy Solutions, “Launch 'Em Version 3.1”, Retrieved from the Internet: http://www.fladnag.net/downloads/telephone/palm/APPS/Inchem31/Documentation/Launch Em.pdf, 2001, pp. 1-39. |
| Takahashi, Masaaki, “Inside Macintosh, Mystery of File V, Mystery of Drag & Drop”, NikkeiMAC, Nikkei Business Publications Inc., vol. 17, Aug. 15, 1994, 9 pages. |
| Thomas et al., “Applying Cartoon Animation Techniques to Graphical User Interfaces”, ACM Transactions on Computer-Human Interaction, vol. 8, No. 3, Sep. 2001, pp. 198-222. |
| Tidwell, Jenifer, “Animated Transition”, Designing Interfaces, Patterns for effective Interaction Design, First Edition, Nov. 2005, 4 pages. |
| Tidwell, Jenifer, “Designing Interfaces, Animated Transition”, Archieved by Internet Wayback Machine, Available at <https://web.archive.org/web/20060205040223/http://designinginterfaces.com:80/Animated_Transition>, Retrieved on Mar. 20, 2018, 2005, 2 pages. |
| Tooeasytoforget, “iPhone—Demo of SummerBoard & Its Features”, 5:05 minutes video, available at <http://www.youtube.com/watch?v=CJOb3ftQLac>, uploaded on Sep. 24, 2007, 2 pages. |
| tuaw.com, “1.1.1 iPhone Multi page Springboard Hack”, Available at <http://www.tuaw.com/2007110/09/l-1-l-iohone-multioaoe-sorinQ″board-hack/>, Oct. 9, 2007, 5 pages. |
| tuaw.com, “Springboard Scrolling”, mid-scroll, Available at:<http://www.tuaw.com/photos/springboard-scrolling/431348/>, Oct. 9, 2007, 3 pages. |
| tuaw.com, “Springboard Scrolling”, mostly unpopulated page, Available at: <http://www.tuaw.com/photos/springboard-scrolling/431349/>, Oct. 9, 2007, 3 pages. |
| tuaw.com, “Springboard Scrolling”, new page dot feature, Available at: <http://www.tuaw.com/gallerv/soringboard-scrolling/431347/>, Oct. 9, 2007, 3 pages. |
| tuaw.com, “Tuaw Hack: Mess with Your iPhone Settings”, Available at: http://www/tuaw.com/tag/SpringBoard/, Dec. 18, 2007, 1 page. |
| Turetta, Jonathan, “Steve Jobs iPhone 2007 Presentation (HD)”, Retrieved from the Internet: URL: https://www.youtube.com/watch?v=vN4U5FqrOdQ&feature=youtu.be, May 13, 2013, 2 pages. |
| Versiontracker, “Photogather-7.2.6. Hi-res Image Viewer & Editor for Palm”, Available online at <http://www.versiontracker.com/dyn/moreinfo/palm/4624>, retrieved on Jun. 12, 2006, 2006, 5 pages. |
| Vrba J., “iPhone Customizations and Applications”, Ezine Articles, Availabe at: <http://ezinearticles.com/?iPhone-Customizations-and-Applications&id=815807&opt=print>, Nov. 2007, 2 pages. |
| Warabino et al., “Video Transcoding Proxy for 3Gwireless Mobile Internet Access”, IEEE Communications Magazine, vol. 38, No. 10, Oct. 2000, pp. 66-71. |
| Wave Technologies International Inc., “Certified Internet Webmaster Foundations Study Guide”, A Thomson Learning Company, CIWF-SGMN-0101A, copyright 1988-2000, 88 pages. |
| Weblogs, “An Overview of WebCore”, Chapter 2, WebCore Documentation, available at <http:/lweblogs.mozillazine.org/hyatt/WebCore/chapter2.html>, 2006, 3 pages. |
| Weblogs, “Downloading and Building WebCore”, Chapter 1, WebCore Documentation, available at <http://weblogs.mozillazine.org/hyatt/WebCore/chapter1.html>, 2006, 2 pages. |
| webmasterworld.com, “Page Zooming with IE-Hidden Feature!”, Available at <http://www.webmasterworld.com/forum83/4179.htm>, Jul. 2004, 7 pages. |
| Widgipedia, “I Need a Blog and a Forum Please?”, available at: <http://www.widgipedia.com/widgets/details/adni18/hyalo-weather_27.html>, retrieved on Oct. 19, 2006, 2 pages. |
| Wikipedia, “Comparison of Layout Engines”, The free encyclopedia, available at <http://en.wikipedia.org/wiki/Comparison_of_layout_engines>, 2006, 3 pages. |
| Wikipedia, “History of YouTube”, The Free Encyclopedia, available at <http://en.wikipedia.org/wiki/History_of_YouTube>, retrieved on Mar. 15, 2011, 4 pages. |
| Wikipedia, “KDE”, The free encyclopedia, available at <http://en.wikipedia.org/wiki/KDE>, 2006, 9 pages. |
| Wikipedia, “KHTML”, The free encyclopedia, available at <http://en.wikipedia.org/wiki/KHTML>, 2006, 3 pages. |
| Wikipedia, “List of Layout Engines”, The Free Encyclopedia, available at <http://en.wikipedia.org/wiki/List_of_layout_engines>, 2006, 1 page. |
| Wildarya, “iDesksoft Desktop Icon Toy v2.9”, Available at: <http://www.dl4all.com/2007/10/16/idesksoft_desktoo_icon_toy_v2.9.html>, Oct. 16, 2007, 4 pages. |
| Williams, Martyn, “LG's Cell Phone Can Pause Live TV”, PC World, Oct. 11, 2005, 2 pages. |
| Wobbrock et al., “WebThumb: Interaction Techniques for Small-Screen Browsers”, UIST'02, Paris France, Oct. 27-30, 2002, pp. 205-208. |
| Wright Ben, “Palm OS PDA Application Mini-Reviews”, Online Available at <http://library.indstate.edu/newsletter/feb04/palmmini.htm>, Feb. 3, 2015, 11 pages. |
| Xiao et al., “Slicing*-Tree Based Web Page Transformation for Small Displays”, International Conference on Information and Knowledge Management, Oct. 31-Nov. 5, 2005, 2 pages. |
| Xie et al., “Efficient Browsing of Web Search Results on Mobile Devices Based on Block Importance Model”, Microsoft Research Asia, 2005, 10 pages. |
| Yin et al., “Using Link Analysis to Improve Layout on Mobile Devices”, Proceedings of the 13th international conference on World Wide Web, available at <http://www.iw3c2.org/WWW2004/docs/1p338.pdf>, May 17-22, 2004, pp. 338-344. |
| Youtube, “Broadcast Yourself”, Available at <www.youtube.com>, Nov. 1, 2005, 2 pages. |
| Youtube, “Broadcasting Ourselves”, The Official Youtube blog Available at <http://youtube-global.blogspot.in/2005_11_01_archive.html>, Nov. 15, 2005, 5 pages. |
| Zhang et al., “An Ergonomics Study of Menu-Operation on Mobile Phone Interface”, In Proceedings of the workshop on Intelligent Information Technology Application, 2007, pp. 247-251. |
| Zytronic, “Touchscreen User Manual Zytronic X-Y Controller (Serial and USB)”, XP007916436, Nov. 17, 2006, pp. 1-51. |
| Non-Final Office Action received for U.S. Appl. No. 17/949,859, mailed on May 10, 2023, 7 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230082382 A1 | Mar 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61019841 | Jan 2008 | US | |
| 61010208 | Jan 2008 | US | |
| 60937993 | Jun 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16987255 | Aug 2020 | US |
| Child | 17950934 | US | |
| Parent | 15493672 | Apr 2017 | US |
| Child | 16987255 | US | |
| Parent | 12217029 | Jun 2008 | US |
| Child | 15493672 | US |
