|
|
|
|
|
|
by nucleardog
588 days ago
|
|
|
To add on to what others have said, as a habitual "no don't send telemetry" clicker, I think this is heading a direction where I _would_ hit allow. Two adjustments I could think of that would make it better (besides explaining clearly, etc): Ask me when you're not actively obstructing me from getting to what I want. Like asking on first boot I've gotten no value from the software yet that I might feel I need to pay back, and I'm actively trying to get _in_ to the game and your pop-up is in my way. The easiest and safest way to get rid of it is "do not allow". Try asking _after_ I finish a game/round/whatever. And that would also give you the opportunity to do something like collect real analytics information to show to the user. Like "Hey I hope you're enjoying the game it's useful for me to have stats about how people use abilities and items to tune and balance the game systems. Would you be willing to contribute to the game's further development by sending information like that below which was collected from your last round?" And then skip the JSON/etc unless your audience is programmers, just show them a table. Finishing some play time having had fun and getting a pop-up that explains what, why, and gives me a chance to make an informed decision on whether to send something innocuous like "(offset-timestamp, event-type, item-id/ability-id)"... I'd actually probably allow it. |
|
|
A way to package it would be to show end of game stats compared to global averages. Histograms of mana/health/bullets vs the world standard. Maybe a personal historical trendline vs past performance. On that screen, give an option to share metrics with the community. Users can immediately see what the aggregated data can provide and might feel more likely to consent.
To be most user forward, keep a local non-obfuscated log of what is shared. This also makes it possible for dedicated users to potentially mine their performance.