BrowserStack
BrowserStackExternal reviews
3,284 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Great cross-browser testing tool - real devices, clean Python integration, but pricey
What do you like best about the product?
The real device cloud is the biggest win. As a Python developer working with FastAPI, Django, and ReactJS, I can test on actual iPhone and Android device without owning them. Selenium integration with Phthon is plug-and-play, just swap the WebDriver config and you are done. BrowserStack tunnel works reliably for localhost testing, and Jenkins CI integration is straightforward. Saves hours compared to maintaining VMs or chasing teammates to test on their phones.
What do you dislike about the product?
Pricing is steep for individual devs or small teams. Parallel session limits on lower plans slow down CI pipelines when running a full degression suits. Older devices in their pool can lag, making it hard to tell if it's a real bug or a platform issue. Free trial is too short to evaluate properly.
What problems is the product solving and how is that benefiting you?
Catches browser-specific bugs in React frontends - especially Safari and iOS rendering issues - before they hit production. Also useful for debugging CORS and fetch quirks that only show up on specific browsers. Automated pipeline runs save the team from manual testing overhead.
Exceptional Device and Browser Coverage That Streamlines UI Testing
What do you like best about the product?
The platform offers an exceptional range of the latest devices and browsers, which lets us run thorough UI testing without friction. It has significantly streamlined our validation process and gives me real confidence as a QA professional when I’m approving tickets. On top of that, the initial setup is very straightforward—nothing more than our standard credentials is needed to get started right away.
What do you dislike about the product?
The system can feel fairly slow at times, and it occasionally gets stuck when trying to open external links during a session. From a usability perspective, when viewing a web page across multiple layouts, there isn’t a straightforward way to close just one specific device so you can swap it out for a new one. Touch interactions could also use some tuning, since dragging left or right to navigate doesn’t always respond as smoothly or consistently as I’d expect.
What problems is the product solving and how is that benefiting you?
It fully addresses the challenge of cross-browser and cross-device fragmentation during UI validation. With instant, cloud-based access to a broad lineup of modern hardware and browser versions, it helps ensure our application stays free of visual and formatting issues, so I can pass deployment tickets with complete confidence.
Smooth experience for building and testing real-world projects
What do you like best about the product?
The access to real device and browsers is a huge help, especially when testing responsive layouts and cross-browser compatibility. As someone working across the full stack, being able to quickly check how the frontend behaves on different devices without setting up emulators saves a lot of time. The interface is clean, and debugging tools like console logs and screenshots make it easy to spot issues.
What do you dislike about the product?
Honestly, not much to complain about. Occasionally there is a bit of lag during live sessions, and some popular devices can take time to load during peak hours, but nothing that has blocked my work. More flexible pricing for individual developers or smaller teams would be a nice addition.
What problems is the product solving and how is that benefiting you?
Overall, the experience has been smooth and reliable. It has made cross-browser and device testing much easier and faster, which directly helps in shipping cleaner builds. For our team, it has reduced the back-and-forth between development and QA, improved bug reporting, and helped catch issues early - which ultimately saves time during releases.
Speeds up regression and improves test coverage
What do you like best about the product?
The biggest plus for me is the access to a wide range of real devices and browsers without having to maintain them in-house. Running Selenium scripts in parallel saves a lot of time during regression, and live testing helps catch issues that emulators usually miss. The debugging tools - logs, screenshots, and video recordings - make it much easier to share findings with developers. Integrations with Jira and CI tools also smoothly into our agile workflow.
What do you dislike about the product?
Occasional lag during live testing sessions can be frustrating, especially when trying to reproduce time-sensitive bugs. Some high-demand devices also get queued during peak hours, which slows things down. Pricing tends to add up quickly once you need more parallel sessions or advanced features.
What problems is the product solving and how is that benefiting you?
BrowserStack has become a key part of our testing process. It has reduced our dependency on a physical device lab, sped up regression cycles through parallel execution, and improved overall test coverage across browsers and devices. Big reporting is faster and more accurate thanks to the built-in debugging tools, which has improved collaboration between QA and development teams. Overall, it has helped us release with more confidence and shorter turnaround times.
Solid cross-browser testing tool that saves us from maintaining our own device lab
What do you like best about the product?
The thing I appreciate most is that I don't have to worry about setting up physical device or virtual machine anymore. I can test our web app on actual iPhone, Samsung phones, and older browser versions within minutes. The Selenium integration is straightforward - I just point my existing scripts to their hub URL and they run on whatever browser/OS combo I need. Live testing is also useful when a developer says "it works on my machine" and I need to quickly check a specific Safari version or an older Android device. The debugging tools like video recordings, screenshots, and network logs help a lot when I need to share big evidence with the developer team.
What do you dislike about the product?
Sometimes the sessions feel slower compared to running tests locally, especially during peak hours. Mobile device sessions can lag a bit, which is frustrating when you are trying to reproduce a quick big. The pricing also gets steep when your team grows or when you need more parallel sessions for your CI pipeline. The UI for App Live can also feel a bit cluttered when you are switching between multiple devices.
What problems is the product solving and how is that benefiting you?
We don't need to maintain an in-house device lab anymore, which saves cost and time. Our team can run automated regression suites in parallel across multiple browsers, which has cut down our release testing time significantly. It also helps us catch browser-specific issues before production - things we'd otherwise miss because we mostly develop on Chrome. For client demos and bug verification on specific OS versions, it's been reliable. Overall, it fits well into our Agile cycles where we need quick feedback across environments.
Solid Platform, became part of our daily workflow
What do you like best about the product?
What I appreciate most is how it has quietly become a default tool in our deployment checklist. Before pushing any release to staging, we do a quick BrowserStack pass - Chrome, Edge, Safari latest, one Android device, one iOS device - and it just works without any installation or configuration hassle.
The integration story is strong. We have connected it with our Azure DevOps pipeline for automated runs, and the reports come back with clear pass/fail per browsers. For .NET project with React frontends, this combo of automate plus pipeline integration has stabilised our release process a lot.
App live ks particularly useful when we ship hybrid apps. Being able to test on a real Pixel or Galaxy device without owning one is a big cost-saver for the team.
The integration story is strong. We have connected it with our Azure DevOps pipeline for automated runs, and the reports come back with clear pass/fail per browsers. For .NET project with React frontends, this combo of automate plus pipeline integration has stabilised our release process a lot.
App live ks particularly useful when we ship hybrid apps. Being able to test on a real Pixel or Galaxy device without owning one is a big cost-saver for the team.
What do you dislike about the product?
Some honest issues - occasionally the device I want is busy and I have to wait or pick a similar model. For Indian-specific testing scenarios like UPI flows in apps or testing on commonly-used budget devices (Redmi, Realme variants), the device library could be expanded.
What problems is the product solving and how is that benefiting you?
Mainly two things - reducing the “works on my machine” problem and eliminating physical device dependency. Our team is distributed, so nobody has to courier a phone to another developer for testing anymore. We catch browser-specific JavaScript issues and CSS rendering problems early, which means fewer hotfixes after go-live. Overall, the confidence to deploy on a Friday evening has improved, and that itself says a lot.
Easy Multi-Device Testing Without Physical Devices
What do you like best about the product?
It's easy to test applications on multiple real devices and browsers in their dynamic interface, without needing to maintain a local infrastructure.
What do you dislike about the product?
Is its price, which can be high for small teams or heavy use. Additionally, performance can sometimes be slow or unstable during remote sessions, especially when testing on certain devices or under certain network conditions.
What problems is the product solving and how is that benefiting you?
Helps us simplify mobile application testing by allowing APK integrations and testing across multiple real devices without maintaining a physical device lab.
Effortless Cross-Browser Testing, Needs Pricing Tweaks
What do you like best about the product?
I use BrowserStack to validate UI and functionality across real devices and browsers, which helps catch compatibility issues early and deliver a consistent user experience. I like that it removes the need for maintaining physical device labs or complex local environments while providing instant access to real browsers and devices. What I like the most is being able to instantly test on real devices without any setup. Also, stable session performance and detailed debugging logs, such as screenshots, videos, and console logs, make issue resolution much faster and easier. These features save a lot of time during debugging because I can quickly reproduce issues, identify root causes, and avoid guessing or local setup issues, making the whole testing process faster, more accurate, and reliable. The initial setup was very easy, with clear documentation and quick integration into our existing Selenium and CI/CD workflow, allowing us to start testing within a short time.
What do you dislike about the product?
Occasionally session latency can be improved, especially during peak usage, and more flexible pricing options for smaller teams would make it even better. Session latency could be improved by making remote device interactions more responsive during peak hours, especially for real-time debugging. On pricing, more flexible pay-as-you-go or smaller team-friendly plans would help startups and individual testers manage cost better.
What problems is the product solving and how is that benefiting you?
I use BrowserStack to validate UI across real devices and browsers, catching compatibility issues. It removes the need for physical labs, speeding up testing cycles and improving release confidence.
Real Device Cloud Delivers Reliable, Production-Ready Testing
What do you like best about the product?
The real device cloud is definitely the standout feature for me. Being able to test on actual hardware, rather than relying on emulators, gives us results that feel far more reliable and accurate for our production builds.
What do you dislike about the product?
Cost is a significant factor for me, since it’s priced higher than some other solutions, which can be difficult for smaller teams to justify. I also occasionally notice some lag that seems tied to the remote network connection, and the session time limits can feel restrictive when we’re in the middle of a complex debugging task.
What problems is the product solving and how is that benefiting you?
It removes the huge burden of maintaining an in-house device lab, while still ensuring our apps run smoothly and reliably across every imaginable platform.
Real device testing without the device lab headache
What do you like best about the product?
Real device cloud is the big win. Testing on actual Android device across OS versions, screen sizes, and OEM skins (Samsung, Pixel, Xiaomi) without maintaining a physical device lab saves hours every release. App Live is great for quick manual checks on cross-platform builds - uploading an APK or IPA and testing on a real device in under a minute just works. Network throttling and geolocation simulation are useful for catching edge cases that emulators miss.
What do you dislike about the product?
Device sessions can lag occasionally, especially on older Android device during peak hours. Pricing scales quickly once you add parallel test runs or App Automate for CI pipelines. Sometimes app installs fail on the first try and need a retry. Would also like longer session timeouts on the lower-tier plans.
What problems is the product solving and how is that benefiting you?
It removed the need to buy and maintain a physical device farm for testing cross-platform apps on real hardware. Catching OEM-specific bugs (especially on Samsung and Xiaomi builds) before release has reduced post-launch crash reports significantly. Integration with CI tools means automated tests run on real devices on every PR, which has cut down regression issues.
showing 1 - 10