Sorry that I can't raise more issues right now 馃槩 馃尩
There is a lot of code and it's hard in this time to see everything that is happening and where problems are.
I would recommend, after code review, raise your user stories are issues, and focus on getting one at a time working (as well as responding to issues I, and others have raised).
It looks like you've tried to implement a lot of different features and quite a few of them are maybe half done or so.
If you raise your user stories as issues, and decide which are the most important, you can work through them more methodically, so that you can make sure each one works before moving onto the next one, maybe having each pair work on a different user story at a time. This is useful in all projects right from the start, so you can define your priorities in terms of which features really matter to your app, and make sure you focus on them.
Sorry that I can't raise more issues right now 馃槩 馃尩
There is a lot of code and it's hard in this time to see everything that is happening and where problems are.
I would recommend, after code review, raise your user stories are issues, and focus on getting one at a time working (as well as responding to issues I, and others have raised).
It looks like you've tried to implement a lot of different features and quite a few of them are maybe half done or so.
If you raise your user stories as issues, and decide which are the most important, you can work through them more methodically, so that you can make sure each one works before moving onto the next one, maybe having each pair work on a different user story at a time. This is useful in all projects right from the start, so you can define your priorities in terms of which features really matter to your app, and make sure you focus on them.