The MVC pattern is basically what you end up with a naive implementation of a GUI interface. A more sophisticated solution is the plugin pattern where independe

The MVC pattern is basically what you end up with a naive implementation of a GUI interface. A more sophisticated solution is the plugin pattern where independent code can "plugin" by for example listening on events. It's kinda like MVC but backwards, instead of a button updating the view, the plugin/view listens for button-clicks. And if a server is involved, the view/plugins should listen for events sent by the server. Where each little plugin/component do it's own thing independently. If you for example have a "new messages" badge that shows both new messages and new chat messages, it should listen for new messages and new chat messages!! versus the spaghetti-strategy of having both the messages model/widget and the chat model/widget update the new-messages widget.