Well, the time has come to publish my company’s first iPhone application. It is intended to be an exploration (rather than a big hit). I’ve worked a couple of days with it, and my designer colleague did a good job in these days, so we’ll send the app for a review to Apple, and then wait anxiously for the results.
This is the first reason I stopped publishing learning materials for MCP exams. The second reason is that I must study for my university exams (which is a very painful thing to do). The last is that I’m working ten hours a day in the family business, we are in the middle of a big project. But the posts will continue, as soon as I finished my semester (or maybe before that, I’d love to start learning WCF…).
But back to the app. From a programmatically point of view, this wasn’t a big challenge, just a quiz with some nice features, such as Facebook integration and communication with a .NET web application, via SOAP (I couldn’t restrict myself). The hard part was Objective-C and the Cocoa Framework. I worked (and studied) with .NET for so long that I tried to solve every problem in the .NET way, tried to follow best practices, etc. But Objective-C is much closer to C++ than it is to C#, so I have a great time allocating, initializing and releasing objects. Also, I had troubles with the exception-handling (especially the information provided) in .NET, but in Objective-C, that was a nightmare. App crashes with EXEC_BAD_ACCESS, and nothing else, give me moments of pleasure. But this the result of my own inexperience and lack of knowledge, nothing else. So I came up with the idea to learn something lower level than the .NET Framework, maybe C. That would help me a lot I think.
Except these issues, it was a pleasure to program against the iPhone, and I’m quite sure that this wasn’t the last time (there will be apps until the price of the Mac comes back, or I’ll be killed, I suppose). I’ll let you know when Apple approves the application.