Modules within Phoenix to get familiar with:

• Phoenix.Presence for tracking players/commentators/watchers
• Phoenix.Channels for bi-directional client <—> app communication which LiveView builds on top of
• Phoenix.PubSub for pub/sub which Channels builds on top of

There’s too many “build a chat room with Phoenix LiveView” posts to list, but they should help stitch together the concepts above. There’s even a handful of “shared canvas cursor tracking” posts if you want a non-text centric example of soft real time communication using Phoenix LiveView.

At a more foundational level, dive into OTP itself e.g. from a Process to a Genserver and how it empowers you to draw a line between runtime concerns and thought concerns as expressed in this oldie but a goodie post To spawn, or not to spawn? that walks through modeling blackjack in OTP as an example.

And on the experimental fun side, OTP makes it fun to prototype novel interactions in my experience. Take a look at the interaction design of couch party games for inspiration!

Yeah, my tip is: don’t create gambling website. At least make sure that there is no conversion between game currency and real money

For this kind of problem where you have “tables” or “rooms” in a game, you will often want to reach for the Dynamic Supervisor.

Docs here: DynamicSupervisor — Elixir v1.20.2

Hopefully that should serve as some inspiration for you