BrowserStack is used for mobile testing.
I work in web technology for logistics with BrowserStack.
The environment I work in with BrowserStack is enterprise level.
Some of the best features with BrowserStack include the ability to inspect network traffic, and the device farm is nice. They offer using two devices at once, but it's a tier that we don't pay for.
Cross-browser compatibility testing is important for my organization and I think it's essential for all organizations since they don't necessarily control the platforms that their clients access their services from.
BrowserStack's wide array of real devices and browsers has helped us address the need for devices, but we don't use them for web testing. I have used BrowserStack for live interactive testing, and it has helped identify and resolve errors during development processes.
It gives me access to devices that I don't have to purchase, which is nice. Being able to manually use a real device, or alleged real device, becomes important because there's a huge difference between testing on a simulator, emulator, and testing on real devices due to how apps get packaged and how things get moved around during the packaging.
I don't really test the feature that simulates various network conditions too much, but it has definitely come in handy. I generally would use something more a proxy, such as Charles, if I'm doing something that. I have the ability to manually do that on the devices that I have locally, so I wouldn't really do latency tests with connectivity speeds across the wide array of devices that they have.
They have an API, which is super helpful, and it is integrated into our pipeline, which helps because that's where our automated tests run. The device farm is one of the positive impacts we have seen from using BrowserStack. We get to run our automation against their full suite of devices, which alleviates the uplift of manual testing. This speeds up regressions, which speeds up our deployment process, allowing us to get updates to customers faster.