2

I could see, we have two options for integrating twitter in Andriod Apps.

1. Twitter REST Api
2. Twitter Fabric - Twitter Core

what is the difference between both. Is it only the way to access the data is different ?(Twitter REST Api is calling GET request and we get response. and Twitter Core is an SDK, we just call methods and use it.)

Whether Twitter continue its support for both REST Api and Twitter Fabric.

Note: I know about Twitter4J, which is external api which in turn calls REST APi. please don't provide info for Twitter4J. I don't want any info for external library.

Little confusing which one to use. Any help is appreciated.

UPDATE:

I could see single signon as one useful difference. It allows sync the twitter accounts configured in twitter app, which can't be achieved using REST API.

Suhaib
  • 2,031
  • 3
  • 24
  • 36
Sowmia Sundararajan
  • 1,613
  • 2
  • 14
  • 17

1 Answers1

0

It depends on you what you want to use twitter fabric is just not for integrating twitter,it is a platform which provides other functionalities like crash reports via crashlytics and monetization etc. but you still need to do network requests for getting tweet and other data from twitter and you will need to integrate the sdk in your application which will increase the size of your app. So if you just want to get the data from twitter and do not want to compromise with the app size you may use the rest apis,but if you think you can benefit from other features provided by the fabric platform then i would definitely recommend to use fabric

Pramod Yadav
  • 2,316
  • 2
  • 23
  • 36
  • Thanks for taking your time ... I am just comparing Twitter Fabrics's - Twitter Core and REST API. I could see single sign on as a added feature in Twitter Core. Is there any other advantage over it.? – Sowmia Sundararajan Jul 14 '15 at 11:32
  • 2
    if apk size doesn't matter to you,i would suggest to use twitter core as it has tweet ui and tweet composer built into it – Pramod Yadav Jul 14 '15 at 11:58