Services Provided
Tablet App Development, Tablet App Design
Client Problem
I've built an app to manage our Cable Car 10+ years ago. Now, the app is outdated, and can't do some functions we need.
I need to update this app with the latest technologies, and I need to make it future-proof for at least a few years in advance.
1
Our Solution
First of all, we should determine if it is easier to update existing app or build a new one from scratch.
Main issue lies in communication between the app and the back-end. Old technologies power the back-end, and we can't update them - we can only touch the tablet app. So we must make sure that new product is compatible with those technologies and that everything works as expected even with an updated app.
The other thing is testing - the only environment where the app works is the cable cart itself due to security reasons. So to properly test the app, we have to be in touch with client so that he can use the device on one of the cable car rides. Therefore we must make sure that there is as few testing iterations as possible.
Then there goes offline functionality - cable car goes up high, and there is no internet at parts of the trip. Software must be synced between the two cars (there are two cars at Stanserhorn). So we must make sure that two cars are synced despite the fact that they can be offline anytime.
2
How we made it work
1. Architecture
After a quick project assessment, we decided to re-build the app from scratch. It was just easier to start fresh.
We studied client's back-end and algorithm of their existing app, and mapped out the scope of work.
Then we signed a fixed-price contract with our guarantee package and began to work!
2. Design & Development
The design for this app was quite simple. We had to make sure the app was suitable for the users of older age, since it is common that the workers at Stanserhorn-Bahn are retired volunteers. We quickly finished the designs, and after a few small changes, continued to the development.
Resource allocation was straightforward, as for any other project we build from scratch. We integrated all algorithms as planned, tested as much as we could internally, and sent the app to the actual cable cars for further testing.
3. Testing "in the field"
This phase went a bit slower than expected - you can't predict certain things without actually testing them. But nothing critical, and our client remained happy about the app.
We were able to deliver the app ahead of scheduled deadline, and received another cool item to our portfolio. I admit - we don't deal with such projects on daily basis - and that's where the fun part is!
3
Explore Other Apps
Let's Connect