Too many views in storyboard - Xcode running Slow

I'm helping someone out with an xcode project but it's almost impossible. They have around 100 View controllers on their storyboard and it's just running really slow. I've followed all of the guides on making Xcode faster but they just don't help for this situation. Outside of that storyboard, when we're working in the .h and .m files it runs perfectly fine, it's just inside the storyboard that it runs slow. Has anyone had any experience with a project like this? What did you do? Or what can I do to make it possible to work in the storyboard? Thanks

I faced the same issue when I was working on an Enterprise App. In the Project I had only one storyboard and all views in a single storyboard. Opening the storyboard caused Xcode to get very slow.

So I divided the storyboard into multiple storyboards as module-wise and load a separate storyboard per module like in the code below:

If I want to push a view controller:

UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@"storyboardName" 
                                                     bundle:nil];
UIViewController *viewController = 
 [storyboard instantiateViewControllerWithIdentifier:@"Members_ViewController"];

[self.navigationController pushViewController:viewController animated:YES];

ios - Too many views in storyboard - Xcode running Slow, Opening the storyboard caused Xcode to get very slow. So I divided the storyboard into multiple storyboards as module-wise and load a separate storyboard per  In this One Minute, you are going to discover that Xcode 11's default project is not using Storyboard anymore! Created and Edited by @AdrienVillez No macaques were harmed during the making of this

My solution is: Open a new Window from the Storyboard and minimize it. So it stays in RAM and won't reload. Working with the storyboard keeps quick and easy now.

Too many views in storyboard - Xcode running Slow, I'm helping someone out with an xcode project but it's almost impossible. They have around 100 View controllers on their storyboard and it's just running really  Too many views in storyboard - Xcode running Slow. I'm helping someone out with an xcode project but it's almost impossible. They have around 100 View controllers on their storyboard and it's just running really slow. I've followed all of the guides on making Xcode faster but they just don't help for this situation.

We're having the same issue, and commonly recommended performance tweaks didn't help. On a MacBook Pro with SSD I see CPU utilization go to 80-90% when in storyboard view and navigation lag is incredibly frustrating. Simulator can take up to a minute to display, and Xcode often won't close, requiring a force quit.

These symptoms all disappear if not viewing the storyboard, or if storyboard is open as source code.

UPDATE: We split our project up into multiple storyboards, and life is good again - CPU utilization is back to single digits and performance is on par with Xcode 4.6.3. There is definitely an issue with larger storyboards; the only change made to our code in the process was updating references to the main storyboard to a storyboardWithName call instead.

One of the view controllers in our project has a container view, and it appeared that the utilization issue stopped when that controller and its container view were moved to a separate storyboard. It may have been a coincidence, and we broke up the rest of the storyboard for consistency, but if I were dealing with this issue again, I'd first move any view controllers with container views to a separate storyboard.

Too many views in storyboard - Xcode running Slow, Opening the storyboard caused Xcode to get very slow. So I divided the storyboard into multiple storyboards as module-wise and load a separate storyboard per  Questions: I have too many views on one storyboard which is causing it to run really slow. I have been told that a solution to this issue would be to split the one storyboard into multiple storyboards. Could anyone tell me how I can segue from a view on storyboard 1 to a view in

If you are using Xcode 7, Storyboard References are a quick way to create multiple storyboards and will definitely help this issue. The great side about using Storyboard References is it does not involve any extra code whatsoever! See the stackoverflow link below for a full description on how to set it up.

https://stackoverflow.com/a/30772789/3316842

Xcode 9 storyboard .. painfully slow |Apple Developer Forums, Anyone experiencing very slow performance on updating storyboard in Dragging a new UIView or UIButton to existing view in storyboard is so painfully slow. After so many years, the quality of XCode is still a disgrace! What part runs slow? Xcode or the app on a device? If it's the app on a device you should start with Instruments and profile the application. If it's Xcode then having a storyboard with 200 view controllers is a lot. I would consider breaking it down into separate storyboards with maybe 20 or 30 scenes in each.

I'm facing the same problem. Massively frustrating. My storyboard has only 41 views. And I'm running a Mac Min i7 running at 2.3Ghz. With the storyboard open, it takes ages to do very simple tasks like move a UILABEL? Then, in counterpart view, editing code is like being back on a ZX81. It's all very well and good banging "intelligence" into the storyboard, but not at the cost of development efficiency. In so far as storyboard "size" guidelines are concerned, I don't ever remember reading that storyboards have to be split beyond a certain size. Maybe I need to read more.

To make the changes required, i.e. split the storyboard up, slap some VC's on several storyboards, will require a bit of a faff. I suppose if that's the new best-practice, fine. But I could do with more than conjecture.

My storyboard in xcode is insanely slow, it takes 10 seconds to clear , How many view controllers do you have? You may need more RAM. I have 16 and I still run into lags opening storyboard, even with storyboards that have 6-7 view  My storyboard in xcode is insanely slow, it takes 10 seconds to clear constraints or even make a constraint. if i begin a new project it does not have any delay. Is my computer bad or is it xcode having a hard time?

iOS Performance Tricks To Make Your App Feel More Performant , A slow and unresponsive app might make users give up on using your app or, Although modern iOS hardware is powerful enough to handle many intensive The launch screen storyboard is like any other storyboard file, except that you Xcode will notify you that using custom class names is prohibited. If you have too many of them on display in a single.storyboard file, it can become a problem to not only see them all and the connections to each other but also slow Xcode down to a crawl (even crash). To solve that problem we have something called ‘ storyboard references.’ They are live links to other storyboard files.

Using Storyboard References in Xcode, They have around 100 View controllers on their storyboard and it's just running really slow. I've followed all of the guides on making Xcode faster but they just  Thanks, this tutorial. I followed this without too many issues on Xcode 4.2 Build 4D5163b. It was useful for me since I'm new to developing for iOS. Obviously due to the NDA, there's not a lot around (Apple of otherwise) that is specific to the iOS 5 SDK.

Why is XCode running slow?, If you have too many of them on display in a single .storyboard file, it can and the connections to each other but also slow Xcode down to a crawl (even crash). to all the other views, then on each of the remaining views, there is a button to 

Comments
  • Apple actually never said "use one storyboard for everything". A xib represents a view, a storyboard represents one or more view controllers. They needed to represent the whole controller, not just its view. I mostly use storyboards with 1-3 controllers, representing one data flow. Also I heavily use nested controllers (content containers) and storyboard references. Even if storyboards with 10+ controllers were faster, it still wouldn't be a good idea to use them.
  • The app has 4 tabs, do you think we should make 4 storyboards? (one for each tab)?
  • yes why not and at the tab define you can Load separated storyboards as i mention. There are no any restication for crating multiples storyboards
  • So do I make the segue link to a view controller in a different storyboard?
  • Nope you doing woth code as we did early without story Board do not connect view segue link from stoaryBoard bcz we are difine instance or particular viewcontroller from storyboard programeticuly instantiateViewControllerWithIdentifier
  • If you need to segue from one view controller to another, they have to be in the same storyboard. That is why, if you have multiple storyboards, each one should represent one major path (or "story") in your app. For instance, if you have a tab-driven app with 4 tabs, where each tab has a navigation controller hierarchy, you could have 4 storyboards, one for each tab. When you setup the UITabBarController, you would have to instantiate the root view controller of each tab using UIStoryboard *tab1SB = [UIStoryboard storyboardWithName:@"foo" bundle:nil] etc..
  • This is perfect! I had just one view controller which was excessively heavy! Thanks!
  • Double click the storyboard.
  • Each storyboard is a (potentially huge) XML document that is parsed and displayed as a GUI when viewed. Maybe the performance dip between Xcode 4 -> 5 in Storyboard is because some caching/optimization was lost, but more likely because the Storyboards got a lot more intelligent in Xcode 5. The interface can check for and resolve constraint issues in real time, for instance.
  • How many screens were in your storyboard, for curiosity? Would be good to get a rough sense at what limit storyboards need to be broken down at.
  • I had 4 screens in a storyboard with < 50 objects total and it was a 6-7 second lag every click, sometimes more. The answer was the container view. As soon as i removed that it instantly went to smooth performance.