What type of Android developer are you?

If your existing code uses public property instead of getter and setter and you want to use Kotlin then, it will force you to use getter and setter.
If you might think of using Kotlin, first you need to refactor legacy code to use getters and setters.
I think you should show some unit test for your article. Main point of MVP and other patterns are to make testable code. If we don’t know how to test the pattern, those design patterns just end up creating more classes.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.