Have you considered not using an iOS architecture?

Nicholas Swift
iOS Seminar
Published in
2 min readFeb 5, 2017

Why care about architecture?

If you’re making an app whose sole purpose is to change the background color when you click a button, which architecture should you use? MVVM, FRP, MVC, VIPER? Before reading the next paragraph (if you haven’t already), think long and hard about why you should choose the one you’re choosing.

If you’ve analyzed all the different possibilities and have come up with the perfect architecture that would fit this app, you’ve wasted your time.

It’s an app that literally just changes the background color when you click a button. Hell, put everything in your base ViewController and call it quits.

Choosing an app architecture is important for large scale apps, so that when you’re boasting over 20+ files inside your Xcode project you can easily manage your project, knowing where things are and your flow of information.

When a large project is your scenario, then app architecture becomes extremely important, and the classic MVC just might not cut it anymore.

This is why other app architectures exist. MVVM, FRP, POP, VIPER, and most of the time they are combined to custom tailor to the individual project. So if you’re starting a larger project soon in the future, or are currently building one, I highly suggest you check out the resources below.

--

--