In the Capstone project, you will build an app of your own design in two stages. In Stage 1, you will design and plan the app, using a template that we provide in the "Instructions" node.
Creating and building your own app idea can be both exciting and daunting; ultimately, we want the experience to be rewarding. You'll apply a wealth of different concepts and components that you've learned across the Nanodegree to bring you own app idea to life.
To keep the process from becoming overwhelming (or simply chaotic), you will design and plan your app, and receive feedback, before you start building. This will help prevent and mitigate pain points you might run into along the way, and also replicates the process of professional Android Developers.
To become a proficient Android Developer, you need to design apps and make plans for how to implement them. This will involve choices such as how you will store data, how you will display data to the user, and what functionality to include in the app.
Through this project, you'll demonstrate the ability to communicate an app idea formally, using:
- An app description
- UI flow mocks, similar to what you've seen in other Nanodegree projects, like the Popular Movies overview
- A list of required tasks that you will complete to build the app, in order
The Capstone project will give you the experience you need to own the full development of an app. This first stage replicates the design and planning experience that proficient Android Developers are expected to demonstrate.
- Import and build on the latest version of Android Studio (Eclipse users take note)
- Be entirely self-contained on an Android device (No external devices/bluetooth peripherals).
- Include a problem description of the problem your app solves.
- Include mocks for all user-facing screens.
- Include at least one alternate mock for tablet / large screens.Implement all mockups, including your tablet layout.
- Have at least two distinct screens (ex. a list view and a detail view).
- Work properly with the app lifecycle (i.e. you must preserve any dynamic instance state on orientation change).
- Use permissions responsibly.
- Use Intents to move between activities inside your app or to an outside app.
- Create and use your own ContentProvider
- Use Loaders to move your data to your views.
- If the application pulls or sends data to/from a web service or API, it handles this network activity properly (i.e on the correct thread, does not abuse network resources)
- Integrate two or more Google services