It’s wrong. Please fix it.
@bbbblinq: It baffles me that this is a hill LingQ is committed to die on. Even though LingQ is on the wrong side of established UI standards.
Users clamor for a fix, even LingQ could easily fix it, but by some bizarre stubborn principle LingQ absolutely refuses to throw a bone to its paying customers.
I don’t see a problem with the feature. If you complete a lesson why would you want the words you didn’t LingQ to keep coming up? I agree that a confirmation step, or moving the button somewhere else so you’re less likely to accidentally complete, would be beneficial.
Why do you claim to not see the problem if you mention it yourself, accidently completing the lesson. That’s the whole point. It is like the responses of the devs stating that the idea of lingq is what is happening now upon completing a lesson, completely ignoring the fact that noone is arguing that, but the design choice regarding the page layout leading to accidently finishing the lesson. So it is not as if we don’t wan’t the remaining words to be marked known upon completion, but a layout design that doesn’t cause the lesson completion to happen accidently over and over again.
Why isn’t it possible to move the finish button to a different location? It’s probably a matter of minutes to change the coordinates of the button gui, moving it down- or upwards a bit. There is more then enough space. And wasn’t there a time were developers came up with solutions to problems reported by their customers as opposed to customers have to come up with solutions to problems just to get ignored by the developers?
I saw it on Android.
Do you have rooster tools? Those have added a ‘are you sure’ option. But obviously you have to pay for them. Not everyone can afford/wants to pay for additional tools to make Lingq work. But it prooves its easy enough to do (for someone with skills obviously! Not easy for me LOL)
I just don’t get this. How difficult can it be to NOT click on the “Complete Lesson” button? The only reason why it might happen is if one were flipping through pages super quickly, but why on Earth would anyone do that when the whole idea behind LingQ is to read?
Can you explain the need to flip through pages, or post a screenshot showing why it’s so difficult to avoid clicking on the button?
Thanks for letting me know! I do have the Rooster tools, and I think they were updated recently. I’ll give it a try. (After making sure there are no blue words in the lesson.)
In an earlier post, I wrote out a few ways that can happen… (not an exhaustive list).
But the lesson editor doesn’t have a “complete lesson” button. You can’t accidentally complete a lesson when you’re in the lesson editor.
I generally edit sentence by sentence.
What caused me to accidently finish the lesson once was that I had clicked on the “next page” button, but the website didn’t respond. So I clicked the button again (after 2-3 seconds). However, the website did recognize both clicks, even though the response to the first one didn’t happen immediately.
What happened in the end was that the first click of mine got recognized delayed and the second click was responded to as if I had done it on the next page, which was the last one. I admit that this doesn’t happen every day, but considering how buggy the webpage often is, this can happen often enough.
Another possible source of this issue is that the finish lesson button often uses the wrong image, making it look like the next page button. If you don’t pay attention to the green line at the top or if the lesson has a lot of pages, it can easely happen that you don’t expect a click to end the lesson.
And to rephrase your (somewhat arrogant) question: How difficult can it be to move the complete lesson button to a different spot, considering the sheer amount of unused space on the webpage?
Both the webpage and the app simple demonstrate a whole lot of issues in regards to ui design choices. The webpage with its unnecessarely large icons compared to the app with its small, fixed-sized icons and its fixed orientation. And don’t get me started on how the translation is displayed. The finish lesson button is just the tip of the iceberg, to be honest.
Excuse me somewhat ranting, but I really don’t get why people nowadays tend to argue against a solution for a problem, if the problem, the solution suggested (move that button somewhere else) as well as the implementation (which probably would take less time then this whole argument here) don’t effect them at all.
Maybe you can make me get THIS.
Greetings
So do I. But I still don’t see how you could accidentally go from editing to completing a lesson without first leaving edit mode. Unless there’s another edit mode that I’m unaware of.
You are correct, I went in and out of edit mode. I used to edit a LOT. So many frustrations. But I’ve mostly stopped editing these days. Too exhausting.
My issue with this thread and others I’ve seen is more around the attitude than the actual complaint. Cuz y’know, no one is forcing you to use this software. In the grand scheme of things it’s a minor issue which is easily worked around if you pay attention. There’s absolutely no reason for folks to be this enraged over it. After using it for a few weeks every day I’m pretty sure LingQ is not a simple application from an engineering point of view. It’s actually fairly rich in terms of features, and the whole thing is built on top of user-generated stuff rather than set lesson material. Meanwhile, I imagine it’s working with a budget comprising a fraction of DuoLingo’s and probably has an order of magnitude fewer engineers. I’m a software engineer, so I suppose I take issue with insinuations that these engineers/designers are incompetent or don’t care about your issue. I promise they do care.
First of all, I and as far as I recall no one else is calling the LingQ staff incompetent. And I am very well aware of the discrepancy between how “easy” something might appear to be implemented versus the real effort involved. For some reason people who are proficient in something (or claim to be so, as I have no means to verify that) always seem to assume everyone else doesn’t.
That beeing said, the only response that was brought up by the devs was that “this is how it is supposed to work”. Now, what am I to do with that? The request already calmed down to a “move the button to a slightly different position, please ”. If there is a reason why this isn’t possible or harder then I may think I am happy to hear it. So the “enragement” you seem to experience is also partly more about the response then the actual issue.
LingQ is more of a service then a finalized product, so of course people take the possibility for further improvement into consideration when asking themselves whether they are willing to pay the not so few bucks for what is essentially a reader software. And the devs are communicating exactly that. “We are looking into it.” “We see what we can do.”
And I really don’t know what is the “grand scheme of things”, but calling something a minor issue just because it isn’t one for you while telling people to “pay attention” is exactly the kind of unconstructive arrogance that get people enraged. And whether not using this software is a solution the LingQ devs would favor …?
Hmm, I’m not trying to be arrogant or condescending. I’m simply stating that engineering teams have to prioritize work and a UX annoyance will always take lower precedence over a bug that cannot be worked around, or new features for that matter. The fact they haven’t done anything about doesn’t mean they don’t care about user pain points, it simply means that it isn’t a big enough issue to warrant immediate action, despite the clamor of some passionate users.
Perhaps you personally did not suggest incompetence (never said you did) but I have definitely seen that word used the describe LingQ and/or the team working on it, due to this very issue, in other threads. This thread also exhibits plenty of inflammatory writing directed at the LingQ team. Again, as a software engineer, it bugs me. Not much else to say.
I have called the LingQ team incompetent, particularly on this issue. Users, i.e. paying customers, endlessly complain with excellent reasons. LingQ could fix the problem easily and won’t.
I stand by what I said.
does it matter why i don’t want words to be automatically to known? It seems that it would be easy to make it a choice to automatically move blue words to known or keep them. a lot of people seemingly want to keep them
It matters because if we know more, maybe we can help you figure out how to get around the issue.
I assume it would be relatively easy to make it a choice to keep words as unknown, but I suspect the team is a bit wary of giving people the option to remove the one thing that makes LingQ work as well as it does. If people were to choose such option in the settings, there’s a huge potential for people to then give LingQ bad reviews because “They’re charging money for what is merely an e-reader”.