All that information is important for the dev itself sure, but also for the UI people, the UX, the product manager, etc.
I mean, I just retired from a career as a self-employed incorporated UI/UX software developer for Fortune 100 companies, but what the fuck do I know, right?
The data telemetry that you are describing is data overload and ends up being not efficient to know. The truth gets lost in the quantity noise.
You have to study the usage patterns of how people use the software, by actually watching people use the app, and you don’t get that from just some counter in memory counting how many times a certain button was pressed, there’s no gestalt in that data set. Great data for selling to third parties, but not for helping you with the UX of an app.
It’s my professional advice that I feel confident in the opinion I expressed on this matter, learned from literal experience on the ground.
I mean, I just retired from a career as a self-employed incorporated UI/UX software developer for Fortune 100 companies, but what the fuck do I know, right?
The data telemetry that you are describing is data overload and ends up being not efficient to know. The truth gets lost in the quantity noise.
You have to study the usage patterns of how people use the software, by actually watching people use the app, and you don’t get that from just some counter in memory counting how many times a certain button was pressed, there’s no gestalt in that data set. Great data for selling to third parties, but not for helping you with the UX of an app.
It’s my professional advice that I feel confident in the opinion I expressed on this matter, learned from literal experience on the ground.
deleted by creator