Best platform for Workshop Manuals?

[RayMe]

Has anyone sorted out which media platform/operating system works best with the current online Workshop Manuals, etc?
I’ve tried a few different systems and so far best results have been with an Apple Mac….not working well with mobile devices (phones & iPads) that use iOS.
Has anyone tried using Windows or other non-iOS platforms.
Ideally the “front office” would dial us in on which platform their system was designed to work with…..long run it would save them bandwidth from us whacking away at it with whatever we have….(Jan C- that’s for you!)

In any case I do really like using it to become more familiar with the ins and outs of my vehicle…..

 

[Ever Pragmatic]

I found the iPad wasn’t great with the software.. not tried the pc yet..

 

[[ Adam ]]

Chrome on Fedora 42 worked fine

 

[slukell]

As it is a web application, I believe the compatibility is more about the browser than the system itself (as long as it is modern enough to render 3d graphics efficiently). It works fine in Chrome for me, so any Chromium based browser should work, like Edge, Opera etc.

The tablet/phone v desktop question I believe is mostly about screen size, orientation and touchscreen v mouse.

I figured out how to make it work well enough on my phone (Pixel 9) with some tweaks to zoom level, full screen, desktop mode etc, but desktop/laptop is by far the easiest to use it in my view.

The most limiting factor (by far) is the lack of content transfer optimisation. This application could be so much faster with the use of caching at different levels. The only way I could make it work from AU was to set up a high-speed VPN connection to NL where the application is hosted. Still extremely slow, but at least it doesn't time out and get stuck indefinitely.

 

[ECrider]

I'm opening it on a modern imac. Very slow to open anything at all. Something popped up in the Ineos App in the bottom rh corner saying something about making access quicker click this and mentioned 2mb. Unfortunately it's all greek to me. Are there any settings within the app I need to apply to make the thing run quicker?

Efharisto!

 

[RayMe]

As it is a web application, I believe the compatibility is more about the browser than the system itself (as long as it is modern enough to render 3d graphics efficiently). It works fine in Chrome for me, so any Chromium based browser should work, like Edge, Opera etc.

The tablet/phone v desktop question I believe is mostly about screen size, orientation and touchscreen v mouse.

I figured out how to make it work well enough on my phone (Pixel 9) with some tweaks to zoom level, full screen, desktop mode etc, but desktop/laptop is by far the easiest to use it in my view.

The most limiting factor (by far) is the lack of content transfer optimisation. This application could be so much faster with the use of caching at different levels. The only way I could make it work from AU was to set up a high-speed VPN connection to NL where the application is hosted. Still extremely slow, but at least it doesn't time out and get stuck indefinitely.

Ahhhh, you do this! Caching would seem to smooth things out. I did see several times while using the system that it asked if I wanted to increase access(?); first 2 GB, the 5 GB. Was this a form of session caching? I did accept both times and sections loaded faster. This would really become a great tool (for field work…) if mobile optimized….and certainly better for the “way outs” in an analog form. Somebody will figure out for sure. Still hunting for the optimal OBDII !