Aug 22, 2017 · 1 min read
Okay I see what you mean. So it’s not necessarily a one or the other approach it’s more “hey be aware of ADTs in Kotlin and use them when they make sense”.
I’m working on an example MVI app currently and I think I have an idea for using ADTs around navigation through the app. It’s going to be a simple 2 screen application where the first screen is a list and the second is a screen where you can add information. I’m probably going to have a type for AddItem (navigate to the Add Item screen) and ItemAdded (go back to the list). I may fudge around with the names but that’s the general gist.
Thanks for the response and the article!
