Simple sharing with Facebook and Twitter
Now it is difficult to meet a site without the Share button (I’m not even talking about “Like”): this is a fast and convenient way to share interesting information with friends and foes through various social networks. The same “button” can be used in your Android application. It is not necessary that the application be a Facebook client: you can simply give the user the opportunity to send himself a simple message to the wall, like “I use Android Yorshik! Try you too! ” Well, this is hypothetical.
But in fact, in the last project I had to provide the user with the opportunity to poison messages (and pictures) on Facebook and Twitter about his progress, and of course, there were some pitfalls (where could they be without them). Before writing the article, I decided to isolate the part of the code responsible for sharing, in a separate component, to demonstrate working with the Facebook API and Twitter API. But then Ostap suffered, and the result was a reusable tool for simple sharing on Facebook and Twitter (and in the future, on other social networks). By “simple sharing” I mean the ability to only send a message or a picture. There is no simple “sharing” to “zafrenit” or “retweet”. Simple functionality - simple interface! I tried to hide all the difficulties of working with the API behind a beautiful facade. But more on that further ...
So, we have a task: send a message to your Facebook wall on your own behalf, update your status on Twitter. Both there and there authorization occurs using OAuth (the principles of OAuth authorization are well reflected in this scheme ). First of all I climb at the office. sites hoping to find something ready.
Facebook
Facebook was pleased with the presence of the official Android SDK, which you can take on GitHub , as well as detailed instructions for starting using this SDK in your application. I can’t say that everything in the SDK is mega-simple (some parameters cause questions), but it performs the authorization task perfectly: we just need to call
To understand what kind of “me / feed” is - you will have to get into the concept of Open Graph Facebook. But this is only if you want to use the full power of the available Facebook API.
The first underwater stone met here: if the Facebook client application is already installed on the device, the facebook.authorize (...) authorization request will not lead to a dialogue with WebView inside, but to launch this client application and open its login form. According to the plan, after authorization, you will return to your application as well as after the dialogue. But, if suddenly you have something slyly tied up in onResume () or onStop () you will have to take into account that they may be called once more. On one device, this form of authorization generally worked anyhow. So I would just like to be sure to always log in via Dialog. And there is such a possibility: an additional parameter Facebook.FORCE_DIALOG_AUTH will help with this. Call:
Twitter
But Twitter did not endorse developers with the official SDK. But the informal abound, with different possibilities. The first thing that got into consideration:
After testing the libraries, it was decided to cross Twitter4J and the UI part of the Sugree project. By trial and error, two ways of authorization were discovered.
1) In the first case (at the moment it is used in the implemented tool) when registering your application on dev.twitter.com we leave the “Callback URL” field empty. Then after the user enters the authorization data and clicks "Authorize / Authorize" he will be transferred to the page with a PIN code, which is generally not clear where to enter. But we need it, because only by transferring it to the Twitter service we will be able to get authorization "token and secret". To torture the user once again by entering codes of this kind is a thankless task. Therefore, we take and parse the HTML page and rip out this pin-code from it. How to get the HTML code loaded in the WebView page? Not difficult at all:
That's all, removed the pin code - completed the authorization.
2) And now the correct way: in the properties of your application on dev.twitter.com in the field
“Callback URL” insert any valid URL (eg “http: //your.shik” ). And now, instead of parsing the page with the pin code, we need to catch the callback from Twitter, whose URL will contain the oauth_verifier parameter, which we will use instead of the pin code to get all the same “token and secret”. This principle has been successfully implemented in this project , and in the near future I planto implement the same logic in myself.
')
A few words about the created project, which was called Simple Social Sharing . As already mentioned at the beginning, the main purpose of the project is to provide a simple API for simple sharing with Facebook and Twitter (in the long term and with other social networks). A simple API includes 4 (+1) methods:
Dialogues will look like this:
All that is needed for work is:
Perhaps the following FacebookFacade method will raise a question:
The code and the illustration of the result, I think, will explain everything:
I think that's all. In the nearest plans of the project - to redo the authorization to use callbacks, to completely get rid of the use of heavy Twitter4J. Well, we'll see.
As always - source on github . I hope the tool is useful to you. Applications for adding support to some other social network are also being accepted (Google+, unfortunately, has not yet provided a coherent SDK).
UPD: At the request of workers. If you think that once a client does not have a specific social network installed, then he doesn’t want to fumble into this network, then you can use the simplest method of sharing (no libraries need to be screwed):
Thanks NikitaG for an example of the simplest sharing.
But in fact, in the last project I had to provide the user with the opportunity to poison messages (and pictures) on Facebook and Twitter about his progress, and of course, there were some pitfalls (where could they be without them). Before writing the article, I decided to isolate the part of the code responsible for sharing, in a separate component, to demonstrate working with the Facebook API and Twitter API. But then Ostap suffered, and the result was a reusable tool for simple sharing on Facebook and Twitter (and in the future, on other social networks). By “simple sharing” I mean the ability to only send a message or a picture. There is no simple “sharing” to “zafrenit” or “retweet”. Simple functionality - simple interface! I tried to hide all the difficulties of working with the API behind a beautiful facade. But more on that further ...
So, we have a task: send a message to your Facebook wall on your own behalf, update your status on Twitter. Both there and there authorization occurs using OAuth (the principles of OAuth authorization are well reflected in this scheme ). First of all I climb at the office. sites hoping to find something ready.
Facebook was pleased with the presence of the official Android SDK, which you can take on GitHub , as well as detailed instructions for starting using this SDK in your application. I can’t say that everything in the SDK is mega-simple (some parameters cause questions), but it performs the authorization task perfectly: we just need to call
facebook.authorize(Activity activity, String[] permissions, DialogListener listener); Bundle params = new Bundle(); params.putString("message", "Android Yorshik is great!"); facebook.request("me/feed", params, "POST"); To understand what kind of “me / feed” is - you will have to get into the concept of Open Graph Facebook. But this is only if you want to use the full power of the available Facebook API.
The first underwater stone met here: if the Facebook client application is already installed on the device, the facebook.authorize (...) authorization request will not lead to a dialogue with WebView inside, but to launch this client application and open its login form. According to the plan, after authorization, you will return to your application as well as after the dialogue. But, if suddenly you have something slyly tied up in onResume () or onStop () you will have to take into account that they may be called once more. On one device, this form of authorization generally worked anyhow. So I would just like to be sure to always log in via Dialog. And there is such a possibility: an additional parameter Facebook.FORCE_DIALOG_AUTH will help with this. Call:
facebook.authorize(context, permissions, Facebook.FORCE_DIALOG_AUTH, authListener); and authorization will consistently take place through dialogue.But Twitter did not endorse developers with the official SDK. But the informal abound, with different possibilities. The first thing that got into consideration:
- Sugree Twitter Android SDK is essentially a Facebook SDK clone tailored to the Twitter API. However, all he can do is provide user authorization (but at least there is a ready-made UI for user login)
- Twitter4J - a powerful set of libraries, extensive functionality for working with Twitter (no UI)
- JTwitter - less extensive than Twitter4J, but ample functionality (no UI)
After testing the libraries, it was decided to cross Twitter4J and the UI part of the Sugree project. By trial and error, two ways of authorization were discovered.
1) In the first case (at the moment it is used in the implemented tool) when registering your application on dev.twitter.com we leave the “Callback URL” field empty. Then after the user enters the authorization data and clicks "Authorize / Authorize" he will be transferred to the page with a PIN code, which is generally not clear where to enter. But we need it, because only by transferring it to the Twitter service we will be able to get authorization "token and secret". To torture the user once again by entering codes of this kind is a thankless task. Therefore, we take and parse the HTML page and rip out this pin-code from it. How to get the HTML code loaded in the WebView page? Not difficult at all:- create a JavaScriptInterface where the HTML code of the page will come
class MyJavaScriptInterface { public void processHTML(String html) { // process HTML } } - add this “interface” to webview
webView.getSettings().setJavaScriptEnabled(true); webView.addJavascriptInterface(new MyJavaScriptInterface(), "HTMLOUT"); - and finally execute the JavaScript code after the page is fully loaded
webView.setWebViewClient(new MyWebViewClient()); ... private class MyWebViewClient extends WebViewClient { ... @Override public void onPageFinished(WebView view, String url) { super.onPageFinished(view, url); browser.loadUrl("javascript:window.HTMLOUT.processHTML('<head>'+document.getElementsByTagName('html')[0].innerHTML+'</head>');"); } }
That's all, removed the pin code - completed the authorization.
2) And now the correct way: in the properties of your application on dev.twitter.com in the field
“Callback URL” insert any valid URL (eg “http: //your.shik” ). And now, instead of parsing the page with the pin code, we need to catch the callback from Twitter, whose URL will contain the oauth_verifier parameter, which we will use instead of the pin code to get all the same “token and secret”. This principle has been successfully implemented in this project , and in the near future I plan
')
Simple social sharing
A few words about the created project, which was called Simple Social Sharing . As already mentioned at the beginning, the main purpose of the project is to provide a simple API for simple sharing with Facebook and Twitter (in the long term and with other social networks). A simple API includes 4 (+1) methods:
- isAuthorized () - checks if the user is authorized and whether the current session is valid
- authorize () - causes a dialog through which the user will log in
- publishMessage (...) - publishes the message
- publishImage (...) - publishes an image (only for Facebook)
- logout () - clears the current session, deletes the saved "token and secret"
Dialogues will look like this:
All that is needed for work is:
- FacebookFacade and TwitterFacade facades that provide the above methods. They are created as follows:
FacebookFacade facebook = new FacebookFacade(activity, FACEBOOK_APP_ID); TwitterFacade twitter = new TwitterFacade(context, TWITTER_CONSUMER_KEY, TWITTER_CONSUMER_SECRET); - FacebookEvents and TwitterEvents , which accept subscriptions to authorization events ( onAuthSucceed () and onAuthFail () ), about posting messages ( onPostPublished () and onPostPublishingFailed () ), about logout ( onLogoutComplete () ). You can add your listeners, but it is important not to forget to delete them later.
Perhaps the following FacebookFacade method will raise a question:
publishMessage(String message, String link, String linkName, String linkDescription, String pictureUrl, Map<String, String> actions) The code and the illustration of the result, I think, will explain everything:
String message = "Look at this great App!"; String link = "https://github.com/nostra13/Android-Simple-Social-Sharing"; String linkName = "Use Android Simple Social Sharing in your project!"; String linkDescription = "Also see other projects of nostra13 on GitHub!"; String pictureUrl = "http://cdn.androidcommunity.com/wp-content/uploads/2011/01/facebook-android-logo-1.jpg"; Map<String, String> actions = new HashMap<String, String>(); actions.put("Android Simple Social Sharing", "https://github.com/nostra13/Android-Simple-Social-Sharing"); facebook.publishMessage(message, link, linkName, linkDescription, pictureUrl, actions); I think that's all. In the nearest plans of the project - to redo the authorization to use callbacks, to completely get rid of the use of heavy Twitter4J. Well, we'll see.
As always - source on github . I hope the tool is useful to you. Applications for adding support to some other social network are also being accepted (Google+, unfortunately, has not yet provided a coherent SDK).
UPD: At the request of workers. If you think that once a client does not have a specific social network installed, then he doesn’t want to fumble into this network, then you can use the simplest method of sharing (no libraries need to be screwed):
final Intent intent = new Intent(Intent.ACTION_SEND); intent.setType(«text/plain»); intent.putExtra(Intent.EXTRA_TEXT, "Try Android Yorshik!"); startActivity(Intent.createChooser(intent, getString(R.string.app_name))); Thanks NikitaG for an example of the simplest sharing.
Source: https://habr.com/ru/post/135342/
All Articles