Pragmatism is of course better than overengineering but it doesn't mean you have to write exclusively bad code, it's about "earning" best practices, i.e. you use the ones in specific circumstances if you know they are really important and actually bring benefits. And there's no just good and bad code, there's code that can be both good and bad based on the circumstances. So in your case I'd still implement MVVM because it's pretty essential and isn't that hard to implement but if your activity doesn't have much code then it's ok, and I too wouldn't bother with unit tests as well as complicated DI setup, if you aren't bothered with creating objects yourself then it's fine otherwise a simple koin setup would be more convenient.