[MUSIC] Hi I'm Doug Schmidt and I'd like to welcome you to the Capstone MOOC, in the Android App Specialization. On behalf of Julie Johnson, Jerry Roth, Mike Walker and Jules White I'd like to congratulate you on successfully finishing all four content area MOOCs and joining us for this final session. In this video I'll give you an overview of the structure of the Capstone MOOC, summarize the requirements for the final Capstone project and explain the means by which submissions will be assessed [MUSIC] This Capstone MOOC gives you an opportunity to integrate and demonstrate your mastery of the knowledge you've acquired in the four previous content MOOCs, to developed a mobile app from the ground up. This app should support one of our users and leverage services running on a mobile device, and/or in a computing cloud accessed over the Internet. This Capstone project is more open ended compared to the previous MOOCs in the Android app development specialization. In particular, the project is described by a lightweight specification that gives you the freedom to choose how craft the specific details of your solution. Each of you will design and implement the specification and then submit it, to receive an assessment at the end of the course by your fellow Capstone learner peers. You need to design and implement your app over four weeks, working roughly ten hours per week. Though naturally, you're free to devote as much time as you'd like to this project. [MUSIC] Your project will incorporate lessons learned from each of the previous MOOCs in the Android App Development Specialization. The project specification outlines the absent intended high level behavior, yet leaves substantial room for individual creativity. You'll therefore need to flush out many important design and implementation details. The basic requirements of the Capstone MOOC project specification include Apps must have a new, private, GitLab repository, with a readme.md file which explains the app at a high level. And make use of markdown, to better format the page's presentation. The app must compile and execute properly without crashing. And App implementation must comprise at least one instance each of the Activity, Service, BroadcastReceiver and ContentProvider Android component categories covered on the four previous content MOOCs in the specialization. Apps Interact with at least one remotely web service over the network via HTTP. At runtime, apps must allow users to navigate between to at least two different user interface screens. For example, a hypothetical RSS, Atom reader apps might have multiple screens. Such as a list view showing RSS feed stories, a detailed view showing a single feed story and a setting view for configuring information about the app's settings. Apps must at least use the JUnit testing framework to implement unit tests and integration tests for their application, and the test must cover the functionality of the app. Additional testing frameworks, such as Espresso, may also be used if desired. Apps must support persistent storage of information in an apps content provider. Although you're welcome to leverage projects from earlier content MOOCs as the starting foundation for your new app. You must make substantial effort to expand upon and/or customize the code provided. [MUSIC] This Capstone MOOC runs four weeks plus an extra week for peer assessment of the final project submission. This submission should be done by the fourth week at the latest, though you're free to submit your solution prior to that point if you finish early. The goal of this timeline is to ensure everyone has a working project to demonstrate, both via source code and a short mp4 video of the working app. Unlike past peer-evaluated assignments in this specialization. You must evaluate five, not three other submissions. This goal is to expose you to other learner's solutions and provide a chance to both learn from and constructively critique a wider range of projects. The grading rubric questions, as well as possible responses are available for download as a PDF file, or it can be viewed in the assignment peer-evaluation page. As with the other MOOCs in the Android app specialization, feel free to post questions about your project to the Capstone discussion forums. The instructors and members of our specialization community will provide feedback on the questions as time permits. Thanks again for participating in the Capstone experience. We look forward to interacting with you on the discussion forums. [MUSIC]