I'm not sure why you think powerlaunch is targeted at end users. It's not even in any standard repository so you have to go to some effort to find and install it. It certainly can be made more end-user friendly such as translating some set of "standard" config options like what mce has into powerlaunch code. But you have to understand that the primary intent of the program is to replace closed source components. For example, the current target of the program is on replacing dsme also and not of making the front-end easier to use. The extreme customizability of powerlaunch is just a side effect of the architecture that happened to make the most sense while programming. It could have had no programmability and just emulated systemui/mce. With that said, it is programmable and if there were a list of "standard" config options that people wanted, it would be pretty easy to create a single file like simple.conf where you could just edit and uncomment out appropriate lines and everything would "just work". I just have no idea what those standard options should be. While you may think changing the power key behavior is important, I mostly need the ability to control the device with the screen off. Also, assigning keypresses to things (which seems like it'd be pretty common desire), seems highly dependent on user's preferences, and aside from writing a GUI, I don't know how you can really simplify the config language from something like "key_up = exec osso-xterm" which seems about as simple as you can get for this operation. Certainly any suggestions are welcome.