3 ms·
Your PMs should not decide what your software does with my hardware without me giving my informed consent. Our PMs don't like making things opt-in. -> Your us
by sturza 1y ago
Your PMs should not decide what your software does with my hardware without me giving my informed consent.
Our PMs don't like making things opt-in.
-> Your users don't like making things opt-out. Low usage metrics is a UX problem. Activating it without informed consent gives you bloated metrics anyway.
- fiddlerwoaroof 1y agoIt’s just not true that users don’t like making things opt-out. HN Users tend not to like it but I think a lot of users dislike the alternatives: either because they’re undiscoverable (toggle in settings or a menu) or intrusive (various sorts of what’s new overlays). Imo, the question of when to make things opt-in vs. opt-out is fairly subtle and largely depends on the feature and pre-existing trust.
- sturza 1y agoThere are infinite ways on how to inform users of a new feature and ask to activate it.
- fiddlerwoaroof 1y agoAnd nearly all of them are annoying and disrupt my flow.
- graphememes 1y agocookie popups that don't even work
- bayindirh 1y agoThe same thing disrupts your flow allows me to make informed decisions, and I'm happy to be offered a choice, and ability to change my mind later.