undefined | Better HN

0 pointsdiegof796y ago0 comments

For those cases the app can collect the exceptions only (as many apps and OS do).

I worked on a desktop product with this type of data collection. Usually what happens is that after a new release you may see new errors coming up, and then they start to repeat. The data collection becomes a burden, new reports of the same error type doesn’t give you more information.

It’s a good opportunity for a good UX, e.g point the user to the relevant support info to solve the problem.

For support cases you may be able to ask for diagnostics on demand. The app can collect it internally without sharing and send part of it when an exception occurs and the user accepts to send it.

0 comments

daemin6y ago

That's actually a good piece of advice, thanks for posting it.

j / k navigate · click thread line to collapse

0 pointsdiegof796y ago0 comments

For those cases the app can collect the exceptions only (as many apps and OS do).

It’s a good opportunity for a good UX, e.g point the user to the relevant support info to solve the problem.

For support cases you may be able to ask for diagnostics on demand. The app can collect it internally without sharing and send part of it when an exception occurs and the user accepts to send it.