For native front-ends most of that work has been done for me already though. I can't remember the last time I've had to worry about performance profiling or heap management in a native front-end - and we build iOS, Android and Windows apps that process huge amounts of (medical) data. Hell, I don't even have to make my own animations to have good looking apps because that's all built into the rich native components that I use.
On native platforms - if I stick to standard, well-known, stable components and if I follow good coding practices and recommended techniques - my apps are fast by default. And I'm just gluing things together most of the time. Easy, scrumptious pie! I can save the work of "squeezing every drop of performance out of my code" for back-end processes.
Things just work for the most part - unlike the web where half the sites that try to do something "fancy" like fixed elements just serve to make scrolling slow and clunky - hence the need for this tool.
On native platforms - if I stick to standard, well-known, stable components and if I follow good coding practices and recommended techniques - my apps are fast by default. And I'm just gluing things together most of the time. Easy, scrumptious pie! I can save the work of "squeezing every drop of performance out of my code" for back-end processes.
Things just work for the most part - unlike the web where half the sites that try to do something "fancy" like fixed elements just serve to make scrolling slow and clunky - hence the need for this tool.