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: Bill Cheeseman <email@hidden>
- Date: Sun, 25 Feb 2007 16:32:14 -0500
- Thread-topic: Implications of changing an app's bundle identifier
on 2007-02-25 3:40 PM, Uli Kusterer at email@hidden wrote:
> 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.
Speaking as a lawyer with considerable intellectual property law experience,
I'm just that little bit more comfortable if I change the bundle identifier
once somebody else owns the company name and domain. Although it is pretty
well hidden from the average user, you have to anticipate that the better
plaintiff's lawyers might find it in the Info.plist file and make a big deal
out of it in front of the jury. I know I would.... (You'd be amazed how many
lawyers go to the trouble of removing metadata from digital photos before
they use them in court cases, simply to prevent the other side from
double-checking things like when and where the photo was taken, what the
lens zoom setting was, and the like.)
But more to the point, yes, my earlier remarks glossed over the difference
between the bundle identifier and the conventional Mac OS X way of naming
preferences files using the same reverse-domain naming. Preference file
names are just a little bit more available to the average user than the
bundle identifier. It seems as though NSUserDefaults makes some assumptions
about use of the bundle identifier to name preferences files, and I do want
to be able to distinguish between the preferences files of the old and the
new applications because of the downgrade issue discussed previously. I've
posted my logic and some code in another message, making use of the two
different domain names for this purpose. If I've got it right, it's
sufficiently easy to do that I don't see why not.
Bill Cheeseman
_______________________________________________
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