Touchscreen + Tablet support

[SCA-ZMT]

Title: As a user, I want the web app to have better support for touch device and 3d mouse.

Additional Notes:
User Training: Consider providing a brief tutorial or notification to inform users of the new PWA capabilities and how they can install the app on their devices.
Performance Monitoring: Implement analytics to track the usage of PWA features, such as installation rates, offline usage, and push notification interactions, to gauge user engagement and adoption.

We should address both, S4L and oSPARC. Thanks.

Event Horizon

Preview Give feedback

No tasks being tracked yet.

Tasks

Preview Give feedback

1. Decide: When to get UX feedback from NK and power-users (not too early, not too late)
2. Add support for 3D mouse #1545
   +0
   
3. Icons for touchscreen get blocked by CORS policies osparc-simcore#6453
   a:frontend bug +2
   

MartinKippenberger

Preview Give feedback

1. Tutorial/Demo with MaG

EisBock

• Gestures support #1370
• Dashboard friendly to small screens (tablet-sized) #1369
• Make oSparc a Progressive Web App (PWA) #1586

[jsaq007]

I think the best approach for this would be to get the following devices the 3rd could be optional as market share is quite low and is a real budget device which probably would be safe to assume not many if any user would use our app on it.

Tablets

1. Apple iPad Pro (latest model)
   Operating System: iOS
   Features: Large screen size, high resolution, powerful processing capabilities. It represents premium tablets and ensures testing for high-performance devices.
2. Samsung Galaxy Tab S8
   Operating System: Android
   Features: Offers a different ecosystem with Android, high-resolution display, and versatility in performance and compatibility, representing high-end Android tablets.
3. Amazon Fire HD 10
   Operating System: Fire OS
   Features: More affordable, runs a modified version of Android. It's important for testing how web applications perform on less powerful and budget-friendly devices.

I wouldn't add support for mobile phones at this point but it would probably be worth having a phone landing page for phones and not allow the user to login as it provides a bad impression as it's not easy to logout at this point on a phone.

[jsaq007]

@mguidon I understand you might already have various touch devices we could use for testing and working with?

[mguidon]

Totally not.