Kobiton

What differentiates Kobiton from other similar products?

I haven't kept up with the device-farm market recently, so perhaps Kobiton is no longer alone in this, but when we first signed up, the big separators were the long list of shared devices and focus on native apps. Other device farms are great, if you have the available funds to purchase dedicated devices. What we really needed was a cost-effective means of accessing a wide array of device configurations when specific issues arise. Kobiton does that, along with making it easy to get new app updates onto those devices.

What is your favorite aspect of this product?

My favorite aspects are what I covered in the previous answer: our development and customer-service teams have quick access to any type of device they need, when they need it, and having Kobiton in our development pipeline means testers can verify device-specific fixes on the fly. Additionally, though, I also really value how easy it is to get people into our workspace and teach them how to use the tool. I've given Kobiton access to dozens of coworkers, and they all can use it almost immediately.

What do you dislike most about this product?

Historically the thing I've disliked the most about Kobiton is the inconsistent connectivity of its devices. I have experienced all too many instances in which shared devices either have poor connections that make interaction very slow or are just unable to connect at all. That's frustrating when I need a very specific device.

What recommendations would you give to someone considering this product?

If you're intending to run automated tests on Kobiton devices, seriously consider investing in dedicated devices. When we attempted to run Katalon tests on Kobiton's shared devices, the connections were so inconsistent that we always had more failures than passes. In the end it wasn't worth our time.