WaveMaker Adds API Designer to RAD Environment

WaveMaker today announced that it is including an API Designer within its namesake rapid application development environment. Aimed at both professional developers short of time and citizen developers lacking application development skills, WaveMaker provides access to both RAD tools and a Platform-as-a-service (PaaS) environment based on Docker containers that is delivered via the cloud.

WaveMaker CEO Samir Ghosh says that as organizations look to rapidly build applications, they not only have to design APIs for those applications, they also have to create APIs that they can then wrap around a variety of legacy Back-end services those applications need to invoke. The result is often a time-consuming process that winds up extending application backlogs throughout the enterprise.

Ghosh says the WaveMaker platform is built from the ground up to make it much simpler to combine Docker containers and APIs to build, deploy and ultimately provision applications faster than any other PaaS environment.

The WaveMaker RAD tool generates modular AngularJS code for the client and Java, Spring and Hibernate code for the server-side of any application. WaveMaker also makes available a number of prefabricated APIs to support Integration with, for example, any one of several social networks.

Ghosh says that as part of the company’s overall PaaS strategy, it became apparent that WaveMaker would need to push the convergence of RAD tools and API design. Developers, notes Ghosh, increasingly need APIs to be in place in order to build out the rest of the application.

In general, Ghosh says WaveMaker expects to see professional and citizen developers working more closely together. It’s not feasible for professional developers to build and update every application imaginable. WaveMaker RAD tools allow citizen developers to build applications in a way that allows a professional developer to extend them later on if they so choose, he says.

Interest in RAD tools in the last years has risen considerably as the application development backlog became larger thanks mainly to the rise in demand for mobile computing applications. The degree to which end users inside any organization will embrace those tools will vary. But the one thing that is for certain is the longer those end users have to wait on professional developers to build their applications, the more likely it is they try to build applications on their own using any set of tools they find handy.

As such, it may turn out to be in the interest of the professional developers that are ultimately going to be held accountable for the integrity of those applications to make sure the tools made available to citizen developers are as robust as possible.

Be sure to read the next API Design article: Amazon Adds PutRecords Function to Kinesis API