Why Do We Not Have Legacy MVC, MVP, And MVVM In Flutter App Architecture

A little known secret-handshake thing about Flutter is that we no longer are forced into using legacy MVC, MVP, or MVVM App architecture. Let’s work ourselves backwards from the end-customer app user experience to the flutter SDK stack and see why that is the case.

Fast Response To User Actions UX

We should ask what is wrong with web apps as opposed to non-web apps in the area of app-user experience. Web apps come up slow in the browser and lack the visual adherence to computer-platform-UI customs that users of those computer-platforms expect. The irony here is this is similar to the reasons cited by the original engineers that started the Flutter project.

But, now I have to get into the technology specifics to explain why we do not use legacy MVC, MVP, or MVVP.

View Legacy

Yeah, we need to talk about this. When Android SDK came out in 2008 it was centered on having a View with no differentiation between a state and stateful view. The only thing revolutionary was the use of XML as layout presentation configuration of the view. But along with Apple’s UIView: