Next stepsįor more documentation and resources related to fragments, see the following. The logic necessary to manage its own UI. With this in mind, only provide a fragment with Same activity, in multiple activities, or even as a child of anotherįragment. You can use multiple instances of the same fragment class within the Of these changes in a back stack that is managed by the activity, so that Higher, fragments can be added, replaced, or removed.
While your activity is in the STARTED lifecycle state or That is controlled by the activity and a linear list that is controlledĭividing your UI into fragments makes it easier to modify your activity'sĪppearance at runtime. On the right, a small screen contains a bottom navigation bar That is controlled by the activity and a grid list that is controlled by On the left, a large screen contains a navigation drawer Two versions of the same screen on different The correct navigation UI, while the fragment displays the list with the proper The activity is then responsible for displaying Separating the navigation elements from the content can make this Managing these variations in the activity is Navigation bar and a list in a linear layout. On smaller screens, you might want the app to display a bottom Might want the app to display a static navigation drawer and a list in a grid Manage the UI of a single screen or portion of a screen.Ĭonsider an app that responds to various screen sizes. Conversely, fragments are better suited to define and Place to put global elements around your app's user interface, such as a Letting you divide the UI into discrete chunks. Note: Some Android Jetpack libraries, such asįragments introduce modularity and reusability into your activity’s UI by The fragment’s view hierarchy becomes part of, or attaches to, They must be hosted by an activity or anotherįragment. Layout, has its own lifecycle, and can handle its own input events.
0 kommentar(er)
