mobile browser cpu/mem requirement >>> mobile twitter client cpu/mem
requirement.

On Mon, Jan 18, 2010 at 11:31 AM, M. Edward (Ed) Borasky
<zzn...@gmail.com>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
> custom thin client or a browser running on the mobile. Mobiles don't
> have the same kind of horsepower, they don't have (yet) practical
> spoken text input or keyboards, and there are far too many different
> configurations for a practical portable native mobile desktop app.
> Mobile apps are all about communication, as is Twitter, and that's
> what servers are for.
>
> On Jan 18, 9:39 am, ryan alford <ryanalford...@gmail.com> wrote:
> > 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
> > <jeff.enderw...@gmail.com>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 providedhttp://beppa.com/ordertogether with the Request
> > > Token. This allows Beppa to know it can now continue to fetch Jane’s
> photos.
> >
> > > With desktop (and possibly unanticipated) mobile apps, there isn't that
> > > redirect back. I'm all for whatever makes the best UX for oath+mobile.
> >
> > > On Mon, Jan 18, 2010 at 6:20 AM, ryan alford <ryanalford...@gmail.com
> >wrote:
> >
> > >> 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 'Desktop Apps'.
> > >>> See the response to my questions here
> > >>>http://bit.ly/5xbydH
> >
> > >>> As a newcomer to OAuth and the Twitter API I'm currently muddling
> thru
> > >>> the whole proxy requirements(I'm using actionscript)
>

Reply via email to