Fragments

Question 1

Describe a fragment

Answer 1

● A fragment represents a reusable portion of an app’s UI within an activity.
● A fragment defines and manages its own layout, has its own lifecycle, and can handle its own input events.

Question 2

Can a fragment live on its own?

Answer 2

● Fragments cannot live on their own, rather, they must be hosted by an activity or another fragment.
● The fragment’s view hierarchy becomes part of, or attaches to, the host’s view hierarchy.

Question 3

Describe modularity and how fragments ensure it

Answer 3

● Modularity is the extent to which a mobile application may be divided into smaller modules
● Fragments introduce modularity and reusability into your activity’s UI by allowing you
to divide the UI into discrete chunks.
● Fragments can be used to define and manage the UI of a single screen or portion of a screen.

Question 4

Describe how fragments can be used to modify the app’s appearance at run time

Answer 4

● Dividing a UI into fragments makes it easier to modify an
activity’s appearance at runtime.
● While an activity is in the started lifecycle state or higher,
fragments can be added, replaced, or removed.

Question 5

How can the changes made to an app’s appearance in during run time be reversed

Answer 5

One can keep a record of these changes in a back stack that is
managed by the activity, allowing the changes to be reversed.

Question 6

Should there be dependencies between fragments?

Answer 6

● One can use multiple instances of the same fragment class within the same activity, multiple activities, or in child fragments.
● Therefore, fragments only need to have necessary logic for
independent UI management to avoid any dependencies among them.