Cursor amongst different devices

[LuchoTurtle]

Currently, the cursor is calculated on the screen percentage, which should translate into a smooth experience across devices (desktop, tablets). So there isn't a concern there, since calculations are being made on the client's side viewport and sending it over to Phoenix's server.

A few questions arise, though:

• is this feature redundant in mobile devices? People using touch screens will just tap and the scroller will just show randomly on the desktop view.
• what happens if the page is scrollable? How will tracking occur here? (calculations will be different)

Just wanted to open this out there =)

[nelsonic]

@LuchoTurtle thank you very much for opening this issue to capture the discussion on this! 👌

Hopefully the UX demo I gave during standup this morning was clarifying of where we see this feature going in the future. But for anyone else curious about this, I've opened an issue to 'splain: dwyl/app#295

Quick answers to your specific questions:

1. It's definitely not "redundant" on mobile devices. It's less useful for Smartphone because there isn't a concept of a cursor on most of them with the exception of those with a Stylus. But on iPad (or other tablets) there is a "pencil" (or other stylus) for which we can capture movements. And on a Smartphone without a Stylus, we can still capture tap, scroll and drag+drop events which can then be recorded for replay-ability. On a Smartphone we will show the cursor of any other person who has a cursor. i.e. any colleagues using a Desktop 🖥️

2. Pages will inevitably be scrollable once there are 10+ items. For this we need to capture what is visible in the viewport. This is way beyond the scope of the current tutorial, but if you want to dive into it, please open a new issue.

[tal32123]

I used the demo and on different window sizes it does not show the cursor location properly.