Chrome DevTools

Positive ROI as it is free with Chrome

Improved performance / speed of websites

Saves time with the preview of websites function

It's free

Reduces time cost for analyst to solve an bug

Can be easely teched to an avarege user

Premium brand look.

Free, saves money.

Easy to utilize on Mac or PC.

Website Performance Improvement

API Integration debugging

UAT

Reduced errors

Efficiency

Quality of work

It helps me every day to get my work done

My websites can be easily styled as I can check these styles easily in the front end

I spend less time figuring out what code is needed to get my websites to look right

Gain of time for DOM Exploring

ROI for performance and memory leaks finding

There is no negative impact on ROI

Positive: it is very useful for front-end developers to check the performance of the application

Positive: We can troubleshoot issue very quickly for production without code change.

Positive: We can test our own website while developing

Negative: For every project, my organization will give a new system. Every time I need to change the default browser to chrome as by default system will tab Microsoft edge browser.

Negative: Another developer will see our code and they will hack the website if it is buggy code.

Positive: having an analysis and diagnostics tool built into the browser

Positive: Facilitates remote support, any user can run the tool, even if they don't have admin permissions on their workstation

Negative: Requires good technical knowledge of networking and web programming to get the best out of the features the tool has to offer.

Good return on investment since it is a practical resource for front-end designers and programmers.

With in-place editing and debugging, changes are made immediately and can be tested.

Increased performance for webpage load.

Absolutely nothing. Maybe it should be easier for non-developers to use.

Check responsiveness of the website

Check performance of website

Check the elements of website

Execute code with console

Check our own website when developing

Positive ROI as it is handy tool for front end developers

Increased performance for website load

Free tooling and comes embedded with chrome

Easy to collaborate in the team

Positive impact as there is faster troubleshooting

Another advance is having less CSS issues

Having a limited customisation and options could impact the productivity using the tool

It takes time and resources in large corporations to change the default browser which in MAC is Safari and in Windows is IE/Edge

It greatly improves the development time and efforts.

It decreases the chance of having unexpected behaviour by visualising the web interactions.

No negative impact.

One major positive impact that using Chrome DevTools has on business is the ability to test your page on multiple devices, screen sizes, and user agents. You can do a lot of QA testing from chrome and that saves time.

Since DevTools is a free product that comes bundled within another free product I don't see any negative impact that derives from its use.

It helps us to get the job done. There is no negative impact.

It's free and powerful.

It allows for faster development.

It helps catch problems right away.

DevTools has streamlined our debugging process when "weird" things happen on our site. We have encountered at least one instance where a third party module caused our main CRM page to fail to load. We were able to quickly identify the problem request using DevTools and mask the offending site with a firewall rule that got our site back in operation for our internal customers quickly (albeit without the third party functionality) until the third party was able to correct the issue with their integration. This allowed us to get our sales organization back in operation quickly, which had a definite impact on our bottom line.

Since DevTools is baked into Chrome, it's free--which means the ROI is off the charts.

Further, because it is baked in, you don't have to spend forever looking around for another extension

And unlike Firebug, your webpages aren't going to render REALLY slowly if you have it open.

Decreases development time for paid projects.

Increases customer satisfaction as we are able to deliver quick fixes to reported issues.

Increases quality of paid projects as we are able to better test sites in a variety of circumstances.

It has saved us vast amounts of time in debugging by offering a quick and easy way to peer under the hood of our applications in browser.

The ability to immediately apply styling changes to your front-end view in-browser and see what changes and how it a massive help and easily reverted by a simple page refresh.

It may be relied on exclusively a bit too much by some developers and it is important not to let your engineers get into the mindset that they should only test your front-end in Chrome.

It has all the benefits on can have with a tool and return of investment is also very good in my thoughts, but the exact data in regards to how my organisation invests in it is not available to me.

All positive, the tool is free so there's no need to spend money on it. Every return is positive.

A lot, their tools increases productivity due because it helps developers to create and test websites inside the browser.

Tools are intuitive so there's no need to invest in education on developers to learn these tools.

It is a free tool so it is hard to give a negative impact. The positive is that it saves a lot of time, the changes you make are visible in your browser immediately. There is no need to upload your changes to your local or remote server and then refresh your browser.

Chrome DevTools is a very good free solution for multiple different use cases.