Chore: Enhance README.md with Context, Screenshots and Conclusion

[nelsonic]

At present, the README.md shows basic setup of the App. 🎉

The barebones stopwatch works: https://liveview-stopwatch.fly.dev/ 🚀

But does not take advantage of the "killer feature" of LiveView ... 🔄
i.e. "free" RealTime Sync between clients! 🤯 😍

Todo

Add:

• Context to why we (or anyone else) would want to use LiveView to build a Stopwatch.
• Reset button similar to Stopwatch in Alpine.js + Tailwind learn-alpine.js#2 (comment)
• Sync between clients
• Screenshot(s) of the app in action
• Future enhancements - what else would we like to add to this?

[nelsonic]

@SimonLab do you want to take a look at this or should I make an attempt while you
review the PRs assigned to you: https://github.com/pulls?q=is%3Aopen+is%3Apr+assignee%3ASimonLab ?

https://github.com/orgs/dwyl/projects/14?fullscreen=true

[nelsonic]

Gonna time-box T1h on this and see how far I get. ⏳
Keen to have at least the RealTime Sync between clients and a Screenshot in the README.md. 💭
Will create a PR even if I don't finish it now it will be a starting point. 👍

[SimonLab]

Do you have a specific implementation in mind for RealTime Sync @nelsonic ?
We could start by using PubSub and add persistence with Postges (the application has been created with --no-ecto, we could add Ecto back to the project but I'm not sure if it is worth it for this stopwatch) or ets if we don't want to persist the timers in database.

[nelsonic]

@SimonLab good question.
I was thinking just the same methodology we used in the Counter App: dwyl/phoenix-liveview-counter-tutorial
but just the PubSub part, I don't even think we need persistence right now.
That's the kind of thing we can just describe in the "potential enhancements" section.

[SimonLab]

Sounds good. I would even maybe use Agent instead of GenServer as the state of the Timer is simple.
Agree to delay persistence for a future feature.

[nelsonic]

@SimonLab yeah, an Agent is a good option.
Provided we can send the:

• start and stop time
• signals/actions (start|stop|reset)

over the socket we have a collaborative stopwatch.

Not saying I don't want to have persistence.
In fact if we can add auth and history it would be amaze.
But one thing at a time. 👍

[SimonLab]

stopwatch sync PR ready: #5
I'll add the reset button and logic on a next PR added to the same PR as the code is not too big for this feature

[nelsonic]

[nelsonic]

@SimonLab please see: #4 🙏 Thanks! ☀️ [when you are back at your desk on Monday!]

[SimonLab]

Readme is up to date, and sync is now working, closing

[nelsonic]

Thanks @SimonLab 🚀