In fact, it isn&#x27;t. From a quick perusal of the github repo[1], it seems that the react devtools can mostly stand alone, and have wrapping shells that access the Chrome and Firefox APIs when necessary. Here&#x27;s the plain shell: [2]. My understanding is that the GP was trying to convey this architectural flexibility while pointing out that the Chrome shell is more mature because it is the tool of choice for most devs at Facebook.<p>[1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;react-devtools&#x2F;" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;react-devtools&#x2F;</a>
[2]: <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;react-devtools&#x2F;tree&#x2F;master&#x2F;shells&#x2F;plain" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;react-devtools&#x2F;tree&#x2F;master&#x2F;shell...</a>