Taylor,

Do you have screens showing the work flow how this Web Intents work on
UIWebView?

Or any working iOS & Android codes we can use as references?

On Apr 5, 10:25 am, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> Hi Vince,
>
> There's actually a much easier way for you to implement the simple ability
> to Tweet from your application without having to code up the OAuth song &
> dance or xAuth, but the frictionless approach comes with the downside of
> less control, attribution, and feedback.
>
> Web Intents (http://dev.twitter.com/pages/intents) has a "Tweet Intent"
> where you would just direct the user tohttp://twitter.com/intent/tweet--
>  if your webview was aware of the current user's twitter.com session,
> authentication would already be handled -- otherwise the user would quickly
> log in and have the ability to Tweet. You can prepare a message, make the
> tweet a reply, use a retweet instead, and a few other options.
>
> @episod <http://twitter.com/episod> - Taylor Singletary
>
> On Tue, Apr 5, 2011 at 10:05 AM, Vince <svguer...@gmail.com> wrote:
> > I've been doing some research on this, and just wanted to confirm that
> > this is what needs to happen in order to develop an iPhone app that
> > has a page which allows a user to simply login to Twitter, then tweet
> > a quick message to their "wall" (no other Twitter functionality is
> > needed, this is a very small feature of a large application).  This
> > may be as simple as a "yes" or "no" question, but I just wanted to
> > confirm before I say this needs to happen, to this client:
>
> > 1) Client must create Twitter account and then create/register an app
> > 2) Client must send me, the developer, the Consumer Key/Secret
> > 3) Client must send an email to a...@twitter.com to get approval for
> > the app to use XAuth
> > 4) Once "approved", then I can develop against that app to authorize
> > and allow users to share to their wall
>
> > Is there an easier way to go about this functionality, or is this the
> > path that must be taken?  Either way is fine, just wanted to make
> > sure.  Thanks for any help with this, as I am very new to using the
> > Twitter API.
>
> > -Vince
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to