4 ms·
The 2 rules they highlighted about location-based APIs stuck out to me: > 4.2 Apps that use location-based APIs for automatic or autonomous control of vehicles
by jackowayed 16y ago
The 2 rules they highlighted about location-based APIs stuck out to me:
> 4.2 Apps that use location-based APIs for automatic or autonomous control of vehicles, aircraft, or other devices will be rejected
I'm not sure why that's there, first of all. Maybe they're afraid they'd be liable if the vehicle crashed?
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).
> 4.3 Apps that use location-based APIs for dispatch, fleet management, or emergency services will be rejected
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.
- MartinCron 16y agoI think the AAA app uses the APIs for dispatch and emergency services. Odd
- devin 16y agomy guess is legal liability.
- gojomo 16y agoMy guess on 4.3 is a combination of liability concerns and some sort of deal with the mobile carriers not to step on existing high-dollar business-focused subscription fleet services. (Look how AT&T wants $10/month for their turn-by-turn 'Navigator' directions app. Hey -- isn't that fee -- on your AT&T bill -- a violation of 11.2, "utilizing a system other than the In App Purchase API (IAP) to purchase content, functionality, or services in an app"?)