Generally not, but in this case I do. The proposed redesign[1] is essentially the same layout, but with a fancy theming. It's good practice not to break the fam

Generally not, but in this case I do. The proposed redesign[1] is essentially the same layout, but with a fancy theming. It's good practice not to break the familiar interface, but there's a lot to improve in terms of UI/UX in Thunderbird. For example: a) presented vertical layout is the same as it is today—you need to have a really high resolution (1080p+) widescreen to fit the entire window. Messages section could have rows with multi-line inlined metadata, thus be significantly narrowed[2]; b) threaded messages feed (or so called conversations) on the same screenshot is presented too vaguely for such an important feature, I bet I'll still have to jump between Sent/Inbox folders in 2018+...; c) replying to/composing a message is impossible to do in tabs[3] (10 years old), you have to manage separate windows. And there's nothing on this matter in current redesign proposal; d) not a single word/screenshot on calendar/todo-lists management; etc. Simply put, this is not the way to redesign such an important large application. Has there been any work done on analyzing user/task scenarios [4]? Any research was conducted on modern best practices? Instead of presenting a list with UI/UX features breakdown and several well-thought solutions, we're supposed to vote on "does it look exciting/professional?" beneath a single 800×500px screenshot. Answering the question: no, it doesn't. It's the very same application, hence stagnant. Do not take offense at the words about "stagnating product", this is what it is. [1] https://twitter.com/omgubuntu/status/855035593289609216 https://twitter.com/omgubuntu/status/855035593289609216 [2] https://errorfixer.co/wp-content/uploads/2016/12/slow-mail-app-mac-os-x.png https://errorfixer.co/wp-content/uploads/2016/12/slow-mail-a... [3] https://bugzilla.mozilla.org/show_bug.cgi?id=449299 https://bugzilla.mozilla.org/show_bug.cgi?id=449299 [4] https://www.usability.gov/how-to-and-tools/methods/scenarios.html https://www.usability.gov/how-to-and-tools/methods/scenarios...