Use or not MainStoryBoard Swift

Question

Use or not MainStoryBoard Swift

Navigation

#1 by (1 votes)
#2 by (1 votes)

0

I started my studies in Swift , I am currently studying Swift 4 , but I came across a doubt, which I believe many people who are starting also have (or not).

In the course I'm seeing, the teacher teaches us how to develop apps using the famous Drag and Drop of MainStoryBoard .

But in another series (gringo), I saw the teacher teaching without using MainStoryBoard , right away, he excludes this file, and everything he does (literally) is in the code, from the constraints to each element of the app.

I've come to doubt, what is the right way to develop apps, what are my limitations using MainStoryBoard ?

swift swift-3

asked by anonymous 02.10.2017 / 14:57

2 answers

Delete result with JS and PHP Add a scroll bar in a DIV

score 1 · Answer 1

IMO This issue is more than a matter of preference.

Using Storyboard really makes certain options and settings simpler and more visual, but will be best used in smaller, simpler projects where there is only one developer.

For systems with modeling architectures, larger projects and more developers, I think using xib files will be more appropriate because it respects the modularity and each feature and does not waste time with merge's of storyboards.

score 1 · Answer 2

For me to use the .storyboard limits me greatly, drag and drop at the beginning until it goes, because you need to know how the components work on the screen, how the constraints work etc. However, as you evolve, you will feel the need to make some changes to the components and these changes can only be made by code. The cool thing to do via code is that you'll understand how the component will actually behave on the screen, without having to do a force unwrapped when you drag and drop a button from the storyboard to VC. >