Skip to main content
Question

Cursor Size and Color? Users can't see the standard cursor.

  • February 18, 2026
  • 2 replies
  • 44 views

I have a display that allows users to interact with a card.  The card and interaction work fine, but the logistics are causing some issues.
The display is mounted about 10 feet in the air and about 5 feet from the actual user work area.   The primary purpose for the display is to communicate data to everyone in the area, but a few times on each shift, a user needs to enter some simple data.
Enter the cursor.  On the large screen, at that distance, with safety glasses on, the cursor is very hard to see.  
All I want to do is change the cursor size and maybe color to make it stand out more.
The display boxes are Chrome units.  I can change the cursor details in Chrome, but once AppSpace launches, the cursor reverts to standard.

If would be nice to have a card that does not display on the screen, but allows background details to be edited such as cursor size, screen scaling, etc.

Any suggestions or Ideas?

Thanks.

-Mike 

2 replies

Dawn Wayland
Forum|alt.badge.img
  • Community Manager
  • February 18, 2026

@WKK_Mike hi there! Good to see you again! I just wanted to let you know that your Customer Success Manager and Account Executive will be reaching out, if they have not already, to try and set some time up with you. I know you have a few things you are working on and through and we wanted to see what we could do to assist, so be on the look out for that email. In the meantime, I hope one of our awesome community members may have some great ideas for you.

That distance/height combo definitely makes for a "where’s Waldo" situation with a standard cursor! Since Appspace tends to override system-level ChromeOS cursor settings once the PWA or kiosk app initializes, here are a few things I found  to consider:

Potential Workarounds

  • CSS Injection: If you are using a custom HTML/Channel card, you can often force a cursor style via CSS. Using cursor: url('large-cursor.png'), auto; within your card code might bypass the default system reset.

  • Appspace Settings: Check the Device Properties within the Appspace console. Sometimes adding specific player properties can influence how the webview renders interactive elements.

  • Touch/Remote Alternatives: Since the screen is 10 feet up, have you considered a "remote" interaction? Using a mobile-friendly version of the card that users can access via a QR code on their phone might eliminate the need to squint at a cursor altogether.

I'll keep an eye on this thread to see if anyone has successfully "pinned" a custom cursor size on Chrome units specifically—let me know if any of these ideas work for your setup!


  • Author
  • Participating Frequently
  • February 18, 2026

I would love to be able to use the QR interface more.
Unfortunately, our onsite systems are not accessible from outside the office network.  A phone would not have access to our internal system so it would be hard to send the data back in through a cellular connection.    I could put a second workstation in place, but it would defeat the goal of having the AppSpace system handle the signage and the user interface.  A cost saving move that eliminated a costly workstation that was only used for a few datapoints a day.
The user interface is a custom site accessed through the web card, but it is generated by a system we cannot access or change easily.  I have tried an Iframe to inject code but that has not worked.  I was hoping to find a way to ‘adjust’ that PWA override somehow.