When David came to madewithlove for help, he had already spent quite the road trying to get GearJot out there. In fact, he’d tried that with various development parties over a period of some six years. So he asked us to tie up the last loose ends. We immediately threw ourselves into understanding the product, a collaborative asset management system aimed at heavy gear users. It soon became clear that GearJot needed a touch more than just tying up some loose ends. After we were done with the app, GearJot was good enough to be released to the world in a first, stable and sellable version.
GearJot is written in the Yii framework, which our developers weren’t familiar with. Yet they were able to fix the blatant bugs pretty fast. Making the platform stable was a continuous battle, but we won it in the end. Two big parts had to be tackled. Firstly, some features needed slashing, while several smaller features with high value were implemented and the remaining features required a bit of polishing. The other big part was integrating the app with various telematics providers. GearJot can now pull in data from five major telematics providers, including John Deere, Komatsu and Verizon.
We started out with lots of quality assurance (QA), because the app really wasn’t stable and it broke on almost every other page. These had to be resolved first. Some features were simply too buggy and brought too little value to the table. To get something out there, we decided together with the client to slash these. After this initial breakdown, we came up with a product plan. It determined what exactly had to be finished to get the first version out there, including some smaller high-value features. We implemented this plan and made sure some basic tools were in place, such as Intercom and Bugsnag, to make sure we could follow up clients and bugs.
The result? A stable platform, already in use by the City of Clearwater in Miami to manage all its garbage trucks!