Abstract: A controller can be used with a computing device to select and/or interact with content using user input devices on the controller. The content can be locally-stored on the computing device and/or streamed from a remote device. In one embodiment, a contextually-aware platform service switcher is provided. In another embodiment, a system and method for automatic content capability detection are provided. In yet another embodiment, a system and method for rich content browsing multitasking on device operating systems with multitasking limitations are provided. These embodiments can be used alone or in combination. Other embodiments are provided.

Abstract: Some cloud gaming and other remote game environments require a user to wait in a queue before playing a game. During this time, the user may be concerned that they will lose their place in the queue if they close the window displaying the game to do another task on the computing device. If the user decides to do something away from the computing device while waiting in the queue, it is possible that the user will be unaware when they progress out of the queue and miss their opportunity to play the game. This can be a frustrating experience for the user. The embodiments presented herein can be used to address this situation.

Abstract: A handheld game controller with a second screen experience is presented. Various embodiments described herein relate to solutions to the problems of: hardware limited controller-specific inputs and outputs, a lack of built-in Bluetooth or Wi-Fi in mobile game controllers, difficulty connecting to TV streaming devices that do not support Bluetooth or Wi-Fi, friction and discoverability around pairing, and a lack of access to game companion app integration. Other embodiments are provided, and each of the embodiments can be used alone or in combination.

Abstract: A gaming device that includes a handheld controller with a handle and a mechanism for connecting the handheld controller to a mobile device. The mechanism includes a substantially rigid arm and a connector. The arm is housed within the handle and is configured to pivot about a pivot point within the handle. The connector is attached to the arm at the end opposite the pivot point and is structured to physically and electrically pair the mobile device and the handheld controller. The connector is structured to pivot about the pivot point with the arm.

Abstract: Space inside a handheld game controller can be limited, making it difficult to add a new or different user input device without increasing the overall size of the handheld game controller. The embodiments provided herein describe user input devices configured for use in such a space-constrained environment. In one embodiment, a cantilevered button is used when a component inside the handheld game controller is positioned in a path between the button and a switch. In another embodiment, an opening is made in a circuit board inside the handheld game controller to allow a joystick assembly to pass through the circuit board. Other embodiments are disclosed, and each embodiment can be used alone or in combination with other embodiments.

Abstract: In one embodiment, a game controller is provided with an opening therein for an aesthetic and/or functional purpose (e.g., to accept a removable wireless charger). In another embodiment, a game controller is provided without an opening but is capable of passing a charge and/or is capable of attaching with a removable charger. In yet another embodiment, a game controller is provided with a magnet for attaching with a mobile device and/or with a removable magnetic charger. In another embodiments, a game controller is disclosed that is sandwiched between a mobile device and a removable charger. Other embodiments are disclosed.

Abstract: A universal mobile game controller is provided that can interoperate with multiple computing device operating systems (e.g., Android and iOS) in an automatic way through a common connector (e.g., USB-C). With these embodiments, instead of building a separate mobile game controller for each operating system, a single mobile game controller can be used for all operating systems. These embodiments can also enable communication with an application running within the computing device operating system. Other embodiments are provided.

Abstract: A universal mobile game controller is provided that can interoperate with multiple computing device operating systems (e.g., Android and iOS) in an automatic way through a common connector (e.g., USB-C). With these embodiments, instead of building a separate mobile game controller for each operating system, a single mobile game controller can be used for all operating systems. These embodiments can also enable communication with an application running within the computing device operating system. Other embodiments are provided.

Abstract: A controller can be used with a computing device to select and/or interact with content using user input devices on the controller. The content can be locally-stored on the computing device and/or streamed from a remote device. In one embodiment, a contextually-aware platform service switcher is provided. In another embodiment, a system and method for automatic content capability detection are provided. In yet another embodiment, a system and method for rich content browsing multitasking on device operating systems with multitasking limitations are provided. These embodiments can be used alone or in combination. Other embodiments are provided.

Abstract: A game controller can provide input to a video game (e.g., to control an object or character in the video game) and, optionally, to interact with a graphical user interface (e.g., to select the video game and/or perform other functions). The game controller can be connected with a mobile computing device, such as a mobile phone, and the game can be played locally on the mobile computing device or remotely via the mobile computing device. In one embodiment discussed herein, a platform-customized mobile game controller is provided. In another embodiment discussed herein, a mobile game controller and method are provided for connecting to a wireless audio device.

Abstract: A gaming device that includes a handheld controller having a handle and a depressible button on the handle configured to receive user input. The depressible button includes a first marking layer including a first indicia, a first light source configured to illuminate the first indicia in the first marking layer, a second marking layer stacked with the first marking layer and including a second indicia, and a second light source configured to illuminate the second indicia in the second marking layer.

Abstract: A handheld gaming device in which configurations allow for default-open, force-close systems and separate the user's insertion of the mobile device and closure of the handles around the mobile device.

Abstract: A universal mobile game controller is provided that can interoperate with multiple computing device operating systems (e.g., Android and iOS) in an automatic way through a common connector (e.g., USB-C). With these embodiments, instead of building a separate mobile game controller for each operating system, a single mobile game controller can be used for all operating systems. These embodiments can also enable communication with an application running within the computing device operating system. Other embodiments are provided.

Abstract: A game controller can provide input to a video game played on a mobile computing device. Some games require a touch input on the touch screen of a mobile computing device, but a game controller may not have its own touch screen to receive and provide the required touch input. The game controller can be manually configured by a user of the game controller to convert an actuation of a control surface (e.g., a button, joystick, etc.) of the game controller to a touch screen input.

Abstract: A game controller can provide input to a video game played on a mobile computing device. Some games require a touch input on the touch screen of a mobile computing device, but a game controller may not have its own touch screen to receive and provide the required touch input. The game controller can be manually configured by a user of the game controller to convert an actuation of a control surface (e.g., a button, joystick, etc.) of the game controller to a touch screen input. However, this can be a very cumbersome and frustrating process for the user and has several limitations. The embodiments described herein can overcome this problem by providing a map that is automatically configured, without user configuration, to convert an input representing an actuation of the control surface into a touch screen input.

Abstract: A gaming device that includes a handheld controller having a handle and a depressible button on the handle configured to receive user input. The depressible button includes a first marking layer including a first indicia, a first light source configured to illuminate the first indicia in the first marking layer, a second marking layer stacked with the first marking layer and including a second indicia, and a second light source configured to illuminate the second indicia in the second marking layer.

Abstract: A game controller for a mobile device that includes a first handle, a first bumper, and a first switch. The first handle is configured to contact and support a mobile device. The first bumper is coupled to the first handle. The first bumper is configured to accept touch inputs. The first bumper includes a pivot rod at a first end of the first bumper that is configured to engage a track slot of the first handle. The pivot rod is configured to rotate within the track slot and to translate within the track slot. The first bumper further includes a plunger at a first-span distance from the pivot rod. The first switch is within the first handle and is configured to be activated by touch inputs to the first bumper. The plunger of the first bumper is configured to contact and impart a force to the first switch.

Abstract: A game controller for a mobile device, the game controller including a first handle, a bridge, and an acoustic waveguide. The first handle is configured to contact and support a mobile device and includes a user-accessible, first hardware interface on a main body portion of the first handle that is configured to accept touch inputs. The bridge extends from the main body portion of the first handle. The acoustic waveguide is at a juncture of the first handle and the bridge. The acoustic waveguide is configured to redirect sound emitted from the mobile device toward at least one of a front side of the game controller, a top side of the game controller, and a bottom side of the game controller.