Go to:
Previous Item
Current News
Next Item

The following is an unedited press release, shown as received from the company represented. We've elected to present selected releases without editorial comment, as a way to provide our readers more information without further overtaxing our limited editorial resources. To avoid any possible confusion or conflict of interest, the Imaging Resource will always clearly distinguish between company-provided press releases and our own editorial views and content.

TweetPhoto's logo. Click here to visit the TweetPhoto website! PRESS RELEASE: TweetPhoto Introduces API Libraries, Facebook Connect and Twitter OAuth Support


Don’t be fooled by the name, TweetPhoto releases API support for Facebook Connect and Twitter OAuth, followed by the introduction of native client libraries to speed up third-party application development.

02.16.2010 – San Diego, CA – TweetPhoto today announced a major milestone to its real-time photo sharing API, the introduction of client libraries for Java, Objective-C and .Net in addition to supporting authentication using Facebook Connect and Twitter OAuth. These releases help developers from two of the world’s largest social networks get up and running quickly with the company’s real-time photo sharing API service while further safe guarding user login credentials. Last month TweetPhoto announced the support of Foursquare authentication through its API.

“We want to make it easier to integrate a photo-sharing service into a third-party application,” according to Sean Callahan, Co-Founder of TweetPhoto. “Now Android, Blackberry and iPhone developers on the Twitter, Facebook and Foursquare platform can effortlessly take advantage of photo uploading functionality, commenting, favoriting, voting, searching, social feeds, and much more.”

The client libraries for Java, Objective-C and .Net are the traditional set of native drop-in classes that will speed up development and enable developers to focus solely on building exciting new photo sharing experiences within their Twitter, Facebook and Foursquare applications.

On top of supporting Facebook Connect and Twitter OAuth authentication in the TweetPhoto API, the company has released a new optional ‘link account’ function for developers to tie users’ social networking accounts together from within their third-party applications. This will let users publish photos to one place from any third-party application and have them instantly shared to their accounts on Twitter, Facebook or Foursquare.

TweetPhoto has not only recently invested heavily in further advancing its photo sharing technology, but also improving API performance by switching to a service-oriented architecture and through upgrading to more powerful hardware.

“We want to put the most robust, feature-rich photo sharing platform in the hands of developers so that they can take their applications to new heights,” said Sean Callahan.

For more information, please visit: http://tweetphoto.com/

###

About TweetPhoto:
TweetPhoto is a real-time photo sharing platform for the social web. The free service allows users to share photos on Twitter, Facebook, and Foursquare through their favorite desktop and mobile clients. The service focuses on creating the best possible photo sharing experience across the social web.

This personalized experience is the evolution and convergence of real-time mobile and web-based social photo sharing. It allows users to quickly and easily publish, share and consume photos.

The company has positioned itself as the leading photo sharing platform on the social web by presenting the developer community with the most expansive and easy-to-use API available. TweetPhoto is feature rich and simply a better way to photo share.

The company’s website, http://tweetphoto.com, was built 100% from the TweetPhoto API.

The company aims to change the way in which people socially share, discover and interact with photos across multiple social networks in a way that feels natural and engaging to users.


(First posted on Wednesday, February 17, 2010 at 13:37 EST)

Go to:
Previous Item
Current News
Next Item