Summary
In this chapter, you learned how to create appealing SPAs using individual plugins, which are merged into a single coherent web application. In contrast to the classic plugin architecture, these modules may get privileges and responsibilities that are on the application level.
As with the SPA composition before, you've seen that user interaction is meant to be quite high, but unlike SPA composition, the user experience and developer experience are supposed to be smooth. While the internal complexity and tool reliance has increased, the major drawback is the dependency of the modules to the API defined in the app shell.
In the upcoming chapters, we'll see how we can efficiently deal with updates to the app shell. We will see that governance and design awareness are required to establish a common foundation.
In the next chapter, we will start the journey of onboarding everyone – not only the developers – with a preparation round involving the...
