Cartography

There is a quite popular iOS lib for layout with the same name [1], where I always thought this, too. [1] https://github.com/robb/Cartography

For some non-obvious on-point tips regarding binary size and (also importantly) startup speed in complex apps, see ‘Swift with a hundred engineers’ (2016) where Tuomas Artman shared what Uber engineering’s learned from their iOS rewrite[0]. Nit: advocating AutoLayout to me doesn’t seem to compute with avoiding libraries. Is it actually feasible to use AutoLayout in a larger-scale app without something like Cartography[1]? Interface Builder still feels quite buggy in this regard. [0] HN discussion: https://news.ycombinator.com/item?id=14207752 [1] https://github.com/robb/Cartography

IB is ok for getting started but it will eventually hold you back. If you get to the point where you feel like you're fighting it as much as using it then look into doing your layouts in code with one of these libraries: https://github.com/SnapKit/SnapKit https://github.com/robb/Cartography It may take a little getting used to but, especially for the kind of dynamic apps people want to build today, it will save you a lot of time and headaches in the end. Also make sure you get your head around UIStackView. It's a little tricky to learn at first but makes a lot of common layout problems easier to solve. Also, start using this library ASAP: https://github.com/mac-cain13/R.swift

And cartography, which is my preference: https://github.com/robb/Cartography constrain(button1, button2) { button1, button2 in button1.right == button2.left - 12 }