True, using multiple activities saves hassle on developer side..especially trying to remember where to back up too.. but is there any benefit from not having a pile of activities?
If you were doing MVC..and your controller keeps track of the screens..properly sends you back to a previous screen when back is pressed..hassle aside, is there any benefit to using one Activity? This is kind of a philosophical question I realize...probably not demanding as much thought as I am giving it..but I appreciate the input. Thank you, Mike On Mar 10, 12:17 pm, niko20 <[email protected]> wrote: > Using multiple activities is much less hassle on the developer side > > > > > > > > On Sunday, March 10, 2013 8:45:09 AM UTC-5, bsd_mike wrote: > > > Just wondering what the consensus is doing a UI. > > Should you kick off a new activity each time you put up a new screen? > > Or should you do what some call a Frankenstein-Activity which handles > > lots of screens and the back-button > > itself. > > > When should you do either? > > > Are there best practice guidelines for this? > > > Thank you, > > Mike -- -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
