Unigram
Unigram copied to clipboard
There is a lot of UI lag and dropped UI interactions
The UI has frequent jank and lag. It seems like you are giving priority to backend data handling and ignoring the importance of responsive UI.
Sometimes UI elements have to be clicked 2-3 times before they respond (ie, clicking to switch to a different chat often doesn't get a UI response) so it seems that you are dropping user inputs when the app is busy rather than buffering them.
UI responsiveness should take priority over data processing handling.
Unprocessed data should go into a buffer while you handle UI events, then after you handle the UI you should process the buffered data. Same for UI. Don't just ignore a user input when you're busy, put the input into a data buffer then handle it when you have resources.
User doesn't care if it takes longer for a message to appear but if you don't respond to their input or display stuff they are typing they want to stop using your app.
Unigram is fast and responsive here, what is your device hardware?
Any kind of input is handled by UWP (and then by Windows/Microsoft) and not by the app, that just consumes data provided by the system.
Your UX doesn't sound any normal tho, never experienced anything like this in 3 years developing and using this app (Even now that I'm forced to use it in a VM)
Can confirm that UI has a lot of janks, especially with multiple account (I have 2 accounts, all have multiple groups and channels which usually have 1000+ chats in every group every day)
I can help profile it if you need the data.
For example, when you activate the search bar, then click on a quick suggestion. Then you have to wait around 2 seconds for a chat to appear.
For example, when you activate the search bar, then click on a quick suggestion. Then you have to wait around 2 seconds for a chat to appear.
That sounds more pointless that the issue itself, since it depends on Telegram servers and using every client the delay is the same
That delay does not matter. UI must appear first instantly (maybe with dummy placeholders until the server responds). But otherwise, you just don't understand what is going on
I think it's not a news that UWP lags like hell?
Well, I think that's a small detail that just 0,1% of users would notice, or at least looks in this way with my laptop (maybe in PCs with worse hw it'll be a lot worse)
If you click on a message sent by you in search results the app is going to lag due a bug in the Windows platform that Microsoft never fixed: https://github.com/microsoft/WindowsCompositionSamples/issues/329
What about intermittent freeze when typing, navigating, or general use of the apps? I sometimes encounter freeze for up to 2secs, UI is totally unresponsive, clicking anything won't do anything. I can still type tho (with it freeze but the text will eventually registered after it unfreezed)
Sometimes, text is doubled too, for example i type this and it also typed "nd it also typed" a chunk of it from micro freezes.
(maybe in PCs with worse hw it'll be a lot worse)
Core i7 8650U, 16GB RAM, SSD NVMe
(maybe in PCs with worse hw it'll be a lot worse)
Core i7 8650U, 16GB RAM, SSD NVMe
Same hardware here, apart from the Ram
I think it's not a news that UWP lags like hell?
I agree in general but not in my case. This case is a matter of algorithm and UX design
I think there’s a lot of confusion going on here as any action that require some loading always update the UI first and then loads the data.
Can we go back to the original issue at hand?
I think there’s a lot of confusion going on here as any action that require some loading always update the UI first and then loads the data.
But why then chat section of a window does not appear instantly when I click on a quick contact suggestion?
But why then chat section of a window does not appear instantly when I click on a quick contact suggestion?
What is this?
Because UWP is really slow to initialize and load the UI
But lag only happens for quick contact suggestions. It does not happen for conversation opened from conversation list.
It doesn't happen for quick contact suggestions here
It doesn't happen for quick contact suggestions here
I have understood that to reproduce you have to close the app and open it again, it seems to happen just the first time, once loaded the next times it won't happen
Then as I said it happens for the first chat you open, doesn't depend on the interaction source
No, it happens always. 1-2 seconds lag is rare while some comparably noticeable delay happens always
Here this just started happening recently as well for me. Here is an example:
@hatzkel you are writing in the wrong ticket
@hatzkel, I had the same issue until I updated to 3.13.2647
I just updated and it started happening. :O I figured this was the right ticket since I was considering it "dropped UI interactions and or ui interaction lag" 🤷♀️
I just updated and it started happening. :O I figured this was the right ticket since I was considering it "dropped UI interactions and or ui interaction lag" 🤷♀️
You have just posted it in the wrong ticket, creating confusion. Next time, kindly check the ticket description, from which you'll understand what it is about
Wow your English is so horrible that I don't even think you understand what I said. You don't see me trying to be smart in Italian maybe you should stick to coding and speaking Italian rather than handle support tickets written in English.