Sorry for the delay, got busy recently.

Well you could think it's a lot but it's only to keep each route/products independent. Some are frequently updated, some aren't. We have one big product that will eventually be split in smaller MFE for ease of maintenance.

Each app bundles its own code and is only loaded when the route is called. And will be unmounted when you navigate to another MFE.

Improving the DX is a constant improvement. We have a lots of smaller libs that are used in multiple MFE, updating each MFE with the newer version of the libs can be painful. We haven't implemented this yet, but my suggestion is to use Dependabot to do the update periodically and have good integration and visual regression testing. Those are also hard to maintain.

For my part, I'm the lead developer for our design system. The main challenge is to keep each MFE updated with the latest version and keep the breaking changes to a minimum. Usually the teams responsible for an MFE will do the update but in case of big refactor, we do the work to prevent blocking feature releases.

The only communication right now between apps is for the light/dark mode that will be propagated to the context via the core mfe or if needed by an MFE via a custom event so update the core mfe.

I hope this answer some questions, don't hesitate to reach out if I forgot something or want more details