List view
"Finalize documentation, refine any rough edges." By this point the app should be done. We should try to make this repo look as professional as possible so we can use it on our resumes or as an employer talking point. We can document why we chose SQLDelight vs Room, how we handled network requests, why we made the UI/UX decisions we did, etc. Overall, make this something the 6 of us can go back to and quickly find the relevant pieces we need to see, for whatever reason that may be.
Overdue by 5 year(s)•Due by May 4, 2020"Refine against focus groups and see where improvements can be made for users." Record a video, get user feedback, generally try to see where the app can be improved. We should make a document that rates the experience with scales using 1-10, or similar. Use friends and family and have them cook a recipe they've never done before. If nothing else, add a "timer" feature to the app so steps with a timer can easily fire one off.
Overdue by 6 year(s)•Due by April 27, 2020"Connect client and server. Write unit tests against critical code for the app. Stress test every worst-case scenario possible and clean up crashes." This can(and should be) be knocked out in the 3/2-3/16, but in the case it isn't, implement this. Make sure the flow of the network request is as follows: Network Request -> Updates SQLite Database -> Updates View If we have the time/means, we can consider adding an "upload recipe" feature here, especially if this sprint was already implemented.
Overdue by 6 year(s)•Due by April 13, 2020"Spring Break, refine and clean any “hacky” code that has accrued, if needed." Dig around, this is the time to say "I did it but it doesn't 'feel' right" and get peer feedback. Also use this time to iron out any bugs and point out anything concerning.
Overdue by 6 year(s)•Due by March 29, 2020"Create RESTful services on the server (Create, Read, Update, Delete). " "UI/UX begins implementation, “backend” of app begins to abstract work and data processing for the View to display" For the server, endpoints should be clearly defined and the JSON schema is mostly by the end of this. The person setting up the http networking on the phone/watch needs to work with the server person to wire this all correctly.
Overdue by 6 year(s)•Due by March 1, 2020•9/9 issues closed"Create RESTful services on the server (Create, Read, Update, Delete)." "UI/UX begins implementation, “backend” of app begins to abstract work and data processing for the View to display." This is the description on the task list. Realistically by this point we need to have all of our screens set up at least as a skeleton with Material Design, including on the Watch. The Watch should start reading from the phone database and updating it's list accordingly.
Overdue by 6 year(s)•Due by March 16, 2020•1/1 issues closed