, 10 tweets, 3 min read Read on Twitter
For the past couple of months, I have been working on a new version of ⚛️🛠React DevTools. Soon this new version will replace the existing version. (I will be writing a blog post on reactjs.org soon explaining what this means and what the rollout process will be) but-
As the new version gets closer to feature complete, I wanted to share a few thoughts.

First: I hope the new version of DevTools will be much faster than the previous version. (I recently wrote some background info about this if you're interested: github.com/bvaughn/react-…)
I also hope that the new version will provide a lot of UX improvements: better searching, new "owners list" and "owners tree" views, better hooks integration, etc.

I plan to add a lot of additional advanced profiling/debugging capabilities over the coming months too!
That being said, I expect that a few of the changes will be controversial.

For example:
1. The new DevTools does not show inline props, only the name and key (if there is one).
2. The new DevTools does not show DOM elements in the Components tree.
A lot of thought (and some early user testing) went into these decisions. I believed it was the right tradeoff to make DevTools faster and easier to use.

The overall the feedback I've gotten from beta users has been positive, but there has been some negative feedback too.
Both types of feedback are welcome and appreciated.

So thank you. Please continue to share your feedback.

The new UX is not perfect (or final). There are definitely some things that will turn out to be wrong, and we'll work with users to improve them over time.
Whether we act on feedback usually boils down to a few factors:
1. Is this a common request? Would a significant percentage of users want this change? (This may change over time.)
2. How difficult would this be to build? Would we need to sacrifice any other important features?
Sometimes I may respond to feedback with an explanation for why a feature is the way it is currently. I hope this feels like an open discussion rather than a defensive reaction, but please correct me if I set the wrong tone. I don't want to stifle feedback or seem unappreciative.
Anyway, as I mentioned at the start of this thread- I plan to write a real blog post about this soon.

Thanks for listening!
I wish I could edit Tweets 😔 I said "I" here when I should have said "we"

The new DevTools has already starting getting contributions from people other than me, which is awesome.

And WE plan to add a lot of additional features going forward...
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Brian Vaughn
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!