How many iOS developers don't use NIBs, Storyboards, and Constraints?

So far I have never met an iOS developer that builds their UI completely programatically. In the earlier days of iOS, before Auto Layout, I used to design a lot of UI elements and handle positioning via code as I found it more flexible. In the modern day, there are too may screen sizes to cater for to make it beneficial not to use, XIBs, Storyboards and Constraints. One of the main purposes of storyboards and constraints was to allow the seperation of UI design and back end coding. In larger teams, a UI designer should be able to just into the project and make visual changes without having to under stand the code that goes behind it. Image if you was working on a 50 screen app and the client decided that a view (for example, lets call this view a custom navigation bar) that was currently at the top over every screen should be at the bottom. Using storyboards, you would simply, move the view to the bottom, reset the top and bottom element's constraint and setup the new constraints for the custom view (the designer could do this by themselves). If you was doing this via code, 'you' would have to do this, as the designer may not know what to do. You would have to rewrite all of your size code that relied on that custom view being at the top. You do not know where this is visually so you have to remember every bit of code that could be affected throughout your whole application and do some heavy regression testing. This will take a lot longer to do and in the development world, time is money. I honestly would recommend learning to use the UI builders that Apple have made as they will speed up and simplify your development process. You can still do code base UI (and in some cases it is the best way) but make sure there is a valid reason for it. read less