Apple v Google: a Contrast in Priorities

Apple v Google: a Contrast in Priorities Advertising Two related stories this week remind us just how Google and Apple see their priorities Where one company is focused on users, the other is focused on serving those users to advertisers.

On the one hand, we have Apple and the ad blocking features of iOS 9. Users are going to have the option of installing a content blocking app from iTunes, and filtering out adverts and tracking scripts.

And this week we learned that Apple also provided an option to reload a page with all the ads active (just in case you forgot what you were missing):

One of the nice perks of Safari in iOS 9 is that, even if you have blockers installed, you can long-press the reload button to reload the site with nothing blocked.

So not only is ad blocking strictly a user option, Apple is also giving users the options of seeing the ads. Nifty.

Google, on the other hand, chose this week to give app developers a tip on how to bypass Apple's security.

Update: It's been pointed out to me that Google was merely forwarding a detail Apple had in its own tech notes for iOS9.  Headdesk.

iOS 9 requires that adverts be served with HTTPS, and not simple HTTP. That's going to increase a user's security, but Google guessed that not all developers would adapt in time. And that's why Google shared a snippet of code that developers could use to bypass the security.

This won't bypass the ad blocking software, but it does subvert one of the underlying reasons we use ad blockers: security.

And it also shows us just where Google's priorities lie.

Google might proclaim that it values the new security standards, but that's just a fig  leaf. Actions speak louder than words, and in this case Google's actions show that it values making money off of a user so much that it is willing to compromise a user's security to do so.

Google isn't quite as malevolent as Lenovo with its ad-injecting malware, but Google comes close - too close, in fact, to honor its motto of "Don't be evil".

image by GotCredit

Nate Hoffelder

View posts by Nate Hoffelder
Nate Hoffelder is the founder and editor of The Digital Reader: He's here to chew bubble gum and fix broken websites, and he is all out of bubble gum. He has been blogging about indie authors since 2010 while learning new tech skills at the drop of a hat. He fixes author sites, and shares what he learns on The Digital Reader's blog. In his spare time, he fosters dogs for A Forever Home, a local rescue group.

3 Comments

  1. Chris Meadows28 August, 2015

    Uh, Nate? Did you see the “Update” note at the bottom where Google makes it clear they’re just passing along advice from Apple themselves on how to deal with ATS standards? Seriously, this is right there under “Exceptions” in Apple’s tech note.

    Reply
    1. Nate Hoffelder28 August, 2015

      No, I didn’t. Facepalm.

      Reply
  2. Chris Meadows28 August, 2015

    As a friend of mine who called my attention to that pointed out, you could have chosen to focus instead on the point that Apple is building an ad-blocker into its OS, while Google won’t allow them on its Android app store, so they won’t let you install ad-blockers unless you throw the big red switch and open up unverified app stores.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scroll to top
%d bloggers like this: