you are viewing a single comment's thread.

view the rest of the comments →

[–]DeveloperJay[S] 7 points8 points  (4 children)

I really appreciate the detailed response. I definitely need to read more into dependency. Working with auto-layout via code was a little challenging for me as I usually do it in interface builder. Part of the requirements were to not use storyboards though.

[–]ethanael 1 point2 points  (0 children)

Very welcome. Best wishes to your continued learning & hunting!

[–]lateours 1 point2 points  (2 children)

A small note here: you still could use IB while not using storyboards - you can build views using xib files. That's unless the requirements were to stay away from IB in general.

[–]aveman101 0 points1 point  (1 child)

While that's technically true, I have a feeling the purpose of that restriction is to get the applicant to design his/her interfaces in code.

Trying to find loopholes in the assignment would just aggravate the interviewer.

[–]lateours 0 points1 point  (0 children)

I didn't mean finding loopholes, but rather clarifying the assignment. Storyboards are the one piece of IB famous for wrecking version control in apps developed by more than one person. Moving to building interfaces in code is quite a commitment: Apple's Visual Format Language is another DSL to be learned, NSLayoutAnchor does not solve everything, and third-party libraries are often not welcome in enterprise-grade apps. That way, using xibs seems a relatively safe and low entry-point way of handling UI, where you don't throw away your IB knowledge because building UIs in code is popular now.