# All at once

> The final project goes real-time, and your pod uses it together.

> make your final project real-time, then decide how it behaves when several
> people use it at once --- and write down why

The [final project](https://comp.anu.edu.au/courses/comp4020-agentic-coding-studio/assessments/final-project/) has to be real-time: a change
one person makes reaches everyone else within about a second, without a reload.
This week it has to be. At the crit your pod opens the app on their own devices
at the same time, and what one of them does should show up for the others.

How the change travels (WebSockets, server-sent events, fast polling) is mostly
settled by your stack. The decision this crit asks for is one level up, about
how the app behaves with several people in it. For example:

- what reaches other people live, and what waits until they reload
- whether people can see who else is here, and how
- what happens when two people change the same thing at once
- what someone sees when they reconnect, or come back the next day

Pick one that matters for your app, decide it by what your `README.md` says good
means, and write it down in the repo with the options you considered and what
your choice costs. An
[architecture decision record](https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions)
is a good form. Your pod will argue for the option you didn't pick.