Kivy's marketing seems to be targeting LOB apps. If I was going to develop one of those, I'd optimize for something standardized and easy to maintain (HTML/JS) vs. the performance benefits of a native UX or cross-platform framework.

Thanks for the reply! If touch handler delays are intentional then it seems like an advantage, not a weakness — who am I to disagree with UX experts employed by some of the top-paying tech companies or Mozilla? This is really a synecdoche of the overall situation, from my perspective: some really good devs want absolute control over every part of the stack, and to feel “close” to bare metal as they code, whereas the dummies like me appreciate that someone did a lot of the hard work for us.

In other words: how would that demo hold up if you asked them to recreate some popular react libraries, such as tables, graphs, and 3D simulations? When dealing with hard tasks (and network latency!) it seems like any platform-level delays would be quickly dwarfed by context-specific delays. And in the latter case, I’d rather have NPM than https://kivy.org/gallery.html !

PS did anyone else know NPM is now owned by Microsoft? We seriously need a revolution, or at the very least a figurative corporate guillotine. They own most of gaming, most of NLP/AI, most of dev tools, most of business/office computing, most of the OS market in general, most of… everything, it seems like. I’m just thrilled in hindsight that the windows phone failed!

" I have seen some mobile browser implementations that explicitly put large delays (hundreds of ms) into their touch handlers for example."

Why would they do that?

This delay can be worked around by using the standard viewport meta tag, which any web app built for mobile will be using.