What was the scope of their involvement?
We used Aurity to complement our core team as part of three projects spanning 18 months. Initially, we had one developer onsite to help us, architect, build, and employ features on the mobile app. That developer also helped build some of the backend API in the first iteration of the product.
We first built the product for iOS only. We decided that expanding onto the Android platform was the quickest way to increase our user base. We reengaged with Aurity for a developer to spend a few weeks taking our existing code and converting it to the Android platform.
In early 2018, we did a complete rework of the frontend application. We needed to accelerate the work faster, so we brought on a couple of remote developers to help our core product team. We worked in one-week sprints for a period of about six months. One developer was chiefly responsible for the Android implementation, the other for UI and the interaction with the mobile app.
What is the team composition?
I work with Peter (founder, Aurity) and a scrum master.
How did you come to work with Aurity?
I met Peter at a meet-up in early 2017. He told me about Aurity and their work, and it seemed like a good fit.
What is the status of this engagement?
We initially worked together from January–June 2017. We used them again in September 2017 for a few weeks. Most recently we worked with them from January–June 2018.
Development velocity increased markedly since the engagement began. Aurity’s expert team inspired confidence by communicating clearly from the start. The ability to turn constructive feedback into implementable, on-time deliverables were hallmarks of their work.