RepreZen API Studio started with the goal of enabling deep interoperability, by unifying data representations across APIs. The core of the product was the API modeling language that became RAPID-ML. API Studio provides the tooling: the RAPID-ML editor, live documentation and diagram views, sandbox testing and code gen framework.
But I always liked Swagger. I admired the pragmatic focus and the platform mentality - building a foundation that would need to serve a broad range of extensions and integration points. Towards the end of the Swagger 2.0 specification effort in August 2014, Tony Tam asked working group members to give their comments for a release announcement. Here's what I wrote:
"API description languages are becoming an essential part of the API development and integration lifecycle. Swagger leads the way with the most vibrant community of users and contributors, and the most comprehensive set of supporting technologies.
The Swagger 2.0 working group has brought some of the best minds in the API community into a remarkably open and efficient design process. Looking forward, we can expect continued innovation from the Swagger community."
Sure enough, great things have happened. The Swagger standard, now formalized within the Linux Foundation as OpenAPI, is the industry standard that connects a growing ecosystem of API editors, documentation formats, testing tools, API management platforms, and more.
The RepreZen development team has been hard at work, building OpenAPI into API Studio, and it has turned out to be a fun, energizing journey. Adding a new first-class description language, alongside RAPID-ML, required some decoupling among different parts of the product. This was a welcome change, and we took the opportunity to make significant improvements in stability, usability, look and feel. The new API Studio just "breathes better."
It also required a deep dive into the OpenAPI Specification and Swagger tooling. Again, we found some opportunities for improvement, which we're contributing back to those projects. It has been a pleasure getting to know OpenAPI at this level of detail, learning more about how it evolved, and forming our own ideas of how to extend and improve the standard.
The integration is complete, and response from our user community has been overwhelmingly positive. You can see our video and feature tour here.
We're seeing exciting opportunities for integration with the Swagger–OpenAPI ecosystem, and an equally exciting evolutionary path for the product architecture to grow into these new capabilities. I couldn't be prouder of our product team, and couldn't be happier with the direction that RepreZen API Studio is taking, as a multi-language workbench for API design, documentation, and downstream integration.
As for the future of OpenAPI, I could express my excitement there as well, but then I'd just be piling on. ;-)