Inspired by this forum post:
If they need to add a legacy component that is NOT already in use in their app, they will have to go to considerable lengths to add it, e.g., adding it to a different App, and then copying and pasting between the two Apps.
Given the sheer number of components that a dependency can add, plus the need to access the Palette of older components, it’s starting to make sense to add tabs at the top of the Palette, one tab per source of the components.
This can be especially helpful when roles/components from one set are intended to work with components from the same set. Those boundaries are then much clearer to the developer.