BrowserStack Reviews & Product Details

1. The ability to jump into any device or browser in seconds is honestly the biggest advantage. I don’t wait for emulators to boot or hunt for physical devices.

2. Touch response and scroll behaviour feel close enough to a real phone to reliably catch UI alignment, gesture issues, and responsive bugs.

3. Built-in tools like network throttling, geolocation, and device rotation make it easier to recreate real-world scenarios without using third-party utilities.

4. Screenshots and video recordings save time when creating bug reports, I can attach evidence instantly.

5. The consistency matters most. Whether it’s Chrome on a Pixel or Safari on an iPhone, I know exactly what environment I’m testing in. Review collected by and hosted on G2.com.

1. The visual frame rate occasionally drops for animation-heavy flows, making certain UI issues slightly harder to observe.

2. Switching between device orientations isn’t always instant, there’s a small lag. Review collected by and hosted on G2.com.

What I like best about BrowserStack is the ability to reliably test automation across a wide range of real browsers and real mobile devices without the overhead of maintaining local infrastructure. It allows me to quickly validate web and mobile applications in parallel across environments, which significantly speeds up feedback loops. The seamless integration with automation frameworks, stable cloud infrastructure, and accurate reproduction of real-world user conditions make it especially valuable for building and maintaining scalable test automation suites. Review collected by and hosted on G2.com.

What I dislike about BrowserStack is that test execution can occasionally be slower or inconsistent, especially during peak usage times, which can impact automation stability. Debugging failed tests can also be challenging at times due to limited visibility into device-level logs or transient environment issues. Additionally, managing sessions and optimizing parallel usage sometimes requires extra tuning to keep costs and execution time under control. Review collected by and hosted on G2.com.

I love using BrowserStack for its awesome feature of eliminating clutter by handling multiple devices for testing. The platform's ability to support Accessibility Testing is great, and I find the Low code automation to be a brilliant feature. The multidevice testing with sync is just mind-blowing as it lets me perform tests across multiple devices with the effort of testing just one. The guide line for setup is awesome, and it makes the initial setup super easy. I especially appreciate the BrowserStack support team—they're just one email away with mostly instant resolution SLAs. The Percy tool is also a favorite feature of mine. Review collected by and hosted on G2.com.

I find the sessions have a low idle timeout, and if that can be increased, it would be great. Also, nowadays all smartwatches support apps, so adding that section for live testing would be a great add-on feature. Review collected by and hosted on G2.com.

Parallel execution actually works reliably. When we run our full suite across multiple OS-browser combinations, the time savings are huge. The integration with popular frameworks (Selenium, Appium, Playwright, Cypress) is straightforward, you don’t waste time wrestling with configs. The session dashboard is clean: logs, video, network timelines, console output - all in one place. Debugging flakiness becomes much easier. Being able to run tests on real mobile + desktop devices without maintaining hardware is a massive operational relief. Build insights (pass/fail trends, flaky test detection, failure clustering) help identify problem tests faster. Review collected by and hosted on G2.com.

Occasional device allocation delays during peak hours can slow down CI pipelines. Video playback during debugging sometimes feels slightly laggy for animation-heavy flows. Network logs are useful but could be more detailed for deep investigation. If the suite has many retries, the dashboard can get cluttered without proper naming conventions. Review collected by and hosted on G2.com.

As a QA engineer, being able to test on real hardware instead of just some fake simulator is the best thing, because those simulators always lie, right? It just means when I find a bug, I know its a real bug the customer will actually hit. And the ability to fire up a test on some obscure old browser in like, two seconds? So smooth. It just makes the whole testing process way less painful. Review collected by and hosted on G2.com.

The main thing is that it can get real slow and laggy sometimes. You're trying to quickly check an animation on an old Android, but the mouse movements and screen updates are delayed, and it throws off the whole test. Review collected by and hosted on G2.com.

I like that BrowserStack provides instant access to a wide range of real devices and browsers, eliminating the need to maintain an internal device lab. The platform is extremely reliable, integrates well with existing CI/CD tools, and offers fast, accurate results. Its combination of live testing, automated testing, and debugging tools helps streamline the entire QA workflow. Review collected by and hosted on G2.com.

My main dislike is the latency when interacting with real devices, which can slow down debugging. Some features feel scattered, and advanced automation capabilities often require higher-tier plans. Device availability during high-traffic times can also be a challenge. Review collected by and hosted on G2.com.

I like BrowserStack because it’s reliable and close to real-world usage.

You get real browsers and devices without setup pain, issues show up like they do in production, and debugging is easier with built-in logs, screenshots, and videos. It saves time and removes guesswork. Review collected by and hosted on G2.com.

What I dislike is the occasional flakiness and slowness, especially during peak hours.

Sometimes sessions lag, browsers disconnect, or tests fail for infra reasons rather than real bugs—which can be frustrating when you’re chasing false negatives. It’s great overall, but not always as fast or stable as you’d want for heavy parallel automation. Review collected by and hosted on G2.com.

At our company, we use it as Agent AI, for test management, and for App Live to support mobile automation. We rely on it often, and it is straightforward to implement. Review collected by and hosted on G2.com.

During our testing of the Generate AI feature, we noticed that it lacks an option to continue the chat and further refine the conversation. Review collected by and hosted on G2.com.

It supports multiple devices and now includes a parallel feature, allowing me to test scenarios on different devices with various operating systems simultaneously. There is also support for local BrowserStack. I also appreciate the App Live and Live Platform features, which make the Appium setup more efficient, enabling easier automation of mobile applications. Review collected by and hosted on G2.com.

Sometimes the device is not available, and the latest updated version is not up to date. For example, while most physical devices now have Android 16, BrowserStack still only shows the older version, Android 15. Review collected by and hosted on G2.com.

App Automate scales my PRs, not my stress. We shard our Appium suite across ~30 devices in parallel. A smoke pack that used to take ~55 minutes now lands in ~14–16 with a clear build status and per-session artifacts. Tunnels for real backends. The secure local tunnel lets test builds hit feature-branch APIs behind VPN, great for pre-merge validation without staging deploys. Geolocation/timezone + network profiles (3G/4G/offline) are handy for edge cases.

Solid session evidence. Every run gets one canonical URL with video, device info, console/network logs, and app/device logs—perfect for tickets and vendor escalations. Framework-friendly. App Automate plays nicely with Appium + GitHub Actions, tagging builds by branch/PR keeps history tidy and makes flaky test hunts less painful.

Console logs from embedded WebViews show JS errors alongside native logs; I don’t have to hop through multiple tools to prove where the bug lives. Review collected by and hosted on G2.com.

Peak-time queues on popular iPhones. Real devices can line up, cold starts aren’t simulator-fast. iOS signing quirks. Resigning IPAs for real devices occasionally trips on entitlements, fixable, but it eats time during setup. Tunnel fragility on long runs. Corporate proxies sometimes need custom flags, and very long sessions can drop if the network hiccups. Review collected by and hosted on G2.com.