You are correct. The PIN handshaking is only for Desktop Apps.
Ryan
On Mon, Jan 18, 2010 at 9:12 AM, eco_bach bac...@gmail.com wrote:
Jeff, I might be wrong, as there seems to be some confusion on this,
but I believe the extra PIN handshaking is ONLY required for what
Twitter defines as
Is a mobile app more like a desktop app or a web app? The PIN in the
'desktop' flow handles this in the 'non-desktop' flow:
Once Jane approves the request, Faji marks the Request Token as
User-authorized by Jane. Jane’s browser is redirected back to Beppa, to the
URL previously provided
Native mobile apps(native Android, native IPhone, etc., meaning they run on
the device itself and NOT in the browser) are considered Desktop apps.
Yes, the mobile UX is one of the biggest issues with Twitter's OAuth
implementation.
Ryan
On Mon, Jan 18, 2010 at 11:35 AM, Jeff Enderwick
On Jan 18, 11:48 am, Jeff Enderwick jeff.enderw...@gmail.com wrote:
mobile browser cpu/mem requirement mobile twitter client cpu/mem
requirement.
Yeah ... I don't develop mobile apps, but I suspect you're right. It's
too bad pure HTML has such a lame user experience, because if you
could live
On Jan 17, 10:46 am, Abraham Williams 4bra...@gmail.com wrote:
It is best practice to always send the user to Twitter in their browser of
choice not embedded in another webpage/application.
Abraham
Thanks! I was just about to code something up to do it the other way!
