mobile browser cpu/mem requirement >>> mobile twitter client cpu/mem
requirement.
On Mon, Jan 18, 2010 at 11:31 AM, M. Edward (Ed) Borasky
wrote:
> To be fair, I don't think "native mobile apps" *should* be written as
> "desktop apps". You should be building them as servers, with either a
> custo
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
wrote:
>
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 http://bep
You are correct. The PIN handshaking is only for "Desktop Apps".
Ryan
On Mon, Jan 18, 2010 at 9:12 AM, eco_bach 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 'Desktop Apps'.
