> Make the report readable by a simple text editor. Let the users have a look at the content inside.how do you explain the concept of a backtrace to an end-user so they can make an informed decision whether it's fine to submit the data or not? How do you do the same with a a full memory dump (if you need one?). How do you expect users to analyze the memory dump for potentially compromising data?
> If you do need the report, ask them to check it then send it through trusted and encrypted ways like Firefox Send.
this works for you and me. It doesn't work even for my coworker. Also: What is the advantage of going through the extra hoop of Firefox Send compared to over plain SSL when you intend the recipient to be able to read the dump anyways?
> No need to fix crashes for users that never cared for reporting them to you
Judging from metrics available to an app I'm working on I would say that users are much more likely to stop using my app completely rather than even bothering to press the "report this issue" bug.
It really depends on your target audience.
But in case of UniFi (as opposed to their AmpliFi line), asking for individual reports to be reported could possibly be feasible given the product audience.