Doubts about Tracking anti-feature

1

I have doubts about Tracking anti-feature because it’s not clear for me in some cases like crash logs or analytics opt-in/opt-out with service such as Bugsnag.

  • If the the log reports/analytic is disable by default and prop to the user to enable it, it’s an anti-feature?
  • If it’s enable by default but the user can disable from settings, it’s an anti-feature?

I think the Tracking anti-feature require more information about the opt-in/opt-out cases

2

No, it’s an informed choice, you want to help them? No? Mmmkay

Yes, most of people don’t roam to see each and every setting, also it might just start transmitting data before you get a chance to disable it.

3

Yes, most of people don’t roam to see each and every setting, also it might just start transmitting data before you get a chance to disable it.

if it’s enabled by default but prop or notify the user about it like We are collection error logs, [Disable]?

4

No, it’s an informed choice, you want to help them? No? Mmmkay

So for that case I think the documentation need more clarification, such as it’s not anti-feature if it’s opt-in

1 Like
5

That’s a NO then, if you can disable it at start.

6

Feel free to MR the website :slight_smile:

7

That’s a NO then, if you can disable it at start.

Yes, But I mean in that case is not a anti-feature coz it’s informing about that to the user, I think is just an anti-feature if the user not know about that and cannot deactivate it

8

yes, that’s why ask before, my English is not perfect but but I’ll send a MR, thanks

9

Not notified & enabled by default or can’t be disabled? Yes, anti-feature!

10

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.