We are planning on enabling automatic text to speech audio for all lessons which would provide the full text listening mode for all lessons. However, the idea to offer a text only view that way is one to look at. Thanks for the suggestion.
I often import youtube clips which don’t have a separate subtitles, but are automatically generated. In the v4 I could edit the text by copying it to open office and remove the line breake easily. But now you seperated the text into paragraphs, which you can select individually. Now I have to remove every paragraph before I can remove the line break. Also the editing function is much more complicated. Maybe you need to separate them to identify meaning, but right now it isn’t very user unfriendly.
There is an option to View Translation in the … menu in the Reader. It now shows that translation in line.
It is frustrating for many when given a new interface for a product that you like and have learned how to use. If you just give it a try I think you’ll get used to it and like the new interface too. The reality is that leaving things unchanged forever is really not an option for any product.
I just tried LingQ 5.0 using Brave browser and my good old Macbook air 13inch from 2014. Works just fine and really like all the changes done. Thx!!
I think this will overall become a good version, but I am baffled why you guys released it at this stage since it is still very “beta-ish” and clearly work-in-progress. Also, clearer communication and polls could certainly have prevented a lot of frustration by users. I do not want to “should have” you guys, but please keep this in mind for V 6.0. 
very bad answer Mark. Its hard to believe you think that more clicks and scrolling is an improvement that people should get used to
The reality is that we have had a beta going for a long time now. But, it’s impossible to anticipate how things will look once thousands of users get their hands on it. With so many different users, with different computer, resolutions, browsers, zoom settings, it is not possible to launch without there being some issues.
The effort required for us to maintain a separate beta version was becoming more and more difficult and we felt this version was ready and would benefit from us being able to focus on it without worrying about maintaining two separate versions.
Many of us have been using the beta version happily for months. The reality is no matter when we launched, many users would complain. That is what users do since they were happily using the product and now have to relearn how to use it. But, it’s a necessary part of the upgrade process and we will all benefit in the long run.
We all just need to have a little patience as we continue refining and improving things.
There is a notorious thing in Russia about how our taxes are spent on the road surfacing. The thing is you’ll have more profit as a developer if you ensure bad quality of the road surfacing, because every year you’ll have to do resurfacing all over again. As a result, we have extremely corrupted rich officials and the very same roads are permanently under development but mostly just broken.
I think the purpose of 5.0 is to generate employment. We were constantly told about back-end and how it allows the team to quickly fix problems. Honestly I can’t be sure about the back-end, but the rest of the update has even more problems and bugs. And the chief among the problems is a complete lack of understanding UX.
Get used to bugs and extra clicks they say. Users already come up with CSS addons to fix this mess 
And this was going on for almost 2 years.
Since this thread is getting quite ungainly I am starting a new one. Please post future feedback there. We are reviewing all feedback even if we don’t respond to all. We are continuing to optimize things as we move forward.