4 ms·
This is exactly how you should build your first app. Using Interface Builder will make you a permanent novice.
by andrewljohnson 14y ago
This is exactly how you should build your first app.
Using Interface Builder will make you a permanent novice.
- M4v3R 14y agoDo you really think that reinvent the wheel is better than using technology that a vendor gives you? Do you really think that folks at Apple make all their interfaces in code? Tip: Probably every feature that was added in Xcode was added because Apple engineers benefited from it.
- deleted 14y ago[deleted]
- andrewljohnson 14y agoI'm not reinventing any wheels - I'm choosing not to use a square wheel, and instead just write the code. Tip: It works for us and many other developers of high-ranking iOS apps.
- myko 14y agoWhy? I've used nibs/IB pretty extensively since I started doing iOS development full time (about 2 years), maybe I'm still a novice and don't realize it but anytime I need to do anything complicated within a layout I can manipulate it programmatically. The only objectively bad thing about IB is that the generated files are impossible to merge. It would be much nicer if they were more like Android's human readable xmls.
- andrewljohnson 14y agoPerhaps you know how things are going on under the hood, but I have worked with many iOS developers, and the ones who love InterFace Builder have been clueless. They don't understand the actual view hierarchy, autoresizing masks, and god forbid you need an IB-guy to dabble in CoreGraphics drawing.