The 2 rules they highlighted about location-based APIs stuck out to me:<p>> <i>4.2 Apps that use location-based APIs for automatic or autonomous control of vehicles, aircraft, or other devices will be rejected</i><p>I'm not sure why that's there, first of all. Maybe they're afraid they'd be liable if the vehicle crashed?<p>Also, as I understand it, that doesn't prevent you from having directly control of a vehicle, like with buttons to change speed and tilting to turn it. Only if you want to use GPS or the like (so I guess sticking an iPhone in the autonomous vehicle and using those coordinates to help you steer it, or something).<p>> <i>4.3 Apps that use location-based APIs for dispatch, fleet management, or emergency services will be rejected</i><p>Once again, I have no idea why that's there. And those applications of location-based APIs seem like they'd be very useful. For example, Ubercab would probably count as using location-based APIs for fleet management.
<i>19.2 Apps may contain or quote religious text provided the quotes or translations are accurate and not misleading.</i><p>Deciding what religious texts are accurately translated sounds like a very thorny problem. Is the KJV accurate? The Conservative Bible Project?
Wow. Several of my favorite app ideas explicitly prohibited. Especially disappointed about:<p><i>4.2 Apps that use location-based APIs for automatic or autonomous control of vehicles, aircraft, or other devices will be rejected</i><p><i>11.3 Apps using IAP to purchase physical goods or goods and services used outside of the application will be rejected</i>