New iPhone Dev Agreement Bans the Use of Third-Party Analytics and Services
erickerr.com
erickerr.com
Apple is changing the rules half way through the game, to the benefit of nobody.
I can't think of a developer OR end user who will be better off as a result of this decision. It's an innovation stifler and I can't understand why they are doing it.
This kills location aware 3rd party advertising.
As the article also says, looks like this will wipe out SimpleGeo. A sad day.
Apple wanted to buy Admob, but Google got them instead. This change will prevent Admob ads from being well targeted on iPhone, and will prop up their (assumed to be upcoming) rebranded Quattro mobile ads.
This smacks of anti-competitive practices. (That is, assuming Quattro ads are allowed to use location aware targeting.)
You don't need to believe me though, here: http://en.wikipedia.org/wiki/Anti-competitive_practices (We can /all/ trust wikipedia, right?) "Barriers to entry" is relevant.
The point I was trying to make was: If we switched this around, and Microsoft had the number one smartphone, and they did something like this, regulators (though you're right, probably not American ones) would have them bent over a table.
This change of the rules makes a ton of sense; with location-aware backgrounding (applications waking up and getting a notice when you change locations), it would be very easy for an agency to track where you're going and in turn sell it to someone else to make a quick buck.
Hmm.
Even you admit as much by suggesting they are removing half the product.
However, if you're a small firm that might be struggling to survive and is somewhat lacking in the morals department ("Is it illegal? No? Then why not? We need the money."), that same money looks far more attractive.
Apple is benefitting. Apple is right to look out for their own interests - they should behave in ways that are good for them, long-term. If you think Apple's actions aren't good for it, fine, but remember that you don't have all the information they do.
If customers don't like Apple's policies, they are free to competitor's product. If developers don't like Apple's policies, they are free to develop for another platform.
I love Apple's products, and I'm going to continue using and buying them.
The second one doesn't prevent analytics. Device Data is a keyword in the contract…
"Device Data" means data or information regarding the characteristics or usage of a particular device, including but not limited to UDID, crash logs, OS version, carrier name, hardware model, installed applications and application usage data.
… so you can't provide a vector for a third party, not bound by your agreement to respect the user's privacy, to loot the device of useful information. Good! You are allowed to collect and use this data, you just have to respect applicable privacy laws and handle notice and consent according to the contract.
The key is, you can't bind some random analytics firm. If you include code that dumps that out to a third party firm they are free to do whatever they want.
So create a UUID the first time you run, send only that to the analytics firm. Leave the Device Data alone. I suspect this would pass, though it is possible it would fail under the "application usage data" section.
One could imagine some extreme interpretation where Apple is trying to prevent any information about which apps are installed being divulged to anyone, but there are so many unaddressed vectors (e.g. loading an ad from an ad server) that it seems unlikely.
At what point do all these restrictions start becoming truly anti-competitive? Locking out 3rd party tools and services in favor of in-house products, and this one now including the actual revenue-generating ones.
If you start to view the App Store as a collection of markets (e.g. for development tools, application niches, ancillary services like ads, analytics, web services, etc), rather than just a vendor-specific platform, where Apple's own products compete with other vendors', the analogies to Microsoft are becoming clearer:
- iPhone OS/App Store => Windows
Markets analogous to Internet Explorer vs. Opera/Firefox:
- iAd vs AdMob
- iBooks vs Kindle (an example where they're actually allowing competition!)
- Phone.app vs Google Voice
- MobileSafari vs Opera/FF
- ObjC runtime vs Flash runtime (this one stretches it a bit, but not that far)
Whereas MS's anti-competitive actions involved threatening OEMs, Apple is exercising actual contractual control over what Apps/services can participate in the market, Period. That should certainly qualify as anti-competitive behavior.
Ad companies are, at their core, analytics companies. By understanding your audience, you serve higher-potency ads, which means you can charge more for their placement, and developers have a higher incentive to use them. Companies like Google and AdMob are analytics companies. By understanding an audience, they can serve relevant content (ads). If they can't understand the audience because collection of metrics is prohibited, then their ability to act as an effective ad provider is massively diminished. Ad revenues dive through the floor and advertisers stop using the platform.
Enter iAd. We can provide you with detailed user analytics and possibly even that coveted location data. Thanks to the new iPhone user agreement, we can even tell you what size underwear a user wears, and how many eggs they had for breakfast. We will give you returns on your ads that you have never before dreamed of. Stop using those wimpy ad companies that can't give you an ROI on their blind-targeted ads to save their life. Use iAd and make more money for us.
It's very difficult to interpret this as anything but a move aimed to invalidate other advertising platforms on the iPhone, in order to make room for iAd as the only viable choice.
Consumers don't write Facebook's checks, companies like Offerpal do: http://www.businessinsider.com/offerpal-coincidentally-repla...
So the differences between Apple's users' data policies and Facebook's become clearer.
Meanwhile, to receive the money, obey the rules. It's simple.
But in the sense you're talking about - if you care about someone buying your "mined personality profile", wouldn't you rather have 10 incomplete profiles out there than 1 really accurate one?
Right now the mobile ad market can work with your approximate age, your gender, your location down to the city level at most, and very high-level interests derived from the site or app you happen to be using at the time. Anything else is too finely grained to sell meaningful volumes of advertising against and therefore not wanted.
I'm guessing people take the reality of the online ad market and falsely assume the mobile market is there as well.
This isn't good for anyone but Apple.
Were I implementing mobile ads, the precise location would stay on the device, and the information sent to the ad server would be city or at least zip level.
Apple is just banning the competition for analysis of said data so they can be the only game in town and "control the user experience" as they like to call it. I wouldn't be surprised if iAd included an analytics dashboard when it's released to the public.
This would affect far more than just ad companies, right? I understand that's probably a motivating factor, but wouldn't this incorporate an even larger subset of third party analytics companies (like Flurry / Pinch Media for example)? The purpose of those companies is not the same purpose as the app itself which rules them out. It could depend on the definition of "User Data" and "Device Data" in the agreement, I suppose.
Third party gaming tools would seem to be safe at least.
"Device Data" means data or information regarding the characteristics or usage of a particular device, including but not limited to UDID, crash logs, OS version, carrier name, hardware model, installed applications and application usage data.
---
Many third-party gaming tools do collect UDID (or a hash derived from the UDID) since this is the only common identifier available across applications, due to sandboxing.
Interpreted liberally, this affects anything that makes an HTTP request to a third-party, since the application name ('application usage data') and the IP address ('user location data') is in the headers.
I guess this is the Admob killer clause? Goes along nicely with the Adobe Flash killer clause...
How long until Apple disbands the senate and declares martial law?