akilesh-io / app.ruscello

Watch Movies Together

Ola Amigo 🎶

app.ruscello's Issues

Code smells

• React components should be inside .tsx
• Utils should be inside .ts
• Format the code
• Replace arrow to named functions in useEffect
• Clean up resources on useEffect
• Remove sample file created as part of create-next-app
• JSDoc for components and functions
• Constants

ENV secrets

All the server configs needs to be parsed from a .env file.
This avoid the need to change the code to change the URL.

This .env file should be ignored from git.

The issue #8 describes the url to be dynamic, but a different approach from this issue can make #8 simpler.
For example, we can setup a different .env file for development and production. This approach makes the BACKEND Url dynamic and thus makes the #8 issue close-able without any development.

Application Flow

There should be a clear documentation for Application flow.
The flow should be in both Use case perspective and Development perspective.

Switch to Next video

Currently this project uses react-player with Material UI using this as reference It has bugs and need to spend times to improve it's quality

Next-video is robust and has all necessary features needed for filmingo

1. Optimized video streaming
2. Adaptive streaming
3. Placeholder posters
4. Timeline hover thumbnails
5. File formats solved
6. Analytics built-in

Dev Environment

Currently the frontend is hardcoded with production Backend URLs and PeerJs URLs.

This needs to be dynamic:

• In development the URL should be pointing to localhost.
• In production the URL should be pointing to production url.

This makes the setting up the dev server so easy.