The glib response is to point out the difference between Apple's and Google's business models. Apple makes money by selling devices, Google sells ads (i.e. sells their customers' data to advertisers).

>(i.e. sells their customers' data to advertisers)

They take the ads, and distribute them to their users based on user taste that's their secret sauce. Giving user data to advertisers would be giving away their secrets I think.

> Google sells ads (i.e. sells their customers' data to advertisers).

They sell targeted ads, they do not sell customers' data to advertisers. i.e. Advertisers get to advertise on Google's platforms, but they do not get access to Customer data.

And that Apple is the OEM behind the device that runs their OS, and Google (usually) isn't.

Also that Android only gained the ability to enforce iOS-style fine-grained app permissions (prompting on first use for access to camera, location, etc., instead of a blanket grant at install time) one major version ago, which means that many if not most users can't actually get the benefit without buying a newer phone.

I gather there are some questions around the strength of its app sandboxing as well, but I can't speak to that at all. Perhaps someone better informed will do so.

Those permissions are also opt-in for devs at the moment (by choosing certain OS versions at build time you can still use the old permissions system).

I'm an Android dev and to me the biggest problem with Android from every aspect (development, security, monetization) is how poorly new versions of Android are supported on devices.

Apple's dig at Android 7 usage vs iOS 10 usage was spot on.

> (i.e. sells their customers' data to advertisers).

This is not true

Couple of examples:

1) iOS has had lazy permissions since the very early days e.g. when an app wants to use this microphone then ask the user right then instead of when the app is installed. This feature is still not implemented on all Android devices nor is it as seamless nor is it mandatory.

2) Apple is providing more and more frameworks e.g. CoreML which run only on the device. This means that developers don't have to run their own server side apps to process data.

I don't really see that as lazy. I see that as considerate/beneficial to the user. I much prefer to be asked in context what/how the app is going to use the microphone for rather than on initial install, when I might be like "why the heck does this app need to use the microphone?"

It was being used in the programming sense, not as an insult. When some code passes around a "placeholder" instead of a value and waits until it is used to bother calculating it, that is commonly described as "lazy".

Got it! Thanks for the explanation and not assuming I'm a programmer, because I'm not!