New and Improved Button


It’s been a little over a month since we first launched our sharecount button for Facebook and what a month it’s been. With very little promotion, our weekend coding project was quickly being served on over 5M pageviews per day. And now, Facebook has released an official version of their own.

As part of Facebook’s button release, they also announced a new API for pulling the share data directly from them. They were kind enough to give us a preview of this API, and we actually launched a new version of our button using the combined Facebook and share data over the weekend. Here’s what’s new:

  • Uses combined share data from Facebook and for the most complete stats
  • Cleaner look and slightly taller (9px) large button (it is now 53px wide by 69px tall)
  • Ability to customize the background and text colors of the badge in the large button
  • When there are no shares, the badge in the large button is clickable as a sharing interface

We also upgraded our WordPress Plugin to accommodate these changes and include some user requests:

  • Support color customization in plugin
  • Added the ability to disable the button from appearing on Pages (vs Posts)
  • Improved plugin performance by eliminating javascript

At this point, our version of the button is primarily targeted at existing publishers. But, there are a few reasons other folks might want to use it over the Facebook version:

Please let us know if you have ideas on how we can make the button even more useful.

This entry was posted in Product and tagged , , , , , . Bookmark the permalink.

5 Responses to New and Improved Button

  1. Albert says:

    Really service are awesome… Just finished survey here… and waiting for invitation code.

    Let try… !!!

  2. joe says:

    You could easily generalize this onto other platforms besides facebook, you could make a recognizable/brandable button

  3. dian senang says:

    very nice plugin, thanks for share

  4. scott says:

    i get a fatal error when i install the plugin on wordpress 2.9.2. does anyone else get that when activating the plugin and are there any available workarounds or beta version of the next release to fix it? thanks!