Rippler makes the custom software development process easier, better and more affordable. The creation process is still an art form which has a lot of complexity to it. At Whyable, we’ve been building custom software for over seven years, and this is what our go to process is using Rippler.
Step 1 – Pick Your Process
I won’t dwell long on this, and while it’s important, we don’t think it is fundamental to a successful project. We use Agile, which provides flexibility in the project process, runs using sprints and provides a well accepted best practice in software delivery that has now migrating into other industries, due its success. One thing to say about Agile, is that it’s not 100% defined, that’s it’s beauty, there’s flexibility in the process too.
Step 2 – Understanding Your Requirements
The first thing to do is to understand what you are trying to build. We like to use user stories but there’s a number of ways you can do it. The challenge here is keeping the requirements down, less is more is a useful adage to consider, in particular if this is an innovative product which should follow the minimum viable product approach with the “lean startup method“.
Step 3 – Design
Once you’ve wrapped up your requirements then typically you’ll move onto the design stage. This is going to involve design skills, so you can get the UX and UI right. This process can involve talking through the requirements with the designer, considering the brand aesthetic in the application and then usually starts with UX before moving into UI.
When we build apps, we like to put the finished UI on to a prototyping application like Invision, so you can play around and test the designs before the coding starts.
We do have a few design templates for Rippler as well. Check out our Entrepreneur’s MVP Template here to see if it works for you (you’ll need to log in to have a play around). We also have a template using Angular Material.
Our templates are not the concluded, like Rippler itself, as they’ll still need some design input for your specific application, but they are coded, so they are going to create significant further development and design savings for you and your team.
Step 4 – Development
With the design work complete, there’s the coding to do. Every application requires front and backend development, and then integration between the two.
With Rippler, the vast majority of your backend development is already completed, perhaps as much as 80%, depending on the size and complexity of your application. The documentation can be found here, once we give you the code, you can also get access to the ReadMe file and we can give you direction regarding the best way to use it.
One tip on the front end side, which is usually the focus for non technical people, look at the work that’s in front of you, it needs to work, don’t get bogged down in the detail of whether every pixel is perfect or that it’s not matching the designs created. You always need to keep the software process moving. One more, while we’re here – talking is the best form of communication!
Step 5 – Testing & Bug Fixing
The testing and bug fixing is often where projects falter. It’s easy to assume that these products are going to be delivered perfectly for you, but even with the best engineers you’ll have a litany of bugs and thus you must test with patience, and gumption in order to ultimately deliver a product of value.
Step 6 – Deployment
We recommend a staging and a live environment to allow for proper testing to be done before going live, particularly given an environment of constant improvement via rapid deployment. We can host Rippler for you on our servers or you can set up your own, like Agile, we want Rippler to be flexible and to work for you.