jump to navigation

Can OpenID solve the mobile web application login problem? February 25, 2008

Posted by James Webster in : web, mobile , add a comment

LinkedIn have announced LinkedIn Mobile (via TechMeme) available at http://m.linkedin.com. The ‘m.’ prefix has definitely become the defacto way to access mobile-specific versions of web applications; so much for the .mobi TLD then which is after all a pain to enter onto a phone keypad without the benefit of T9.

Anyway, having a mobile version of LinkedIn and Facebook and which-social-network-is-hot-this-month is all good but now I have the challenge of having to enter my username and password for the mobile version as well. See, since I use Johannes la Poutré’s Password Composer bookmarklet to generate a unique password based on a hash of the website’s domain and a strong password that never leaves my browser (see Jon Udell’s excellent screencast from 2005 on Simple Single Sign-On to understand more) I don’t really know what my password for LinkedIn/Facebook/etc is, at least not off the top of my head.

It has struck me that OpenID could provide a solution here. If my carrier offered an OpenID provider tied to my phone number I could authenticate to OpenID-compatible websites using my phone in hopefully a reasonably transparent fashion, once I had maybe used the main web interface of LinkedIn (or Facebook, etc, etc) to approve my OpenID on my mobile carrier’s provider.

OpenID has seen a growth in support from big players in the industry, with Google, VeriSign, IBM, Microsoft and Yahoo! all joining recently as corporate board members of the OpenID Foundation. Some of them have OpenID-access enabled to their web applications or OpenID-providers available as beta releases. Major mobile carriers are conspicuously absent however. To me, it seems like they missing a major opportunity to innovate.

Oh, and here’s a link to my LinkedIn profile :-).

bluepulse; konfabulator for mobile phones January 20, 2006

Posted by James Webster in : mobile , 4 comments

MobileCrunch has a writeup on Bluepulse, and since they are an Aussie startup in the mobile space I feel obliged to bring them to your attention.

Isaac Timothy makes a good point in the comments however:

Just a thought. Hasn’t Opera released a software development kit using AJAX technology that allows developers to create also platfrom independent applications. What is the difference between these two products?

That is indeed true! And I’m keen to hear about the differences as well. If the products are indeed technological similar, Opera has an advantage with its existing relationships with carriers. Read more about the Opera Mobile Platform at the source or over at Russell’s blog.

Still, gotta wish the Aussies the best of luck, and hopefully I’ll get to check it out on my Nokia 6600 soon!