Also we should remember that data needs to be stored first before it is aggregated. What happens with information about each single event?
Reviewing aggregated user behavior data is how good UIs get built. It helps us to identify pain points, confusing or misrepresented user paths, poor hierarchy or site structure, poorly indicated calls to action, and many other valuable metrics.
Every positive user experience you've ever had online has been derived from countless hours of studying user behavior, and the larger the source the better it gets.
Also note that aggregated user data is typically anonymous, but there is a lot to be said for keeping it identifiable. Some of the best tools for debugging customer support issues start by recording your clicks so a developer can see exactly what caused an issue, rather than guessing and hoping.
Not by mass surveillance.
The perspective expressed, basically that anything is acceptable as a means to optimise "user experience" (most likely so more money can be extracted) verges on unethical and immoral, if the bigger issues of group and individual privacy rights are considered.
Nevertheless, as a web developer you are most likely only gathering stats from your particular web site, which is a different kettle of fish to browsers gathering and aggregating data across many sites.
Really? The browser-maker learning what features people use vs. don't, or what features are fast vs. slow on actual user machines, doesn't benefit the user by getting them a better browser over time?
I would like it if the statistics from Chrome in particular, were sent to Chromium-project servers rather than Google servers, though. Even if only Google's derivative of Chromium is collecting the stats, the Chromium-project staff are who will (theoretically) make the best use of the information so collected; and so it'd be much better for them (as a non-profit org) to steward that data, rather than it ending up owned by Google.
(Yes, yes, a majority of the Chromium-project staff are Google employees; that doesn't change how changing the data's ownership would change what Google thinks it has a right to do with it.)
It's hard because if (due to a bug) something were not correctly aggregated and anonymized, then their private data would leak to the public.
They are also worried about the non-tech press going through the metrics and making misguided headlines like "Google says 66 percent of Chrome users have been targeted by russian malware, and even more in the USA!"
Again, I don't feel like I am invading anybody's privacy when I look at what all my users are doing in order to help decide what to prioritize.
E.g., is it okay to track user location, if in aggregate they use it to advice on traffic?
While I still don't see it as ethically flawless, aggregating information about a website is certainly much more acceptable than aggregating information about a web browser.
- buy more stuff you don't need
- look at ads longer
- more likely to click a button because of specific color
- scroll your feed longer because of the content you are getting served
I'm not sharing shit with anyone, no matter if it's anonymous, aggregated or not.
It blurs the discourse and hampers objective discussions IMO.
I understand that A/B testing can be used to exploit addictions mechanisms and other gray (at best, more likely dark) patterns and IMO that should be forbidden.
At the same time, I don't know any mobile company launching a new feature without a server side A/B lock these days.
Simply because that way :
- it allows you to open the feature gradually and close it if there is a nasty side effect like a crash.
- look at usage patterns between 2 features. I guess the separation between helping the user and exploiting them can get blurry but really when we look at data it is to see if they know the feature exists and find it useful. The truth is that almost all users barely know how to use their phones, so each time there is a feature based on long click, gesture, something buried in a screen other than the first one of the app, a button in the toolbar, etc, chances are that most users won't even know that it is there, even if they would like to use this feature.
I honestly don't know how to conciliate the 2.
I don't really understand the issue people have with aggregated information. All the companies I have worked for have been tracking how people use their product. It does not feel like I am invading somebody's privacy by tracking that 20% of our users clicked on the banner in order to see the screen 'xy' and among them, 67% clicked on 'ok' .
To be clear, I am only talking about aggregated information