Archive for the 'developers' Category

Thursday, April 30th, 2009

I just wrapped up a day and a half at AT&T’s business analyst event here in New Jersey. I “live tweeted” the event to some extent – see here for a broad view of some of the themes discussed there.

But one of the things I was most encouraged about and interested in was some of AT&T’s activities that I would classify as fitting within my social telco definition. As AT&T expands into the cloud computing space, it will be launching storage-as-a-service and compute-as-a-service offerings in the coming months. But it will also be developing something it calls “platform-as-a-service”. It’s not the best name, because it’s not all that descriptive – as a colleague said, it reminds you of Salesforce’s efforts to expand from its core CRM-as-a-service proposition to something broader. But the concept is good, even if the nomenclature isn’t.

What platform-as-a-service would do is expose both computing and network functionality through APIs to third parties. This would allow those third parties – whether ISVs, enterprises developing their own apps or even web players – to create apps that would be able to issue commands to AT&T’s compute and network infrastructure. The focus in AT&T’s presentation on the topic was on the compute-type commands, but the plan is very much to roll out more or less the full set of Parlay X commands over time in handfuls at intervals over the next year or two, starting later this year. 

One of the things I found interesting about this is how AT&T is approaching some of the greatest challenges associated with exposing this kind of functionality to third parties: namely, verifying identity and providing security in order to protect privacy. AT&T is piggybacking off its efforts on the mobile application side here, benefiting from its DevCentral developer community and the processes and interfaces developed to facilitate the development of mobile apps by partners. This is probably a good model for other telcos with well developed mobile developer ecosystems since a lot of the legwork has already been done. 

I’m going to be requesting a more detailed briefing on these activities, and especially on the linkages between consumer and business efforts in this area, and will likely put something together for publication subsequently. But this certainly looks like an interesting and promising initiative from AT&T in this area, and one that other telcos can learn from.

Monday, March 3rd, 2008

Of late, I’ve just been struck by how frequently new software development work is being done for the iPhone – whether it’s LinkedIn’s new mobile interface, Gmail’s latest mobile updates or Remember The Milk’s mobile features. All this is being done for a device with 2% or less of smartphone market share, and which is the only device with its OS. Compare that with other mobile operating systems like Windows Mobile, Symbian, RIM’s OS and even Palm and they all dwarf iPhone’s share.

Now, if I were a developer, I imagine I might quite enjoy the challenge of developing for such an attractive and highly-functional platform. But in doing all this, these developers are tying up finite resources in developing a platform which will serve only a small fraction of the userbase of their web services / sites. And although not all these companies’ mobile development resources are going into iPhone they often seem to launch for that platform first, and roll out the newest and best features there first too. Admittedly, this is partly because the iPhone is a much more capable platform than its competitors, but even so these companies are alienating the 95% plus of their users who are not iPhone owners but do want to use their mobile devices to access their services.

Now, I’m speaking here mainly as a non-iPhone-using mobile user. I resent some of this at a personal level, but that’s neither here nor there in the grand scheme of things. The larger implication is that those other mobile platforms need to take notice of this trend and do something about it. Apple hasn’t released the SDK for the iPhone yet (though that’s imminent) and it has a tiny market share, but even so developers are paying attention and prioritizing iPhone development. This should tell those responsible for other operating systems and device platforms that they have some serious catching up to do in order to attract that kind of energy and attention. Just think what will happen when the iPhone actually has significant market share…