[brudgers]

That means now they have to do everything twice.

And also deal with "they say they respect privacy but they collect data" complaints. Because people who talk about privacy are rarely a sound market segment for anything other than privacy tools...that are free.

The market segment for most products is people who don't care about privacy. Or at least people who don't find privacy a reason to spew moral outrage on the internet.

I mean there are endless HN threads where people are complaining about the privacy evils of products they don't use...e.g. Windows.

[b-pixel]

I’m not sure I understand why they need to do everything twice. But regarding your comment about most market segments not caring about privacy, I agree especially when it comes to B2C products.

Users will complain about it but it will rarely be a deal breaker. Will only matter if the product being offered holds really sensitive info

Either way if a company or Dev wants to respect privacy, that’s great and I applaud it. A product doesn’t need to collect every single piece of data on all their users to figure out their strategy...unless your product’s monetization strategy is all about selling user data

[brudgers]

Implementation for people who don’t care.

A different implementation for the few people who both care and actually pay.

Your applause won’t put beans in the cookpot.

[b-pixel]

You looove beans.

Definitely a bit of extra work but can be minimal if event tracking is centralized in one area of the code.

But yeah, not saying I recommend you do it, just saying it’s possible and not something that should be seen as a waste of time, especially if you truly believe in creating privacy focused software.