Ask HN: Honesty vs simplicity: how honest should you be to your users?
3 comments
What does the user care about? In your example, I guess they care about bandwidth usage and personal data. So in that light, I would inform them that a small amount of game-specific, non-personal info needs to be sent to the website (server is jargon, so should be avoided) to record the score.
My point is that as much info as the user cares about should be provided in a clear, accessible manner.
Where personal data and/or legal disclosure laws apply, then more transparency and info is better.
Unfortunately, it is not unnecessary to point out that all information of all types at all times should always be rigorously honest. If you're going to tell your users something, be truthful.
My point is that as much info as the user cares about should be provided in a clear, accessible manner.
Where personal data and/or legal disclosure laws apply, then more transparency and info is better.
Unfortunately, it is not unnecessary to point out that all information of all types at all times should always be rigorously honest. If you're going to tell your users something, be truthful.
Couldn't you say "send the result to the server", and it could mean both things without sounding too scary?
in my opinion, i'd give them multiple levels of information. give them a simple notice that they're submitting score information, and provide an option to view more detailed information if they wish.
I agree, I'd suggest with Terms & Conditions there are:
1) people who don't read/skim them (the majority)
2) people who want all the details (a vocal minority)
So if your T&C's state something like 'we may send puzzle data to our server, where it might be stored' & you also have an FAQ on your website with the full details that should satisfy both.
I would second this opinion. Anyone who cares about the detailed information surely understands the need for simplicity, and will only be annoyed if you're intentionally misleading.
For example, in an iPhone puzzle app, you might tell the user that you are sending their score to the server.
But maybe you are doing more: the server may not trust the app and require a solution -- not just the score.
Telling the user that you are sending the solution to the server is also misleading, as the server may not store the solution (other than temporarily in a log perhaps) -- but use it only to check the score.
Explaining all this to the user is probably too much.
So what would you do in a situation like this?
Just say something that is close to the truth that is easy to understand?