You're right. And you shouldn't put any possible sub-division of a screen into a Fragment. But if you plan to have your app support both regular/large and extra-large screens and want to have tablet-specific layouts (extra-large), then Fragments are an excellent way to go, enabling to re-use UIs between various forms of Activities. E.g. an app with showing a list of e-mails and the details/contents of a particular e-mail: Your tablet specific part of your app could have one activity: For both the list of e-mails and the contents of the selected e-mail. You put the list of e-mails in one Fragment and the e-mail details in another Fragment. Your phone specific part of your app could have two activities: One for the list of e-mails, the other for the contents of a selected e-mail. When you click on a e-mail list-item, the details activity opens. When you have put the two 'screens' in the two Fragments, you can easily re-use the two Fragments between the tablet part and the phone part of your app. You also could do this by using <include> or <merge> items instead of Fragments. But when using these constructs, you have to implement the 'back-stack' functionality yourself for the tablet part of your app.
-- 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
