MVC is fine. After years experience in mobile development, my main takeaway is that application architecture acronyms in general are over-rated. The most impo

MVC is fine. After years experience in mobile development, my main takeaway is that application architecture acronyms in general are over-rated. The most important thing is to separate concerns, and to agree on some sensible structure for managing views and state, and communicating between them. Usually the details of that should arise from the needs of the application, not come top-down from some idea about "the perfect application architecture". Aside from that, everything should just be kept as simple as possible. IMO it actually adds a lot of unnecessary pain and complication to a project when a team is too rigid about which letter of an acronym each piece of code must fit into. VIPER would be an extreme example of this. It should not take five+ separate code files to execute an HTTP request and display the results in a list view.