android - Fragments vs. Deprecated TabActivity on a pre 3.0 device -


so tabactivity officially deprecated of 3.0, i'm going through , switching of tabactivities fragments. first decided research little fragments

i'm reading design philosophy , 1 of lines is:

android introduced fragments in android 3.0 (api level "honeycomb"), support more dynamic , flexible ui designs on large screens, such tablets.

now, i'm not developing tablet, nor app ever see tablet. barring bad idea of using deprecated code, have gain if i'm not going use big screens or animations, seems main thing touting?

now, i'm not developing tablet, nor app ever see tablet.

that may case if you're not shipping app. because writing phone not prevent tablet owners installing it. may using hardware capabilities tend used phones , not tablets (e.g., telephony), there's nothing stopping hardware manufacturer offering capabilities in tablet.

barring bad idea of using deprecated code, have gain if i'm not going use big screens or animations, seems main thing touting?

fragments offer benefits, such simpler management of configuration changes, more annoying need without fragments.

more importantly, increasing percentage of android ui require fragments going forward. example, note, tabs (particularly activities-in-tabs) going away, being replaced tabs in action bar controlling fragments. now, may think tablets, when ice cream sandwich (ics) ships later year, action bar , tabs extended phones well. while old-style tabs should still function on ics phones, odd comparison. whether or not "odd" problem you, of course.


Comments

Popular posts from this blog

c# - How to set Z index when using WPF DrawingContext? -

razor - Is this a bug in WebMatrix PageData? -

visual c++ - Using relative values in array sorting ( asm ) -