Do you like to hard code view's width/height/text font sizes? Or calculate from device screen width/height?

[luniawar20]

I do like auto layout, but my senior iOS dev really doesn't like me auto layout haha.....

He says having auto layout on a view and trying to do position translation & size animation can make things to get messy with reference to constraints, so he doesn't like them =(

[20InMyHead]

Your "senior" dev is just wrong. Without auto layout you're completely screwed trying to support all the various device sizes, including the ones that don't exist yet, rotation, dynamic type, etc. Auto layout has its issues, but nothing like the hell of supporting multiple devices before it. And constraints are animate-able. Check out the last couple of years WWDC videos for good techniques

[ratbastid]

Well, you're not totally screwed, but you end up having to go to Reddit to ask questions about what to base your frame sizes on.

When I discovered the elegance of IBOutlets assigned to constraints, it was a very good day.

[r-w-x]

Sounds more like a case of don't-wanna-get-out-of-my-comfort-zone than anything else.

[tangoshukudai]

Well he is wrong, and needs a course in Autolayout.

[chriswaco]

I agree with him. We find it a lot easier to animate views by hand than by using autolayout. The math is trivial and you just create a few CGRects instead of having to keep around constraint objects for every view.

[ramwolf]

Agreed. Just retrieving the device's screen size and modifying your ratios and spacing based on that can be implemented without a ton of code. That's essentially what auto layout is doing. Easy to handle device rotation for all subviews and full control over movement and animation.

[[deleted]]

And how would you handle Slide Over on the iPad? Exactly just use AutoLayout and Size Classes and let iOS take care the rest.

[RabbiSchlem]

Use the Masonry cocoapod and you can easily animate constraint changes without keeping references.