Re: Implications of changing an app's bundle identifier
Re: Implications of changing an app's bundle identifier
- Subject: Re: Implications of changing an app's bundle identifier
- From: Uli Kusterer <email@hidden>
- Date: Sun, 25 Feb 2007 21:40:38 +0100
Am 24.02.2007 um 21:17 schrieb Bill Cheeseman:
My products have used a bundle identifier in the Info.plist file that
includes the company's name, in compliance with standard Mac OS X
protocol.
Now, however, for good and sufficient business reasons, it is
necessary to
change the bundle identifier in the next versions of the products.
Keep in mind that the bundle identifier is an internal unique
identifier that, ideally, is never seen by any users. So, if your
company name just changed, I would just leave the bundle ID the same.
It's not really worth the hassle and potentially annoying your users,
and unless you're "forking" the application, it's unlikely that
someone will ship a product with the old company name and the same
application name.
The reason why one uses the company name is simply because that
makes it easy to segment the namespace in a way that also reflects
organizational structures. In English: If you use the name of *your*
company, chances are you know enough other people there to be able to
negotiate with them who gets to use what app name and what bundle ID,
thus avoiding collisions. Also, by necessity company names are
already fairly unique themselves and trademark law also helps keep it
that way.
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden