At the start, their development team set out to fulfill a common workflow. "To build a new feature, we planned to push code of a feature branch, and run tests on every commit," says Geoff Spears, Senior Software engineer at Kashoo." At some point, we'd share the feature with the rest of the engineering team, and send it our internal QA team for testing. Once the feature was ready, we'd commit to master and ship it to our customers."

In an attempt to meet their requirements, they built an in-house solution, using a combination of Jenkins, a Mac mini, and Testflight.

"After months of iterations and countless engineering hours, we'd made a series of small incremental improvements that ultimately culminated in wanting to destroy the Mac mini," says Amrik Randhawa, Project Manager at Kashoo. In short, their development pipeline was not easy to use, and even harder to maintain.

Realizing they were one build break away from an engineer smashing the Mac mini, Randhawa and the development team started looking for alternate solutions. Having built, and fought with, an in-house system, they had a clear list of requirements when shopping for a new CI / CD.

They needed a solution that would allow them to:

• Work remotely as a close-knit team
• Quickly bring new team members up to speed, and auto-provision devices
• Communicate changes and updates to non-technical clients on a regular basis
• Most of all, be a time saver, not a time sink for the development team

"Buddybuild does everything we need, and more," says Randhawa. "For us, it's a one-stop shop that fills the missing piece in our development pipeline." For Ben Kennedy, an iOS developer at Kashoo now free from managing the Mac mini, "the common development workflows that ought to straightforward, now actually are."