Iphone app distribution questions

Question

My app is a very simple table drill down within a tab bar. From recommendations on this list I'd like to keep my data (the catalog - 250 items of 6 attributes) in a plist.
I can't give the user the ability to edit or add to the catalog/plist. But the catalog will get updated on the order of 3-4 times per year.
What's the simplest way to keep all the users' catalogs up-to-date? My first guess is just to reissue the app package with the updated plist built in. Thoughts or suggestions?
As for the initial distribution, I'm selling the app to a manufacturer that wants their 5000 dealers to have access at no charge. I'm guessing that means putting it on iTunes as a free app. And as above, resubmitting it to the iTunes store whenever I have an updated catalog. Thoughts or suggestions?
This is my first foray into actually finishing an app and trying to distribute it.
Thanks.
-Phil

Answer 1

Not sure what you mean by 'a remote based data style app'. Is that the same as the server based solution mentioned above?
Oopss, sorry, yes. Server/remote versus local, on the device. It would be an elegant solution, with its own benefits, of course. I think you appreciate the extra effort tho.
If you need an example of how easy it can be to get into trouble depending on a simple upgrade solution...let me outline a true example.
I know of an outfit that paid handsomely/$$$$ to have a full page color ad appear in a major industry print magazine about an upgrade to an existing app that was in big demand, only to have the ad come out nearly three weeks before the app was approved. When the ad was placed, approvals were running between 7 & 10 days. By the time their print ad hit the streets, approvals had slowed to more than 3 weeks. Clearly they failed to count on a lengthy approval process.
They spent far too much time fending off rants on their forums, while also finding themselves defenseless against negative reviews in the app store. The magazine ad promised one thing, but what was being downloaded/purchased was another.
When the app was finally released, they didn't mess with the original app release date and choose instead to forego any visibility an updated release date would have bought them.
This happened to a competitor, and their timing loss was my coincidental gain. My app made it into the store right after their print ad surfaced and before their app was approved. Cha...ching for me.
So again, while pushing an upgraded app is a good plan if you pay attention, don't get too comfortable relying on a specific release date and don't let a client talk you into putting your neck into that particular noose.