This is part of a series on the evolution of theCisco Collaboration Cloudplatform, exploring the technical and design principles behind its unique architecture.

So far in this series my colleagues have talked about various elements of our Cisco Collaboration Cloud platform. Rowan mentioned its origins and the problems we're trying to solve. Jonathan discussed our approach to architecture for a platform that delivers innovative experiences for companies of all shapes, sizes, and deployments. And Jens hit home on user experience (no surprise from the guy who owns all of our user-facing apps).

My platform is about the platform itself. I believe that simple and open APIs unleash the power of a platform in ways that accelerate workflows and business processes, that result in driving user engagement.

I'm the new GM responsible for the Cisco cloud collaboration API strategy. My team cares most about three things when it comes to evolving our platforms for developers:

A Great Developer Experience:First and foremost, our goal is to make our APIs easy-to-learn and use. Developers want APIs to be comprehensive, yet simple so they can focus on their own applications rather than the complexity of a platform. We've gone to extreme lengths to make our APIs elegant, abstracting away the complexities of the underlying platform.

But even the smartest coders need help so our Tropo APIs are surrounded by handy quickstart guides, sample codes, and examples written by our support team, who are developers themselves. Our APIs are hosted on a free, open portal and enhanced by Cisco DevNet training and sandbox resources. Most important, we're always available to chat. You can easily engage with us through a variety of channels including industry events and social media.

Amazing Support:Developer experience is not just about great APIs, but the entire experience. This means providing responsive support from people who know our APIs. Since our early days as Tropo, we've delivered 24