3 ms·
Okay.so let’s hypothetically say I buy your argument that providing a reasonable default is bad UX. In what other places of application development should we a
by josteink 7y ago
Okay.so let’s hypothetically say I buy your argument that providing a reasonable default is bad UX.
In what other places of application development should we also stop providing reasonable defaults and force the user to choose instead?
- country? city?
- localization?
- number for local support hotline?
- email of logged in user?
- type of currency for payments?
No? Then why is having a reasonable default for downloads bad?
- zzo38computer 7y agoMy "WebOptions" idea would permit the user to customize these and other settings (both globally and locally; there could be some set of "common" keys as well as supporting keys specific for the server), in a similar format to cookies, although the server and document scripts would not be allowed to set them, and the user only sets them explicitly. For email, there is a "From" header, so that can be used if it is available. But anyways, the service should not make it difficult to download if it detects a wrong computer; it should allow it always, and should not be so difficult by trying to hide it.