Nothing usual about my situation, though we know from the Facebook app that developers sometimes try to game the system. Perhaps that was the case with Waze, and it's different now, I really don't know. All I know is what happened and that I wasn't interested in using Waze after I discovered what it was doing in the background.
The article you cite isn't particularly helpful in that it refers to forcing an app to "quit," and then cites as a reference Apple's support information that uses the terminology of forcing an app to "close" (in the case of it becoming unresponsive). Apple is perhaps oversimplifying the issue somewhat by using this language instead of speaking more technically about iOS app states.
Anyway, I wasn't planning on becoming anywhere close to this engaged in this discussion interesting though it may be. The main takeaway that I hope everyone gets from it is that users will only rarely have any reason to delete saved suspended states. It's a useful thing to know about I suppose but it is not a maintenance method or requirement of iOS. Let your device do this work for you, and be happier and more productive. And that's all I have left to say about it.
