We needed to fix it fast since it was at the end of a sprint. I just wanted to solve the problems with the other implementations.
You could feel and see the performance from not beeing 30fps every was to having smooth animations with 30fps+ everywhere.
Also, I would need to ask if I can show these metrics in public since this project is for a client.
In general, if I see some performance issues in a small part of the app I use the performance tool from firefox or chrome and dig into the charts and output since you can see what caused what in detail.
interesting article! thanks for writing this.
I'd just like to ask if there was any way to check on the performance gained by implementing things in this new method
Hey thank you :)
Sadly we did not compare before and after.
We needed to fix it fast since it was at the end of a sprint. I just wanted to solve the problems with the other implementations.
You could feel and see the performance from not beeing 30fps every was to having smooth animations with 30fps+ everywhere.
Also, I would need to ask if I can show these metrics in public since this project is for a client.
In general, if I see some performance issues in a small part of the app I use the performance tool from firefox or chrome and dig into the charts and output since you can see what caused what in detail.
wow, thank you for such a detailed response!
and yes, i can imagine the difference between < 30 fps and > 30fps being quite noticeable even without hard numbers :P