Oleg has over 5 years of experience developing Android apps and has worked with various architectures from Loaders/Services to MVI. He discusses how architectures have evolved from Service/Loader patterns to MVP and Clean Architecture. MVI is described as having advantages like reliable state management, testability, and forcing better app decomposition, but also potential disadvantages like complexity for new developers or with large states. Common MVI frameworks and concepts like states, flows, and handling side effects are also covered.

1. MVI in production
Mazhukin Oleg
Senior DataArt Developer

2. Mazhukin Oleg
Senior Android Developer
I Have over 5 years experience of developing Android apps
and came a long way through various architectures in
production. Have wide experience with different architecture
solutions from Loaders/Services to MVI.

3. How did we all start

4. Service/Loader Pattern

5. MVP

6. Clean Architecture

7. MVI

9. User app interaction

10. User app interaction

11. User app interaction

12. User app interaction

13. User app interaction

14. User app interaction

15. - UI is a cycle
- UI is a function
- UI is asynchronous
- UI симетричен с пользователем
- User is a function
User app interaction

16. User is a function

17. Reactive programming

18. Reactive programming

19. App architecture bullet points
- Events stream
- UI Stream
- Cycle

24. App architecture

26. Let’s talk about the model

27. Why model?
- State problem
- Screen orientation changes
- Process death
- Immutability
- Reproducible states
- Testability

37. Too complex?
- Flexibility
- Immutability
- Reproducible states
- Testability
- State partial change

43. States
Flow

44. What’s next?
- Complex States
- Side effects in MVI
- Testing

49. Disadvantages in MVI
- Can be too complex for new developers
- Becomes very complex for big states
- Hard to test all state flows
- Side effects still use MVP approach
- Lots if analyzing possible states
- UI redraws every time state changes
- Some logic need to be implemented on every screen

50. Advantages in MVI
- Reliable state
- Single method that changes view state
- View interface reflects it’s functionality
- Testability
- Force to decompose app
- Force to think about states and state changes

51. Available frameworks
-'com.hannesdorfmann.mosby3:mvi:3.1.0'
-'com.github.badoo.mvicore:mvicore:{latest-version}‘
-'com.freeletics.rxredux:rxredux:1.0.0'

52. Summary

53. Mazhukin Oleg
Senior Android Developer
Mail :mazhukin.social@gmail.com
LinkedIn: https://www.linkedin.com/in/oleg-mazhukin-7415847b/
https://github.com/HellCat24
Thank you!