CODEWITHSUNDEEP
iosxcodeversion-controlstoryboard
icemelon
icemelon

Reputation: 1711

How to manage the development of storyboard when several people edit the storyboard?

All of our views are in a single storyboard. After we edit the interfaces we are responsible for, we find it is a disaster when we commit the storyboard. Do any better ways exist that make it easier to manage the storyBoard? Should we write UI with code instead of storyboard or xib? While it is really efficient to use storyboard.

Upvotes: 2

Views: 1483

Answers (3)

Sergey Demchenko
Sergey Demchenko

Reputation: 2954

The following post helped me to understand answer on this question: http://robsprogramknowledge.blogspot.pt/2012/01/uistoryboard-best-practices.html

Upvotes: 0

Bunyod
Bunyod

Reputation: 1371

You need to read this links:

  1. http://blog.waynehartman.com/archive/2012/01/07/uistoryboard-on-ios-5-the-good-the-bad-and-the.aspx
  2. http://www.linkedin.com/groups/Which-is-better-StoryBoard-NIB-162305.S.185584395
  3. Should I use storyboard and mercurial for team work?

Storyboard is one single file, so only one person can work on the storyboard at once. It is essential factor for working with team in iOS.

Upvotes: 1

Eric
Eric

Reputation: 5681

What's generally worked for me and my team is to separate related functionality into different storyboards. So if one person is working on x portion of the app, stick all things x related there. As long as only one person is dealing with each component at a time, there's no chance for conflicts that blow up your whole storyboard.

Another thing to keep in mind if you can only use one storyboard, is to limit who can work on each ViewController in the storyboard. It's not the best idea to have multiple people working on the same controller anyways, since you will both be interfering with each others layout. I have found that as long as we stick to our own components, merges are super easy.

Your solution of using code instead of storyboard is also a very valid way to go about it. The decision between code and xib based approaches depends on the user. Code takes longer to get going, but is super easy to reuse, whereas xibs/storyboards make prototyping a snap but are very hard to reuse.

Upvotes: 1

Related Questions