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
Hello everyone, i'm here to talk about the next steps of this project. We've seen how fast we are growing and how many people have joined us, hence this project must become modular as soon as possible.
The next project structure will have 2 different repositories for:
The API will do must of the today's backend work. Later on we'll have an active websocket connection with the end user, this should belong to its own repository. About the future i like to think about the API being able to serve every possible client (Android App, iOS app, etc...) without any problem.
Please, share your thoughts.
To all contributors and future contributors.
The text was updated successfully, but these errors were encountered:
First of all I would like to congratulate you for the project initiative. 👏 👏
I really like the idea to split this project into two different repositories.
For the client I will suggest to use things like (React+Redux+Axios) or (Vue+Vuex+Axios), I've been work a lot with React, but I think that both React and Vue could be a better idea instead of using Angular.
And if the intention is to make a client to Mobile Devices, we could easily use React Native or Weex, and this way we'll could keep the same logic/states for both environment, web and mobile devices.
@eddiecode I'll consider React+Redux+Axios and make the call together with the contributors on Slack. To be honest, I don't quite like Angular2. Thanks for sharing.
Hello everyone, i'm here to talk about the next steps of this project. We've seen how fast we are growing and how many people have joined us, hence this project must become modular as soon as possible.
The next project structure will have 2 different repositories for:
The API will do must of the today's backend work. Later on we'll have an active websocket connection with the end user, this should belong to its own repository. About the future i like to think about the API being able to serve every possible client (Android App, iOS app, etc...) without any problem.
Please, share your thoughts.
To all contributors and future contributors.
The text was updated successfully, but these errors were encountered: