Activity is typically a single, focused operation that a user can work (such as dial a number, take a picture, send an email, view a map, etc.). Yet at the same time, there is nothing that prevents a developer from producing an activity that is complicated.
Activity implementations can optionally make use of the Fragment class for ideas such as producing more modular code, building more sophisticated user interfaces for larger screens, improving scale applications between small and large screens, and so on.
A fragment is typically a modular section of an activity, with its own lifecycle and input events, and which can be added or removed at will. It is necessary to remember, though, that a fragment’s lifecycle is directly affected by its host activity’s lifecycle; i.e., when the activity is paused, so are all fragments in it, and when the activity is ended, so are all of its fragments.
Regards,
Nitesh Bavishiya