Snippets against deprecated TabActivity on pre 3.0 device

So now that TabActivity is officially deprecated since 3.0, I am browsing and switching all my TabActivities to Fragments. But first, I decided to explore the fragments a bit.

I am reading a design philosophy, and one of the lines:

Android introduced fragments in Android 3.0 (the Honeycomb API level), primarily to support more dynamic and flexible user interfaces on large screens such as tablets.

Now I am not developing a tablet, and my application will never see the tablet. Banning the bad idea of ​​using outdated code, what should I get if I don’t use large screens or animations, which, apparently, are the main ones that they advertise?

+5
source share
1 answer

Now I am not developing a tablet, and my application will never see the tablet.

This can only be if you are not sending the application. Just because you write it for the phone, this does not prevent the owners of the tablet from installing it. You may be using hardware features that are commonly used by phones rather than tablets (such as telephony), but there is nothing to prevent the hardware manufacturer from offering these features on a tablet.

Banning the bad idea of ​​using outdated code, what should I get if I don’t use large screens or animations, which, apparently, are the main ones that they advertise?

, , , .

, Android- . , , ( , ) , , . , , , IceCream Sandwich (ICS) , . ICS, . , , "" , , .

+8
source

All Articles