Most professional applications are web services extensions.  iPhone applications require specific data streams, different from those sent to browsers. Yet rarely do your server teams have the mobile focus to produce appropriate streams for your own app. This either results in delays in delivering C4M specified data or worse, the app is delivered unresponsive and bandwidth hungry.

The bottom line is that iPhone application programming doesn't stop with the device, server coding is involved. Most of the times, the workload is light and C4M teams will ready efficient APIs in a matter of days. And for your budget the operation is neutral: time spent preparing streams server side is gained on dealing with bulgy XML docs application side.

This is why C4M has nurtured an in house a server team that it considers a natural part of its iPhone application work force.