Exactly. Integrating many apps is something we do as well. We have a large application that handles roughly 500 different domain classes (just scan through <a href="https:&#x2F;&#x2F;apidocs.mendix.com&#x2F;modelsdk&#x2F;latest&#x2F;" rel="nofollow">https:&#x2F;&#x2F;apidocs.mendix.com&#x2F;modelsdk&#x2F;latest&#x2F;</a> to see how vast that is).<p>This approach enables our partners to write plugins that are not only simple to write, because they can just work with &#x27;plain&#x27; javascript classes and arrays (and don&#x27;t need to learn the whole, for example, redux architecture), but which are also really easy to integrate in our visual tools. Our UI stays always efficiently in sync with <i>whatever</i> mutations plugins make. In an architecture with explicit subscriptions, events or selectors this would be a lot harder to achieve.