11 Reasons Why Not to Use Storyboards and Interface Builder || Why I stopped using storyboards and Interface Builder

Actually, up until a few months ago, I could not imagine creating a project without my beloved storyboard. I had looked a little into laying out constraints in code, and the syntax alone had scared the hell out of me. And yet, a couple of weeks after letting go of the storyboard, I couldn’t imagine myself ever using one again. 

So here are top 11 reasons why not using storyboards:

Reason 1 : Merge conflicts will drive you crazy. If you are working to team its better to avoid storyboards.

Reason 2 : Teaching beginner iOS programmers what is exactly going on is difficult with storyboards. Because we need to use drag and drop for outlets it's really pain.
 
Reason 3 : Difficult to record and explain things on storyboard because switching between stotyboards and View Controllers will take time.

Reason 4 : Screen size on laptop too small for storyboards. So we need a big external display.

Reason 5 : Productivity decrease when hands leave the keyboard.


Reason 6 : Refactoring all fonts in Storyboard components take too long.

Reason 7 : Compile time for complicated storyboards increases if you are building a big project.

Reason 8 : Cell Identifiers and Storyboard Id strings are unsafe it may leads to crash.

Reason 9 : IBOutlet & IBAction crashes when refactoring so we need to be carefull while refactoring.
 
Reason 10 : Difficulty in laying out views that are stacked. If there are so many subviews under , its difficult to give layouts.

Reason 11 : They complicate code reusability. In code, if you have 11 screens that look almost the same, it’s so easy to use a protocol to efficiently reuse your UI code between them. With a storyboard, good luck figuring out how to share outlets and actions!

For more updates follow us.