I am still in the process of ironing out how I want my control scheme, but when looking for a web browser to run in Gaming Mode on my Steam Deck that worked well (Firefox was being funky when run in Gaming Mode/Big Picture) I experimented a little bit with Qutebrowser. https://qutebrowser.org/doc/quickstart.html [https://qutebrowser.org/doc/quickstart.html] Edit figured out how to share steam controller profiles, it is under the gear icon -> layout details, here is my draft vim/qutebrowser profile, try it out and let me know what you think! steam://controllerconfig/2919876185/3227309282 Qutebrowser is downloadable from the Discover package manager in Desktop Mode on the Steam Deck (then find Qutebrowser in start menu ->right click add to steam). Qutebrowser is designed for a linux window manager like I3 where you don’t really use a mouse much, everything in Qutebrowser is meant to be navigated with keyboard commands, no mouse required in the style of Vim keyboard commands. lt also prioritizes using screen real estate efficiently which is a boon for the Steam Deck. Like Vim, Qutebrowser has modes, an input mode (entered by pressing the i key) where you can enter text normally and a navigation mode (entered by pressing escape) that you use the keyboard letters to navigate and input web browser commands. In my control scheme you simply press the menu button to toggle between input and navigation modes. While this might initially seem like the last software on the planet you would want to try to adapt to using with the Steam Deck’s onboard controls, the wisdom of Vim-style keybindings mean that almost every important function in the software is kept to the letters on the main keyboard, i.e. a-z. We can build a nice control scheme with the idea of mapping all the web browser controls to the steam deck while simultaneously mapping letters a-z to the steam deck… 1. The hjkl keys as up/down left/right navigation in vim naturally map to the left joystick, holding shift (long press R1 bumper) and hitting these keys navigates to previous page/next page/tab to the left/tab to the right 2. the entire top row of letters on the keyboard can be assigned to a touch menu on the left trackpad and the entire third row of letters can be assigned to a touch menu on the right trackpad. 3. The shift key can be mapped to long pressing the R1 bumper. 4. That leaves 5 letters remaining, put f aside and map a s d g to the back buttons of the steam deck. Backspace maps naturally to the x facebutton on the steam deck, the a facebutton to Enter and the b facebutton to Spacebar. 5. Finally, the last letter f can be mapped to the y facebutton on the Steam Deck. In qutebrowser f is an important key as it prompts what are called hints. When you press f you see something like this… [https://sopuli.xyz/pictrs/image/d2e9017f-2427-49a0-ba4b-e4c4253b160e.webp] If you input a sequence of keys shown, Qutebrowser will navigate the cursor to that spot and left click. The really nice accident of this Steam Deck control scheme is that Qutebrowser by default only uses letters that are mapped to physical buttons on the Steam Deck (hjkl asdf and g) in this Steam Controller configuration. With f bound to the y facebutton on the Steam Deck, it is natural to bind a similar command / that allows to search on the page (bound to long pressing the y facebutton). Clicking the leftstick inputs o which opens up the prompt to navigate to a url, clicking the right stick inputs : which is used to access Qutebrowsers advanced commands and settings. The thing about running Qutebrowser in Gaming Mode is that you can use a separate control scheme in Steam designed exclusively for using Qutebrowser. Obviously, inputting bulk text with the touchscreen keyboard is going to be faster, but I think this control configuration is worth exploring since the modal nature of Vim style keyboard commands reduces the amount of necessary keybindings to fully utilize and navigate a web browser by a huge amount. The left joystick being a good fit for hjkl is the icing on the cake!