Merge Code & Components into One?

[emozio]

Hey everyone,

I have an idea for a new feature that you might find either really useful or completely unnecessary. It concerns the Code and Component Tree tabs—I believe these could potentially be integrated into a single view. Let me explain.

While the Graph tab does provide insights into relationships, I find it somewhat abstract and not particularly valuable in practice. Of course, I’d love to hear about your experiences. However, since its purpose is to illustrate connections between code and components, I wondered: could the Code and Component Tree tabs be merged into one for a more cohesive experience?

Here’s how it could work:
Each time a component is selected, the corresponding or interacting code would be highlighted, and vice versa. This way, both the code and component structure remain in view, but within separate panels or subwindows inside a single tab. To clarify, I’m referring to the following view:

I do understand that global components take up part of the screen, but in most cases, they don’t need to be so prominently displayed. This approach could potentially streamline the workflow without sacrificing clarity.

Of course, this is a subjective take, and I’d love to hear your thoughts—whether you agree or completely disagree. Looking forward to your feedback!

Thanks!

[emozio]

While we're on this topic, I also think a few options could be removed entirely. For instance, Code Search seems redundant given that there's already a search bar at the top. Similarly, State might not need a dedicated section—how often do you check it separately? Wouldn't it make more sense as part of debugging?

Additionally, the "Add UI" button feels out of place, as most users would likely use the Component Tree to insert elements. On that note, there's currently no way to add Modules directly from the Component Tree, which I strongly recommend supporting.

In my view, less is more. These changes would make the interface easier to scan and process, particularly for newcomers.

[sarahs]

Really solid suggestions here, @emozio ! I passed this along to the Eng team, and it’s already sparked some great conversations. We’re definitely looking at ways to streamline app-building even more in 2025, so it’s super helpful to hear what would make it smoother for you.

Can’t promise anything specific just yet, but this kind of feedback is always valuable as we think about improvements—keep them coming!