Project feedback
Interesting idea! The chosen technologies meet the course requirements and seem to work fine together.
Some points:
- It’s always a good idea to have a time plan and define milestones.
- It's a good idea to have some time only dedicated for solving possible unforeseen issues.
- Let’s not reinvent the wheel. It’s always a good idea to use third-party libraries and services when possible, if not against the course requirements. For example, third-party authentication.
- The size of the project shall be moderate. The use of technologies shall be at a good level.
- You need to be able to show that you’ve used the technologies in a sensible way at a good level and that you understand them. This is how the grading is done.
- It is important that the chosen front-end framework is used at a good level.
Some notes:
- You should prioritize using web-related technologies at a good level instead of developing web-related algorithms.
- No use of server-side templating, instead use the backends as REST-apis.
- There is a risk that the project becomes bigger than what can be done during the course. Prioritizing functional requirements and doing them in order can be a good approach to achieve a working application by the end of course anyhow.