Thanks Dave,
this could be a good approach.
Something like a "social proof" is good enough, and this
brings me to mind that project:

Where any developer can submit their app, and any user can comment it:

In any case,
answering this question involves a social point of view,
a design and UI experience point of view, and a "politically correct"
point of view (as you stated don't say what you are not doing by
batch processing...), so you got some good points of those ones ;)

Also, there's a difference between Twitter and Facebook, because
of Facebook Canvas. "Embedding" the app in Facebook give the users
more confidence with the app itself, since is not something out of the
but it something "belonging to" Facebook itself.

So if you trust Facebook, you probabily would trust such an app.

I figure out also the different UI experience between Twitter oAuth
popup based or redirect based and  - finally - via the xAuth on
mobile devices.

Those three ui experience, bring us a lot of questions
about which is the best user experience during the authorization


On 26 Ott, 18:17, Dave-twiends <> wrote:
> I totally agree. It would be difficult for twitter to do this...
> Give your users confidence by proactively anticipating their fears and
> addressing them. Figure out what would stop them from signing in with
> OAuth and answer those questions upfron. The example is
> very good as it demonstrates this process, and shows specific answers
> to specific fears.
> Perhaps also show some "social proof". tell them how many other user
> are successfully using your app. Have you got 100,000 users..? Well if
> you do then tell them that 100,000 users are using your app safely
> already, and have all signed in with OAuth. 100,000 is just an
> example..
> Address the topic in your support forums with specific articles,
> questions and answers too. And finally, honor their confidence. If you
> say you'll never tweet to their account, NEVER tweet to their account.
> If you betray this unspoken trust then all will be lost..
> If you can get this right then you'll really see your conversions
> climb..!
> Good luck
> Dave
> On Oct 26, 4:53 pm, Nik Fletcher <> wrote:
> > I'm not sure what sort of "Verification" you're looking for - however,
> > you might want to take steps on your own end to reassure users why
> > they're being sent to Twitter. See, for example, Favstar.
> >
> > It's the your job as an application developer to instil confidence in
> > the user to feel happy entering their credentials.
> > -N
> > On Oct 24, 12:56 am, loretoparisi <> wrote:
> > > Hi,
> > > I'm cto for and, oauth based twitter apps.
> > > Many users told us that they just don't use our oauth sign in service,
> > > since it seems to them to be unsafe with this kind of sign in (single
> > > sign-on from oauth client site)
> > > This is not a design problem I guess, but a people misunderstanding
> > > problem, about the authorization protocol (going away from people like
> > > developers, engineers, etc, who really knows what oAuth is about?),
> > > even if we tried to explain this process as well in our sites tos.
> > > I was wondering if you @twitter have any idea in the future to
> > > certificate an app in order this app to be "verified" by twitter (in
> > > the same way some accounts are).
> > > In this ways app users would not be scared when clickin on "Sign in to
> > > Twitter" buttons.
> > > Of course using Twitter's button styles would be a better experience
> > > for the user in order to trust the thirdy-party service, but this is
> > > not possibile in all cases.
> > > Thanks,
> > > Loreto Parisi
> > > CTO at stickphone, lyricsmood
> > >
> > >

Twitter developer documentation and resources:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:

Reply via email to