Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
neeno104566dI'd say to keep it optional. It increases the friction for the user, so it would likely increase the chance of the user pressing ignore. Also, why ask the email? If I got an email about a crash on an app I'd just ignore it.
Diactoros138366dI’m curious to hear the justification for an email address. I can’t think of a reason it’s needed. Why do you need anything other than a usage description? Why don’t you automatically send the crash report in the background immediately, and just allow the user to submit a description and no identifying information? What is the gain to you as a developer for gathering that data? It’s very likely your response rate will drop dramatically too.
AlmondSauce841866dIf it's internal, maybe. If it's external, no way.
adante7365d@ItsaMeTuni @Diactoros primarily, it is so we can contact them to (a) notify them when that crash is fixed, (b) providing them with workarounds and (c) asking for further information to replicate the crash when it is not clear.
To provide some context we write fairly niche software used by engineering professionals. Our userbase is actually currently small enough that personally know and often work in close conjunction with the majority of our users. Odd as that may seem (and the challenges it presents with scaling notwithstanding), this has been consistently cited as our one of our greatest competitive strengths so is something we think carefully about.