You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would make it possible for people to listen to songs directly in the gallery and discuss in a comment thread on the right; much like the experience when looking at photos on Facebook. All of that can be packaged into a modal component that
comes up over the top of the gallery after clicking on a tile.
This would make it possible for students to discuss and respond to their peers' work in the gallery directly.
Caveats and Considerations
COPPA / Student Identities
Currently, students' don't engage with the site as users. If they did, it creates a COPPA concern. I think that Oauth implementation is out of the picture just because it's so challenging to get approval from Google and everything, and I think for a SPA application it would be even harder.
Probably just letting students choose their name is the best move, then that can definitely be saved in LocalStorage on the device for easier fetching; so students don't have to input their name every time.
The text was updated successfully, but these errors were encountered:
Replacing "song" with "embed" in the url pattern for the Song Maker gives an embeddable component; like so:
This would make it possible for people to listen to songs directly in the gallery and discuss in a comment thread on the right; much like the experience when looking at photos on Facebook. All of that can be packaged into a modal component that
comes up over the top of the gallery after clicking on a tile.
This would make it possible for students to discuss and respond to their peers' work in the gallery directly.
Caveats and Considerations
COPPA / Student Identities
Currently, students' don't engage with the site as users. If they did, it creates a COPPA concern. I think that Oauth implementation is out of the picture just because it's so challenging to get approval from Google and everything, and I think for a SPA application it would be even harder.
Probably just letting students choose their name is the best move, then that can definitely be saved in LocalStorage on the device for easier fetching; so students don't have to input their name every time.
The text was updated successfully, but these errors were encountered: