Apple Begins Rejecting Apps for Using the Unique Device Identifier (UDID)
As the name suggests, the UDID is a unique identifier for every iOS device. It's tied specifically to the hardware and can't be changed by the user. Apple had previously warned developers with the introduction of iOS 5 that the use of the UDID was deprecated and would be phased out. The sudden rejections, however, have caught some developers off guard:
“Everyone’s scrambling to get something into place,” said Victor Rubba, chief executive of Fluik, a Canadian developer that makes games like Office Jerk and Plumber Crack. “We’re trying to be proactive and we’ve already moved to an alternative scheme.” Rubba said he isn’t sending any updates until he sees how the situation shakes out in the next few days.The reason for the phasing out of UDIDs from developer use is due to increased pressure on Apple due to the privacy implications. Apple and several App developers have been sued over the use of the UDID to track users across different apps. While the UDID doesn't specifically identify a user, the sharing of UDIDs across ad networks and apps can help piece together a valuable picture of activity and interests of the user of a specific device. Apple seems to be requiring apps to generate their own unique identifiers for each installation to avoid this ability to share such information across apps.
Top Rated Comments
(View all):rolleyes:
"We're trying to be proactive..."
Really? iOS 5 and Apple's warning have been out there for quite a while now. Seems at lot more reactive to me.
yep, there are non ad uses for it.
The tough part is that if Apple doesn't allow a well defined transition period for it (where devs can still use the udid), users' apps that do use it for something like above (connecting a device to high scores, storage of preferences / data) will have their data lost on the next app update.
arn
If the app has proper customer service, they can do a simple score-transfer. The user would have to prove that they upgraded their device by either logging into their old or new device with their username. If the old device broke, it becomes a little harder to prove the identity of players, but IPs can also prove useful.
give me a better way that doesn't require registration.
arn
As I understand it, the problem with using the UDID is that it doesn't track your scores across devices. If you upgrade to a new iPhone, say goodbye to your highscores.
A better idea could be to just do it through Game Center, or being able to sync highscores to iCloud. You have to sign up if you want to use it for other things, anyways.
give me a better way that doesn't require registration.
arn
I think this is why Game Center has seen such popularity. No registration is needed assuming you already registered an Apple ID. Registration may not be the easiest method, but it clearly is the best in terms of flexibility, especially when the login is device-wide.
Looks like Apple not only gave enough advanced notice, but also told developers exactly what to do to workaround the problem.
Another article that only serves to exemplify the laziness, self-righteousness, and extreme sense of entitlement of some people.
For many developers, this is a very scary thing. For instance, this goes beyond just advertisers. For online games, UDIDs are used to identify specific users, to ensure that they don't get mixed up and that scores (if the game has scores) are being recorded properly. I know a couple apps that use UDIDs for this purpose.
I am not trying to be argumentative here. Just trying to illustrate that these problems could have been avoided with a little more thought on the developers side.
Of course, but we're not building an app here.
You just asked for why you would use UDID, and I gave you probably one of the biggest reasons. I'm not saying you would use it exclusively. Of course, you'd offer user registration too.
But, my point is. If you built a game using that technique (anonymous UDID high scores), all your unregistered users will lose their high scores on their next update.
arn
[ Read All Comments ]
