It is very customary for people to start enthusiastically into the world of iOS developers but gets instantly overwhelmed by an unexpected extensive amount of tools and technologies to acquire. They come beyond Xcode and Objective-C but also even in that first day, hit terms like Cocoa Touch and Frameworks and Release Pools, Memory Management, MVC, Delegation, Target Action, Certificates, and Provisioning. Moreover, it’s considerably tight to estimate out what’s the appropriate order. How should you learn this? How does this support each other? What should you do first? So, while you absolutely can learn it by submitting yourself into these cases randomly, what I find a bit more useful is to address your app development on the iPhone as being guarded by four pillars.
Four areas of information that you need to have to establish the applications that you want. The first pillar is the Tools. You’ll begin with Xcode and the iPhone and iPad simulator. Later on, you’ll see another program called Instruments. You already have this. It’s included in the developer tools, and it will let you view and analyze various diagnostic information about how well your app is performing. The second pillar is the language. You need to know Objective-C but also the coding patterns that we use inside like MVC and delegation and the supporting frameworks that are available, all the pre-written code that Apple has provided to make our app development more accessible.
Now the next one is the design. Not just making your application look good, but how to flow through multiple screens. How to determine the particular kind of user interface components to generate the appropriate kind of application. Because this is a very formal environment. Using user interface elements the wrong way can cause your app to be rejected from the app store. We’ll see it some great documentation like the Apple human interface guidelines or Apple HIG documents that can give us great pointers for what we should be used in certain circumstances. Moreover, there’s much thought that’s gone into this.
Moreover, just as important in all of this is the overall process, you’re in a very formal environment now, working with Apple rules. You saw that even when creating the first project, Apple expected some exact details for naming information. Well, there’s that same formality for testing your applications, provisioning your devices, submitting to the app store. You need to know the process to follow. So when you keep this in mind that all these pillars support your app development company, you can avoid getting buried in just one specific area. Stay conscious of the whole process.
This is not just about Objective-C, it’s not just about Xcode, it’s not just about dragging and dropping random user interface elements onto a screen. Moreover, as you learn more and more as we go through this course, kind of understanding where the different pieces fit into this.