On Mon, Jan 26, 2009 at 8:42 AM, Mike Hearn <[email protected]> wrote:
> > > 5) I understand the concept of opening/closing the applications in > > Android, but you could provide a functionality to force the close of > > the application. It would be nice to have this functionality as a part of > > the Running Application List (long press of Home button). Then if > > somebody would keep long press on one of the icons, a dialog with the > > close functionality would appears. > > Long-press on home actually shows recent activities - they are not > guaranteed to be running. More generally, I suggest reading the SDK > docs on the application lifecycle and component philosophies of > Android. The system is designed to make "running" vs "not running" > transparent and something the user doesn't have to bother with so > adding a force quit button would be a step backwards, the system > already shuts down apps when it needs the resources for something > else. > Any time a user has to read the sdk docs to understand something basic to how their phone behaves, there is a problem. You've not only blown up the principle of least surprise, you've also failed to document it in a user-acceptable way.. (And yes, for the record, I agree there needs to be -some- form of 'top'/resource manager and process manager. "Hey, that app I opened for just a sec is still running and if I go back to my browser, I'll lose launcher and be unable to send an sms for 30 seconds while the system churns and chews.") --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
