Why Swift Developers Don’t Need More Than MVC

Other architectures are fine, but MVC is all you really need

Photo by Kelly Sikkema on Unsplash

There are a lot of architectures and patterns out there. You’ve got MVVM you got MVP, VIPER. Each pattern and architecture is created to deal with specific scenarios or problems that are common to iOS Development, or software development in general.

Knowing various patterns and architectures is advantageous. But there’s a common misconception among many Swift developers. That misconception is that to be a good Swift developer you need to know tons of patterns and architectures. This makes some developers feel inadequate if they only use MVC.

Why a Good Swift Developer Doesn’t Need to Know a Ton of Patterns

In the last article I wrote about patterns,

RichG

mentioned something very interesting. He said that they went to a meetup and poled 8 senior developers on what architectures they use. Every single one of them only used MVC. And all these Swift developers were senior.

So what does that mean?