Mobile device controller system and method for interacting with client applications

Abstract

This provides a mobile device controller system and method for interacting with client applications. [Solution] The mobile device controller 100 comprises a first controller module 105 that engages with a first side 310 of the mobile device 305, a second controller module 110 that engages with a second side 315, a bridge, and at least one processor. The processor transmits one or more mobile device controller characteristics from the mobile device controller 100 to the mobile device 305. The client application of the mobile device 305 is modified based on the mobile device controller characteristics and interacts with the user using a graphical user interface.

Description

Background Art

[0001] Cross - reference to Related Applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 240,443, filed Sep. 3, 2021, and U.S. Provisional Patent Application No. 63 / 364,974, filed May 19, 2022, the entire contents of each of which are incorporated herein by reference.

[0002] Background Art The mobile game field is crowded, and finding opportunities for new breakout content is a challenge even for the newest developers. Despite content competition and the flexibility provided by touch interfaces, mobile games still lack significant representation from all genres of games with a proven track record, such as retro and casual arcades. Retro and casual arcade games and game dynamics were originally designed to be played with physical inputs. Due to the need to add additional hardware, the fragmentation in mobile handsets and the lack of vertical integration between controller manufacturers and content developers for games in this genre remain undervalued in the mobile field.

Summary of the Invention

Means for Solving the Problems

[0003] Summary A mobile device controller system and method for interacting with a client application are provided. Related systems, methods, devices, technologies, and articles are also described.

[0004] In one embodiment, a first controller module of the mobile device controller can engage with a first side of the user's mobile device. A second controller module of the mobile device controller can engage with a second side of the mobile device. One or more mobile device controller characteristics associated with the characteristics of the mobile device controller can be transmitted from the mobile device controller to the mobile device. A client application on the mobile device can be modified by the first data processor based on one or more mobile device controller characteristics. The modified client application can be provided to the user of the mobile device by the first data processor, and the user can interact with the modified client application using the mobile device controller.

[0005] One or more of the following features can be included in any viable combination. For example, communication between the mobile device controller and the mobile device can be initiated. For example, initiating communication may include pairing the mobile device controller with the mobile device via a wireless communication protocol. For example, the first and second sides may be located on opposing sides of the mobile device, the first controller module may be elastically coupled to the second controller module, and the mobile device controller may be in contact with the mobile device in a form-fitting configuration. For example, engaging the first controller module with the mobile device may include sliding the first controller module away from the second controller module. For example, the mobile device controller may include a pair of flaps configured to hold the mobile device when the first side of the mobile device is engaged by the first controller module and when the second side of the mobile device is engaged by the second controller module. For example, the mobile device may be disengaged from the first and second controller modules, and the first controller module may be slid toward the second controller module. For example, a mobile device can be oriented vertically when a first side of the mobile device is engaged by a first controller module and a second side of the mobile device is engaged by a second controller module. For example, at least one of the first and second controller modules may include at least one button located on it and configured to receive user input for controlling a client application. For example, at least one of the first and second controller modules may include a directional pad button located on it and configured to receive user input for controlling a client application.

[0006] In another embodiment, a mobile device controller is provided, which may include a first controller module configured to engage with a first side of a mobile device, a second controller module configured to engage with a second side of the mobile device, the second side being opposite to the first side, and a deployable bridge placed between the first and second controller modules. At least one of the first or second controller modules may include at least one processor and memory for storing instructions, which, when executed by the at least one processor, cause the at least one processor to perform an operation that includes transmitting from the mobile device controller to the mobile device one or more mobile device controller characteristics associated with the characteristics of the mobile device controller, a client application on the mobile device being modified based on the one or more mobile device controller characteristics, the modified client application being provided to a user in the mobile device, and the user interacting with the modified client application using the mobile device controller.

[0007] One or more of the following features can be included in any executable combination. For example, a first controller module may be configured to receive a first user input for controlling a client application, and a second controller module may be configured to receive a second user input for controlling a client application. For example, the first controller module may include a first hinge structure that extends from the first controller module and is configured to engage with a first side of a mobile device when the first controller module extends laterally away from the second controller module. For example, the second controller module may include a second hinge structure that extends from the second controller module and is configured to engage with a second side of a mobile device when the second controller module extends laterally away from the first controller module. For example, the deployable bridge may include a first elastic structure and a second elastic structure for adjusting the mobile device controller to fit mobile devices of different sizes, the first elastic structure may be coupled between a first controller module and a first end of the deployable bridge, and the second elastic structure may be coupled between a second controller module and a second end of the deployable bridge. For example, the operation may further include initiating communication between the mobile device controller and a client application running on the mobile device. For example, initiating communication may include pairing the mobile device controller with the mobile device via a wireless communication protocol. For example, the mobile device may be oriented vertically when a first side of the mobile device is engaged by the first controller module and a second side of the mobile device is engaged by the second controller module.For example, at least one of the first controller module and the second controller module may include at least one button located on it and configured to receive user input for controlling a client application. For example, at least one of the first controller module and the second controller module may include a directional pad button located on it and configured to receive user input for controlling a client application. The present invention provides, for example, the following items: (Item 1) Engaging the first controller module of the mobile device controller with the first side of the user's mobile device, Engaging the second controller module of the mobile device controller with the second side of the mobile device, The mobile device controller transmits one or more mobile device controller characteristics to the mobile device, wherein the one or more mobile device controller characteristics are associated with the characteristics of the mobile device controller. The first data processor modifies the client application on the mobile device based on the characteristics of one or more mobile device controllers, The first data processor provides the modified client application to the user in the mobile device, the user interacting with the modified client application using the mobile device controller. Methods that include... (Item 2) The method according to item 1, further comprising initiating communication between the mobile device controller and the mobile device. (Item 3) The method of item 2, wherein the commencement includes pairing the mobile device controller with the mobile device via a wireless communication protocol. (Item 4) The method according to item 1, wherein the first and second sides are located on opposing sides of the mobile device, the first controller module is elastically coupled to the second controller module, and the mobile device controller contacts the mobile device in a form-fitting configuration. (Item 5) The method according to item 1, wherein engaging the first controller module with the mobile device includes sliding the first controller module away from the second controller module. (Item 6) The method according to item 1, wherein the mobile device controller includes a pair of flaps configured to hold the mobile device when the first side of the mobile device is engaged by the first controller module and when the second side of the mobile device is engaged by the second controller module. (Item 7) Disengaging the mobile device from the first controller module and the second controller module, The first controller module is slid toward the second controller module. The method described in item 1, further including the method described in item 1. (Item 8) The method according to item 1, wherein the mobile device is positioned vertically when the first side of the mobile device is engaged by the first controller module and the second side of the mobile device is engaged by the second controller module. (Item 9) The method according to item 1, wherein at least one of the first controller module and the second controller module includes at least one button located thereon, the at least one button being configured to receive user input for controlling the client application. (Item 10) The method according to item 1, wherein at least one of the first controller module and the second controller module includes a directional pad button located thereon, the directional pad button being configured to receive user input for controlling the client application. (Item 11) A mobile device controller, A first controller module configured to engage with a first side of a mobile device, A second controller module configured to engage with a second side of the mobile device, wherein the second side is opposite to the first side and is connected to the second controller module. A deployable bridge placed between the first controller module and the second controller module, wherein at least one of the first controller module or the second controller module includes at least one processor and memory for storing instructions, and when an instruction is executed by the at least one processor, the at least one processor is sent to the at least one processor. The mobile device controller transmits one or more mobile device controller characteristics to the mobile device, wherein the one or more mobile device controller characteristics are associated with the characteristics of the mobile device controller, a client application on the mobile device is modified based on the one or more mobile device controller characteristics, the modified client application is provided to the user on the mobile device, and the user interacts with the modified client application using the mobile device controller. A deployable bridge that enables the execution of operations including A mobile device controller equipped with the following features. (Item 12) The mobile device controller according to item 11, wherein the first controller module is configured to receive a first user input for controlling the client application, and the second controller module is configured to receive a second user input for controlling the client application. (Item 13) The mobile device controller according to item 11, wherein the first controller module includes a first hinge structure, the first hinge structure extending from the first controller module and configured to engage with the first side of the mobile device when the first controller module extends laterally away from the second controller module. (Item 14) The mobile device controller according to item 13, wherein the second controller module includes a second hinge structure, the second hinge structure extending from the second controller module and configured to engage with a second side of the mobile device when the second controller module extends laterally away from the first controller module. (Item 15) The mobile device controller according to item 11, wherein the deployable bridge includes a first elastic structure and a second elastic structure for adjusting the mobile device controller to fit mobile devices of different sizes, the first elastic structure being coupled between the first controller module and the first end of the deployable bridge, and the second elastic structure being coupled between the second controller module and the second end of the deployable bridge. (Item 16) The aforementioned operation is, To initiate communication between the mobile device controller and the client application running on the mobile device. The mobile device controllers listed in item 11, which also include the mobile device controllers listed in item 11. (Item 17) The starting as described in item 16 of the mobile device controller includes pairing the mobile device controller with the mobile device via a wireless communication protocol. (Item 18) The mobile device is placed vertically when the first side of the mobile device is engaged by the first controller module and when the second side of the mobile device is engaged by the second controller module, as described in item 11 of the mobile device controller. (Item 19) At least one of the first controller module and the second controller module includes at least one button disposed thereon, and the at least one button is configured to receive user input for controlling the client application, as described in item 11 of the mobile device controller. (Item 20) At least one of the first controller module and the second controller module includes a direction pad button disposed thereon, and the direction pad button is configured to receive user input for controlling the client application, as described in item 11 of the mobile device controller. Brief Description of the Drawings

[0008] Brief Description of the Drawings The above embodiments will be more fully understood from the following detailed description in conjunction with the accompanying drawings. The drawings are not drawn to scale. For clarity, not all components are labeled in all the drawings.

[0009] [Figure 1] It is a diagram of a mobile device controller in an expanded configuration for interacting with a client application.

[0010] [Figure 2]This is a diagram of a mobile device controller in a folded configuration.

[0011] [Figure 3] This is a diagram of a mobile device controller configured to engage with a mobile device.

[0012] [Figure 4] This block diagram shows an exemplary system for interacting with one or more client applications.

[0013] [Figure 5] This is a diagram of an alternative mobile device controller in a deployed configuration for interacting with a client application.

[0014] [Figure 6] This is a diagram of an alternative mobile device controller in a partially closed or folded configuration.

[0015] [Figure 7] This is a diagram of an alternative mobile device controller configuration engaged with a vertically oriented mobile device.

[0016] [Figure 8] This is a diagram of an alternative mobile device controller in a configuration that engages with a landscape-oriented mobile device.

[0017] [Figure 9A] This is a side view of an alternative mobile device controller in a closed or folded configuration for interacting with client applications.

[0018] [Figure 9B] Figure 9A is a front, upper right perspective view of the mobile device controller.

[0019] [Figure 9C]Figure 9A is a front, upper left perspective view of the mobile device controller.

[0020] [Figure 9D] Figure 9A is a perspective view of the upper left rear of the mobile device controller.

[0021] [Figure 9E] Figure 9A is a perspective view of the upper right rear of the mobile device controller.

[0022] [Figure 9F] Figure 9A is a perspective view of the lower right rear of the mobile device controller.

[0023] [Figure 9G] Figure 9A is a perspective view of the lower left rear of the mobile device controller.

[0024] [Figure 9H] Figure 9A is a front view of the mobile device controller, showing the lower right corner.

[0025] [Figure 9I] Figure 9A is a front, lower left perspective view of the mobile device controller.

[0026] [Figure 9J] Figure 9A is a top view of the mobile device controller.

[0027] [Figure 9K] Figure 9A is a bottom view of the mobile device controller.

[0028] [Figure 9L] Figure 9A is a left perspective view of the mobile device controller.

[0029] [Figure 9M] Figure 9A is a front perspective view of the mobile device controller.

[0030] [Figure 9N] Figure 9A is a right-hand perspective view of the mobile device controller.

[0031] [Figure 9O] Figure 9A is a rear perspective view of the mobile device controller.

[0032] [Figure 10] This is a diagram of an alternative mobile device controller with a partially open configuration.

[0033] [Figure 11A] This is a diagram of an alternative mobile device controller in a fully deployed configuration.

[0034] [Figure 11B] Figure 11A is a front, upper right perspective view of the mobile device controller.

[0035] [Figure 11C] Figure 11A is a front, upper left perspective view of the mobile device controller.

[0036] [Figure 11D] Figure 11A is a perspective view of the upper left rear of the mobile device controller.

[0037] [Figure 11E] Figure 11A is a rear upper right perspective view of the mobile device controller.

[0038] [Figure 11F] Figure 11A is a perspective view of the lower right rear of the mobile device controller.

[0039] [Figure 11G] Figure 11A is a perspective view of the lower left rear of the mobile device controller.

[0040] [Figure 11H]Figure 11A is a front, lower right perspective view of the mobile device controller.

[0041] [Figure 11I] Figure 11A is a front, lower left perspective view of the mobile device controller.

[0042] [Figure 11J] Figure 11A is a top view of the mobile device controller.

[0043] [Figure 11K] Figure 11A is a bottom view of the mobile device controller.

[0044] [Figure 11L] Figure 11A is a left side view of the mobile device controller.

[0045] [Figure 11M] Figure 11A is a front view of the mobile device controller.

[0046] [Figure 11N] Figure 11A is a right side view of the mobile device controller.

[0047] [Figure 11O] Figure 11A is a rear view of the mobile device controller.

[0048] [Figure 11P] Figure 11A is a front, upper right perspective view of the mobile device controller.

[0049] [Figure 11Q] Figure 11A is a front, upper left perspective view of the mobile device controller.

[0050] [Figure 11R] Figure 11A is a perspective view of the upper left rear of the mobile device controller.

[0051] [Figure 11S] Figure 11A is a rear upper right perspective view of the mobile device controller.

[0052] [Figure 11T] Figure 11A is a perspective view of the lower right rear of the mobile device controller.

[0053] [Figure 11U] Figure 11A is a perspective view of the lower left rear of the mobile device controller.

[0054] [Figure 11V] Figure 11A is a front, lower right perspective view of the mobile device controller.

[0055] [Figure 11W] Figure 11A is a front, lower left perspective view of the mobile device controller.

[0056] [Figure 11X] Figure 11A is a top view of the mobile device controller.

[0057] [Figure 11Y] Figure 11A is a bottom view of the mobile device controller.

[0058] [Figure 11Z] Figure 11A is a left side view of the mobile device controller.

[0059] [Figure 11AA] Figure 11A is a front view of the mobile device controller.

[0060] [Figure 11AB] Figure 11A is a right side view of the mobile device controller.

[0061] [Figure 11AC]Figure 11A is a rear view of the mobile device controller.

[0062] [Figure 12] This is a side view of an alternative mobile device controller in a closed or folded configuration for interacting with client applications.

[0063] [Figure 13] This is a diagram of an alternative mobile device controller with a partially extended configuration.

[0064] [Figure 14] This is a diagram of an alternative mobile device controller with a fully extended configuration.

[0065] [Figure 15] This is a diagram of a posable directional pad that uses a pointing stick in a keyboard layout.

[0066] [Figure 16] This is a diagram of a movable input surface for a keypad layout.

[0067] [Figure 17A] This is a diagram of an array of contact point fingers for a directional pad. [Figure 17B] This is a diagram of an array of contact point fingers for a directional pad.

[0068] [Figure 18] This is a side view of the contact pad for the directional pad.

[0069] [Figure 19] This flowchart shows an exemplary method for interacting with a client application.

[0070] [Figure 20]This is a block diagram of an exemplary computing device according to this embodiment that can perform one or more of the operations described herein. [Modes for carrying out the invention]

[0071] Detailed explanation Herein, in order to provide an overall understanding of the structure, function, manufacturing and use principles of the devices and methods disclosed herein, certain exemplary embodiments are described. One or more examples of these embodiments are shown in the accompanying drawings. Those skilled in the art will understand that the devices and methods specifically described herein and shown in the accompanying drawings are non-limiting exemplary embodiments, and that the scope of the invention is defined solely by the claims. Features illustrated or described in relation to one exemplary embodiment may be combined with features of other embodiments. Such modifications and variations are intended to fall within the scope of the invention. Furthermore, in this disclosure, components with similar names in embodiments generally have similar features, and therefore, within a particular embodiment, each feature of each component with a similar name is not necessarily fully described.

[0072] The present invention relates to a mobile device controller system and method for interacting with a client application, and includes decorative designs for a mobile device controller as shown in and described in relation to the drawings. The mobile device controller can form-fit onto a mobile device and provide physical inputs that enable a user to control, interact with, or otherwise engage with a client application running on the mobile device. The mobile device controller may include left and right controller modules that are divided to be placed on either side of the mobile device. For maximum portability, the two halves of the mobile device controller may be connected by an adjustable bridge that can accommodate different sizes and orientations of the mobile device while folding when not in use. In some embodiments of the present invention, the center of the bridge between the two controller modules may be an inductive charging array having magnetic alignment features, including, for example, a plurality of oriented magnetic arrays arranged in a circle. The adjustable bridge mechanism can be deployed and retracted from (or nearly from) the center or center of the mobile device controller so that the inductive charging array of the mobile device controller can be kept substantially centered on the bridge. Centering actions may be used to maintain alignment between the mobile device controller and the mobile device, regardless of model and orientation. The mobile device controller may support any suitable button layout. For example, the button layout could be similar to a game console, with two analog sticks, a D-pad, four right-side input buttons, four shoulder buttons, and two triggers. Mobile device controllers can also include menus, functions, and rear paddle inputs, but other combinations of buttons, triggers, paddles, and joysticks are also possible.

[0073] In some embodiments of the present invention, an inductive charging array having magnetic alignment features can address several problems found in conventional mobile device controller proposals. For example, an advantage of the present invention may be the ability to quickly and reliably attach and detach a mobile device to a mobile device controller with one hand using an inductive charging array connection. The magnetic centering action supported by the magnetic alignment features of the inductive charging array can enhance the ability to easily rotate the mobile device to either portrait or landscape mode when attached to the mobile device controller. The complexity of the holding mechanism can be reduced by not having to rely on mechanical connections to hold the mobile device to the mobile device controller, as this allows for accommodating mobile devices of various sizes without the need for continuous adjustments over various dimensions. Such advantages also allow for a much larger range of motion between the widest extension (to accommodate the largest mobile devices in landscape mode) and a fully folded state, resulting in a more compact form when not in use.

[0074] In some embodiments of the present invention, the advantages of incorporating an inductive charging array into a mobile device controller can extend to the setup and playability of the mobile device controller. For example, using Near Field Communication (NFC) or other similar circuits incorporated into the inductive charging array, pairing of the mobile device controller can be automatically initiated via an appropriate wireless communication protocol when the mobile device is physically placed inside the mobile device controller. Such features can eliminate the need for the user to manually initiate pairing. In some embodiments of the present invention, power can be supplied to the mobile device controller using reverse wireless charging to reduce complexity and allow the user to maintain battery charge. For example, the mobile device controller may be configured to plug into a power source, and the wireless charging connection can be reversed to power both the mobile device controller and the mobile device controller simultaneously to charge the mobile device for a prolonged interaction or engagement session with a client application(s). Alternatively, since the mobile device controller is not electrically connected to the mobile device, the mobile device can be powered directly from an external charger plugged into the mobile device, such as when the mobile device controller is in portrait mode.

[0075] According to embodiments of the present invention, a mobile device controller may be designed to address the location and method of holding a mobile phone during gameplay. While some controllers, particularly those repurposed from game consoles for mobile use, may leave it to the user to find ways to enhance the mobile device while playing in an un-ideal manner, most propose a method of holding the mobile phone with the controller. Generally, there are two main solutions for holding a phone: form-fitting and stand-under. Form-fitting refers to a controller that is split in half, usually in a horizontal format, with the mobile phone positioned between the two halves. The user then places one hand on each side while playing. Form-fitting controllers are large, support only specific mobile phone models, are expensive to manufacture, and may offer compromised ergonomics compared to console-type controllers. Controllers in this category are, in most cases, directly powered by the phone (e.g., via USB, Lightning connector, or other similar connection ports). Stand-under controllers may be similar to those proposed by game console manufacturers, having a clamp mounted on top to hold the mobile phone in place. Most stand-under controllers can be wirelessly connected, while others may propose a direct wired connection to the mobile phone. Such a configuration could also mean that the stand-under controller could include its own battery power, requiring user charging. Because they model themselves after game console-style controllers, stand-under controllers can be larger and not designed for portability. In both form-fitting and standalone controllers, mechanically holding the phone to the controller may require the user to engage in a multi-step process to attach and detach the controller. The added bulk of the controller could mean that using the mobile device vertically (or for other tasks besides gaming) is not ideal.Wireless controllers also have to be paired upon first use and manually turned on and off by the user before and after subsequent game sessions. Embodiments of the present invention can overcome such drawbacks.

[0076] For illustrative purposes only, and not limiting, this disclosure refers to mobile digital games as exemplary client applications to illustrate various aspects of the present invention. However, the present invention may be used in and with any suitable type of client application (e.g., a mobile application, or any other suitable type of client application that can run on a mobile device) in which a user can interact or otherwise engage via physical input. Furthermore, for illustrative purposes only, and not limiting, this disclosure refers to mobile phones as exemplary mobile devices to illustrate various aspects of the present invention. However, the present invention may be used in and with any suitable type of mobile device, such as a smartphone or a tablet computer.

[0077] Figure 1 shows a mobile device controller 100 in an open or deployed configuration for interacting with a client application. The mobile device controller 100 may include a first controller module 105 (e.g., left controller) and a second controller module 110 (e.g., right controller). The first controller module 105 and the second controller module 110 may be divided so that they can be placed on opposite sides of the mobile device (e.g., left and right or top and bottom, but not front and back). Although shown as having approximately equivalent size, the first controller module 105 and the second controller module 110 may be similar or different in size depending on the desired configuration. The first controller module 105 may include a first button layout 115. For example, the first button layout 115 may include any appropriate number of arrow keys (e.g., up, down, left, right, etc.) in any appropriate configuration. The second controller module 110 may include a second button layout 120. For example, the second button layout 120 can include any appropriate number of buttons (e.g., buttons A, B, X, Y, etc.) in any appropriate configuration. The first controller module 105 and the second controller module 110 can each include or support any appropriate button layout. For example, the button layout could be similar to that of a game console, having two analog sticks, a D-pad, four right-side input buttons, four shoulder buttons, and two triggers. The first controller module 105 and the second controller module 110 can additionally or alternatively include menus, functions, and rear paddle inputs, although other combinations of buttons, triggers, paddles, joysticks, etc., are also possible.

[0078] In an embodiment, the mobile device controller 100 may include an adjustable bridge structure 125 that can be located between and within a first controller module 105 and a second controller module 110. The adjustable bridge structure 125 may include a front surface 130 that can engage with and make full contact with the back surface of the mobile device. The first controller module 105 may be coupled to the adjustable bridge structure 125 via a first pair of guide rails 135. The second controller module 115 may be coupled to the adjustable bridge structure 125 via a second pair of guide rails 140. Each of the first pair of guide rails 135 and the second pair of guide rails 140 may be rigid, semi-rigid, or flexible, depending on the desired configuration. The first pair of guide rails 135 may be permanently and fixedly attached to the first controller module 105 via a first anchor 145 that can form a structural component of the first controller module 105. The second pair of guide rails 140 can be permanently and securely attached to the second controller module 110 via second anchors 150 that can form structural components of the second controller module 110. The first pair of guide rails 135 and the second pair of guide rails 140 can be coupled to the adjustable bridge structure 125 using a suitable elastic structure (e.g., a spring) that can be present within the adjustable bridge structure 125. The elastic structure within the adjustable bridge structure 125 can allow the first controller module 105 and the second controller module 110 to be pulled apart laterally or expanded, wrapped around the back of the mobile device, and then contracted to engage with the opposing side of the mobile device in a form-fitting configuration for a secure hold. In such a configuration, the adjustable bridge structure 125 can engage with the back of the mobile device. In this way, the mobile device controller 100 can be adapted to mobile devices of different sizes and orientations.

[0079] In some embodiments of the present invention, the first controller module 105 and the second controller module 110 can communicate with each other via a wired communication channel. For example, either or both of the first pair of guide rails 135 and the second pair of guide rails 140 can be rigid or semi-rigid hollow structures (e.g., tubes), and the wired communication channel can extend through and through either or both of the first pair of guide rails 135 and the second pair of guide rails 140, and through an adjustable bridge structure 125, enabling communication between the first controller module 105 and the second controller module 110. In alternative embodiments, the first controller module 105 and the second controller module 110 may include appropriate electronic components to support wireless communication with each other using any suitable wireless communication protocol (e.g., Bluetooth®, Wi-Fi, NFC, etc.). Either or both of the first controller module 105 and the second controller module 110 may include appropriate electronic components to support wireless communication with a mobile device using any suitable wireless communication protocol (e.g., Bluetooth®, Wi-Fi, NFC, etc.). For example, the first controller module 105 and the second controller module 110 can communicate wirelessly with each other and with a mobile device. In an alternative embodiment, if such rails are made of a solid or hollow structural material (e.g., a suitable metal or other conductive material) capable of carrying electrical signals, the first controller module 105 and the second controller module 110 can communicate with each other using either or both of the first pair of guide rails 135 and the second pair of guide rails 140 themselves.

[0080] Figure 2 shows the mobile device controller 100 in a closed or folded configuration. When in the folded configuration, the first pair of guide rails 135 and the second pair of guide rails 140 can be retracted and stationary or located within an adjustable bridge structure 125 so that the first anchor 145 of the first controller module 105 can contact or substantially contact the second anchor 150 of the second controller module 110. In one embodiment, the first pair of guide rails 135 can form an outer pair of guide rails, and the second pair of guide rails 140 can form an inner pair of guide rails. In such an embodiment, in the folded configuration, the (inner) second pair of guide rails 140 can be stationary between the (outer) first pair of guide rails 135 within the adjustable bridge structure 125. In an alternative embodiment, the first pair of guide rails 135 can form an inner pair of guide rails, and the second pair of guide rails 140 can form an outer pair of guide rails. In such an embodiment, in the folded configuration, the (inner) first pair of guide rails 135 can be resting between the (outer) second pair of guide rails 140 within the adjustable bridge structure 125. In the folded configuration, the mobile device controller 100 can be approximately credit card sized or in other compact configurations.

[0081] Figure 3 shows the mobile device controller 100 in a configuration engaged with the mobile device 305. In this embodiment, the mobile device controller 100 can form-fit onto the mobile device 305 and provide a physical input that allows the user to control, interact with, or otherwise engage with a client application running on the mobile device 305. As previously mentioned, the elastic structure within the adjustable bridge structure 125 can allow the first controller module 105 and the second controller module 110 to be pulled apart or expanded laterally, wrap around the back of the mobile device 305, and then contract to engage with the opposing side of the mobile device in a form-fitting configuration and hold securely. For example, the first anchor 145 can contact and engage securely with the first side 310 of the mobile device 305, and the second anchor 150 can contact and engage securely with the second side 315 of the mobile device 305. The mobile device 305 is shown in portrait orientation. When the mobile device is in landscape orientation, the first anchor 145 can contact and firmly engage with, for example, the third side 320 of the mobile device 305, while the second anchor 150 can contact and firmly engage with, for example, the fourth side 325 of the mobile device 305. In either configuration, the adjustable bridge structure 125 can engage with the back of the mobile device 305. In this way, the mobile device controller 100 can be adapted to mobile devices of different sizes and orientations.

[0082] In Figure 1, in some embodiments of the present invention, the first controller module 105 and the second controller module 110 may include appropriate electronic components to support at least wireless communication with a mobile device and control of a client application running on the mobile device via physical inputs provided by the user when interacting with the first button layout 115 and the second button layout 120. In such a configuration, either or both of the first controller module 105 and the second controller module 110 may include a battery component to power the mobile device controller 100. For example, if one of the first controller module 105 and the second controller module 110 includes a battery component, the controller module having the battery component may power the other controller module via a power communication channel that can extend through either or both of the first pair of guide rails 135 and the second pair of guide rails 140 and through an adjustable bridge structure 125. Additionally or alternatively, the adjustable bridge structure 125 may include appropriate electronic and / or power components to support some or all of such functions. For example, the adjustable bridge structure 125 may include either or both electronic and power components (e.g., a battery) to manage and power either or both of the first controller module 105 and the second controller module 110, and to control a client application running on a mobile device (e.g., via physical inputs provided by the user when interacting with the first button layout 115 and the second button layout 120).In such a configuration, the adjustable bridge structure 125 can manage and power the first controller module 105 and the second controller module 110 via combined or separate control and power communication channels that can pass through either or both of the first pair of guide rails 135 and the second pair of guide rails 140. In an alternative embodiment, if such rails are made of a material capable of carrying electrical signals (e.g., a suitable metal or other conductive material), control signals and / or power signals can be communicated using either or both of the first pair of guide rails 135 and the second pair of guide rails 140 themselves.

[0083] In some embodiments of the present invention, the adjustable bridge structure 125 may include an inductive charging array having magnetic alignment features or other suitable electronic circuits. The adjustable bridge structure 125 can be deployed and retracted from (or nearly from) the center or center of the mobile device controller 100 so that the inductive charging array of the mobile device controller 100 can be kept substantially centered within the mobile device controller 100. Such centering action may be used to maintain alignment between the mobile device controller 100 and the mobile device, regardless of model and orientation. For illustrative purposes only and not limiting, MagSafe® is a technology from Apple Inc. that provides a combination of magnetic mounting, wireless charging, and NFC. From a charging perspective, MagSafe can be used to address alignment issues encountered with wireless chargers that result in reduced efficiency due to misalignment of the mobile device to the charger. To properly secure and orient the accessory to the mobile device, MagSafe may employ an array of magnets (e.g., 18) arranged in a circle hidden beneath the surface of the mobile device, with additional line magnets that can be positioned perpendicularly out of the circle at the 6 o'clock position. Such a configuration can allow the accessory to align perfectly or nearly perfectly with the charging coil, securely holding the accessory in a specific orientation. MagSafe magnetic arrays allow relatively small magnets to attract accessories with similar configurations at close range, while a single large magnet tends to attract and affect other objects in undesirable ways at longer distances. For example, Apple employs NFC on its MagSafe accessories to help mobile devices identify what they are connected to, even if the object is passive. NFC can also offer advantages when pairing Bluetooth® devices. For example, instead of having to initiate pairing, select the device from the mobile device, and enter a PIN to pair the devices, the user can simply bring their mobile device close to initiate pairing.

[0084] In some embodiments of the present invention, additional configuration and playability features of the mobile device controller 100 can be supported by an inductive charging array integrated into an adjustable bridge structure 125. For example, during initial setup, the mobile device controller 100 can initiate pairing via an appropriate wireless communication protocol (e.g., Bluetooth®, Wi-Fi, etc.) using NFC, etc., which can be done automatically when a mobile device is physically placed inside the mobile device controller 100. Such features can eliminate the need for the user to manually initiate pairing. In one embodiment, the mobile device controller 100 can be powered using reverse radio charging to reduce complexity and maintain battery charge for use by the user with additional mobile devices. For example, the mobile device controller 100 can be configured to plug into a power source (e.g., via a port such as USB-C). For example, either or both of the first controller module 105 and the second controller module 110 may include appropriate ports to support charging from a power source. When plugged in, the wireless charging connection is reversed, allowing power to be supplied to the mobile device controller 100 while the mobile device is being charged for extended interaction or engagement sessions with client applications running on the mobile device. Alternatively, since the mobile device controller 100 is not physically connected to the mobile device's port, the mobile device can be powered directly from an external charger plugged into the mobile device, such as when the mobile device controller is in vertical mode.

[0085] In one embodiment, the mobile device controller 100 can control various aspects of the mobile device and / or one or more client applications running on the mobile device using NFC or the like. For example, during initial setup, the mobile device controller 100 can communicate commands to the mobile device using NFC or the like and display to the user a list of recommended client applications, such as a list of digital games that can be used with the mobile device controller 100. The mobile device controller 100 may have a first button layout 115 and a second button layout 120 with different layouts. In one embodiment, depending on a particular button layout of a particular mobile device controller 100, the mobile device controller 100 can communicate commands to the mobile device using NFC or the like and display a list of recommended client applications suitable for use with that particular configuration of the mobile device controller 100. For example, if the first button layout 115 and the second button layout 120 are configured in a manner similar to a game console controller, the mobile device controller 100 can use NFC or the like to communicate commands to the mobile device to display a list of recommended digital games similar to game console games. In one embodiment, the mobile device controller 100 can maintain such a list and communicate the list to the mobile device for display.

[0086] In an alternative embodiment, one or more client applications and / or appropriate support applications can be installed on the mobile device, and the mobile device controller 100 can be configured to support controlling various aspects of the mobile device, the client application or support application itself, and / or one or more other client applications running on the mobile device. In such an alternative embodiment, the mobile device controller 100 can communicate appropriate information (e.g., identifiers or other identifying information) to the client applications and / or support applications running on the mobile device using NFC or the like. Upon receiving such information, the client applications and / or support applications can use the received information to generate and display recommendation lists (e.g., by accessing lists via lookup tables or key-value pairs stored in the client applications and / or support applications that are referenced or accessed based on the received information). As a result, the mobile device controller 100 can work with such client applications and / or support applications to tailor the user experience on the mobile device in any appropriate way. For example, if user identification information is stored in or otherwise maintained in the mobile device controller 100, such user identification information can be communicated to client applications and / or support applications, thereby tailoring or otherwise customizing the user experience on the mobile device to the user's preferences. For illustrative purposes only and not limited to, the graphical user interface of a digital game can be personalized to display, for example, player incentives, special offers, advertisements, etc., within the digital game or to players within the digital game.In embodiments, other characteristics are also possible, but for example, different player incentives, special offers, advertisements, etc., can be displayed to players of the digital game based on characteristics associated with the mobile device controller 100, such as its type and / or configuration. Additionally or alternatively, the digital game can personalize the prizes, rewards, and / or gifts displayed or presented to players in the digital game's associated gift store, for example. For example, a player using one type of mobile device controller 100 may be presented with different prizes / rewards / gifts than those presented to other players using a different type of mobile device controller 100. In this way, the menu or list of prizes, rewards, and / or gifts can be tailored to each player or any player in the associated gift store displayed in the digital game. Additionally or alternatively, the digital game can personalize graphic information displayed to users outside the digital game, such as advertisements or offers surfaced to players on mobile devices outside the digital game. Other personalization and customization are possible, such as other appropriate changes to the internal or external graphical user interface of the digital game.

[0087] In one embodiment, the client application and / or support application may be configured to support account profiles. The user can create an account profile in the client application and / or support application, which can be used to store user preferences such as preferred client applications, whether the user wishes to be presented with recommendations, and if so, the type and kind of recommendations. Once connected, the mobile device controller 100 can communicate commands to the client application and / or support application using NFC or the like to present them to the user with personalization, customization, preferences, etc. For example, the client application and / or support application can maintain a record of the last client application used by the user. Thus, the mobile device controller 100 can communicate one or more commands to the client application using NFC or the like, and / or use the support application to start the execution of one or more other client applications on the mobile device, such as the last digital game played by the user or the digital game played most recently by the user. Such control by the mobile device controller 100 can be performed during initial setup or at any appropriate time while the mobile device controller 100 is being used with the mobile device.

[0088] The mobile device controller 100 can be considered a type of Human Interface Device (HID). An HID is a type of device that receives input from or provides output to a user. HID can also refer to the HID protocol, a standard for bidirectional communication between a host and a device, designed to simplify installation procedures. The HID protocol was originally developed for USB devices, but has since been implemented on many other protocols, including Bluetooth®. An HID report is a binary data packet communicated between a host and a device. Input reports are sent from the device to the host, output reports are sent from the host to the device, and feature reports may be sent in either direction. The format of an HID report is device-specific. An HID report descriptor may be requested by the host during device enumeration. The HID report descriptor describes the binary format of the report supported by the device. For illustrative purposes only and not limitation, an HID report descriptor for the mobile device controller 100 could declare that it is a device of type "controller" (or something similar) having a certain number of buttons, joysticks, triggers, etc. for input, and even a certain output (e.g., an LED). Each time a button is pressed on the mobile phone controller 100, the mobile phone controller 100 can send an HID report to the host describing which button is currently pressed. In some embodiments of the present invention, the HID report can be used to pair the mobile device controller 100 over a wireless link. Such a process may require a native application on the host side to initiate the process. To compensate for multiple different operating systems, slight differences in the firmware of the mobile phone controller 100 are required to provide the correct HID report. These different firmwares can be maintained and stored within the mobile device controller 100.However, different firmware may require the user to press a combination of buttons to connect to a specific (host) profile during pairing. In some embodiments of the present invention, the mobile device controller 100 can support a custom Bluetooth Low Energy (BLE) service to facilitate easier pairing between the mobile device controller 100 and a mobile device that requires (or requires minimal) user input. In some embodiments of the present invention, a suitable support application installed on the mobile device may be configured to write appropriate information to a custom BLE service on the mobile device controller 100 to signal which operating system the mobile device is using, so that the mobile device controller 100 can send appropriate HID reports. In this way, the mobile device controller 100 can automatically configure and pair with the mobile device without requiring additional user input when the mobile device controller 100 is engaged with or otherwise fitted to the mobile device.

[0089] In one embodiment, the mobile device controller 100 can communicate with one or more remote servers, such as a remote game server or database, using one or more client applications and / or appropriate support applications installed on the mobile device. For example, the mobile device controller 100 can communicate to one or more remote servers any appropriate type of information, such as when and which mobile device controller 100 is being used by a user, which client applications the user is interacting with or engaging with using the mobile device controller 100, the length of time the user is using the mobile device controller 100, the length of time the user is interacting with or engaging with a client application via the mobile device controller 100, the results or outcomes of user interaction with a client application via the mobile device controller 100 (e.g., to determine the user's skill rating), and other similar information collected from the user that can be processed by one or more remote servers to improve the user experience, for example, by tracking engagement and fairness metrics. In one embodiment, in the case of a competitive skill-based digital game, such information can be used to help ensure fairness in competition and / or implement anti-cheat measures by matching players using mobile device controllers with other players also using mobile device controllers. For example, one player using a mobile device controller 100 may have an unfair advantage in a competition against another player who is not using a mobile device controller 100.In one embodiment, players in a competition can be matched based on characteristics associated with the mobile device controller 100, such as the type of mobile device controller 100 being used, the configuration of the mobile device controller 100 being used (e.g., button layout), or simply the fact that the mobile device controller 100 is being used by a player. Other characteristics such as the mobile device controller 100, the player, and the client application can be used for the purpose of matching players in digital game competitions, etc. Additionally or alternatively, players can be matched using appropriate machine learning / artificial intelligence techniques. For example, a machine learning model can be trained based on data from all players in a mobile game. The machine learning model can then be used to dynamically match players in a competition or tournament. The machine learning model can be updated or otherwise adapted as player characteristics evolve over time (e.g., changes in the usage patterns of the mobile device controller 100, changes in win-loss ratios and experience levels, preferences for a particular game that are not preferences for other games, etc.).

[0090] Figure 4 is a block diagram illustrating an exemplary system 400 for interacting with one or more client applications, such as digital games. The server system 414 can provide functionality for collecting data associated with a player's gameplay in a digital game. The server system 414 may include software components and databases that can be deployed, for example, in one or more data centers 412 located in one or more geographical locations. The software components of the server system 414 may include a server data processing module 416. The software components may include subcomponents that can run on the same or different individual data processing devices. The databases of the server system 414 may include, for example, a player data database 418 and a game data database 420, but other databases are also possible. The databases may reside in one or more physical storage systems or may be cloud-based. The software components and data are described further below.

[0091] As shown in Figure 4, the server data processing module 416 can communicate with the player data database 418 and the game data database 420. The player data database 418 may include any appropriate information relating to one or more players of a digital game and their interactions with the digital game, such as whether a player is playing one or more digital games using a mobile device controller, if so, which digital games they are playing, when and for how long, the type / configuration of the mobile device controller used by the player, player game history (e.g., which digital games were played, the number of games won in each digital game, the number of games lost in each digital game, the number of games played in each digital game, the score for each digital game, the time played in each digital game, etc.), player identification information (e.g., username), history of player connections to system 400, player purchases, player achievements, player tasks, player interactions with other users (e.g., chat), player purchases, player deposits / withdrawals, acquisition or use of player virtual items, other conditions in the digital game, and other similar information. The game data database 420 may, for example, include information about digital games played using the system 400. The game data database 420 may also include information about each digital game, such as the virtual environment of each digital game, images, video and / or audio data for each digital game, event data corresponding to past, present, or future events, and game state data defining the current state of each digital game.

[0092] For example, software applications such as digital games or other web-based or suitable client applications may be provided as end-user client applications to enable users to interact with the server system 414. Software applications may relate to and / or provide a wide variety of functions and information, including, for example, entertainment (e.g., games, music, video), business (e.g., word processing, accounting, spreadsheets), news, weather, finance, sports, etc. In some cases, software applications may provide digital games. Digital games may be, or include, sports games, adventure games, virtual playing card games, virtual board games, puzzle games, racing games, or any other suitable type of digital game. In one embodiment, a digital game may be an asynchronous competitive skill-based game in which players can compete with each other in the digital game, but do not need to play the digital game simultaneously. In an alternative embodiment, a digital game may be an asynchronous competitive skill-based game in which players can play the digital game simultaneously and compete with each other in the digital game in real time. Other suitable digital games and software applications are also possible.

[0093] The software application or its components can be accessed by users of client devices such as mobile device A402, mobile device B404, mobile device C406, ..., mobile device N408 via the network 410 (e.g., the Internet), where N can be any suitable natural number. Each mobile device can be any suitable type of mobile electronic device capable of running the software application and communicating with the server system 414 via the network 410, such as a smartphone or tablet computer. Other mobile devices are also possible. One or more of the mobile devices can be used with a mobile device controller, and the same or different types and configurations of the mobile device controller can be used with each, all, or any combination of the mobile devices. In an alternative embodiment, the player data database 418, the game data database 420, or any part thereof can be stored on one or more mobile devices. Additionally or alternatively, software components for the system 400 (e.g., server data processing module 416) or any part thereof may reside on one or more mobile devices or be used to perform operations on one or more mobile devices.

[0094] Figure 5 shows an alternative mobile device controller 500 in an open or deployed configuration for interacting with a client application. The mobile device controller 500 may include a first controller module 505 (e.g., left controller) and a second controller module 510 (e.g., right controller). The first controller module 505 and the second controller module 510 may be divided so that they can be placed on opposing sides of the mobile device (e.g., left and right or top and bottom, but not front and back). Although shown as having approximately equivalent size, the first controller module 505 and the second controller module 510 may be similar or different in size depending on the desired configuration. The first controller module 505 may include a first button layout 515. For example, the first button layout 515 may include any appropriate number and combination of buttons 520, one or more joysticks 525, one or more paddles 530, etc., in any appropriate configuration. The second controller module 510 may include a second button layout 535. For example, the second button layout 535 may include any appropriate number and combination of buttons 540 in any appropriate configuration, one or more joysticks 545, one or more paddles 550, etc. The first controller module 505 and the second controller module 510 may each include or support any appropriate button layout. For example, the button layout may be similar to that of a game console, having two analog sticks, a D-pad, four right-side input buttons, four shoulder buttons, and two triggers. The first controller module 505 and the second controller module 510 may additionally or alternatively include menus, functions, and rear paddle inputs, but other combinations of buttons, triggers, paddles, joysticks, etc. are also possible.

[0095] In an embodiment, the mobile device controller 500 may include an adjustable bridge structure 555 that can be located between and within a first controller module 505 and a second controller module 510. The adjustable bridge structure 555 may include a front surface 560 that can engage with and make full contact with the back surface of the mobile device. The first controller module 505 may be coupled to the adjustable bridge structure 555 via a first set of guide rails 565. The second controller module 510 may be coupled to the adjustable bridge structure 555 via a second set of guide rails 570. Each of the first set of guide rails 565 and the second set of guide rails 570 may consist of one or more guide rails, for example, a single guide rail structure or two (or more) separate guide rails. Each of the first set of guide rails 565 and the second set of guide rails 570 may be rigid, semi-rigid, or flexible, depending on the desired configuration. A first set of guide rails 565 can be permanently and securely attached to the first controller module 505 via a first anchor 575 which can form a structural component of the first controller module 505. A second set of guide rails 570 can be permanently and securely attached to the second controller module 510 via a second anchor 580 which can form a structural component of the second controller module 510. In some embodiments of the present invention, the first anchor 575 and the second anchor 580 can be retracted (fully or partially) into and stationary within the first controller module 505 and the second controller module 510, respectively (e.g., using a suitable elastic structure). The first set of guide rails 565 and the second set of guide rails 570 can be coupled to an adjustable bridge structure 555 using a suitable elastic structure (e.g., a spring) which can be present within the adjustable bridge structure 555.The elastic structure within the adjustable bridge structure 555 allows the first controller module 505 and the second controller module 510 to be pulled apart or expanded laterally, wrapped around the back of the mobile device, and then contracted to engage with the opposing side of the mobile device in a form-fitting configuration, holding it securely. In such a configuration, the adjustable bridge structure 555 can engage with the back of the mobile device. In this way, the mobile device controller 500 can be adapted to mobile devices of different sizes and orientations.

[0096] In one embodiment, the first controller module 505 and the second controller module 510 can communicate with each other via a wired communication channel. For example, either or both of the first pair of guide rails 565 and the second pair of guide rails 570 can be rigid or semi-rigid hollow structures (e.g., tubes), and the wired communication channel can extend through either or both of the first set of guide rails 565 and the second set of guide rails 575 via an adjustable bridge structure 555 to enable communication between the first controller module 505 and the second controller module 510. In an alternative embodiment, the first controller module 505 and the second controller module 510 may include appropriate electronic components to support communication with each other using any suitable wireless communication protocol (e.g., Bluetooth®, Wi-Fi, NFC, etc.). Either or both of the first controller module 505 and the second controller module 510 may include appropriate electronic components to support wireless communication with a mobile device using any suitable wireless communication protocol (e.g., Bluetooth®, Wi-Fi, NFC, etc.). For example, the first controller module 505 and the second controller module 510 can communicate wirelessly with each other and with a mobile device. In an alternative embodiment, if such rails are made of a solid or hollow structural material (e.g., a suitable metal or other conductive material) capable of carrying electrical signals, the first controller module 505 and the second controller module 510 can communicate with each other using either or both of the first set of guide rails 565 and the second set of guide rails 570 themselves.

[0097] The first controller module 505 and the second controller module 510 may include appropriate electronic components to support at least wireless communication with the mobile device and control of client applications running on the mobile device via physical inputs provided by the user when interacting with the first button layout 515 and the second button layout 535. In such a configuration, either or both of the first controller module 505 and the second controller module 510 may include a battery component to power the mobile device controller 500. For example, if one of the first controller module 505 and the second controller module 510 includes a battery component, the controller module having the battery component may power the other controller module via a power communication channel that can extend through an adjustable bridge structure 555 through either or both of the first set of guide rails 565 and the second set of guide rails 570. Additionally or alternatively, the adjustable bridge structure 555 may include appropriate electronic and / or power components to support some or all of such functions. For example, the adjustable bridge structure 555 may include either or both electronic and power components (e.g., a battery) to manage and power either or both of the first controller module 505 and the second controller module 510, and to control a client application running on a mobile device (e.g., via physical inputs provided by the user when interacting with the first button layout 515 and the second button layout 535). In such a configuration, the adjustable bridge structure 555 may manage and power the first controller module 505 and the second controller module 510 via combined or separate control and power communication channels that may extend through either or both of the first set of guide rails 565 and the second set of guide rails 570.In an alternative embodiment, if such rails are made of a material capable of carrying electrical signals (e.g., a suitable metal or other conductive material), control signals and / or power signals can be communicated using either or both of the first set of guide rails 565 and the second set of guide rails 570 themselves.

[0098] In some embodiments of the present invention, the adjustable bridge structure 555 between the first controller module 505 and the second controller module 510 may be centered or substantially centered on an inductive charging array 585 having magnetic alignment features (e.g., MagSafe or other suitable electronic circuitry) including a plurality (e.g., three or more) of aligning magnets 590 arranged in a circle, such as at the 3 o'clock, 6 o'clock, and 9 o'clock positions, although any suitable number, configuration, and arrangement of aligning magnets 590 is possible. The adjustable bridge structure 555 can be deployed and retracted from (or nearly from) the center or center of the mobile device controller 500 so that the inductive charging array 585 of the mobile device controller 500 can be kept substantially centered within the mobile device controller 500. Such centering action may be used to maintain alignment between the mobile device controller 500 and the mobile device, regardless of model and orientation. The inductive charging array 585 may also be used to support additional configuration and playability features and functions similar to or identical to those described above with respect to the inductive charging array integrated into the adjustable bridge structure 125 of the mobile device controller 100.

[0099] Figure 6 shows an alternative mobile device controller 500 in a partially closed or folded configuration. When in the folded configuration, the first set of guide rails 565 and the second set of guide rails 570 can be retracted and stationary or located within an adjustable bridge structure 555 so that the first anchor 575 of the first controller module 505 can contact or substantially contact the second anchor 580 of the second controller module 510. In one embodiment, the first set of guide rails 565 can form an outer set of guide rails, and the second set of guide rails 570 can form an inner set of guide rails. In such an embodiment, in the folded configuration, the (inner) second set of guide rails 570 can be stationary between the (outer) first set of guide rails 565 within the adjustable bridge structure 555. In an alternative embodiment, the first set of guide rails 565 can form an inner set of guide rails, and the second set of guide rails 570 can form an outer set of guide rails. In such embodiments, in the folded configuration, the first set of guide rails 565 (inner) can be stationary between the second set of guide rails 570 (outer) within an adjustable bridge structure 555. In the folded configuration, the mobile device controller 500 can be approximately the size of a credit card, etc. In alternative embodiments, if each of the first set of guide rails 565 and the second set of guide rails 570 includes a single guide rail structure, the first set of guide rails 565 can be retracted and stationary within a first anchor 575 in a first controller module 505, and the second set of guide rails 570 can be retracted and stationary within a second anchor 580 in a second controller module 510.

[0100] Figure 7 shows an alternative mobile device controller 500 in a configuration engaged with a vertically oriented mobile device 705. In this embodiment, the mobile device controller 500 can form-fit onto the mobile device 705 and provide physical inputs that allow the user to control, interact with, or otherwise engage with client applications running on the mobile device 705. As previously mentioned, the elastic structure within the adjustable bridge structure 555 can allow the first controller module 505 and the second controller module 510 to be pulled apart or expanded laterally, wrap around the back of the mobile device 705, and then contract to engage with the opposing side of the mobile device in a form-fitting configuration and hold securely. For example, the first anchor 575 can contact and engage securely with the first side 710 of the mobile device 705, and the second anchor 580 can contact and engage securely with the second side 715 of the mobile device 705. The adjustable bridge structure 555 can engage with the back of the mobile device 705.

[0101] Figure 8 shows an alternative mobile device controller 500 in a configuration engaged with a landscape-oriented mobile device 705. When the mobile device 705 is in landscape orientation, the first anchor 575 can contact and firmly engage with, for example, the third side 810 of the mobile device 705, and the second anchor 580 can contact and firmly engage with, for example, the fourth side 815 of the mobile device 705. The adjustable bridge structure 555 can engage with the back of the mobile device 705. As a result, the mobile device controller 500 can be adapted to mobile devices of different sizes and orientations.

[0102] Figures 9A to 9O show multiple illustrations of alternative mobile device controllers 900 in closed or folded configurations for interacting with client applications. The mobile device controller 900 can form-fit onto a mobile device and provide physical inputs that enable the user to control, interact with, or otherwise engage with client applications running on the mobile device. In embodiments, the mobile device controller 900 may include a linear unfolding or sliding mechanism for use with a mobile device. The mobile device controller 900 may include a first controller module 905 (e.g., left controller) and a second controller module 910 (e.g., right controller). The first controller module 905 and the second controller module 910 may be divided so that they can be placed on opposing sides of the mobile device (e.g., left and right or top and bottom, but not front and back). Although shown as having substantially equivalent size, the first controller module 905 and the second controller module 910 may be similar or different in size depending on the desired configuration. The first controller module 905 may include a first button layout 915 on its first (e.g., top) surface. For example, the first button layout 915 may include any suitable number of buttons or keys in any suitable configuration (e.g., A, B, X, Y buttons, and / or arrows such as up, down, left, right). The second controller module 910 may include a second button layout 920 on its second (e.g., top) surface. For example, the second button layout 920 may include any suitable number of buttons or keys in any suitable configuration (e.g., A, B, X, Y buttons, and / or arrows such as up, down, left, right). The first controller module 905 and the second controller module 910 may each include or support any suitable button and / or key layout.For example, the button layout may be similar to that of a game console, having two analog sticks, a D-pad, four right-side input buttons, four shoulder buttons, and two triggers. The first controller module 905 and the second controller module 910 may additionally or alternatively include menus, functions, and rear paddle inputs, but other combinations such as buttons, triggers, paddles, and joysticks are also possible.

[0103] In the embodiment, the mobile device controller 900 may include a deployable bridge structure 925 that can be located between and within a first controller module 905 and a second controller module 910. The deployable bridge structure 925 may include an outer deployment structure 930 that can include two separate sections or parts, namely, a first outer deployment section 930A located within the first controller module 905 and a second outer deployment section 930B located within the second controller module 910. An inner deployment structure 940 may be located within the outer deployment structure 935 and between the first outer deployment section 930A and the second outer deployment section 930B. The outer deployment structure 930 and the inner deployment structure 940 may have two linear steps to allow the deployment of the mobile device controller 900 to fit the size or orientation of various mobile devices. The first outer deployment section 930A may include a pair of first grooves 945 (each located on an opposing side of the first outer deployment section 930A) to support the lateral movement of the first outer deployment section 930A. The second outer deployment section 930B may include a pair of second grooves 950 (each located on an opposing side of the second outer deployment section 930B) to support the lateral movement of the second outer deployment section 930B. The first controller module 905 may include a pair of first guide anchors 955 (each located on an opposing inner side of the first controller module 905). Each of the pair of first guide anchors 955 may include a first projection 960 of appropriate height and width to engage with each of the pair of first grooves 945 to support the lateral movement of the first outer deployment section 930A. In some embodiments of the present invention, each of the first projections 960 can be any suitable elliptical or circular shape having a diameter equal to or slightly smaller than the width of the corresponding first groove 945 in order to facilitate the free lateral movement of the first outward extension 930A. The second controller module 910 may include a pair of second guide anchors 965.Each of the pair of second guide anchors 965 may include a second projection 970 of appropriate height and width to engage with each of the pair of second grooves 950 in order to support the lateral movement of the second outer extension 930B. In some embodiments of the present invention, each of the second projections 970 may be any suitable elliptical or circular shape having a diameter equal to or slightly smaller than the width of the corresponding second groove 950 in order to facilitate the free lateral movement of the second outer extension 930B.

[0104] In some embodiments of the present invention, the mobile device controller 900 may include a pair of flappers (or flaps) or grippers (or grips) for gripping and holding a mobile device, enabling the mobile device controller 900 to be more compact and thinner in design. For example, the flappers may reside within the body of the mobile device controller 900 and may be pre-installed to automatically rise when the first controller module 905 and the second controller module 910 are deployed apart, and to automatically lower and retract into the body when the first controller module 905 and the second controller module 910 are retracted together. According to one embodiment of the present invention, the first controller module 905 may include a first flapper hinge 975 for engaging with a first side of a mobile device. The first flapper hinge 975 may have any suitable width between the opposing inner sides of the first controller module 905, as well as any suitable height and thickness, depending, for example, the thickness of the mobile device being gripped, the desired amount of external expansion of the first controller module 905 when in the fully engaged position, etc. The first flapper hinge 975 may be coupled to the inside of the first controller module 905 via a pair of first pivot joints 980 (each located on the opposing inside of the first controller module 905) to allow the first flapper hinge 975 to rotate. In one embodiment, each or both of the pair of first pivot joints 980 may have a spring mechanism that allows the first flapper hinge 975 to rise as the first controller module 905 is laterally expanded and to descend as the first controller module 905 is laterally contracted. The second controller module 910 may include a second flapper hinge 985 for engaging with a second side of the mobile device.The second flapper hinge 985 can have any suitable width between opposing inner surfaces of the second controller module 910, as well as any suitable height and thickness, depending, for example, the thickness of the mobile device being gripped, the desired amount of external expansion of the second controller module 910 when in the fully engaged position, etc. In one embodiment, the first flapper hinge 975 and the second flapper hinge 985 may be similar or identical in size and shape. In an alternative embodiment, the first flapper hinge 975 and the second flapper hinge 985 may each be different in size and shape. The second flapper hinge 985 may be coupled to the inside of the second controller module 910 via a pair of second pivot joints 990 (each located on the opposing inner surfaces of the second controller module 910) to allow the second flapper hinge 985 to rotate. In one embodiment, each or both of the pair of second pivot joints 985 may be equipped with a spring mechanism that allows the second flapper hinge 985 to rise as the second controller module 910 is laterally extended and to descend as the second controller module 910 is laterally retracted.

[0105] In some embodiments of the present invention, to support the deployment and retraction of the mobile device controller 900, the deployable bridge structure 925 may be coupled to the respective first controller module 905 and second controller module 910 using a suitable elastic structure (e.g., a spring). The elastic structure may be coupled to each end of the deployable bridge structure 925. Alternatively, the elastic structure may reside within the deployable bridge structure 925 and extend through it. For example, the elastic structure may be attached to or otherwise secured to the first end 992 in the casing of the first controller module 905 and to the second end 994 in the casing of the second controller module 910. In one embodiment, the elastic structure may extend through each end of the deployable bridge structure 925 or comprise one or more internal springs attached thereto. In an alternative embodiment, the elastic structure may include a spring-loaded reel fastened or otherwise secured to one end within the casing of the mobile device controller 900 (for example, at the first end 992 of the first controller module 905). The ends of the cord or line of the spring-loaded reel may extend through a deployable bridge structure 925 (for example, at the second end 994 of the second controller module 910) and be fastened or otherwise secured to the opposing ends within the casing of the mobile device controller 900. Alternatively, each of the first controller module 905 and the second controller module 910 may include spring-loaded reels attached or otherwise secured to the inside of the respective casings of the first controller module 905 and the second controller module 910 at both ends of the mobile device controller 900. The ends of the cord or line of each spring-loaded reel may be attached or otherwise secured to the respective ends of the first outer deployment section 930A and the second outer deployment section 930B.The elastic structure for the deployable bridge structure 925 can allow the first controller module 905 and the second controller module 910 to be pulled apart laterally or deployed, wrapped around the back of the mobile device, and then contracted (for example, using the first flapper hinge 975 and the second flapper hinge 985) to engage with the opposing side of the mobile device in a form-fitting configuration and hold it securely. In such a configuration, the deployable bridge structure 925 can engage with the back of the mobile device. In this way, the mobile device controller 900 can be adapted to mobile devices of different sizes and orientations.

[0106] The first controller module 905 and the second controller module 910 may include appropriate electronic components to support at least wireless communication with the mobile device and control of client applications running on the mobile device via physical inputs provided by the user when interacting with the first button layout 915 and the second button layout 920. In such a configuration, either or both of the first controller module 905 and the second controller module 910 may include a battery component to power the mobile device controller 900. For example, if one of the first controller module 905 and the second controller module 910 includes a battery component, the controller module having the battery component can power the other controller module via a power communication channel that can extend within and through a deployable bridge structure 925. In some embodiments of the present invention, either or both of the first controller module 905 and the second controller module 910 may include a suitable switch (e.g., toggle, push button, selector, joystick, rotary, slide, etc.) for, for example, turning the mobile device controller 900 on and off, initiating pairing between the mobile device controller 900 and a mobile device, disconnecting the mobile device controller 900 from a mobile device, switching or otherwise cycling through client applications that a user is interacting with on a mobile device, or providing other similar functions. For illustrative purposes only and not limiting, the second controller module 910 may include a switch 995 as shown in Figure 9B, although the switch 995 may be located additionally or alternatively on the first controller module 905. In some embodiments of the present invention, the deployable bridge structure 925 may include a suitable electronic and / or power component to support some or all of such functions.For example, the deployable bridge structure 925 may include an inductive charging array having magnetic alignment features (e.g., MagSafe) or other suitable electronic circuitry. The deployable bridge structure 925 can be deployed and retracted from (or nearly from) the center or center of the mobile device controller 900 so that the inductive charging array of the mobile device controller 900 can be kept substantially centered within the mobile device controller 900. Such centering action may be used to maintain alignment between the mobile device controller 900 and the mobile device, regardless of model and orientation. Such an inductive charging array may also be used to support additional configuration and playability features and functions similar to or identical to those described above with respect to the inductive charging array integrated into the adjustable bridge structure 125 of the mobile device controller 100 in Figure 1. In one embodiment, the first controller module 905 and the second controller module 910 can communicate with each other via a wired communication channel. For example, a wired communication channel may extend within and through the deployable bridge structure 925 to enable communication between the first controller module 905 and the second controller module 910. In alternative embodiments, the first controller module 905 and the second controller module 910 may include appropriate electronic components to support communication with each other using any suitable wireless communication protocol (e.g., Bluetooth®, Wi-Fi, NFC, etc.). Either or both of the first controller module 905 and the second controller module 910 may include appropriate electronic components to support wireless communication with a mobile device using any suitable wireless communication protocol (e.g., Bluetooth®, Wi-Fi, NFC, etc.). For example, the first controller module 905 and the second controller module 910 may communicate wirelessly with each other and with a mobile device.

[0107] Figure 10 shows a mobile device controller 900 in a partially open configuration. In Figure 10, the first controller module 905 and the second controller module 910 are deployed laterally from each other, partially exposing the outer deployment structure 930 of the deployable bridge structure 925. When the user separates the first controller module 905 and the second controller module 910, the first outer deployment section 930A and the second outer deployment section 930B of the deployable bridge structure 925 begin to extend from the casings of the first controller module 905 and the second controller module 910, respectively, along the pair of first projections 960 and the pair of second projections 970 of the pair of first guide anchors 955 and the pair of second guide anchors 965, respectively, guided by the pair of first grooves 945 and the pair of second grooves 950. Furthermore, the first flapper hinge 975 and the second flapper hinge 985 are exposed. As described above, the first flapper hinge 975 and the second flapper hinge 985 can be pre-mounted to allow them to pop up and retract automatically (for example, using a spring-loaded pair of first pivot joints 980 and second pivot joints 990).

[0108] Figures 11A to 11AC illustrate the mobile device controller 900 in a fully deployed configuration. In Figures 11A to 11AC, the first controller module 905 and the second controller module 910 are fully deployed laterally. As a result, the first outer deployment section 930A and the second outer deployment section 930B of the deployable bridge structure 925 extend from the casings of the first controller module 905 and the second controller module 910, respectively. The inner deployment section 940 of the deployable bridge structure 925 is also exposed. In some embodiments of the present invention, the deployable bridge structure 925 may include an inductive charging array having magnetic alignment features or other suitable electronic circuits. In one embodiment, the inductive charging array may be located on the first surface 1105 of the inner deployment section 940 that engages with, or otherwise contacts, or is adjacent to the back of the mobile device. Furthermore, the first flapper hinge 975 and the second flapper hinge 985 are fully open and upright, extending substantially perpendicularly to the deployable bridge structure 925. In such a fully deployed configuration, the mobile device is ready to be mounted or inserted into the mobile device controller 900. The mobile device controller 900 can then be retracted to engage with the opposing side of the mobile device in a form-fitting configuration and hold it securely. In this way, the mobile device controller 900 can accommodate mobile devices of different sizes and orientations.

[0109] Figure 12 is a side view of an alternative mobile device controller 1200 in a closed or folded configuration for interacting with a client application. The mobile device controller 1200 can form-fit onto a mobile device and provide physical inputs that allow the user to control, interact with, or otherwise engage with a client application running on the mobile device. In some embodiments of the present invention, the mobile device controller 1200 may feature a multi-bar deployment mechanism for use with a mobile device. For illustrative purposes rather than limiting, Figure 12 shows a four-bar deployment mechanism for the mobile device controller 1200 (i.e., four pairs of swing bars, each pair located on the opposing inner side of the casing, for a total of eight swing bars), although configurations with fewer or more bars may also be used. The mobile device controller 1200 may include a first controller module 1205 (e.g., left controller) and a second controller module 1210 (e.g., right controller). The first controller module 1205 and the second controller module 1210 may be divided so that they can be placed on opposite sides of the mobile device (e.g., left and right or top and bottom, but not front and back). Although shown as having approximately equivalent size, the first controller module 1205 and the second controller module 1210 may be similar or different in size depending on the desired configuration. The first controller module 1205 may include a first button layout 1215 on its first (e.g., top) surface. For example, the first button layout 1215 may include any appropriate number of buttons or arrow keys (e.g., A, B, X, Y buttons, and / or arrows such as up, down, left, right) in any appropriate configuration. The second controller module 1210 may include a second button layout 1220 on its second (e.g., top) surface.For example, the second button layout 1220 can include any appropriate number of buttons or keys in any appropriate configuration (e.g., A, B, X, Y buttons, and / or arrows such as up, down, left, right). The first controller module 1205 and the second controller module 1210 can each include or support any appropriate button layout and / or keys. For example, the button layout could be similar to that of a game console, having two analog sticks, a D-pad, four right-side input buttons, four shoulder buttons, and two triggers. The first controller module 1205 and the second controller module 1210 can additionally or alternatively include menus, functions, and rear paddle inputs, although other combinations such as buttons, triggers, paddles, and joysticks are also possible.

[0110] In one embodiment, the mobile device controller 1200 may include an expandable bridge structure 1225 which may be located between and within a first controller module 1205 and a second controller module 1210. The expandable bridge structure 1225 may include two separate sections or parts: a first expandable portion 1225A located within the first controller module 1205 and a second expandable portion 1225B located within the second controller module 1210. The first expandable portion 1225A includes a pair of first swing arms 1230 (each located on the opposite side of the first expandable portion 1225A). The pair of first swing arms 1230 may be coupled to the first expandable portion 1225A via a pair of first pivot joints 1235 (each located on the opposite side of the first expandable portion 1225A) which allow the upper parts of the pair of first swing arms 1230 to rotate about an axis. The first expandable portion 1225A may be coupled to the inner casing of the first controller module 1205 via a pair of first swing arms 1230, through a pair of second pivot joints 1240 (each located on the opposite side of the first expandable portion 1225A) that allow the lower parts of the pair of first swing arms 1230 to rotate about an axis. The first expandable portion 1225A includes a pair of second swing arms 1245 (each located on the opposite side of the first expandable portion 1225A). The pair of second swing arms 1245 may be coupled to the first expandable portion 1225A via a pair of third pivot joints 1250 (each located on the opposite side of the first expandable portion 1225A) that allow the upper parts of the pair of second swing arms 1245 to rotate about an axis. The first expandable portion 1225A may be further coupled to the inner casing of the first controller module 1205 via a pair of second swing arms 1245, through a pair of fourth pivot joints 1255 (each located on the opposite side of the first expandable portion 1225A), which allow the lower parts of the pair of second swing arms 1245 to rotate about an axis.

[0111] In one embodiment, the second expandable portion 1225B includes a pair of third swing arms 1260 (each located on the opposite side of the second expandable portion 1225B). The pair of third swing arms 1260 may be coupled to the second expandable portion 1225B via a pair of fifth pivot joints 1265 (each located on the opposite side of the second expandable portion 1225B) that allow the upper parts of the pair of third swing arms 1260 to rotate about an axis. The second expandable portion 1225B may be coupled to the inner casing of the second controller module 1210 via the pair of third swing arms 1260 via a pair of sixth pivot joints 1270 (each located on the opposite side of the second expandable portion 1225B) that allow the lower parts of the pair of third swing arms 1260 to rotate about an axis. The second expandable section 1225B includes a pair of fourth swing arms 1275 (each located on the opposite side of the second expandable section 1225B). The pair of fourth swing arms 1275 may be coupled to the second expandable section 1225B via a pair of seventh pivot joints 1280 (each located on the opposite side of the second expandable section 1225B) that allow the upper parts of the pair of fourth swing arms 1275 to rotate about an axis. The second expandable section 1225B may be further coupled to the inner casing of the second controller module 1210 via the pair of fourth swing arms 1275 via a pair of eighth pivot joints 1285 (each located on the opposite side of the second expandable section 1225B) that allow the lower parts of the pair of fourth swing arms 1275 to rotate about an axis.

[0112] In one embodiment, the first expandable portion 1225A and the second expandable portion 1225B of the expandable bridge structure 1225 may be coupled via a pair of guide rails 1290 (however, more than one or two guide rails 1290 may be used) that can extend through the first expandable portion 1225A and the second expandable portion 1225B, or otherwise attached. In some embodiments of the present invention, the pair of guide rails 1290 are not directly coupled to either the first controller module 1205 or the second controller module 1210, thereby allowing the expandable bridge structure 1225 to swing freely within the casing of the mobile device controller 1200 (via their respective swing arms) when the first controller module 1205 and the second controller module 1210 are expanded apart. In one embodiment, one or both of the pair of guide rails 1290 may include a rigid or semi-rigid hollow structure (e.g., a tube). A suitable elastic structure (e.g., a spring) can be located either internally or externally along the length (whole or in part) of one or both of the pair of guide rails 1290. In an alternative embodiment, one or both of the pair of guide rails 1290 may include a rigid or semi-rigid solid structure. A suitable elastic structure (e.g., a spring) can be located externally along the length (whole or in part) of one or both of the pair of guide rails 1290. For example, a suitable elastic structure can be located externally around each end of the pair of guide rails 1290 and fixed thereto, with the other end of the suitable elastic structure being fixed to or otherwise attached to each end of the first expandable portion 1225A and the second expandable portion 1225B. Alternatively, one or both of the pair of guide rails 1290 themselves may be equipped with a suitable elastic structure (e.g., a spring). In each of the embodiments described above, the first expandable portion 1225A and the second expandable portion 1225B may be mounted along the pair of guide rails 1290 and coupled to a suitable elastic structure.A suitable elastic structure can allow the first controller module 1205 and the second controller module 1210 to be pulled apart or expanded laterally, wrapped around the back of the mobile device, and then contracted to engage with the opposing side of the mobile device in a form-fitting configuration, holding it securely. In such a configuration, the expandable bridge structure 1225 can engage with the back of the mobile device. In this way, the mobile device controller 1200 can be adapted to mobile devices of different sizes and orientations.

[0113] In some embodiments of the present invention, the mobile device controller 1200 may include a pair of flappers for gripping and holding a mobile device, enabling the mobile device controller 1200 to be more compact and thinner in design. For example, the flappers may reside within the body of the mobile device controller 1200 and may be pre-installed to automatically rise when the first controller module 1205 and the second controller module 1210 expand apart and automatically retract into the body and descend when the first controller module 1205 and the second controller module 1210 contract together. According to one embodiment of the present invention, the first controller module 1205 may include a first flapper hinge 1292 for engaging with a first side of a mobile device. The first flapper hinge 1292 may have any suitable width between opposing sides of the first expandable portion 1225A, as well as any suitable height and thickness, depending on, for example, the thickness of the mobile device to be gripped, the desired amount of expansion of the outside of the first controller module 1205 when in the fully engaged position, etc. The first flapper hinge 1292 may be coupled to the first expandable portion 1225A via a pair of first pivot joints 1294 (each located on an opposing side of the first expandable portion 1225A) to allow the first flapper hinge 1292 to rotate. In one embodiment, one or both of the pair of first pivot joints 1294 may have a spring mechanism that allows the first flapper hinge 1292 to rise as the first controller module 1205 expands laterally and to descend as the first controller module 1205 contracts laterally. The second controller module 1210 may include a second flapper hinge 1296 for engaging with a second side of the mobile device.The second flapper hinge 1296 can have any suitable width between opposing sides of the second expandable portion 1225B, as well as any suitable height and thickness, depending, for example, the thickness of the mobile device being gripped, the desired amount of expansion outside the second controller module 1210 when in the fully engaged position, etc. In one embodiment, the first flapper hinge 1292 and the second flapper hinge 1296 may be similar or identical in size and shape. In an alternative embodiment, the first flapper hinge 1292 and the second flapper hinge 1296 may each be different in size and shape. The second flapper hinge 1296 may be coupled to the second expandable portion 1225B via a pair of second pivot joints 1298 (each located on opposing sides of the second expandable portion 1225B) to allow the second flapper hinge 1296 to rotate. In one embodiment, either or both of the pair of second pivot joints 1298 may be equipped with a spring mechanism that allows the second flapper hinge 1296 to rise as the second controller module 910 expands laterally and to descend as the second controller module 910 contracts laterally.

[0114] The first controller module 1205 and the second controller module 1210 may include electronic components (e.g., a first electronic component 1217 of the first controller module 1205 and / or a second electronic component 1222 of the second controller module 1210) suitable for supporting at least wireless communication with a mobile device and control of client applications running on the mobile device via physical inputs provided by the user when interacting with the first button layout 1215 and the second button layout 1220. In such a configuration, either or both of the first controller module 1205 and the second controller module 1210 may include a battery component that supplies power to the mobile device controller 1200. For example, if one of the first controller module 1205 and the second controller module 1210 includes a battery component, the controller module having the battery component may supply power to the other controller module via a power communication channel that can extend within and through an expandable bridge structure 1225 (e.g., through one or both of a pair of guide rails 1290). Additionally or alternatively, the expandable bridge structure 1225 may include appropriate electronic and / or power components to support some or all of such functions. In some embodiments of the present invention, the expandable bridge structure 1225 may include an inductive charging array having magnetic alignment features (e.g., MagSafe, or other appropriate electronic circuitry). For example, such an inductive charging array or other appropriate electronic circuitry may be present in either or both of the first expandable portion 1225A and the second expandable portion 1225B.The expandable bridge structure 1225 can be deployed and retracted from (or nearly from) the center or center of the mobile device controller 1200 so that the inductive charging array of the mobile device controller 1200 (e.g., each half of the inductive charging array from the first expandable portion 1225A and the second expandable portion 1225B) can be maintained in the center of the mobile device controller 1200, near it, or around it. Such centering action may be used to maintain alignment between the mobile device controller 1200 and the mobile device, regardless of model and orientation. Such an inductive charging array (or other suitable electronic circuitry) may also be used to support additional configuration and playability features and functions similar to or identical to those described above with respect to the inductive charging array integrated into the adjustable bridge structure 125 of the mobile device controller 100 in Figure 1. In one embodiment, the first controller module 1205 and the second controller module 1210 can communicate with each other via a wired communication channel. For example, a wired communication channel may extend within and through an expandable bridge structure 1225 (e.g., via one or both of a pair of guide rails 1290) to enable communication between the first controller module 1205 and the second controller module 1210. In an alternative embodiment, the first controller module 1205 and the second controller module 1210 may include appropriate electronic components to support communication with each other using any suitable wireless communication protocol (e.g., Bluetooth®, Wi-Fi, NFC, etc.). Either or both of the first controller module 1205 and the second controller module 1210 may include appropriate electronic components to support wireless communication with a mobile device using any suitable wireless communication protocol (e.g., Bluetooth®, Wi-Fi, NFC, etc.). For example, the first controller module 1205 and the second controller module 1210 may communicate wirelessly with each other and with a mobile device.

[0115] Figure 13 shows a partially extended configuration of the mobile device controller 1200. In Figure 13, the first controller module 1205 and the second controller module 1210 are extended laterally from each other, partially exposing the first expandable portion 1225A and the second expandable portion 1225B of the expandable bridge structure 1225. When the user separates the first controller module 1205 and the second controller module 1210, the first expandable portion 1225A and the second expandable portion 1225B begin to extend from the casings of the first controller module 1205 and the second controller module 1210 along a pair of guide rails 1290. The first expandable section 1225A expands along a pair of guide rails 1290 by rotating or swinging via a pair of first swing arms 1230 and a pair of second swing arms 1245 (around each pair of first pivot joints 1235, second pivot joint 1240, third pivot joint 1250, and fourth pivot joint 1255). The second expandable section 1225B expands along a pair of guide rails 1290 by rotating or swinging via a pair of third swing arms 1260 and a pair of fourth swing arms 1275 (around each pair of fifth pivot joints 1265, sixth pivot joint 1270, seventh pivot joint 1280, and eighth pivot joint 1285). Furthermore, the first flapper hinge 1292 and the second flapper hinge 1296 are exposed and partially raised. As described above, the first flapper hinge 1292 and the second flapper hinge 1296 can be pre-mounted to allow them to automatically rise and retract (for example, using a pair of spring-loaded first pivot joints 1294 and a pair of second pivot joints 1298).

[0116] Figure 14 shows a mobile device controller 1200 in a fully extended configuration. In Figure 14, the first controller module 1205 and the second controller module 1210 are fully extended laterally. As a result, the first expandable portion 1225A and the second expandable portion 1225B of the expandable bridge structure 1225 extend from the casings of the first controller module 1205 and the second controller module 1210, respectively. In some embodiments of the present invention, the expandable bridge structure 1225 may include an inductive charging array having magnetic alignment features or other suitable electronic circuits. In one embodiment, the inductive charging array may be located on the first surface 1405 of the expandable bridge structure 1225 that engages with, or otherwise contacts, the back of the mobile device (e.g., a first portion of the circuitry present in the first expandable portion 1225A and a second portion of the circuitry present in the second expandable portion 1225B) or is adjacent to it. Arrow 1410 indicates the position and movement of the expandable bridge structure 1225, which swings near the bottom of the casing of the mobile device controller 1200 (via pairs of first, second, third, and fourth swing arms 1230, 1245, 1260, and 1275). The first and second flapper hinges 1292 and 1296 are fully open and upright, extending substantially perpendicularly to the expandable bridge structure 1225. In such a fully deployed configuration, the mobile device is ready to be mounted or inserted into the mobile device controller 1200. The mobile device controller 1200 can then be retracted to engage with the opposing side of the mobile device in a form-fitting configuration and hold it securely. In this way, the mobile device controller 1200 can accommodate mobile devices of different sizes and orientations.

[0117] As described above, the mobile device controllers 100, 500, 900, and / or 1200 can include and support any appropriate number of buttons and / or keys in any appropriate configuration within the button layout of each controller module. Different structures and mechanisms can be used in the button layout to support buttons and / or keys, as well as additional functions. For example, the directional pad ("D-pad") position sensing mechanism of the present invention can attempt to solve two controller layouts that were previously mutually exclusive, namely the conventional D-pad and analog stick, into a single unified control mechanism. In embodiments, the same layout can be used on the ABXY input button side of the mobile device controller, thereby enabling a compact layout in space and dual analog stick inputs that were previously impossible with conventional layouts. In addition to enabling more compact packaging of the mobile device controller, such hybrid analog button layouts can also propose the possibility of improving play performance. For example, by placing the analog stick and buttons on essentially the same surface, such a mechanism can enable the activation of button inputs (such as ABXY) while maintaining input on the analog "stick".

[0118] Figure 15 is a diagram of a posable directional pad using a pointing stick in a keyboard layout, according to one embodiment of the present invention. In Figure 15, the keypad layout 1500 includes a directional pad 1505 having a set of arrow keys 1510 (e.g., up, down, left, and right). The keypad layout 1500 may also include a set of buttons 1515 (e.g., A, B, X, and Y). The set of arrow keys 1510 may include a first projection 1520 having a substantially circular configuration that can be located at the center of the set of arrow keys 1510. The set of buttons 1515 may include a second projection 1525 having a substantially circular configuration that can be located at the center of the set of buttons 1515. In one embodiment, the first projection 1520 and the second projection 1525 may partially extend through the surface to provide a suitable input interface. In an alternative embodiment, the directional pad 1505 may be mounted on the first projection 1520 instead of a conventional post / ball joint. In such alternative embodiments, a non-returning or "non-slip" surface can be used on the first projection 1520, which the user can interact with. A similar alternative embodiment can be used on the second projection 1525 for the set of buttons 1515 to provide the user with a secondary "analog" input. In either embodiment, the bezels of the first projection 1520 and the second projection 1525 can function as posable input surfaces to provide the user with additional input control functionality.

[0119] Figure 16 is a diagram of a movable input surface for a keypad layout according to one embodiment of the present invention. In Figure 16, the keypad layout 1600 includes a directional pad 1605 having a set of arrow keys 1610 (e.g., up, down, left, and right). The keypad layout 1600 may also include a set of buttons 1615 (e.g., A, B, X, and Y). The set of arrow keys 1610 may include a first stopper 1620 having a substantially circular configuration that can be located at the center of the set of arrow keys 1610. The set of buttons 1615 may include a second stopper 1625 having a substantially circular configuration that can be located at the center of the set of buttons 1615. In one embodiment, the set of arrow keys 1610 of the directional pad 1605 may be mounted on a floating plate 1630 having a perimeter that can be clicked on the Z axis via the contacts of the directional pad 1605. A flexible membrane 1635 (e.g., TPU (thermoplastic polyurethane) or other suitable material) can surround the floating plate 1630 to enable XY conversion input. A similar configuration can be used for the set of buttons 1615. In one embodiment, the set of buttons 1615 can be mounted on a floating plate 1640 having a perimeter that allows clicking on the Z axis via the contacts of the set of buttons 1615. A flexible membrane 1645 (e.g., TPU or other suitable material) can surround the floating plate 1640 to enable conversion input. With a limited range of motion, a reasonable level of resistance can be provided to the user for either or both of the set of arrow keys 1610 or the set of buttons 1615.

[0120] Figures 17A and 17B illustrate an array of contact point fingers for a directional pad according to one embodiment of the present invention. A radial layout 1705 is shown in Figure 17A. The radial layout 1705 may include a plurality of metal fingers 1710. A plurality of corresponding metal contacts 1715 may be located beneath each of the plurality of metal fingers 1710. In such embodiments, by using the plurality of metal fingers 1710 in the radial layout 1705, a closed electrical connection can be formed when actuated in a particular direction (i.e., when a user presses one or more of the plurality of metal fingers 1710 to make electrical contact with one or more of the plurality of metal contacts 1710). By knowing which channel has formed a closed connection, the present invention can determine in which direction the directional pad 1720 has been actuated. In an alternative embodiment shown in Figure 17B, a plurality of individual curved metal fingers 1725 may be arranged and positioned substantially equally spaced around the periphery of the directional pad 1730. One or more suitable electrical contacts (not shown) can be positioned beneath each of the multiple individual curved metal fingers 1725. In such alternative embodiments, a closed electrical connection can be formed when actuated in a particular direction (i.e., when a user presses one or more of the multiple individual curved metal fingers 1725 to electrically contact the corresponding one or more metal contacts beneath them). By knowing which channels have formed closed connections, the present invention can determine in which direction the directional pad 1730 has been actuated. In any embodiment, the closed connections can also be used as magnitude inputs. For example, a deformable material such as TPE (thermoplastic elastomer) or silicone can be used above the section pressed against the contacts. The number of contacts being pressed can be measured, and from there the general direction can be determined by averaging the orientation of the contacts around a circle. In Figures 17A and 17B, the client application may be configured to report the required fidelity for the orientation necessary for a proper user experience.For illustrative purposes only and not as a limitation, a client application can report directions in, for example, 4 / 8 / 360 points. As a result, if the client application only requires four directions (e.g., up, down, left, and right), pressing or touching in other directions will not generate incorrect input, but it will allow the client application to use the directional pad (e.g., the central part of the directional pad) in a manner similar to an analog stick with 360 degrees of freedom.

[0121] Figure 18 is a side view of a contact pad 1805 for a directional pad 1800 according to one embodiment of the present invention. In Figure 18, for a client application that can accept up, down, left, and right inputs via the directional pad 1800, a conventional button membrane 1810 and contact switch configuration can be used. For a client application that can use analog inputs, two distance sensors 1815 and 1820 can be used to detect deflections on both the X and Y axes. According to one embodiment, the contact pad 1805 can be mechanically designed to pivot on a fixed ball joint 1825 so that the movement of the contact pad 1805 can be reliably predicted. In one embodiment, a magnet 1830 can be placed above a Hall effect sensor 1835 on the back of a printed circuit board assembly (PCBA) on one axis (either the X or Y axis) and above a similar magnet / Hall effect sensor pair mounted on the other axis (the other of the X or Y axis). Hall effect sensors on the X and Y axes, working in conjunction with corresponding magnets, can return linear displacements in the X and Y axes, which can be used to calculate a direction vector having the magnitude of a key press on the contact pad 1805. In the embodiment shown in Figure 18, spring fingers 1840 and 1845, separated from each arm of the contact pad 1805, can be used to prevent the contact pad 1805 of the direction pad 1800 from floating within the housing. Each spring finger 1840 and 1845 can be slightly pre-mounted in the starting position. Button membranes 1810 can be slightly pre-mounted in opposing directions (1850 and 1855) to firmly hold the contact pad 1805 in place. Guides 1860 and 1865 on both sides of the contact pad 1805 can constrain the contact pad 1805 to X and Y movement. In an alternative embodiment, the Hall effect sensor can be centered below or near the bottom 1870 of the directional pad 1800, and the magnet can be positioned above (e.g., directly above) the Hall effect sensor at or near the top 1875 of the directional pad 1800, which can be configured to tilt together with the contact pad 1805.In such alternative embodiments, the Hall effect sensor can return a change in the magnetic field vector (magnitude and direction) which can be used to approximate the displacement angle of the contact pad 1805. In further alternative embodiments, a suitable pair of gyro ICs can be used to determine the position delta between the reference inner surface and the contact pad 1805.

[0122] Figure 19 is a flowchart illustrating an exemplary method 1900 for interacting with a client application that can be run using, for example, mobile device controllers 100, 500, 900, and / or 1200, according to embodiments of the present disclosure. In block 1905, a first controller module of the mobile device controller can engage with a first side of a user's mobile device. In block 1910, a second controller module of the mobile device controller can engage with a second side of the mobile device. The first and second sides can be located on opposing sides of the mobile device. In one embodiment, the first controller module can be elastically coupled to the second controller module, and the mobile device controller can contact the mobile device in a form-fitting configuration. In block 1915, communication can be initiated between the mobile device controller and a client application running on the mobile device. In block 1920, one or more mobile device controller characteristics can be transmitted from the mobile device controller to the client application. For example, one or more mobile device controller characteristics can be associated with characteristics of the mobile device controller. In block 1925, the client application can be modified based on one or more mobile device controller characteristics. In one embodiment, the client application can be modified by a data processor on the mobile device. In block 1930, the modified client application can be provided to a user in the mobile device. In one embodiment, the modified client application can be provided by a data processor on the mobile device. The user can interact with the modified client application using the mobile device controller.

[0123] Figure 20 is a block diagram of an exemplary computing device 2000 according to this embodiment, capable of performing one or more of the operations described herein. The computing device 2000 may be connected to other computing devices in a LAN, intranet, extranet, and / or the Internet. The computing device 2000 may operate in the capacity of a server machine in a client-server network environment, or in the capacity of a client in a peer-to-peer network environment. The computing device 2000 may be provided by a personal computer (PC), a set-top box (STB), a server, a network router, a switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specifies the actions to be taken by that machine. Furthermore, although only a single computing device 2000 is shown, the term “computing device” should also be interpreted to include any set of computing devices that individually or collectively execute a set of instructions (or sets of instructions) to perform the methods described herein.

[0124] An exemplary computing device 2000 may include computer processing devices 2002 (e.g., general-purpose processors, ASICs, etc.), main memory 2004, static memory 2006 (e.g., flash memory, etc.), and data storage devices 2008 that can communicate with each other via bus 2030. The computer processing devices 2002 may be provided by one or more general-purpose processing devices, such as microprocessors, central processing units, etc. In an exemplary example, the computer processing device 2002 may comprise a composite instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or a processor that implements a processor or combination of instruction sets, or a processor that implements a combination of instruction sets. The computer processing device 2002 may also comprise one or more dedicated processing devices, such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), and network processors. The computer processing device 2002 may be configured to perform the operations described herein in accordance with one or more aspects of this disclosure in order to perform the operations and steps described herein.

[0125] The computing device 2000 may further include a network interface device 2012 capable of communicating with the network 2014. The data storage device 2008 may include a machine-readable storage medium 2028 capable of storing one or more instruction sets, such as instructions for performing operations described herein, according to one or more aspects of the present disclosure. Instructions 2018 implementing the core logic instructions 2026 may also reside entirely or at least partially in the main memory 2004 and / or the computer processing device 2002 during execution by the computing device 2000, the main memory 2004, and the computer processing device 2002, which also constitute the computer-readable medium. Instructions may be further transmitted or received over the network 2014 via the network interface device 2012.

[0126] Although machine-readable storage medium 2028 is shown as a single medium in the illustrative examples, the term “computer-readable storage medium” should be interpreted to include a single or multiple mediums (e.g., a centralized or distributed database and / or associated caches and servers) that store one or more instruction sets. The term “computer-readable storage medium” should also be interpreted to include any medium that can store, encode, or carry instruction sets for machine execution, causing a machine to perform the methods described herein. Thus, the term “computer-readable storage medium” should be interpreted to include, but not be limited to, solid-state memory, optical media, magnetic media, and the like.

[0127] The subject matter and embodiments of operation described in this disclosure may be implemented in digital electronic circuits, or in computer software, firmware, or hardware, or one or more combinations thereof, including the structures disclosed herein and their structural equivalents. Embodiments of the subject matter described herein may be implemented as one or more modules of one or more computer programs, i.e., computer program instructions, encoded on a computer storage medium for execution by a data processing device or for controlling the operation of a data processing device. Alternatively or additionally, program instructions may be encoded in artificially generated propagating signals, such as machine-generated electrical, optical, or electromagnetic signals generated to encode information for transmission to a suitable receiving device for execution by a data processing device. The computer storage medium may be or may be a computer-readable storage device, a computer-readable storage board, a random-access or serial-access memory array or device, or one or more combinations thereof. Furthermore, although the computer storage medium is not a propagating signal, the computer storage medium may be a source or destination for computer program instructions encoded in artificially generated propagating signals. Computer storage media may also be one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices), or may be contained within them.

[0128] The operations described in this disclosure may be performed by a data processing device on data stored in or received from one or more computer-readable storage devices.

[0129] The term "data processing device" encompasses all kinds of devices, machines, and equipment for processing data, including, for example, programmable processors, computer processing devices, computers, systems on a chip, or a combination of the above. Computer processing devices may include one or more processors, such as FPGAs (Field Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits), central processing units (CPUs), or multi-core processors that may contain dedicated logic circuits. In addition to hardware, a device may also include code that makes up the execution environment for the computer program in question, such as processor firmware, protocol stacks, database management systems, operating systems, cross-platform runtime environments, virtual machines, or a combination of one or more of these. Devices and execution environments can realize a variety of different computing model infrastructures, such as web services, distributed computing, and grid computing infrastructures.

[0130] Computer programs (also known as programs, software, software applications, scripts, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative languages, procedural languages, or functional languages, and can be deployed in any form, including as standalone programs or as modules, components, subroutines, objects, or other units suitable for use in a computing environment. Computer programs may or may not correspond to files in a file system. A program may be part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language resource), a single file dedicated to the program in question, or multiple collaborative files (e.g., a file that holds one or more modules, subprograms, or parts of code). Computer programs may be deployed to run on one or more computers located at one site or distributed across multiple sites and interconnected by a communication network.

[0131] The processes and logic flows described herein may be executed by one or more programmable processors that execute one or more computer programs to perform actions by manipulating input data to produce outputs. The processes and logic flows may also be executed by dedicated logic circuits, such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits), and the devices may also be implemented as dedicated logic circuits.

[0132] Processors suitable for executing computer programs include, for example, both general-purpose and dedicated microprocessors, as well as any one or more processors in any type of digital computer. Generally, a processor will receive instructions and data from read-only memory, random-access memory, or both. Essential elements of a computer are a processor for performing actions according to instructions, and one or more memory devices for storing instructions and data. Generally, a computer will also include one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, optical disks, solid-state drives, etc., or will be operablely coupled to them to receive data from them, transfer data to them, or both. However, a computer is not required to have such devices. Furthermore, a computer can be incorporated into another device, to name just a few, such as a smartphone, mobile audio or media player, game console, Global Positioning System (GPS) receiver, or portable storage device (e.g., Universal Serial Bus (USB) flash drive). Devices suitable for storing computer program instructions and data include, for example, semiconductor memory devices such as EPROMs, EEPROMs, and flash memory devices; magnetic disks such as internal hard disks or removable disks; magneto-optical disks; and CD-ROMs and DVD-ROM disks, and all forms of non-volatile memory, media, and memory devices. Processors and memory may be complemented by or incorporated into dedicated logic circuits.

[0133] To provide user interaction, embodiments of the subject matter described herein may be implemented on a computer having a display device for displaying information to the user, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, and a keyboard and pointing device, such as a mouse, trackball, touchpad, or stylus, on which the user can provide input to the computer. User interaction may also be provided using other types of devices, for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or haptic feedback, and input from the user may be received in any form, including acoustic, voice, or haptic input. In addition, the computer may interact with the user by sending resources to and receiving resources from devices used by the user, for example, by sending a web page to a web browser on the user's client device in response to a request received from a web browser.

[0134] Embodiments of the subject matter described herein may be implemented as a computing system including, for example, a backend component as a data server, or a middleware component such as an application server, or a frontend component such as a client computer having a graphical user interface or a web browser on which a user can interact with the embodiments of the subject matter described herein, or as any combination of one or more such backend, middleware, or frontend components. Components of the system may be interconnected by digital data communications in any form or medium, such as communication networks. Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), internetworks (e.g., the Internet), peer-to-peer networks (e.g., ad-hoc peer-to-peer networks), and the like.

[0135] A computing system can include clients and servers. Clients and servers are generally remote from each other and typically interact via a communication network. The relationship between the client and server arises from computer programs running on each computer that have a client-server relationship with each other. In some embodiments, the server transmits data (e.g., an HTML page) to the client device (for example, to display data to a user interacting with the client device and to receive user input from the user). Data generated on the client device (e.g., the results of user interaction) can be received by the server from the client device.

[0136] One or more computer systems may be configured to perform a specific operation or action by installing software, firmware, hardware, or a combination thereof on the system that causes the system to perform an action while it is running. One or more computer programs may be configured to perform a specific operation or action by containing instructions that cause the data processing device to perform an action when executed by the device.

[0137] Throughout this disclosure, any reference to “one embodiment” or “embodiment” means a specific feature, structure, or characteristic described in relation to an embodiment included in at least one embodiment. Therefore, the appearance of the phrase “in one embodiment” or “in one embodiment” in various parts of this disclosure does not necessarily all refer to the same embodiment. In addition, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.”

[0138] While this disclosure includes details of many specific embodiments, these should not be construed as limitations on the scope of any invention or claimable, but rather as descriptions of features specific to particular embodiments of a particular invention. Certain features described in this disclosure in the context of separate embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented separately or in any suitable partial combination in multiple embodiments. Furthermore, features described above as acting in a particular combination may be initially claimed as such, but one or more features from a claimed combination may, in some cases, be removed from the combination, and the claimed combination may cover a partial combination or a variation of a partial combination.

[0139] Similarly, although the operations are shown in a specific order in the drawings, this should not be understood as requiring that such operations be performed in a specific or sequential order, or that all shown operations be performed, in order to achieve the desired result. In certain situations, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged in multiple software products.

[0140] Accordingly, specific embodiments of the subject matter are described. Other embodiments are within the scope of the following claims. In some cases, the actions described in the claims may be performed in a different order and still achieve the desired results. In addition, the processes shown in the accompanying drawings do not necessarily require the specific order or sequence shown to achieve the desired results. In certain embodiments, multitasking and parallel processing may be advantageous.

[0141] The above description of the exemplary embodiments of the present invention is not intended to be exhaustive or to limit the invention to the exact form disclosed. Specific embodiments and examples of the present invention are described herein for illustrative purposes, but various equivalent modifications are possible within the scope of the invention, as will be recognized by those skilled in the art. The terms “example” or “exemplary” are used herein to mean that they serve as examples, cases, or illustrations. Any aspect or design described herein as “example” or “exemplary” should not necessarily be construed as being preferable or advantageous to other aspects or designs. Rather, the use of the terms “example” or “exemplary” is intended to specifically present the concepts. Where used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless otherwise specified or as is evident from the context, “X includes A or B” is intended to mean either of the natural inclusive substitutions. That is, if X includes A, if X includes B, or if X includes both A and B, then “X includes A or B” satisfies any of the aforementioned cases. In addition, the articles “a” and “an” used in this application and the attached claims should generally be interpreted as meaning “one or more” unless otherwise specified or unless the context makes it clear that they refer to a singular form. Furthermore, throughout this specification, the use of the terms “one embodiment” or “one embodiment” or “one embodiment” or “one embodiment” is not intended to mean the same embodiment or embodiment unless otherwise stated. Furthermore, terms such as “first,” “second,” “third,” and “fourth” used herein mean labels for distinguishing different elements and do not necessarily imply order according to their numerical designation. Furthermore, any solid line or combination of solid lines shown in the drawings may alternatively be shown as a dotted line, and vice versa.

Claims

1. A mobile device controller, A first controller module configured to engage with a first side of a mobile device, A second controller module elastically coupled to the first controller module, the second controller module configured to engage with a second side of the mobile device opposite to the first side of the mobile device, such that the mobile device controller contacts the mobile device in a form-fitting configuration. A deployable bridge placed between the first controller module and the second controller module, wherein at least one of the first controller module or the second controller module includes at least one processor and a memory for storing instructions, and when an instruction is executed by the at least one processor, the at least one processor is sent to the at least one processor. The mobile device controller transmits one or more mobile device controller characteristics to the mobile device, wherein the one or more mobile device controller characteristics are associated with the characteristics of the mobile device controller, and the client application on the mobile device is modified based on the one or more mobile device controller characteristics so that the client application is provided to the user on the mobile device using a graphical user interface corresponding to the mobile device controller characteristics, and the user interacts with the modified client application using the mobile device controller. A deployable bridge that enables the execution of operations including A mobile device controller equipped with the following features.

2. The mobile device controller according to claim 1, wherein the first controller module is configured to receive a first user input for controlling the client application, and the second controller module is configured to receive a second user input for controlling the client application.

3. The mobile device controller according to claim 1, wherein the first controller module includes a first hinge structure, the first hinge structure is configured to extend from the first controller module and to engage with the first side of the mobile device when the first controller module is extended laterally away from the second controller module.

4. The mobile device controller according to claim 3, wherein the second controller module includes a second hinge structure, the second hinge structure being configured to extend from the second controller module and engage with a second side of the mobile device when the second controller module is extended laterally away from the first controller module.

5. The mobile device controller according to claim 1, wherein the deployable bridge includes a first elastic structure and a second elastic structure for adjusting the mobile device controller to fit mobile devices of different sizes, the first elastic structure being coupled between the first controller module and a first end of the deployable bridge, and the second elastic structure being coupled between the second controller module and a second end of the deployable bridge.

6. The operation described above is: To initiate communication between the mobile device controller and the client application running on the mobile device. The mobile device controller according to claim 1, further comprising:

7. The mobile device controller according to claim 6, wherein the commencement includes pairing the mobile device controller with the mobile device via a wireless communication protocol.

8. The mobile device controller according to claim 1, wherein at least one of the first controller module and the second controller module includes at least one button disposed thereon, the at least one button being configured to receive user input for controlling the client application.

9. The mobile device controller according to claim 1, wherein at least one of the first controller module and the second controller module includes a directional pad button located thereon, the directional pad button being configured to receive user input for controlling the client application.

Images