Recap
We’ve covered a lot of ground in this chapter. The main goal was to introduce you to the different ways you need to begin thinking about objects and data in an iOS app, compared to your experiences with JavaScript. You have certainly seen some small similarities between JavaScript and Objective-C, such as assignment operators and notions of methods that optionally return values. But you have also seen that an iPhone or iPad app is largely a collection of class files, assisted by Interface Builder nib files (if you choose to go that way). Classes rule the day, and the basic structure of defining objects (through classes) entails writing more code, some of which will seem redundant based on your interpreted language experience. If you make a change to an instance variable name or method argument structure, you have to code the changes in both the header and implementation files.
The significance of the class structure should come into more focus in the next chapter. There, you’ll see how you’ll need to change your top-to-bottom interpretative conceptions to a completely different program execution flow model.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access