We are not really using Channels, but our LiveView is a process so I guess that should work, right? Presence Setup The first thing I notice is this: Provides Presence tracking to processes and channels. First we'll head over to the docs and see how it is setup. Let's create a basic LiveView boilerplate: defmodule doĪ small LiveView that shows the number of readers of a post using Phoenix Presence I am definitely planning on doing a writeup on using LiveView components, but for our usecase we simply need the basic LiveView. Components basically are small building blocks that either are stateful or stateless. LiveView is maturing quickly and currently also has a concept of Components. At a later stage I will probably want to make it more generic, but for now let's focus on getting this to work for this blog post. Just like we did in my last post when I rendered scrambled text.

To do this, we'll create a very small LiveView component inserted in the markdown of our post. So where do we want this indicator? Preferably this would reside on the same page as a blog post so that it would indicate for every individual blog post how many users are currently reading that article. We'll add an indicator at the top of the page that shows how many people are currently reading this page. We are going to build a very simple but powerful feature for the blog you're currently reading. Amazing! I will definitely dig into the internals at some point in the future, but for now I wanted to show a very simple example of using Phoenix Presence inside LiveView! I love the way you can very simply add Phoenix Presence to your Phoenix app and easily track user's presence with it. Normally I'm not a big fan of things that seem like magic, but in the case of Phoenix Presence I actually love it. Phoenix Presence inside LiveView |> A Simple Example

Phoenix liveview examples