Feature Requests

Under “trending”, there are often news releases from 2023 and even later. People new to LingQ have not figured out that LingQ sorts newsletters and blogs by the oldest to newest. Oldest-to-Newest makes sense with BOOKS, but this is user unfriendly for the news and with blogs. IMO, the default should be "Newest-to-Oldest," and "oldest-to-newest" for books. If both defaults cannot be done, "newest- to-oldest" is the better default for both. I use and highly recommend RFI, Radio Français International, but LingQ makes it difficult to easily find the latest edition. RFI is sponsored by the French government, and has many things that are great for new learners. LingQ rarely features the latest news release. Please make it easy for us for people new, and for the rest of us. For those who are old enough to have had a stack of newspapers at home, NO ONE (especially librarians) would stack newspapers with the oldest newspaper on top of the pile and the news on the bottom. Oldest LingQ “Newspapers” are ordered on top of stack :-(

When adding a lesson yourself, it's a bit difficult knowing which level it belongs to. It would be nice if this could be suggested automatically, perhaps after the transcription has been completed.

there are some phrases not really always staying together, like pick something up, and I only want to creat a LingQ of “pick up”. And this problem is more deadly for the German separabale verbs(which are very commonly seprated and German learners cannot creat LingQ for them)

Propose adding a confirmation modal that appears by default when users move to a new page in the reader. The confirmation would ask the user if they wish to move their unlingqed tokens to known and provide an option to not show the modal in the future. In addition, propose adding a toggle to the settings for users to be able to re-enable this confirmation. Example: "You've completed a page! Move all unlingqed words to known? YES / NO __ Don't ask me again." This proposal attempts to solve a few issues at once and provides a few benefits besides: New users often don't know that paging (by default) marks all their blue lingqs as known, which frustrates them, especially as there's no easy way to reverse the action The move-to-known behavior is fairly destructive—it's extremely tedious or requires third-party scripts to reverse it. UX best practice recommends having confirmations for destructive actions like this, especially if they are unintuitive and would catch the user by surprise. The proposed behavior doesn't change the default intended use of the app, while also informing a new user how the app wants to behave Expert users may get annoyed by having a confirmation every time they change pages, so providing the option to opt out of future confirmations keeps this change for new users from affecting expert users' experiences.

When I’m listening to a lesson and I click a word to bring up the dictionary, if I click to hear the word, the audio volume is much lower than the lesson volume. Could the volumes be made the same?