4 ms·

Storyboards kind of suck for any team bigger than 1 as far as I’m concerned. They also lock you into a visual binding style development pattern the doesn’t scal

• dep_b 9y ago
  I think that's a bit overstated but it really depends what kind of application you're writing. I have an accounting app I maintain alone where I almost completely abandoned storyboards because a lot of screens had similar elements and it was very important to have all data reliably passed around. Also helped with consistency and maintainability. On the other hand I'm doing a new app with three people now where we use storyboards because every screen is vastly different. The following things should be improved to make storyboards more useful in teams: * No more bullshit changes of 0.5px just by looking at the storyboard alone * Compile time check for connected outlets and actions, allowing to set them without the ! or ? * Constructable view controllers that always require you to init them in some kind of way, so you don't end up with optionals everywhere * Reusable constants for colors, sizes etcetera. I want to simply state cellSpacing as a value for the constant of a constraint where cellSpacing is something I can change in one place. * Reusable components / controls, like .xibs but immediately visible * Less flaky IBDesignable performance