Feature Requests

Lose against apps like Duolingo. As bad as Duolingo is, its success is undeniable. One of the keys to its success is their green avatar: the owl. The owl allows them to market themselves more easily. It allows them to position a powerful and memorable image in the mind of their users. However, you can do so much better. Remember the addictive game/app Pou? Steal the concept and blend it with Duolingo's marketing strategy, and you've got a winner. I mean, imagine how powerful it would be if LingQ users could use their points to customise their avatars just like the good old times. And on top of that, imagine being able to interact with the avatar and share it with others... Engagement would skyrocket if you're creative with this idea. Currently, points are of no other use than keeping the streak safe, which, personally, isn't an exciting usage. If bringing in many more users to the platform is one of your priorities, creating an engaging and fun avatar to play around with is a killer move in my opinion.

将这个每日目标改为通知，而不是对话框，例如在页面顶端停顿三秒自动消失的通知，这样会好很多，起到了提醒的作用，并且不会被太过打扰，安卓端目前是这样的，非常舒适，论坛中很多人都在抱怨在抱怨这个通知，它应该以更温和的方式运行。

I was interested in a Korean language Youtube video, for which there are no subtitles, so, I could not use the Lingq add-on. I downloaded the audio, and went ahead to import the audio using the menu item "import/from Audio" on the front page. Furthermore, I recorded the process, until the moment it was clear that the import had made up stuff. The Final result (see screen print) is that the last line on page 1 (call it line n ) is in the audio. Preceding line n should be line n-2 according to the audio. The line n-1 is fully made up and is never read in the audio. See the screen print for the last line ( n ), the made up line ( n-1 ) and the line preceding the last line in the audio (line n-2 ). If you look closely, you see that line n-1 is largely a copy of line n, except for the 4 last syllables ( 고 있어요 ). This line does not exist at this stage in the audio. I repeated the process several times, always with the same result. Could you please confirm my suspicion and let me know when it will be planned to be fixed? I will send the screen recording to the support email with a reference to the title of this feature request.

When studying a new language, I want to use a dictionary in a specific reference language. For example: Swedish → Danish Russian → Polish Latin → English Currently, changing the dictionary language requires manual adjustment in the settings each time, which discourages me from using it. I’d like the dictionary language to automatically adapt based on the language I am studying.

It would be useful to have a field added to the lesson similar to the "Liked" field. The status could be for the level of understanding which would help to select lessons for review. Pull Down could be something as simple as: Full Understanding, Partial Understanding, Not Understood or Complete Review or a comprehension percentage 100 75 50 25 0 I have watched hundreds of lessons and lose track of ones I wanted to review again. I was marking ones I understood with "liked" but that has the disclaimer every time and feels like you are taking credit for someone else's work. I am aware it coild be done with tags but it feels conceptually wrong.

We’re always looking for ways to bring more authentic, everyday content into LingQ. Right now, we support imports from places like YouTube, Netflix, Prime Video, TikTok, and various news sites via RSS. I’d love to hear from you about other types of content you’d like to see supported. Here are some ideas to get you started: Restaurant menus – great for learning food and daily life vocab. Street signs – short, practical text that you actually see in real life. Reddit threads or subreddit feeds – conversational, community-driven discussions. Live recording + transcription – record a conversation, lecture, or meeting and instantly turn it into a LingQ lesson. Memes – short, funny, often colloquial language from images. We would need to OCR the text from the image here and then clean it up. But that’s just the start! What else would you love to import into LingQ? Drop your suggestions below. We can’t guarantee we can add all of your ideas (some of them might be technically unfeasible at the moment…), but the more users seem interested in a particular type of content, the more we know to prioritise adding it.

I make screenshots of Kindle books a purchased, recognize them into text and upload to LingQ as a lesson. Unfortunately, Kindle format does not allow to choose not to split words being in the end of the line and thus ending with a hyphon. Would it be possible to add a function analyzing for wxtra hyphons and removing them?

In one of my Korean podcasts, I have a sentence, where the audio in sentence mode is cut short. I have made a screencast containing the error for you guys to enjoy. What happens is this: if the timestamp is as it should be, right after the end of the previous sentence, the sound only plays the last fraction of the sentence. If I cross the previous sentence, I get some of the previous sentence, plus the sentence I was aiming for. Of course, what I would expect is the whole sentence when the timestamps are correct. You can hear and see that in the screencast. I will send the screencast to support once I know who to address it to. Let me know. EDIT. I sent the screencast to support with the title of my feature request.

Full screen mode in the app so that when you click on a dead space it will hide the top progress bar and the bottom buttons (sentence, grammar, and flashcard buttons) Or have an option when you click the three buttons in the top right to go into full screen mode. It would be nice to read without visual distractions

In the current system in sentence mode, when the focus is lost, the current word rectangle is no longer visible and remains invisible until I press an arrow to go forward or backward. I would really like to have visible which word in the sentence is current, even when filling out a note or looking at the dictionary. It makes navigating a lot easier. In page mode, this already works.