In practice you should never want to use the native fragments because you'll have to suffer platform-specific bugs and API variances. The ones embedded in the support library will at least be consistent in bugs and behavior. Additionally, the use of ActionBarActivity (which extends from FragmentActivity) does nothing to prevent you from using native fragments.
On Fri, Oct 17, 2014 at 2:38 PM, Karl Åström <[email protected]> wrote: > If I understand the documentation correctly I can have "native" Material > design in Lollipop or I can have "appcompat" Material design for v7 and up > which is nice if you want to support really old phones I guess. > > The problem however is that I'm trying to get away from that so I can use > "native" fragments and activities but now I can't do that because I can't > get Material design through appcompat-libraries for Activities between Api > 15 and Api 20 without using the support library ActionBarActivity. Am I > missing something or is this a regression towards having to use > appcompat-activities/fragments again just as I've managed to convince my > bosses we don't have to support gingerbread? > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" 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/d/optout. > -- You received this message because you are subscribed to the Google Groups "adt-dev" 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/d/optout.
