Screen state modeling

RU / Day 2 / 10:30 / Track 3

The talk about how to model screen state, why it's needed and how it helps solve problems with fuzzy, incomplete and ambiguous requirements and why not only developers but also related teams of products, designers and testers have benefits from it.

Also, there will be a story about architectural approach to screens modeling which is used in the "My Beeline" application. Some goals that were set before the creation of the approach will be affected, with the help of which it was possible and what insights the team had. After that, there will be a lot of examples of the real screens, the story about intricacies, degenerate cases and exceptions. The icing on the cake will be the opportunity of complete removal of analytics from Interactors, Presenters and View.

During the planning of the report, Dmitry was inspired by the book "Object-oriented modeling and development" as well as the information from his friend who is an enterprise architect. As a result, the described concept was born.

The described approach can be safely used in existing projects written in VIPER/RIBs/CleanSwift/MVVM/MVP.