Wednesday 28 December 2016

The Case for WordPress Telemetry


WordPress prides itself on being an application built by the user for the user. The problem is with the popularity and reach of WordPress today, the distance between the WordPress 1% (or even .1%) and the average user is becoming so vast we (the people who contribute to WordPress core) know almost nothing about the actual people who use WordPress or how they use the application. This will become more of an issue as the application evolves, and it is high time we do something about it. Lack of data means we’re flying blind
During the development of WordPress 4.7, I was involved in several conversations centered around assumed use of features. The general argument was that based on the 80/20 rule, certain features should be added while others should be removed. I kept brining up the well known fact we don’t have a clue what features 80%, or even 20%, of WordPress users actually use so any claim of validity in the 80/20 rule is guesswork at best, and in response one developer told me, point blank, “we know what the user wants.” I don’t know about you, but in my book that is not the way to build an application for real people.
What we need is raw data based
Source: https://managewp.org/articles/14097/the-case-for-wordpress-telemetry




source https://williechiu40.wordpress.com/2016/12/29/the-case-for-wordpress-telemetry/

No comments:

Post a Comment