A modern programming language that makes developers happier.

kotlinlang

I am confused about a scenario where there are couple of activities put together, but I want to have single viewmodel for each of the activities instead of keeping each activity with their individual viewmodel. What are pros and cons with this approach?

what do you mean with “put together”?

In an application, suppose A,B,C are activity and A launches B, B launches C. "put together" i meant in an app...

Separation of concerns comes to my mind first

Also if they’re using the same viewmodel it’s a code smell they should be fragments not activities, since the concept behind an activity is that it’s a completely separate thing, and if they have a shared VM then that implies they’re actually tightly interwoven and relate to the same process/activity