I didn't like the 'activity' concept when I first started using Android. However, it's grown on me well. Activities themselves are their own encapsulated parts of the application and makes debugging much easier. It is a pain at first to figure out how to destroy/ recreate activities, but after a little while, it's no problem.
The only time I really use more than one view in a single activity is for a splash screen (thanks Mark), and loading screens. I'm sure there are many more uses, but that's how I've done my apps. On Feb 26, 11:17 pm, Michal <mic...@gmail.com> wrote: > > Those are just a few of the design criteria that might lead you in the > > direction of multiple activities. > > Thanks a ton Mark, this is great feedback. I will continue exploring > the single-activity approach until I run into issues. > > I owe ya! > > Michal --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
