January 4th, 2019 • RAD
So, you’ve decided to build your own custom applications rather than rely on readymade software out in the market. Because most of the applications you need are simple, they also need to be built super-quick and be very flexible to changes.
And it just so happens that you don’t have any developers sitting around twiddling their thumbs with nothing to do.
Rapid Application Development (RAD) is the perfect methodology to use when building your apps, but what does it actually look like in practice? Are there some good RAD examples out there to see?
To start, let’s quickly revisit the core concepts of RAD.
Clearly define the requirements. Anyone working on a RAD project should have an extremely clear vision on what the application should do and what problem it is trying to solve.
Rapid prototyping. A real, working application should be constructed within a very short amount of time and changes need to be implemented instantly.
Lots of feedback. Stakeholders should give their ideas for improvement continuously and be able to contribute to quick iterations.
The most important thing you can do is select the right platform to build your apps. If you have extremely talented developers, they may be able to build these apps from scratch. But to speed up the development process, you’ll most likely want to look at low-code options.
If many of your applications are a similar type, you may even find a great no-code platform. For example, if you primarily need process applications that automate data collection and workflows, you can use a platform like Kissflow to build what you need.
RAD principles translate easily to Kissflow because you can build a working prototype in minutes, and the layout is easy enough that your stakeholders can actually participate and drive the development process. With simple drag-and-drop modules, they can build their own forms and workflows without any help from a programmer.
RAD projects examples are easy to show in the context of Kissflow. Here are three process applications you can build quickly using RAD principles.
Collecting data for purchase orders and approving them sounds like a very simple process, but readymade options often complicate it. However, you also want to build them on a platform that gives you more than just basic functionality.
To start this RAD example, gather all the people who know the process best, starting with the procurement team. Bring together current forms and a complete understanding of the workflow. Discuss how you want the app to function. With purchase orders, it’s often helpful to also have a vendor database for quick reference to call up information in the form.
Decide what fields should be shown at what steps, and if you want to add some conditional steps that only happen when certain parameters are met.
Then the procurement team can sit alongside someone familiar with Kissflow to build the first prototype. You should be able to have a working form and workflow built within 1-2 hours depending on the complexity of your form and how many databases you want to link it to.
After getting the basic app up and running, it should be shared with those who are going to be using it. Those who are requesting purchase orders may have some additional ideas for how to improve the form or workflow. These changes can be implemented immediately and shown to stakeholders on the spot.
Another RAD example is handling employee resignation. HR teams have a lot to coordinate when an employee decides to leave the company. This app might seem trickier to build just because there are so many moving parts involved. But you can use the same approach.
HR will be leading the charge on this development. However, they need input from management, payroll, IT, and many others.
Creating the perfect workflow is the key challenge here. As you develop the application, you’ll continually think of other people who need to be informed and take action. RAD can play a key role in quickly adding steps to your workflow and testing to make sure that confidential data is hidden from those who don’t need to see it.
At some point in the development process, the HR team may also want to handle resignations and terminations in the same application. In traditional development, this means going back to the beginning and building the app from scratch. But if you are using Kissflow and RAD principles, you can quickly go through and create a different workflow for terminations, or make some tasks conditional.
The last RAD example we’ll look at is Travel Request. This one may be used more broadly by the entire company anytime someone is traveling for official business. Depending on your company, the sales team or the customer accounts team might use it the most. However, it’s usually the finance team that is responsible for the application.
The key with travel requests is keeping tight control over adherence to policies. There’s usually a lot of chaos surrounding travel. Even if the finance team has set a detailed policy, some departments might find ways around it. That’s where building an application in Kissflow with RAD principles can help keep things in order.
The finance team can create a form that displays the written travel policy, and validates key data to make sure everything is correct before getting a manager’s approval. It’s important for the finance team to be able to do a budget and/or cash flow check as well before the travel is arranged.
By using RAD principles, the finance team can quickly create a prototype of the application and get feedback from various departments before going live. With a no-code platform like Kissflow, they can also take responsibility to maintain the app and make changes along the way.
If you are looking to try some of these RAD examples that involve automating core processes in your company, Kissflow is the perfect tool. You can collaborate with other team members and design your own form and workflow, and have a working prototype in less than an hour.
If RAD appeals to your business and you want to try it out, start with a free trial of Kissflow and see how easy it is to get off the ground!
* - Based on usage requirements