But historically, apps on iOS can only ask for permissions at run time, not at installation time, and you can refuse any permission if you choose (and restore it later if you want). So if an app wants to use a camera, it can either (terribly) ask you the first time you run it, or (nicely) ask you when you do something that uses the camera, and app store guidelines say the app has to not break horribly when it is told no.
In Android (historically) at installation time you get a list of requested permissions, and you either accept them all ("can access the microphone", "can access your contacts", "can access your browser history", "can control your phone", "can implant thoughts into your mind") or you can opt out by not installing the app. That's the scary thing; you go to install a todo app that wants to access your contacts -- what do you do? Is it malware? Will it be changed to be malware in the future?
From what I can tell, the interface in Marshmallow is still annoying in that the app tells you what it is going to ask for at install time, but doesn't get granted those permissions until it asks explicitly and you say yes.
>looking at what an app wants in order to install.
I believe they request the same things in iOS as they do in Android in the case of multi-Platform apps like Facebook, but Google decided to show them in a different way that looks like it is worse than how Apple does it.