Projects
✅ = solution code posted
| Project | Due Date |
| 0: Rock Paper Scissors ✅ | Friday, 10/7 @ 4:00 pm |
| 1: To-Do Lists ✅ | Friday, 10/21 @ 3:30 pm |
| 2: Mobile Commerce App ✅ | Thursday, 11/10 @ 4:00 pm |
| 3: Team Project | Wednesday, 12/7 @ 11:00 am |
| 4: Portfolio Project | Monday, 1/9/17 @ 9:00 am |
Suggestions for how to approach your projects:
- Write user stories - know exactly what features you plan to implement
- Draw a paper prototype & list out all the XML files you'll need
- Plan the custom Java classes you'll need to hold your app's data, and the corresponding database tables (if applicable)
- List all the adapters, fragments, view holders, etc. you'll need to make each screen work
- Prioritize your features - don't work on bonuses before your main requirements are met!
- Before working on a new feature, make sure your app builds and runs successfully - don't start working on feature #2 if feature #1 is still crashing!
How to download soution code posted after you made your fork:
- Navigate to your local repo from the command line
- Run
git remote -vand note there is only one remote listed, your fork with the nameorigin - Run
git remote add upstream <url of original repo, not your fork>to add an additional remote namedupstreamwhich points to the original repo - Run
git remote -vagain to confirm that you now have two remotes, withupstreamlinked to the original repo - Run
git pull upstream masterto pull in changes from theupstreamremote'smasterbranch - You shouldn't encounter merge conflicts, but if you do, resolve them and do a commit after the resolution
- Run
git push origin masterto push the changes you got fromupstreamout to your fork on Github