Apple has finally achieved its aim of outlawing all Universal Device Identifiers (UDID) in developer applications. As of May 1st, Apple automatically blocked applications which use UDID. Furthermore, any existing apps must use Apple’s Retina displays and the 4” iPhone 5 display.It’s a sign Apple hasn’t had as much success as it wanted with convincing app developers to transition to the newest Apple devices and encouraging them to respect their new stance on privacy.
Apple has warned developers repeatedly about the use of the UDID for tracking. The UDID is a unique code which marks every piece of hardware. Developers often use it for advertising, upgrades, and tracking their customers. It’s also prominent with advertising networks. Apple will now ban developers and apps which use them.
The company has come up with an alternative. It developed the iOS 6 Advertising Identifier. This is a unique number not tied to a specific piece of hardware. The only way to change it is to reset the device. Many advertisers have expressed anger over the alternative, saying it’s a poor option.
In a further blow to advertisers, Apple has implemented a setting to limit ad tracking with the Settings app on the iPhone.
It’s certainly easier for consumers who don’t want to share information about what they’re doing. In making this change, Apple has conformed to the promise it made to the Senate subcommittee. During this 2012 hearing, it promised to be more transparent about issues surrounding privacy and tracking.
Many speculate the move came after a UDID database was released by the AntiSec hacking group. The database had one million UDIDs stored at the time. They claimed they had gained it from a laptop left by an FBI agent, but it still convinced Apple to act quickly.
Regardless of the views of developers, Apple has confirmed every app and developer using the UDID after 1st May will be banned.
How Does it Influence App Makers?
This tracking method has worked well for developers for some time. It doesn’t mean developers have no way of tracking their customers. As long as you’ve adequately prepared yourself for the change, there’s no reason why you should suffer because of this change.
Start by implementing alternative tracking technologies in each of your apps. Since there’s no universal method of tracking, you have to use a mix of technologies. Begin by switching to the IDFA.
IDFA still has its disadvantages. Its main drawback is it only tracks in-app traffic. It can’t track mobile web traffic. UDID could track both of these things. Developers are working around the ban by installing tracking which acts in much the same way as fingerprints. It matches clicks to your map installs and in-app conversions.
Clearly, this isn’t perfect, but it gives you a good idea as to your true traffic levels.
Verify whether you have been integrated with SDK. It should track users accurately without using UDIDs. If you can’t track without UDIDs, switch providers immediately. Choose a different provider who uses a range of tracking solutions. Use Google to get in touch with providers who have successfully made the transition from UDIDs.
Using an updated SDK gives you complete control over your use of UDIDs. Some providers integrated non-UDID versions prior to the ban. It had an option where you could keep UDIDs running until the ban came into force. If you haven’t updated to the latest version, update immediately to remove the use of UDIDs. Check the settings to make sure it’s switched off.
Neither of these tracking options is ideal. As of this writing, developers are still searching for alternative ways of getting the same high quality tracking returns as UDIDs offered.
John Kravz is a representative of Vpn-guru.com. Read more about hidemyass vpn.
