title: Create a true plugin architecture using angular ivy
body: <p>I'm working at a project where we wanna build a web frontend using a &quot;true&quot; plugin architecture. Well, what do I mean saying &quot;true&quot;.</p>
  <p>Imagine having a web app for configuration. The frontend of this app can dynamically change as we are able to install functionality on runtime. We are therefore able to add some new features at runtime. My idea is to have a simple UI that can load multiple plugins. Those plugins can be loaded into this simple UI as single pages.</p>
  <p>At the time I'm compiling this simple UI for configuration I don't know the plugins that will be installed later. Unfortunately. My idea is to have a rest API that provides the plugins (maybe as webpack modules?) and that the simple UI will just load those plugins on startup.</p>
  <p>I did some research today and I'm quite not sure if doing something like this is possible with angular Ivy. As I'm not an expert maybe someone could answer this, before I'm going to dig deeper.</p>
  <p>Is it possible to create angular components that are not known at compile time to the app but that are later loaded via a backend?</p>
  <p>Thanks for a short response</p>
  <p>Best Regards</p>