If you’ve arrived here after clicking on a link in a Twitter message, welcome!  Please read on.

Historically, providing developer-level access to any features of a mobile network has been tricky, to say the least. Even with the relevant service provisioning completed, you’re still stuck with a myriad of interfaces, standards, web protocols and security methods. And that’s just with one operator. As soon as you hit your second there’s usually a whole new set of enabler access methods to implement.

These difficulties have resulted in relatively few applications making use of mobile network APIs. Some operator groups – notably Telenor and Vodafone – have been piloting developer programs which generally formalize broader access to the various enablers (e.g. messaging, location, billing), but are still dependent on underlying platform technologies. (Orange, for example, exposes nearly 30 different APIs via their developer program!)

The GSMA’s OneAPI inititive is an attempt to revert this situation, and it is something we’re proudly supporting. Standing for Open Network Enablers, the OneAPI aims to bring network features to a much broader audience of Web and Web 2.0 developers. Practically speaking, it is a single API – REST and SOAP access methods are supported – through which developers can access services consistently across multiple operators. The project goal is to make it easy, safe, and beneficial for developers to utilise mobile capabilities in a far broader set of applications.

One of the OneAPI objectives is simplicity; it’s not trying to be a massive or overly-complex single platform that must be adopted by all. Instead it is a set of simple functions that will be accessible and friendly to any of the typical web development languages like Perl, PHP, Python and Java. A kind of mobile API for the masses, if you like.

Locatrix has recently deployed our reference implementation of the OneAPI at http://oneapi.locatrix.com and, being the intrepid former software engineer that I am, I set out today to create a mashup between the OneAPI, our favourite network operator, Chime – our social SMS solution, Google Latitude and the Locatrix XLF application service in a little PHP script. Proving that we do “eat our own dog food” (or “drink our own champagne” – with thanks to Kevin Smith), the code was built, tested and deployed in a couple of hours. By a distinctly former software developer!

The OneAPI initiative has the potential to change the way application developers think about mobile networks, and also to create genuine revenue opportunities for monetizing applications. If you’re interested in learning more about the OneAPI there’s some more material here, and I would welcome you to contact us if you’re a web developer interested in trying it out. Those in the Twitterverse can also follow the OneAPI account here, and you could also subscribe to our newsletter Position Update, which provides a wealth of location, mobile and social networking industry information each month.

Thanks for reading, and we now welcome you back to regular Twittering!