How many projects use Storyboard in thesedays?

Hi !


I am return developer of iOS. (for 2 years I used to develop android apps)


I had not used storyboard, because I used to use nib files only.


Now, how much of projects use storyboard ? ( more than 90% ??????)


Is there still many projects do not use storyboard ?


For me, storuboard is not easy to understand ....


But, if storyboard is main trend of iOS development, I love to study stortboard surely.


Thanks alot ! love!

Answered by westerlund in 42285022

Storyboards are definitely the way Apple wants us to go. I'd say they're pretty polite and easy to use when you get to understand the basic concept.


Some things to know about Storyboards:

- They're slowing the compiling down a lot

- There's currently no easy way to re-use custom views, like cells in multiple collection views

- Layouting and implementing design is so much faster using Storyboards, and with @IBDesignable and @IBInspectable you can even render custom views


I personally didn't like Storyboards, basically because Interface Builder used to be quite bad, but now I use Storyboards in all new projects!

Accepted Answer

Storyboards are definitely the way Apple wants us to go. I'd say they're pretty polite and easy to use when you get to understand the basic concept.


Some things to know about Storyboards:

- They're slowing the compiling down a lot

- There's currently no easy way to re-use custom views, like cells in multiple collection views

- Layouting and implementing design is so much faster using Storyboards, and with @IBDesignable and @IBInspectable you can even render custom views


I personally didn't like Storyboards, basically because Interface Builder used to be quite bad, but now I use Storyboards in all new projects!

Storyboards are strictly a personal choice. I still use individual xibs for most of my work

and storyboards only when it's necessary (Apple Watch apps for example)...


There really isn't a lot of difference between the two techniques both are the same xml formatted

files, the main difference is many views are contained in a single storyboard which can make it

easier to see UI flow if you have a large display but you do lose some flexibility going that route.

Other than reuse of a custom view, which I rarely run into needing, what flexibility are you losing? I never use XIB any longer because storyboard makes things so much easier for me, and now that they finally let us use references to other storyboards, the main complaint I had about them is gone (They could get too big)

The main loss of flexibility comes from data loss. If that single storyboard is damaged

you've lost all of your views and have to reconstruct every one of them. With seperate

xib's if one is damaged, it's just one view to reconstruct. I also find it much simpler to

have things seperate since I can modify one part without it effecting any other part of

the app in appearence or function. It's a bit more code but worth it to me.

How many projects use Storyboard in thesedays?
 
 
Q