cyanlemons
commented
3 years ago Repost of a relevant comment on discuss:
Twitter poll on whether or not Status should collect opt-in anonymized usage data: https://twitter.com/ethstatus/status/1339245853798768642.
So, less than 50% of people were confident in saying "Yes, that's fine." This is a bit biased, because "show results" isn't exactly the same as "undecided," but it's close enough that I don't think it would be a good move to add an option to provide usage data. I think it would damage our credibility in terms of our security and privacy as both a messenger and wallet if we were to move forward on this.
Instead, I think the best route for acquiring this very important data will be a separate beta build of Status in both the App Store and Play Store. It could be titled "Status BETA with usage tracking" and the description would say it's a beta build that includes usage tracking to assist our developers in making more informed decisions. This way, we can entirely compile out any tracking code in the default builds (not with a runtime option, only a compile-time option), while keeping it enabled in the beta builds.
The users of beta builds will inherently be more technically inclined, so to account for this, there could be a self-reported metric for how technically apt a user is from 1 to 10. This way we could, perhaps, exclude users that are an 8 and higher from our analysis of the data.
As a user I want to be able to provide anonymous metrics to the status-team So they can better improve the product
Notes