Reminds me of this 2013 story where they moved to native Java for Android and hit limits with e.g. too many methods and instead of refactoring or just not bloating their app they hacked some internals of the Davlik VM while it's running during app install: https://engineering.fb.com/2013/03/04/android/under-the-hood...

Mobile is where the users are. Desktop users are vanishing before our eyes as a market segment.

For some application certainly. Instant messaging of course has many strong point in term of what is to be dealt with. Short messages, photos, quick visios.

But to edit large document, visualize any large corpus with side by side comparison, unless we plug our mobile on a large screen, a keyboard and some arrow pointer handler, there is no real sane equivalent to work with on mobile.

Yeah, but the majority of people who would've been daily desktop or at least laptop users some 10 to 15 years ago now make do with a phone. Most people do not need to visualize any large corpus or edit large documents. Similarly, there's a great deal of phone users who's first interaction with computers was via a smartphone.

A 2012 iPhone and a 2025 Windows PC shouldn't be assumed to have the same tradeoff set just because "web vs native" is found in each description.

It's a tradeoff, different companies are allowed to chose differently or even to change their mind after some time.