|
|
|
|
|
by akira2501
663 days ago
|
|
> and we as a society would rather risk everything than be arsed to take few additional steps Large manufacturers would like you to think this. It would provide them a convenient excuse for not even trying to differentiate the market along these lines. > We (the society) don't even want to change the default password on most things. Actually.. I just want to use my device _first_ and not go through some manufacturer controlled song and dance of dark patterns. In my experience, if you don't pre load the user with this garbage, and then wait for them to have an actual _need_ that depends on the feature, they're FAR more compliant with following even lengthy instructions to get it done. It's more a problem of aligned benefits and timing than anything else. |
|
Nope, they want to have it working out of the box like with any other manufacturer out there. If you enable functions only after user wants it, they will comment "this sh*t doesn't work" on your app store page. Then you have to respons to each comment with "what doesn't work, could you specify please?" and then after several days that user has enabled the functionality, but in the mean time several another gave such comments.