Okay, I was gonna do a big multi-quote but Fenny already said a few things I wanted to:
First and foremost, I repeat, the app isn't ready yet for decompiling smali files out of the blue. It is in a very, VERY alpha stage where we don't even have all of the smali functions enumerated or even coded, to have it work on even a simple smali file. In fact, it needs work, but in terms of
coding work.
I have to agree with Fenny though. While a GUI is a nice feature to have (and I'm more of a GUI rather than a CLI person and is one of the reasons why I prefer Windows over Linux), I don't think we should focus our work on a GUI, which, more likely than not, will need to be changed a lot through the whole development. Instead, I'd rather get help in coding the needed stuff to make this work nicely and then I promise we'll work toegether to make a good GUI for it. I have plans for a good GUI ! I just don't feel it is the right time to do it with the app not even being able to decompile correctly a smali file yet. Still, if someone does it, the work is appreciated and well if I like it it'll be included, it just isn't the main focus now.
I also agree with the comment thing. I've been working my head around today on how to display some debug info without complicating the working code much. I'm having a bit of a struggle trying to debug some specific smali lines and reaching to them in the debugger is a bit annoying, lol.
I would also like to see what files did broodplank1337 used. I assume they would come in handy in our tests
Keep up the great ideas and contributions!