API should allow app statistics access

[Alan Pope 🍺🐧🐱 🦄]

As a developer I am interested in knowing details about how many people use my app, which versions and what region they're in.

I am able to view this on the /stats page for my app, but this is a very limited view. I'd like to create my own graphs so I can plot trends and use this data to make development decisions and motivate myself and other developers.

Ideally I'd like access to the raw data for number of downloads per day, number of users, and from what region they come. I'd like whole dataset from the start please, but be able to download a subset as time goes on.

Other data such as the types of devices would be a bonus, but I don't think the store tracks that, so that would probably be tricky.

[Stephen Stewart (stephen-stewart)]

Hi,

You've said that the /stats page is limited, but I'm not sure you've been specific about how it is limited.

Which additional graphs would you like to see?

Would adding trend lines to existing charts be useful?

[Matti Rinta-Nikkola (matti-rintanikkola-d)]

Hi, one thing you could improve is to change the scale of the vertical axis (number of downloads). Now the minimum value is always 0... in time being there will straight line on the top of the graph which will be rather useless. The minimum should be about the minimum value of downloads on the period shown.

Matti

[Alan Pope 🍺🐧🐱 🦄 (popey)]

Okay, the stats page has a number of issues:-

* It only goes back a week, I have no way to say "show me stats for the year, month, or any arbitrary date selection"
* The pie chart colour selection is pretty awful. In some cases you get repeated segments with very similar colour.
* No historical data for users, only downloads.

I don't really want more graphs, I want the data, so I can manipulate it myself, add it to other charts I have, overlay it with other apps etc.

[Matti Rinta-Nikkola (matti-rintanikkola-d)]

or maybe better on that graph you could change the vertical axis as downloads/day.

[Robert Ancell (robert-ancell)]

See also bug 1426965