So if we don't have time, should we stick to Massive View Controller ?
So if we don't have time, should we stick to Massive View Controller ?
Ibrahim Kteish
2

Well… it depends.
First of all, it’s not a developers decision when the product should be released. And which features should be included.
If you are familiar with Lean methodology (ship early-measure-decide-iterate) then you know that it “forces” you to go fast. I’ve been working in a startup that was using this methodology. I made the first version of my app in a month. It was ugly MassiveViewControllers + Stackoverflow solutions. Next release was with iPad support, next one with more features. Business logic of the App was changing rapidly. Yeah, it was an ugly code. But after several releases, I had a month of refactoring and I rewrite most of the main ViewControllers to MVVM. After a year and couple of releases-refactorings, it was more or less acceptable code. By this time we had like 1M installs and 160K MAU. In this case, VIPER is running in front of the train. 
But my case was really unique. Even if you don’t have much time to implement MVVM or VIPER it does not mean that you stuck with MassiveVC. You can apply some best practices from the community. There are plenty of articles on that.

Show your support

Clapping shows how much you appreciated Andrei Malyhin’s story.