Architecture choices usually get argued as matters of taste. On Android, one of them was measured.
The usual case for design patterns is maintainability. Cleaner separation, easier testing, fewer surprises six months later. A 2023 study on Android interface rendering adds a second ledger to that argument, and it is one teams rarely check.
The team built one Android route navigation app twice, once with MVC and once with MVVM, then timed how long each version took to put its interface on screen. MVVM came out ahead. The reason is mechanical rather than mysterious.
In MVC, the controller has to tell the view to refresh after data arrives. That is an extra hop, and the user waits through it. MVVM binds the view to the data, so the screen redraws itself when the data lands.
The study is one comparison, not a verdict. MVVM carries its own costs, including more indirection and a steeper learning curve, and the paper does not claim it wins everywhere. Its claim is narrower and more useful: the pattern is a variable that affects performance, so it should be measured rather than assumed.
That has a practical consequence for how teams benchmark. Fast devices hide rendering delays that mid-range hardware exposes. If you want to know whether your architecture is costing you, test on the phones your users actually carry, running the scenarios they actually run.
Paramadani, Akbar, and Pinandito (2023). User Interface Rendering Time in Android Applications: Revealing the Effects of Design Patterns. Proceedings of the 8th International Conference on Sustainable Information Engineering and Technology.
