Hasta La Gadget!

Last spring an announcement from the platform team at Twitter not-at-all-subtly suggested developers of third party clients should find something else to do, and today a list of changes to its API turns that whisper into a firm nudge. The limit that most directly affects any of the unofficial clients you may be interested in using is that existing apps currently servicing more than 100,000 individual user tokens will be allowed to double their current count, but cannot add any users past that without Twitter’s permission. Going forward, any app that needs more than 100,000 tokens to do things like access the timeline, show DMs or anything else a client app might do will also need Twitter’s permission to operate. Other changes include that any pre-installed client app on something like a phone, computer, or TV will need Twitter’s permission before it ships (sensing a trend here?), or potentially face revocation of its application key. Moving on, the Display Guidelines about the information any app that displays tweets must provide are shifting to Display Requirements, with violators potentially losing that application key. Those Twitter Cards that started rolling out over the last few months are also getting a big push, with plans to include other ways for developers to bring their rich content to Twitter, and embed real-time Twitter content on existing websites.

In a section of the blog post that specifically calls out popular third party clients like Tweetbot and Echofon, it puts them in a zone of Twitter apps that it believes developers “should not build” since they mimic or reproduce the mainstream Twitter client experience. Other services focused on aggregation like Storify and Favstar.fm are also called out as not having much of a future in Twitter’s view of its universe A-OK, see the update below. It’s pretty clear where we’re headed, as Twitter seeks to monetize a growing and talkative user base, it wants to make sure users are all seeing things in the format it wants them to. With a six month migration period ahead, developers and users may have hard choices to make. Tweetbot developer Paul Haddad has already tweeted that “the sky is not falling…the cap is pretty huge and we aren’t going anywhere”, and we’ll undoubtedly hear from others soon. The rest of the details reside beyond the source link, but let us know first — are you learning to love the official Twitter clients, or are you thinking paying $50 a year for an entirely unproven alternative with no users doesn’t sound so ridiculous after all?

Update: Twitter platform director Ryan Sarver tweets that Favstar.fm and Storify are actually “good examples” of services it would like to see. Also, TweetLanes developer Chris Lacy is apparently encouraged by the change, thanking Twitter for “giving client devs a chance”

Filed under: Internet, Software

Twitter’s API v1.1 rules put user caps on third party clients, exert more control overall originally appeared on Engadget on Thu, 16 Aug 2012 19:17:00 EDT. Please see our terms for use of feeds.

Permalink   |  Twitter Developers Blog  | Email this | Comments

Rapid turnaround just may be the name of Facebook’s game. Just a few weeks after its SDK 3.0 for iOS reached beta, the new developer tool has surfaced in a polished version. As it’s shipping, the SDK continues to emphasize a more iOS-native experience, better API support and slicker session management. Any iOS 6 integration will still have to wait until Apple finishes its software update; Facebook is keeping a separate beta track active to serve forward-thinking developers. The social network’s regular members aren’t quite getting the same reward, however. The expanded app support is being followed just as quickly by a mobile ad beta. While Facebook is still sparing us from a full-bore marketing assault, it’s letting developers pitch their Android and iOS apps from Facebook’s mobile portals, with a quick hop to the relevant app store if the title isn’t already loaded. While there’s no estimated completion date, we have a feeling that this is one Facebook beta where most customers won’t mind a delay or two… or ten.

Filed under: Cellphones, Internet, Software

Facebook SDK 3.0 for iOS arrives in finished form, mobile ads tag along in beta originally appeared on Engadget on Tue, 07 Aug 2012 19:29:00 EDT. Please see our terms for use of feeds.

Permalink   |  Facebook (SDK), (Mobile Ads)  | Email this | Comments

Remember that partnership between OnStar and RelayRides we wrote about last March? Well it’s finally coming to fruition today, with the peer-to-peer car sharing service launching support for remote door unlocking via OnStar’s proprietary API. As a result, RelayRides members with OnStar-enabled vehicles no longer have to exchange keys in person if they so choose. Another benefit is that participants can list their automobile on RelayRides directly from their OnStar account — renters then benefit from the added safety and security that comes with OnStar.

We had the chance to test an early version of the functionality on a Chevy Volt at SXSW a few months ago and it worked pretty much as advertised. There was a bit of a delay between the time we sent the unlock command from RelayRides’ website on the demo iPad and the moment the doors actually unlocked on the car, but we’re told this has been significantly improved since our hands-on. Of course, RelayRides also supports remote unlocking via text message. Take a look at the galleries below then hit the break for our hands-on video, RelayRides’ video and OnStar’s PR.

Continue reading OnStar seals partnership with RelayRides, makes renting out your car even easier (hands-on video)

Filed under: Cellphones, Tablet PCs, Transportation, Software

OnStar seals partnership with RelayRides, makes renting out your car even easier (hands-on video) originally appeared on Engadget on Tue, 17 Jul 2012 07:00:00 EDT. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments

Merriam-Webster just announced its new Dictionary API, which gives developers access to the full dictionary and thesaurus, along with more specialized content like medical, Spanish, ESL and student-targeted vocabulary lists. The API will let app makers integrate word definitions, etymologies, audio pronunciations and more. While this content will no doubt make it into a slew of educational apps, Merriam-Webster says it will also enhance word games, so maybe Scramble and Words with Friends will finally start accepting those obscure three-letter words you have up your sleeve.

Continue reading Merriam-Webster announces Dictionary API for developers, coming to a word game near you

Filed under: Software

Merriam-Webster announces Dictionary API for developers, coming to a word game near you originally appeared on Engadget on Fri, 13 Jul 2012 15:32:00 EDT. Please see our terms for use of feeds.

Permalink   |  Dictionary API  | Email this | Comments

Ma Bell’s been hard at work on its Watson speech recognition system for years, and 2012 has seen the tech show up in an automobile and a real-time translator app. Months after announcing it would grant Watson’s skills to the developer masses, AT&T has made good on its promise and officially released its Speech API. In case you forgot, AT&T’s Nuance competitor’s been tailored for different use cases — including voice web search, voicemail-to-text and talk-to-text — so that it can offer contextually accurate results in any app. If you’re among the coders itchin’ to test out Watson’s capabilities, head on past the break for a promotional video, then click the source below to sign up for access.

Continue reading AT&T officially releases Watson speech API, gives devs a bit of babel fish for their apps

Filed under: Software

AT&T officially releases Watson speech API, gives devs a bit of babel fish for their apps originally appeared on Engadget on Tue, 10 Jul 2012 02:26:00 EDT. Please see our terms for use of feeds.

Permalink   |  ATT Developer Program, AT&T Innovation Space  | Email this | Comments