I'm working on https://github.com/styluslabs/maps/ including a new 3D map engine (based on Tangram-ES) and JS plugin support, so while there is no offline routing yet, support for additional online routing services can be added by users.
I've built a server for generating OpenStreetMap vector tiles on demand from a GeoDesk database, which is barely larger than an .osm.pbf (100GB vs. 80GB for current planet.osm.pbf) - much smaller than a PostGIS instance: https://github.com/styluslabs/geodesk-tiles
I believe QML ListView actually does support kinetic scrolling - Qt calls it "flicking". To get behavior closer to React Native, it might work to decrease the value of the Flickable flickDeceleration property [1].
That said, my troubles with Qt's performance and behavior on mobile led me to create my own cross-platform GUI library: https://github.com/styluslabs/ugui/
Getting sufficient antialiasing quality for 2D graphics is difficult on GPUs. https://github.com/memononen/nanovg accomplishes this with GL2/GLES2 level hardware for most of the stuff one would want to render as part of a GUI. My project https://github.com/styluslabs/nanovgXC supports rendering arbitrary paths with exact coverage antialiasing, but requires GLES3.1 or GL4 level hardware for reasonable performance.
Regarding aluminum vs. steel - I've had two aluminum frames crack after a couple years of normal riding (no crashes). Trek, to their credit, honored their warranty and replaced the bikes. Given enough time, aluminum will always fail; steel will not: https://en.wikipedia.org/wiki/Fatigue_limit
I'm working on computational chemistry, with the very long-term (decades) goal of designing molecules (proteins/enzymes) for things like artificial photosynthesis and molecular computing (chips still rely on the bulk properties of semiconductors; for miniaturization to continue, at some point it will become necessary to design molecules to function as logic and interconnect).
For my cross-platform app, I was originally using Qt for desktop platforms and Android. I was fairly happy with Qt on the desktop, but less so on Android, in part because I was using Qt Widgets - Qt Quick is the newer, preferred way to build GUIs in Qt, at least for mobile. Around 2016 I started looking into an iOS port - at the time, Qt for iOS was fairly immature and there was (is?) some uncertainty about licensing requirements for statically linking Qt on iOS. Having already spent more time than I wanted fighting various problems with Qt on Android, I decided to consider alternatives and ended up creating my own SVG-based GUI library that I now use across desktop and mobile:
One way that SVG could be used for multipage documents is with a convention that the top-level <svg> tag is the document and child <svg> tags are the pages - this is what I do in my app. I also use the fact that gzip files can be created with independently decompressible blocks to create svgz files with page-level random read access [1].
But another barrier is that browsers refuse to support SVG fonts. One supposed reason for this, the lack of hinting support in SVG fonts, is less relevant now with high DPI displays - macOS no longer does hinting at all I believe. The additional effort to support SVG fonts is really minimal [2], so it seems strange that it's intentionally omitted.
I've just released a fork of nanovg that does GPU rendering a bit like Pathfinder, so it can support arbitrary paths - nanovg's antialiasing has some issues with thin filled paths. It also adds support for dashed lines.