"iOS Dev-5" storyboard or a hard-pressed stack of code? Look at the words of the family

(1) The game between code handwriting Ui,xib and storyboard, and some tips from interface Builder

For beginners, it is advisable to use storyboard without having to spend too much time in the boring code to lose interest. And as for the code, he says that using storyboard inevitably will use the code. The xib mentioned here should be the predecessor of storyboard. At that time the xib is not suitable for version management, such as the diff to check the differences between two versions, so for a bigger serious project is code first, and Xib as an introductory exercise bright. But since the storyboard evolved, nature has improved a lot, so ...

(2) What is the difference between StoryBoard and direct write code?

If you want to really understand the internal code logic, it seems inevitable to study the code behind builder, and if you're investing in a time-limited project, it's not economically worthwhile to study internal code and abandon builder. So I think the conclusion is that the code behind the study is needed, but it's more appropriate to spend time on your own amateur projects.

In other words, if you plan to go on long term, the code is unavoidable, but only for the amateur play, use storyboard bar.

(3) Storyboard, NIB files and code to achieve the advantages and disadvantages of the UI

It's a good idea to use a simple project that someone has developed.

Well, the bird thought about it. For beginners who want to get into the line, the main focus is on code learning, with storyboard as an aid to better understand view controllers, views, controls, and various jumps.

As to what code Easy version management, easy to multi-person collaborative development, easy to find and modify maintenance and so on, these temporary regardless of it, the reason is only one: learn what to learn, after all, is to go into the line!

"iOS Dev-5" storyboard or a hard-pressed stack of code? Look at the words of the family