I’ve been wondering for a long time about the real popularity of Facebook apps that are targetted at specific niche user groups.
Well with Developer Analytics you can find out – without needing to be the actual developer of the Facebook application in question.
With the museum community starting to build useful applications like the Brooklyn’s ArtShare or the Steve Art Tagger, the ability for us all to evaluate the success of these sort of projects is increasingly important. This is especially the case for cross-institutional projects to which we are all beginning to contribute our content. Are these projects reaching the audiences that we want our content to reach? Where should we focus our energies?
What can you learn from Developer Analytics?
For Artshare I can quickly see that as of today it has 2,900 install with 58 average daily users, as well as pull up a popularity graph to see this over time. (Update: Shelley at the Brooklyn says that these stats conflict with the ones she can pull up from within Facebook – see comments below) I can also compare it with the Steve Art Tagger which has been up for a few months and has 200 installs but only an average of 2 active daily users. Readers from the libraries world might be interested in taking a look at the statistics for the OCLC’s recently released WorldCat Facebook app.
I can also look at which commercial applications are most successful and track trends across, say, the multitude of Flickr-related applications to see which are the most sticky and used.
There are important lessons to be learnt from the other successful Facebook applications which we can draw upon when building our own.
Here’s a chart from the My Flickr application which, being an app with a large-ish userbase provides significantly more data about users – including the other apps that users of My Flickr use, gender, age and friend demographics. (A side note – the availability of this information to application developers in itself should be of interest to all Facebook users concerned with privacy).
Head over to Developer Analytics and do some digging of your own.