>Erik has asked me to write an exploratory app for user-agent data. The >idea is to enable Product Managers and engineers to easily explore >what users use so they know what to support. I've thrown up an example >screenshot at http://ironholds.org/agents_example_screen.png
I cannot speak as to the interest of community about this data but for developers and PM we should make sure we have a solid way to update any data we put up. User Agent data is outdated as soon as a new version of android or iOs is released, a new popular phone comes along or a new autoupdate for popular browsers. Not only that, if we make changes to, say, redirect all iPad users to the desktop site we want to asses effect of those changes as soon as possible. A monthly update will be a must. Also distinguishing between browser percentages on desktop site versus mobile site versus apps is a must for this data to be real useful for PMs and developers (specially for bug triage). We have couple backlog items to make monthly reports on this regard. A UI on top of them will be superb. On Tue, Mar 3, 2015 at 1:05 PM, Oliver Keyes <[email protected]> wrote: > Hey all, > > (Sending this to the public list because it's more transparent and I'd > like people who think this data is useful to be able to shout out) > > Erik has asked me to write an exploratory app for user-agent data. The > idea is to enable Product Managers and engineers to easily explore > what users use so they know what to support. I've thrown up an example > screenshot at http://ironholds.org/agents_example_screen.png (I'd > host it on Commons, inb4Dario, but I'm not sure the copyright status > of the UI) > > One side-effect of this is that we end up with files of common user > agents, split between {readers,editors} and {mobile, desktop}, parsed > and unparsed. I'd like to release these files. The reuse potential is > twofold; researchers and engineers can use the parsed files to see > what browser penetration looks like globally and what browsers should > be supported at a top-10, and software engineers can use the unparsed > files to improve detection rates. > > The privacy implications /should/ be minimal, because of how this data > is gathered. The editor data is gathered from the checkuser table, > globally, and automatically excludes any user agent used by fewer than > 50 distinct usernames. The reader data is gathered from a month of > 1:1000 sampled log files, and excludes any agent responsible for fewer > than 500 pageviews in a 24 hour period (except, sampled. So, > practically speaking, that's 500,000 pageviews) > > What do people think about making this a data release? Would people > get value from the data, as well as the tool? > > -- > Oliver Keyes > Research Analyst > Wikimedia Foundation > > _______________________________________________ > Analytics mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/analytics >
_______________________________________________ Analytics mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/analytics
