Ad Hoc IPhone Distribution and CI (pt 1)

What I need to do

1. Build our IPhone App
2. Build it using Continuous Integration (Hudson Rocks)
3. Follow Agile, deploy often to customers to get feedback and to keep them as up to date as possible.

Our customers don’t typically use a portal (like app store) to find us, we use ‘traditional’ sales.

Which deployment?

App Store?

We’ll need the app store, at some point.

The oft discussed turnaround time for App Store deploys is sounding worrying. It doesn’t really fit with Agile development… does it?

Ad Hoc

Ad Hoc is a nightmare with a CI server. You need to update your provisioning profile on the CI server and it’s not simple. I’ve worked out theoretically how to make the process speedier, but am yet to implement. More on this in part 2.

We need Ad Hoc because of how the app store approach fails us. That is, it’s a better (not necessarily good) way to be Agile.

Enterprise

Enterprise just doesn’t apply to us. It probably won’t to you either. If all our customers were enterprise we could suggest they all use this license, but they aren’t. Not even close.