ArminTamzarian

Superb. Looking forward to it! And keep up the good work!

First of all, this is a great app that is attractive, functional, and easy to configure. It seems almost an ideal frontend in that it provides a simple, straightforward, easy-to-use interface for launching, playing, and exiting Windows games entirely via gamepad. That said, it seems that there is no setting within the app for the gamepad's buttons or analog sticks to be customized by the end user. As impressive as it may seem at first to have nearly every capability of the app accessible by controller, implementing the feature in a non-user-configurable manner ultimately sacrifices ease-of-use for the end-user, which is precisely the intention (for many) of having a frontend in the first place. As a specific example, I would like for my kids to be able to nagivate, play, and exit any Windows game that fully supports, say, an Xbox 360 controller, from the couch on the bigscreen TV using ONLY the 360 controller (that is to say, NO MOUSE and NO KEYBOARD). Like, you know, a game console. This app would work quite nicely for that purpose were there some way to customize the button behavior of the controller. As it stands, there are too many unnecessary functions that have been mapped all over the gamepad, and no way to selectively disable them. For many people, the only features that the controller truly needs to have are the ability to choose a game and way to start that game (and perhaps a way to navigate backward to a previous folder, if a folder system is somehow supported in the app), for which two buttons and a thumbstick/d-pad ought to suffice. Any other functions just make the end-user experience needlessly complicated for a significant portion of users that only actually care about being able to play the games conveniently (once the program has been installed and configured, obviously). Nobody wants to have to figure out how to exit from some unwanted menu with an unintuitive button press--especially a menu that was probably opened by mistakenly pressing a controller button in the first place! Would it be possible to incorporate the ability for the end-user to customize the gamepad's buttons, preferably via an .xml configuration file? This would dramatically improve end-user ease-of-use for those of us who intend the frontend to be used primarily by non-PC-savvy users (e.g. "elementary school kids").