4 ms·

So all of the scenes in your storyboards are blank? According to whom is this a "best practice"?

• bsaul 8y ago
  According to anyone that has ever tried to git merge a storyboard. But if you’re working alone on a small project , doing everything in the storyboard could be an option.
  • bunnycorn 8y ago
    What's the problem then? Unless two people change the same view at the same time, it won't have problems. And that's a management problem of putting two people doing the same problem. It's XML and it's easy to understand even. Also, separate components into different storyboards.
  • skohan 8y ago
    Not using storyboards due to the widely exaggerated git merge issue is throwing the baby out with the bathwater. In my experience, if you keep storyboards small merge issues are a minor, extremely rare annoyance. If you compare the time spent on merge issues to the enormous amount of time waisted on coding UI manually it's not even close.
    • bsaul 8y ago
      i do keep using xib, because they’re confined to one viewcontroller, and it makes it more possible to split to work between people. storyboard are meant to design workflow, so at least two screen but often more than that. The more you put screens in the same storyboard, the more the chances of a git merge issue. Git merge on storyboard aren’t a minor issue, they can take someone about an hour a day every day for the duration of the project, since most work on an iphone app is correlated with GUI changes. ( and then again it gets worse the more screens you have in a single storyboard). I personnaly didn’t think it was a problem until i had to manage a team of 11 ios developers working in parallel on a single app in rush mode. In that case storyboard are simply out of question.