StefanSarzio wrote:From the glorious iOS announcement: "While some simpler implementations require the user to manually disconnect the app, waze has a different approach to background processing and shut down. When waze goes into the background, algorithms are applied to detect whether or not the device is in motion."
There's an simple and easy solution for exactly this problem on Android (without any fuzzing with 'smart' alogrithms doing educated guesses), allowing you to shut down Waze in a clean way at precise the correct time - yet you still didn't get that right, although that solution was available from the beginning...and was requested several times.
In case you see Waze on Android as some kind of second class citizen: why don't you just say that loud and send everybody over to Google Navigation?
I agree, Stefan. I just find it very strange that multitasking has been present for years on WinMo, Symbian, Blackberry and Android, and it has just been taken for granted that the user will simply end the app when they've finished with it. But now 'The Almighty' Steve Jobs has finally got on board the multitasking bandwagon, suddenly the strategy is being rethought in a blaze of glory. Why, again, are iPhone users given preferential treatment? Or is it just that they can't be trusted to end their apps manually, just as they can't be trusted to hold their phones properly?
I must say, the only app on my phone that is unstable and crashes regularly is Waze. Yet is was rock solid on my Nokia 5800. Maybe the whole app on Android needs to be re-visited from the ground up.