The Capstone, this is what it has all been leading up to.This is where you're set free to design your own project and utilize your own ideas, albeit always within the boundaries set by the specifications.
These boundaries are placed for good reason, though.The rubric is there to make you think hard about every detail of your project and to foresee and anticipate every requirement that could lead to congestion or extraneous effort, protecting you from crying out it's "too late" when deep into the project.
They take shape in a generic template which sets them in boilerplate text which you are expected to replace with your own comments in order to demonstrate the ability to communicate your ideas formally.They are grouped by :
- An app description
- UI flow mocks
- Key Considerations
- A list of required tasks
After filling out the document you have to submit it and await feedback on it in order to complete Capstone's first stage.This is done for preventing and mitigating pain points you might run into along the way and also for replicating the process professional Android Developers go through.
By the way, it's not easy to get the go ahead by the reviewer. In my case I had to revise twice before my plan got accepted.But that's the best part of this process. Rather than being negative, The feedback is insightful, pointing out the troubling parts that need amendment and making recommendations to help you be more specific and think about the conditions you've missed. This meticulous planning ahead is going to prove golden when you get to the actual implementation phase, Capstone stage 2.