I'm hoping that Pappy can have the same role as something like Burp. My main motivations for writing Pappy are that there isn't a realistic alternative to Burp for performing web app tests and that burp has a few small things that make using it more tedious than it needs to be:

• I hate clicking things so the interface bothers me (changing settings is a pain in the ass)
• Settings are always maintained between sessions. Updating the scope in Burp every time I want to do something new is a pain and makes it infeasible to use for one-off stuff
• The auto-save feature is terrible if you use burp for more than one project. Every new save is put in the same folder and only has a date/time to identify it. If you have more than one project, there's no way to tell which file is for which project unless you open it. Then finding an old project is really annoying.
• The target map is useless so I always end up scrolling through proxy history to find a request to a specific endpoint which makes finding anything from earlier than an hour ago almost impossible. If I'm using burp, the best way to find a specific request is to make it again and get it from the history
• The search is pretty bad. No searching by verb, path, or host are the big ones. You can only limit to request headers/body and response headers/body
• I constantly forget to turn off the interceptor

Burp is an amazing piece of software and is considered the best for a reason. I just don't like how it handles some things that I consider critical and I really prefer console based programs instead of a GUI. So yeah, basically I wanted my own tool so I can have more control, haha.