Could you share any evidence that would demonstrate the productivity, quality of work, or the impact of the engagement?
From a development standpoint, they were able to deliver apps that were submitted and approved for both iOS and Android. That was good, but I'd say it took a little bit longer than I would have liked.
On the iOS side, the code was very solid, and it was very easy for somebody to take over the code they had put together. On the Android side, it was also fairly clean. I would say the code, for the most part, is pretty solid, minus some of the issues we've had with connectivity on both the iOS and Android side. Whether it’s the firmware, the app, or the mobile phone, it’s difficult to tell.
Where they weren't as strong is that they're extremely structured in their sprint process, and it doesn't really lend itself to quick changes. As a startup, we're constantly readjusting and trying to be as nimble as possible. Even for something as simple as a text change, we felt like we were beholden to their one-week development cycle rather than being able to get something back from them in five minutes, which is how long it now takes us internally.
How did Droids on Roids perform from a project management standpoint?
They're very organized. I don't think we ever had any qualms with that, so I don't have issues there. Their organization is absolutely not one of their weaknesses. We didn't experience any issues with a language barrier. I think speed was one of our issues with them. We used Slack, Skype, and occasional video conferencing calls to communicate.
What did you find most impressive about Droids on Roids?
They're always trying to stay up-to-date with the different types of coding languages, and they're always incorporating that. You can get something organized out with them if you plan far enough in advance. Their pricing is definitely attractive.
It gets a little trickier for a more exotic style app development like the one we did with multiple different protocols running from a phone to a connected hardware device. You really need the app developers and the firmware teams to speak and sit down next to one another. If I had to do it all over again, I would try and hire somebody internally so that they could sit next to the person day in and day out. But given that they didn't have that, I thought that they did a pretty decent job.
Are there any areas Droids on Roids could improve?
I'd like to see them be a little less rigid in their one-week sprint process because they didn’t have the ability to change or add even very small things. I think that is something that we'd want to see that's different. To be completely honest, I wasn't always 100% involved in this process. I was in the beginning, but in the last 5 months of development, I started to pass this off to other engineers at our company.