Welcome to the fourth and final assignment submission in the capstone MOOC for the Android App Development Specialization. As discussed in this video, the final submission is designed to provide you with feedback on whether you're completed app meets all the requirements for the capstone project. You'll also get a chance to learn from and provide feedback on apps submitted by some of your peers. For the final submission, you need to submit a completed version of your project's app, including the source code and test files which addresses the peer reviewer comments received for all three previous milestones in this capstone MOOC. You'll also need to create an MP4 video that shows how your app works when it's run. Please combine the final implementation and test files as well as the associated build files into a single ZIP file, and submit it via the prompt on the final submission webpage. Once again, the name you choose for this file doesn't matter. Upon completing the final assignment submission, your app should contain the following artifacts and exhibit the following properties that will be evaluated by your peers. It must contain a README.md file that explains the app's key features and components, and uses markdown formatting to improve the pages presentation. It must compile and execute properly without crashing. It must contain at least one instance each of the following Android components covered in the Android App Development Specialization, including activities, a broadcast receiver, a bound or started service, and a content provider that encapsulates an SQLite database. It must interact with at least one remotely hosted web service over the network via HTTP. It must allow users to navigate at runtime between at least two different user interface screens implemented by activities. For example, a hypothetical, RSS Atom reader app might have multiple screens, such as a List View showing all RSS feed stories, a Detail View showing a single-feed story, and a Settings View for configuring information about the app settings. Your submission must also at least use the JUnit testing framework to implement unit and integration testing for your application. The test must cover the functionality of the app. Additional testing frameworks such as Espresso UI testing may also be used if desired. It must support persistent storage of data via an SQLite database encapsulated within an app's content provider. And finally, it must have well-documented source code and an MP4 for video of your app. Your video doesn't need to be fancy. It can just be a screencast that shows how your app works when it runs. As usual, after submitting your implementation and test files in a single ZIP file, you'll review three peer submissions for the final app, and answer a question about the peer submission on each of the topics above. Likewise, there's also an ungraded text box for you to elaborate upon each topic, as well as another ungraded text box for the overall project, if you'd like to constructively comment on the final project. Your feedback is an essential part of the learning process, so please take the time to help others improve their apps! Thanks again for participating in our Android App Development Specialization. We hope you've enjoyed learning this material as much as we've enjoyed creating it.
