Agile Development Notes on iPhone Development

As I prepare/continue to build my first two iPhone applications (more later on what they do), I have been researching ways to bring the world of Agile Development that is common on .NET to iPhone development. Specifically, I have interest in assuring I can apply the following concepts on my project from a technical perspective (more on the project management side using BaseCamp, Beanstalk and other integrated cloud-based online tools later as well):

• Unit Testing. This is essential to ensure correctness in implementation at the earliest possible point in the development cycle, where making corrections is the cheapest.
• Continuous Integration. Being able to build a project–especially one that has client and server sides as most non-trivial iPhone applications will–while ensuring that unit tests are included in the build cycle is a core concept in a true Agile Development project.

I have found two blog entries that provide good information on how to approach these issues in iPhone development:

Unit Testing

This documentation from Apple on unit testing provides good information on how to set up an iPhone project. Combined with my previous post covering unit testing, most information has been gathered.

Continuous Integration

I have not found a lot on how to do continuous integration in iPhone development, but I did come across one interesting article by Jeffrey Fredrick that explained how to use Cruise Control on Xcode projects.

Coming next…

Upcoming blog posts will cover how to build static libraries for iPhone that allow you to share code across projects, leveraging and extending the new UXKit iPhone static library that replaces Three20, which was developed by Joe Hewitt, the developer of the Facebook iPhone application, and my experiences building intuitive iPhone user interfaces.