In upstream Backstage, the New Frontend System is still in alpha state, and known to not be ready for some production solution to be based on it.

So it seems that we cannot base the released RHDH frontend application on top of it right now.

However upstream the frontend application is being actively worked on and structured, using the new frontend system framework. And the final component granularity and extension point availability provided by the upstream New Frontend Application will highly impact the feasibility & complexity of basing the existing RHDH frontend application extension capabilities on top of it.
So we should contribute as much as we can to the New Frontend Application components and extension points.

This is very important since it :

• provides a great opportunity to increase our contribution to the upstream project,
• allows us limiting the amount of application customization left on the RHDH side, and avoid being blocked in the implementation of some existing RHDH extension capabilities.

For more context, here we distinguish:

• the new frontend system framework (underlying APIs & application runtime), part of the Core backstage frontend packages,
• the new frontend application, which is a frontend plugin itself comprising the whole frontend UI, providing a bunch of extensions points, and based on the new frontend system framework primitives.

This outcome is really about helping shaping the final structure of the New Frontend Application.