-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Laggy UI #20
Comments
Nah, it was already laggy in the beta. It gets worse when you scroll up to request older messages. The more messages, the more it lags. You can help by creating a CPU profile in the browser and attach it here. |
Can confirm that it is very laggy. Should be one of the top priorities. |
Yes, it's a lot worse in Firefox. |
Yes, Webkit (Chrome/Chromium/Opera) is much faster in this regard. |
I've sent it to *SUPPORT… |
@dbrgn: Do you have any ideas how to fix this issue? It's really so bad that using the Web Client is not fun at all. Especially with Firefox it's a pain, however even with Chrome the performance is not great. |
Maybe upgrading to Angular 2 should bring a performance boost 🤔 |
@ovalseven8 yes, mostly #40. I hope that should speed up things a lot. We'll tackle that issue once we fixed the low(er) hanging fruits. @screendriver Angular 2 is a completely different framework. It would mean porting, not upgrading. When development on Threema Web was started, Angular 2 final wasn't released yet. Note that performance on Chrome seems to be significantly better than on Firefox. |
For 1.0.6 I have the feeling that toggling between different chats got slower. Perhaps can some of you check too? |
Try out 1.1.0, which was released today. 😃 |
Oh, I mean 1.1.0 of course. 😆 |
Since the UI is much less laggy now, let's close this in favor of #39. |
Well, I don't really think it's much less laggy. But #40 will hopefully improve things! |
It's still a real pain with Firefox. Threema should definitely focus on improving the performance and efficiency. While it's a lot better with Chromium (that I don't use), I think the performance could also be better there when opening chats. |
@ovalseven8 Sure but #39 covers that. |
Do not understand why this issue is not priority. A swift application improves UX dramatically and at the moment it's really bad. Some time ago I tried Chrome just for Threema Web and once I was using it for around an hour (and chat history grew) it also got that slow because loading of chats is an issue also for Chrome then. |
Threema Web is sometimes a bit laggy. I have got around 30 contacts and the UI sometimes is a bit slow.
I can especially see it when (fastly) opening the context menu of messages:
Personally I'd say in the beta (before the last RC) it was not so laggy…
The text was updated successfully, but these errors were encountered: