Question

What is the Difference between HPLMN and EHPLMN?Can u give me a Example?

Answer 1

android android-fragments android-activityandroid-actionbaractivity appcompatactivity

I'm coming from iOS where it's easy and you simply use a UIViewController. However, in Android things seem much more complicated, with certain UIComponents for specific API Levels. I'm reading BigNerdRanch for Android (the book is roughly 2 years old) and they suggest I use Activity to host my FragmentActivities. However, I thought Activity was deprecated.

So for API Level 22 (with a minimum support for API Level 15 or 16), what exactly should I use both to host the components, and for the components themselves? Are there uses for all of these, or should I be using one or two almost exclusively?

share improve this question

askedJul 8 '15 at 15:32



Jameson
1,290●2●9●21

editedJul 13 '16 at 9:48



Majid
7,470●8●51●96

1

You won't be hosting FragmentActivityies. You only host Fragments. On newer Android versions the Activity class itself has been updated to host them directly. To support older versions FragmentActivity was introduced. – Ravi ThapliyalJul 8 '15 at 15:45

4

Similarly, with API 11+ Activityies had support for an ActionBar. This was supported on older versions through ActionBarActivity first which now has been deprecated and replaced with AppCompatActivity. Since, both of these classes extend FragmentActivity they support hosting Fragments as well. – Ravi Thapliyal Jul 8 '15 at 15:50

add a comment

9 Answers

order by                          active                         oldest                         votes                     

up vote255down voteaccepted

I thought Activity was deprecated

No.

So for API Level 22 (with a minimum support for API Level 15 or 16), what exactly should I use both to host the components, and for the components themselves? Are there uses for all of these, or should I be using one or two almost exclusively?

Activity is the baseline. Every activity inherits from Activity, directly or indirectly.

FragmentActivity is for use with the backport of fragments found in the support-v4 and support-v13 libraries. The native implementation of fragments was added in API Level 11, which is lower than your proposed minSdkVersion values. The only reason why you would need to consider FragmentActivity specifically is if you want to use nested fragments (a fragment holding another fragment), as that was not supported in native fragments until API Level 17.

AppCompatActivity is from the appcompat-v7library. Principally, this offers a backport of the action bar. Since the native action bar was added in API Level 11, you do not need AppCompatActivity for that. However, current versions of appcompat-v7 also add a limited backport of the Material Design aesthetic, in terms of the action bar and various widgets. There are pros and cons of using appcompat-v7, well beyond the scope of this specific Stack Overflow answer.

ActionBarActivity is the old name of the base activity from appcompat-v7. For various reasons, they wanted to change the name. Unless some third-party library you are using insists upon an ActionBarActivity, you should prefer AppCompatActivity over ActionBarActivity.

So, given your minSdkVersion in the 15-16 range:

If you want the backported Material Design look, use AppCompatActivity

If not, but you want nested fragments, use FragmentActivity

If not, use Activity

Just adding from comment as note: AppCompatActivity extends FragmentActivity, so anyone who needs to use features of FragmentActivity can use AppCompatActivity.