MVVM, MVP, MVC or VIPER, all of these are not Architectures, they are design patterns because they only guide you on how someone should handle the Presentation Layer. An Application is much more than the Presentation Layer. So if I ask a team how is their Application Architecture, and they respond with MVVM, they are just telling me that they use MVVM to handle UI State. What about the Network Infrastructure, Database Infrastructure, how do you abstract data fetching, where is the business logic code, is it separate from the Presentation Layer? Etc... Application Architecture can't be described with a combination of letters, only through diagrams.