The Twitter 1.1 API and what it means for webOS | webOS Nation
 
 

The Twitter 1.1 API and what it means for webOS 32

by Ryan St. Andrie Wed, 27 Feb 2013 6:23 pm EST

Twitter Hero

Twitter, that lovely place where we all send random 140 character snippets of news, thoughts, and rants. Love it or hate it Twitter is an important part of social networking and has played a very important part in the webOS community over the years. Some of this platform’s first great apps (think Tweed) were Twitter clients. Whether you’re following @webosnation for the latest and greatest in webOS news or one of the many awesome developers out there you probably use Twitter even if it’s just to spectate the conversations. Due to the popularity of this social network within the webOS community we have had the blessing of many truly great third party Twitter clients over the years. Unfortunately due to webOS’ current status of uncertainty developers abandoned our treasured platform in search of ecosystems with a pulse thus abandoning or removing their apps from the webOS App Catalog.

As time moved on Twitter slowly changed their API (software components developers use to access services in a nutshell) to “better” their product. When the API changed if a developer didn’t update their app said app’s functionality would break or cease to work altogether. One quick search through the App Catalog for Twitter will result in a graveyard of apps that have been abandoned. Several months back we composed a roundup of fully functioning Twitter clients that could still be had on webOS and unfortunately that list is about to get a bit smaller soon.

On March 5th (that’s less than a week away folks!) Twitter will begin what they call “blackout tests” for API v1 and fully retiring @Anywhere API altogether. According to Twitter’s developer site the first test will run from 9:00am 10:00am PST on March 5th. During this test they temporarily retire the old API to let developers know how their apps will be affected. After the first test more tests will be announced before, during, and after each test by @twitterapi. The eventual endgame is to fully retire the old v1 API for Twitter in the near future and apps need to migrate to the new API or they will be forever broken.

So what does this mean for us? In a nutshell it means that a lot of our favorite apps that developers have left behind will cease to function. So if you’re still using an app like Carbon, Bad Kitty, or Glimpse to access or interact with Twitter in anyway now would be a good time to move on. We have reached out to several developers on this matter and so far we know for a fact there are a couple of diehard developers that have either updated their app already or have plans to. Here is the short list that we have been able to confirm so far (we'll be updating this list if/when other developers update their apps):

We know that list is small but we are happy to see that there are still dedicated developers for webOS out there that are dedicated to keep their apps up to date after all that this platform has been through. We thank all of them for all their hard work and urge our readers to open up the App Catalog and buy all of these apps if you don’t already have them. If the app is free get ahold of the developer and see how you can go about donating to them or at least give them a huge thank you for their continued support of webOS.

Source: Twitter

32 Comments

Thanks for the helpful article!

One thing you forgot to mention though: you've named sprw (the Enyo 2 version to be exact) as to getting an update. But Arthur Thornton, the developer, has also announced that Sparrow (the Enyo 1 version in the App Catalogue) will also get an update to support API 1.1
So you might wanna mention Sparrow in the article too.

Join me in my quest to (nicely) put a little pressure on @ingloriousapps to get them to update glimpse and sleet!

I follow him on Twitter n get the feeling he has moved on. It sucks cause I don't expect carbon or graphite to get updated neither.

He has moved on to android, however he just replied to me on Twitter agreeing to update them!! This is good news!

Yes I just saw it. Good for you.

Thanks Inglorious dude! Still use Glimpse every day!

I use Spaz will it be safe or not?? Please tell me...

spaz is open source so it could be done by anyone. We will have to see if someone wants to do it.

It's open souce. If no one updates it then I'll try. But I'll wait for the API 1.1 to go live first so I can better test what I've changed in the code.

if it is not one thing it is something else. Can we get a break here? All we want is to use our beloved webOS

Third party APIs don't care who you are. And rightly so, since they've gotta develop their apps further, just as a phone developer has to further develop his apps if he want to stay relevant.

Speaking of apps not working, what the heck is up with LinkedIn already???

Linkedin stopped working in December, also because of an API update. Synergy as well as the app. The Linkedin app is closed source, I have not seen any indication of possible support by Linkedin. See forums for more info.

I have problems with remix player in the application does not appear cataloging 2.5.11, and 2.5.11 feed mail me wants to charge for the application as if he had never bought

@MAMISHO As I mentioned to you on Twitter, the webOS app catalog is having an issue with my app update for Music Player (Remix).  2.5.11 is still not showing up.  Unfortunately the webOS app catalog & developer portal have always been notoriously buggy.  I've emailed the support team, but haven't heard back from them yet (wondering if there's anyone left at Palm/HP/LG/Gram/whatever).  Luckily though the Quick Post 1.2.1 update seems to be available in the app catalog.

Quick Post 1.2.1 update went live yesterday and it works fine :)

thanks Ryan

I will make up my mind on my new client by tomorrow and make it a point to purchase or Donate...I will miss Carbon on my phone

I see you didn't mention the new "Neo" TP client ....any news on them updating????

Kataran I have been in touch with the developer for Neo and he is swamped with school work. He has no idea when he will have time to update his app. Sorry :(

It uses Spaz as its API layer, so once Spaz is updated, it'll be easy to get Neo updated as well.

thanks again.....

fxspec06 rumored to me about a possible smartphone release of Neo

TP version working fine as of today

Time to make the switch to Macaw ;)

I have updated the list of apps that have either updated or will be updating to reflect Glimpse and Flixi. I will keep this list updated as developers come forward with information. Feel free to post in the comments or get ahold of me to let me know if any of you know of apps that I have missed. Thanks. 

I already posted that Sparrow will also get an update but you didn't add it to the list.

FYI:
-Sparrow=the current stable version of sprw, available in the HP App Catalog
-sprw, which you mentioned=the current experimental version of sprw, available via the dev's website

I assume this only affects Twitter apps not other apps like Groovesharl or Done?

The Twitter API is used by? Twitter Apps. That's right.

Did you even look at the list? Music Player (Remix) is... well, a music player. But it does have post to Twitter built-in so that had to be updated. And if things like Grooveshark have that built-in too then they need to be updated as well.

Believe it or not, I'm still using Tweed. I purchased many of the other twitter clients, but it is the easiest on my eyes. If I recall correctly, it was supposed to cease to function months, if not years, ago, so I guess I count myself lucky. I don't know what I'll use once it actually stops working. :(

Not directly a Twitter client, but I just submitted Headlines 2 as an update to the AppCatalog which also includes the change to the new Twitter v1.1 API.
When approved by Palm/HP/LG you can share news, articles and so on to Twitter like with the v.1.0 API.

Today I got updates for Glimpse and incredible!. Many thanks to Inglorious Apps and Zhephree for their continuing support of our beloved OS.

I was using Carbon until a week ago when it first stopped working. The Carbon dudes said they weren't going to support webOS anymore a while back. It's a shame - I feel Carbon was the fastest twitter app for webOS and it *just worked*. I especially liked its Power Scroll that never seemed to catch on. Oh well.

As of right now, Spaz ad Macaw are working great. Macaw seems to be the replacement I'll stick with until I fully move over to Windows Phone...

Sadly my little Pre2 is looking at a retirement any day now.

I was using Carbon until a week ago when it first stopped working. The Carbon dudes said they weren't going to support webOS anymore a while back. It's a shame - I feel Carbon was the fastest twitter app for webOS and it *just worked*. I especially liked its Power Scroll that never seemed to catch on. Oh well.

As of right now, Spaz ad Macaw are working great. Macaw seems to be the replacement I'll stick with until I fully move over to Windows Phone...

Sadly my little Pre2 is looking at a retirement any day now.

I have Carbon, Graphite and TweetPad on my HP TouchPad and none of them have been updated to support API 1.1

Any other suggestions for a TouchPad formatted Twitter client that works with API 1.1? Doing a quick search in the App Catalog, I see Glimpse is coming up. Also incredible! is showing up.

I really liked TweetPad. So wishing it would have been updated to support API 1.1