thanks mark, your explanation makes my head clear about android structure... :)
On Tue, Sep 30, 2008 at 5:58 PM, Mark Murphy <[EMAIL PROTECTED]>wrote: > > Rio Astamal wrote: > > suppose we open many app, let say 10 app (browser, contact, dialer, > > etc), I'm not quite sure that all app not consume much memory as they > > were closed. > > Android handles that for you. If the operating system determines it > needs RAM, it will close down your activities on an as-needed basis. > Then, when the user tries to go back into them, it will let you restore > your activities' states, so the user largely will not realize the > application was ever gone. > > I believe the #1 goal is for a seamless user experience. Google (hackbod > in particular) has pointed this out many a time on the > [android-developers] Google Group. They looked at the Windows Mobile > model of lots-of-third-party-task-killers-needed and decided to go > another route. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com > > Android Training on the Ranch! -- Mar 16-20, 2009 > http://www.bignerdranch.com/schedule.shtml > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" 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-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
