The various benefits of using storyboards in your Xcode projects Some of them might have a good reason, but in general, I think that most are wasting more time than they are saving. So I don’t buy it when developers avoid storyboards. What’s the point of having something like storyboards if using them is equal to not using them? *cough* Especially since Apple does not seem to put much effort in Xcode, to begin with. Think about it: would Apple put a lot of effort into developing and promoting tools that have no apparent benefits? It makes no sense. While I see many benefits, the few problems storyboards create do not seem to me to be enough to eschew them all together. I have researched at length the pros and cons of using storyboards. Mostly though, the excuse I hear is “I am used to doing it this way.” There might sometimes be reasons for doing so. That is why I am surprised when I find iOS developers that still insist on having all the UI in code. But a big part of the code base was UI code, which made the code grow larger than it should have been. The main reason was that everything was written in code, including the user interface.Įven when I had to fix simple bugs, it took me hours to locate the correct code to change. In my opinion, they are just making their life harder than it should be.Ī couple of years ago I worked on a big project for a client together with a 20+ people team.Īfter four months, I still did not know how to move around their code base. ![]() Some iOS developers seem to be opposed to storyboard. Architecting SwiftUI apps with MVC and MVVM GET THE FREE BOOK NOW It does not make sense to have storyboards in Xcode if they are not usefulĪ storyboard outlines the different screens of an app the relationships between them like it happens in storyboards for movies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |