I re-read How Google Works, Engineering at Google, etc. Kind of ironically, YT delivered these fantastic talks from 2011:
Google I/O 2011: HTML5 versus Android: Apps or Web for Mobile Development? https://youtu.be/4f2Zky_YyyQ?si=rbKgYi7Rck-6y3qE
Or HTML5, CSS3, and DOM Performance, Breaking News at 1000ms with Patrick Hamann
This was and still is fantastic stuff.
The next step would be to drop the unofficial requirement that every manager be able to code. MBAs at Google: regression to the mean.
Old Google was inspirational; new Google seems to evolve into yet another drawing board MBA construct.
Sure you could use a react based app with some of the compilers but it’s like opening another bag of worms.
We have much better features for building offline apps than we did before html5 anyway (local and session storage and web workers)
Offline apps aren’t as common because they don’t make money and if someone is using a web browser 9 out of 10 times, they have an internet connection.
Profit centres, lacking any understanding of costs, are scared to increase them and fixed on reducing them, even when short-term profit destroys long term market share. Mostly because profit centres reward on a short cycle and have high turnover as staff seek bigger profits.
----
[1] this takes time: after _years_ of saying I'm going to I've finally started experimenting with using Kagi for search instead. It also takes _good_ alternatives, a paid option won't be seen as good by many.
At least Google's M.O. has mostly been to make stuff and then just throw it out into the open (with no support). Apple has been the opposite, ingesting the ideas and features of whole other companies without buying them, because they control their own little ecosystem.
Yes, developers can use basic/locked down UWB functionality in their apps, but no they cannot run it in the background constantly like Apple does for their airtags, essentially making it useless.