I made a few updates today to better format the MudBlazor interface components, making more use of the Stack component and the Class style options. I also found the Dispose component lifecycle method on Microsoft’s documentation, which seems similar to the OnDestroy method in Unity. I reworked the event subscriptions using this Dispose method, so the Razor pages subscribe to the model updates when they’re initialized, and then unsubscribe when they’re disposed of. Anyway these changes should make it easier to add more interactivity to the model, which is what I’m planning to work on next. Here are the two Microsoft Learn pages on state management and component disposal that I found very helpful today.