Why is TabActivity out of date (reason)?

This is not a duplicate. How to use fragments, now that TabActivity is out of date?

After some research, the conclussion is that TabActivity is deprecated, because now we have to use fragments. And the reason for this, as far as I read, is that fragments work better with the action bar, and with the support of the compatibility library it can also be implemented starting from Android 2.1

But I still do not understand why it is out of date. Why not just make the action bar work with actions as well? Why are fragments preferable?

I also read that fragments have better performance ... is that the reason?

Actions, at least, are pure separated objects, which is something positive. Now I don’t have enough understanding of fragments to understand why they are better.

Thanks in advance...

+5
source share
2 answers

TabActivity is deprecated because it is a subclass of ActivityGroup, which is also deprecated.

ActityGroup is deprecated and a snippet has been added and proposed instead. Because using fragments is simpler and more flexible than ActivityGroup. It also allows Android components to have a uniform pattern.

+3
source

The main reason Google rejects certain methods / objects is to apply best practices and get the most consistent patterns compared to applications.

TabActivities ActionBar , TabActivities, .

- , API (, Clipboard, " " " -" ).

+1

All Articles