Closed iainsmith closed 8 years ago
This would be really great! I think it could be done completely independently from the current setup. It'd be nice to have a small server for this. For this, we'd probably need some unique identifier for each video. (See also #58).
I've always wanted to use something like Amazon Cognito. Maybe that could be a backend? (Not sure, have never used it)
Cognito is a possibility. I was personally leaning towards Parse.com http://parse.com/ due to previous good experiences with it and their Apple TV SDK announcment. I’ll try and take a look over the holiday period.
If anyone else is motivated to make a start on this, please do, as I don’t know how much time I’m going to have.
On 21 Dec 2015, at 13:47, Chris Eidhof notifications@github.com wrote:
This would be really great! I think it could be done completely independently from the current setup. It'd be nice to have a small server for this. For this, we'd probably need some unique identifier for each video. (See also #58 https://github.com/chriseidhof/pomotv/issues/58).
I've always wanted to use something like Amazon Cognito. Maybe that could be a backend? (Not sure, have never used it)
— Reply to this email directly or view it on GitHub https://github.com/chriseidhof/pomotv/issues/60#issuecomment-166309089.
I'm a bit afraid of Parse, but feel free to go ahead as you please!
I'm closing this for now, I think it'd be a great feature but let's discuss more when there's actually code.
Hey Chris, really happy to see this project coming together.
I'd love to be able to queue up a series of videos and track what I've watched. Ideally this would work across devices & could use GitHub login.
This would probably require adding a server component and would potentially open up options for other features in the future. E.g push notifications, easy submission of new videos via forms, etc.
This could be implemented with Parse.com, iCloud, AWS etc, but may incur costs in the future.
Alternatively if we only expose this feature through GitHub then we could create a pomo_playlist repo in the user'a account. This nicely sidesteps adding a central service for now, but doesn't create the infrastructure for other features down the road.
Obviously there are down sides beyond just cost, it would complicate development & maintenance.
What are your thoughts on the feature & infrastructure?