MVVM vs MVI in big production apps | Catalin Ghita and Florian Walther

MVVM vs MVI for big Android apps.
Coding in Flow Podcast full episode: • How to Successfully Se...

[@Alchemist10241]

MVVM is easy to understand and explain, and memory efficient (it doesn't create a lot of intermediate objects) but generates more bugs because it is more difficult to track events in this arch. MVI is much more scalable, maintainable and testable and if you get the concepts right, it makes programming so straightforward, but it comes with a price; MVI arch makes a lot of intermediate objects which in turn makes the app a little slow I, too, think MVVM + MVI is a better option. Thanks Catalin Ghita.

[@bitwisedevs469]

The argument on the last question still very weak in my opinion.

[@wagnerarcieri]

Could someone please type the name he mention at 9m43s ??

[@ebrahimshami9928]

you can use 9:43 to jump to specific time in a video. the name he said is "gabor baradio" according to the subtitle.

[@qwerasdfhjkio]

Gabor Varadi