Scouttlo
All ideas/devtools/Plataforma SaaS que ofrezca herramientas de desarrollo web modulares, personalizables y remotas, integradas con navegadores como Firefox, con enfoque en rendimiento, UI mejorada y soporte para desarrollo móvil.
HNB2Bdevtools

Plataforma SaaS que ofrezca herramientas de desarrollo web modulares, personalizables y remotas, integradas con navegadores como Firefox, con enfoque en rendimiento, UI mejorada y soporte para desarrollo móvil.

Scouted 6 hours ago

7.0/ 10
Overall score

Turn this signal into an edge

We help you build it, validate it, and get there first.

Go from idea to plan: who buys, what MVP to launch, how to validate it, and what to measure before spending months.

Extra context

Learn more about this idea

Get a clearer explanation of what the opportunity means, the current problem behind it, how this idea solves it, and the key concepts involved.

Share your email to view this expanded analysis.

Score breakdown

Urgency8.0
Market size7.0
Feasibility7.0
Competition6.0
Pain point

Los desarrolladores web y diseñadores necesitan herramientas de desarrollo integradas en navegadores que sean potentes, personalizables y no saturen la interfaz.

Who'd pay for this

Equipos de desarrollo web, diseñadores UX/UI, empresas de software que buscan optimizar su flujo de trabajo de desarrollo y depuración web.

Source signal

"The current plan is to build a bunch of performance-related tools, improve the user interface, make the tools remotable (for mobile development), and drastically improve the WebConsole."

Original post

Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

Published: 6 hours ago

I'm @paulrouget. I'm part of the Firefox Developer Tools team (we are working on the builtin tools and Firebug). I believe that the HN community includes a lot of web developers and designers, so I guess you can help us.<p>We have recently added a bunch of new builtin tools in Firefox (please try Firefox Aurora or Firefox Nightly to see a recent version of these tools). We also redesigned the way we show these tools (screenshot here: http://paulrouget.com/e/toolboxTesting/).<p>We are now working on defining what should be our next moves, and I'm trying to gather as much feedback as possible.<p>The current plan is to build a bunch of performance-related tools (see https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.developer-tools/L9vfZ1-smUI), improve the user interface (better theme), make the tools remotable (for mobile development), and drastically improve the WebConsole (see an experiment here: http://paulrouget.com/e/jsterm.v2/).<p>But we really want to get as much feedback as possible to make sure we're going into the right direction.<p>What do you think we should add/remove/fix in our tools? Anything you miss from Chrome or Opera? Or anything you haven't seen yet you'll like to see part of the browser?<p>PS: because a lot of people have raised concern about "cluttering" Firefox: we are considering providing some of these tools only as addons, to keep the Firefox DevTools as simple as possible.