The video tutorial below shows how to use the performance tools that come with the Apple development kit to find memory leaks in Cocoa and Cocoa Touch code.

I enjoy writing applications for the iPhone, not because I like Objective-C or Xcode but I really like seeing the application on my phone. This means I have to endure the other two. Being fairly new to the Cocoa and Objective-C world I spend a fair amount of time in documentation. This is always a mundane task but Xcode just makes it a completely bad experience. Recently I ran across an application that improves the task. The application is called AppKiDo.

Microsoft recently announced a new SDK for Cocoa and Cocoa touch applications that would easily allow developers to perform various searches using their new Bing "decision" engine. As a person actively working on iPhone applications, this is something I had to try out. This tutorial will introduce you to the Bing SDK and how to use it to build a simple web search application.

The iPhone has plenty of neat features to use, one of the more recent features is using the built in Google Maps support. The specific SDK library we are looking at is MapKit.

Most of the time, your iPhone application data storage needs will be taken care of by simple object serialization and flat file storage. However, there comes a point when that type of storage just won't work anymore - when you start storing thousands or tens of thousands of objects. Apple recognized that fact, and so gave app developers the ability to use SQLite inside their applications.

Last week we received an email requesting a tutorial that covers playing sounds on the iPhone. I started digging into the documentation and it appears the SDK offers two choices. Using the AV Foundation Framework, which makes it very easy, or using Audio Queue Services, which is about the most difficult thing in the world. The person in the email mentioned buffers and such, so it is clear that this person wanted a tutorial covering Audio Queue Services. I'll be getting to a tutorial on that in the near future, but for now I'm going to create a simple audio player that should cover most people's needs using the AV Foundation Framework.

One of the great features in the iPhone is the ability to get your location, which is available on all of the versions with the 1st edition relying on cell tower triangulation, the rest using built in GPS. As a developer, I can think of endless possibilities for using this information, but the first step is getting a hold of the information. This tutorial is going to cover how to get location data using the iPhone SDK.

The video tutorial below covers how to create an application without using a nib file. This is a quick tutorial, if you have any question feel free to leave a comment.

Twitter is on everyone's hot list right now. I enjoy it myself and we have one for Switch On The Code. Anyway, being the Month of iPhone, I decided to do something a little different with it. Twitter Counter is a service that tracks how many followers you have but takes it a step further - they will estimate future number of followers using historical data. Basically stats for tracking Twitter followers. This tutorial is going to show how to use the Twitter Counter API to get follower information on any account.

So you are making an application for the iPhone, eh? One thing that you might not realize right off the bat is that an iPhone app, like your regular old computer applications, has the potential to be sold in upwards of 80 countries (according to good ol' wikipedia). This means that if you really want to take advantage of the market that the iPhone app store presents to you, you will have to localize your application. Nobody really likes localization - it is just one of those things in software development that has to get done anyway. Fortunately, Xcode and the iPhone SDK keep the pain level down to a minimum.