BrowserStack

What do you like best about the product?

Honestly speaking, as a UI/UX designer I always thought my job ends after handling off designs to developers. But then clients started saying things like "this button is not showing properly on my phone" or "this screen looks very different on my device." That is when BrowserStack became my best friend. Now before any design goes live I check it myself on real devices. No need to ask developer, no need to wait for client feedback. I open BrowserStack, select the device, and see exactly what user will see. That feeling of catching a problem before client sees it - very satisfying honestly.

What do you dislike about the product?

Platform is little bit confusing for designers. It is mostly made keeping developers in mind. First few times I was not sure where to click and what to do. Some device sessions also disconnect suddenly when you are in middle of checking something important.

What problems is the product solving and how is that benefiting you?

Earlier the design review process was very dependent on developer and client feedback. Something would break on specific Android phone or iOS device and nobody would know until client complained. Now that whole problem is handled before delivery. Spacing issues on smaller screens, font rendering on different devices, color differences across displays - everything gets checked on real hardware before client sees anything. Revision cycles reduced, client trust increased and design delivery became much more smooth and professional.

What do you like best about the product?

Android fragmentation is real and every Android developer knows that pain personally. Different manufactures, different OS versions, different screen sizes, different behavior - owning enough physical devices to test properly is simply not realistic. BrowserStack solved that problem directly. Access to real Android devices across manufactures and OS versions without maintaining a single piece of hardware changed how thoroughly I test before every release. Seeing my app behave on a real Samsung, Xiaomi, OnePlus and Pixel device simultaneously exposed issues that my personal device and emulator combination never once revealed. App Live feature works smoothly and feels genuinely close to having the physical device in hand.

What do you dislike about the product?

Certain older Android devices in the pool feel sluggish enough to make performance testing unreliable. You cannot tell if the slowness belongs to your app or to the device struggling inside a data center. Emulator like behavior occasionally creeps into sessions on specific devices which defeats the entire purpose of real device testing.

What problems is the product solving and how is that benefiting you?

Android device fragmentation was always the biggest source of post release crash reports and one star reviews. BrowserStack systematically reduced both. Manufacturer specific UI rendering issues, OS version compatibility problems, touch event inconsistencies across screen sizes - all surfaced during testing instead of after publishing. Release confidence improved because every build now gets validated across a realistic range of real Android devices before any user downloads it.

What do you like best about the product?

CORS handling different across browsers, fetch API behavior inconsistencies consuming REST endpoints, and async response rendering issues that only surface on specific mobile browsers - all invisible locally and all catchable on BrowserStack. Docker based local environments connect cleanly through the tunnel meaning the complete backend stack gets validated on real devices without staging deployment overhead. Stopped blaming backend code for what turned out to be browser specific frontend behavior every single time.

What do you dislike about the product?

Some device sessions load slowly enough to break debugging concentration during complex API response tracking workflows. When you are validating a FastAPI endpoint response rendering chain across multiple real browser environments session instability adds friction that compounds quickly. Free tier is too restricted to properly evaluate whether the platform fits backend heavy workflows before committing financially.

What problems is the product solving and how is that benefiting you?

CORS handling difference across browsers, REST API response rendering inconsistencies, and async Celery task results behaving unexpectedly on specific mobile browsers - all of these were invisible locally and all of them reached production regularly before BrowserStack. Docker based local environments now connect directly through the tunnel meaning the complete backend stack gets validated on real devices before deployment not after.

Backend developers stopped spending hours defending perfectly written API code against browser specific frontend behavior that had nothing to do with the server. Debugging conversations became shorter, release cycles became cleaner and post deployment fixes related to browser compatibility dropped significantly across the entire team.

What do you like best about the product?

I use it for live app testing and to check the CB websites.

What do you dislike about the product?

The video recording quality isn’t that great. I really need better resolution for video recording, because the current output doesn’t look clear enough.

What problems is the product solving and how is that benefiting you?

It helps the team test across multiple platforms and provide feedback as quickly as possible, so decision-making and bug fixing can happen faster.

What do you like best about the product?

The clean, approachable interface makes it very straightforward to manage our test suites without a complicated onboarding process. Its seamless integration with automated frameworks like Selenium lets us run extensive script pipelines with minimal friction. It also delivers an elite level of cloud scalability, enabling our remote and distributed engineering teams to collaborate effectively from anywhere.

What do you dislike about the product?

The premium subscription cost can be a significant financial constraint for smaller, localized project budgets. In addition, during remote real-device streaming sessions, the overall execution can occasionally feel sluggish compared to working on a local machine. This slight lag sometimes reduces the efficiency of fast-paced, interactive manual UI debugging.

What problems is the product solving and how is that benefiting you?

It removes the heavy administrative workload and financial overhead that come with maintaining an internal, physical device lab for cross-browser verification. With immediate cloud access to a broad matrix of real hardware, it makes environment setup and ongoing management much simpler. As a result, it saves valuable development time, significantly cuts infrastructure costs, and helps ensure a consistent user experience across a wide range of devices and browsers.

What do you like best about the product?

Managing digital product delivery means the final responsibility lands on your desk regardless of where the problem originated. BrowserStack gave me something I genuinely did not expect - visibility. Before sign off I can verify exactly how a delivered product behaves across real devices without depending entirely on developer assurances or waiting for end users to report problems. LMS interfaces rendering incorrectly on specific mobile browsers, e-learning modules behaving inconsistently across tablet screen sizes, HRMS dashboards breaking on Safari - all catchable before delivery rather than after. That visibility transformed how confidently I close a project.

What do you dislike about the product?

For someone managing timelines and deliverables rather than writing code the platform feels over engineered. Too many technical options competing for attention when all you need is quick visual verification before final sign off. A simpler non technical interface would make BrowserStack genuinely accessible for project and operations roles without reducing any value for technical team members using it daily.

What problems is the product solving and how is that benefiting you?

Post delivery client complaints about display issues on specific devices used to reopen closed projects and derail everything that came after. BrowserStack moved that discovery inside the delivery cycle where fixing costs time not relationships. Digital projects now leave the team already verified across real devices. Client confidence in delivery quality improved and post launch revision requests related to device compatibility dropped significantly.

What do you like best about the product?

The broad coverage of real hardware and browsers makes it very straightforward to validate our responsive designs. It also offers fast deployment capabilities, so we can spin up tests quickly and check real-world scenarios whenever we need to.

What do you dislike about the product?

The remote connection speed can occasionally feel sluggish, which leads to noticeable rendering lag during intensive manual script debugging. The initial workflow configuration also felt a bit complex and took some fine-tuning before it fully clicked with our routine.

What problems is the product solving and how is that benefiting you?

It tackles the core problem of cross-platform layout inconsistencies across different mobile aspect ratios and operating systems. By replacing hands-on physical device management with centralized cloud access, it helps eliminate fragmented infrastructure costs and simplifies the overall setup.

What do you like best about the product?

Years of full stack experience taught me that the gap between local development and real world behavior never fully closes - BrowserStack just makes that gap visible before it becomes a problem. What I appreciate most is how little it disrupts an already established workflow. Plug in, connect local environment, test on real hardware, done. No lengthy onboarding, no process overhaul - just honest results from actual devices that local testing consistently fails to provide.

For a senior developer managing both frontend and backend responsibilities simultaneously that efficiency matters more than any individual features.

What do you dislike about the product?

Parallel session limits become a genuine bottleneck during peak development periods. When the entire team pushes code simultaneously queued sessions slow down release validation at exactly the wrong moment. Dashboard navigation also feels like it was designed for someone with unlimited time to explore - experienced developers working under deadline pressure need faster access to what they use most.

What problems is the product solving and how is that benefiting you?

Full stack bugs that lived specifically in the intersection of backend responses and frontend browser rendering used to be the hardest category to reproduce and fix. BrowserStack made that intersection testable on real devices systematically. Production surprises became rare. Client reported issues became reproducible instantly. Release confidence stopped being a feeling and became something the team could actually back up with evidence.

What do you like best about the product?

Client mobile projects demand pixel perfect delivery across every device. BrowserStack made that possible without owning a single physical phone. Verifying my own designs on real hardware before client presentations - without waiting for developer feedback - gave me a level of quality ownership I never had before. Cross functional collaboration with developers became faster because design implementation issues got caught internally before anyone external saw them.

What do you dislike about the product?

Build for developers not designers. Finding the right device quickly during a live client session feels harder than it should. The interface needs a simpler layer for non technical users who just need quick visual verification without navigating through options built for engineering workflows.

What problems is the product solving and how is that benefiting you?

Late stage client feedback revealing design inconsistencies across devices used to mean expensive rework and awkward conversations. BrowserStack moved that discovery earlier in the process. Fewer revision rounds, faster approvals and stronger client confidence in final delivery. For a client facing design role that impact on project timelines is genuinely significant.

What do you like best about the product?

Building full stack applications with .NET core and Angular means you own both ends of the stack - and when something breaks in production it could be anywhere. BrowserStack narrowed that search dramatically. Angular components consuming web APIs behaved completely differently across real browsers and I would never have caught that locally.

Third party API integrations that rendered response data inside the frontend showed inconsistencies on real mobile devices that no amount of local Chrome testing revealed. What genuinely impressed me was the tunnel feature connecting my locally running ASP.NET application directly to real remote devices - validating the complete request response cycle on actual hardware without deploying to a staging environment first saved significant time during active development cycles.

What do you dislike about the product?

SQL heavy operations returning large response payloads through Web APIs sometimes exposed session performance issues that made it unclear whether the slowness was application side or BrowserStack side. That ambiguity wastes debugging time when you are trying to isolate a genuine performance problem.

What problems is the product solving and how is that benefiting you?

Third party API response rendering inconsistencies across browsers was a recurring problem that reached clients before it reached us. BrowserStack flipped that timeline completely. C# backend returning perfectly structured JSON that Angular parsed and displayed differently on Safari versus Chrome versus real Android browsers - that category of bug used to generate client escalations regularly.

Now it gets caught during development before anyone outside the team sees it. ASP.NET Core application behavior validated across real device and browser combinations before every release means deployments became predictable rather than anxious. The team stopped firefighting post release and started shipping with genuine confidence backed by actual evidence.