I'm currently working on an Android application using Jetpack Compose and Hilt, following the MVVM architecture. My HomeScreen has a large ViewModel handling five dynamic tabs(HorizontalPager), each providing different functionality. These tabs share some common data (UI state) and are hidden if their respective functionality is unavailable.

To improve maintainability and separation of concerns, I'd like to refactor this into multiple ViewModels.

Ideally, I'd have:

• 1 main ViewModel for common data
• 1 ViewModel for each tab (5 total)

Has anyone implemented a similar structure? What suggestions do you have for structuring this? Are there any potential pitfalls or best practices I should be aware of?

I'm looking for guidance on how to structure multiple ViewModels and handle shared state between them. A clear explanation, code examples, or references to relevant resources would be greatly appreciated.