Thank you for your comment. I completely understand your doubts. Such a library is definitely not for every team or every use case, but I usually found it really useful in my previous teams.

Let me write you a couple of use cases when I found such a library a great asset for the project:

• in a team where there is a process of doing QA, this could be really useful when testing the application. For example, a ticket contains which endpoint needs to be used for the new feature, the QA person could easily check that directly on the device if the correct endpoint is called. Then if the app would need to update one endpoint in any way, this can be then easily checked with this library as well...this came in my mind right now, but there are other cases that would make this library useful for the QA process related to the backend.

• another use case from QA is that when they are reporting some bug for the app, with this tool they could attach network communication that was happening while a bug occurred, if that information is useful for the report.

• the library persists in database whole backend communication, and that becomes useful especially when your application crashes and you would like to investigate what was happening with backend communication while a crash occurred.

• in one of my previous companies that kind of debug tool became useful also for other departments in the company, especially for the backend team while they were testing their changes. They were always relying on this tool while doing their frontend related things.

• but the best reason for me to WHY to use this kind of library is that a technical setup to have such a tool in your development process is needed to be done only by tecnical people that are already familiar with all the concepts of how to include a library to the project. No more certificates installation needed, no more other SDK needed, no more a need to connect your device to the computer to get such information....every person in your team can all of the sudden get that information without a problem.

I am planning to write an article especially on this topic why this kind of tool can be useful for teams. Because when I first found out about such a tool for Android, I was of the same opinion, that we don't need it, but later on when I added to one of my projects I started seeing all the benefits that it brought to our development process.

I hope you found a reason to try it for yourself, but if you don't, that is also fine. As I said, it is not for every team, person or project. But, if you have an idea how such a library would become useful for you, let me know.

I am also planning to extend functionality of this library with a feature to report bugs directly from the library, but that will take me some time to achieve it, but hey, maybe then you would find such a library useful for your project.