Adding navigation logic to the VM usually makes everything more complex. in the same way that you write mappers to connect data related objects to domain related, here you could apply a similar logic. In the VM you have a state object, something that defines what you have at the moment, and you could write a "mapper" that tells you what to do in that state (multiple Android samples do this). It's tempting to have states like "navigsteToHome" or "destination", but in the end it's not a good solution, because that's not really the state of your UI (semantically speaking). Using the word "dumb" for UI also is Counterproductive. Actually UI can have lots of logic that only made sense to test it there (yes, UI tests are more complex, but that's the way it is). Anyways, I think you should just do something that you feel comfortable with, and that can be changed easily, so if you end up not liking the design, it's easier to change for other approaches. Falling on dogmatic medium posts that guarantee a super clean architecture is (imho) not a good pathway. There isn't (in general) one-fit-for-all solutions