News for hackers. Stuff that matters.
Re:Why your Android app doesn't need an exit button by minouye on Monday May 17, 2010 @04:28PM (#1355421)
From my perspective, I like having an exit button, particular for services that do some sort of push notifications (e.g. if I'm using Google Talk or Skype, I want to ensure I don't continue to receive messages on my phone after I exit). Pandora is also another example of an app that needs to have an exit button (or 'quit' in their case).

Back and Exit are completely different in my mind. If I hit Back and the app is still running or I continue to get notifications, then that's potentially expected behavior from the app. If I "Exit" out of an app, then I know that if I continue to get notifications, that's on the developer.

Re:Why your Android app doesn't need an exit button by zzzmarcus on Monday May 17, 2010 @04:55PM (#1355510)
I agree. Another case is audio players. I have a couple that try to play audiobooks (come on Audible...) and they usually put a play/pause notification or toggle in the status bar. There's no way to get rid of it when I'm not actually using the audiobook player apart from force-killing the app. The notification doesn't hurt anything, but my OCD side says it shouldn't be there if I'm not using it.
Re:Why your Android app doesn't need an exit button by technomancy on Monday May 17, 2010 @07:27PM (#1355937)
That doesn't mean it needs an exit button; it just needs to quit putting a notification up when it's not playing.
Re:Why your Android app doesn't need an exit button by djmdjm on Tuesday May 18, 2010 @01:00AM (#1356550)
Gtalk does have a "sign out of talk" button.