Hi Raffi and everyone,
Firstly, Twitter is doing better than some other oAuth pages I could
At Xumii we’re using Twitter mobile oAuth on a wide range of phones,
from low-end feature phones to high-end smartphones. A recent QA cycle
revealed 7 out of 30 Most Popular devices not coping with Twitter
mobile oAuth: Samsung C3110, Nokia 3120, SE G502, SE C905, LG KU990,
Nokia N96, SE W705.
But… rather than tracking individual defects on specific handsets, how
about a standards-based approach, using something like the w3 MobileOK
Currently, Twitter mobile oAuth scores 68% when the user is already
logged in to Twitter, and 79% when the user isn't yet logged in.
@raffi i’ll email over the MobileOK reports which explain more; it’s
the CSS, the images, the DOCTYPE, and the HTTP headers.
Aiming for 100% on MobileOK should solve a big chunk of current issues
on those lower-end feature phones.
What do you think?
On Apr 29, 9:07 pm, Raffi Krikorian <ra...@twitter.com> wrote:
> i'll follow up on this - do you have a notion of what browsers, what phones,
> etc. your users are coming from
> On Thu, Apr 29, 2010 at 1:49 AM, twittme_mobi <nlupa...@googlemail.com>wrote:
> > Hello,
> > I migrated my mobile web site to OAuth.
> > Now, I have a lot of users complaining that the OAuth page of twitter
> > is not
> > mobile friendly.Some of them are getting just a blank screen or just
> > cannot open it.
> > My honest question is - this is being discussed many times but where
> > are we with this?
> > Are all those users really suppose to get such a bad user experience?
> > on a login page?Is it so hard to create such page just for mobile
> > browsers?
> > Is anybody handling this - I mean it is an obvious problem that we
> > have for more than a year already.
> > Any comments on this are highly appreciated.
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi