If you plan on loading a game to the App Store via iTunes Connect, budget a lot of time for additional configurations and sandbox testing. I had hoped you could programmatically invoke the leaderboard and achievements but, they have to be predefined with icons, descriptions, titles, etc. This level of configuration is what makes the iTunes App Store what it is, but it is just one more task that can seem very tedious when trying to push out even the most bare bones app. I now know why game development takes so many team members.
Today’s tip is short and sweet. I recently subscribed to Objc.io, which is self-described “periodical about best practices and advanced techniques in Objective-C.” In their very first issue they discuss view controllers and how they almost inherently become unwieldy beats within our application code. The first issue focuses on ideas, designs, and best practices for keeping view controllers light and flexible and moving your reusable code into a, such as, “myApplication.h/.m” class that can handle most of your application’s heavy lifting.
I learned two valuable lessons when working with Xcode projects this week. A lot of times developers will create Proof of Concept (POC) projects wherein they will not use all of the potential features offered; in this case Core Data in Xcode. If you’re lucky, you may find you have hit on something and want to expand the capabilities of a project. You can often just import a framework from the Project Overview screen in Xcode like to the right here. For most frameworks, merely adding the framework and including the reference to it in the header file of your desired class is enough. For Core Data, you have to go a bit further than this.