In some ways you can think of a Fragment as a mini-Activity, though it can’t run independently but must be hosted within an actual Activity. A Fragment is a self-contained component with its own UI and lifecycle it can be-reused in different parts of an application’s user interface depending on the desired UI flow for a particular device or screen. Introducing the FragmentĪndroid 3.0 further helps applications adjust their interfaces with a new class called Fragment.

However, as we move up into tablet-oriented UIs with 10-inch screens, many applications also benefit from a more radical UI adjustment than resources can easily provide by themselves. As a result, many existing handset applications Just Work under Honeycomb on full-size tablets, without special compatibility modes, with no changes required. The combination of layout managers and resource selection based on screen size goes a long way towards helping developers build scalable UIs for the variety of Android devices we want to enable. Developers can use the resource system to select between different layouts based on the screen size. Developers immediately started using this facility when higher-resolution screens were introduced, first on Droid and then on other phones.Īndroid 1.6 also made screen sizes accessible to developers, classifying them into buckets: “small” for QVGA aspect ratios, “normal” for HVGA and WVGA aspect ratios, and “large” for larger screens. A common example is a ListView whose height changes depending on the size of the screen, which varies a bit between QVGA, HVGA, and WVGA aspect ratios.Īndroid 1.6 introduced a new concept of screen densities, making it easy for apps to scale between different screen resolutions when the screen is about the same physical size. Since the beginning, Android’s UI framework has been designed around the use of layout managers, allowing UIs to be described in a way that will adjust to the space available. An important goal for Android 3.0 is to make it easier for developers to write applications that can scale across a variety of screen sizes, beyond the facilities already available in the platform: rssreader import import import android.os.Bundle import 7.app.AppCompatActivity import import import import import import import .RssItem public class RssfeedActivity extends Activity implements MyListFragment.

Android studio fragment return intent