@adamkmccarthy

When not writing iPhone apps, tinkering with his mac, and babysitting the mac mini Adam is a keen sailor who has steered some very famous boats indeed. He also races mountain bikes, and is a staunch Munster supporter.

Adam is a Cork man, so I for one am looking forward to the O2 jersey meeting the Vodafone Jersey in the Summer!
Do join me in wishing Adam all the best for his new role.
Dermot.

• Waiter taking orders at a table
• UPS Delivery guy
• Gas man coming to take a reading
• Charity worker – getting sign-ups but also using the multimedia capabilities to show where the donations are going to good work

etc. etc.

Right now, there are three ways to distribute iPhone apps:

1. The App Store – This is designed for general purpose apps that anyone may want to use
2. Enterprise Distribution – This is designed for “in house” only apps. This is where a company wants to supply apps for their staff use only, and not put them on the app store.
3. Ad Hoc Distribution – This is where a developer can distribute the apps privately to a group of people. It is primarily aimed at developers who want to get real-world feedback before really releasing the app through 1 or 2 above

When we consider that some of the app ideas (e.g. the waiter concept) is really an “in house” app. But each of the distribution mechanisms has its drawbacks:

• You may not want to put it in the app store, because it only works with your restaurant management system.
• You’ll not qualify for Enterprise distribution, because Apple restricts this to companies of 500 employees or more
• You could use ad-hoc, but this does take a fair bit of management for the developer. The developer needs to know each and every device id that the app will be installed on (and has a limit of 100 slots per year; which cannot be re-used during the year).

None of these are insurmountable, but they are niggles. Basically, there isn’t a simple way to distribute “private” apps. This is by design; It is a commercial decision by Apple. If there was a way, people would use it to bypass the app store (to avoid the apple cut), so its unlikely to change.

One thing it could lead to is an explosion of “new” software as a service offerings. Consider the “menu ordering” SAAS system; The restaurant signs up online, and enters their menu details. The Menu Ordering App is sold through the app store, and the restaurant simply enters their restaurant id and password when they use the app for the first time. This could work, but its a big education job to explain SAAS to restaurant owners.

I think all of those who want to put iPads into their businesses will find the distribution options confusing and consider it a hinderance.

That’s a challenge for us developers.

You’re reading the tapadoo blog. Did you know that as well as publishing our own applications, we offer iPhone development services and consultancy? If you have an idea, project or something you think we can help you with, please get in touch through our contact page.