Open watsonarw opened 7 years ago
My thoughts are basically feature parity with existing app.
nvm
eitheretc etc
I would add:
Need to add a Wiki, as mentioned by Adam in https://github.com/twlevelup/watch_edition_react/issues/18
Hi guys, since we are nearing the completion of Milestone 1. I just wanted to consolidate and confirm that the following is the final list for Milestone1? if you have any additions please just edit it.
nvm
eitherDo we actually need the Notification stuff?
@AMitchemTW I thought so! it was in the old app. If we don't need it's better, less code :)
Yes. It gets used a lot
On 23 Aug 2017, at 2:59 pm, Sinan Aumarah notifications@github.com wrote:
@AMitchemTW I thought so! it was in the old app. If we don't need it's better, less code :)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
It's a way of simulating server based functionality. It's mostly used for push notifications like "your next class is about to start in room …", "your friend is in the area" etc etc
On 23 Aug 2017, at 2:59 pm, Sinan Aumarah notifications@github.com wrote:
@AMitchemTW I thought so! it was in the old app. If we don't need it's better, less code :)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
So notifications can be generated by the watch pages, or only by manually typing them?
In order to break down the work needed, I'd like to capture the key pieces of functionality that we need to replicate from the existing watch app.
This should help us know when we're "done", at least to the point where we can comfortably use this as the base for student projects.
The app
Default Pages
Home Page
Contact Page
Setup
nvm
eitherTesting
CI/CD