Slides from a meetup talk in which I explained how I could leverage Phoenix LiveView's unique architecture to build a simple solution to track time spent by users visiting pages in the application.
customers use our platform and analyze their behaviour. As a LiveView evangelist, you told them we could do this natively and don't need any 3rd party services. 2
a session and store page view details in the database. Track how many seconds the page content may be at least partially visible. This means that the page is in a foreground tab of a non-minimized window. 3
that receives events, updates its state, and render updates to a page as diffs. 7 initial assigns updated assigns send html/diff event updated assigns new url msg updated assigns mount handle_params render wait handle_event handle_info
that receives events, updates its state, and render updates to a page as diffs. 8 initial assigns updated assigns send html/diff event updated assigns new url msg updated assigns mount handle_params render wait handle_event handle_info
that receives events, updates its state, and render updates to a page as diffs. 9 initial assigns updated assigns send html/diff event updated assigns new url msg updated assigns mount handle_params render wait handle_event handle_info When do we stop?