Mobile device controller system and method for interacting with client applications

Abstract

In one aspect, a first controller module (105) of the mobile device controller (100) can engage with a first side (301) of a user's mobile device (305). A second controller module (110) of the mobile device controller (100) can engage with a second side (315) of the mobile device (305). One or more mobile device controller properties associated with properties of the mobile device controller (100) can be transmitted from the mobile device controller (100) to the mobile device (305). A client application on the mobile device (305) can be modified by a first data processor based on the one or more mobile device controller properties.

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63 / 240,443, filed September 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 technology The mobile gaming space is crowded, and finding new breakout content opportunities presents a challenge for even the newest developers. Despite the content competition and the flexibility that touch interfaces offer, mobile gaming still lacks significant representation from the entire genre of time-tested games: retro and casual arcade. Retro and casual arcade games and game dynamics were originally designed to be played with physical input. Due to the need to add additional hardware, fragmentation in mobile handsets and a lack of vertical integration between controller manufacturers and content developers for this genre of game remain underrepresented in the mobile space. Summary of the Invention [Means for solving the problem]

[0003] overview A mobile device controller system and method for interacting with a client application is provided. Related systems, methods, apparatus, techniques, and articles are also described.

[0004] In one aspect, a first controller module of the mobile device controller can engage with a first side of a 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 properties associated with the properties 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 a first data processor based on the one or more mobile device controller properties. The modified client application can be provided to a 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 may be included in any workable combination. For example, communication between the mobile device controller and the mobile device may be initiated. For example, initiating 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 opposite sides of the mobile device, the first controller module may be resiliently coupled to the second controller module, and the mobile device controller may contact 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 controller module and the second controller module, and the first controller module may be slid toward the second controller module. For example, the mobile device can be placed in a portrait orientation when a first side of the mobile device is engaged by a first controller module and when a second side of the mobile device is engaged by a second controller module. For example, at least one of the first controller module and the second controller module can include at least one button disposed thereon and configured to receive user input for controlling the client application. For example, at least one of the first controller module and the second controller module can include a directional pad button disposed thereon and configured to receive user input for controlling the client application.

[0006] In another aspect, a mobile device controller is provided, the mobile device controller 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 the first side; and a deployable bridge interposed between the first controller module and the second controller module. At least one of the first controller module or the second controller module may include at least one processor and memory storing instructions, which, when executed by the at least one processor, cause the at least one processor to perform operations including transmitting, from the mobile device controller, one or more mobile device controller characteristics associated with the mobile device controller characteristics to a mobile device; 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 a user in the mobile device; and the user interacts with the modified client application using the mobile device controller.

[0007] One or more of the following features may be included in any workable combination. For example, the first controller module may be configured to receive a first user input for controlling the client application, and the second controller module may be configured to receive a second user input for controlling the client application. For example, the first controller module may include a first hinge structure configured to extend from the first controller module and engage with a first side of the mobile device when the first controller module is extended laterally away from the second controller module. For example, the second controller module may include a second hinge structure 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. For example, the deployable bridge may include a first elastic structure and a second elastic structure for adjusting the mobile device controller to fit different sizes of mobile devices, the first elastic structure may be coupled between the first controller module and a first end of the deployable bridge, and the second elastic structure may be coupled between the second controller module and a second end of the deployable bridge. For example, the operations may further include initiating communication between the mobile device controller and a client application running on the mobile device. For example, initiating may include pairing the mobile device controller with the mobile device via a wireless communication protocol. For example, the mobile device may be placed in a portrait orientation when a first side of the mobile device is engaged by the first controller module and when 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 disposed thereon and configured to receive user input for controlling the client application. For example, at least one of the first controller module and the second controller module may include a directional pad button disposed thereon and configured to receive user input for controlling the client application. The present invention provides, for example, the following items. (Item 1) Engaging a first controller module of the mobile device controller to a first side of a user's mobile device; engaging a second controller module of the mobile device controller with a second side of the mobile device; transmitting, from the mobile device controller, one or more mobile device controller characteristics to the mobile device, the one or more mobile device controller characteristics associated with characteristics of the mobile device controller; modifying, by a first data processor, a client application on the mobile device based on the one or more mobile device controller characteristics; providing, by the first data processor, the modified client application to the user in the mobile device, wherein the user interacts with the modified client application using the mobile device controller; A method comprising: (Item 2) Item 10. The method of item 1, further comprising initiating communication between the mobile device controller and the mobile device. (Item 3) Item 3. The method of item 2, wherein the initiating includes pairing the mobile device controller with the mobile device via a wireless communication protocol. (Item 4) Item 10. The method of item 1, wherein the first and second sides are located on opposite sides of the mobile device, the first controller module is resiliently coupled to the second controller module, and the mobile device controller contacts the mobile device in a form-fitting configuration. (Item 5) Item 10. The method of 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) Item 10. The method of 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; sliding the first controller module toward the second controller module; Item 1, the method of claim 1 further comprising: (Item 8) Item 10. The method of item 1, wherein the mobile device is placed in a portrait orientation 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 9) Item 10. The method of item 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 configured to receive user input for controlling the client application. (Item 10) Item 10. The method of item 1, wherein at least one of the first controller module and the second controller module includes a directional pad button disposed thereon, the directional pad button configured to receive user input for controlling the client application. (Item 11) 1. A mobile device controller, comprising: a first controller module configured to engage a first side of the mobile device; a second controller module configured to engage a second side of the mobile device, the second side being opposite the first side; and a deployable bridge interposed 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 storing instructions, the instructions, when executed by the at least one processor, causing the at least one processor to: transmitting, from the mobile device controller, one or more mobile device controller characteristics to the mobile device, the one or more mobile device controller characteristics being associated with characteristics of the mobile device controller; modifying a client application on the mobile device based on the one or more mobile device controller characteristics; providing the modified client application to the user in the mobile device; and the user interacting with the modified client application using the mobile device controller. Deployable bridges and A mobile device controller comprising: (Item 12) Item 12. The mobile device controller of 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) Item 12. The mobile device controller of item 11, wherein the first controller module includes a first hinge structure configured to extend from the first controller module and engage with the first side of the mobile device when the first controller module is extended laterally away from the second controller module. (Item 14) Item 14. The mobile device controller of item 13, wherein the second controller module includes a second hinge structure 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. (Item 15) Item 12. The mobile device controller of 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 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. (Item 16) The operation is Initiating communication between the mobile device controller and the client application running on the mobile device. Item 12. The mobile device controller of item 11, further comprising: (Item 17) Item 17. The mobile device controller of item 16, wherein the initiating includes pairing the mobile device controller with the mobile device via a wireless communication protocol. (Item 18) Item 12. The mobile device controller of item 11, wherein the mobile device is placed in a portrait orientation 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 19) Item 12. The mobile device controller of item 11, 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 configured to receive user input for controlling the client application. (Item 20) Item 12. The mobile device controller of item 11, wherein at least one of the first controller module and the second controller module includes a directional pad button disposed thereon, the directional pad button configured to receive user input for controlling the client application. [Brief explanation of the drawings]

[0008] BRIEF DESCRIPTION OF THE DRAWINGS The above embodiments will be more fully understood from the following detailed description taken in conjunction with the accompanying drawings, in which: The drawings are not drawn to scale, and for clarity, not every component is labeled in every drawing.

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

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

[0011] [Figure 3] FIG. 1 illustrates a mobile device controller in an engaged configuration with a mobile device.

[0012] [Figure 4] FIG. 1 is a block diagram illustrating an exemplary system for interacting with one or more client applications.

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

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

[0015] [Figure 7] FIG. 10 illustrates an alternative mobile device controller in a configuration engaged with a mobile device in portrait orientation.

[0016] [Figure 8] FIG. 10 illustrates an alternative mobile device controller in a configuration engaged with a mobile device in landscape orientation.

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

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

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

[0020] [Figure 9D] FIG. 9B is a rear, top-left perspective view of the mobile device controller of FIG. 9A.

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

[0022] [Figure 9F] FIG. 9B is a rear, bottom right perspective view of the mobile device controller of FIG. 9A.

[0023] [Figure 9G] FIG. 9B is a rear, bottom-left perspective view of the mobile device controller of FIG. 9A.

[0024] [Figure 9H] FIG. 9B is a front-bottom right perspective view of the mobile device controller of FIG. 9A.

[0025] [Figure 9I] FIG. 9B is a front-bottom left perspective view of the mobile device controller of FIG. 9A.

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

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

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

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

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

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

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

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

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

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

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

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

[0038] [Figure 11F] FIG. 11B is a rear, bottom right perspective view of the mobile device controller of FIG. 11A.

[0039] [Figure 11G] FIG. 11B is a rear, bottom-left perspective view of the mobile device controller of FIG. 11A.

[0040] [Figure 11H] FIG. 11B is a front-bottom right perspective view of the mobile device controller of FIG. 11A.

[0041] [Figure 11I] FIG. 11B is a front-bottom left perspective view of the mobile device controller of FIG. 11A.

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

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

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

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

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

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

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

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

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

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

[0052] [Figure 11T] FIG. 11B is a rear, bottom right perspective view of the mobile device controller of FIG. 11A.

[0053] [Figure 11U] FIG. 11B is a rear, bottom-left perspective view of the mobile device controller of FIG. 11A.

[0054] [Figure 11V] FIG. 11B is a front-bottom right perspective view of the mobile device controller of FIG. 11A.

[0055] [Figure 11W] FIG. 11B is a front-bottom left perspective view of the mobile device controller of FIG. 11A.

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

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

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

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

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

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

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

[0063] [Figure 13] FIG. 10 is a diagram of an alternative mobile device controller in a partially expanded configuration.

[0064] [Figure 14] FIG. 10 is a diagram of an alternative mobile device controller in a fully expanded configuration.

[0065] [Figure 15] FIG. 10 is a diagram of a translatable directional pad using a pointing stick with keyboard layout.

[0066] [Figure 16] FIG. 1 is a diagram of a translatable input surface for a keypad layout.

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

[0068] [Figure 18] FIG. 10 is a side view of a contact pad for a directional pad.

[0069] [Figure 19] 1 is a flowchart illustrating an exemplary method for interacting with a client application.

[0070] [Figure 20] FIG. 1 is a block diagram of an exemplary computing device that may perform one or more of the operations described herein, according to the present embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0071] Detailed Description Certain exemplary embodiments will now be described to provide a general understanding of the principles of the structure, function, manufacture, and use of the devices and methods disclosed herein. One or more examples of these embodiments are illustrated 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 only by the claims. Features illustrated or described in connection with one exemplary embodiment may be combined with features of other embodiments. Such modifications and variations are intended to be included within the scope of the present invention. Furthermore, in this disclosure, like-named components of embodiments generally have similar features, and therefore, within a particular embodiment, every feature of each like-named component is not necessarily described in detail.

[0072] The present invention relates to a mobile device controller system and method for interacting with a client application, including a decorative design for the mobile device controller as shown in and described in connection with the drawings. The mobile device controller can form-fit to a mobile device and provide physical inputs that allow a user to control, interact with, or otherwise engage with a client application running on the mobile device. The mobile device controller can include left and right controller modules split to be placed on either side of the mobile device. For maximum portability, the two halves of the mobile device controller can be connected by an adjustable bridge that can accommodate different sizes and orientations of mobile devices while folding when not in use. In some embodiments of the present invention, the bridge between the two controller modules can be centered on an inductive charging array with magnetic alignment features, including, for example, a circularly arranged, multi-orientation magnetic array. The adjustable bridge mechanism can deploy and retract from (or approximately from) the center or center of the mobile device controller so that the inductive charging array of the mobile device controller can be maintained substantially centered on the bridge. The centering action can be used to maintain alignment between the mobile device controller and the mobile device regardless of model and orientation. The mobile device controller can support any suitable button layout. For example, the button layout may be similar to a game console, with two analog sticks, a D-pad, four right input buttons, four shoulder buttons, and two triggers. Mobile device controllers may also include menu, function, and rear paddle inputs, although other combinations of buttons, triggers, paddles, joysticks, etc. are possible.

[0073] In some embodiments of the present invention, an inductive charging array with magnetic alignment features can address some of the problems found in conventional mobile device controller proposals. For example, an advantage of the present invention can be the ability to quickly and reliably attach and detach a mobile device to a mobile device controller with one hand using the inductive charging array connection. The magnetic centering action supported by the magnetic alignment feature of the inductive charging array can enhance the ability to easily rotate the mobile device into either portrait or landscape mode when attached to a mobile device controller. By not having to rely on a mechanical connection to hold the mobile device to the mobile device controller, the complexity of the holding mechanism can be reduced because it can accommodate mobile devices of various sizes without the need for continuous adjustment across different dimensions. Such advantages also allow for a much greater 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 configuration when not in use.

[0074] In some embodiments of the present invention, the benefits 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, near-field communication (NFC) or other similar circuitry integrated into the inductive charging array can be used to automatically initiate pairing of the mobile device controller via an appropriate wireless communication protocol when the mobile device is physically placed within the mobile device controller. Such a feature can eliminate the need for a user to manually initiate pairing. In some embodiments of the present invention, reverse wireless charging can be used to power the mobile device controller, reducing complexity and allowing the user to maintain battery charge. For example, the mobile device controller can be configured to be plugged into a power source, and the wireless charging connection can be reversed to power both the mobile device controller and simultaneously charge the mobile device for extended interaction or engagement sessions with client application(s). Alternatively, because 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, mobile device controllers can be designed to address where and how to hold a mobile phone during gameplay. While some controllers, particularly those repurposed from game consoles for mobile use, may leave users to find ways to enhance their mobile device while playing in less-than-ideal ways, most offer methods for holding a mobile phone with the controller. Generally, there are two primary solutions for holding a phone: form-fitting and stand-under. Form-fitting refers to a controller that is split in half, usually in landscape 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 bulky, only support certain mobile phone models, are expensive to manufacture, and may offer compromised ergonomics compared to console-style controllers. Controllers in this category are most often powered directly from the phone (e.g., via USB, a Lightning connector, or other similar connection port). Stand-under controllers may resemble those offered by game console manufacturers, with a clamp attached to the top to hold the mobile phone in place. While most stand-under controllers can be connected wirelessly, others offer a direct wired connection to the mobile phone. Such a configuration can also mean that the stand-under controller may contain its own battery power source and require charging by the user. Because they are modeled after game console-style controllers, stand-under controllers can be larger and are not designed for portability. In both form-fitting and freestanding controllers, mechanically holding the mobile phone to the controller can require the user to engage in a multi-step process to attach and detach the controller. The bulk added by the controller can mean that using a mobile device in portrait orientation (or for much of any other task other than gaming) is not ideal.Wireless controllers also must be paired upon first use and then manually turned on and off by the user before and after each subsequent gaming session. Embodiments of the present invention can overcome such drawbacks.

[0076] For purposes of explanation only and not limitation, this disclosure will reference a mobile digital game as an exemplary client application for illustrating 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) with which a user can interact or otherwise engage via physical input. Furthermore, for purposes of explanation only and not limitation, this disclosure will reference a mobile phone as an exemplary mobile device for illustrating various aspects of the present invention. However, the present invention may be used in and with any suitable type of mobile device, such as, for example, a smartphone, a tablet computer, etc.

[0077] FIG. 1 is a diagram of 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., a left controller) and a second controller module 110 (e.g., a right controller). The first controller module 105 and the second controller module 110 may be split 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). While shown as having approximately equal sizes, the first controller module 105 and the second controller module 110 may be similarly sized or differently sized 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 suitable number of arrow keys (e.g., up, down, left, right, etc.) in any suitable configuration. The second controller module 110 may include a second button layout 120. For example, second button layout 120 may include any suitable number of buttons (e.g., buttons A, B, X, Y, etc.) in any suitable configuration. First controller module 105 and second controller module 110 may each include or support any suitable button layout. For example, the button layout may be similar to a game console, such as having two analog sticks, a D-pad, four right input buttons, four shoulder buttons, and two triggers. First controller module 105 and second controller module 110 may additionally or alternatively include menu, function, and rear paddle inputs, although other combinations of buttons, triggers, paddles, joysticks, etc. are possible.

[0078] In an embodiment, the mobile device controller 100 may include an adjustable bridge structure 125 that may reside between and within the first controller module 105 and the second controller module 110. The adjustable bridge structure 125 may include a front surface 130 that may engage and fully contact the rear 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, which may form a structural component of the first controller module 105. The second pair of guide rails 140 may be permanently and fixedly attached to the second controller module 110 via a second anchor 150, which may form a structural component of the second controller module 110. The first pair of guide rails 135 and the second pair of guide rails 140 may be coupled to the adjustable bridge structure 125 using a suitable resilient structure (e.g., springs, etc.) that may be present within the adjustable bridge structure 125. The resilient structure within the adjustable bridge structure 125 may 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 and securely hold opposite sides of the mobile device in a form-fitting configuration. In such a configuration, the adjustable bridge structure 125 may engage with the back of the mobile device. In this manner, the mobile device controller 100 can accommodate mobile devices of different sizes and orientations.

[0079] In some implementations 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 a wired communication channel can extend in and through either or both of the first pair of guide rails 135 and the second pair of guide rails 140 and through the adjustable bridge structure 125 to enable 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 can 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 suitable electronic components to support wireless communication with mobile devices 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 may communicate wirelessly with each other and with mobile devices. In alternative embodiments, the first controller module 105 and the second controller module 110 may 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, if such rails are constructed of a solid or hollow structural material capable of carrying electrical signals (e.g., a suitable metal or other conductive material).

[0080] 2 is a diagram of 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 retract and rest or reside within the adjustable bridge structure 125 such 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 rest 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 rest 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 the size of a credit card or other compact configuration.

[0081] FIG. 3 is a diagram of the mobile device controller 100 in an engaged configuration with a mobile device 305. In an embodiment, the mobile device controller 100 can form-fit to the mobile device 305 and provide physical inputs that allow a user to control, interact with, or otherwise engage with client applications running on the mobile device 305. As previously described, 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 305, and then contracted to engage and securely hold opposite sides of the mobile device in a form-fitting configuration. For example, the first anchor 145 can contact and securely engage the first side 310 of the mobile device 305, and the second anchor 150 can contact and securely engage the second side 315 of the mobile device 305. The mobile device 305 is shown in a portrait orientation. When the mobile device is in landscape orientation, the first anchor 145 can contact and securely engage, for example, the third side 320 of the mobile device 305, while the second anchor 150 can contact and securely engage, 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 manner, the mobile device controller 100 can accommodate mobile devices of different sizes and orientations.

[0082] 1 , in some embodiments of the present invention, first controller module 105 and second controller module 110 may include appropriate electronic components to support at least wireless communication with a mobile device and control of client applications running on the mobile device via physical input provided by a user when interacting with first button layout 115 and second button layout 120. In such a configuration, either or both of first controller module 105 and second controller module 110 may include a battery component that provides power to mobile device controller 100. For example, if one of first controller module 105 and second controller module 110 includes a battery component, the controller module having the battery component can provide power to the other controller module via a power communication channel that can extend in and through either or both of first pair of guide rails 135 and second pair of guide rails 140 and through adjustable bridge structure 125. Additionally or alternatively, adjustable bridge structure 125 may include appropriate electronic and / or power components to support some or all of such functionality. For example, the adjustable bridge structure 125 may include either or both electronic and power components (e.g., a battery, etc.) to manage and power either or both of the first controller module 105 and the second controller module 110, and to control client applications running on the mobile device (e.g., via physical input provided by a 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 be in and through either or both of the first pair of guide rails 135 and the second pair of guide rails 140. In alternative embodiments, control 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, if such rails are constructed of a material capable of carrying electrical signals (e.g., a suitable metal or other conductive material).

[0083] In some embodiments of the present invention, the adjustable bridge structure 125 can include an inductive charging array with magnetic alignment features or other suitable electronic circuitry. The adjustable bridge structure 125 can deploy and retract from (or approximately from) the center or center of the mobile device controller 100 so that the mobile device controller's 100 inductive charging array can be maintained substantially centered within the mobile device controller 100. Such a centering action can 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 by way of limitation, MagSafe® is a technology from Apple Inc. that combines magnetic mounting, wireless charging, and NFC. From a charging perspective, MagSafe can be used to address alignment issues encountered with wireless chargers, whose efficiency decreases due to misalignment of the mobile device with the charger. To properly secure and orient accessories to the mobile device, MagSafe can employ an array of magnets (e.g., 18) arranged in a circle hidden beneath the surface of the mobile device, with an additional line magnet extending perpendicularly from 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. The MagSafe magnetic array allows 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 in its MagSafe accessories to help mobile devices identify what is connected, 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 device, a user can simply bring their mobile device into proximity to initiate pairing.

[0084] In some implementations of the present invention, additional configuration and playability features of the mobile device controller 100 can be supported with an inductive charging array integrated into the adjustable bridge structure 125. For example, upon initial setup, the mobile device controller 100 can initiate pairing of the mobile device controller 100 via an appropriate wireless communication protocol (e.g., Bluetooth, Wi-Fi, etc.), such as using NFC, which can be performed automatically when a mobile device is physically placed within the mobile device controller 100. Such a feature can eliminate the need for a user to manually initiate pairing. In one embodiment, to reduce complexity and allow a user to maintain battery charge for use with additional mobile devices, the mobile device controller 100 can be powered using reverse wireless charging. For example, the mobile device controller 100 can be configured to be plugged 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 can include an appropriate port to support charging from a power source. Once plugged in, the wireless charging connection can be reversed to power the mobile device controller 100 while charging the mobile device for extended interaction or engagement sessions with a client application running on the mobile device. Alternatively, because the mobile device controller 100 is not physically connected to a port on 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.

[0085] In one embodiment, the mobile device controller 100 can use NFC or the like to control various aspects of the mobile device and / or one or more client applications running on the mobile device. For example, upon initial setup, the mobile device controller 100 can use NFC or the like to communicate commands to the mobile device to 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 can include a first button layout 115 and a second button layout 120 with different layouts. In one embodiment, depending on the specific button layout of a particular mobile device controller 100, the mobile device controller 100 can use NFC or the like to communicate commands to the mobile device to 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 alternative embodiments, one or more client applications and / or appropriate support applications may be installed on the mobile device, which may be configured to support the mobile device controller 100 to control various aspects of the mobile device, the client applications or support applications themselves, and / or one or more other client applications executing on the mobile device. In such alternative embodiments, the mobile device controller 100 may communicate appropriate information (e.g., an identifier or other identifying information) to the client applications and / or support applications executing on the mobile device, such as using NFC. Upon receiving such information, the client applications and / or support applications may use the received information to generate and display a recommendation list (e.g., by accessing a list via a lookup table 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, in conjunction with such client applications and / or support applications, may tailor the user experience at the mobile device in any appropriate manner. For example, if user identification information is stored or otherwise maintained on the mobile device controller 100, such user identification information may be communicated to client applications and / or support applications, thereby allowing the user experience on the mobile device to be tailored to the user's preferences or otherwise customized. By way of example only and not limitation, the graphical user interface of a digital game may be personalized to display, for example, player incentives, special offers, advertisements, etc. to a player within or within the digital game.In embodiments, different player incentives, special offers, advertisements, etc. may be displayed to a player of a digital game based on characteristics associated with the mobile device controller 100, such as its type and / or configuration, although other characteristics are possible. Additionally or alternatively, the digital game may personalize the prizes, rewards, and / or gifts displayed or presented to a player, for example, in the digital game's associated gift store. For example, a player using one type of mobile device controller 100 may be presented with different prizes / rewards / gifts than may be presented to another player using a different type of mobile device controller 100. In this manner, a menu or list of prizes, rewards, and / or gifts may be tailored to each player or any player in the associated gift store displayed in the digital game. Additionally or alternatively, the digital game may personalize graphical information displayed to a user outside the digital game, such as, for example, advertisements or offers surfaced to a player on a mobile device outside the digital game. Other personalizations and customizations are possible, such as other suitable modifications to the graphical user interface within or outside the digital game.

[0087] In one embodiment, the client application and / or support application may be configured to support account profiles. A user can create an account profile with the client application and / or support application, which can be used to store user preferences, such as preferred client applications, whether the user wants to be presented with recommendations, and if so, the type and variety 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 their personalization, customization, preferences, and the like to the user. 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 and / or use the support application using NFC or the like to initiate 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 most recently played by the user. Such control by the mobile device controller 100 can occur 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). 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®. HID reports are binary data packets 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 HID reports is device-specific. HID report descriptors may be requested by the host during device enumeration. HID report descriptors describe the binary format of reports supported by the device. For purposes of illustration and not limitation, a HID report descriptor for the mobile device controller 100 may declare that it is a device of type “controller” (or the like), with a specific number of buttons, joysticks, triggers, etc. for input, and even a specific output (e.g., LEDs). Each time a button is pressed on the cell phone controller 100, the cell 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 to initiate the process. To compensate for different operating systems, slight differences in the firmware of the cell phone controller 100 are required to provide the correct HID report. These different firmware can be maintained and stored within the mobile device controller 100.However, different firmware may require the user to press a button combination to connect to a specific (host) profile upon pairing, for example. In some embodiments of the present invention, the mobile device controller 100 may support a custom Bluetooth Low Energy (BLE) service to facilitate easier pairing between the mobile device controller 100 and a mobile device with no (or minimal) user input. In some embodiments of the present invention, a client application and / or an appropriate support application installed on the mobile device may be configured to write appropriate information to the custom BLE service on the mobile device controller 100 to signal which operating system the mobile device uses so that an appropriate HID report can be sent from the mobile device controller 100. In this manner, the mobile device controller 100 may be automatically configured and paired with the mobile device without requiring additional user input when the mobile device controller 100 is engaged or otherwise fitted with 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, database, etc., 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 any suitable type of information to one or more remote servers, such as which mobile device controller 100 is being used by a user and at what time, which client application the user is interacting with or engaging with using the mobile device controller 100, the length of time the user uses the mobile device controller 100, the length of time the user interacts with or engages with the client application via the mobile device controller 100, the results or outcomes of user interactions with the client application via the mobile device controller 100 (e.g., to determine the user's skill rating), and other similar information that can be collected from users and 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 match players using mobile device controllers with other players also using mobile device controllers to help ensure competitive fairness and / or to implement anti-fraud / anti-cheat measures. For example, one player using a mobile device controller 100 may have an unfair advantage in a competition against another player not using a mobile device controller 100.In one embodiment, players in a competition may 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 the player; however, other characteristics of the mobile device controller 100, the player, the client application, etc. may be used for purposes of matching players for digital game competitions, etc. Additionally or alternatively, suitable machine learning / artificial intelligence techniques may be used to match players. For example, a machine learning model may be trained based on data from all players in a mobile game. The machine learning model may then be used to dynamically match players for a competition or tournament. The machine learning model may be updated or otherwise adapted as player characteristics evolve over time (e.g., changing mobile device controller 100 usage patterns, changing win-loss ratios and experience levels, preferences for certain games but not others, etc.).

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

[0091] 4, the server data processing module 416 can communicate with a player data database 418 and a game data database 420. The player data database 418 can include any suitable information related to one or more players of a digital game and their interactions with the digital game, such as, for example, whether a player is playing one or more digital games using a mobile device controller, and 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 at each digital game, the number of games lost at each digital game, the number of games played at each digital game, the score for each digital game, the time played at each digital game, etc.), player identification information (e.g., username), history of player connections to the system 400, player purchases, player achievements, player tasks, player interactions with other users (e.g., chat), player purchases, player deposits / withdrawals, player virtual item acquisition or use, other terms in the digital game, and other similar information. Database of game data 420 may include, for example, information about digital games implemented using system 400. Database of game data 420 may include, for example, information about each digital game, such as the virtual environment of each digital game, image, video, and / or audio data for each digital game, event data corresponding to previous, 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 server system 414. The software applications may relate to and / or provide a wide variety of functions and information, including, for example, entertainment (e.g., games, music, video, etc.), business (e.g., word processing, accounting, spreadsheets, etc.), news, weather, finance, sports, etc. In some cases, the software applications may provide digital games. The digital games may be or include, for example, 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, the digital game may be an asynchronous, competitive skill-based game in which players can compete with each other in the digital game, but need not play the digital game simultaneously. In an alternative embodiment, the 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 components thereof, can be accessed via a network 410 (e.g., the Internet) by users of client devices, such as mobile device A 402, mobile device B 404, mobile device C 406, ..., mobile device N 408, where N can be any suitable natural number. Each mobile device can be any suitable type of mobile electronic device, such as a smartphone, tablet computer, or the like, capable of executing the software application and communicating with the server system 414 via the network 410. Other mobile devices are 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 mobile device controllers can be used with each, all, or any combination of the mobile devices. In alternative embodiments, the player data database 418, the game data database 420, or any portions thereof, can be stored on one or more mobile devices. Additionally or alternatively, software components for the system 400 (e.g., the server data processing module 416), or any portions thereof, can reside on or be used to perform operations on one or more mobile devices.

[0094] FIG. 5 is a diagram of an alternative mobile device controller 500 in an open or unfolded configuration for interacting with a client application. The mobile device controller 500 may include a first controller module 505 (e.g., a left controller) and a second controller module 510 (e.g., a right controller). The first controller module 505 and the second controller module 510 may be split so that they can be placed on opposite sides of the mobile device (e.g., left-right or top-bottom, but not front-to-back). While shown as having approximately equal sizes, the first controller module 505 and the second controller module 510 may be similar or different sizes 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 suitable number and combination of buttons 520, one or more joysticks 525, one or more paddles 530, etc. in any suitable configuration. The second controller module 510 may include a second button layout 535. For example, the second button layout 535 may include any suitable number and combination of buttons 540, one or more joysticks 545, one or more paddles 550, etc. in any suitable configuration. The first controller module 505 and the second controller module 510 may each include or support any suitable button layout. For example, the button layout may be similar to a game console, such as having two analog sticks, a D-pad, four right input buttons, four shoulder buttons, and two triggers. The first controller module 505 and the second controller module 510 may additionally or alternatively include menu, function, and rear paddle inputs, although other combinations of buttons, triggers, paddles, joysticks, etc. are possible.

[0095] In an embodiment, the mobile device controller 500 may include an adjustable bridge structure 555 that may reside between and within the first controller module 505 and the second controller module 510. The adjustable bridge structure 555 may include a front surface 560 that may engage and fully contact the rear 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 be comprised of one or more guide rails, such as, 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. The first set of guide rails 565 may be permanently and fixedly attached to the first controller module 505 via first anchors 575, which may form a structural component of the first controller module 505. The second set of guide rails 570 may be permanently and fixedly attached to the second controller module 510 via second anchors 580, which may form a structural component of the second controller module 510. In some embodiments of the invention, the first anchors 575 and the second anchors 580 may be retracted (fully or partially) and rest within the first controller module 505 and the second controller module 510, respectively (e.g., using a suitable resilient structure). The first set of guide rails 565 and the second set of guide rails 570 may be coupled to the adjustable bridge structure 555 using a suitable resilient structure (e.g., springs, etc.), which may be present within the adjustable bridge structure 555.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 laterally or expanded, wrapped around the back of the mobile device, and then contracted to engage and securely hold opposite sides of the mobile device in a form-fitting configuration. 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 accommodate 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, etc.), and a 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 and through the 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 can 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 suitable electronic components to support wireless communication with mobile devices 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 may communicate wirelessly with each other and with mobile devices. In an alternative embodiment, the first controller module 505 and the second controller module 510 may 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, if such rails are constructed of a solid or hollow structural material capable of carrying electrical signals (e.g., a suitable metal or other conductive material).

[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 input provided by a 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 that provides power to 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 can provide power to the other controller module via a power communication channel that can extend through the adjustable bridge structure 555, within 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 functionality. For example, the adjustable bridge structure 555 may include one or both of electronic and power components (e.g., a battery, etc.) to manage and power either or both of the first controller module 505 and the second controller module 510 and to control client applications running on the mobile device (e.g., via physical input provided by a 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 alternative embodiments, control and / or power signals may be communicated using either or both of the first set of guide rails 565 and the second set of guide rails 570 themselves, if such rails are constructed of a material capable of carrying electrical signals (e.g., a suitable metal or other conductive material).

[0098] In some embodiments of the present invention, centered or substantially centered on the adjustable bridge structure 555 between the first controller module 505 and the second controller module 510 can be an inductive charging array 585 having a magnetic alignment feature (e.g., MagSafe, etc., or other suitable electronic circuitry) including multiple (e.g., three or more) orienting magnets 590 arranged, for example, in a circle, such as at the 3, 6, and 9 o'clock positions, although any suitable number, configuration, and arrangement of the orienting 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 such that the inductive charging array 585 of the mobile device controller 500 can be kept substantially centered within the mobile device controller 500. Such a centering action can 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] 6 is a diagram of 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 retract and rest or reside within the adjustable bridge structure 555 such that the first anchors 575 of the first controller module 505 can contact or substantially contact the second anchors 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 rest 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 the inner set of guide rails, and the second set of guide rails 570 can form the outer set of guide rails. In such an embodiment, in the folded configuration, the (inner) first set of guide rails 565 can rest between the (outer) second set of guide rails 570 within the adjustable bridge structure 555. In the folded configuration, the mobile device controller 500 can be approximately the size of a credit card, or the like. In an alternative embodiment, where the first set of guide rails 565 and the second set of guide rails 570 each include a single guide rail structure, the first set of guide rails 565 can rest retracted within first anchors 575 within the first controller module 505, and the second set of guide rails 570 can rest retracted within second anchors 580 within the second controller module 510.

[0100] FIG. 7 is a diagram of an alternative mobile device controller 500 in a configuration engaged with a mobile device 705 in portrait orientation. In an embodiment, the mobile device controller 500 can form-fit to the mobile device 705 and provide physical inputs that allow a user to control, interact with, or otherwise engage with a client application running on the mobile device 705. As previously described, 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, wrapped around the back of the mobile device 705, and then contracted to engage and securely hold opposite sides of the mobile device in a form-fitting configuration. For example, the first anchor 575 can contact and securely engage the first side 710 of the mobile device 705, and the second anchor 580 can contact and securely engage the second side 715 of the mobile device 705. The adjustable bridge structure 555 can engage the back of the mobile device 705.

[0101] 8 is a diagram of an alternative mobile device controller 500 in a configuration engaged with a mobile device 705 in a landscape orientation. When the mobile device 705 is in a landscape orientation, the first anchor 575 can contact and securely engage, for example, the third side 810 of the mobile device 705, and the second anchor 580 can contact and securely engage, 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 accommodate mobile devices of different sizes and orientations.

[0102] 9A through 9O illustrate several views of an alternative mobile device controller 900 in a closed or folded configuration for interacting with a client application. The mobile device controller 900 can form-fit into a mobile device and provide physical inputs that allow a user to control, interact with, or otherwise engage with a client application running on the mobile device. In embodiments, the mobile device controller 900 can include a linear deployment or sliding mechanism for use with a mobile device. The mobile device controller 900 can include a first controller module 905 (e.g., a left controller) and a second controller module 910 (e.g., a right controller). The first controller module 905 and the second controller module 910 can be split 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). While shown as having approximately equal sizes, the first controller module 905 and the second controller module 910 can be similar or different sizes depending on the desired configuration. The first controller module 905 may include a first button layout 915 on a first (e.g., top) surface of the first controller module 905. For example, the first button layout 915 may include any suitable number of buttons or keys (e.g., A, B, X, Y buttons and / or up, down, left, right, etc. arrows) in any suitable configuration. The second controller module 910 may include a second button layout 920 on a second (e.g., top) surface of the second controller module 910. For example, the second button layout 920 may include any suitable number of buttons or keys (e.g., A, B, X, Y buttons and / or up, down, left, right, etc. arrows) in any suitable configuration. 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 a game console, with two analog sticks, a D-pad, four right input buttons, four shoulder buttons, and two triggers. The first controller module 905 and the second controller module 910 may additionally or alternatively include menu, function, and rear paddle inputs, although other combinations of buttons, triggers, paddles, joysticks, etc. are possible.

[0103] In an embodiment, the mobile device controller 900 may include a deployable bridge structure 925 that may reside between and within the first controller module 905 and the second controller module 910. The deployable bridge structure 925 may include an outer deployment structure 930 that may include two separate sections or portions: a first outer deployment portion 930A that resides within the first controller module 905 and a second outer deployment portion 930B that resides within the second controller module 910. An inner deployment structure 940 may reside within the outer deployment structure 935 and between the first outer deployment portion 930A and the second outer deployment portion 930B. The outer deployment structure 930 and the inner deployment structure 940 may include two linear steps to allow deployment of the mobile device controller 900 to fit various mobile device sizes or orientations. The first outer deployment portion 930A may include a pair of first grooves 945 (each located on opposite sides of the first outer deployment portion 930A) to support lateral movement of the first outer deployment portion 930A. The second outer deployment portion 930B may include a pair of second grooves 950 (each located on opposite sides of the second outer deployment portion 930B) to support lateral movement of the second outer deployment portion 930B. The first controller module 905 may include a pair of first guide anchors 955 (each located on opposite inner sides of the first controller module 905). Each of the pair of first guide anchors 955 may include a first protrusion 960 of an appropriate height and width to engage with a respective one of the pair of first grooves 945 to support lateral movement of the first outer deployment portion 930A. In some embodiments of the invention, each of the first protrusions 960 may be any suitable oval or circular shape having a diameter equal to or slightly smaller than the width of the corresponding first groove 945 to facilitate free lateral movement of the first outer deployment portion 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 protrusion 970 of an appropriate height and width to engage with a respective one of the pair of second grooves 950 to support lateral movement of the second outer deployment portion 930B. In some embodiments of the invention, each of the second protrusions 970 may be any suitable oval or circular shape having a diameter equal to or slightly smaller than the width of the corresponding second groove 950 to facilitate free lateral movement of the second outer deployment portion 930B.

[0104] In some implementations of the present invention, the mobile device controller 900 can include a pair of flappers (or flaps) or grippers (or grips) for grasping and holding a mobile device, allowing the mobile device controller 900 to have a more compact size and a thinner design. For example, the flappers can be present within the body of the mobile device controller 900 and can be pre-installed to automatically rise when the first controller module 905 and the second controller module 910 are deployed apart and 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 can include a first flapper hinge 975 for engaging with a first side of the mobile device. The first flapper hinge 975 can be any suitable width between opposing interior sides of the first controller module 905, as well as any suitable height and thickness, depending, for example, on the thickness of the mobile device to be grasped, the desired amount of outward extension of the first controller module 905 when in a fully engaged position, etc. The first flapper hinge 975 may be coupled to an interior side of the first controller module 905 via a pair of first pivot joints 980 (each located on an opposite interior side 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 comprise a spring-loaded configuration that allows the first flapper hinge 975 to rise as the first controller module 905 is deployed laterally and to lower as the first controller module 905 is retracted laterally. The second controller module 910 may include a second flapper hinge 985 for engaging a second side of the mobile device.The second flapper hinge 985 can be any suitable width between opposing interior sides of the second controller module 910, as well as any suitable height and thickness, depending, for example, on the thickness of the mobile device to be gripped, the desired amount of outward 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 can be similar or identical in size and shape. In alternative embodiments, the first flapper hinge 975 and the second flapper hinge 985 can each be different sizes and shapes. The second flapper hinge 985 can be coupled to the interior side of the second controller module 910 via a pair of second pivot joints 990 (each located on opposing interior sides 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 include a spring-loaded configuration that allows the second flapper hinge 985 to rise as the second controller module 910 is deployed laterally and to fall as the second controller module 910 is retracted laterally.

[0105] In some implementations of the present invention, to support deployment and retraction of the mobile device controller 900, the deployable bridge structure 925 may be coupled to each of the first controller module 905 and the second controller module 910 using suitable resilient structures (e.g., springs, etc.). The resilient structures may be coupled to each end of the deployable bridge structure 925. Alternatively, the resilient structures may reside within and extend through the deployable bridge structure 925. For example, the resilient structure may be attached or otherwise secured to a first end 992 within the casing of the first controller module 905 and to a second end 994 within the casing of the second controller module 910. In one embodiment, the resilient structures may comprise one or more internal springs extending through or attached to each end of the deployable bridge structure 925. In an alternative embodiment, the resilient structure may comprise a spring-loaded reel fastened or otherwise secured to one end within the casing of the mobile device controller 900 (e.g., at the first end 992 of the first controller module 905). The end of a cord or line of the spring-loaded reel may extend through the deployable bridge structure 925 and be fastened or otherwise secured to an opposite end within the casing of the mobile device controller 900 (e.g., at the second end 994 of the second controller module 910). Alternatively, the first controller module 905 and the second controller module 910 may each include a spring-loaded reel attached or otherwise secured to the interior of the casing of the first controller module 905 and the second controller module 910 at opposite ends of the mobile device controller 900. The end of a cord or line of each spring-loaded reel may be attached or otherwise secured to the respective ends of the first outer extension 930A and the second outer extension 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 a mobile device, and then contracted (e.g., using the first flapper hinge 975 and the second flapper hinge 985) to engage and securely hold opposite sides of the mobile device in a form-fitting configuration. 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 accommodate 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 input provided by a 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 that provides power to 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 provide power to the other controller module via a power communication channel that may extend in and through the 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 appropriate switches (e.g., toggles, push buttons, selectors, joysticks, rotary switches, slides, etc.) for, for example, powering the mobile device controller 900 on and off, initiating pairing between the mobile device controller 900 and the mobile device, disconnecting the mobile device controller 900 from the mobile device, switching or otherwise cycling through client applications with which a user is interacting on the mobile device, or providing other similar functionality. For purposes of illustration only and not limitation, the second controller module 910 may include a switch 995 as shown in FIG. 9B , although the switch 995 may additionally or alternatively be located on the first controller module 905. In some embodiments of the present invention, the deployable bridge structure 925 may include appropriate electronic and / or power components to support some or all of such functionality.For example, the deployable bridge structure 925 can include an inductive charging array with magnetic alignment features (e.g., MagSafe, etc.) or other appropriate electronic circuitry. The deployable bridge structure 925 can deploy and retract from (or approximately from) the center or middle of the mobile device controller 900 so that the inductive charging array of the mobile device controller 900 can be maintained substantially centered within the mobile device controller 900. Such a centering action can 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 can 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 of FIG. 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 can 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 suitable 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 suitable 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] 10 is a diagram of the mobile device controller 900 in a partially unfolded configuration. In FIG. 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 a user pulls the first controller module 905 and the second controller module 910 apart, the first outer deployment portion 930A and the second outer deployment portion 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 along the pairs of first grooves 945 and second grooves 950, respectively, guided by the pairs of first protrusions 960 and second protrusions 970 of the pairs of first guide anchors 955 and second guide anchors 965, respectively. Additionally, first flapper hinge 975 and second flapper hinge 985 are exposed. As mentioned above, first flapper hinge 975 and second flapper hinge 985 can be pre-loaded to allow for automatic pop-up and retraction (e.g., using spring-loaded first pivot joint 980 and second pivot joint 990 pairs).

[0108] 11A-11AC are diagrams of the mobile device controller 900 in a fully deployed configuration. In FIGS. 11A-11AC, the first controller module 905 and the second controller module 910 are fully deployed laterally. As a result, the first outer deployment portion 930A and the second outer deployment portion 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 portion 940 of the deployable bridge structure 925 is also exposed. In some implementations of the invention, the deployable bridge structure 925 can include an inductive charging array having magnetic alignment features or other suitable electronic circuitry. In one embodiment, the inductive charging array can be disposed on a first surface 1105 of the inner deployment portion 940 that engages, otherwise contacts, or is adjacent to the back of the mobile device. Additionally, first flapper hinge 975 and second flapper hinge 985 are fully open and upright, extending substantially perpendicular to deployable bridge structure 925. In such a fully deployed configuration, a mobile device is ready to be attached to or inserted into mobile device controller 900. Mobile device controller 900 can then be retracted to engage and securely hold the opposing side of the mobile device in a form-fitting configuration. In this manner, mobile device controller 900 can accommodate mobile devices of different sizes and orientations.

[0109] FIG. 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 into a mobile device and provide physical inputs that allow a user to control, interact with, or otherwise engage with a client application running on the mobile device. In some implementations of the present invention, the mobile device controller 1200 can include a multi-bar deployment mechanism for use with a mobile device. For purposes of illustration and not limitation, FIG. 12 shows a four-bar deployment mechanism for the mobile device controller 1200 (i.e., four pairs of swing bars, each pair located on opposite insides of the casing, for a total of eight swing bars), although configurations with fewer or more than four bars can also be used. The mobile device controller 1200 can include a first controller module 1205 (e.g., a left controller) and a second controller module 1210 (e.g., a 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). While shown as having approximately equal sizes, the first controller module 1205 and the second controller module 1210 may be similar or different sizes depending on the desired configuration. The first controller module 1205 may include a first button layout 1215 on a first (e.g., top) side of the first controller module 1205. For example, the first button layout 1215 may include any suitable number of buttons or arrow keys (e.g., A, B, X, Y buttons, and / or up, down, left, right, etc. arrows) in any suitable configuration. The second controller module 1210 may include a second button layout 1220 on a second (e.g., top) side of the second controller module 1210.For example, the second button layout 1220 may include any suitable number of buttons or keys (e.g., A, B, X, Y buttons, and / or up, down, left, right, etc. arrows) in any suitable configuration. The first controller module 1205 and the second controller module 1210 may each include or support any suitable button layout and / or keys. For example, the button layout may be similar to a game console, such as having two analog sticks, a D-pad, four right input buttons, four shoulder buttons, and two triggers. The first controller module 1205 and the second controller module 1210 may additionally or alternatively include menu, function, and rear paddle inputs, although other combinations of buttons, triggers, paddles, joysticks, etc. are possible.

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

[0111] In one embodiment, the second extendable portion 1225B includes a pair of third swing arms 1260 (each located on opposite sides of the second extendable portion 1225B). The pair of third swing arms 1260 may be coupled to the second extendable portion 1225B via a pair of fifth pivot joints 1265 (each located on opposite sides of the second extendable portion 1225B) that allow upper portions of the pair of third swing arms 1260 to rotate about an axis. The second extendable 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 opposite sides of the second extendable portion 1225B) that allow lower portions of the pair of third swing arms 1260 to rotate about an axis. The second extendable portion 1225B includes a pair of fourth swing arms 1275 (each located on opposite sides of the second extendable portion 1225B). The pair of fourth swing arms 1275 may be coupled to the second extendable portion 1225B via a pair of seventh pivot joints 1280 (each located on opposite sides of the second extendable portion 1225B) that allow upper portions of the pair of fourth swing arms 1275 to rotate about an axis. The second extendable portion 1225B may further be 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 opposite sides of the second extendable portion 1225B) that allow lower portions 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 can be coupled or otherwise attached via a pair of guide rails 1290 (although more than one or two guide rails 1290 can be used) that can extend through the first expandable portion 1225A and the second expandable portion 1225B. In some embodiments of the invention, the pair of guide rails 1290 are not directly coupled to either the first controller module 1205 or the second controller module 1210, which can allow the expandable bridge structure 1225 (via their respective swing arms) to swing freely within the casing of the mobile device controller 1200 when the first controller module 1205 and the second controller module 1210 are extended apart. In one embodiment, one or both of the pair of guide rails 1290 can comprise a rigid or semi-rigid hollow structure (e.g., a tube). A suitable resilient structure (e.g., a spring, etc.) can be present either internally or externally along the length (all or part) of one or both of the pair of guide rails 1290. In alternative embodiments, one or both of the pair of guide rails 1290 can include a rigid or semi-rigid solid structure. A suitable resilient structure (e.g., a spring, etc.) can be present externally along the length (all or part) of one or both of the pair of guide rails 1290. For example, a suitable resilient structure can be present externally and fixed around each end of the pair of guide rails 1290, with the other end of the suitable resilient structure being fixed 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 itself can be equipped with a suitable resilient structure (e.g., a spring, etc.). In each of the aforementioned embodiments, the first expandable portion 1225A and the second expandable portion 1225B can be attached along the pair of guide rails 1290 and coupled to a suitable resilient structure.A suitable elastic structure can allow the first controller module 1205 and the second controller module 1210 to be pulled apart laterally or expanded, wrapped around the back of a mobile device, and then contracted to engage and securely hold the opposing side of the mobile device in a form-fitting configuration. 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 accommodate mobile devices of different sizes and orientations.

[0113] In some implementations of the present invention, the mobile device controller 1200 can include a pair of flappers for gripping and holding a mobile device, allowing the mobile device controller 1200 to have a more compact size and a thinner design. For example, the flappers can be present within the body of the mobile device controller 1200 and can be pre-installed to allow the flappers to automatically rise when the first controller module 1205 and the second controller module 1210 are extended apart and to automatically retract and lower into the body when the first controller module 1205 and the second controller module 1210 are contracted together. According to one embodiment of the present invention, the first controller module 1205 can include a first flapper hinge 1292 for engaging with a first side of the mobile device. The first flapper hinge 1292 can be any suitable width between opposing sides of the first extendable portion 1225A and any suitable height and thickness, depending, for example, on the thickness of the mobile device to be gripped, the desired amount of outward extension of the first controller module 1205 when in a fully engaged position, etc. The first flapper hinge 1292 may be coupled to the first extendable portion 1225A via a pair of first pivot joints 1294 (each located on opposite sides of the first extendable 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 comprise a spring-loaded configuration that allows the first flapper hinge 1292 to rise as the first controller module 1205 is extended laterally and to lower as the first controller module 1205 is contracted laterally. The second controller module 1210 may include a second flapper hinge 1296 for engaging a second side of the mobile device.The second flapper hinge 1296 can be any suitable width between opposite sides of the second extendable portion 1225B, as well as any suitable height and thickness, depending, for example, on the thickness of the mobile device to be gripped, the desired amount of outward expansion of 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 can be similar or identical in size and shape. In alternative embodiments, the first flapper hinge 1292 and the second flapper hinge 1296 can each be different in size and shape. The second flapper hinge 1296 can be coupled to the second extendable portion 1225B via a pair of second pivot joints 1298 (each located on opposite sides of the second extendable 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 include a spring-loaded configuration that allows the second flapper hinge 1296 to rise as the second controller module 910 is laterally extended and to fall as the second controller module 910 is laterally contracted.

[0114] The first controller module 1205 and the second controller module 1210 can 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 input provided by a 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 can include a battery component that provides 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 can provide power to the other controller module via a power communication channel that can extend in and through the expandable bridge structure 1225 (e.g., through one or both of a pair of guide rails 1290). Additionally or alternatively, the extendable bridge structure 1225 may include appropriate electronic and / or power components to support some or all of such functionality. In some embodiments of the present invention, the extendable bridge structure 1225 may include an inductive charging array with magnetic alignment features (e.g., MagSafe, etc., 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 extendable portion 1225A and the second extendable portion 1225B.The extendable bridge structure 1225 can deploy and retract from (or approximately 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 extendable portion 1225A and the second extendable portion 1225B) can be maintained at, near, or around the center of the mobile device controller 1200. Such a centering action can 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 appropriate electronic circuitry) can 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 of FIG. 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 can extend into and through the 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 can include suitable 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 can include suitable 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 can wirelessly communicate with each other and with a mobile device.

[0115] 13 is a diagram of the mobile device controller 1200 in a partially expanded configuration. In FIG. 13, the first controller module 1205 and the second controller module 1210 are extended laterally toward each other, partially exposing the first and second expandable portions 1225A and 1225B of the expandable bridge structure 1225. When a user pulls the first and second controller modules 1205 and 1210 apart, the first and second expandable portions 1225A and 1225B begin to extend from the casings of the first and second controller modules 1205 and 1210 along a pair of guide rails 1290. The first extendable portion 1225A extends by rotating or swinging via a first pair of swing arms 1230 and a second pair of swing arms 1245 (about respective pairs of first pivot joint 1235, second pivot joint 1240, third pivot joint 1250, and fourth pivot joint 1255) along a pair of guide rails 1290. The second extendable portion 1225B extends by rotating or swinging via a third pair of swing arms 1260 and a fourth pair of swing arms 1275 (about respective pairs of fifth pivot joint 1265, sixth pivot joint 1270, seventh pivot joint 1280, and eighth pivot joint 1285) along a pair of guide rails 1290. Additionally, the first flapper hinge 1292 and the second flapper hinge 1296 are exposed and partially elevated. As described above, the first flapper hinge 1292 and the second flapper hinge 1296 can be pre-loaded to allow them to automatically raise and retract (e.g., using a spring-loaded pair of first pivot joints 1294 and a spring-loaded pair of second pivot joints 1298).

[0116] FIG. 14 is a diagram of the mobile device controller 1200 in a fully extended configuration. In FIG. 14, the first controller module 1205 and the second controller module 1210 are fully deployed laterally. As a result, the first extendable portion 1225A and the second extendable portion 1225B of the extendable bridge structure 1225 are extended from the casings of the first controller module 1205 and the second controller module 1210, respectively. In some implementations of the invention, the extendable bridge structure 1225 can include an inductive charging array having magnetic alignment features or other suitable electronic circuitry. In one embodiment, the inductive charging array can be disposed on a first surface 1405 of the extendable bridge structure 1225 that engages, otherwise contacts, or is adjacent to the back surface of the mobile device (e.g., a first portion of the circuitry present in the first extendable portion 1225A and a second portion of the circuitry present in the second extendable portion 1225B). Arrow 1410 indicates the position and movement of extendable bridge structure 1225, which is swung near the bottom of the casing of mobile device controller 1200 (via each pair of first swing arm 1230, second swing arm 1245, third swing arm 1260, and fourth swing arm 1275). First flapper hinge 1292 and second flapper hinge 1296 are fully open and upright, extending substantially perpendicular to extendable bridge structure 1225. In such a fully deployed configuration, a mobile device is ready to be attached to or inserted into mobile device controller 1200. Mobile device controller 1200 can then be retracted to engage and securely hold the opposing side of the mobile device in a form-fitting configuration. In this manner, 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 suitable number of buttons and / or keys in any suitable configuration within the button layout of their respective controller modules. Different structures and mechanisms can be used for the buttons and / or keys, as well as the button layout, to support additional functionality. For example, the directional pad ("D-pad") position sensing mechanism of the present invention can resolve two previously mutually exclusive controller layouts—the traditional D-pad and the analog stick—into a single, unified control mechanism. In embodiments, the same layout can be used for the ABXY input button side of the mobile device controller, thereby enabling a more compact layout and dual analog stick inputs in a space previously not possible with traditional layouts. In addition to enabling more compact packaging for the mobile device controller, such a hybrid analog button layout can also offer the potential for improved playability. For example, by locating the analog stick and button on essentially the same surface, such a mechanism can enable actuation of button inputs (e.g., ABXY) while maintaining inputs on the analog "stick."

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

[0119] FIG. 16 is a diagram of a translatable input surface for a keypad layout, according to one embodiment of the present invention. In FIG. 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 detent 1620 having a generally circular configuration that may be located at the center of the set of arrow keys 1610. The set of buttons 1615 may include a second detent 1625 having a generally circular configuration that may 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 periphery that may enable clicking on the Z-axis via the contact points 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 translational input. A similar configuration can be used for the set of buttons 1615. In one embodiment, the set of buttons 1615 can be attached to a floating plate 1640 having a periphery that can enable 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 translational input. A moderate 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, with limited travel.

[0120] 17A and 17B are diagrams of 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 FIG. 17A . The radial layout 1705 can include a plurality of metal fingers 1710. A corresponding plurality of metal contacts 1715 can reside beneath each of the plurality of metal fingers 1710. In such an embodiment, the plurality of metal fingers 1710 in the radial layout 1705 can be used to form a closed electrical connection 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 a corresponding one or more of the plurality of metal contacts 1710). By knowing which channels form a closed connection, the present invention can determine in which direction the directional pad 1720 was actuated. In an alternative embodiment, shown in FIG. 17B , a plurality of individual curved metal fingers 1725 can be arranged and spaced substantially equally around the circumference of the directional pad 1730. One or more appropriate electrical contacts (not shown) can be positioned beneath each of the plurality of individual curved metal fingers 1725. In such an alternative embodiment, 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 individual curved metal fingers 1725 to make electrical contact with one or more corresponding underlying metal contacts). By knowing which channels form a closed connection, the present invention can determine in which direction the directional pad 1730 was actuated. In either embodiment, the closed connection can also be used as a magnitude input. For example, a deformable material such as TPE (thermoplastic elastomer) or silicone can be used above the section that presses against the contacts. The number of contacts being pressed can be measured, from which a general direction can be determined by averaging the orientation of the contacts around a circle. In FIGS. 17A and 17B, the client application can be configured to report the required fidelity of directionality required for a proper user experience.For purposes of example only and not limitation, a client application may report, for example, 4 / 8 / 360 point directionality, so that if a client application only requires four directions (e.g., up, down, left, and right), presses or touches in other directions will not generate erroneous input, but will allow the client application to use the directional pad (e.g., the center portion of the directional pad) in a manner similar to an analog stick with 360 degrees of freedom.

[0121] FIG. 18 is a side view of a contact pad 1805 for a directional pad 1800, according to one embodiment of the present invention. In FIG. 18 , for client applications that can accept up, down, left, and right input via the directional pad 1800, a traditional button membrane 1810 and contact switch configuration can be used. For client applications that can use analog input, two distance sensors 1815 and 1820 can be used to detect deflection in 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 to ensure predictable movement of the contact pad 1805. In one embodiment, a magnet 1830 can be placed above a Hall effect sensor 1835 on the back of the printed circuit board assembly (PCBA) on one axis (either the X or Y axis) and 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 displacement in the X and Y axes, which can be used to calculate a directional vector with the magnitude of a key press on the contact pad 1805. In the embodiment shown in FIG. 18 , spring fingers 1840 and 1845 off each arm of the contact pad 1805 can be used to prevent the contact pad 1805 of the directional pad 1800 from floating within the housing. Each spring finger 1840 and 1845 can be slightly pre-loaded in a starting position. The button membrane 1810 can be slightly pre-loaded in opposite directions (1850 and 1855) to hold the contact pad 1805 firmly in place. Guides 1860 and 1865 on either side 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 is located 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 with the contact pad 1805.In such an alternative embodiment, the Hall Effect sensor can return a change in magnetic field vector (magnitude and direction) that can be used to approximate the displacement angle of the contact pad 1805. In a further alternative embodiment, a pair of suitable gyro ICs can be used to determine the position delta between the reference inner surface and the contact pad 1805.

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

[0123] FIG. 20 is a block diagram of an exemplary computing device 2000 that can perform one or more of the operations described herein, according to the present embodiments. The computing device 2000 can be connected to other computing devices in a LAN, an intranet, an extranet, and / or the Internet. The computing device 2000 can 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 can be provided by a personal computer (PC), a set-top box (STB), a server, a network router, switch, or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by the machine. Furthermore, while only a single computing device 2000 is shown, the term “computing device” should also be interpreted to include any collection of computing devices that individually or together execute a set (or sets) of instructions to perform the methods described herein.

[0124] The exemplary computing device 2000 may include a computer processing device 2002 (e.g., a general-purpose processor, an ASIC, etc.), a main memory 2004, a static memory 2006 (e.g., a flash memory, etc.), and a data storage device 2008, which may communicate with each other via a bus 2030. The computer processing device 2002 may be provided by one or more general-purpose processing devices, such as a microprocessor, a central processing unit, etc. In an illustrative example, the computer processing device 2002 may comprise a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets or a processor implementing a combination of instruction sets. The computer processing device 2002 may also comprise one or more special-purpose processing devices, such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), a network processor, etc. The computer processing device 2002 may be configured to perform the operations described herein in accordance with one or more aspects of the present disclosure to perform the operations and steps described herein.

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

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

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

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

[0129] The term "data processing apparatus" encompasses all kinds of apparatus, devices, and machines for processing data, including, by way of example, a programmable processor, a computing device, a computer, a system-on-chip, or a plurality or combination of the above. A computing device may include one or more processors, which may include special-purpose logic circuits, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a central processing unit (CPU), or a multi-core processor. In addition to hardware, an apparatus may also include code that creates an execution environment for the computer program in question, such as code constituting processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or one or more combinations thereof. The apparatus and execution environment may implement a variety of different computing model infrastructures, such as web services, distributed computing, and grid computing infrastructures.

[0130] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted, declarative, procedural, or functional, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may or may not correspond to a file in a file system. A program may be stored as part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language resource), in a single file dedicated to the program in question, or in multiple cooperating files (e.g., files storing one or more modules, subprograms, or portions of code). A computer program can be deployed to run on one computer or on multiple computers located at one site or distributed across multiple sites and interconnected by a communications network.

[0131] The processes and logic flows described in this disclosure may be performed by one or more programmable processors executing one or more computer programs to perform actions by manipulating input data and generating output. The processes and logic flows may also be performed by, and an apparatus may also be implemented as, special purpose logic circuitry, such as, for example, an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

[0132] Processors suitable for executing a computer program include, by way of example, both general-purpose and special-purpose microprocessors, as well as any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random-access memory, or both. The essential elements of a computer are a processor for performing actions in accordance with 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 be operatively coupled to receive data from or transfer data to them, or both. However, a computer need not have such devices. Furthermore, a computer may be incorporated into another device, such as a smartphone, a mobile audio or media player, a game console, a global positioning system (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), to name just a few. Suitable devices for storing computer program instructions and data include, by way of example, all forms of non-volatile memory, media, and memory devices, including semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0133] To provide for interaction with a user, embodiments of the subject matter described herein may be implemented on a computer having a display device, such as a CRT (cathode ray tube), LCD (liquid crystal display) monitor, etc., for displaying information to the user, and a keyboard and pointing device, such as a mouse, trackball, touchpad, stylus, etc., by which the user can provide input to the computer. Other types of devices may also be used to provide interaction with the user; for example, feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback, and input from the user may be received in any form, including acoustic, speech, or tactile input. Additionally, 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 the web browser.

[0134] Embodiments of the subject matter described in this disclosure may be implemented in a computing system that includes a back-end component, e.g., a data server, or includes a middleware component, e.g., an application server, or includes a front-end component, e.g., a client computer having a graphical user interface or web browser through which a user can interact with embodiments of the subject matter described in this disclosure, or any combination of one or more such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication, e.g., a communications network. Examples of communications 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), etc.

[0135] A computing system may include clients and servers. Clients and servers are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some embodiments, a server transmits data (e.g., HTML pages) to the client devices (e.g., for the purpose of displaying the data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., the result of a user interaction) can be received from the client device at the server.

[0136] One or more computer systems may be configured to perform particular operations or actions by installing software, firmware, hardware, or a combination thereof on the system that causes the system to perform the actions during operation. One or more computer programs may be configured to perform particular operations or actions by including instructions that, when executed by a data processing device, cause the device to perform the actions.

[0137] References throughout this disclosure to "one embodiment" or "an embodiment" mean a particular feature, structure, or characteristic described in connection with an embodiment that is included in at least one embodiment. Thus, the appearances of the phrase "in one embodiment" or "in an embodiment" in various places throughout this disclosure are not necessarily all referring to the same embodiment. Additionally, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or."

[0138] While the present disclosure contains many specific implementation details, these should not be construed as limitations on the scope of any invention or what may be claimed, 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 can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, while features may be described above as acting in particular combinations and initially claimed as such, one or more features from a claimed combination may, in some cases, be deleted from the combination, and the claimed combination may be directed to a subcombination or a variation of the subcombination.

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

[0140] Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous.

[0141] The above description of illustrated embodiments of the invention is not intended to be exhaustive or to limit the invention to the precise form disclosed. While specific embodiments and examples of the invention have been described herein for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the art will recognize. The terms "example" or "exemplary" are used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as "example" or "exemplary" should not necessarily be construed as preferred or advantageous over other aspects or designs. Rather, use of the term "example" or "exemplary" is intended to specifically present the concept. As 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 clear from context, "X includes A or B" is intended to mean any of the natural inclusive permutations. That is, if X includes A, if X includes B, or if X includes both A and B, then "X includes A or B" is satisfied in any of the foregoing cases. Additionally, the articles "a" and "an" used in this application and the appended claims should generally be construed to mean "one or more" unless otherwise specified or unless the singular form is clearly intended from the context. Furthermore, the use of the terms "one embodiment" or "one embodiment" or "one implementation" or "one embodiment" throughout is not intended to refer to the same embodiment or implementation unless so stated. Furthermore, terms such as "first," "second," "third," and "fourth," as used herein, are intended as labels to distinguish different elements and do not necessarily imply an 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. Engaging a first controller module of the mobile device controller to a first side of the user's mobile device; engaging a second controller module of the mobile device controller with a second side of the mobile device and contacting the mobile device with an inductive charging array, the inductive charging array comprising a plurality of magnets configured to align the mobile device with charging coils of the inductive charging array, the plurality of magnets further configured to allow the mobile device to rotate to a portrait mode or a landscape mode while in contact with the inductive charging array; the first controller module is resiliently coupled to the second controller module via a deployable bridge, the deployable bridge configured to deploy and retract to maintain the mobile device and the inductive charging array in a centered position between the first controller module and the second controller module; and the mobile device controller contacting the mobile device in a form-fitting configuration; transmitting, from the mobile device controller, one or more mobile device controller characteristics to the mobile device, the one or more mobile device controller characteristics associated with characteristics of the mobile device controller; modifying, by a first data processor, a client application on the mobile device based on the one or more mobile device controller characteristics; providing, by the first data processor, the modified client application to the user at the mobile device, wherein the user interacts with the modified client application using the mobile device controller; A method comprising:

2. The method of claim 1 , further comprising initiating communication between the mobile device controller and the mobile device.

3. The method of claim 2 , wherein the initiating includes pairing the mobile device controller with the mobile device via a wireless communication protocol.

4. The method of claim 1 , wherein engaging the first controller module with the mobile device comprises sliding the first controller module away from the second controller module.

5. 10. The method of claim 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.

6. disengaging the mobile device from the first controller module and the second controller module; sliding the first controller module toward the second controller module; The method of claim 1 further comprising:

7. 10. The method of 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 configured to receive user input for controlling the client application.

8. 10. The method of claim 1, wherein at least one of the first controller module and the second controller module includes a directional pad button disposed thereon, the directional pad button configured to receive user input for controlling the client application.

Images