dj-m / ToDoOrNot

0 stars 0 forks source link

Initial To Do App Submission... #2

Open dj-m opened 8 years ago

dj-m commented 8 years ago

Hi, I've put together the initial required user stories for the To Do Android app, titled: To Do Or Not. /cc @codepathreview @codepath

I'm going to continue plugging away at it to incorporate more user stories, but I wanted to know when would be a good time to start refactoring/getting rid of unnecessary code? Also, do you recommend creating a global variable, that's written to with the To Do list item that's tapped/clicked, when going on to replace it, after it's been updated/edited?

Thanks!

nesquena commented 8 years ago

Hi Domingo,

Looks good, this exercise is intended in part to give you an introduction to the general rhythm of this course. The course is entirely project-based with an app being assigned each week and then due the following week. Each project builds on the last to help each engineer learn the practical elements of Android development and best practices as quickly as possible. We also do a code review for each submitted project once the program begins.

The next step now that you submitted the initial version before the deadline is to continue working on extensions to your todo app. With regards to extensions to implement, we are looking for developers with an interest in user experience and product development so be sure to focus on additional functional enhancements and/or improving the user interface of the app. Please ping us back for a review once you've added a few extensions.

nesquena commented 8 years ago

I'm going to continue plugging away at it to incorporate more user stories, but I wanted to know when would be a good time to start refactoring/getting rid of unnecessary code? Also, do you recommend creating a global variable, that's written to with the To Do list item that's tapped/clicked, when going on to replace it, after it's been updated/edited?

I would refactor as you add new features. I would avoid global variables. Instead use persistence (writing to the local disk) or the intents approach. In Android development, global variables in memory are an anti-pattern.