iOS basically has two ways, one is the IB WYSIWYG form of Storyboard; the other is the pure code form. Android is slightly better. In addition to WYSIWYG and pure code, it can also be achieved by editing XML. The use of XML for configuration in Android is most similar to the Web front-end operation of layout, CSS, etc. Don’t ask why iOS can’t be configured this way. I can only say that the XML source code of iOS IB is really impossible to read and operate.
Now Apple is increasingly advocating the use of storyboard development. Generally speaking, it is recommended to use storyboard for small projects developed by individuals For large projects developed through teamwork, multiple storyboards/codes can be used for development
The autolayout adaptation in the storyboard personally feels more intuitive than the code
iOS basically has two ways, one is the IB WYSIWYG form of Storyboard; the other is the pure code form.
Android is slightly better. In addition to WYSIWYG and pure code, it can also be achieved by editing XML.
The use of XML for configuration in Android is most similar to the Web front-end operation of layout, CSS, etc.
Don’t ask why iOS can’t be configured this way. I can only say that the XML source code of iOS IB is really impossible to read and operate.
Now Apple is increasingly advocating the use of storyboard development. Generally speaking, it is recommended to use storyboard for small projects developed by individuals
For large projects developed through teamwork, multiple storyboards/codes can be used for development
The autolayout adaptation in the storyboard personally feels more intuitive than the code
It depends on the situation, storyboard is more suitable and does not require too much error information