I think fragments are more of a replacement for components... this is so you could re-use UI components in the app (with UI for tablets in mind)... i wouldn't try to re-use them as an activity replacer (they also make it much harder to handle the Back button since they have their own stack.. especially since the Back button will close the last added fragment, which might not be even visible to the user).
On Monday, March 11, 2013 3:30:07 AM UTC+2, Lew wrote: > > TreKing wrote: > >> bsd_mike wrote: >> >>> is there any benefit to using one Activity? >> >> >> For games, I believe, it avoids the resource management and dependency >> issues related with dealing with the lifecycles of multiple Activities. >> >> Beyond that, though, I believe shoving all of your functionality into a >> single Activity is asking for a maintenance headache. >> > > I don't know if this addresses the OP's concern, but fragments put you > somewhere between those two extremes. > > The usual model in Android programs is one Activity per screen, with > fragments as a way to manage "frames" > within the screen. > > -- > Lew > > -- -- 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.
