True, but how far does this one consideration take you while designing your application's UI? Surely you need to think about other consideration too when deciding whether to do the immediate task at hand with one activity, one view, or a mix of activities and views, such as one activity and several views, some with back keys some without...
So that is why in addition to asking myself, "where can I let the system do the navigation for me with the activity stack and back key?" I ask myself (during UI design), "how many views can I comfortably put on this one screen?" and "which views should spawn their own activities on user action?" as well. Then we have all the non-UI considerations that Mark Murphy mentioned in his excellent reply. On Aug 17, 8:02 am, JP <[email protected]> wrote: > On Aug 16, 9:30 pm, Mark Murphy <[email protected]> wrote: > > > On Mon, Aug 16, 2010 at 11:38 PM, David <[email protected]> wrote: > > > What advantages of multiple activities am I missing? > > I'm sure we can come up with other reasons > > Breaking down an app into activities supports navigation with the BACK > button. Must be manually coded otherwise. -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
