I think that many fledgling people first create UI with storyboard.
You can see it at a glance, it's intuitive, and you feel it's ** easy to understand **.
That's right, the advantage of Storyboard is that it's intuitive.
However, as we develop it, there are major disadvantages to such Storyboard.
I notice.
Anyway, the storyboard is heavy. If you put all the screens together in one storyboard, it may get stuck just by opening it. Therefore, some use the storyboard reference or use the library to split the storyboard.
It's not coding-based, so it's over when you have a conflict. Either implementation will disappear. Also, it is difficult to debug because it does not throw an error when debugging. Furthermore, it cannot be reviewed on Github or sourcetree. It can be said that the management cost is quite high.
In SwiftUI, it is a coding-based UI drawing. Is this from the lesson of storyboard? The Swift UI, which allows you to check and operate the preview without building with the Canvas function, is epoch-making. It can be said that this also means a break from the storyboard.
What did you think. Of course, storyboards may be much more convenient in some cases, but Basically, I think you should get used to drawing the UI by coding.
Recommended Posts