mwburn wrote:Yep, in fact they got it wrong and backwards.
The "recommendation" is that if your application doesn't "exit" when the home button is pressed, THEN you warn the user that it's still running (and why, etc). Granted, I don't like the idea of waze (or any other app) using a "warning" screen if I want to hit the home button and change applications either.
There's been a lot of debate about how to enlighten/inform users of apps running in the "background", with no real good overall solution. Which is why I believe Apple made it a "recommendation", and if waze incorporates this, I for one will probably turn it on less frequently, unless I'm driving for longer trips (the majority of my trips are only a few minutes).
Nah, you're misreading the Apple document.
A single press of the Home button never does anything besides exiting the currently active application. An app does not have the opportunity to warn a user about anything once the home button is pressed (other than possibly via a push notification, in certain circumstances). The language about alerting a user to a problem is in the context of an error which does not close the app but which limits its functionality somehow.
"A: There is no API provided for gracefully terminating an iOS application.
In iOS, the user presses the Home button to close applications."
Apple wants to be sure that all their apps provide a consistent experience. Most likely Waze didn't just choose to enforce this now—probably someone at Apple caught on and told Waze "take the shutdown feature out or we won't approve the next version of your app".