Since Twitter announced that they will be discontinuing support for the Twitter SDK for iOS, Android and Unity (https://blog.twitter.com/developer/en_us/topics/tools/2018/discontinuing-support-for-twitter-kit-sdk.html), I am unsure of the best way to proceed with my application. I am specifically interested in options for iOS.
I am currently only using a subset of the full capabilities, primarily:
Authentication
Fetching tweets
Displaying tweets
For authentication, OAuthSwift looks to be a possible replacement.
https://github.com/OAuthSwift/OAuthSwift
For fetching tweets from the API, Swifter is a library that I have been using and could continue to use.
https://github.com/mattdonnelly/Swifter
However, I'm currently using the TWTRTweetView class of the Twitter SDK and am not aware of any other options to replace this.
Twitter seem to be suggesting to use web views to display tweets in apps but this option doesn't lend well to my use cases. I'm looking for a native solution.
Can anyone suggest any other alternatives or approaches to take in light of these developments?
As mentioned in the blog :
Documentation and source code for all three SDKs on GitHub will remain
available for consumption in an archived state.
Also,
You can fork the Twitter Kit project and build it into your app, or
copy the parts you need into your app. Or you can use Twitter’s
standard API to power your own native displays and login
functionality.
Related
I am new to iOS development and need to make a change to an iOS app I'm taking over to add video to a tweet. My current app UI allows the user to type in text for a tweet but I would be changing that to allow them to pick a video to upload along with the tweet similar to how the Twitter app works.
I see the Twitter API supports uploading video but I haven't been able to find any good examples on how to accomplish this using XCode and Objective-C. Any recommended approaches or tool kits I can leverage to accomplish this?
https://dev.twitter.com/rest/public/uploading-media
I had to roll my own solution. Check out my project https://github.com/mtrung/TwitterVideoUpload.
Light-weight due to using built-in Apple's Social framework to keep things light. No need to add extra frameworks such as TwitterKit and Fabric.
Support chunk upload.
Built-in support for user's credential retrieval
Thanks for the -1 that was helpful. So thought I found the answer with Fabric (https://get.fabric.io/). The Android side supports image and video upload with a tweet but the iOS side does not (image only). It looks like you have to roll your own solution including building a video picker. Then you can use the Twitter REST API to upload the video. Not exactly what I was hoping for but it is doable.
This link shows Objective C and Swift code to do the video upload Share video on Twitter with Fabric API without composer iOS.
I hope this is not off topic for StackOverflow since it is not just software development related but also marketing. But I guess this problem is something we developers are all confronted to.
To monitor and market our iOS app, we use a bunch of third party SDKs:
Google Analytics to understand what's happening
a push notification system (e.g. Urban Airship)
a "smart" review prompting engine (e.g. Apptentive)
a testing / crash reporting system (e.g. Testflight)
should you want to run app installs ads, you also need the FB SDK, an SDK to track Twitter conversions, etc.
you may also want to track where other installs come from via something like Tapstream.
So we are already running more than 6 3rd party SDKs in our app, and it does not feel right:
each of them will do some kind of hand shake every time the app is opened
it's as many potential issues
each of them will have a different web interface
Is there a way to optimise all this, i.e. to have just one SDK doing most things? Or does someone know of a lib to wrap all this stuff under one lib for instance?
There is no getting around a few of these. If you want to talk with FaceBook, Twitter, etc. You will need their SDK no matter the 3rd party SDK you choose.
You could actually write your own setup to track and deal with everything, but there are those that have done it before.
For example, Parse will do:
Analytics
push notifications
a "smart" review prompting engine (you can do this yourself by reviewing the analytics)
crash reporting system
it also uses FB SDK, Twitter SDK already to help with user logins where users my want to use their credentials from their sites on your app
user login
cloud database
You could technically throw an "event" into the analytics to track how many folks are using your app that was installed from x store. However, this would require a different version of your app for each store. Sounds like an interesting idea none the less. Tapstreme and others are basically marketing though, not really something required to do something specific. You will need an SDK if they are tracking something specific themselves.
one web interface
There are multiple systems built like this. they are called BaaS or Backend as a Service.
Hope this helps, Cheers
I am new bie to xcode.I want to create google glass app in ios.I googled many sites.But didn't find proper information regarding this and even want to know how to upgrade google glass API in xcode. please give any links and suggestions to develop sample google glass app in xcode.Thanks for your suggestions in advance.
You'll be using the Mirror API, which is a REST based web API. Although the Google Objective C library supports the Mirror API, there is not a lot of documentation on its use. You can see the Mirror API documentation for generic guidance which you will need to apply to the specific ObjC implementation.
Update: While you don't need to download or use this library, if you don't, you'll need to use HTTPS calls to Google's servers instead. You should read the documentation about the Mirror API at https://developers.google.com/glass/
In my App, I have used MGTwitter Engine. I used twitter in many files in app.
Now there is Twitter 1.1 is announced.
I want to know where I can download API 1.1 for iOS.
What are changes I need to do in my existing code?
I tried to read the documentation of twitter, but new version looks much different than previous which I am using.
Based on latest fragmentation report - http://appleinsider.com/articles/13/06/20/apple-now-charting-app-store-ios-fragmentation-just-like-googles-android there is no need in implementing Twitter as external library/SDK.
Currently there is more than 93% users on iOS 6 and plus 5% iOS 5. You can safely use internal iOS integration of Twitter and cover 98% users.
Read here about this: http://developer.apple.com/library/ios/#documentation/Twitter/Reference/TwitterFrameworkReference/_index.html
If you will still want to use external library - please se the ShareKit https://github.com/ShareKit/ShareKit I believe that they have already implemented 1.1 API. But since I don't use their library I'm not 100% sure.
I want to write app that is heavily integrated with Facebook. I'm not sure what shoud I use - sdk provided by Facebook or new Social Framework provided by Apple. Do you know some pros and cons of them?
[EDIT]
I ended using Social Framework provided by Apple, because it's much easier to integrate, It will be develop in future, and I have access to device owner Facebook account, so user don't have to log in to Facebook when using my app. I want to do some custom stuff, so I get oauth token from ACAccountCredential and then I make requests with AFNetworing to Facebook's Graph API.
The Social Framework is designed for simple, site-neutral data manipulation. Examples might include getting the user's 'activity feed' (as described by the docs) or posting a new status or photo. It currently works with Twitter, Facebook and Weibo however, other than lack of features, the current main disadvantage is that it is limited to iOS 6, which won't be as much of a problem in the future.
On the other hand Facebook does have an iOS SDK that makes it reasonably easy to integrate Facebook into your app, and it is much more powerful than the Social Framework. Another benefit is that support goes back to iOS 4.3.
I'd recommend using the Facebook iOS SDK over writing your own custom one and using OAuth because Facebook has already done the work for you.
I've struggled with this decision for a long time and came to this conclusion. If your app doesn't care for iOS 5 and older phones, then the iOS Social framework is the way to go, as it allows the user to share with any of the popular social outlets (Facebook, Twitter, email, Weibo, SMS...) just like one can do in mobile safari. According to Apple, 89% of the iDevices are already on iOS 7. The percentage will be higher if you include iOS 6.