Fire TV killed Chrome DevTools. Good.

Every migration note frames it as a loss. React Native on Vega moves off the old Chrome-debugger path; Amazon's docs point you at React Native DevTools instead, and old-RN apps are told to "use Chrome DevTools instead" like it's the thing being taken away. Cue the mourning. But step back and ask what that debugger was ever good for on a TV — and who was actually served by it.

This is part three of the Vega teardown, after the debug bridge and the closed driver — and it's the one where Amazon gets it right.

A debugger for apps you control

Chrome DevTools is a white-box tool. To attach it, the app has to be yours: Vega's own setup for React Native DevTools requires Metro running and "a Vega app built in debug mode" — you need to be the author, or hold the keys. That's fine for a developer poking at their own build. It's a wall for anyone doing the other job: testing across apps you didn't write. On the TV platforms that kept a debugger-first model, that wall is the whole pain — dev-mode toggles, re-signing test builds, debug-launch dances, just to read one screen.

	CDP — the white-box way	Accessibility tree — the black-box way
the app	must be debug-launched	any app, as shipped
the keys	dev-signed, yours	no signing, no debug build
setup	per-app, every time	zero per-app setup
production apps	impossible — you can't sign Netflix	work from the first call
speaks	DOM and JS internals	elements: ids, roles, bounds

What stands in the debugger's place for automation on Vega is the accessibility-tree model — the same idea Appium and UIAutomator are built on. Instead of injecting into an app's JavaScript, you read the system's UI tree of whatever is on screen. No keys required, because you're not opening the app — you're reading the surface it already exposes to the OS.

The receipt: a production app we don't own, read in ~130 ms

Here's the thing the white-box path could never do. We pointed the on-device automation server at the live home screen — Amazon's own shipped UI, an app we don't own, can't sign, and have no source for — and pulled its element tree in about 130 milliseconds:

<root>
  <app name="com.amazon.frenchpress">
    <window 1920×1080>
      <child test_id="featureRotator_learnMore" 168,832 240×64/>
      <child test_id="scrollableRow_title_text" …/>
      <child test_id="tile_..._touchable_3" …/>
  … 393 elements, every one addressable by id

Element ids. Roles. Pixel bounds. Enough to write findByTestId('featureRotator_learnMore').click() against an app whose source we'll never see. Under the debugger model, this screen is a locked door. Under the tree, it's a document. For a device lab — where the whole point is driving other people's apps at scale — that's not a downgrade. That's the feature.

A debugger lets you test your app. The tree lets you test everyone's. On a TV, the second job is the bigger one.

Coordinate-free, and sturdier for it

There's a quieter win. Because you address elements by identity — test_id, text, role — not by pixel, your tests survive a layout change that would shatter a coordinate script. "Press Play" keeps meaning the Play button when the row reflows. That's the robustness web testers get from selectors, now available on a set-top box, precisely because the model stopped being a JS debugger and became an element tree. It is the same outside-in philosophy as measuring TV performance without touching the app: the less your tooling demands of the app, the more apps it works on.

The honest cost

This isn't free, and the fair version of the argument says so. If you're the app's developer, the white-box goodies — live console, breakpoints, component inspector, profiler — are genuinely useful, and the tree gives you none of them. Vega keeps all of that for you through React Native DevTools on a debug build of your own app; it just isn't there for black-box testing, and by definition never could be.

So the honest framing isn't "the debugger was bad." It's that the debugger was the wrong tool for the job most people around a TV actually have — validating that a build behaves, across apps, without owning any of them. For that job, a platform arriving without a general debugging back door pushed everyone toward the model that was going to win anyway.

The take

Mourn Chrome DevTools if you're debugging your own app. Cheer if you're testing the platform. Vega arriving debugger-less for third-party automation nudged Fire TV testing onto the accessibility-tree model — black-box, no signing, coordinate-free, working on production apps from the first call. That's not what a regression looks like. That's a platform picking the right default by leaving out the wrong one.

Part three of the Vega teardown, after The one-line fork and The driver you can't read. The page tree and timing above were captured from a live Fire TV Stick (Vega OS 1.2) via the on-device automation server over adb — no app source, no signing, no debug launch. App identifiers are the platform's own. Chrome DevTools is Google's; React Native is Meta's; Vega and Fire TV are Amazon's. Independent commentary.