My #1 Tip When ViewModels Grow Too Big

When a single ViewModel grows too large due to complex screens with multiple features, the solution is simple: use multiple ViewModels per screen. There is no rule requiring one ViewModel per screen. For a complex screen like a video calling app with integrated chat, splitting into a VideoCallViewModel and a ChatViewModel gives each clear, isolated responsibilities. Each gets its own state class and action interface, and both states are passed down to the composable screen. This reduces complexity and improves maintainability without any architectural violations.