[eternityforest]

I don't really think the performance hit is that bad, except in odd cases like embedding a browser in an Android app that has to be opened when you load it.

It doesn't matter if you have 200 layers of function call on a button click handler, it's going to run in 1ms compared to 200ms to even think about clicking it. Some stuff doesn't matter.

However, the code to render the page full of buttons and scroll it smoothly could be performance critical.

A one size fits all framework can afford to put tons of effort into optimizing the heavy operations.

Handwritten code might not even use GPU acceleration, because there's no reuse and nobody thought it was worth it to spend months on it.

[BenjiWiebe]

There's bad performance hits coming from somewhere.

Very noticeable if you are like me and run an older smartphone (Galaxy S5, 2014).

[eternityforest]

There was definitely bad performance hits on older phones after about a year. Not exactly sure what causes that.

Maybe something in the older Androids, maybe performance of the hardware has just increased so much that it finally caught up with software.

Older phones should be fast, just like old video games, but they haven't optimized that much, they just stopped making stuff slower and started mostly incremental gains and stuff that requires new GPUS.