When Twitter’s API first hit the Internet, one of the most exciting things about the service was how developer-friendly it was. Over time, though the API hasn’t gone away, the service has been taking a lot more of its activity in house and some developers are being left in the cold.
With the new Tweet Button, could TweetMeme be next on the list?
According to Mashable, Twitter is introducing its own share button and it could be available as soon as Thursday. Here’s a quick view of what we know so far:
As you can see, Twitter appears to be aiming both barrels directly at the TweetMeme audience. Full analytics behind the button should make it a pretty notable piece for site owners and a single line of code to implement it keeps things easy.
While it is worthy to note that implementing TweetMeme into your site is every bit as easy as what the Tweet Button is trying to flaunt, Twitter seems hell-bent on touting the simplicity of the service.
The final slide goes into some details that are, again, exactly the same as what TweetMeme is offering. However, the Tweet Button doesn’t offer a choice of URL shortening services, quite obviously because of Twitter’s integrated t.co links.
Mashable postulates that Twitter and TweetMeme have already sat down to talk about things, but we’re honestly not so sure. We’ve reached out to TweetMeme, and we’ll let you know what information we find, but the rest is a bit of a waiting game for the time being.
So for you site owners: is a retweet button, native to Twitter, enough to pull you away from another service? Why or why not?
This looks really interesting, I wonder what features the button will have and whether it will be more interesting than the tweetmeme button.
cheers!
For me, a lot of it is going to have to do with how it’s implemented. If it’s implemented more like John Resig’s Easy Retweet button and less like TweetMeme’s, I will most likely make a change (I currently use John Resig’s button and/or Wibiya).
The last slide says you can override the URL shortening service, btw.
It’s a freakin’ iframe ? :|
yeah a wondefull creepy iframe. Facebook had the good idea to let us choose between iframe (yerk) and js via sdk …
From looking at the Mashable story (which included more pics), it looks like they’re going to let us choose between iFrame and JS, but I’d be willing to bet that the JS is going to do nothing more than insert an iFrame into our pages dynamically. :(
seems a bit harsh for TweetMeme, but I have to say I’m more likely to use twitter’s own button on my site
we’re making a black and white version right now to try out, so shout if you’d like the gfx to post here for others
If the native service has more value to publishers than TweetMeme then eventually it could win out, but I suspect we will start seeing a lot more innovation coming from TweetMeme now, which is good.
I bet TweetMeme wishes they sold out earlier, because now their value proposition will decline by the day as the native feature gets adopted. Same goes with a lot of these third party tools because Twitter ultimately controls the ecosystem.
Yes, If its as easy as tweetmeme to implement, more stats and maybe easier way to customize (colors, icons…). I will move from an other service in a second.