My work with the iPhone SDK continues, working on three clients to our backend services at the moment. I'm very much looking forward to blogging about this as it's cleared at work. But as you probably have noticed from my posts, working locally and synchronizing with the back-end is what I believe most iPhone applications are about. Do quick and stuff you need to remember on the iPhone, work out the details from your computer, keep everything in sync. That's why I'm excited about Google's data integration. That's why I'm excited about integrating SQLite. That's why I spend a lot of time working with SOAP integration. And of course, it's all good fun. I'm tempted to say that working with a back-end is a lot easier than doing everything local. At least the satisfaction of seeing the work you do on the little screen influencing the real world ...

After asking on the MacRumors forums I was pointed back to FMDB that I had looked at a couple of days ago. FMDB is a Cocoa wrapper for SQLite3. I had a look at it, and after my initial difficulties, I found that I was trying a way to complicated way to use it for my iPhone applications. To add FMDB, simply do the following:

• in XCode in your project window, rightclick your "Classes" and Add -> "New Group", call it FMDB
• drag the files from src in the FMDB package into the new group
• Rightclick Frameworks, Add -> "Existing frameworks", select /Developer/Platforms/Aspen.platform/Developer/SDKs/Aspen1.2.sdk/usr/lib/libsqlite3.dylib ...

Way cool, a composer/musician/LDAP-developer has made Mono run on iPhone. Jailbreaked, by the look of it, looking forward to seeing it compile with the official iPhone SDK as well and a Mono Touch library.

So, two days of implementing ideas, trying stuff out, reading discussions, documentation and watching videos have passed since the iPhone SDK was launched. My dayjob has become developing for the platform, which is great. It's a fun platform to work with and developing for it is quick. I'm really looking forward to Apple delivering those certificates soon so I can try it out on the iPod Touch (no iPhone in Denmark yet).

So that was rant number one, certificates. Why-oh-why do I need them when I do software development? I would also very much like to be able to share my apps with friends, perhaps even beam them wirelessly over to them. And I should be able to do this with a self-signed certificate like with SSL. Self-signed for development, signed by an authority for production, that's a good scheme.

What's up with Bluetooth? ...

After yesterdays iPhone SDK release, my boss agreed that we should spend some time making a client for our apps with it and got me an iPod touch to work with. Good stuff. The SDK and tutorials seem very good. Strange thing that many of the samples don't run in the Aspen Simulator. Especially since I need a certificate to be able to deploy them on the iPod, and that certificate is right now not available outside the US. I didn't expect to need a certificate to develop, I thought that was just for publishing on iTunes. So not being able to deploy those samples on a device and not being able to run them on the simluator, I'm stuck with guessing. I hope that is soon resolved as developing for it is good fun.