If it is a web-based mobile app, using the twitter/facebook icons or a share-this type solution works. It does not work if you are planning on creating an html5/js app and then using a framework like Phonegap to create a "native" application to be downloaded from various app stores.
That requires a bit more work with childbrowser and dealing with facebook connect and twitter's OAUTH api's.
I am developing a mobile application using jQuery Mobile and converting that to native application using PhoneGap. In my application I have a functionality of sharing a link to Facebook and Twitter. In regular browser based application we just keep the share link in our page which will redirect the users to facebook page and login and then share. If the user sharing another link, since the facebook session is available it won't ask them to login again.
I want to achieve the same kind of approach here. In your reply you said "That requires a bit more work with childbrowser and dealing with facebook connect and twitter's OAUTH api's". So can you please explain why we need to use API's and how to implement it?
You need to use an API because your app is going to act as the user, and you are not going to rely on an external browser remembering the user's login. This is more convenient for the user, and, as well, mobile users are more likely to be using a native Facebook app, and wouldn't normally be using the browser to access Facebook.
oAuth and the API allow your app to act on behalf of the user, without the user giving your app their login credentials.
Leave a comment on watusiware's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic