Today we have another case study of an app that runs using Kumulos. Some of you reading may already know it as it’s become quite popular here in the UK among the student crowds. The app’s name is Student Recommendation app, and it’s full of awesome recommendations and discounts for students in whatever city they live in.
The man behind the app is one of Waracle’s own Ryan Cowan. Ryan was brought on board for the SR project after he had finished porting a mobile game to a cross platform engine for iOS and Android for Waracle. At the time they were in need of an Android coder, so in Ryan’s words, “I took the job.” and so he became the creator of the Student Recommendation app.
The G1 group who commissioned the app are one of the largest independent leisure operators in Scotland and were looking for a way to expand their market and also get themselves established in the mobile world. That was when they turned to Waracle, and in so doing, essentially turned to Ryan to create the app.
As the Student Recommendation App is mostly online and requires various databases to be accessible, it was in no doubt that Kumulos and our Mobile Backend as a Service could make development a lot easier.
Ryan elaborated to us just what “making it easier” actually means: “Kumulos makes managing remote data easier by removing all of the problems in setting up a server. It allows you to easily add/edit tables and create methods to return data to the app.” he tells us, but that the real power of Kumulos, “comes from kscript which enables you to program on the server. This means you can return data via a kumulos method in any form you need for the app.”
Going further, he gives us a great example of how Kumulos (Backend as a Service) helped him solve exactly the kind of problem that app developers are likely to come across regularly. When the Student Recommendation app was first released it had only about half the number of features that G1 wanted in it, but they were looking to step the launch of the app and add features as they went. This is a smart way of releasing an app of this nature because once you have established interest you can start adding more complex or silver plating features.
The problem was though, in Ryan’s words, “[the] v2 features meant that the data structure on the server had changed enough that they would be incompatible with v1. The problem was that the client wanted both versions of the app to work using one database.”
If the app had been developed on a custom Mobile Backend, this would be a nightmareish scenario involving a lot of work if it had not been planned upon in advance. But as Ryan was working with Kumulos, it was easy. “To make both versions of the app work using the v2 database, v1’s API methods had to be edited to use the v2 database to return data in the same format that the old app was expecting. This also introduced some of the new features to the old app as new logic could be added to the server to return the data.”
By utilising the flexiblity and power of Kumulos’ Mobile Backend as a Service, Ryan was easily able to change how the app was interacting with the database on the server and get both versions of the app working off of one set of data.
These are exactly the type of problem our Mobile Backend as a Service is designed to help app developers fix easily and quickly, and this is just an example of the type of thing you can do with the power of Kumulos’s Mobile Backend. So if you’re an app developer and you’ve got a problem with your app’s Mobile Backend, why not talk to us and see if our mBaaS can work for you and take your app to the next level?
After all, time is money, and we can save you both.