My project is doing a Honeycomb app for tablets and we seem to be using Fragments "just because" they exist :-). The decisions we are running into are along these lines -
- View Toggle - a widget that changes part of the screen in the same Activity. You can do this with Fragments. Or just use Views (as developers have been doing since day-1 Android). So why use Fragments in this case? - Big Activities + Multiple Fragments VERSUS separate Activities. Since you can't share Fragments between Activities, if you have implemented cool functionality with a Fragment the question is whether to (a) re-instantiate the fragment (say a page header) in a separate Activity, or (b) fold the two activities into one and use the one fragment instance. Does option (b) raise concerns about the app using lots of memory? Is option (a) going to be different user experience re displaying the whole page? The "quintessential use case" for Fragments as noted by Mark Murphy in another thread, is supporting different layouts on different screen sizes. If you are building an app only for tablets that use case is not relevant. So what are the use cases for Fragment based designs? -- 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
