Agreed. The performance of the word dialog box isn’t good enough. It’s core to the functionality of Lingq. It should be super responsive with no glitches. It isn’t. If the introduction of ai is slowing it down, then either the ai should be fixed and tested properly now, or scrapped now.
Sorry to hear you are having issues. We will investigate it.
Also wondering if the downloading of the audio for a word may be slowing things down. If you are working quickly you rarely get time for it to play anyway. Perhaps a setting to turn off the downloading of the audio for words may improve performance and reduce load on the back end.
In other words, a setting to turn off the autoplay of the word’s audio. Pressing the speaker icon on the word would still download and play it, of course.
Major issues with iPad Mini 6 (iOS 18.2). The pages freeze for about a minute, and I’m unable to press words or turn the page. Restart of the app fixes the issue for only maybe 2 minutes. On my phone (Android) there seems to be not the same issue.
Yes, I wonder if there’s a big build-up of audio data in the cache. I agree that you don’t need instant pronunciation of a word. Tapping the word could download the individual pronunciation. I’m happy to wait for that. I’m not happy for the app to grind to a halt. Zoran and his team are looking at the problem, but how long do we have to wait? I tend to import whole newspaper articles. Maybe it can’t cope with large volumes of text. I think you may be right about the audio though.
The app seems a lot slower than using the browser. It’s all driving me mad. Is there any other software that does the same kind of thing but without so many bugs?