> How do you describe in a legal way the difference between a useful feature people want and an addictive feature they don’t want?

I don't know how you'd write it in a law either, but if you're in a meeting at your tech company, and the product owner or tech lead uses language like "We need to get users to do..." and "We need to incentivize..." and "It should be easy to do X and hard to do Y..." then do whatever is in your power to steer/stop. You're not really building a product users want, you're pushing a behavior-modification scheme onto users.

> It should be easy to do X and hard to do Y

> you're pushing a behavior-modification scheme onto users

In general I think that your comment is reasonable. I just would like to point out that such "behavior-modification" schemes are sometimes introduced for genuinely good and ethical reasons.

For instance, it is in my opinion desirable to make it more difficult for users to delete all their photos by e.g. having to confirm their decision in a dialog first. Because it prevents them from accidentally doing something they might not want to do and which is potentially impossible to revert.

I feel like they will just frame it differently: “Users aren’t getting the full value from product x, so let’s change the workflow to help enable them to get more value with no additional effort” or “Users are losing out on a ton of value by cancelling their subscriptions without realizing what they are losing out on, so let’s implement feature x to make them less likely to mistakenly cancel”