Attach the latest mock$-$up$,$ description, and paper prototype to this activity for your peers to understand the concept and reason behind your model. Sports App$$

$$

Explain what changes you made to your mock$-$up$,$ description, and paper prototype and why they were made.$$

$$

Discuss why you would or would not make use of fragments, data handling, and running of background tasks in your application. Hello Theodore, thanks for the post. Fragments usually introduce modularity and reusability into your activity$$s UI by allowing you to divide the UI into discrete chunks. An activity can include multiple fragments, and each fragment can have its own layout. It contains its own view objects, encapsulates its own functionality, and can be reused by other activities. Each fragment has its own lifecycle and is dependent on activity. An app I frequently use that utilizes multiple fragments is the Gmail app. In the mobile app, the dropdown menu brings up different types of folders all, spam, trash, sent, ETC... In each folder, the content is displayed with a list consisting of a title and a couple of sentences. Upon clicking on an email, in the app $($regardless of the chosen folder$),$ the email contents will open in another pane. The app adds fragments dynamically based on user interaction. The dropdown menu has a list fragment of the mail folders, each folder adds an additional list fragment to the screen in order to show the title and the first couple of sentences of the email, and by clicking an email, another fragment is added displaying the full contents of the email.