base should be ok and frontend can handle:
- jwt login/register/logout (by cookie/local storage/url params like ?token=)
- multi currency, loading balances from api
- handling extra meta data
- change bet (implemented for now just on the Three in a Row game)
- theme system that also changes game look
to do:
- init game data handling so loads from api at load game: bet sizes, theme settings, possibly language etc.
- game history
- multiplayer game
- chat maybe (?)
- error highlights/toasts and unifying this through out app
- refactor more clearly between non-auth components and authed components
- ping back every request using middleware to sync info (as security + against cached components in non auth state)
- headless session only